Sjzl20092367-ZXWR RNC (V3.07.300) Alarm Handling Reference

ZXWR RNCRadio Network Controller

Alarm Handling Reference

Version 3.07.300

ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 Fax: (86) 755 26770801 URL: http://ensupport.zte.com.cn E-mail: [email protected]

http://support.zte.com.cn/

mailto:[email protected]

LEGAL INFORMATION Copyright © 2006 ZTE CORPORATION. The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations. All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION or of their respective owners. This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein. ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Date Revision No. Serial No. Reason for Issue

April. 20, 2009 R1.0 sjzl20092367 First edition (ZXWR RNC V3.07.300j+NetNumenM31(RAN) V3.10.410d)

ZTE CORPORATION Values Your Comments & Suggestions! Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers.

Please fax to (86) 755-26772236 or mail to Marketing Department, ZTE University, ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057.E-Mail to [email protected]

Thank you for your cooperation!

Document Name ZXWR RNC Radio Network Controller Alarm Handling Reference

Product Version ZXWR RNC V3.07.300j+NetNumenM31(RAN) V3.10.410d

Document Revision Number R1.0

Serial No. sjzl20092367 Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Make it more concise/brief

Improve the Contents Add more step-by-step procedures/tutorials

Improve the organization Add more troubleshooting information

Include more figures Make it less technical

Add more examples Add more/better quick reference aids

Add more detail Improve the index

Other suggestions

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

# Please feel free to write any comments on an attached sheet.

If you wish to be contacted regarding your comments, please complete the following:

Name Company

Postcode Address

Telephone E-mail

This page is intentionally blank.

Contents

About This Manual ............................................................ i

Purpose................................................................................ i What Is in This Manual ........................................................... i Conventions......................................................................... ii How to Get in Touch............................................................. iii

Chapter 1.......................................................................... 1

Overview..........................................................................1

Overview of Fault Management .........................................2

Fault View......................................................................2

Alarm..................................................................................2 Notification ..........................................................................2

Alarm............................................................................3

Alarm Property .....................................................................3 Probable Cause.....................................................................4 System Impact .....................................................................4 Handling Suggestion..............................................................4

Notification ....................................................................5 Notification Property..............................................................5 Probable Cause.....................................................................5 System Impact .....................................................................6 Handling Suggestion..............................................................6

Chapter 2.......................................................................... 7

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

198000002 Loss of Optical Transceiver Module Signal ..........8

Alarm Property .....................................................................8 Probable Cause.....................................................................8 System Impact .....................................................................8 Handling Suggestion..............................................................9

198000256 Ethernet Controller's Physical Link Off ...............9

Alarm Property .................................................................... 9 Probable Cause .................................................................... 9 System Impact .................................................................... 9 Handling Suggestion ............................................................10

198001026 Cell delineation do not synchronization about cell on E1 link .................................................................... 10

Alarm Property ...................................................................10 Probable Cause ...................................................................10 System Impact ...................................................................10 Handling Suggestion ............................................................11

198001284 Clock Phase Does not Match When Inputting 8k,16M Clock to Backboard. ........................................... 11


198001286 Loss of Clock When Input to Board.................. 12


198001792 SDH/SONET fault ......................................... 13


198002560 Board CPU Overloaded .................................. 15 Alarm Property ...................................................................15 Probable Cause ...................................................................15 System Impact ...................................................................16 Handling Suggestion ............................................................16

198002561 Excess Temperature of CPU on Board .............. 16 Alarm Property ...................................................................16 Probable Cause ...................................................................17 System Impact ...................................................................17 Handling Suggestion ............................................................17

198003073 Board FLASH faults ....................................... 17 Alarm Property ...................................................................17 Probable Cause ...................................................................18

System Impact ................................................................... 18 Handling Suggestion............................................................ 18

198005121 Inter-Shelf Media Plane Links Abnormal ........... 18

Alarm Property ................................................................... 18 Probable Cause................................................................... 18 System Impact ................................................................... 19 Handling Suggestion............................................................ 19

198005124 Capacity of Intra-Shelf Control Plane Trunk Communication Is Insufficient......................................... 19


198005125 Incorrect Connection of GE Optical Transceiver Module with Board Slots on Peer-end ............................... 21


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


198005379 Board Doesn’t Exist/ CPU is in Reset Status for a Long Time.................................................................... 25


198005381 Input Clock Abnormal.................................... 26 Alarm Property ................................................................... 26 Probable Cause................................................................... 26 System Impact ................................................................... 26 Handling Suggestion............................................................ 26

198005389 A (CPU) Subcard Is Online, but Is not Configured in Database.................................................................. 27

Alarm Property ................................................................... 27 Probable Cause................................................................... 27 System Impact ................................................................... 27

Handling Suggestion ............................................................27

198005390 (CPU) A (CPU) Subcard Is not Online, but Has Been Configured by Database. ........................................ 27


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


198005396 Exceptional Internal Media Plane Communication.................................................................................. 30


198005399 DSP Resource Unavailable ............................. 31


198005632 Usage Rate of Board Hard Disk Above Threshold33 Alarm Property ...................................................................33 Probable Cause ...................................................................33 System Impact ...................................................................33 Handling Suggestion ............................................................33

198005633 Hard Disk Broken ......................................... 34 Alarm Property ...................................................................34 Probable Cause ...................................................................34 System Impact ...................................................................34 Handling Suggestion ............................................................34

198005635 The Board Is Not Plugged Firmly..................... 35 Alarm Property ...................................................................35 Probable Cause ...................................................................35 System Impact ...................................................................35 Handling Suggestion ............................................................35

198005637 Error in Rear Board That Mismatches With Front Board .......................................................................... 36


198005639 High Error Rate of Optical Interface................. 37 Alarm Property ................................................................... 37 Probable Cause................................................................... 37 System Impact ................................................................... 37 Handling Suggestion............................................................ 38

198005640 FPGA Exception ............................................ 38 Alarm Property ................................................................... 38 Probable Cause................................................................... 38 System Impact ................................................................... 38 Handling Suggestion............................................................ 39

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


198005645 Subcard Abnormal ........................................ 40


198005646 Phase-lock Loop Unlock ................................. 41 Alarm Property ................................................................... 41 Probable Cause................................................................... 41 System Impact ................................................................... 41 Handling Suggestion............................................................ 41

198005647 High Error Rate at E1 Bottom Layer................. 42 Alarm Property ................................................................... 42 Probable Cause................................................................... 42 System Impact ................................................................... 42 Handling Suggestion............................................................ 43

198005655 DSP Reports Exceptions after Detection ........... 43 Alarm Property ................................................................... 43 Probable Cause................................................................... 43

System Impact ...................................................................44 Handling Suggestion ............................................................44

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


198005661 Media Interactive GE Port Link Down............... 45 Alarm Property ...................................................................45 Probable Cause ...................................................................45 System Impact ...................................................................45 Handling Suggestion ............................................................45

198005663 Board Device Is Abnormal.............................. 46 Alarm Property ...................................................................46 Probable Cause ...................................................................46 System Impact ...................................................................46 Handling Suggestion ............................................................46

198015874 Physical Channel for Data Transmission Blocked 46


198019456 All high-speed links between line card and package switching board are out of synchronism ............... 47


198019712 APS channel mismatched............................... 49


198019713 APS mode mismatched.................................. 50 Alarm Property ...................................................................50 Probable Cause ...................................................................50 System Impact ...................................................................51 Handling Suggestion ............................................................51

198019714 Board resets for APS configuration changes...... 52


198026116 CLKG PP2S Output Clock Lost......................... 53 Alarm Property ................................................................... 53 Probable Cause................................................................... 53 System Impact ................................................................... 53 Handling Suggestion............................................................ 53

198026127 Clock reference source lost (Level 3 alarm) ...... 54






198026133 Out put clock lost ......................................... 57 Alarm Property ................................................................... 57 Probable Cause................................................................... 57 System Impact ................................................................... 57 Handling Suggestion............................................................ 57

198066005 SCCP SSN is invalid ...................................... 57


198066006 Broadband link congestion ............................. 59

Alarm Property ................................................................... 59 Probable Cause................................................................... 59 System Impact ................................................................... 59

Handling Suggestion ............................................................60

198066010 MTP3 office inaccessible ................................ 60 Alarm Property ...................................................................60 Probable Cause ...................................................................61 System Impact ...................................................................61 Handling Suggestion ............................................................61

198066011 MTP3 link unavailable.................................... 61 Alarm Property ...................................................................61 Probable Cause ...................................................................61 System Impact ...................................................................62 Handling Suggestion ............................................................62

198066013 MTP3 link congestion .................................... 63


198066014 M3UA office inaccessible ................................ 64 Alarm Property ...................................................................64 Probable Cause ...................................................................64 System Impact ...................................................................64 Handling Suggestion ............................................................64

198066044 Fault on Board (GPS) .................................... 65 Alarm Property ...................................................................65 Probable Cause ...................................................................65 System Impact ...................................................................66 Handling Suggestion ............................................................67

198066047 Abnormal status in SDH/SONET...................... 67 Alarm Property ...................................................................67 Probable Cause ...................................................................68 System Impact ...................................................................70 Handling Suggestion ............................................................71

198066048 SDH/SONET:Excessive Error Code .................. 73 Alarm Property ...................................................................73 Probable Cause ...................................................................73 System Impact ...................................................................73 Handling Suggestion ............................................................73

198066049 ATM Communication Abnormally..................... 74

Alarm Property ...................................................................74

Probable Cause................................................................... 74 System Impact ................................................................... 74 Handling Suggestion............................................................ 74

198083003 Log server is offline alarm.............................. 75 Alarm Property ................................................................... 75 Probable Cause................................................................... 75 System Impact ................................................................... 75 Handling Suggestion............................................................ 76

198083027 RSVB Offline alarm ....................................... 76 Alarm Property ................................................................... 76 Probable Cause................................................................... 76 System Impact ................................................................... 77 Handling Suggestion............................................................ 77

Chapter 3........................................................................79

Communication Alarm ...................................................79

198005122 Communication Link between Active and Standby Boards Off ................................................................... 80


198005126 Incorrect FE Routing Connection ..................... 81 Alarm Property ................................................................... 81 Probable Cause................................................................... 81 System Impact ................................................................... 81 Handling Suggestion............................................................ 81

198005378 Board HW Error............................................ 82 Alarm Property ................................................................... 82 Probable Cause................................................................... 82 System Impact ................................................................... 82 Handling Suggestion............................................................ 83

198005382 Communication between power board and OMP board abnormal ............................................................ 83


198005397 RAWMACIP Channel Communication Exception . 84


198005401 Test Pack Check Abnormal ............................. 85 Alarm Property ...................................................................85 Probable Cause ...................................................................85 System Impact ...................................................................86 Handling Suggestion ............................................................86

198005650 MAC Address Conflict Exists in Boards of Same Shelf ........................................................................... 86


198005651 IPMAC Conflict When OSS Detects Control Plane87 Alarm Property ...................................................................87 Probable Cause ...................................................................87 System Impact ...................................................................88 Handling Suggestion ............................................................88

198015617 Faulty Frames Received by FE/GE/ATM/MP/POS/E1 Port ........................................... 88


198015873 Faulty Frames Received by Internal Switching Interface...................................................................... 89


198019213 LIF Alarm of Near-End Receiving Link .............. 90 Alarm Property ...................................................................90 Probable Cause ...................................................................91 System Impact ...................................................................91 Handling Suggestion ............................................................91

198019214 LODS Alarm of Near-End Receiving Link........... 91 Alarm Property ...................................................................91

Probable Cause................................................................... 92 System Impact ................................................................... 92 Handling Suggestion............................................................ 92

198019215 RDI Alarm of Near-End Receiving Link ............. 93 Alarm Property ................................................................... 93 Probable Cause................................................................... 93 System Impact ................................................................... 93 Handling Suggestion............................................................ 93

198022784 BFD Session Interrupted................................ 94 Alarm Property ................................................................... 94 Probable Cause................................................................... 94 System Impact ................................................................... 94 Handling Suggestion............................................................ 94

198066003 Control Plane Communication Abnormal Between Board and Its Home Module............................................ 96


198066004 Control Plane Communication Abnormal Between MP and OMP ................................................................. 97


198066019 Association link broken.................................. 98 Alarm Property ................................................................... 98 Probable Cause................................................................... 98 System Impact ................................................................... 98 Handling Suggestion............................................................ 98

198066026 Association path broken ................................ 99


198066029 PPP link broken .......................................... 100 Alarm Property ................................................................. 100 Probable Cause................................................................. 100 System Impact ................................................................. 101

Handling Suggestion .......................................................... 101

198066045 Trunk error................................................ 101 Alarm Property ................................................................. 101 Probable Cause ................................................................. 102 System Impact ................................................................. 102 Handling Suggestion .......................................................... 102

198066046 Trunk abnormal.......................................... 103 Alarm Property ................................................................. 103 Probable Cause ................................................................. 103 System Impact ................................................................. 103 Handling Suggestion .......................................................... 103

198066060 FE Link Error Alarm..................................... 104

Alarm Property ................................................................. 104 Probable Cause ................................................................. 104 System Impact ................................................................. 104 Handling Suggestion .......................................................... 104

198083021 CCP Link Fault Alarm................................... 105 Alarm Property ................................................................. 105 Probable Cause ................................................................. 105 System Impact ................................................................. 105 Handling Suggestion .......................................................... 105

Chapter 4......................................................................107

Processing Alarm.........................................................107

198005123 DB Config Doesn't Fit for Device ................... 108


198005387 Alarm Due to Inconsistent MP Type............... 109 Alarm Property ................................................................. 109 Probable Cause ................................................................. 109 System Impact ................................................................. 109 Handling Suggestion .......................................................... 109

198005388 Startup File Does Not Exist .......................... 110 Alarm Property ................................................................. 110 Probable Cause ................................................................. 110 System Impact ................................................................. 110

Handling Suggestion.......................................................... 110

198005398 Inconsistent Office ID Settings of DIP Switch.. 110 Alarm Property ................................................................. 110 Probable Cause................................................................. 111 System Impact ................................................................. 111 Handling Suggestion.......................................................... 111

198005649 Port Work Mode Doesn't Match Settings......... 111 Alarm Property ................................................................. 111 Probable Cause................................................................. 111 System Impact ................................................................. 112 Handling Suggestion.......................................................... 112

198015360 Microcode Is Abnormal ................................ 113

Alarm Property ................................................................. 113 Probable Cause................................................................. 113 System Impact ................................................................. 114 Handling Suggestion.......................................................... 114

198018944 PVC Fault .................................................. 114 Alarm Property ................................................................. 114 Probable Cause................................................................. 114 System Impact ................................................................. 114 Handling Suggestion.......................................................... 115

198019207 Near-End IMA Group Configuration Failure ..... 116 Alarm Property ................................................................. 116 Probable Cause................................................................. 116 System Impact ................................................................. 116 Handling Suggestion.......................................................... 116

198023040 Number of Alarms Over Threshold ................ 117 Alarm Property ................................................................. 117 Probable Cause................................................................. 117 System Impact ................................................................. 117 Handling Suggestion.......................................................... 117

198066027 SNTP failure............................................... 117 Alarm Property ................................................................. 117 Probable Cause................................................................. 118 System Impact ................................................................. 118 Handling Suggestion.......................................................... 118

198066031 Number of management module alarms exceeds the threshold.............................................................. 119

Alarm Property ................................................................. 119

Probable Cause ................................................................. 119 System Impact ................................................................. 119 Handling Suggestion .......................................................... 119

198066032 NTP time exceeds threshold ......................... 119 Alarm Property ................................................................. 119 Probable Cause ................................................................. 120 System Impact ................................................................. 120 Handling Suggestion .......................................................... 120

198066057 Database Config Is Different from File Named bootcfg ini.................................................................. 120


198083022 Cell Is out of Service................................... 121


198083023 Node B Is out of Service .............................. 124


198083024 receiver on ICM is abnormal......................... 125


Chapter 5......................................................................127

Environment Alarm......................................................127

198025856 Rack temperature is higher than high threshold................................................................................ 128


198025857 Rack temperature is lower than low threshold. 129


198025858 House temperature is higher than high threshold................................................................................ 130


198025859 House temperature is lower than low threshold131


198025860 Any one of rack voltage inputs above threshold................................................................................ 132


198025861 Voltage is lower than low threshold ............... 133


198025862 Humidity in equipment room above threshold . 134 Alarm Property ................................................................. 134 Probable Cause................................................................. 134 System Impact ................................................................. 134 Handling Suggestion.......................................................... 134

198025863 Humidity in equipment room below threshold . 135 Alarm Property ................................................................. 135 Probable Cause................................................................. 135 System Impact ................................................................. 135 Handling Suggestion.......................................................... 135

198025864 Rack fans faults.......................................... 136 Alarm Property ................................................................. 136 Probable Cause................................................................. 136

System Impact ................................................................. 136 Handling Suggestion .......................................................... 136

198025865 Rack door access control alarm .................... 136


198025866 Smoke alarm ............................................. 137 Alarm Property ................................................................. 137 Probable Cause ................................................................. 137 System Impact ................................................................. 138 Handling Suggestion .......................................................... 138

198025867 Infrared alarm ........................................... 138 Alarm Property ................................................................. 138 Probable Cause ................................................................. 138 System Impact ................................................................. 138 Handling Suggestion .......................................................... 139

198025868 Lightning alarm.......................................... 139


198066064 Power Switch Alarm.................................... 140


Chapter 6......................................................................141

QoS Alarm ....................................................................141

198023296 Inter-board Message Communication Flow Rate Over Alarm Threshold .................................................. 142


198066018 Association congested ................................. 143 Alarm Property ................................................................. 143 Probable Cause ................................................................. 143

System Impact ................................................................. 143 Handling Suggestion.......................................................... 143

Glossary........................................................................145

Figures..........................................................................155

Tables...........................................................................157

Confidential and Proprietary Information of ZTE CORPORATION i

About This Manual

Purpose

WCDMA 3G mobile telecommunication system, independently developed by ZTE, consists of ZXWN (ZTE WCDMA Core Network) and ZXWR (ZTE WCDMA Radio Network Subsystem). ZXWR consists of ZXWR RNC (Radio Network Controller) and ZXWR Node B.

This manual introduces the alarms that might occur during the installation, operation and maintenance of ZTE WCDMA RNC product. Alarm code and description displayed by NetNumen M31 centralized NMS, probable cause for the alarm, and the corresponding handling suggestion are covered in this manual.

What Is in This Manual

This manual contains the following chapters:

T AB L E 1 C H A P T E R S U M M AR Y

Chapter Summary

Chapter 1, Overview of Fault Management

Introduces the concept of fault management, as well as the definition, type, level classification of alarm and notification.

Chapter 2, Equipment Alarm

Introduces RNC equipment alarms with respect to alarm property, probable cause, system impact, and handling suggestion.

Chapter 3, Communication Alarm

Introduces RNC communication alarms with respect to alarm property, probable cause, system impact, and handling suggestion.

Chapter 4, Processing Alarm

Introduces RNC processing alarms with respect to alarm property, probable cause, system impact, and handling suggestion.

Chapter 5, Environment Alarm

Introduces RNC environment alarms with respect to alarm property, probable cause, system impact, and handling suggestion.

Chapter 6, QoS Alarm Introduces RNC QoS alarms with respect to alarm property, probable cause, system

ZXWR RNC Alarm Handling Reference

ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter Summary

impact, and handling suggestion.

Conventions

ZTE documents employ the following typographical conventions.

T AB L E 2 TY P O G R AP H I C AL C O N V E N T I O N S

Typeface Meaning

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields, radio button names, check boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

Constant width Text that you type, program code, files and directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Select one of the parameters that are delimited by it.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding further.

Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.

T AB L E 3 M O U S E OP E R AT I O N C O N V E N T I O N S

Typeface Meaning

Click Refers to clicking the primary mouse button (usually the left mouse button) once.

Double-click Refers to quickly clicking the primary mouse button (usually the left mouse button) twice.

Right-click Refers to clicking the secondary mouse button (usually the right mouse button) once.

Drag Refers to pressing and holding a mouse button and moving the mouse.

Typographical Conventions

Mouse Operation

Conventions

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii

How to Get in Touch

The following sections provide information on how to obtain support for the documentation and the software.

If you have problems, questions, comments, or suggestions regarding your product, contact us by e-mail at [email protected]. You can also call our customer support center at (86) 755 26771900.

ZTE welcomes your comments and suggestions on the quality and usefulness of this document. For further questions, comments, or suggestions on the documentation, you can contact us by e-mail at [email protected]; or you can fax your comments and suggestions to (86) 755 26772236. You can also browse our website at http://ensupport.zte.com.cn, which contains various interesting subjects like documentation, knowledge base, forum and service request.

Customer Support

Documentation Support


iv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r 1

Overview

This chapter introduces the concept of fault management, as well as the definition, type, level classification of alarm and notification.


2 Confidential and Proprietary Information of ZTE CORPORATION

Overview of Fault Management Fault management is responsible for collecting information of failures and events that occur during system operation or service processing.

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

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

Alarm

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

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

Notification

Notification refers to the non-repeated/instantaneous fault or event that occurs during system operation. Examples include board reset, signaling overload, etc.

Notification is mostly caused by sudden environment change or other accidental factors. No special handling is required for the notification, which can be automatically removed by the system. Only the notification that occurs persistently requires troubleshooting.

Chapter 1 Overview


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 code value.

Description

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

Severity

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

Critical alarm causes system breakdown and service interruption. It requires immediate troubleshooting.

Major alarm significantly affects system operation or weakens network service capability. It requires troubleshooting as soon as possible.

Minor alarm affects system operation and network service capability in a non-significant way. It requires timely troubleshooting so as to avoid severity escalation.

Warning poses a potential hazard to system operation and network service capability. It requires troubleshooting at an appropriate time so as to avoid severity escalation.

The degree of impact as described in the definition of alarm severity refers to the impact of a single index, such as reliability and security. Once the impact on any of the index reaches the specified threshold, the severity level of the alarm can be roughly determined. If an alarm has an impact on multiple indices, alarm severity should be escalated accordingly.



Note:

Alarm severity can be modified in NetNumenM31 NMS (network management system) if necessary.

Generally speaking, the default alarm severity is reasonably set. Users should think twice before making any modification.

In addition, the severity of a few alarms is undefined. It is up to users to define the severity of such alarms.

Alarm Type

Alarm is classified into six types according to alarm trigger condition 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-T Recommendation X.733).

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

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

OMS alarm: related with the NMS.

Probable Cause

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

System Impact

System impact refers to the impact that the alarm incurs on system or services.

Handling Suggestion

Troubleshooting measures and suggestions are provided.

Pay attention to the following tips when handling alarms.

Chapter 1 Overview


After recording the fault phenomenon, O&M personnel may handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed (alarm restored) at any handling step, terminate the handling process. If the fault is not removed, go ahead to the next handling step.

If the fault cannot be removed, contact the local ZTE office as soon as possible.

Notification Notification Property

Notification Code

Notification code is the identifier to differentiate notifications.

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

Description

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

Importance

There are two levels of notification importance: Important and Ordinary.

Notification Type

No notification type exists.

Probable Cause

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



System Impact

System impact refers to the impact that the notification incurs on system 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 may handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed 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, or the system normal operation cannot be restored, contact the local ZTE office as soon as possible.


C h a p t e r 2

Equipment Alarm

This chapter introduces RNC equipment alarms with respect to alarm property, probable cause, system impact, and handling suggestion. The information is intended for system maintenance personnel to have a clear understanding of each RNC equipment alarm item.



198000002 Loss of Optical Transceiver Module Signal Alarm Property

Alarm Code: 198000002

Description: Loss of Optical Transceiver Module Signal

Severity: Major

Alarm Type: Equipment alarm

Probable Cause

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

Receiving optical fiber is faulty or disconnected.

Optical connector is polluted.

Receiving optical module is faulty.

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

Transmitting optical fiber is faulty or disconnected.


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

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

Transmitting optical power at opposite end is too low.

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

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

5. Optical fiber and optical module is incompatible.

The fiber transmission rate and the optical module wavelength are incompatible.

System Impact

The optical interface fails to work normally. If the optical interface is configured with APS protection, service will be

Chapter 2 Equipment Alarm


switched to protection optical interface. Otherwise, all services on the optical interface will be down.

Handling Suggestion

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

2. Replace the optical module.

3. Replace fiber.

4. Replace board.

198000256 Ethernet Controller's Physical Link Off Alarm Property


Description: Ethernet Controller's Physical Link Off

Severity: Minor


Probable Cause

1. No network cable is connected with Network Port OMC1 on rear board.

2. Network cable is disconnected or cable connector is loose.

3. Network port on the board is faulty.

System Impact

Master/slave switching will occur if OMP (ROMB board) is configured in master/slave mode.

If master/slave switching is normal, system will not be affected.



If master/slave switching is abnormal, OMP board will fail to obtain version package from NMS, leading to board power-on failure, UE access failure, and interruption of ongoing services.

Handling Suggestion

1. Ensure that network cable is connected to Network Port OMC2.

2. Unplug and plug the network cable on Network Port OMC2 Of OMP board

3. Check if OMC2 network cable works normally. If no, replace the cable.

198001026 Cell delineation do not synchronization about cell on E1 link Alarm Property


Description: Cell delineation do not synchronization about cell on E1 link

Severity: Minor


Probable Cause

1. Cell Header HEC (Header Error Check) is damaged, leading to cell location failure in physical layer frame.

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

System Impact

Data reception on E1 link is abnormal. If merely one E1 link is available for the port, all services on the board will be down.



Otherwise, port bandwidth will be affected, leading to decreased access bandwidth. The number of successful upper-layer service access related to the port will decrease, but service interruption will not occur.

Handling Suggestion

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

Related alarms:

198066045 Trunk error

198066046 Trunk abnormal

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

3. Use meter measurement or loop test to judge whether the alarm is caused by local end or opposite end.

Meter Measurement

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

Loop Test

Perform self-loop at local trunk. If the alarm persists, fault might lie in local equipment. If the alarm disappears, inform the opposite end to troubleshoot.

4. Replace trunk cable.

5. Replace board.

198001284 Clock Phase Does not Match When Inputting 8k,16M Clock to Backboard. Alarm Property




Description: Clock Phase Does not Match When Inputting 8k,16M Clock to Backboard.

Severity: Minor


Probable Cause

1. Clock cable is broken or cable connection is incorrect.

2. Clock board is faulty.

System Impact

System synchronization fails and board operation is abnormal, leading to UE access failure and interruption of board services.

Handling Suggestion

1. Check the clock input cable at the shelf. Ensure that the cable is intact and properly inserted.

2. Switch clock board.

3. Switch UIM/GUIM board.

4. Replace board.

198001286 Loss of Clock When Input to Board Alarm Property


Description: Loss of Clock When Input to Board

Severity: Minor




Probable Cause

1. The board is not in place (not properly inserted) in the slot.

2. Clock cable is disconnected.

3. Clock cable is faulty.

4. Board is faulty.

System Impact

The board fails to synchronize with system clock and fails to work normally, leading to UE access failure and interruption of board services.

Handling Suggestion

1. Check if the clock (input) cable at the shelf is intact and properly connected.

2. Check if the following alarm occurs in the board. If yes, refer to the corresponding alarm handling suggestion.

Related alarm: 198005635 The board is not plugged firmly

3. Replace board.

198001792 SDH/SONET fault Alarm Property


Description: SDH/SONET fault

Severity: Major

Alarm Type: Equipment Alarm



Probable Cause

The alarm occurs when the receiving optical power is below optical receiver sensitivity. Generally speaking, normal receiving optical power range for optical modules is between -28 dBm and -8 dBm. Optical signals within this range can be detected.

Probable causes for the alarm include:

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

Receiving optical fiber is faulty or disconnected.


Receiving optical module is faulty.

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

Transmitting optical fiber is faulty or disconnected.


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

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

The related connector is in poor contact.

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

Optical power attenuation on the fiber transmission line at receiving end is too much.

Opposite-end transmitting optical power is too low.

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

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

6. Optical fiber and optical module is incompatible.

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

System Impact

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



Handling Suggestion


Meter Measurement

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

Loop Test

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

2. Replace optical module.

3. Replace optical fiber.

4. Replace board.

198002560 Board CPU Overloaded Alarm Property

Alarm code: 198002560

Description: Board CPU overloaded

Severity: Major


Probable Cause

1. Excessive data traffic at higher layer.

2. System is performing data synchronization or saving.

3. CPU alarm threshold setting is under configured.



System Impact

CPU occupancy indicates the current status of system operation. CPU overloaded, or over high occupancy, is usually caused by service or operation that consume much time.

It has the following impact on the system.

Services with low priority level have little or no access to the processing of CPU, which reduces processing speed of the services or even halts the processing.

System board could reset under excessively overloading conditions, causing interruption to the service it performs.

Handling Suggestion

1. Open the rack map on the Configuration Management window, select Board, right click and select Display Properties Tab. Check the CPU overload threshold setting on the Processor tab. Please reset CPU overload threshold if the CPU overload threshold value is too low. It will take 30 seconds for the new setting to take effect.

Recommended threshold value: 80% for low level load threshold, 90% for high level load threshold.

2. Check for the record of data synchronization, data saving or other file operations in the network manager log files. Those operations might increase the CPU utilization rate radically, and it might take 2 minutes.

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

198002561 Excess Temperature of CPU on Board Alarm Property


Description: Excess Temperature of CPU on Board



Severity: Major


Probable Cause

1. Environmental temperature around rack is too high

2. Board hardware fault

System Impact

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

Handling Suggestion

1. Check the thermometer in machine room for accurate temperature, and take effective measures when actual temperature is over high.

2. Check and clean the boards for dust accumulation which may cause heat trapped in the system.

3. Check and clean the air inlet and air outlet for dust accumulation or remove the impediments if any.

4. Check and make sure the fan(s) on the rack is in normal operation.

5. Replace the relevant boards.

198003073 Board FLASH faults Alarm Property


Description: Board FLASH faults

Severity: Major




Probable Cause

The flash on the board is damaged.

System Impact

1. For a single OMP board, the flash fault may cause board start up failure. For both master/slave boards with flash fault the entire system may have start up failure.

2. For other boards, the board may start up normally with out impact on its service.

Handling Suggestion

Replace the relevant boards.

198005121 Inter-Shelf Media Plane Links Abnormal Alarm Property


Description: Inter-shelf media plane links abnormal

Severity: Major


Probable Cause

1. Fiber optics connection error between UIM/GUIM/GLI and UIM/GUIM/GLI or fiber optics unplugged.

2. The UIM back ground configuration is different than that of the RNC NE physical connection.

3. Board failure.



System Impact

Reduces the inter-shelf service bandwidth. The inter-shelf service may be interrupted if no backup system is configured.

Handling Suggestion

1. Check the Unit Connection Relation in the configuration management interface to make sure it is consistent with actual connection settings. Change the connection cables according to actual configuration if they are inconsistent.

2. Check fiber optics for its proper cross connection and relevant alarm(s). Perform recommended solution to process the possible alarm(s).

Relevant Alarm: 198005125 The GE optical transceiver module is incorrectly connected on the left and right board slot on the peer-end

3. Replace the fiber optics cable or the optical transceiver module until the SD indicator is ON on the corresponding port.

4. Replace the local optical board.

5. Replace the optical board at the peer end.

198005124 Capacity of Intra-Shelf Control Plane Trunk Communication Is Insufficient Alarm Property


Description: Capacity of inter-shelf control plane TRUNK communication is insufficient.

Alarm level: Minor




Probable Cause

1. Connection failure.

2. Circuitry failure.

3. Board failure.

4. Rear board failure.

System Impact

It has usually no impact on the services.

Handling Suggestion

1. Check about whether TRUNK connection is used for Inter-shelf control planeIf not used, no processing is needed.

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

3. Check whether the connection is proper.

For the FE port trunk, the UIM board on BUSN shelf does not support TRUNK connection, so this alarm does not exist. For other shelf, FE7, FE8, FE9 and FE10 set up TRUNK ports. For the GUIM board, FE3, FE4, FE5, FE6 set up TRUNK ports.

For CHUB board, every 4 neighboring FE ports set up a TRUNK port, such as FE1~FE4, FE5~FE8 etc. All the 4 ports on the TRUNK port must be connected. The direct connect method is recommended.

The proper connection: 2 GE interfaces (CHUB board connection) are both connected and the connection is cross-connection. The #1 GE port on the left board on the local shelf corresponds to the #1 GE port on the left board on the opposite shelf, and the #2 GE port on the left board on the local shelf corresponds to the #2 GE port on the right board on the opposite shelf.

The #1 GE port on the right board on the local shelf corresponds to the #2 GE port on the left board on the opposite shelf, and the #2 GE port on the left board on the local shelf corresponds to the #2 GE port on the right board on the opposite shelf. This is shown in Figure 1 .



F I G U R E 1 CHUB C O N N E C T I O N

4. Replace the cable or optics module.

5. Replace the rear board.

6. Replace the board connected.

198005125 Incorrect Connection of GE Optical Transceiver Module with Board Slots on Peer-end Alarm Property


Description: 198005125 The GE optical transceiver module is incorrectly connected on the left and right board slot on the peer-end.

Alarm level: Minor


Probable Cause

The fiber optics connection error.



System Impact

Cause interruption to all services performed on this shelf.

Handling Suggestion

Check the fiber optics for its proper cross connection, the detailed steps are as below:

Each connection kit includes 4 cables, 2 boards ( one at each ends of the connection kit). Each board provides 2 ports which are to connect to the 2 boards on the peer side. The cross-connection method is as below: the #1 port on the left board on the local shelf corresponds to the #1 port on the left board on the opposite shelf, the #2 port on the left board on the local shelf corresponds to the #21 port on the right board on the opposite shelf. The #1 port on the right board on the local shelf corresponds to the #2 port on the left board on the opposite shelf, and the #2 port on the left board on the local shelf corresponds to the #2 port on the right board on the opposite shelf

An example of cross connection is shown below:

In case of a dual-shelf office, make connection between the fiber UIM and UIM, GUIM and UIM,GUIM and GUIM， as shown in Figure 2 .

F I G U R E 2 F I B E R C O N N E C T I O N D I AG R AM

In case of a multi-shelf office, UIM is connected to GLI by fiber optics cross connection. In which, UIM uses board backup, and GLI uses port backup. This is shown in Figure 3 .



F I G U R E 3 F I B E R OP T I C S C O N N E C T I O N 2

1

2

3

4

GLI#1

1

2

3

4

GLI#2

U IM# 1

U IM# 3

U IM# 5

U IM# 2

U IM# 4

U IM# 6

U IM# 7

U IM# 8

In the second case of a multi-shelf office, GUIM is connected to GLI by fiber optics cross connection. In which, GUIM uses board backup, and GLI uses port backup, as shown in Figure 4

F I G U R E 4 F I B E R OP T I C S C O N N E C T I O N 3

198005376 Internal Port of Board Is Down Alarm Property


Description: internal media plane port failure.



Severity: Major


Probable Cause

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

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

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

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

5. Service over the rated capability of the board.

System Impact

1. The internal media plane stream processing failure, service failure of all services provided by this board.

2. If the alarm source is port failure or connection failure, all services provided by this board will be interrupted.

3. If the alarm source is CPU overload, or service overloaded, services provided by this board may be delayed, or interrupted under serious conditions.

Handling Suggestion

1. Check the Alarm Management window for the CUP overloaded on the first level switching board, UIM board at the shelf, or local board. Perform recommended solution to process the alarm(s) if any.

Related Alarm: 198002560 Board CPU Overloaded

2. Check the Alarm Management window for the alarms of Inter-shelf media plane links abnormal. Perform the recommended solution to process the alarm(s) if any.

Related Alarm: 198005121 Inter-shelf Media Plane Link Error

3. Replace the board.

4. Change the slot of the board.

5. Replace the UIM in the same shelf.



198005379 Board Doesn’t Exist/ CPU is in Reset Status for a Long Time Alarm Property


Description: board offline / over long period of CPU reset status

Severity: Major


Probable Cause

1. Board not properly positioned.

2. Hardware failure.

System Impact

If the board is operational, and the alarm is board position failure, it does not affect the service operation.

The board is in blocked status, and no service by this board is available. If the board with alarm is resource board, then the resource is not available on this board.

Handling Suggestion

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

2. Plug/unplug the board.


4. Replace the slot




198005381 Input Clock Abnormal Alarm Property


Description: Clock input error

Severity: Critical


Probable Cause

1. The Clock board is not completely operational.

2. The clock board is not synchronized with reference clock.

3. The clock reference error.

System Impact

System services is interrupted as no proper clock information is provided to the system.

Handling Suggestion

1. Reconnect the board and clock reference firmly.

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

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




198005389 A (CPU) Subcard Is Online, but Is not Configured in Database. Alarm Property


Description: A (CPU) Subcard Is Online, but Is not Configured in Database.

Severity: Warning


Probable Cause

1. Configuration is incorrect.

2. Board is misplaced.

System Impact

Since the board where the unconfigured subcard is located resets repeatedly, power resource of the equipment is wasted. Service is not affected.

Handling Suggestion

Check if the subcard is needed.

If not, unplug the subcard.

If yes, configure board type into the one that supports the subcard.

198005390 (CPU) A (CPU) Subcard Is not Online, but



Has Been Configured by Database. Alarm Property


Description: The (CPU) Sub-card Configured in Database Not Online

Severity: Major


Probable Cause

1. Configuration errors:

2. The Board plugged is incorrect.

System Impact

The sub-card not operational. This board does not support this sub-card, and the impact of this error is subject to actual functions of the board.

If the sub-card is an interface board, then the transmission link on this board is not connectable, and the service will access through other sub-card; if the sub-card is a signaling processor board, then the cell/Node B on this board is not available for service; if the sub-card is a user’s panel, then the user plane processing capability will decline and the service will access through other sub-card.

Handling Suggestion

Check whether the sub-card is required. If this sub-card is not required, modify the board type as none sub-card board; if the sub-card is required, plug the sub-card firmly.



198005395 External Port of Board Is Down Alarm Property


Description：External Board Port Error

Severity: Major


Probable Cause

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.

System Impact

This port is not available for the service. If there is a back for this port, then data communicate through the back port, but the total communication rate will decline. Also the reliability and stability of the system declines too. If there is no back for this port, then all the office communication links through this port will not be available, and the services through this port are not available.

Handling Suggestion

1. Reconnect or replace the cable.


3. Contact the opposite engineers to check the opposite ports for possible failure.



198005396 Exceptional Internal Media Plane Communication Alarm Property


Description: Exceptional Internal Media Plane Communication

Severity: Major


Probable Cause

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

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

3. Backplane wiring failure of local slot to UIM.

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

5. Service over the rated capability of the board.

System Impact

In the case of the internal media plane stream processing failure of the board, and packet loss occurs, the service provided by this board might become unstable.

In the case of port failure of connector failure, the internal media plane is completely interrupted, and none of the services provided by this board is available.

If the alarm source is CPU overload, or service overloaded, services provided by this board may be delayed, or interrupted under serious conditions.



Handling Suggestion


Related Alarm: 198005376 internal media plane port failure.

2. Check the Alarm Management window for the CUP overloaded on the first level switching board, UIM board at the shelf, or local board. Perform recommended solution to process the alarm(s) if any.

Related Alarm: 198002560 Board CPU Overloaded


Related Alarm: 198005121 Inter-shelf Media Plane Link Error


5. Change the slot of the board.


198005399 DSP Resource Unavailable Alarm Property


Description: DSP Resource Unavailable

Severity: Major


Probable Cause

This alarm indicates the DSP resource is not available. It is monitored by higher level layer, and is reported once DSP is blocked, the report conditions include:

1. DSP version loaded failure, system is unable to operate normally.

2. HPI port error on DSP



3. DSP media plane communication failure.

4. DSP reset.

System Impact

All the services performed on this DSP is interrupted, and those services will be re-created on other normal DSP’s. The long period absence of this DSP might cause decline to the performance of the system.

Handling Suggestion

1. Check the operation maintenance log files in network manager for the operations of DSP version replacing. If there is operation of DSP version replacing which would cause DSP reset, then the alarm does not require procession, the DSP will resume operational after the resetting.

2. There is a DSP index in the detailed information of the alarm. Open the rack map on the Configuration Management window, select Board, right click and select “Subunit Configuration”. Select the DSP with alarm, and click Status at Subunit Configuration>Status Attribute> Query Status. Then check if the Management Status of DSP is Blocked. If it is Blocked, it means the alarm is a normal consequence of manually blocking the DSP.

Open the rack map on the Configuration Management window, select Board, right click and select “Subunit”. Run Unblock DSP to resume DSP operation.

3. Check the Alarm Management window for the corresponding alarms. Perform the recommended solution to process the alarm, if any.

Related Alarms:

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

198005655 DSP Reports Exceptions After Detection

198005700 DSP resets for error.

4. Reset the board.




198005632 Usage Rate of Board Hard Disk Above Threshold Alarm Property


Description: Usage rate of board hard disk above threshold

Severity: Major


Probable Cause

1. Usage rate threshold configuration is improper.

2. The usage of hard disk is over high.

System Impact

When hard disk usage is over threshold, there may be error for the write-in operation of new data, or data loss. It has no impact to the service.

Handling Suggestion

1. Open the Configuration Management window>MPX86 or MPX86/2 alarm parameter> Hard Disk Full, check the threshold value in the configuration of Hard Disk Usage Alarm level. Increase the threshold value if the setting is not larger enough.

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



198005633 Hard Disk Broken Alarm Property


Description: The hard disk has failure.

Severity: Major


Probable Cause

There is failure in ribbon cable connection or the hard disk. This is usually a hardware failure.

System Impact

This alarm is dedicated to OMP only. Its system impact is:

1. Hard disk failure in ROMP start up may cause ROMP board start up failure and service accessing failure.

2. Hard disk failure in the log server may cause data loss of the performance data stored on the ROMP hard disk in the abnormal status.

3. When a peripheral board is starting up and requesting version from ROMP, Hard disk failure may cause start up failure and power off of the peripheral board.

Handling Suggestion

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



198005635 The Board Is Not Plugged Firmly Alarm Property


Description: The board is not plugged firmly.

Severity: Major


Probable Cause

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

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

System Impact

When the ENUM switch on the board is ON, or is not firmly connected, it has no impact on the system.

Handling Suggestion

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

2. Switch off and switch on ENUM.



198005637 Error in Rear Board That Mismatches With Front Board Alarm Property


Error in Rear Board That Mismatches With Front Board

Alarm level: Minor


Probable Cause

1. Incorrect rear board is used.

2. Rear board failure.

System Impact

1. When the rear board is used for the access of other NE, it would cause link interruption on the bottom layer, and service interruption of the corresponding link.

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

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

Handling Suggestion

1. Check the front board type for the correct rear board type, and use the correct rear board.

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



198005639 High Error Rate of Optical Interface Alarm Property


Description: High Error Rate of Optical Interface

Severity: Major


Probable Cause

The fiber is not completed connected to the port, or is damaged, or is not compatible with the optical transceiver module in T-network switch. There is no light signal input into the optics module.

This alarm is dedicated to the TDM optical port only. The possible causes of this alarm include:

1. TDM receiver fiber optics failure, fiber optics module failure.

This type of failures include: damaged fiber on the receiver, unconnected fiber, contaminated fiber or damaged optics module on the receiver.

2. Fiber optics failure at the transmitting module on the corresponding TDM.

This type of failures include: damaged fiber on the transmitter, unconnected fiber, and contaminated fiber.

3. Compatibility between fiber optics and optics module.

The fiber transmission rate of TDM signal is incompatible with the wave length of the optics module.

4. Loss of signal (LOS) alarm operation is performed on the corresponding SDH device.

This includes the manual diagnosis test alarm operation.

System Impact

There might be error in the data transmitted by the optical port which affects the quality of all the services performed on this optical port.



Handling Suggestion

1. Perform loopback test to determine source of this alarm is on the local devices or the corresponding devices. Perform self-loop test on local device. If the failure persists, the failure source is on local device; if the failure disappears after self-loop test, then the source of failure is on the corresponding device. Contact the corresponding device for solution.

2. Replace optics module.

3. Replace the fiber optics.


198005640 FPGA Exception Alarm Property


Description: FPGA Exception

Severity: Major


Probable Cause

EPGA runs abnormally, for example, FPGA is lost, or the board clock is lost.

System Impact

EPGA verification fails.

The read and write function of EPGA cannot be ensured.

The board cannot provide complete functions and work normally.

The service carried by the board is interrupted.



Handling Suggestion

1. Restart the board. In this case, the board downloads FPGA again.


198005644 The Channel in a Subcard Is Down Alarm Property


Description: The Channel in a Subcard Is Down

Severity: Major


Probable Cause

1. The sub-card is not inserted in position.

2. The sub-card has hardware faults.

System Impact

The sub-card channel is not initialized or the initialization fails. As a result, the channel corresponding to the alarm chip cannot be used normally. This affects the service carried by the board of the sub-card. After the channel is available and the alarm is eliminated, the service is recovered.

Handling Suggestion

1. Unplug and plug the sub-card again. Wait for the board to be powered on.

2. Replace the sub-card.



198005645 Subcard Abnormal Alarm Property


Description: Subcard Abnormal

Severity: Minor


Probable Cause

1. The GCS sub-card of UIMC/GUIM/CHUB is not inserted in position.

2. The sub-card is faulty.

System Impact

UIMC/GUIM/CHUB GCS sub-card functions abnormally. Packets may be lost, and even worse, link disconnection may occur on the control planes of some boards. For active/standby configuration, there are two cases:

1. If the active board is abnormal while the standby board is normal, the system performs active/standby switchover. Thus, the standby board takes over the services of the faulty active board. In this case, the service is not affected.

2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this case, the service is interrupted because the faulty board cannot restore to the normal status.

Handling Suggestion

1. Check the sub-card connection on the board. If the sub-card is loosely inserted, tightly insert it and wait for the board to be powered on.

2. Replace the sub-card.



198005646 Phase-lock Loop Unlock Alarm Property


Description: Phase-lock Loop Unlock

Severity: Critical


Probable Cause

1. The clock extraction reference is changed, including the case that the clock output is closed by the interface board when optical port is faulty. This leads to the change of clock board input. Or, configuration is modified at NMS and a new optical port is used to extract the clock.

2. The change in input of clock board results in the change in output.

3. UIMC/GUIM input is disconnected, or UIMC/GUIM clock phase loop is abnormal.

4. The board lock phase loop has hardware faults.

System Impact

The service clock and system clock are inconsistent on the board with unlocked phase-lock loop. As a result, the service carried by the board is interrupted.

Handling Suggestion

1. On NMS fault management interface, check if the related clock alarm occur. If yes, handle the alarm by referring to the corresponding suggestions.

The related alarm is as follows:

198005381 Input Clock Abnormal



2. On NMS fault management interface, check if related alarms occur on the optical port for clock extraction. If yes, handle the alarm by referring to the corresponding suggestions.

The related alarms are as follows:

198001792 SDH/SONET fault

198066047 Abnormal status in SDH/SONET

198005639 High Error Rate of Optical Interface

198000002 Loss of Optical Transceiver Module Signal

3. Check the operation and maintenance logs. If the operation of changing the clock extraction reference for the loop is recorded, report the alarm as a normal phenomenon. In this case, no handling operation is required.

4. Switch to the standby clock board.

5. Switch to the standby UIM/GUIM board.


198005647 High Error Rate at E1 Bottom Layer Alarm Property


Description: High Error Rate at E1 Bottom Layer

Severity: Major


Probable Cause

1. The E1/T1 link is faulty.

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

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

System Impact

The trunk fails to receive trunk signals. If the belonged port has only this link, all services on the port are interrupted. Otherwise,



only the port bandwidth is affected. The quantity of upper layer access services associated with the port is decreased. The accessed bandwidth is reduced. The service, however, is not interrupted.

Handling Suggestion

1. Conduct a meter measurement or loopback test to find out whether the alarm is rooted in the local end or peer end.

Meter measurement: Connect a trunk test meter to check if the signal received by the local end trunk is normal. If yes, the fault is rooted in the local end. If the test shows the problem persists, the fault is rooted in the peer end. In this case, inform the peer end to troubleshoot.

Loopback test: Perform self-loop at the trunk where alarm occurs at local end. If the problem persists, it indicates that the fault is rooted in the local end. If the alarm is eliminated, it indicates that the alarm is rooted in the peer end. In this case, inform the peer end to troubleshoot.

2. Replace the trunk cable.


198005655 DSP Reports Exceptions after Detection Alarm Property


Description: Auto-detection and Report

Severity: Major


Probable Cause

1. The HPI port fails

2. Hardware failure.



System Impact

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

Handling Suggestion

1. Reset the board.

2. Replace DSP sub-card.


198005656 Loss of Clock When Input to Sub-card Alarm Property


Description: Loss of Clock When Input to Sub-card

Severity: Major


Probable Cause

1. The sub-card is not inserted in position.

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

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

System Impact

The unavailable sub-card clock affects the normal operation of the board. This may cause clock jittering, and the service that implements media stream exchange through this board becomes unstable. In the most serious case, the system clock is lost and the service carried by the board is interrupted.



Handling Suggestion

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


198005661 Media Interactive GE Port Link Down Alarm Property


Description: Media Interactive GE Port Link Down

Severity: Warning


Probable Cause

The network port or board is faulty.

System Impact

The APS optical port data on the standby board cannot reach the active board. When the active optical port is normal, the service is not affected. When the active optical port is faulty, APS fails to protect optical port and thus all services carried by the optical port are interrupted.

Handling Suggestion


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

3. Replace the slot. Use the slot that supports GE channel between boards.



198005663 Board Device Is Abnormal Alarm Property


Description: Board Device Is Abnormal

Severity: Major


Probable Cause

The board device or sub-card is working abnormally.

System Impact

This alarm only occurs on IMAB board. When this fault occurs, IMAB board cannot work normally and the trunk link that the board bears is broken. As a result, users cannot gain access and the ongoing service is interrupted.

Handling Suggestion

Replace the board.

198015874 Physical Channel for Data Transmission Blocked Alarm Property


Description: Physical Channel for Data Transmission Blocked



Severity: Major


Probable Cause

1. The traffic flow to the board is excessive.

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

3. The board has hardware faults.

System Impact

The services carried by the board are unstable. In most serious case, all services carried by the board are interrupted.

Handling Suggestion

1. On NMS fault management interface, check if the PSN in the same shelf has generated related alarms. If yes, follow the suggestions on handling the related alarms.


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

2. Unplug and plug the board.


198019456 All high-speed links between line card and package switching board are out of synchronism Alarm Property




Description: All high-speed links between line card and package switching board are out of synchronism

Severity: Critical


Probable Cause

1. The PSN board type configured does not accord with the PSN board type actually in use.

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

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

System Impact

1. All services on the equipment are down if the alarm is caused by Cause 1 or Cause 2.

2. All services on the line card are affected if the alarm is caused by Cause 3. If the service is not configured in master/slave or load sharing mode, all services on the line card will be down. If the service is configured in master/slave or load sharing mode, all services on the line card will soon be restored after being down temporarily.

Handling Suggestion

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

If inconsistent (for example, the configured board type is PSN4V and the board type actually in use is PSN8V), modify board type configuration or replace the board actually in use to keep consistency between board configuration and the board in use.

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

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

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



If merely the line card where this alarm occurs reboots repeatedly, replace the board where the alarm is generated.

198019712 APS channel mismatched Alarm Property


Description: APS channel mismatched

Severity: Major


Probable Cause

1. Fiber connection is wrong.

2. Configuration of APS backup mode at local end and opposite end is inconsistent.

3. Configuration of APS protection mode at local end and opposite end is inconsistent.

4. Opposite equipment is faulty.

System Impact

APS automatic protection switching function is paralyzed. When the work optical port is abnormal, protection optical port will not work, leading to service interruption on this optical interface.

Handling Suggestion

1. Check fiber connection.

Check fiber connection at both ends. Ensure that the work optical ports at both ends are interconnected, and the protection optical ports at both ends are interconnected.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and



shortcut menu appears. Click Optical port APS protection in the shortcut menu to view the “Work optical port” and “Protection optical port” configured at local end.

2. Check APS backup mode configuration at both ends.

Check APS backup mode (1＋1 or 1:1) at local end to ensure configuration consistency at both ends.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and shortcut menu appears. Click Optical port APS protection in the shortcut menu to view the “Protection Type” (1+1 or 1:1).

3. Check APS protection direction at both ends.

Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure configuration consistency at both ends.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and shortcut menu appears. Click Optical port APS protection in the shortcut menu to view the “Protection Direct” (unidirectional or bidirectional).

4. Check whether APS is supported by the opposite equipment. Check whether APS configuration is correct and has taken effect.

198019713 APS mode mismatched Alarm Property


Description: APS mode mismatched

Severity: Major


Probable Cause

1. Fiber connection is wrong.

2. Configuration of APS backup mode at local end and opposite end is inconsistent.



3. Configuration of APS protection mode at local end and opposite end is inconsistent.

System Impact

When fiber connection is correct and work optical port works, service is not affected.

When work optical port is faulty, APS automatic protection switching might fail, and service on this optical interface might be interrupted due to lack of protection.

Handling Suggestion

1. Check fiber connection.

Check fiber connection at both ends. Ensure that the work optical ports at both ends are interconnected, and the protection optical ports at both ends are interconnected.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and shortcut menu appears. Click Optical port APS protection in the shortcut menu to view the “Work optical port” and “Protection optical port” configured at local end.

2. Check APS backup mode configuration at both ends.

Check APS backup mode (1＋1 or 1:1) at local end to ensure configuration consistency at both ends.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and shortcut menu appears. Click Optical port APS protection in the shortcut menu to view the “Protection Type” (1+1 or 1:1).

3. Check APS protection direction at both ends.

Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure configuration consistency at both ends.

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and shortcut menu appears. Click Optical port APS protection in the shortcut menu to view the “Protection Direct” (unidirectional or bidirectional).



198019714 Board resets for APS configuration changes Alarm Property


Description: Board resets for APS configuration changes

Severity: Major


Probable Cause

Board backup mode is configured as 1:1 or 1+1. APS protection mode is unconfigured.

System Impact

Board operation status is abnormal. All board services fail to be established.

Handling Suggestion

1. If board backup mode is configured as 1:1 or 1+1 and SDH optical interface is needed, at least one set of APS protection needs to be configured.

To configure APS protection:

On NMS configuration management interface, locate the relevant board in the rack. Right-Click the board and shortcut menu appears. Click Optical port APS protection in the shortcut menu.

2. If board master/slave mode is not needed, modify board backup mode into.

To configure board backup mode:

Delete the relevant board on NMS configuration management interface. Then recreate the board. Select board backup mode as “None” during board creation.



3. f board backup mode is configured as 1:1 and no SDH optical interface is required, modify the board backup mode into 1+1.

To configure board backup mode:

Delete the relevant board on NMS configuration management interface. Then recreate the board. Select board backup mode as “1+1” during board creation.

198026116 CLKG PP2S Output Clock Lost Alarm Property


Description: CLKG PP2S Output Clock Lost

Severity: Major


Probable Cause

Hardware is faulty.

System Impact

If this alarm occurs to master clock board, the system will fail to get clock, leading to processing failure of clock-related boards and interruption of board services. Relevant boards include IMA protocol processing board and the interface board capable of HW processing.

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

Handling Suggestion

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

2. Replace the board where the alarm is declared.



198026127 Clock reference source lost (Level 3 alarm) Alarm Property


Description: Clock reference source lost (Level 3 alarm)

Severity: Minor


Probable Cause

Input clock reference is in unavailable status for no more than 10 minutes.

Probable causes include:

1. Clock reference input is abnormal.

2. The configured clock reference does not exist.

System Impact

When all configured clock reference sources are lost, the clock board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. No impact on service.

Handling Suggestion

1. Re-connect the input clock reference.

2. For the clock reference not in use, delete the corresponding “Circuitry Clock Reference” configuration on NMS configuration management interface (board property).






Severity: Major


Probable Cause

Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours.




System Impact

When all configured clock reference sources are lost, the clock board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. The clock loss leads to synchronization failure between system clock and clock reference source. Service interruption might occur.

The system will not be affected if the following two events happen together.

Input clock reference source is lost.

The phase-locked loop locks other clock reference source.

Handling Suggestion








Severity: Critical


Probable Cause

Input clock reference is in unavailable status for more than 24 hours.




System Impact

When all configured clock reference sources are lost, the clock board comes to free running or hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board. The clock loss leads to synchronization failure between system clock and clock reference source. Service interruption will occur.

The system will not be affected if the following two events happen together.

Input clock reference source is lost.

The phase-locked loop locks other clock reference source.

Handling Suggestion





198026133 Out put clock lost Alarm Property


Description: Out put clock lost

Severity: Major


Probable Cause

Hardware is faulty.

System Impact

If this alarm occurs to master board, system clock synchronization will fail and service interruption will occur.

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

Handling Suggestion

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

2. Replace board.

198066005 SCCP SSN is invalid Alarm Property


Description: SCCP SSN is invalid

Severity: Minor




Probable Cause

Note:

Subsystem configuration involves local equipment and opposite equipment. A refers to local equipment. B refers to opposite equipment. To make subsystem configuration sensible, the following requirements must be met:

At A end, local subsystem (for A) and remote subsystem (for B) must be configured.

At B end, local subsystem (for B) and remote subsystem (for A) must be configured.

The mapping relationship between configuration at A end and that at B end is as follows:

Local subsystem (for A) at A end corresponds to the remote subsystem (for A) at B end. Remote subsystem (for B) at A end corresponds to the local subsystem (for B) at B end.

1. From the perspective of A, remote signaling point subsystem is out of service.

2. From the perspective of A, remote signaling point is inaccessible.

3. Remote subsystem (for B) is configured at A end, but the corresponding local subsystem (for B) is not configured at B end.

4. Local subsystem (for B) is blocked at B end.

5. From the perspective of A, SCCP user is unconfigured in remote MTP3 or M3UA user configuration.

System Impact

Signaling data cannot be sent to and received from the relevant subsystem. Access of new service under the corresponding office fails, and release of the ongoing service occurs.

Handling Suggestion

1. Check whether there exists office (the office that corresponds to the subsystem) inaccessible alarm. If yes, refer to the corresponding alarm handling suggestion.

Related alarms:



198066010 MTP3 office inaccessible

198066014 M3UA office inaccessible

2. Unblock the subsystem in dynamic data management.

3. On NMS configuration management interface, check the configuration of signaling point code (for A) at A end. See if SCCP user is included in user type configuration. If no, add the configuration. Meanwhile, check the corresponding configuration at B end.

4. Check whether the status of signaling point subsystem (for B) is available at B end. If no, the signaling point subsystem at B end must be out of service. Locate the cause for the abnormal status.

5. Check whether the signaling point subsystem (for B) is configured at B end. If no, add the configuration at B end.

198066006 Broadband link congestion Alarm Property


Description: Broadband link congestion

Severity: Minor


Probable Cause

1. The configured signaling PVS bandwidth is insufficient.

2. Bottom-layer physical transmission quality is poor.

System Impact

Link congestion leads to transmission delay. If congestion is not serious, service will not be affected. Otherwise, packet loss or call loss might occur, and access success rate of PS service might fall.



Handling Suggestion

1. Check the counter of “Peak Traffic of Signalling Link” in MTP3B signaling link performance statistics. If the load (nearly) reached 6000 during alarm occurrence, upper layer traffic must be heavy. Increase PVC bandwidth or add links to share load.

2. Check NMS alarms/notifications to see whether there exists physical transmission alarm(s) /notification(s) that occurred simultaneously with this alarm. If yes, refer to the corresponding alarm handling suggestion.

Alarms/Notifications related to physical transmission are listed below, with respect to access mode.

Fiber Access Mode



198066048 SDH/SONET:Excessive Error Code


E1 Access Mode

198005647 High Error Rate at E1 Bottom Layer



198000576 Trunk Slide

3. Check the performance statistics of SSCOP link. Check if there was message retransmission of “Number of PDU Retransmitted” during alarm occurrence. If yes, packet loss must have occurred during transmission. Since packet loss might occur at opposite end, ask opposite end to cooperate in troubleshooting.

198066010 MTP3 office inaccessible Alarm Property


Description: MTP3 office inaccessible

Severity: Major




Probable Cause

1. No service link exists in the office route.

2. TFP is received.

System Impact

Reception and sending of messages from/to the relevant office fail. Access of new service under this office fails, and abnormal release of the ongoing service occurs.

Handling Suggestion

1. Check if there exists unavailable link alarm. If yes, refer to the corresponding alarm handling suggestion.

Related alarm: 198066011 MTP3 link unavailable

2. Check whether office and link configuration at opposite end is correct.

198066011 MTP3 link unavailable Alarm Property


Description: MTP3 link unavailable

Severity: Minor


Probable Cause

1. Bottom layer physical link is down or link quality is poor.

2. Link test fails to be passed.



3. Link deactivation is performed in dynamic data management.

4. The link is released at opposite end.

5. SMP SPB/SPB2/APBE/APBE2 board resets

System Impact

If several MTP3 links are available under the office, service will not be affected. In the case of heavy traffic, congestion of available link(s) might occur, leading to packet/call loss or increasing PS call access failures.

If merely one link is available to the destination signaling point, the office might become inaccessible. Reception and sending of messages from/to the relevant office fail. Access of new service under this office fails, and abnormal release of the ongoing service occurs.

Handling Suggestion

1. On NMS configuration management interface (signaling link configuration), check PVC configuration. Configuration of CVPI and CVCI at both ends should be consistent.

2. Check link status in dynamic data management. If link interruption occurs now and then, link unavailability might be caused by MTP3 link test failure.

i. On NMS configuration management interface, check the signaling point code configuration at both ends. Ensure that the configuration at both ends is consistent.

ii. On NMS configuration management interface, check the signaling link configuration at both ends. Ensure that the SLC (signaling Link Code) configuration at both ends is consistent.

3. Reactivate the link in dynamic data management.

4. Check board status. If board status is abnormal, reset/replace the board.

5. The relevant link is released at opposite end. Ask the opposite end to perform handling as link is unavailable.



198066013 MTP3 link congestion Alarm Property


Description: MTP3 Link Congestion

Severity: Major


Probable Cause

1. There are too many upper layer service messages.

2. Bottom layer link quality is poor, leading to frequent message retransmission.

System Impact

Link congestion leads to transmission delay. If congestion is not serious, service is not affected. Otherwise, packet loss or call loss might occur, and access success rate of PS service might fall.

Handling Suggestion

1. Add links to the office that is in service for the congested link.

2. Take the following measures to improve transmission quality of physical links.

Replace bottom layer links.

Ensure that connector contact and cable connection are normal.



198066014 M3UA office inaccessible Alarm Property


Description: M3UA office inaccessible

Severity: Major


Probable Cause

1. Association link is broken or application server (AS) is not in serving status.

2. DUNS (destination signaling point unavailable) is reported by remote office of the association.

System Impact

Reception and sending of messages from/to the relevant office fail. Access of new service under this office fails, and abnormal release of the ongoing service occurs.

Handling Suggestion

1. Check if there exists broken association link alarm. If yes, refer to the corresponding alarm handling suggestion.

Related alarm: 198066019 Association link broken

2. Check AS configuration on NMS configuration management interface. Main checking items include the existence of routing context, routing context ID, APP server AS ID, and traffic mode.

Correct configuration is described below.

The routing context ID and traffic mode at both ends must be the same.

APP server AS ID configuration must meet the following requirements. If ASP is configured for local end, SGP should be configured for Opposite end. If IPSP client is



configured for local end, IPSP server should be configured for opposite end.

3. Reactivate the ASP in dynamic data management.

4. Check whether the configuration of the relevant office is correct at opposite end.

198066044 Fault on Board (GPS) Alarm Property


Description: Fault on Board (GPS)

Severity: Critical


Probable Cause

According to alarm details, alarm status falls into three types:

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

Type B Fault on Board (GPS) Phase-lock Equipment

Phase-lock Equipment of This Board (GPS) Is in Power-on Status

The causes for the three alarm types are described below.


Probable alarm causes include 16chip loss/out of lock, 12.8M loss/out of lock, PP2S output loss, 8K output loss, and 10M output loss.


Probable alarm causes include antenna feeder short circuit or open circuit, poor quality of received satellite signals or difficulty in receiving satellite signals, and large phase difference of 10M OCXO assistant phase control.


The alarm cause is that the GPS module of ICM board is in power-on status, and power-on has not been completed.



System Impact

The system impact that corresponds to the three alarm status are described below.


The nature of persistent Class A fault is usually determined as hardware fault, which affects system clock. It might lead to the system clock loss and system synchronization failure.


Class B fault has no impact on system clock and services in 48 hours. After 48 hours, the fault might lead to system clock offset and system synchronization failure. When GPS signal is poor, the alarm will be repeatedly declared/restored. As long as the alarm persists for no more than 48 hours, system clock and service will not be affected.


If this alarm persists, it is usually determined as hardware fault, which affects system clock. It might lead to the system clock loss and system synchronization failure.

When system clock loss/offset occurs, its subsequent impact on service is described below.

For TDM transmission, all links based on the TDM transmission medium (including the transmission link currently in service for UE and cell transmission link) are affected. Packet loss might occur on these links, leading to degradation of service quality. In the case of serious packet loss, service interruption and handover failure will occur. Even worse, the cell might be out of service.

For non-TDM transmission (for example, IP transmission), Iub interface service is affected, while Iur interface and Iu interface services are not affected. The clock that Node B derives from RNC via IEEE1588 is inaccurate.

When RNC clock frequency offset is no more than 0.05 ppm, Node B synchronization will not fail, but success rate of inter-RNC inter-Node B soft handover might fall.

When RNC clock frequency offset exceeds 0.5 ppm, Node B will fail to lock the clock. In this case, Node B will oscillate freely and success rate of inter-Node B soft handover might fall.



Handling Suggestion

On NMS fault management interface, view alarm Details where Error type information is given. Locate the corresponding alarm handling suggestion according to the error type.

The alarm handling suggestions that correspond to the error types are described below.


i. On NMS test management interface, perform diagnostic test on ICM board. Check the working status of the GPS module. If Class A fault persists in the GPS module, replace the board.

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


Check the antenna feeder input circuit of ICM board to ensure that the board can best receive GPS signal source. The checking items include:

i. The position of the receiving antenna.

The antenna should be installed in an open area, far away from high buildings and clear from shades. The effective visibility angle of the antenna should be greater than 150 degrees.

ii. The connection of the power splitter and front panel.

The power splitter and the front panel connector should be in good contact and properly connected.


If the alarm persists, hardware fault might exist. Replace the board.

198066047 Abnormal status in SDH/SONET Alarm Property


Description: Abnormal status in SDH/SONET

Severity: Minor




Probable Cause

On NMS fault management interface, view alarm Details where Error type information is given. Each error type corresponds to an alarm status Altogether there are twenty-two types of alarm status. Probable causes which correspond to different alarm status are listed below.

1. Loss of frame

This alarm will occur when the A1A2 frame aligning signal in SDH regenerator section overhead fails to be received properly for a consecutive 3 ms.

2. Regenerator section trace identifier mismatch

This alarm will occur when J0 byte in “access point identifier” at receiving end and transmitting end is inconsistent with the expected (the previous agreement between two ends). The alarm might be caused by configuration inconsistency of J0 byte mode/value at both ends.

3. Multiplex section alarm indication signal.

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

4. Multiplex section remote defect indication.

This alarm is a remote alarm indication. It is an indication of an alarm currently reported at opposite equipment. The alarm which originates from remote multiplex section is in return indicated by the local SDH equipment.

5. Multiplex section remote error indication.

When multiplex section B2 bit error occurs in opposite SDH equipment, the number of bit errors can be detected at local end. The alarm will be reported if the number of bit errors reaches a certain limit.

6. Signal failure.

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

7. Signal deterioration.

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

8. Administration unit loss of pointer.

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



9. Administration unit alarm indication signal.

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

10. High order path trace identifier mismatch.

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

11. High order path unequipped.

This alarm will occur when the “VC-4 path signal identifier” received by local SDH equipment is coded in all zero mode. The following two reasons might account for the alarm.

The path in local SDH equipment has not been equipped by opposite end.

The path configured at opposite end is 0.

12. High order path signal label mismatch.

This alarm will occur when the “VC-4 path signal identifier” received by local SDH equipment is different from the expected one. The alarm might be caused by configuration inconsistency of C2 byte at both ends.

13. High order path remote defect indication.

This alarm is a remote alarm indication. It is an indication of an alarm currently reported at opposite equipment. The alarm which originates from remote high order path is in return indicated by the local SDH equipment.

14. High order path remote error indication.

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

15. Tributary unit loss of multiframe.

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

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

Multiframe alignment fails for consecutive 8 frames

16. Tributary unit loss of pointer.



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

17. Tributary unit alarm indication signal.

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

18. Tributary unit remote defect indication.

This alarm is a remote alarm indication. It is an indication of an alarm currently reported at opposite equipment. The alarm which originates from the remote tributary is in return indicated by the local SDH equipment. The remote defects include tributary unit multiframe loss, tributary unit pointer loss, tributary unit trace identifier mismatch, and tributary unit unequipped, etc.

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

This alarm is the same with Alarm 18, except in that it applies to VC-11 structure, where T1 is 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 be caused by configuration inconsistency of J2 byte mode/value at both ends.

21. Tributary unit unequipped.

This alarm will occur when the “VC-12 path signal identifier” received by local SDH equipment is coded in all zero mode. The following two reasons might account for the alarm.

The relevant tributary has not been equipped by opposite end.

The relevant tributary configured at opposite end is 0.

22. Tributary unit signal label identifier mismatch.

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

System Impact

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



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

Handling Suggestion

On NMS fault management interface, view alarm Details, where Error type is listed. Locate the specific handling suggestion according to the listed error type.

The handling suggestions that correspond to different error types are presented below.

Regenerator section trace identifier mismatch.

On NMS configuration management interface (SDH optical channel parameter), check whether the configuration of “J0 configuration mode” and “regenerator section trace” at local end is consistent with those at opposite end. If no, modify configuration to keep consistency.

Multiplex section remote defect indication.

Check alarm status in the multiplex section of opposite end. Since the alarm origin is opposite end, first perform alarm handling at opposite end.

Multiplex section remote error indication.

Check alarm status in the multiplex section of opposite end. Since the alarm origin is opposite end (B2 bit error), first perform alarm handling at opposite end.

High order path trace identifier mismatch.

On NMS configuration management interface (SDH optical channel parameter), check whether the configuration of “J1 Mode 0” and “high order path trace 0” at local end is consistent with those at opposite end. If no, modify configuration to keep consistency.

High order path unequipped.

On NMS configuration management interface (SDH optical channel parameter), check the configuration of optical channel payload type. If the configured value is 0, modify the configuration.

High order path signal label mismatch.

On NMS configuration management interface (SDH optical channel parameter), check the configuration of optical channel payload type. Ensure that the parameter configuration at both sides is the same.

High order path remote defect indication.

Check alarm status in the high order path of opposite end. Since the alarm origin is opposite end, first perform alarm handling at opposite end.



High order path remote error indication.

Check alarm status in the high order path of opposite end. Since the alarm origin is opposite end (B3 bit error), first perform alarm handling at opposite end.

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

Check alarm status in the corresponding tributary unit at opposite end. Since the alarm origin is opposite end, first perform alarm handling at opposite end.

Tributary unit trace identifier mismatch.

On NMS configuration management interface (SDH tributary channel parameter), check whether the configuration of “J2 mode” and “low order path trace” at local end is consistent with those at opposite end. If no, modify configuration to keep consistency.

Tributary unit unequipped.

On NMS configuration management interface (SDH tributary channel parameter), check the configuration of tributary unit payload type. If the configured value is 0, modify the configuration.

Tributary unit signal label identifier mismatch.

On NMS configuration management interface (SDH tributary channel parameter), check the configuration of tributary unit payload type. Ensure that the parameter configuration at both sides is the same.

Others

i. Use meter measurement or loop test to judge whether the alarm is caused by local end or opposite end.

a. Meter Measurement

Use a SDH test meter to test whether the receiving optical signals at local end are normal. If normal, inform the opposite end to troubleshoot.

b. Loop Test


ii. Replace optical module.

iii. Replace optical fiber.

iv. Replace board.



198066048 SDH/SONET:Excessive Error Code Alarm Property


Description: SDH/SONET:Excessive Error Code

Severity: Warning


Probable Cause

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

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

3. Fiber connector is polluted or misconnected.

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

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

System Impact

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

Handling Suggestion


Meter Measurement

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



Loop Test


2. Replace optical module.

3. Replace optical fiber.

4. Replace board.

198066049 ATM Communication Abnormally Alarm Property


Description: ATM Communication Abnormally

Severity: Minor


Probable Cause

1. Bottom layer physical link is abnormal.

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

System Impact

Communication at ATM port is down. All services based on the trunk are interrupted.

Handling Suggestion

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

Related alarms:





2. On NMS configuration management interface, check if SDH/SONET mode configuration exists at both ends. Ensure that the configuration at both ends is consistent.


Meter Measurement

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

Loop Test

Perform self-loop at local trunk. If the alarm persists, fault might lie in local equipment. If the alarm disappears, troubleshoot at opposite end.


5. Replace board.

198083003 Log server is offline alarm Alarm Property


Description: Log server is offline alarm

Severity: Major


Probable Cause

1. Log service is unavailable.

2. Communication between log server and RNC NE is faulty.

System Impact

Log/performance files fail to be reported to the log server.



Handling Suggestion

1. Check whether the control plane communication of the log server is normal

The checking method is as follows.

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

ii. Issue SHELL command of “ping 128.0.31.1” at terminal to see if ping operation is successful. If no, troubleshoot communication fault in control plane.

2. Check whether the log service operation in log server is normal. If no, restart log service.

The checking method is as follows.

Run “/StartLogServ” under the “/home/zte/LogService/bin” directory.

198083027 RSVB Offline alarm Alarm Property


Description: RSVB Offline alarm

Severity: Critical


Probable Cause

1. RSVB rear board of SBCX is manually unplugged from the slot.

2. RSVB board hardware is faulty.

3. RSVB board is not tightly inserted.



System Impact

When the SBCX board which corresponds to the rear board is used as log server, OMM will fail to fetch performance data from the log server.

Handling Suggestion

1. Check if RSVB board is manually unplugged.

If yes, the alarm is certain to be declared. Plug the RSVB board back into the slot.

If no, unplug and plug RSVB board.

2. Replace RSVB board.


C h a p t e r 3

Communication Alarm

This chapter introduces RNC communication alarms with respect to alarm property, probable cause, system impact, and handling suggestion. The information is intended for system maintenance personnel to have a clear understanding of each RNC communication alarm item.



198005122 Communication Link between Active and Standby Boards Off Alarm Property


Description: Communication Link between Active and Standby Boards Off

Alarm level: Minor

Alarm Type: Communication alarm

Probable Cause

1. The board is configured as active/standby, but the opposite board is not in place.

2. Hardware Problem.

System Impact

The active board and standby board communication fails, and the active/standby switchover fails. It has no impact to the services.

Handling Suggestion

1. Make sure the board is Active / Standby configuration, and the active board and standby board is firmly in place.

2. Check the opposite board for the Related Alarms. Perform the recommended solution to process the possible alarms.

Description: 198005379 Board Offline or the CPU is in long period reset status

3. Replace the opposite board.

4. Change the slots of both the active board and the standby board.

Chapter 3 Communication Alarm


198005126 Incorrect FE Routing Connection Alarm Property


Description: Incorrect FE Routing Connection

Severity: Critical


Probable Cause

1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used in the UIM

2. When CHUB connects UIM/GUIM, the connector cable from CHUB rear card RCHUB1/RCHUB2 uses none continuous ports, (example: port1/port3) to connect UIM rear card.

3. When UIM/GUIM connects UIM/GUIM CHUB, pairless connection (such as FE-C2/4) is used for FE routing connection.

4. When UIM is connected to UIM/CHUB, only 1 piece of cable is used for FE connection.

System Impact

Control plane routing disconnection, or circularly handover of the ports. Cause interruption to all the services performed on this shelf.

Handling Suggestion

Reconnect the FE wire.

1. If the UIM on the BUSN shelf uses RUIM1 rear board for FE routing connection, make sure FE-C1/2 port is used for routing port. .

2. If the GUIM on BGSN shelf, make sure FE1,FE2 ports as routing ports for dual shelf cascaded connection or multiple shelf cascaded connection.



3. If TRUNK mode is used, please use multiple FE ports for the TRUNK port of cascaded connection. In this case, make sure the both ends are paired ports.

If the local end or opposite end is not paired port, please reconnect the FE wire and make sure the both ends are paired ports.

Here is an example of connection method:

i. When CHUB is connected to UIM/GUIM, the connecting wire from CHUB rear board RCHUB1/RCHUB2 must use continuous ports ( such as port1/port2 pair, port3/port4, pair, port5/port6 pair, port7/port8 pair ) to connect to the port pairs on the UIM/GUIM rear board.

ii. When UIM is connected to UIM/CHUB, UIM rear board paired ports must be used. If RUIM1 rear board is used, then 2 FE-C1/2 ports must be used for FE routing ports; if RUIM2/RUIM3 rear board is used, then use FE1/FE2 pair, FE3/FE4 pair and FE5/FE6 pair for the FE routing ports.

iii. When GUIM is connected to UIM/GUIM/CHUB, the GUIM rear board ports must be in pair too, i. e. , FE1/FE2 pair must be used for FE routing ports.

198005378 Board HW Error Alarm Property


Description: Hardware Failure on Board

Severity: Major


Probable Cause

1. Clock synchronization error.

2. Hardware failure with the board or the slot.

System Impact

HW connection disturbance, and services through this HW might be interrupted.



Handling Suggestion

1. Check the local board for the Related Alarms. Perform the recommended solution to process the possible alarms.

Related Alarms

198001286 Loss of Clock Input to Board

198005646 Phase-lock Loop Unlocked

2. Check the clock board for the Related Alarms. Perform the recommended solution to process the possible alarms.

Related Alarms

198026133 Clock Output Loss

198026129 Clock reference source lost (Level 1 alarm)



3. Open the Configuration Management window and check whether the SDTB/SDTB2 has configured APS while the active/ standby board is configure.

How to check APS protection configuration: open the rack map on the Configuration Management window, find the SDTB/SDTB2 board, right click to pop up shortcut menu, and select Optical port APS Protection.


5. Replace the slot


198005382 Communication between power board and OMP board abnormal Alarm Property


Description: Communication between power board and OMP board abnormal

Severity: Major




Probable Cause

1. The power board is not connected to the OMP or connection failure occurs.

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

System Impact

Unable to monitor the power supply condition and the environment condition. It has no impact to the services.

Handling Suggestion

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

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

198005397 RAWMACIP Channel Communication Exception Alarm Property


Description: RAWMACIP Channel Communication Exception

Severity: Major


Probable Cause

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

The service media stream exceeds the threshold.



The hardware is faulty.

System Impact

The channel between user plane processing board and signaling processing board is abnormal. This causes the degradation of QoS. In most serious case, the service is totally interrupted.

Handling Suggestion

1. On NMS fault management interface, check if the UIM/GUIM board in the same shelf has related alarms. If yes, follow the suggestions on handling the related alarms.

Related alarm:

198002560 Board CPU overloaded


3. Replace the UIM/GUIM in the same shelf.

4. Replace the slot.

198005401 Test Pack Check Abnormal Alarm Property


Description: Test Pack Check Abnormal

Severity: Major


Probable Cause

1. The board is faulty.

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



System Impact

This alarm affects the service transfer on media plane.

In alarm details, the detected alarm type gives the error type of the alarm. The alarm impact varies depending on the alarm type.

If the test alarm type is “ATM test abnormal”, the ATM board cannot normally provide ATM services. Thus, the service carried by the board is interrupted.

If the test alarm type is “Level 1 switch test abnormal”, it indicates that media plane communication is abnormal. This causes the service carried by this shelf to be interrupted.

Handling Suggestion

On NMS fault management interface, view the alarm details, which give the test alarm type. You can quickly locate the handling method according to the test alarm type.

The handling suggestion for each test alarm type is as follows:

Test alarm type: ATM test abnormal

The link between C5 and APC of ATM processing board is abnormal. In this case, replace the board.

Test alarm type: Level 1 switch test abnormal

The level 1 media plane switching from UIM/GUIM to GLI is abnormal. This is always caused by the abnormal link between UIM/GUIM and GLI. In this case, reconnect the cables between UIM/GUIM and GLI or replace the cables. If optical fibers are used, replace the optical module.

198005650 MAC Address Conflict Exists in Boards of Same Shelf Alarm Property


Description: MAC Address Conflict Exists in Boards of Same Shelf



Severity: Critical


Probable Cause

The DIP switch setting changes

The board is not inserted in position

System Impact

The board fails to start up, or control plane communication is abnormal. As a result, users cannot gain access and existing services are interrupted.

Handling Suggestion

1. Reset the board. After the resetting, the board re-calculates and sets the MAC address according to the DIP switch.

2. Insert the board tightly. Or, unplug and plug the board.

198005651 IPMAC Conflict When OSS Detects Control Plane Alarm Property


Description: IPMAC Conflict When OSS Detects Control Plane

Severity: Major


Probable Cause

1. The board is not plugged in place.



2. Backplane DIP switch configuration has been modified.

System Impact

IPMAC Conflict leads to communication fault in board control plane.

For the board that has powered on, packet loss occurs and board services is unstable. Even worse, link interruption might occur and all services on the board might be interrupted.

For the board that is powering on, board resets repeatedly, and service access to the board fails.

Handling Suggestion

1. Unplug and plug board.

2. Check the backplane DIP switch at the shelf where the board is located and the switch at the shelf where OMP is located. If the switches at two shelves are inconsistent, reconfigure the DIP switch to keep consistency. Reset the relevant boards after reconfiguration.

3. Reset board.

198015617 Faulty Frames Received by FE/GE/ATM/MP/POS/E1 Port Alarm Property


Description: Faulty Frames Received by FE/GE/ATM/MP/POS/E1 Port

Severity: Minor




Probable Cause

1. The network connected with FE/GE/ATM/MP/POS/E1 port is abnormal.

2. The board is in abnormal status.

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

4. Other board hardware faults.

System Impact

Datagram reception of the board is affected. The service on this port might be unstable. Worst of all, all services on the board might be interrupted.

Handling Suggestion

1. Unplug and plug port fiber/network cable.

2. Replace port fiber/network cable.

3. Reset board.


5. Replace board.

198015873 Faulty Frames Received by Internal Switching Interface Alarm Property


Description: Faulty Frames Received by Internal Switching Interface

Severity: Major




Probable Cause

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

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

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

System Impact

If the fault lies in PSN board, service of the entire RNC NE will become unstable. If the alarm persists, all services will be interrupted.

If the fault lies in the board where the alarm is declared, only the services on this board are affected.

Handling Suggestion

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

Related alarm: 198019456 All high-speed links between line card and package switching board are out of synchronism


3. Replace board.

198019213 LIF Alarm of Near-End Receiving Link Alarm Property


Description: LIF Alarm of Near-End Receiving Link

Severity: Major




Probable Cause

Physical fault or connection error occurs to E1 link.

System Impact

IMA link is down.

If several links are available in the IMA group, bandwidth of the IMA group will be affected, and the number of successful upper-layer service access will decrease. However, service interruption will not occur.

If merely one link is available in the IMA group, all services on the IMA group are interrupted.

Handling Suggestion

On NMS fault management interface, view alarm Details where information of IMA chip ID, IMA group ID, IMA link ID, and E1 index is given. Locate the faulty IMA link according to the given information.

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

2. On NMS fault management interface, check if E1-related alarm exists in the board. If yes, refer to the corresponding alarm handling suggestion.

Related alarms:



198001026 Cell delineation do not synchronization about cell on E1 link

198019214 LODS Alarm of Near-End Receiving Link Alarm Property




Description: LODS Alarm of Near-End Receiving Link

Severity: Major


Probable Cause

1. Operation of the input clock is abnormal.

2. Transmission quality of the link is poor.

System Impact

IMA link is down.



Handling Suggestion


1. Check the RUN indicator of clock board. If the indicator is green and flashes slowly, operation of the clock board must be normal. Otherwise, reset/replace the clock board.

2. On NMS fault management interface, check if clock-related alarm occurs in UIM/GUIM. If yes, input clock source must be abnormal. Refer to the corresponding alarm handling suggestion.

Related alarms: 198026117 PP2S clock reference lost

3. On NMS fault management interface, check if E1-related alarm exists. If yes, refer to the corresponding alarm handling suggestion.

Related alarms:



198001026 Cell delineation do not synchronization about cell on E1 link



198019215 RDI Alarm of Near-End Receiving Link Alarm Property


Description: RDI Alarm of Near-End Receiving Link

Severity: Major


Probable Cause

1. Remote IMA link is not in activated status.

2. Remote receiving direction is faulty.

System Impact

IMA link is down.



Handling Suggestion


Check the working status of the relevant remote receiving link by referring to the opposite equipment operation guide. If remote receiving link is not in activated status, activate the link.



198022784 BFD Session Interrupted Alarm Property


Description: BFD Session Interrupted

Severity: Minor


Probable Cause

1. The network cable connection on relevant equipment (including local/ intermediate/opposite equipment) is loose or disconnected.

2. Intermediate equipment is faulty.


4. Local equipment is faulty.

5. Configuration related to the BFD session is incorrect.

System Impact

All services on the path related to the BFD session will be switched to the slave path. Service interruption will occur if slave path does not exist.

Handling Suggestion

On NMS fault management interface, view alarm Details where information of source address and destination address of the BFD session is given. The source address is the address of local equipment. The destination address is the address of BFD session terminal equipment.

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

2. Check the physical connection at the BFD session-related port on local line card. If the connection is loose or broken,



unplug and plug the cable or replace the cable. If port indicator is on, the physical link must be normal.

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

i. Telnet to the interface board. Test if the link is normal via ping. If the destination address is 2.2.2.10, issue the following command in telnet interface.

brs_ping_b “2.2.2.10”

ii. Wait for 5 seconds and issue the following command.

BrsShowLog “ICMP”

a. If “PING===>destine 2.2.2.10 timeout, Response timeout must occur” appears on the interface, response timeout must occur.

b. If “ping_receive:Reply from 2.2.2.10: bytes=60 time<1ms” appears, response must be normal, indicating that the link is normal.

iii. In the case of response timeout, check if the configuration of related route and address is correct. If not, perform reconfiguration and retest.

iv. In the case of response timeout despite correct route/address configuration, certain link or intermediate equipment might be faulty. Check if disconnected network cable, loose connection, or abnormal equipment status exists on the faulty link along the BFD session path. If yes, take necessary measures, including cable replacement and replugging, equipment repair or replacement.

4. If packet reception and transmission are normal as confirmed by ping, check if the BFD session configuration at both ends is correct.

On NMS configuration management interface,

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

ii. Ensure that BFD session working modes at both sides are consistent.

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

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

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

vi. Check configuration authentication information. Ensure that the number of authentication information configured at both ends are consistent.

5. Reset the board where the interface is located.



198066003 Control Plane Communication Abnormal Between Board and Its Home Module Alarm Property


Description: Control Plane Communication Abnormal Between Board and Its Home Module

Severity: Major


Probable Cause

1. The board is not in position.


3. The control plane communication is abnormal.

4. The board is reset.

System Impact

The services carried by the board are interrupted.

Handling Suggestion

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

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


4. Replace the board slot.

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



198066004 Control Plane Communication Abnormal Between MP and OMP Alarm Property


Description: Control Plane Communication Abnormal Between MP and OMP

Severity: Major


Probable Cause

1. The board is not in position.


3. The control plane communication is abnormal.

4. The board is reset.

System Impact

The board is blocked and the functions of the board are unavailable. As a result, all services of the units under this module are unavailable.

Handling Suggestion

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

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


4. Replace the board slot.

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



198066019 Association link broken Alarm Property


Description: Association link broken

Severity: Major


Probable Cause

1. The association is released in dynamic data management.

2. Association configuration is modified at local end.

3. Association is released at opposite end.

4. Bottom layer link is faulty.

System Impact

If several association links are available to the destination office, service will not be affected. In the case of heavy traffic, congestion of available association(s) might occur, leading to upper layer call loss or increasing PS call access failures.

If merely one association link is available to the destination office, the office might become inaccessible. Reception and sending of messages from/to the relevant office fail. Access of new services under this office fails, and abnormal release of ongoing services occurs.

Handling Suggestion

1. Establish the association in dynamic data management.

2. On NMS configuration management interface, check association configuration at local end and opposite end. Checking items include protocol type of SCTP association, SMP module No, local IP address, local port No., remote IP address, remote port No., the number of in/out streams. If



the configuration at both ends is inconsistent, modify configuration to keep consistency.

3. Ping the opposite board address to see if the network cable or other intermediate link is faulty. Replace the cable if ping fails.

4. Check if the association is released at opposite end. If yes, troubleshoot according to the corresponding cause.

198066026 Association path broken Alarm Property


Description: Association path broken

Severity: Major


Probable Cause

1. Network communication is faulty.

2. Control plane path in NE is interrupted.


4. The route to remote address is lost.

System Impact

If multiple paths are available for the association and there exists normal path, relevant services will not be affected.

If merely one path is available for the association, all services on the association is down.

Handling Suggestion

On NMS fault management interface, view alarm Details, where information of association ID, local address, and remote address is given.



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

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

Related alarm: 198066003 Control plane communication abnormal between board and its home module

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

4. Check the intermediate equipment on association path. If the routes to local address and remote address of the association are not configured, add the configuration according to equipment operation manual.

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

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

198066029 PPP link broken Alarm Property


Description: PPP link broken

Severity: Major


Probable Cause

1. The alarm occurs once in PPP port during board power-on, and recovers after successful PPP negotiation..

2. Physical link is down, or link transmission quality is poor.

3. Adjustment of PPP link parameter leads to link re-negotiation, causing the alarm.



System Impact

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

Handling Suggestion

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

1. Check cable connection at both ends. If the cable is disconnected or connection is loose, unplug and plug the cable or replace the cable.

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

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

4. On NMS configuration management interface, check PPP configuration. Ensure that the relevant configuration at both sides is consistent.

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

198066045 Trunk error Alarm Property


Description: Trunk error

Severity: Major




Probable Cause

1. The receiving cable of local trunk equipment is faulty.

The cable is disconnected, or cable connector is broken.

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

The cable is disconnected, or cable connector is broken.

3. Trunk transmission line is faulty.

The local DDF and equipment are not properly connected.

4. Operation of LOS insertion is operated at opposite trunk equipment.

Manual inset alarm operation is performed in diagnostic test

System Impact

The trunk equipment fails to work normally. All services based on the trunk are interrupted.

Handling Suggestion

1. check whether the alarm is caused by local end or opposite end via meter measurement or loop test.

Meter Measurement

Use a trunk test meter to test whether the trunk receiving signals at local end are normal. If yes, fault might lie in local equipment. If no, troubleshoot at opposite end.

Loop test

Perform trunk self-loop at local end. If the alarm persists, fault might lie in local equipment. If the alarm disappears, troubleshoot at opposite end.


3. Replace board.



198066046 Trunk abnormal Alarm Property


Description: Trunk abnormal

Severity: Major


Probable Cause

1. Trunk frame formats at local end and at opposite end are inconsistent.

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

3. Local trunk equipment is faulty.

4. Equipment grounding at both ends is bad.

5. Impedance mismatch occurs.

System Impact

All services based on the trunk are interrupted.

Handling Suggestion

On NMS fault management interface, view alarm Details, where Error type is listed. Locate the specific handling suggestion according to the listed error type.

The handling suggestions that corresponds to different error types are presented below.

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 configuration), Check whether frame type configuration at local end and at opposite end is consistent.

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

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



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

Far-end alarm indication received by trunk of E1.

Check the alarm status at opposite end. Since the alarm origin is opposite end, first troubleshoot at opposite end.

198066060 FE Link Error Alarm Alarm Property


Description: FE Link Error Alarm

Severity: Minor


Probable Cause

1. In a pair of FE ports, one has normal link but the other has link error.

2. The hardware is faulty.

System Impact

Since one FE port in the control plane link can work normally, the service is not affected. If this port is also faulty, the service will be interrupted because the service cannot be switched over to the other port.

Handling Suggestion

1. Check if only one cable is used to connect the port pair of the rear board to the peer-end FE port. Ensure that both cables are connected to the peer end.

2. Reconnect the cables or replace the cables.

3. Replace the rear board.




198083021 CCP Link Fault Alarm Alarm Property


Description: CCP Link Fault Alarm

Severity: Major


Probable Cause

The transmission is faulty.

System Impact

The CCP transmission link is unavailable. Therefore, the CCP cannot be used during radio link establishment. If Node B continues to select this CCP, RNC messages cannot reach Node B and the current service is interrupted.

Handling Suggestion

Check if the Node B corresponding to the faulty CCP has generated associated alarms. Follow the suggestions on handling the related alarms. The related alarms are as follows:

IP mode

According to the association link number, check if alarms related to association links exist through the fault management interface. If yes, follow the suggestions on handling the related alarms:


198066018 Association congested

198066019 Association link broken

ATM mode



i. Bottom layer transmission fault

Check if related alarms exist. If yes, follow the suggestions on handling the related alarms.




198066048 SDH/SONET: Excessive Error Code


ii. PVC link break

Check if the related alarm exists. If yes, follow the suggestions on handling the related alarm.


198018944 PVC Fault


C h a p t e r 4

Processing Alarm

This chapter introduces RNC processing alarms with respect to alarm property, probable cause, system impact, and handling suggestion. The information is intended for system maintenance personnel to have a clear understanding of each RNC processing alarm item.



198005123 DB Config Doesn't Fit for Device Alarm Property


Description: DB Config Doesn't Fit for Device

Severity: Minor

Alarm Type: Processing alarm

Probable Cause

1. The type of physical board is incorrectly configured.

2. A wrong board is inserted

System Impact

The board fails to be normally powered on. The services carried by the board are interrupted.

Handling Suggestion

1. The NMS configuration management interface gives the rack diagram. Select the board and check if the board and subunit settings of rack are correct. If the settings are incorrect, delete the board and create a new one.

2. Check if a correct board is inserted in the slot on the rack. If not, insert the correct one.

Chapter 4 Processing Alarm


198005387 Alarm Due to Inconsistent MP Type Alarm Property


Description: Alarm Due to Inconsistent MP Type

Severity: Major


Probable Cause

1. The MP type is changed on NMS and the board is not restarted.

2. The active MP type on the local board is not consistent with that configured on NMS.

System Impact

This alarm has no effect on the service.

Handling Suggestion

1. For CMP and SMP, reset the board.

2. For OMP, set the start mode as “foreground start” on NMS and then reset the board.

Do as follows:

On NMS software version management interface, select the menu for querying foreground (that is, RNC NE) board start mode. In the pop-up dialog box, set the start mode to “foreground start”.



198005388 Startup File Does Not Exist Alarm Property


Description: Startup File Does Not Exist

Severity: Major


Probable Cause

The startup configuration file is deleted.

System Impact

This alarm may cause OMP work abnormally, and the entire NE services are affected.

Handling Suggestion

1. Reset the active and standby OMPs.


198005398 Inconsistent Office ID Settings of DIP Switch Alarm Property


Description: Inconsistent Office ID Settings of DIP Switch



Severity: Major


Probable Cause

The office ID set through DIP switch is different from that of the shelf where OMP is located.

System Impact

The MAC addresses conflict. The board MAC and IP address verification fails. All boards in the shelf cannot be powered on. All services carried by the shelf are interrupted.

Handling Suggestion

Set the DIP switch for office ID setting in this shelf to that of the shelf where OMP is located.

198005649 Port Work Mode Doesn't Match Settings Alarm Property


Description: Port Work Mode Doesn't Match Settings

Severity: Major


Probable Cause

1. The local device does not support this mode setting.

2. The peer device does not support this mode setting.



System Impact

1. The port fails to work in the preset mode. This causes the port to be unavailable and all services of the port are interrupted.

2. For Auto mode, the bandwidth of the external port becomes insufficient. As a result, some services of the port are interrupted.

Handling Suggestion

On NMS fault management interface, view the alarm details, which give the reason of mode error. You can quickly locate the handling method according to the reason of mode error.

The handling suggestion for each reason of mode error is as follows:

Speed mode error

i. Determine the rate to be configured. Replace the existing board with the one supporting the configured rate mode.

ii. For Force mode, configure the port with the rate supported by the bottom layer in actual working status.

Do as follows:

On NMS configuration management interface, set the rate in subunit details to the rate supported by the bottom layer in actual working status.

iii. For Auto mode, re-configure the expected rate and ensure that it is consistent with the actual port rate.

Do as follows:

On NMS configuration management interface, set the rate in subunit details to the expected one.

Duplex mode error

i. Determine the required mode. Replace the existing board with the one supporting the mode configured on RNC.

ii. For Force mode, configure the port with the duplex mode supported by the bottom layer in actual working status.

Do as follows:

On NMS configuration management interface, set the Work Mode in subunit details to the work mode supported by the bottom layer in actual working status.

iii. For Auto mode, re-configure the expected duplex and ensure that it is consistent with the actual port duplex.

Do as follows:



On NMS configuration management interface, set the work mode in subunit details to the expected one.

GE port master and slave mode error

i. Determine the required master and slave mode. Replace the existing board with the one supporting the master and slave mode configured on RNC.

ii. For Force mode, configure the port with the master and slave mode supported by the bottom layer in actual working status.

Do as follows:

On NMS configuration management interface, set the GE port master and slave mode in subunit details to the master and slave mode supported by the bottom layer in actual working status.

iii. For Auto mode, re-configure the expected master and slave mode and ensure that it is consistent with the actual port master and slave mode.

Do as follows:

On NMS configuration management interface, set the GE port master and slave mode in subunit details to the expected one.

198015360 Microcode Is Abnormal Alarm Property


Description: Microcode Is Abnormal

Severity: Major


Probable Cause

Network Processor hardware is faulty.



System Impact

The board will reboot.

If the alarm can be restored after board rebooting, all board services during rebooting will be down, but access of new services to the board after rebooting will be successful.

If the alarm cannot be restored after board rebooting, all board services during and after rebooting will be down.

Handling Suggestion

Wait for the board to reboot. If the alarm cannot be restored after board rebooting, unplug and then plug the board. If the alarm still cannot be restored, replace the board.

198018944 PVC Fault Alarm Property


Description: PVC Fault

Severity: Minor


Probable Cause

1. PVC connection for the equipment is loose or disconnected. PVC connection falls into the following three types.

Fiber connection, carried by optical interface.

E1/T1 connection, carried by IMA port.

Fiber connection, carried by IMA port.

2. Continuity Check (CC) test is started at local end, but not started at opposite end.

System Impact

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



Handling Suggestion

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

For example, the PVC ID given in alarm Details is 1. On NMS configuration management interface (PVC configuration), try to locate the PVC whose ID is 1. View the related subsystem No., unit No., ATM port No. to locate the corresponding interface board and port.

2. Check the relevant equipment based on the physical bearer of the port.

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

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

Related alarms:

a. 198019207 Near-End IMA Group Configuration Failure

b. 198019213 LIF Alarm of Near-End Receiving Link

c. 198019214 LODS Alarm of Near-End Receiving Link

d. 198019215 RDI Alarm of Near-End Receiving Link

e. 198019221 Remote Receiving Link ID Mismatched

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

4. Check if the PVC status at opposite end is successful. If no, refer to the maintenance manual of opposite equipment for troubleshooting.

5. Deactivate CC test at local end, or activate CC test at opposite end.

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

To activate CC test at opposite end, initiate PVC CC test on NMS test management interface. When configuring test parameters, select “1: Activate CC” for activation type; select “1: B-A” for test type.



198019207 Near-End IMA Group Configuration Failure Alarm Property


Description: Near-End IMA Group Configuration Failure

Severity: Major


Probable Cause

IMA group configuration at local end and at opposite end is inconsistent.

System Impact

All services on the IMA port are interrupted.

Handling Suggestion

On NMS fault management interface , view alarm Details where information of the faulty IMA group is given.

On NMS configuration management interface (IMA group configuration), locate the corresponding IMA group according to the information given in alarm Details. Compare the configuration of the following parameters at both ends. If the configuration at both ends is inconsistent, modify configuration at either end to keep consistency.

“Near-End OMA Label”

“Rx Frame Length (cells)”

“Tx Frame Length (cells)”

“Near-End Symmetry”



198023040 Number of Alarms Over Threshold Alarm Property


Description: Number of Alarms Over Threshold

Severity: Major


Probable Cause

There are too many alarms for this board. The alarm pool is full of board alarms.

System Impact

Alarm information loss might occur. No impact on user service.

Handling Suggestion

Troubleshoot the current alarms in the system.

198066027 SNTP failure Alarm Property


Description: SNTP failure

Severity: Minor




Probable Cause

1. SNTP server does not exist or server operation is abnormal.

2. The configured SNTP IP address in the database is inconsistent with the real IP address.

3. Communication between RNC NE and SNTP server is down.

System Impact

SNTP synchronization failure might lead to inconsistency between system time and real time. For example, the real time is 1:00 am, but the displayed system time is 2:00 am. Since system clock frequency is correct, service will not be affected.

Handling Suggestion

On NMS fault management interface, view alarm Details where Alarm Reason is given. Locate the specific handling suggestion according to the given reason.

The handling suggestions that correspond to different alarm reasons are described below.

Illegal DB configuration.

On NMS configuration management interface (RNC ground resource management), check if SNTP server IP address or SNTP synchronization period are incorrectly configured. If yes, which means SNTP server IP is configured as 255.255.255.255 or SNTP synchronization period is 0, correct the configuration.

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 database and the real server IP are consistent.



198066031 Number of management module alarms exceeds the threshold Alarm Property


Description: Number of management module alarms exceeds the threshold

Severity: Major


Probable Cause

There are too many system alarms. The alarm pool is full of system alarms.

System Impact

Alarm information loss might occur. No impact on user service.

Handling Suggestion

Delete the trivial alarms on NMS fault management interface.

198066032 NTP time exceeds threshold Alarm Property


Description: NTP time exceeds threshold



Severity: Minor


Probable Cause

1. Link between OMP and RPU is down.

2. NTP time and local time differs greatly.

System Impact

NTP time synchronization terminates, leading to interruption of ongoing services.

Handling Suggestion

On NMS fault management interface, check if the alarm related to RPU board exists. If yes, refer to the corresponding alarm handling suggestion.

Related alarm: 198066004 Control plane communication abnormal between MP and OMP

198066057 Database Config Is Different from File Named bootcfg ini. Alarm Property


Description: Database Config Is Different from File Named bootcfg ini.

Severity: Major




Probable Cause

After the start information of OMP is modified, the active and standby OMP boards are not restarted.

System Impact

The bootcfg ini. file contains the information on the office ID, district ID, OMP gateway, OMC MAC address, and OMC gateway mask. If the information is modified, the OMP cannot connect to OMC and external network normally.

Handling Suggestion

Restart the active and standby OMPs.

198083022 Cell Is out of Service Alarm Property


Description: Cell Is out of Service

Severity: Major


Probable Cause

1. Node B returns the message that the cell fails to be established.

2. Cell Configuration Generation ID (CGID) audited by Node B is zero.

3. Real-time cell blockage is performed at Node B side.

4. The failure to update system message results in cell deletion and creation.



System Impact

The cell is unavailable and fails to provide services. Users fail to gain access through this cell.

Handling Suggestion

On NMS fault management interface, view the alarm details, which give the alarm cause. You can quickly locate the handling method according to the alarm cause.

The handling suggestions for each alarm type are as follows:

Alarm reason: Node B setup cell failed.

i. Check if the frequency points of RNC and Node B are consistent with the local cell ID.

Do as follows:

On NMS configuration management interface, select the cell to be viewed under Base Station Radio Resource Management > WCDMA Radio Resource Management >Baseband Resource Pool. Check if the values of Local Cell ID, Receiving Frequency Point, and Transmitting Frequency Point in “Local Cell Basic Parameters” are consistent with those at RNC side. If not, modify the RNC or Node B configurations to make them consistent.

ii. On NMS fault management interface, check if Node B has generated “198084129 Board reboots alarm”. If yes, it indicates that the Node B has just been started or hardware has been just replaced or added. In this case, wait for the Node B to finish powering on.

Alarm reason: Cell CGID is zero audit by NodeB.

Local cell is blocked

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

Node B is blocked or faulty

On the ground resource configuration interface, view Node B status. If the status is blocked, unblock the Node B. If the status is faulty, it indicates that FS board may be faulty. In this case, check if related alarms exist. If yes, follow the suggestions on handling the related alarms.


i. 198084117 Application software monitoring alarm



ii. 198084123 Board communication link is interrupted.

iii. 198084107 Board parameter synchronization abnormity

Local cell is faulty

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




iv. 198084129 Board reboots alarm

Baseband board is blocked

View the BPC board status. If the status is blocked, unblock it.

Baseband board is faulty

View the BPC board status. If the status is faulty, handle the alarm by referring to the following suggestions:




iv. 198084129 Board reboots alarm

Alarm reason: Cell is blocked at NodeB side.

On NMS configuration management interface, select the cell to be viewed under Base Station Radio Resource Management > WCDMA Radio Resource Management > Baseband Resource Pool. If the cell status is blocked, unblock it.

Alarm reason: System information update fail.

The alarm is caused by the failure to update system messages, that is, system message broadcast fails. Handle the alarm by referring to the suggestion for “198070009 Broadcast fail”.

For other alarm causes, the system re-establishes the cell automatically. No human intervention is required.



198083023 Node B Is out of Service Alarm Property


Description: Node B Is out of Service

Severity: Major


Probable Cause

The transmission is faulty.

System Impact

The Node B is unavailable and fails to provide services. Users fail to gain access through this Node B.

Handling Suggestion

The handling suggestions classified by transmission mode are as follows:

IP mode

According to the association link number, check if alarms related to association links exist through the fault management interface. If yes, follow the suggestions on handling the related alarms:


198066018 Association congested

198066019 Association link broken

ATM mode

i. Bottom layer link fault

Check if related alarms exist on the board. If yes, follow the suggestions on handling the related alarms.






198066048 SDH/SONET:Excessive Error Code


ii. Unavailable PVC

Check if related alarms exist on the board. If yes, follow the suggestions on handling the related alarms.


198018944 PVC Fault

198083024 receiver on ICM is abnormal Alarm Property


Description: receiver on ICM is abnormal

Severity: Major


Probable Cause

1. GPS subcard is not tightly inserted.

2. Hardware of GPS subcard is faulty.

System Impact

GPS subcard mainly provides positioning function for RNC NE. The subcard fault leads to handset positioning failure. Service is not affected.

Handling Suggestion

1. Unplug and plug GPS subcard.

2. Replace GPS subcard.


C h a p t e r 5

Environment Alarm

This chapter introduces RNC environment alarms with respect to alarm property, probable cause, system impact, and handling suggestion. The information is intended for system maintenance personnel to have a clear understanding of each RNC environment alarm item.



198025856 Rack temperature is higher than high threshold Alarm Property


Description: Rack temperature is higher than high threshold

Severity: Minor

Alarm Type: Environment alarm

Probable Cause

1. Threshold configuration is unreasonable.

2. Actual rack temperature is too high.

System Impact

1. If the alarm is caused by unreasonable threshold configuration, service will not be affected.

2. If the alarm is caused by high rack temperature, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the upper limit of rack temperature. Modify the threshold value if the previous configuration is unreasonable. The recommended upper threshold value is 70.

2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take necessary cooling measures.

3. Remove dust at the air inlet and outlet of the rack. Remove the nearby object that obstructs rack ventilation.

Chapter 5 Environment Alarm


4. Ensure that the rack fan works normally.

198025857 Rack temperature is lower than low threshold Alarm Property


Description: Rack temperature is lower than low threshold

Severity: Minor


Probable Cause


2. Actual rack temperature is too low.

System Impact


2. If the alarm is caused by low rack temperature, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the lower limit of rack temperature. Modify the threshold value if the previous configuration is unreasonable. The recommended low threshold value is 0.

2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes, take necessary warming measures.



198025858 House temperature is higher than high threshold Alarm Property


Description: House temperature is higher than high threshold

Severity: Minor


Probable Cause


2. Actual temperature in equipment room is too high.

System Impact


2. If the alarm is caused by high room temperature, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the upper limit of equipment room temperature. Modify the threshold value if the previous configuration is unreasonable. The recommended high threshold value is 40.

2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take necessary cooling and ventilation measures.



198025859 House temperature is lower than low threshold Alarm Property


Description: House temperature is lower than low threshold

Severity: Minor


Probable Cause


2. Actual temperature in equipment room is too low.

System Impact


2. If the alarm is caused by low room temperature, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the lower limit of equipment room temperature. Modify the threshold value if the previous configuration is unreasonable. The recommended low threshold value is 0.

2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take necessary cooling and ventilation measures.



198025860 Any one of rack voltage inputs above threshold Alarm Property


Description: Any one of rack voltage inputs above threshold

Severity: Minor


Probable Cause


2. Actual voltage is too high.

System Impact


2. If the alarm is caused by high voltage, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the upper limit of rack voltage. Modify the threshold value if the previous configuration is unreasonable. For 48 V power, the recommended high threshold value is 57. For 60 V power, the recommended value is 72.

2. Locate the specific line whose voltage is over high threshold according to the voltage index listed in alarm Details. Lower the input voltage of that line.



198025861 Voltage is lower than low threshold Alarm Property


Description: Voltage is lower than low threshold

Severity: Minor


Probable Cause


2. Actual voltage is too low.

System Impact


2. If the alarm is caused by low voltage, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the lower limit of rack voltage. Modify the threshold value if the previous configuration is unreasonable. For 48 V power, the recommended low threshold value is 40. For 60 V power, the recommended value is 50.

2. Locate the specific line whose voltage is below low threshold according to the voltage index listed in alarm Details.. Increase the input voltage of that line.



198025862 Humidity in equipment room above threshold Alarm Property


Description: Humidity in equipment room above threshold

Severity: Minor


Probable Cause


2. Actual humidity in equipment room is too high.

System Impact


2. If the alarm is caused by high room humidity, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the upper limit of equipment room humidity. Modify the threshold value if the previous configuration is unreasonable. The recommended high threshold value is 90.

2. Check the hygrometer in equipment room to see if the actual humidity is too high. If yes, take necessary dehumidifying measures.



198025863 Humidity in equipment room below threshold Alarm Property


Description: Humidity in equipment room below threshold

Severity: Minor


Probable Cause


2. Actual humidity in equipment room is too low.

System Impact


2. If the alarm is caused by low room humidity, board operation might be abnormal and board services might be interrupted.

Handling Suggestion

1. On NMS configuration management interface (power board alarm parameters), check the lower limit of equipment room humidity. Modify the threshold value if the previous configuration is unreasonable. The recommended low threshold value is 20.

2. Check the hygrometer in equipment room to see if the actual humidity is too low. If yes, take necessary humidifying measures.



198025864 Rack fans faults Alarm Property


Description: Rack fans faults

Severity: Minor


Probable Cause

1. FAN module is not tightly inserted into the rack.

2. FAN module hardware is faulty.

System Impact

This alarm might lead to excessively high rack temperature, resulting in abnormal board operation and interruption of board services.

Handling Suggestion

1. Check if the FAN module is tightly inserted into the rack. If no, unplug and plug the FAN module.

2. Replace FAN module.

198025865 Rack door access control alarm Alarm Property


Description: Rack door access control alarm

Severity: Minor




Probable Cause

1. The rack door is not closed.

2. Door control connection is incorrect.

System Impact

Service is not affected, but the alarm poses a potential safety hazard.

Handling Suggestion

1. Open and re-close the rack door to ensure that the rack door is tightly closed.

2. Open the rack door to check the installation of door control. Ensure that the door access control is correctly installed and connected. Then close the rack door.

198025866 Smoke alarm Alarm Property


Description: Smoke alarm

Severity: Minor


Probable Cause

1. The alarm is faulty.

2. The smoke density in equipment room is too high.



System Impact

Service is not affected, but the alarm poses a potential safety hazard.

Handling Suggestion

1. Locate and handle the smog origin as soon as possible.

2. If no smog exists in the equipment room, replace the smog detector.

198025867 Infrared alarm Alarm Property


Description: Infrared alarm

Severity: Minor


Probable Cause

1. Heat source (such as animal/human) comes near.

2. Configuration of Infrared sensor is incorrect.

3. Infrared sensor is faulty.

System Impact

If the alarm is caused by infrared sensor configuration error, system is not affected.

If the alarm is caused by infrared over threshold, be careful of potential safety hazard in the equipment room.



Handling Suggestion

1. Check if any animal or human comes near the infrared sensor. If yes, remove the heat source. If no, check the infrared sensor configuration. If appropriate, sensor sensitivity can be somewhat reduced.

2. The infrared sensor is faulty. Replace sensor.

198025868 Lightning alarm Alarm Property


Description: Lightning alarm

Severity: Minor


Probable Cause

In bad weather, the equipment room is hit by lightning stroke.

System Impact

The board operation might be abnormal due to the lightning stroke. Interruption of board services might occur.

Handling Suggestion

1. Check earthing connection.

2. Check lightning protection antenna.



198066064 Power Switch Alarm Alarm Property


Description: Power Switch Alarm

Severity: Minor


Probable Cause

The power switch is open.

System Impact

Shelf power supply is affected. All boards on the shelf fail to work normally and board services are interrupted.

Handling Suggestion

Check if the shelf is needed.

If yes, ensure that the power switch is closed and that ALM Indicator light is normal.

If no, shield the monitor of power switch in NMS. On NMS configuration management interface (power board alarm parameters), configure the power switch as shielded.


C h a p t e r 6

QoS Alarm

This chapter introduces RNC QoS alarms with respect to alarm property, probable cause, system impact, and handling suggestion. The information is intended for system maintenance personnel to have a clear understanding of each RNC QoS alarm item.



198023296 Inter-board Message Communication Flow Rate Over Alarm Threshold Alarm Property


Description: Inter-board Message Communication Flow Rate Over Alarm Threshold

Severity: Minor

Alarm Type: QoS alarm

Probable Cause

The configured alarm threshold is less than the usual inter-board communication traffic in input and output directions of the board control plane.

System Impact

No impact on user service.

Handling Suggestion

On NMS configuration management interface, check if the configured alarm threshold of communication traffic in input and output directions of the board control plane is too low.

Recommended value: 0xffffffff(4096M).

Chapter 6 QoS Alarm


198066018 Association congested Alarm Property


Description: Association congested

Severity: Minor

Alarm Type: QoS alarm

Probable Cause

1. Transmission quality of bottom layer link is poor.

2. Upper layer traffic in sending service data is heavy.

System Impact

Transmission delay, or even packet loss will occur. If congestion is not serious, service will not be affected. Otherwise, call loss might occur, and access success rate of PS service might fall.

Handling Suggestion

1. Check network cable connection. Ensure that the network cable is tightly inserted.

2. Add association links to the office that is in service for the congested association.

3. If intermediate equipment exists between local end and opposite end, check the transmission quality of intermediate equipment.


Glossary

Glossary Full Name

A

AAL2 ATM Adaptation Layer 2

AAL5 ATM Adaptation Layer type 5

ACL Access Control List

AEM Antenna Equipment Module

AIS Alarm Indication Signal

AIU A Interface Unit

AMR Adaptive Multi Rate

APBE ATM Process Board Enhanced version

APP Agere Processor Product

APS Automatic Protection Switching

AS Application Server

ASP Application Server Process

ATM Asynchronous Transfer Mode

B

BBU BaseBand Unit

BCCH Broadcast Control Channel

BCSN Backplane of Circuit Switch Network

BCTC Backplane of Control Center

BFD Bidirectional Forwarding Detection

BGP Border Gateway protocol

BGSN Backplane of Giga Universal Service Network

BHCA Busy-Hour Call Attempts

BIOS Basic Input/Output System

BIPB Abis Interface Processing board

BIPI BSC IP Interface board

BIU Abis Interface Unit

BPC Baseband Processing board type C

BPSN Backplane of Packet Switch Network



Glossary Full Name

BSC Base Station Controller

BSS Base Station System

BSSAP Base Station System Application Part

BSSGP Base Station System EDGE/GPRS Protocol

BTS Base Transceiver Station

BUSN Backplane of Universal Switch Network

C

CAS Channel Associated Signaling

CC Calling Control

CC Control and Clock Module

CCS Common Channel Signaling

CCS7 Common Channel Signaling System NO.7

CDU Combiner Distribution Unit

CEU Combiner Extension Unit

CHP Channel Processor

CHUB Control plane HUB

CIP Carrier Interface Part

CLKG Clock Generator

CM Communication Management

CMB Control & Maintenance Board

CMM Controller & Maintenance Module

CMP Control Main Processor

CN Core Network

CP Channel Processor

CPU Central Processing Unit

CRC Cyclic Redundancy Check

CS Circuit Switch

CSU Channel Service Unit

CTC Common Transmit Clock

CU Carrier Unit

D

DBS Data Base Subsystem

DC Direct Current

DCE Data Circuit terminating Equipment

DDF Digital Distribution Frame

DDN Digital Data Network

Glossary


Glossary Full Name

DFCM Dual -carrier Fan Control Module

DH Dual Homing

dRCU Double Radio Carrier Unit

DRTB Dual Rate Transcoder Board

DSP Digital Signal Processor

DTB Digital Trunk Board

DTE Data Terminal Equipment

dTPB Dual-carrier Transceiver Process Board

DTRU Dual -carrier Transceiver Unit

DTU Digital Trunk Unit

DTX Discontinuous Transmission

DXC Digital Cross Connection

E

EAM External Alarm Module

EIPI E1 IP Interface

EIR Equipment Identification Register

EMC ElectroMagnetic Compatibility

EMI Electro Magnetic Interference

EPLD Erasable Progammable Logic Device

EPU Epilogue protocol Process Unit

ETSI European Telecommunications Standards Institute

ETSN Enhanced TDM Switch Network Board

F

FAM Fan Alarm Module

FCLK Frame Clock

FCM Fan Control Module

FCU Fused Combiner Unit

FDM Fan Driver Module

FE Fast Ethernet

FIB Fast-Ethernet Interface Board

FN Frame Number

FNCB Fan Control Board

FNIB Fan Interface Board

FPGA Field Programmable Gate Array

FR Frame Relay

FRS Full Rate Service



Glossary Full Name

FSMU Far SubMultiplexing Unit

FU Frame Unit

FUC Frame Unit Controller

G

GERAN GSM/EDGE Radio Access Network

GIPB Gb Interface Processing board

GIPI GE IP Interface

GIU Gb Interface Unit

GLI Gigabit Line Interface

GND Ground

GNDP Ground Protection

GOV Global Overflow

GPRS General Packet Radio Service

GPS Global Position System

GSM Global System for Mobile Communication

GT Global Title

GUIM Gigabit universal Interface Module

GUN Global Underflow

GUP GSM Universal Processing board

GUP2 GSM Universal Processing board

H

HBTS Home-BTS

HDLC High-level Data Link Control protocol

HEC Header Error Check

HLR Home Location Register

HPI Host Port Interface

HSCSD High Speed Circuit Switched Data

HTRG Home-BTS Transceiver Unit for GSM900/DCS1800

HTRP Home-BTS Transceiver Unit for GSM850/PCS1900

HTRU Home-BTS Transceiver Unit

HW High Way line

I

ICM Integrated Clock Module

ICP IMA Control Protocol

ICT Independence Clock Template

IFB IP interface control Block

Glossary


Glossary Full Name

IMA Inverse Multiplexing for ATM

IMAB IMA Board

IMSI International Mobile Subscriber Identity

IP Internet Protocol

IPCP IP Control Protocol

ISNI Intermediate Signaling Network Identification

ISIS Intermediate System to Intermediate System

ITU International Telecommunication Union

L

LAN Local Area Network

LAPD Link Access Protocol on the D channel

LCD Loss of Cell Delineation defect

LLC Logical Link Control

LMT Local Management Terminal

LNA Low Noise Amplifier

LOF Lose Of Frame

LOM Loss of Multiframe

LOP Loss of Pointer

LOS Lose Of Signal

LSA Link State Advertisement

LVDS Low Voltage Differential Signaling

M

MAC Medium Access Control

MCC Multi-Channel Control

MM Mobility Management

MNIC Multi-Service Network Interface Card

MO Management Object

MS Mobile Station

MSC Mobile Services Switching Center

MSS Mobile Switch System

MTP Message Transfer Protocol

M2PA MTP2 Peer-to-Peer User Adaptation

M3UA MTP3 User Adapter Layer

N

NEF Network Element Function

NID Network Identifier



Glossary Full Name

NS Network Service

NSE Network Service Entity

NSEI Network Service Entity Identifier

NSMU Near SubMultiplexing Unit

NSVC Network Service Virtual Connection

NSVCI Network Service Virtual Connection Identifier

NTP Network Time Protocol

O

OAM Operation Administration and Maintenance

ODF Optical Distribution Frame

OMC Operation and Maintenance Center

OMP Operation Main Processor

OMS Operating Maintenance Subsystem

OSI Open System Interconnection

OSS Operating & Support Subsystem

P

PA Power Amplifier

PACCH Packet Associated Control Channel

PAGCH Packet Access Granted Channel

PBCCH Packet Broadcast Control Channel

PCH Paging Channel

PCM Pulse Code Modulation

PCU Packet Control Unit

PDP Packet Date Protocol

PDTCH Packet Data Traffic Channel

PDU Packet Data Unit

PE Protective Earthing

PHY Physical Layer

PLL Phase Locked Loop

PLMN Public Land Mobile Network

PPCH Packet Paging Channel

PPP Point to Point Protocol

PS Packet Switch

PSN Packet Switch Network

PSPDN Packet Switched Public Data Network

PSTN Public Switching Telephone Network

Glossary


Glossary Full Name

PTP Point To Point

PVC Permanent Virtual Circuit

PWR Power Module

PWRD Power Distributor

PWRDB Power Distributor Backplane

Q

QoS Quality of Service

R

RACH Random Access Channel

RBID Rearboard of ID Interface

RCBU Resources Board Configuration Basal Unit

RCHB1 Rear Board 1 of CHUB

RCHB2 Rear Board 2 of CHUB

RCKG1 Rear Board 1 of CLKG

RCKG2 Rear Board 2 of CLKG

RDI Remote Defect Indication

RDTB Rear Board of DTB

RGER Rear Card of GE for BUSN and BGSN

RGIM1 Rear General Interface Module 1

RGUM1 Rear Board 1 of GUIM

RGUM2 Rear Board 2 of GUIM

RIP Routing Information Protocol

RLC Radio Link Control

RMPB Rear Board of OMP

RMNIC Rear Board of MNIC

RPU Route Protocol Process Unit

RR Radio Resource

RRU Remote Radio Unit

RS Regenerator Section

RSPB Rear Board of SPB

RSVB Rear Board of Server

RTU Radio Transceiver Unit

RUIM1 Rear Board 1 of UIM



S



Glossary Full Name

SACCH Slow Associated Control Channel

SAPI Service Access Point Indicator

SAR Segment And Reassemble

SBCX Single Board Computer of X86

SCCP Signal Connect Control Part

SD Signal Degrade

SDCCH Stand-Alone Dedicated Control Channel

SDH Synchronous Digital Hierarchy

SDTB Sonet Digital Trunk Board

SDTB2 Sonet Digital Trunk Board

SF Signal Fail

SIO Service Information Octet

SLC Signaling Link Code

SM SubMultiplexing

SMBUS System Management BUS

SMC Short Message Center

SMLC Serving Mobile Location Centre

SMS Short Message Service

SMU Subchannel Multiplexing Unit

SNTP Simple Network Time Protocol

SONET Synchronous Optical Network

SPB Signaling Processing Board

SPB2 Signaling Processing Board

SSM Subjoin Service Management

SSN SubSystem Number

SST Subsystem Status Test

STC Signalling Transfer Converter

STM-1 Synchronous Transfer Mode 1

SUA SCCP User Adaptation

SVR Server Board

SYNCLK Synchronous Clock

T

TBF Temporary Block Flow

TC TransCoder

TCB TCP Control Block

TCH Traffic Channel

Glossary


Glossary Full Name

TCP Transmission Control Protocol

TCU TransCoder Unit

TDM Time Division Multiplex

TEI Terminal Equipment Identification

TFI TDM Fiber Interface Board

TFO Tandem Free Operation

TIM Trace Identifier Mismatch

TPU Transceiver Process Unit

TRM Transceiver Module

TRX Transmitter & Receiver

TS Time Slot

TTL Transistor-Transistor Logic

TU Tributary Unit

U

UBPG UTCA Baseband Processing Board for GSM

UDP User Datagram Protocol

UID User Identifier

UIMC Universal Interface Module for Control plane（BCTC or BPSN）

UIMU Universal Interface Module for User plane

UNEQ Unequipped

UPPB User Plane Processing Board

UPU User Plane Process Unit

Um Um Interface

V

VLR Visitor Location Register

X

XP Executive Processor


Figures

Figure 1 CHUB Connection ................................................ 21

Figure 2 Fiber Connection Diagram .................................... 22

Figure 3 Fiber Optics Connection 2 ..................................... 23

Figure 4 Fiber Optics Connection 3 ..................................... 23

Tables

Table 1 Chapter Summary ...................................................i

Table 2 Typographical Conventions ...................................... ii

Table 3 Mouse Operation Conventions .................................. ii

Sjzl20092367-ZXWR RNC (V3.07.300) Alarm Handling Reference

Documents

Transcript of Sjzl20092367-ZXWR RNC (V3.07.300) Alarm Handling Reference