ZTE Media Gateway ZXC10

ZXC10 MGWcdma2000 Media Gateway

Alarm and Notification Information (1)

Version 2.04.20

ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: [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

Jan. 28, 2008 R1.0 sjzl20080260 First edition

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

Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057.

Thank you for your cooperation!

Document Name ZXC10 MGW cdma2000 Media Gateway Alarm and Notification Information (1)

Product Version V2.04.20 Document Revision Number R1.0

Serial No. sjzl20080260 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 Intended Audience ................................................................. i Prerequisite Skill and Knowledge .............................................. i What Is in This Manual ........................................................... i Related Documentation.......................................................... ii Conventions......................................................................... ii How to Get in Touch............................................................. iii

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

General Concept...............................................................1

Overview .............................................................................1 Alarms and Notifications Mechanism ........................................1 Alarm Handling Flow..............................................................1

Chapter 2.......................................................................... 3

Alarm Information...........................................................3

Overview .............................................................................3

Handling Error Alarms......................................................3

SMBUS Error ........................................................................3 The CSIX Receptivity Examination Error Surpasses the Threshold 4 Area Number from Database does not agree with the one in Bootcfg.ini ...........................................................................4 OMC MAC in Database does not agree with the one in bootcfg.ini.5 OMC IP in Database does not agree with the One in bootcfg.ini....5 MP Type in Database does not agree with the one in bootcfg.ini...5 Bootcfg.ini does not Exist .......................................................6 The Bit Error Rate in a Fiber High ............................................6 FE Reports Unacceptable Configuration Parameters (M size)........6 FE Reports Unacceptable Configuration Parameters (The Symmetry between Operation and Configuration) .....................................7

FE Reports Unacceptable Configuration Parameters (IMA agreement Version Number) .................................................. 8 FE Reports Unacceptable Configuration Parameters ................... 8 NE is in Config_Aborted State ................................................ 9 Persistence of Loss of IMA Frame Defect at the NE .................... 9 Persistence of Link out of Delay Synchronization Defect at the NE........................................................................................10 Persistence of an RDI-IMA Defect at the NE.............................10 APS Reset ..........................................................................11 L2FWDTBL Get DB Info Fail...................................................11 L2FWDTBL Get SCS Info Fail .................................................12 Resource Board can not Get L2fwd's Information from UIM Board........................................................................................12 Bureau Number does not agree with the one in bootcfg.ini ........13 MTP2 Link Sending Traffic Overload .......................................13 MTP2Link Receiving Traffic Overload ......................................13 MTP3 Link Congest ..............................................................14 UTS HOST Power Fail ...........................................................14 UTS HOST Request NPL2TAB Timeout ....................................14 SDH: Multiplex Section far End Receive Failure ........................15 UTS HOST Request Security Variable of Timeout ......................15 Connection Check Switch is Off .............................................16 SNTP Client can’t get the Network Clock .................................16 Cx29704 Status is ERR.........................................................16 Block or Unblock Office is not success ....................................16

Equipment Alarms......................................................... 17

OMP Config is Changed ........................................................17 Board’s ENUM Switch is ON...................................................17 Rare and Front Card Mismatch Error.......................................17 Port Link Breaks..................................................................18 Sub-card is Abnormal ..........................................................18 Phase Lock Loop is Unlocked.................................................18 The Bit Error Rate in E1 Link is High.......................................19 The Micro Code is Abnormal..................................................19 Link Level Flow Control can’t be Eliminated .............................20 All HSSLS are Out of Sync ....................................................20 Fibers Connect Error ............................................................21 Board does not Exist............................................................21 Clock Base Lost First Level (High) Alarm .................................22 Optical Module has no Light ..................................................22

SDH: Loss of Signal............................................................. 23 SDH: Loss of Frame ............................................................ 23 CPU Sub Card Is Active, But not Configured in the Database ..... 24 CPU Sub Card is Not Active, But Configured in Database........... 24 OMP Gate-Way IP in BootCfg.ini File is Different from DBs ........ 24 OMC Server IP in BootCfg.ini File is different from DBs ............. 25 Gate-Way Mask in BootCfg.ini File different from DBs............... 25 The State of Out Port is Down............................................... 26 Hard Disk Utilization Ratio Threshold Warning ......................... 26 The Board’s Hard Disk is Bad ................................................ 27 LVDS Signal Unlocked.......................................................... 27 FPGA is Abnormal ............................................................... 27 The Hard Disk’s Reliability Reduces........................................ 28 Far End is in Starting-up State .............................................. 28 FE is in Blocked State .......................................................... 28 FE is in Insufficient Links State ............................................. 29 FE Transmit Clock Mode is different than NE Transmit Clock Mode........................................................................................ 29 NE Group is in Insufficient Links State.................................... 30 Implementation Specific TX Fault Declared at the NE................ 30 FE TX is Mis-Connected........................................................ 31 Implementation Specific Rx Fault Declared at the NE................ 31 Implementation Specific Rx Failed Declared at the NE .............. 31 NE TX is Mis-Connected ....................................................... 32 FE TXLSM is in Unusable State .............................................. 32 APS Protection Channel Mismatch.......................................... 33 APS Protection Mode Mismatch ............................................. 33 CLKG 32M Output Clock Lost ................................................ 34 CLKG 32M8K Output Clock Lost............................................. 34 CLKG 16M Output Clock Lost ................................................ 34 CLKG 16M8K Output Clock Lost............................................. 34 CLKG PP2S Output Clock Lost ............................................... 35 CLKG PP2S Clock Base Lost .................................................. 35 CLKG Clock 16CHIP Base Lost............................................... 35 SDH: Multiplex Section Alarm Indication Signal ....................... 36 SDH: Signal Failure ............................................................. 36 SDH: AU-4 Pointer Lost ....................................................... 37 SDH: AU-4 Alarm Indication Signal........................................ 37 SDH: VC-4 Trace Identifier Mismatch..................................... 37

SDH: VC-4 Unequipped ........................................................38 SDH: VC-4 Channel Payload Mismatches.................................38 SDH: TU-12 Loss of Multi-frame ............................................38 HP_SF ...............................................................................39 CPU Rate is Over Threshold ..................................................39 Flash Device Initialize Failed .................................................39 Media Port is Abnormal ........................................................40 Alarm RSMM HW Loop Error..................................................40 Input Clock Abnormal ..........................................................41 Communicate Link of PWRD 485 Broken .................................41 Clock Base Lost Second Level (Middle) Alarm ..........................42 OSS Communication Link Off ................................................42 Alarm of Office not Access from MTP3 ....................................43 Cluster Not Access...............................................................43 Alarm of Office not Access from M3UA....................................44 Cannot Reach the Office .......................................................45 Association Broken Down .....................................................45 8k Input Clock Lose .............................................................46 16M Input Clock Lose...........................................................46 PP2S Input Clock Lose .........................................................46 32M Clock Lost in TSNB........................................................47 Phase Lock Loop Work Mode is Abnormal ................................47 The Channel in the Sub-card is Abnormal................................48 Recive Bad Packets..............................................................48 PVC Fault ...........................................................................49 SDH: Signal Degrade ...........................................................49 SDH: VC-4 Far End Receive Failure ........................................50 HP_SD...............................................................................50 GE Link Error ......................................................................51 The DB Config does not Inconsistent with the Hardware Equipment........................................................................................51 Clock Base Lost Third Level (Low) Alarm.................................52 SCCP SSN is Invalid.............................................................52 SSCS Congest.....................................................................52 SSCS Overloaded ................................................................53 Alarm of Link Unavailability...................................................53 SUA Subsystem is Invalid .....................................................54 M2PA Link is Broken ............................................................54 Association is Congestive......................................................55

Trunk Frame Lose ............................................................... 55 Trunk Signal Lose ............................................................... 56 Trunk Alarm Indication ........................................................ 56 Trunk Multi-frame Lose........................................................ 56 Trunk Receive far End CRC Multiframe Alarm Indication............ 57 Trunk Receive Far End Alarm................................................ 57 Cell Delimiter cannot Synchronize ......................................... 57 Cell Delimiter Lose .............................................................. 58 SDH: TU-12 Loss of Pointer .................................................. 58 SDH: TU-12 Alarm Indication Signal ...................................... 58 SDH:TU-12 Remote Defect Indication .................................... 59 SDH: TU-12 Remote Failure Indication ................................... 59 SDH: TU-12 Trace Identifier Mismatch ................................... 60 SDH: TU-12 Unequipped ...................................................... 60 SDH: TU-12 Payload Mismatch.............................................. 61 The HDLC is Unusable.......................................................... 61 The UID Bind is Unusable..................................................... 62 MAC Address of the board Conflicts ....................................... 62 DSP over Load High Alarm ................................................... 63 DSP over Load Middle Alarm................................................. 63 DSP over Load Low Alarm .................................................... 63 Tone Resource Board DSP Tone Type Differ ............................ 63 Error Connection on 129ts of T-net board ............................... 64 Loop Error of LVDS 129 time slot .......................................... 64 Dual Attribution Office has been Blocked ................................ 64 Dual Attribution Link has been Blocked................................... 65 Dual Attribution Association has been Blocked......................... 65 8K, 16M Input Clock no Match .............................................. 65 BOOT/EPLD Upgrade Information .......................................... 66 BOOT Version Synchronization Information............................. 66 Powing Error of SETS........................................................... 66 Spending of DSP has Reached a Dangerous Degree ................. 66 The BFD Session is Down ..................................................... 67 This Trunk is Used to CSU Test ............................................. 67 VC_4 Far End Error Indication............................................... 67 High Order Signal failure...................................................... 68 A Class Error of SETS .......................................................... 68 B Class Error of SETS .......................................................... 68 TRUNK Link Error ................................................................ 68

MP PROC INST ERROR .........................................................69 TRUNK Port Down ...............................................................69 OSS Check out that IP&MAC Address of the Board Bonflicts .......69 DSP Automatic Check Abnormal ............................................70 Function Epld Version Update Fail ..........................................70 E3S Sub-card Receive Alarm Signal Indication .........................70 Remote Error Indication .......................................................71 FE RX LSM can't turn to Active State ......................................71 Associate Path Break ...........................................................71 STC Office Unaccess ............................................................71 STC Office Congest..............................................................72 Abis Link Down ...................................................................72 The Communication Flow over Alarmed Threshold Value ...........72 Ctrl Port to UIM Error...........................................................73 Input Clock of Subcard is Lost ...............................................73 2350 Receive Rardware Error................................................73 FE RXLSM is in Unusable State ..............................................73 SCCP Connect ID Less than1000............................................74

Communication Alarms .................................................. 74 PPP_UID Link Down .............................................................74 PPP Link Down ....................................................................75 Internet Port Physical Link Off ...............................................75 The Communication between the Master and Slaver is Interrupted........................................................................................76 IUA Association is Broken .....................................................76 The Link between NE And Server Breaks.................................77 Communication between MP and OMP Error ............................77

Qos Alarms .................................................................. 77 INLP Fails to Request SCTP's Load Balancing Table...................78 Expired Password Alarm .......................................................78 Expired Password Notify .......................................................78

Environment Alarms ...................................................... 78

CPU Temperature over Threshold...........................................79 Rack Temperature Higher than Higher Threshold .....................79 Rack Temperature is Lower than Low Threshold.......................80 House Temperature is Higher than High Threshold ...................80 House Temperature is Lower than Low Threshold.....................80 Voltage is Higher than High Threshold ....................................81 Voltage is Lower than Low Threshold......................................81

Humidity is Higher than High Threshold.................................. 82 Humidity is Lower than Low Threshold ................................... 82 Fan is Lower than Low Threshold........................................... 83 Alarm Because Of Door........................................................ 83 Alarm because of Fume ....................................................... 83 Alarm because of Infrared .................................................... 83 Alarm because of Thunder.................................................... 84 Inner Media VLAN Communication Abnormal........................... 84 E3S sub-card Transmitter Direction Loss of Signal ................... 84 E3S Sub-card Receive Direction Loss of Signal ........................ 85 Out of Frame...................................................................... 85 Port not Work on the Configured Mode ................................... 86

Appendix A.....................................................................87

Abbreviations.................................................................87

Appendix B.....................................................................93

Collection of Alarm Information....................................93

Tables...........................................................................103

Index............................................................................105


Confidential and Proprietary Information of ZTE CORPORATION i

About This Manual

Purpose

This manual provides alarm and notification information of ZXC10 MGW cdma2000 Media Gateway.

Intended Audience

This manual is intended for engineers and technicians who perform operations on ZXC10 MGW cdma2000 Media Gateway.

Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding of wireless communication technologies. Familiarity with the following is helpful:

ZXC10 MGW system and its various components

User interfaces of ZXC10 MGW

Local operating procedures

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, General Concept

Introduces mechanism and general flow for handling alarms.

Chapter 2, Alarm Information

Provides alarm information about the daily occurring alarms of MGW, including alarm code, alarm name, alarm level, etc.

ZXC10 MGW cdma2000 Media Gateway Alarm and Notification Information (1)

ii Confidential and Proprietary Information of ZTE CORPORATION

Related Documentation

The following documentation is related to this manual:

ZXC10 MGW cdma2000 Media Gateway System Description

ZXC10 MGW cdma2000 Media Gateway User Guide

ZXC10 MGW cdma2000 Media Gateway Operating Instruction

ZXC10 MGW cdma2000 Media Gateway Alarm Monitoring

ZXC10 MGW cdma2000 Media Gateway Configuration

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.

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 and (86) 800-9830-9830.

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

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

General Concept

Overview

Alarm management system implements centralized monitoring on the running status of the whole system. The system collects real time abnormal information of each board, link, database, server, and other necessary units. When an alarm occurs, the alarm management system informs the maintenance engineer about the occurred alarm information in real time. So it is easy for the engineers to locate and recover the faults to ensure the stability of the system.

Alarms and Notifications Mechanism

An alarm occurs when there is a fault or abnormal event. Alarm system monitors the entire system. When any part of the system has a fault the alarm service process of the foreground server sends messages to OMC server. Thus generates alarm information.

A notification is originated against an event that does not directly effects. Notification information occurs during the daily running of the system to prompt the maintenance personnel of the system running status information. Notification information refers to unrepeatable or transient events occurring during running of the system and is displayed by OMC. The maintenance personnel can grasp the running status of each part of the system with the help of the information. Notification stands for occurrence of an event, but not potential danger. Besides, notification information needs no subsequent restore.

Alarm Handling Flow

Alarm management system implements centralized monitoring on the running status of the whole system. An alarm is given

Description

Description

Description


2 Confidential and Proprietary Information of ZTE CORPORATION

when part of the system is abnormal. Alarm level indicates the level of the alarm. Alarm information is prompting information displayed by OMC when the system has troubles or faults during running, usually lasts for a time period and disappears after the trouble shooting. If there is alarm, conduct troubleshooting in time to clear the alarm, otherwise, the result may be critical.

Alarm information can be classified into four levels according to the severity:

Level 1, Critical

Level 2, Major

Level 3, Minor

Level 4, Warning

Take different measures to handle alarms of different levels. When critical and major alarm information occurs, notify the local office of ZTE Corporation at once and handle the fault according to the instruction of the engineers from ZTE Corporation. When minor and warning alarm information occurs, the maintenance personnel in equipment room should record the fault phenomenon, and handle the fault according to the methods provided in this manual. Notify the local office of ZTE Corporation if the fault can not be handled.

Generally, alarms are cleared according to the following flow:

1. Confirm the alarm code, alarm level, description and involved parts.

2. Estimate the cause for the alarm and effect on the system.

3. Decide the handling method according to the result of the two steps above.

4. Handle the alarm.

Alarm Level

Steps


C h a p t e r 2

Alarm Information

Overview

Alarm information is divided into the following classifications:

Handling error alarm information

Device alarm information

Communication alarm information

Service quality alarm information

Environment alarm information

A collection of alarm information listed in ascending sequence of alarm codes is provided in “Appendix B Collection of Alarm Information”at the end of manual.

Handling Error Alarms This section introduces alarms related to handling error.

SMBUS Error

The alarm information includes:

Alarm code: 5636

Default level: Critical

Alarm description: SMBUS has error.

Resetting boards before reading and writing time sequence may cause this alarm.

While booting MPX86 board and running the version through setting BIOS when SMBUS is invalid, the temperature of the board may not be truly tested. Then the board may run at very

Description

Description

Alarm Information

Cause

Influence



high temperature without being observed. Moreover, in the invalid SMBUS, the memory size is configured based on default rule and may be inconsistent with the real configuration.

Pull out and insert the board or replace it.

The alarm disappears.

The CSIX Receptivity Examination Error Surpasses the Threshold


Alarm code: 15873


Alarm description: CSIX receptivity examination error surpasses the threshold.

CSIX receptivity examination error surpasses the threshold.

Handle this fault referring to the following actions:

Automatically restart the board.

If the board is successively restarted automatically, and there is alarm for receptivity examination error, plug out and then plug in the board.

If the fault still exists after extracting the board, exchange the board.

The alarm disappears.

Area Number from Database does not agree with the one in Bootcfg.ini

Alarm information has the following content:

Alarm code: 5384

Default level: Major

Alarm description: Alarm due to the area code inconsistency.

The system can not start normally.

The area code exported from the database is inconsistent with that read from “bootcfg.ini”.

Restart the board.

The alarm is eliminated.

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Chapter 2 Alarm Information


OMC MAC in Database does not agree with the one in bootcfg.ini


Alarm code: 5385


Alarm description: The OMP generates this alarm because the MAC address of the background OMP is inconsistent.


The MAC address of the background OMP read from the database is inconsistent with that read from “bootcfg.ini”.

Restart the board.


OMC IP in Database does not agree with the One in bootcfg.ini


Alarm code: 5386


Alarm description: The OMP generates this alarm because the IP address of the background OMP is inconsistent.


The IP address of the background OMP read from the database is inconsistent with that read from “bootcfg.ini”, which does not frequently happen.

Restart the board.


MP Type in Database does not agree with the one in bootcfg.ini


Alarm code: 5387


Alarm description: The OMP generates this alarm because the MP type is inconsistent.

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information




The MP type read from the database is inconsistent with that read from the “bootcfg.ini” file, which does not happen frequently.

Restart the board.


Bootcfg.ini does not Exist


Alarm code: 5388


Alarm description: The “Bootcfg.ini” startup file does not exist.


The “Bootcfg.ini” startup file does not exist, which does not happen frequently.

Restart the board (If the version is the DEBUG version, it is required to manually set the MP type before restarting the board; if the version is the RELEASE version, then the file is corrupted.)


The Bit Error Rate in a Fiber High


Alarm Code: 5639

Alarm Level: Major

Alarm description: The error rate at the optical port is high.

The error rate at the optical port is high.

Check whether the optical fiber is inserted correctly and whether it is damaged.


FE Reports Unacceptable Configuration Parameters (M size)


Alarm code: 19201

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information




Alarm description: The remote IMA group enters into the status of configuration failure because the local end refuses to participate in negotiable parameter’s (frame length) configuration.

The physical link on IU port can not be established.

The alarm occurs when the local IMA group receives the report of “the remote IMA group being in the configuration failure status”. IMA group enters into this status because the local end refuses to configure the frame length.

Check whether the frame length configurations at both the local group and the remote group are consistent.


FE Reports Unacceptable Configuration Parameters (The Symmetry between Operation and Configuration)


Alarm code: 19202


Alarm description: The remote IMA group enters into the status of configuration failure because the local end refuses to participate in the negotiable parameter (symmetry of configuration and operation) configuration.


The alarm occurs when the local IMA group receives the report of “the remote IMA group being in the configuration failure status”. IMA group enters into this status because the local end refuses to configure the symmetry-related parameters.

Check whether the group symmetry-related parameters at the remote group are correctly configured.


Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



FE Reports Unacceptable Configuration Parameters (IMA agreement Version Number)

Alarm information has the following contents:

Alarm code: 19203


Alarm description: The remote IMA group enters into the status of configuration failure because the local end refuses to participate in the negotiable parameter (IMA protocol version number) configuration.


The alarm occurs when the local IMA group receives the report of “the remote IMA group being in the configuration failure status”. IMA group enters into this status because the local end refuses to configure the IMA protocol version number.

Check whether the protocol version parameters at both the local group and the remote group are correctly configured.


FE Reports Unacceptable Configuration Parameters


Alarm code: 19204


Alarm description: The remote IMA group enters into the status of configuration failure because the local end refuses to participate in the negotiable parameter configuration (other reasons).


The alarm occurs when the local IMA group receives the report of “the remote IMA group being in the configuration failure status”. IMA group enters into this status because the local end refuses to participate in the negotiable parameter configuration.

Check whether the parameters at both the local group and the remote group are correctly configured.


Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



NE is in Config_Aborted State


Alarm code: 19207


Alarm description: The local IMA group enters into the status of configuration failure because the remote IMA group refuses to participate in the Config_Aborted State negotiable parameter configuration.


Invalid configuration of remote IMA group parameters causes that the local IMA group to enter into the Config_Aborted status.

Check whether the parameters at both the local IMA group and the remote IMA group are correctly configured.


Persistence of Loss of IMA Frame Defect at the NE


Alarm code: 19213


Alarm description: The local receiving link loses the IMA frame.


Fault in the E1 physical connection causes the loss of the IMA frame.

Handle the fault referring to the followings:

Check whether the E1 link is connected with the corresponding remote link to avoid errors in the connection sequence of the E1 link.

If the onsite environment causes the loss of the IMA frame, but the alarm automatically disappears.

The alarm is eliminated, and the system works normally.

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



Persistence of Link out of Delay Synchronization Defect at the NE


Alarm code: 19214


Alarm description: The delay synchronization signal of the local receiving link is lost.


The alarm occurs on the link when the delay synchronization signal of the local receiving link is lost.

Check whether the access clock of the IMAB works normally and whether the RUN indicator on the clock board of the corresponding NE is green and flashes slowly.


Persistence of an RDI-IMA Defect at the NE


Alarm code: 19215


Alarm description: The alarm occurs when the local receiving link receives the remote failure indication.


The causes for this alarm may include the followings:

If the ICP cell received by the local receiving link from the remote end contains “remote failure indication”, the alarm occurs at the local end.

The alarm indicates that the remote receiving link connected with the local end is in LIF and LODS.

Handle the alarm referring to the followings:

Check the working status of the remote receiving link by using the DDM dynamic management tool of the background to make sure it is active.

The alarm caused by the reliability problem of the chip automatically disappears.


Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



APS Reset


Alarm code: 19714


Alarm description: APS resets the board (there is resolute character string in alarm source).

There may be two causes for this alarm:

The boards are configured to be active and standby, but APS is not configured.

It fails to open FE or HW.

The service is interrupted.

Handle this fault according to the causes:

Configure APS.

Exchange the board.

The alarm disappears, and the system works normally.

L2FWDTBL Get DB Info Fail


Alarm code: 19968


Alarm description: There is no response to the request of Level 2 forwarding table from database.


OMP is not powered on normally.

The control plane messages are delayed.

Level 2 forwarding table can not be generated.

Handle this fault referring to the following operations:

Ensure UIM and OMP are powered on normally.

Use relevant tools to test whether the control plane between UIM and OMP is reachable.

The alarm disappears, and the system works normally

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification



L2FWDTBL Get SCS Info Fail


Alarm code: 19969


Alarm description: There is no response while retrieving Level 2 forwarding table port information from the system.


The system control process on UIM is not normally powered on.

Number of IP addresses configured for the subunits of one shelf surpasses the maximum value (200).

Level 2 forwarding table can no be generated.

Handle this fault referring to the followings:

Ensure the system control process on UIM is normally powered on.

Ensure the number of IP addresses of all subunits is less than 200.


Resource Board can not Get L2fwd's Information from UIM Board


Alarm code: 19970


Alarm description: The resource board can not acquire information of Level 2 forwarding table from UIM.

There may be three causes for this alarm:

UIM is not normally powered on.

Level 2 forwarding table is not generated on UIM.

Messages can not be sent to the control plane.

The resource board can not get the Level 2 forwarding table.

Handle this fault referring to the followings:

Ensure that UIM is normally powered on.

If there is no Level 2 forwarding table on UIM, but there is alarm L2FWDTBL get DB info fail or L2FWDTBL get SCS info fail. Clear the alarm referring to the two topics immediately prior to this topic.

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Influence

Handling



If there is no alarm information, check whether the shelf with UIM is BUSN. Note that Level 2 forwarding table can be generated only when UIM is in BUSN shelf.

Use relevant tool to test whether the control plane between UIM and OMP is reachable, ensuring it reachable.


Bureau Number does not agree with the one in bootcfg.ini

The alarm information has the following content:

Alarm code: 5383


Alarm description: Alarm occurs due to the inconsistent office number.


The office number exported from the OMP database is inconsistent with that previously saved on OMP.

Restart the OMP board.


MTP2 Link Sending Traffic Overload

The alarm information has the following contents:

Alarm code: 8399872


Alarm description: Alarm is generated due to the traffic overload on the MTP2 link.

The sent traffic overload on the link of the local end is caused by the service message flow control. The alarm severity level 1 is the highest and level 4 is the lowest.

Reduce the sent load of the local end.


MTP2Link Receiving Traffic Overload

The alarm information has the following content:

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information



Alarm code: 8399873


Alarm description: Alarm due to received traffic overload on the MTP2 link.

The received traffic overload on the link of the local end is caused by the service message flow control of the opposite end. The alarm severity level 1 is the highest and level 4 is the lowest.

Reduce the sent load of the remote end.


MTP3 Link Congest

The alarm information has the following contents:

Alarm code: 8400131


Alarm description: MTP3 link congestion.

It may delay the response time of subscribers’ services.

The link is congested. The percent of the buffer occupied by the service messages sent from mtp3 to mtp2 reaches the threshold.

Reduce the service message flow at the local end.


UTS HOST Power Fail


Alarm code: 25166848


Alarm description: Powering on HOST process fails.

HOST process can not be powered on.

If system running abnormally, contact maintenance personnel of ZTE Corporation.


UTS HOST Request NPL2TAB Timeout


Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information



Alarm code: 25166849.


Alarm description: Requesting Level 2 forwarding table during powering on VTCD is timeout.

Requesting Level 2 forwarding table during powering on VTCD is timeout.

Please contact maintenance personnel of ZTE Corporation.


SDH: Multiplex Section far End Receive Failure


Alarm code: 1796

Default level: Minor

Alarm description: SDH: multiplexing section far end receiving failure (MSFERF).

When a network node (such as the regenerator) of the multiplexing section where the board is located detects any fault in the uplink direction of its downstream equipment, it will all send 1 in the uplink (ADM direction) multiplexing section. When the ADM detects MS AIS, it will send MS RDI remote alarm in the downlink direction.

Eliminate “original fault” according to the alarm generated by the network node equipment of multiplexing section where the board is located.


UTS HOST Request Security Variable of Timeout

Alarm information has the followings:



Alarm description: Security variable request during powering on VTCD is timeout.

During powering on VTCD, security variable request is timeout.

Check OMP.


Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



Connection Check Switch is Off


Alarm code: 25600

Default level: Warning

Alarm description: connection check with board is turned off.

Connection check on board is turned off, so connection check cannot be done.

Sometimes, the connection can not be self-restored.

Restore the connection in proper time.


SNTP Client can’t get the Network Clock


Alarm code: 8392705


Alarm Description: SNTP client fails to get the network clock.

SNTP client fails to get the network clock.

Check whether the SNTP server exists.

Cx29704 Status is ERR


Alarm code: 6400


The Status of Cx29704 is ERR.

The Status of Cx29704 is ERR.

Change another chip.

Block or Unblock Office is not success



Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information




Alarm Description Block or unblock office is not success.

Block/unblock office is failed.

Please check whether the office has been manual block.

Equipment Alarms This section introduces alarms related to equipment.

OMP Config is Changed

Alarm information has to the following contents:

Alarm code: 5394


Alarm description: The OMP configuration is changed.

Otherwise, the system can not run normally.

The OMP configuration is changed, and it is necessary to perform manual reset. For example, if the configuration type of OMP is changed, it is necessary to manually reset the OMP.

The OMP is needed to be reset. Manually reset the OMP again.


Board’s ENUM Switch is ON


Alarm code: 5635


Alarm description: ENUM switch of the broad is turned on.

ENUM switch of the broad is turned on.

Turn off the ENUM switch of the broad.


Rare and Front Card Mismatch Error


Alarm code: 5637

Cause

Handling

Description

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information




Alarm description: Error in the back board that mismatches with the front board.

The back board mismatches with the front board.

Replace the back board with one that matching with the front board, or pull out the back board if not needed.


Port Link Breaks


Alarm code: 5641


Alarm description: Port link breaks and causes alarm.

Chip lan91 or bcm5328 has fault.

Call loss is increased.

Reset the correspondent DSP chip or the board through background tool.


Sub-card is Abnormal


Alarm code: 5645


Alarm description: Sub-card is abnormal.

Sub-card is abnormal.

Check the connection status of the sub-card or replace it with another sub-card.


Phase Lock Loop is Unlocked

Alarm information has to the following contents:

Alarm code: 5646


Alarm description: The phase-locked loop is unlocked.

Cause

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information



The phase-locked loop is unlocked.

Check the phase-locked loop of the board. The alarm occurs maybe due to the hardware fault.


The Bit Error Rate in E1 Link is High


Alarm code: 5647


Alarm description: The bit error rate in E1 link is high.

E１ link or uplink device has fault.

The trunk is interrupted in receiving trunk signals.


Check there is fault with the trunk link of the local end.

Check there is other device fault in the upward trunk link.


The Micro Code is Abnormal


Alarm code: 15360.


Alarm description: The micro code is abnormal

The causes leading this alarm include:

Micro code program falls into endless loop.

Micro engine hardware failure has caused this alarm

The board can not receive and send messages.


Restart the board..

If the board successively restarts automatically, and still there is and alarm about micro code, plug out and then plug in the board.

If the fault still exists, exchange the board.


Cause

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification



Link Level Flow Control can’t be Eliminated


Alarm code: 15874.


Alarm description: The link level flow control is unable to eliminate.

The link level flow control is unable to eliminate.

The board can not receive and send messages.

Handle the fault referring the followings:

Restart the board.

If the board successively restarts automatically, and still there is a link level flow control alarm, check whether PSN is abnormal.

If PSN is normal, plug out and then plug in the board.

If the fault still exists, exchange the board.


All HSSLS are Out of Sync


Alarm code: 19456.


Alarm description: All HSSLS are out of sync.

The causes for this alarm may include:

872 chip have fault if out of synchronization is with PSN high speed serial link

882 chip on PSN have fault.

PSN board have fault.

Some board may completely fail to work. If the alarm is caused by PSN fault, the whole service is interrupted.

Check whether the PSN board is correctly configured and normally powered on. If both are normal, restart the board.


Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification



Fibers Connect Error


Alarm code: 5120


Alarm description: The fiber cables are not properly connected.

The fiber connection between the UIM and the TFI is inconsistent with the optical interface configured in the background.

Reconnect fibers, or reset DB.


Board does not Exist


Alarm code: 5379


Alarm description: The board is not in the position, or the CPU is in the reset status for a long time.

The board in the slot or the CPU on it runs abnormally.

The causes leading to the alarm may include:

The board configured in the database is not in the position.

A fault occurs after resetting the board.

The TDM connection chip has exceptions.

The UIM end connection has exceptions.

The Healthy hardware pin of this slot on the backboard is destroyed.


Plug the configured board into the slot.

Manually reset the board through the background.

Unplug and plug the board again, or check whether the pin of this slot is destroyed.


Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



Clock Base Lost First Level (High) Alarm


Alarm code: 26129


Alarm description: Level-1 alarm due to the loss of the Clock Base source.

The Clock Base has been lost for more than 24 hours.

Check the access reference of the CLKG board (through the CLKG back board).


Optical Module has no Light


Alarm code: 2


Alarm description: The optical module has no light.

The associated communication link is broken.


The receiving fiber (RX) of the local end or the sending fiber (TX) of the opposite end is not connected properly.

The optical module of the local end or the opposite end is faulty.


Check whether the fibers of the local end and the opposite end are properly connected.

If the alarm still exists replace the fibers.

If the alarm still exists after replacing the fibers, replace the optical module of the local end; if the alarm still exists, replace the optical module of the opposite end.

The alarm is eliminated, this optical module and the link works normally.

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



SDH: Loss of Signal


Alarm code: 1792


Alarm description: SDH: Loss of Signal (LOS).


The optical signal generation equipment is faulty

The optical fiber transmission line is faulty

The tail fiber and the flange between the local-end ODF and the equipment are faulty

The local-end optical receiver is faulty.


Check the opposite-end SDH sending equipment

Check the optical fiber transmission line

Check the local-end optical fiber connection

Check the local-end optical receiver

If it is confirmed that the local-end optical receiver is faulty, it is required to replace the board.


SDH: Loss of Frame


Alarm code: 1793


Alarm description: SDH: Loss of Frame (LOF).

LOF can have following reasons:

LOF occurs due to LOS,

SDH transmission equipment is faulty.

Note: When A1A2 frame location signal cannot be correctly received for 3ms, LOF occurs.

Check whether LOS occurs and whether the SDH transmission equipment is faulty. Invite the equipment maintenance personnel to check the SDH transmission equipment.


Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



CPU Sub Card Is Active, But not Configured in the Database


Alarm code: 5389


Alarm description: The (CPU) sub-card is in position, but the database is not configured.

A (CPU) sub card is online, but is not configured in database. The host CPU of the board will check it and alarm. The alarm will not appear frequently.

Pull out the sub-card where the alarm occurs.


CPU Sub Card is Not Active, But Configured in Database


Alarm code: 5390


Alarm description: The database is configured with the CPU sub-card, but the sub-card is not in position.

The database is configured with the CPU sub-card, but the sub-card is not in its proper position. The alarm is detected and reported by the active CPU of the board.

Plug the configured CPU sub-card into its position.


OMP Gate-Way IP in BootCfg.ini File is Different from DBs


Alarm code: 5391


Alarm description: The IP address of the gateway of the OMP in the “BootCfg.ini” file is inconsistent with that configured in the database.


Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence



The IP address of the gateway of the OMP read from the database is inconsistent with that read from the “bootcfg.ini”.

Restart the board.


OMC Server IP in BootCfg.ini File is different from DBs


Alarm code: 5392


Alarm description: The IP address of the OMC Server in the “BootCfg.ini” file is inconsistent with that configured in the database.


The IP address of the OMC Server read from the database is inconsistent with that read from the “bootcfg.ini” file.

Restart the board.


Gate-Way Mask in BootCfg.ini File different from DBs


Alarm code: 5393


Alarm description: The mask of the gateway in the “BootCfg.ini” file is inconsistent with that configured in the database.


The mask of the OMC gateway read from the database is inconsistent with that read from the “bootcfg.ini” file.

Restart the board.


Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



The State of Out Port is Down


Alarm code: 5395


Alarm description: The external port of the board is down.

Data can not be transmitted.

Causes leading to the alarm may include:

The network port at the local end is faulty.

The switch at the opposite end is faulty.

The middle connection line is faulty.


Check whether the network port at the local end is faulty (by using SCSShowCTData).

Check whether the switch at the opposite end runs normally (by checking the flashing indicator of the network port on the switch), and whether the corresponding port is broken.

Check whether the connection between the two ends is broken.


Hard Disk Utilization Ratio Threshold Warning


Alarm code: 5632


Alarm description: The hard disk is full.

Data may be lost.

The usage rate of the hard disk exceeds the threshold of one level.

Switch the board.


Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



The Board’s Hard Disk is Bad


Alarm code: 5633


Alarm description: The hard disk of the board is broken.

The hard disk of the board is broken.

Replace the hard disk of the board.


The alarm may cause data loss.

LVDS Signal Unlocked


Alarm code: 5638


Alarm description: LVDS signal is unlocked.

LVDS signal is unlocked.

Detect whether the LVDS signal cable on the backboard is unblocked. Block this signal cable.


FPGA is Abnormal


Alarm code: 5640


Alarm description: FPGA is abnormal.

FPGA loses and correct verification can not be found.

The board works abnormally.

Restart the board.


Alarm Information

Cause

Handling

Verification

Precautions

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification



The Hard Disk’s Reliability Reduces


Alarm code: 5642


Alarm description: Reliability of hard disk is degraded.

If the error rate, starting/stopping times, seek error rate, power-on time, GSense error rate, power off retract count, reallocated sector event count, currently to-be-determined sector count, offline and irretrievable sector count, and Ultra ATA CRC error rate cause this alarm.

The data loses or the system goes down.

Save the attached information of the alarm, and then exchange the hard disk.


Far End is in Starting-up State


Alarm code: 19200


Alarm description: The remote IMA group connected with the local IMA group is in the startup status.


The alarm occurs when the local IMA group receives the report of “the remote IMA group status machine being in the startup status”.

Check whether the UIM/DTB connection, the clock and the trunk cable connection are correct, and confirm that the IMA equipment at the opposite end runs normally.


FE is in Blocked State


Alarm code: 19205


Alarm description: The remote IMA group connected with the local IMA group is in the blocking status.

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information




The alarm occurs when the local IMA group receives the report of “the remote IMA group status machine being in the blocking status”.

Check the status of the remote IMA group.


FE is in Insufficient Links State


Alarm code: 19206


Alarm description: The remote IMA group connected with the local IMA group is in the status of having insufficient links.


The alarm occurs when the local IMA group receives the report of “the remote IMA group status machine being in the status of having insufficient links”.

Check the statuses of the links in the remote IMA group to confirm that the number of active links is greater than or equal to the configured minimum number of activated links.


FE Transmit Clock Mode is different than NE Transmit Clock Mode


Alarm code: 19208


Alarm description: Mismatch between the clock mode sent by the remote IMA group and that sent by the local IMA group.


The clock mode sent by the remote IMA group through the ICP cell mismatches with that sent by the local IMA group.

Check the related configuration of the clock mode of the remote end or the local end to make the clock modes at the two ends match with each other.

The alarm is eliminated, and the system works normally

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



NE Group is in Insufficient Links State


Alarm code: 19209


Alarm description: The links in the local IMA group are insufficient.


The number of links in the “ACTIVE” status at the local end does not reach the minimum number of sending/receiving links set by the user.

Handle the alarm referring to the followings:

The alarm automatically disappears when the number of links in the “ACTIVE” status in the corresponding group exceeds or equals the minimum number of sending/receiving links configured in the group.

Checks whether the number of links configured in the group are more than the required links.


Implementation Specific TX Fault Declared at the NE


Alarm code: 19211


Alarm description: Fault in the local sending link, which is generally caused by the equipment.


In general, the IMA equipment fault causes the fault in the local sending link.

Check whether the IMA chip works normally and the E1 cable connection.


Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



FE TX is Mis-Connected


Alarm code: 19212


Alarm description: The local sending link is broken.


The alarm occurs when a sending link in the group is not connected to the remote IMA group as others are.

Check whether the IMA chip works normally and make sure each link connected to the remote IMA group.


Implementation Specific Rx Fault Declared at the NE


Alarm code: 19216


Alarm description: The local receiving link is faulty.


The local receiving link is faulty.

Check the IMA chip works normally, and make sure each link can be normally connected to the local IMA group.


Implementation Specific Rx Failed Declared at the NE


Alarm code: 19217


Alarm description: The local receiving link is disabled.


The local receiving link is disabled.

It can automatically recover to normal status.

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling




NE TX is Mis-Connected


Alarm code: 19218


Alarm description: The local receiving link is broken.


The alarm occurs when a receiving link in the group is not connected to the remote IMA group as others are.

Check the connection conditions of each receiving link at both the local end and the remote end to make sure that each receiving link is connected to the local IMA group. Check the specified local E1 link is connected with the corresponding remote E1 link.


FE TXLSM is in Unusable State


Alarm code: 19219


Alarm description: The far-end sending link connected with the local end is unusable.

The physical link on Iu port can not be established.


A sending link at the remote end is faulty, so it is changed to the “Unusable” status from the “ACITIVE” status.

The link enters into the “Unusable” status after the link is just enabled.

Handle the fault according to different causes:

The alarm automatically disappears in case that the link enters into the “Unusable” status after the link is just enabled.

For the alarm caused by the fault in the remote sending link, check whether the IMA link configuration such as scrambling code and direction at the remote end matches with that at the local end.

Check the E1 cable is loosed.

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling




APS Protection Channel Mismatch


Alarm code: 19712


Alarm description: Mismatch of the automatic protection switchover channel

The APS may not function.

The services at the two ends are not transmitted on the same optical fiber.


Use the man-machine command on the background to switch the service on one end from one optical fiber to the other one.

If the switchover cannot be performed through the man-machine command, it is necessary to pull out and plug the optical fiber to implement the APS switchover at one end.

If the step 2 fails, it is required to reset the board.


APS Protection Mode Mismatch


Alarm code: 19713


Alarm description: Mismatch of the automatic protection switchover mode

The APS may not function.

The protection types at the two ends are inconsistent. The protection type at one end is 1+1, and that at the other end is 1: n.

Modify the protection types to make them consistent at the two ends.


Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



CLKG 32M Output Clock Lost


Alarm code: 26112


Alarm description: The 32M output clock is lost.

The 32M output clock of the CLKG board is lost.

Check (measure) the output clock of the CLKG board. If the output clock is exceptional, replace the CLKG board.


CLKG 32M8K Output Clock Lost


Alarm code: 26113


Alarm description: The 32M8K output clock is lost.

The 32M8K output clock of the CLKG board is lost.



CLKG 16M Output Clock Lost


Alarm code: 26114


Alarm description: The 16M output clock is lost.

The 16M output clock of the CLKG board is lost.

Check the CLKG board and the software.


CLKG 16M8K Output Clock Lost


Alarm code: 26115

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information




Alarm description: The 16M8K output clock is lost.

The 16M8K output clock of the CLKG board is lost.



CLKG PP2S Output Clock Lost


Alarm code: 26116


Alarm description: The CLKG PP2S output clock is lost.

The CLKG PP2S output clock is lost.

Check (measure) the output clock on the CLKG. If the output clock is exceptional, replace the CLKG board.


CLKG PP2S Clock Base Lost


Alarm code: 26117


Alarm description: The PP2S Clock Base is lost.

The CLKG PP2S input clock is lost.

Check there is any input in the CLKG PP2S, and whether the connection line is correct.


CLKG Clock 16CHIP Base Lost


Alarm code: 26118


Alarm description: The 16CHIP Clock Base is lost.

The CLKG 16CHIP input clock is lost.

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause



Check there is any input in the CLKG 16CHIP, and whether the connection line is correct.


SDH: Multiplex Section Alarm Indication Signal


Alarm code: 1795


Alarm description: SDH: Multiplexing Section Alarm Indication Signal (MSAIS).

When a network node of the multiplexing section has any fault in its upstream equipment, it all send 1 in the downlink (board direction) multiplexing section. The faults in the upstream equipment include LOS, LOF and RS TIM.

Eliminate “original fault” according to the alarm generated by the network node equipment of multiplexing section where the board is located.


SDH: Signal Failure


Alarm code: 1797


Alarm description: SDH: Signal Failure

Causes leading to the alarm may include:

The error code occurs because the fiber pigtail on the downlinks of all the NEs in the multiplexing section is damaged, transmission line attenuation is increased or the optical transmission mode changes;

The ADM sending equipment is faulty.

Handle the fault according to the causes:

Check whether the fiber pigtail is polluted;

Check whether the optical power attenuation of each connection point in the downlink of the multiplexing section using optical dynamometer.

Ask the transmission network maintenance personnel to check whether the ADM sending equipment is faulty.

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling




SDH: AU-4 Pointer Lost


Alarm code: 1799


Alarm description: SDH: Loss of AU-4 pointer.

The upstream AU-4 pointer processing unit is faulty.

Ask the transmission network maintenance personnel to check whether the upstream AU-4 pointer processing unit is faulty.


SDH: AU-4 Alarm Indication Signal


Alarm code: 1800


Alarm description: SDH: AU-4 Alarm Indication Signal

The upstream VC-4 channel control unit is faulty.

Check whether the upstream VC-4 channel control unit is faulty.


SDH: VC-4 Trace Identifier Mismatch


Alarm code: 1801


Alarm description: SDH: VC-4 signal trace mismatch

During the cutover and dispatching of the optical fiber, the optical fiber connection on ODF is wrong or the expected value set by the network management system is wrong.

Check the fiber connections on the local-end and opposite-end ODFs, and whether the preset values of the VC-4 channel access point identifiers of the two ends are consistent.


Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



SDH: VC-4 Unequipped


Alarm code: 1802


Alarm description: SDH: VC-4 unequipped (UNEQ).


Check whether the upstream VC-4 channel control unit is faulty.


SDH: VC-4 Channel Payload Mismatches


Alarm code: 1803


Alarm description: SDH: VC-4 channel label mismatch (VC4PLM).

The cross connection in the SDH network is incomplete during the stage of engineering installation.

Check the circuits in the corresponding slots of the data cross connection equipment at each station are correctly configured.


SDH: TU-12 Loss of Multi-frame


Alarm code: 1805


Alarm description: Loss of the branch multi-frame.


Check the upstream VC-4 channel control unit is normal.


Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



HP_SF


Alarm code: 1814


Alarm description: High-channel signal failure.

Causes for this alarm may include:

The error code occurs because the fiber pigtails on the downlinks of all the NEs in the multiplexing section are damaged, transmission line attenuation is increased or the optical transmission mode changes;

The ADM sending equipment is faulty.

Check whether the ADM sending equipment is faulty, whether the attenuation of the fiber line is too big, and whether the optical power of each connection point is normal.


CPU Rate is Over Threshold


Alarm code: 2560


Alarm description: The CPU usage is too high.

When the upper-layer service traffic is huge, the CPU usage is too high and many exceed the threshold of CPU occupancy.

Reduce the service traffic.

The alarm is eliminated and the system works normally.

Flash Device Initialize Failed


Alarm code: 3073


Alarm description: Flash device initialize failed.

FLASH is damaged.

Replace the board.


Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



Media Port is Abnormal


Alarm code: 5376


Alarm description: Media port is abnormal.

Media port is abnormal.

BRS can not perform processing related to Level 2 forwarding table.

Check the hardware port and the board are normal.


Alarm RSMM HW Loop Error


Alarm code: 5378


Alarm description: Board HW loop test failure.

Circuit switching traffic may be interrupted.


The HW electronic switch is not opened.

The NE clock is exceptional.

The TDM connection chip is exceptional.

The UIM end connection is exceptional.

The board connection is exceptional.

Handle the fault referring to the following operations:

Check whether the HW electronic switches on this board and the UIM board in the same frame are normally opened.

Check the clock of this frame, and check whether any alarm is lost.

Check the connection chips on this board and the UIM board are normal through timeslot self-loop (in the TestMenu operation).

Check the connection of the corresponding slot on the UIM board is normal (in general, the test of some timeslot receiving/sending packets is performed on the UIM board).

Check the board connection is normal (test the connection chips in TestMenu)

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Influence

Cause

Handling




Input Clock Abnormal


Alarm code: 5381


Alarm description: The input clock is exceptional.


The clock board runs exceptionally, and is not in the normal working status.

No Clock Base is input to the clock board or the Clock Base is exceptional.


Check the clock board runs normally through the indictors on the panel.

Check the Clock Base is input to the clock board, whether the Clock Base is exceptional, and whether the input line is correctly connected.


Communicate Link of PWRD 485 Broken


Alarm code: 5382


Alarm description: PWRD 485 communication link interruption

It may not be monitored whether the power supply of each shelf and board is normal.


The 485 communication link between the PWRD and the OMP is interrupted.

There is no connection between the PWRD and the OMP, or the connection line between the PWRD and the OMP is faulty.

The number configured for the rack where the PWRD is located in inconsistent with that dialed up by the PWRD.


Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling



Check the corresponding 485 link is broken on the OMP (by using SCSShowPWRDInfo).

Check the connection line between the PWRD and the OMP is faulty.

Check the number configured for the rack where the PWRD is located is consistent with that dialed up by the PWRD.


Clock Base Lost Second Level (Middle) Alarm


Alarm code: 26128



The Clock Base has been lost for more than 10 minutes.



OSS Communication Link Off


Alarm code: 8393985


Alarm description: The OSS-layer communication between the service board and the homing module is interrupted.

Inter-board communication is abnormal.


The board is configured in the database, but it is not normally powered on.

The board is powered on, but the control panel link between the board and its homing MP is broken.

After the board is powered on, the ENUM switch is opened.


Check the board is successfully powered on, and the indicator on the panel is normal (the RUN indicator flickers at

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling



the frequency of 1HZ, while the ALARM indicator is off all the time).

(Use “OSS_DbgShowComm” and “OSS_DbgCommBrokenStatShow” to) check the status of the control panel link; (use “OSS_DbgShowUbPool” to) check whether there is UB deficiency in the board or its homing MP.

Check the ENUM switch on the alarm board is opened (check whether the ENUM indicator is on all the time).


Alarm of Office not Access from MTP3


Alarm code: 8400128


Alarm description: The MTP3 office direction is inaccessible. The system failed to receive/send any message to the corresponding office direction.

The system fails to transmit message to or receive messages from the corresponding office.


There are errors in the office direction and route configuration.

The link is broken.


Check whether the static route configuration of the destination office direction is correct.

Query the statuses of the office direction and the dynamic route through the dynamic management.

Query the status of the link in the route table. If the link is broken, see the processing method for the “Alarm of link unavailability” for the fault location method.


Cluster Not Access


Alarm code: 8400130


Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information



Alarm description: Cluster unreachable.

Messages can not be sent to or received from the corresponding office.


There are errors in the cluster and route configuration.

The link is obstructed.


Check whether the static routing configuration of the target cluster is correct.

Query the cluster status and the dynamic routing status through the dynamic management tool.

Query the status of the link in the routing table through the dynamic management tool. If the link is obstructed, refer to the processing method of the alarm of the link unreachable.


Alarm of Office not Access from M3UA


Alarm code: 8400384


Alarm description: The M3UA office direction is inaccessible. The system failed to receive/send any message to the corresponding office direction.

Messages can not be sent to or received from corresponding offices.


The association releasing or AS not in the service status causes the office direction inaccessible.

The SIOLOCAS sheet data to the office direction is not configured, which causes that the office directions managed by the AS and M3UA cannot be bound.


If the association status is normal, check the status of the AS serving the office direction through the dynamic management, and change the AS enter to service status. If the association is unavailable, see the SSM alarm.

Check the data configuration to see whether the SIO of the office direction is configured, and whether there is ASP service.

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling




Cannot Reach the Office


Alarm code: 8401153


Alarm description: Alarm due to SUA office direction unreachable

Messages can not be sent to or received from corresponding offices.


The association status or the AS not in service status makes a signaling point unreachable.

The AS information of the SSN location of all the subsystems to the office is not configured.


Use the dynamic management tool to check the association status. Check the status of the AS serving the office direction, and make it into working state. If the association is unavailable, refer to the SSM alarm.

If the association status is normal, and the AS is in the serving status, check AS information configuration of the location of the corresponding subsystem.


Association Broken Down


Alarm code: 8402690


Alarm description: The association is broken.

It may cause office inaccessible and congestion at other associations.


The association is deleted.

The association is manually released.

Other reasons cause that the association is broken.

If the association is not deleted or manually released, check the association status to make it recover to the normal status.

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling




8k Input Clock Lose


Alarm code: 1280

Default severity: Minor

Alarm description: The 8K input clock of the board is lost.

This alarm may cause communication interruption.

There is a problem in the clock input of this frame.

Check the clock input line of this frame is well connected.


This alarm may cause communication interruption

16M Input Clock Lose


Alarm code: 1281


Alarm description: The 16M input clock of the board is lost.



Check whether the clock input line of this frame is well connected.



PP2S Input Clock Lose


Alarm code: 1282


Alarm description: PP2S input clock loses.


This alarm may cause communication interruption of the system.


Verification

Alarm Information

Influence

Cause

Handling

Verification

Precautions

Alarm Information

Influence

Cause

Handling

Verification

Precautions

Alarm Information

Cause

Influence

Handling



Check the clock input line of this frame is well connected.

Check GCM shelf has locked GPS signals.

The alarm is eliminated and the clock board is normal.

32M Clock Lost in TSNB


Alarm code: 1283


Alarm description: The 32M clock of the TSNB board may be lost.


The 32M clock and the 8K clock are bound, 32M clock alarm occurs when the 32M clock or the 32M8K clock jitters to a certain extent, which influences the connection.

There is no clock.


To ensure that the 32M clock source and the middle link can work normally, switch the clock board first to verify that the alarm disappears or not. If the clock board is normal, it is necessary to check whether the clock driving chip on the board is normal.

Check whether the clock input line of this frame is well connected.


A system has two TSNB boards. One is active, and the other is standby. When the clock alarm occurs, the system switches the standby board to active state, and the active one to be standby state.

For the TSNB, if this alarm occurs, the whole link is obstructed. In a big T Net, if the clock is lost, the data in the whole link is lost. When the clock is recovered, the link will be recovered.

Phase Lock Loop Work Mode is Abnormal


Alarm code: 5643


Alarm description: Working mode of the phase lock loop is abnormal.

Verification

Alarm Information

Cause

Handling

Verification

Precautions

Alarm Information



The working mode of the phase lock loop varies.

Processing related to clock becomes abnormal.


Check whether there is available reference resource.

Check whether the distributing line is correct and whether there is self-loop.

Check whether a Level 2 clock locks a Level 3 clock.


The Channel in the Sub-card is Abnormal


Alarm code: 5644


Alarm description: The channel for the sub-card is abnormal.

The channel for the sub-card is abnormal.

Individual channel can not be used normally.


Reset the board.

Replace the sub-card.

Replace the board.


Recive Bad Packets


Alarm code: 15616


Alarm description: The number of frames discarded at the external port exceeds the threshold.

The system can not receive data messages normally.


The status of the network connected with the external port is exceptional.

The hardware of the board is faulty.

Cause

Influence

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Influence

Cause



The 2400 sub-card originally working normally is loosed due to vibration.

Check whether the board and the link are normal or whether there is any exceptional attack message.


PVC Fault


Alarm code: 18944


Alarm description: Fault in PVC.

Upper-layer traffic may be interrupted.

Timeout when perform the local continuity checking.


Check whether the physical link is normal. Make sure that the status of the optical fiber and the optical module are good and that the indication link of the port indicator is normally connected.

Check the local office has activated the CC module and acts as the receiving end. If the local office cannot receive the CC cell or the subscriber cell sent from the sending end, the link continuity is lost, activate the CC on the background and check whether the link is normal.

If other NEs on the whole PVC link indicate that the PVC link is faulty, AIS or RDI received by the local NE also indicates that the PVC link is faulty. Check the reasons of PVC faults in other NEs by referring to steps 1 and 2.


SDH: Signal Degrade


Alarm code: 1798


Alarm description: signals get degraded.

SD occurs when the board tests that there is error code larger than 1e-6 in the multiplexing section of the received signals. Clear SF first when SD and SF occur simultaneously. If SD occurs individually, it can be determined that the transmission device of the ADM network element has problem.

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Cause



Various alarms occur with part of trunk received signals.

Handle the alarm referring to the following operations:

Clear SF.

Inform the transmission network maintenance personnel to check whether the ADM transmission device has fault.


SDH: VC-4 Far End Receive Failure


Alarm code: 1804


Alarm description: SDH: VC-4 remote receiving failure (VC4FERF).

When a network node of the VC-4 channel where the board is located detects any fault in the uplink direction of its downstream equipment, it sends 1 in the whole AU-4 in the uplink direction. The upstream VC-4 channel terminal sends VC-4 RDI remote alarm in the downlink direction.

Eliminate “original fault” according to the alarm generated by the network node equipment of VC-4 channel where the board is located.


HP_SD


Alarm code: 1815


Alarm description: High-order channel signal deterioration.

When the board detects the error code greater than 1e-6 exists in the receiving signal multiplexing section, SD occurs. When SD and SF occur at the same time, eliminate SF first. When only SD occurs, it can be judged that the ADM sending equipment is faulty.

Check the ADM sending equipment is faulty, whether the attenuation of the fiber line is too big, or the optical power of each connection point is proper.


Influence

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



GE Link Error


Alarm code: 5121


Alarm description: Exception in the GE routing

Media layer is down.

Causes for this alarm may include the followings:

The UIM needs no cascade connection between frames, but the GXS sub-card is inserted.

The UIM and UIM/GLI fiber connections are incorrect or fiber is not connected.

There are exceptions in receiving/sending the detection packets on the UIM link, or the GE routing.

The UIM background configuration is inconsistent with the foreground physical configuration.

Check the physical connection configuration and the optical fiber connection.


The DB Config does not Inconsistent with the Hardware Equipment


Alarm code: 5123


Alarm description: The DB configuration is inconsistent with the hardware equipment.

The system functions can not be implemented.

The database configuration is inconsistent with the hardware equipment.


Check the background configuration.

Modify the configuration according to the hardware device.

Powering on the board again.


Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



Clock Base Lost Third Level (Low) Alarm


Alarm code: 26127



The loss of the Clock Base is successfully detected for the first time.



SCCP SSN is Invalid


Alarm code: 8398848


Alarm description: The SCCP subsystem is unavailable.

Messages can not be sent to or received from the subsystem that it concerns.

A signaling point subsystem exits the service; or a signaling point is inaccessible.

Make the link recover to be normal, the (office direction) signaling point accessible, or the subsystem enter into the service again.


SSCS Congest


Alarm code: 8399104


Alarm description: congestion in the broadband link.

Congestion occurs on the link, which may cause package loss and even call loss.

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause



The SSCOP detects that the usage of sending buffer and queues are over 85% of the total window size, which may be caused by congestion in the link or insufficient processing ability of the opposite end.

MTP3 detects the congestion report of this layer. The system can automatically make processing.


SSCS Overloaded


Alarm code: 8399105


Alarm description: Alarm due to overload in the broad-band link.

Congestion occurs on the link, which may cause package loss and even call loss.

The SSCOP detects that the usage of the sending cache and the queue has reached about 80% of the cache, so it reports overload.

The MTP3 detects the congestion alarms on this layer and the system automatically processes it.


Alarm of Link Unavailability


Alarm code: 8400129


Alarm description: The MTP3 link is unavailable, which may cause the office direction inaccessible and congestion in other available links.

It may cause office inaccessible and congestion on other links.

Causes leading to the fault may include:

The physical link is broken.

The link test is not passed.

The SMP board or the SPB/APBE board is restarted.


The link breaking request initiated by the MTP3 may be caused by that two times of link tests are not passed.

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling



If T2 times out, and the link is in the “Initial_alignment” status all the time. Check the configuration and physical connection at the two ends of the link.

There are many errors, and the link quality is not good. It is necessary to check the configuration from the engineering side, including E1 resistance and clock.

When the link receives SIOS from the opposite end in its service status, it is necessary to confirm the reason of the link broking at the opposite end.

Check whether the configurations at the two ends of the link are consistent, including point code and SLC.

Check the link. If the link needs to be tested, check the test code is configured,

Check whether there is any alarm about the SMP board or SPB/APBE board restarting


SUA Subsystem is Invalid


Alarm code: 8401152


Alarm description: SUA subsystem unusable

Messages can not be sent to or received from the subsystem that it concerns.

A signaling point subsystem exits the service or is unreachable.

Recover the link or the association to the normal status, the (office direction) signaling point reachable, or the subsystem enters into the service status again.

The alarm is eliminated

M2PA Link is Broken


Alarm code: 8402177


Alarm description: The M2PA signaling link is broken.

Data may be lost.

Causes leading to the fault may include:

The timer of data receiving/sending times out.

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause



The association is broken.


Use the dynamic management tool (use the debugging function “SsmState” if there is no dynamic management tool on the background) to check the status. If the association status is normal, check the configurations at the two ends is consistent.

Check whether the M2PA predefined timers T1~T4 are configured.

Check whether the protocol type of the M2PA link is consistent.


Association is Congestive


Alarm code: 8402688


Alarm description: association congestion.

Data may be lost.

The sending cache of the association at the SCTP layer is congested.

Reduce the data flow of the upper-lay user to the sending direction.


Trunk Frame Lose


Alarm code: 512

Default severity: Warning

Alarm description: The trunk frame is lost.

It fails to receive signals from this trunk.

The trunk frame is lost.

Check whether the upstream equipment.


Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



Trunk Signal Lose


Alarm code: 513


Alarm description: The trunk signal is lost.


The two ends have no common ground, the clocks are not synchronized, or the transmission equipment is faulty.

Check the upstream equipment or the physical connection at the local end.


Trunk Alarm Indication


Alarm code: 514


Alarm description: Trunk alarm indication signal.


The upstream equipment is faulty.

Check which alarms occur in the corresponding E1 of the upstream equipment, and eliminate them.


Trunk Multi-frame Lose


Alarm code: 515


Alarm description: The trunk multi-frame is lost.


The frame format is inconsistent.

Configure the frame format at the two ends connected together consistent and check the upstream equipment.


Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification



Trunk Receive far End CRC Multiframe Alarm Indication


Alarm code: 516


Alarm description: The alarm indication occurs when the trunk receives remote CRC multi-frames.


Causes for this alarm may include the followings:

The clock is instable.

The uplink equipment is faulty.

Use the E1 tester or loop tester to check whether the middle transmission equipment of the trunk link is faulty.


Trunk Receive Far End Alarm


Alarm code: 517


Alarm description: The alarm occurs in the remote receiving end.


A problem occurs when the local end sends signal, or the middle transmission equipment is faulty.

Check the communication between the board and the control plane of its home module.


Cell Delimiter cannot Synchronize


Alarm code: 1024


Alarm description: The cell delineation cannot be synchronized.

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information



Generally, the reason is that the configurations of mutually-connected equipments are inconsistent, and the cell cannot be delineated from the physical-layer frames through the HEC check.

Check whether there is any other physical-layer alarm. If the OCD/LCD alarm still exists, check the opposite-end and local-end equipments have performed the co-set processing on the HEC.


Cell Delimiter Lose


The cell delineation Alarm code: 1025


Alarm description: The cell delineation is lost.

Check whether there is any other physical-layer alarm. If the OCD/LCD alarm still exists, check the opposite-end and local-end equipments have performed the co-set processing on the HEC.


SDH: TU-12 Loss of Pointer


Alarm code: 1806


Alarm description: Loss of branch pointer (TU12LOP).

The upstream TU branch pointer processing unit is faulty.

Check the upstream TU-12 branch pointer processing unit is faulty.


SDH: TU-12 Alarm Indication Signal


Alarm code: 1807


Alarm description: Branch alarm indication signal (TU12AIS)

A fault occurs in an upstream equipment of the branch function node that sends all 1 for TU.

Cause

Handling

Verification

Alarm Information Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause



Check the upstream TU-12 branch pointer processing unit is faulty.


SDH:TU-12 Remote Defect Indication


Alarm code: 1808


Alarm description: Branch remote defect indication.

The reason may be that a fault occurs in the downstream equipment (including boards) of the branch function node that sends “TU RDI remote alarm”.


Use the SDH tester to check whether any TU-12 branch function fault exists on the local end.

Use the SDH tester to check whether any branch function fault exists on the equipments of other nodes in the TU-12 branch.


SDH: TU-12 Remote Failure Indication


Alarm code: 1809


Alarm description: Branch remote failure indication.

When the 5 consecutive frames of the V5 bit4 received by the board in the TU branch are “1”, the TU RFI alarm occurs.

Use the SDH tester to check whether any fault exists on the control unit in the upstream TU-12 branch.


Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



SDH: TU-12 Trace Identifier Mismatch


Alarm code: 1810


Alarm description: Branch signal track mismatch.

During the cutover and dispatching of the cable, the cable connection on DDF (Digital Distribution Frame) is wrong or the expected value set by the network management system is wrong.


Use the SDH tester to check whether the remote equipment of the branch has been equipped with the branch.

Check the circuit configuration in the corresponding slot of each DXC node in the transmission line by using the SDH tester.


SDH: TU-12 Unequipped


Alarm code: 1811


Alarm description: Branch unequipped.

The cross connection in the SDH network is incomplete during the stage of engineering installation, or the branch remote equipment is not equipped.


Using the diagnostic test function check the signal label received by the branch is consistent with that configured at the local end. Check the configuration at both local and remote end.

Check whether the circuit configuration in the corresponding slot of each DXC node in the transmission line is correct by using the SDH tester.


Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



SDH: TU-12 Payload Mismatch


Alarm code: 1812


Alarm description: Branch channel label mismatch.

The cross connection in the SDH network is incomplete during the stage of engineering installation.


First eliminate the SF alarm in the SDH.

Use the SDH tester to check the bit error rate in the high-order channel and fix it.

Check the transmission line is faulty.


The HDLC is Unusable


Alarm code: 8407296


Alarm description: HDLC channel is unavailable and HDLC drops packets successively for three times.

Causes leading to the alarm may include the followings:

HDLC is dynamically created.

HDLC link is unconnected or the quality is bad, or the bottom layer module (e.g. BSP or microcode) has fault,.

For active and standby boards, when HDLC of the new active board has an initial state BAD, it is first restored to OK state, and then the alarm occurs.

Traffic amount reduces, or the service is interrupted.


When HDLC receives replied packets successively for three times, it can be considered that the HDLC is connected. Change the state BAD to OK, and then restore the alarm.

If there is a need to delete HDLC and the previous state of HDLC is BAD, first restore the alarm to avoid that there is no alarm next time the HDLC is generated.


Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification



The UID Bind is Unusable


Alarm code: 8407297


Alarm description: UID Bind is Unavailable.

Causes leading to the alarm may include the followings:

HDLC is dynamically created.

For power-on UID, because there is only one home HDLC, therefore, whenever the state varies from OK to BAD, the alarm occurs.

For service UID, when all home HDLCs change to BAD state, first delete UID binding with bottom layer BSP, and then generates the alarm occurs.

While the active and standby boards changing over, when UID of the new active board does not be bound, restore it before the alarm occurring.

Traffic amount reduces, or the service is interrupted.


For power-on UID, when the state recovers to normal state, the alarm occurs; For service UID, when there is one HDLC firstly connected in UID (the state changes to OK) , first add UID binding in bottom layer BSP, and then restore the alarm.

If to delete a UID without adding binding, first restore the alarm to avoid that there is no alarm next time the UID is generated.


MAC Address of the board Conflicts


Alarm code: 5650


Alarm description: MAC address of the board conflicts.

Board is not on its position rightly or other exceptional reasons.

Reinsert the board.

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information

Cause

Handling



DSP over Load High Alarm


Alarm code: 26626


Alarm description: DSP over load High Alarm.

DSP load is higher than the high threshold.

Please decrease DSP's call load.

DSP over Load Middle Alarm


Alarm code: 26627


Alarm description: DSP over load High Alarm.

DSP load is higher than the middle threshold.


DSP over Load Low Alarm


Alarm code: 26628


DSP over load Low Alarm.

DSP load is higher than the low threshold.


Tone Resource Board DSP Tone Type Differ


Alarm code: 5659


Alarm description: Tone resource board’s DSP tone type differ.

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information



Differ Tone cannot exist On Board.

Switch Same Type Tone.

Error Connection on 129ts of T-net board


Alarm code: 25601


Alarm description: Error connection on 129ts of T-net board.

Connection error on 129ts of T-net board.

No further solution. Inform staff of 3G platform to analyze if alarm can't restore.

Loop Error of LVDS 129 time slot


Alarm code: 5658


Alarm description: Loop error of LVDS 129 time slot.

Loop error of LVDS 129 time slot.

Change the board.

Dual Attribution Office has been Blocked


Alarm code: 14592


Dual attribution office has been blocked.

Dual attribution office changing to slave state, DH process starts to block the office.

Unblock the dual attribution office or unblock the links and associations of it by hand.

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



Dual Attribution Link has been Blocked


Alarm code: 14593


Alarm description: Dual attribution link has been blocked.

Dual attribution office changing to slave state, DH process starts to block the links of the office.

Unblock the dual attribution office's associations or unblock all associations of it by hand.

Dual Attribution Association has been Blocked


Alarm code: 14594


Alarm description: Dual attribution association has been blocked.

Dual attribution office changing to slave state, DH process starts to block the associations of the office.

Unblock the dual attribution office's associations or unblock all associations of it by hand.

8K, 16M Input Clock no Match


Alarm code: 1284


8K, 16M input clock no match.

8K, 16M input clock no match.

Check the CLKG board.

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



BOOT/EPLD Upgrade Information


Alarm code: 5891


Alarm description: BOOT/EPLD upgrades information.

BOOT/EPLD upgrades information.

Switch BOOT version again, and reset board manually.

BOOT Version Synchronization Information


Alarm code: 5892


BOOT version synchronization information.

BOOT version synchronization information.

Powing Error of SETS


Alarm code: 5654


Alarm description: Powing Error of SETS.

SETS chip has some fault.

1. Check whether the SETS chip abnormal by the diagnostic test.

2. If problem does not recover, change the board and check the alarm information.

Spending of DSP has Reached a Dangerous Degree


Alarm code: 26624


Alarm Information

Cause

Handling

Alarm Information

Cause

Alarm Information

Cause

Handling

Alarm Information



Spending of DSP has reached a dangerous degree.

Spending of DSP has reached a dangerous degree.

Limit the traffic of DSP.

The BFD Session is Down


Alarm code: 22784


Alarm description: The BFD session is down.

The BFD session is down.

Check that whether the link is normal and the BFD configuration is correct.

This Trunk is Used to CSU Test


Alarm code: 518


Alarm description: This trunk is used to CSU test.

This trunk is used to CSU test.

Unit A transmits CSU Loop down Code to unit B.

VC_4 Far End Error Indication


Alarm code: 1821


Alarm description: VC_4 Far End Error Indication.

VC_4 Far End Error Indication.

1. Find out whether the receive power is too low. If true, make sure the fiber and optic modulator are all right and compatible.

2. Conduct the self loopback test. If no B1ERR declare, the remote peer device may have problem. It is recommended to change a board.

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



High Order Signal failure


Alarm code: 1822


Alarm description: High order signal failure.

When the bit error rate exceeds 1e-3 in the VC_4, SF shall be declared.

Check if the optical fiber is damaged or link is broken.

A Class Error of SETS


Alarm code: 5652


Alarm description: A Class Error of SETS.

SETS chip has some problems.

1. Check whether the SETS chip is abnormal by the diagnostic test.


B Class Error of SETS


Alarm code: 5653


Alarm description: B Class Error of SETS.

SETS chip has some problems.

1. Check whether the SETS chip abnormal by the diagnostic test.


TRUNK Link Error


Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information



Alarm code: 5124


Alarm description: TRUNK Link Error.

Physical FE Link or port setting Error.

Check TRUNK connecting, correct the wrongs.

MP PROC INST ERROR


Alarm code: 2562


Alarm description: MP PROC INST ERROR.

MP PROC INST ERROR.

Reconfigure the process's instance.

TRUNK Port Down


Alarm code: 5634


Alarm description: TRUNK port down

TRUNK line or bcm5615 port is wrong.

Check up board ENUM and close the ENUM. If the alarm happens because of EXCH, repeat the operation again.

OSS Check out that IP&MAC Address of the Board Bonflicts


Alarm code: 5651


Alarm description: OSS checks out that IP&MAC address of the board conflicts.

Board is not on its position rightly or other exceptional reasons.

Reinsert the board.

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



DSP Automatic Check Abnormal


Alarm code: 5655


Alarm description: DSP automatic check is abnormal.

DSP check port or abnormal status is more than the threshold limit (default 25%).

Reset DSP.

Function Epld Version Update Fail


Alarm code: 5890


Alarm description: Function EPD Version Update Fail.

Following causes lead to this alarm:

EPLD version too big (limited to 64K).

Write EPLD fail.

Switch another EPLD version

E3S Sub-card Receive Alarm Signal Indication


Alarm code: 2051


Alarm description: E3S sub-card receives alarm signal indication.

AIS is asserted when AIS pattern is received in near end;AIS is eliminated when valid frame is received.

Check the remote device whether there is e3 subcard corresponding alarm, if exist, and eliminate the corresponding alarm.

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



Remote Error Indication


Alarm code: 2052


Alarm description: Remote error indication.

Remote error indication is asserted when remote error indication bit in received frame is set.

Use a new cable to replace old cable.

FE RX LSM can't turn to Active State


Alarm code: 19221


Alarm description: FE RX Links's LID has been changed, that caused FE RX LSM can't turn to active state.

The links have been misconnected or the LID has been changed from OAM.

Configure the TX clock mode on NODEB, or disconnect the links and then connect the links again.

Associate Path Break


Alarm code: 8417537


Alarm description: Associate Path Break.

Associated path break.

Check link and IP configuration.

STC Office Unaccess


Alarm code: 8402944


Alarm description: STC office inaccessible.

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information



All associations are out of service.

Check the state of associations.

STC Office Congest


Alarm code: 8402945


Alarm description: STC office congestion.

All associations are out of service.

Check the state of associations.

Abis Link Down


Alarm code: 8392448


Alarm description: Abis link is down.

Abis link failed to negotiate. This could occur frequently.

Check the BTS state.

Check the Alarming Board workload.

The Communication Flow over Alarmed Threshold Value


Alarm code: 23296


Alarm description: The communication flow over alarmed threshold value.

OAM called the interface of calculating the flow afforded by OSS, judged if the flow over the alarmed value.

Decrease the communication flow.

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



Ctrl Port to UIM Error


Alarm code: 5648


Alarm description: CTRL Port to UIM Error.

CTRL Port to UIM links is down or packets are being lost for 3 minutes.

Check the status of UIM port, Reset board or reset uim and so on.

Input Clock of Subcard is Lost


Alarm code: 5656


Alarm description: Input clock of sub-card is lost.

Sub-card is inserted wrongly or hardware is error.

Reinsert or exchange sub-card, or exchange the board.

2350 Receive Rardware Error


Alarm code: 16640


Alarm description: 2350 receive hardware error.

The Alarm happens when MNIC_2 board receive a certain numbers of hardware-error frames.

Check the board, maybe need to replace another board if alarm occurs continually.

FE RXLSM is in Unusable State


Alarm code: 19210

Default severity: Major

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information



Alarm description: The remote receiving link connected with the local end is unusable.



A receiving link at the remote end is faulty, so it is changed to the “Unusable” status from the “ACITIVE” status.

The link enters into the “Unusable” status after the link is just enabled and not activated.

Handle the alarm referring to the following operations:

The alarm automatically disappears in case that the link enters into the “Unusable” status after the link is just enabled.

For the remote receiving link problem, check whether the IMA link configuration such as scrambling code and direction at the remote end matches with that at the local end.

Check whether the RUN indicator on the clock board is green and flash slowly, and use the debugging function “ppdbgpslot（ BYTE ucSlot ） ” to check the UIM/DTB connection relationship, and check whether the E1 cable is loosed.


SCCP Connect ID Less than1000


Alarm code: 8256


The SCCP Connect ID Less Than 1000.

The SCCP Connect ID Less Than 1000.

Please Contact ZTE.

Communication Alarms This section introduces alarms related to communication fault.

PPP_UID Link Down




Influence

Cause

Handling

Verification

Alarm Information

Cause

Handling

Description

Alarm Information



Alarm description: PPP_UID link breaks.

PPP negotiation fails due to E1 link to BTS has problem or BTS is down.



Check whether BTS has booted.

Check whether the E1 link to BTS is normal.


PPP Link Down




Alarm description: PPP link breaks.


Most ports are dynamically created. And there is alarm while initially creating a port.

If the previous state of IPCP is OPENED, when the link changes from connected to unconnected or the link quality is not good

The bottom layer module has fault (e.g. BSP or microcode fault), PPP drops packets successively for 5 times, the alarm occurs.



If the link is connected and IPCP can successively negotiate, restore the alarm.

Restore alarm first before deleting the opened ports to avoid that there is no alarm next time the port is created.

According to different logic boards, PPP port is created and deleted in different ways.

INLP and ABPM, IB_PPP are added/deleted dynamically, while POSI does not vary (has only one exterior port).


Internet Port Physical Link Off


Cause

Influence

Handling

Verification

Alarm Information

Cause

Influence

Handling

Verification

Alarm Information



Alarm code: 256


Alarm description: The physical link of Ethernet controller is broken. This alarm may cause breaking of the one Ethernet-related link.

Associated link off

There may be faults in the network cable or network interface.

Check the Ethernet cable connection.

The alarm is eliminated, and the link connection is normal.

The Communication between the Master and Slaver is Interrupted


Alarm code: 5122


Alarm description: Interruption of the active/standby communication link

The active and standby boards can not communicate with each other.


The board is configured to active/standby mode, but the standby board is not inserted.

The communication link between the active board and the standby board is broken.


For the board configured to active/standby mode, insert the standby board, and the alarm disappears after power-on.

Check the statuses of the communication links at the bottom layers of the OSS subsystem and the BSP subsystem.


IUA Association is Broken




Alarm description: IUA association is broken

IUA association is broken.

Influence

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Alarm Information

Cause



Check the association, and restore it.


The Link between NE And Server Breaks




Alarm description: The link between NE and server breaks.

The network cable or port has fault.

Check the Ethernet link.


Communication between MP and OMP Error


Alarm code: 8393988


Alarm description: The communication between the module and the OMP is interrupted. The status of the unit belonging to the MP is unknown.

he heartbeat signal of the MP cannot be successfully detected du to IP address problem or some error in the link. The status of units belonging to this home MP is unknown if the communication between MP and OMP is broken.

The communication between the module and the OMP is interrupted. The heartbeat signal of the MP cannot be successfully detected on the OMP.

Check the control panel communication between the module and the OMP.


Qos Alarms This section introduces alarms related to service quality.

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Influence

Cause

Handling

Verification

Description



INLP Fails to Request SCTP's Load Balancing Table




Alarm description: INLP fails to request SCTP's load balancing table.

INLP fails to request SCTP's load balancing table.

Check the configuration for SMP and INIP boards.


Expired Password Alarm


Alarm code: 50001


Expired Password Alarm.

Expired Password Alarm.

Please modify password immediately.

Expired Password Notify


Alarm code: 50002


Expired Password Notify.

Expired Password Notify.

Please modify password immediately.

Environment Alarms This section introduces alarms related to environment conditions.

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling

Description



CPU Temperature over Threshold


Alarm code: 2561


Alarm description: The CPU temperature is too high.

The CPU temperature of one board is too high due the CPU fan failure.


Check whether fans work normally. Check the power supply of the fan.

If the environment in the equipment room is too high, improve ventilation and take other measures to reduce the temperature in the equipment room.

The alarm is eliminated and the temperature is within the normal range.

Too high temperature may cause that the CPU is automatically reset.

Rack Temperature Higher than Higher Threshold


Alarm code: 25856


Alarm description: The temperature of the rack exceeds the upper limit of the alarm threshold.

The temperature of the rack exceeds the pre-set upper limit of the alarm threshold due to increase in the room temperature.


Cool the rack.

Increase the pre-set upper limit of the alarm threshold.

Check the environment in the equipment room, make sure the air conditions work normally, and cools the rack.

The alarm is eliminated, and the temperature in the equipment room and that of the rack are within the normal range.

Alarm Information

Cause

Handling

Verification

Precautions

Alarm Information

Cause

Handling

Verification



Rack Temperature is Lower than Low Threshold


Alarm code: 25857


Alarm description: The temperature of the rack is lower than the lower limit of the alarm threshold.

The temperature of the rack is lower than the pre-set lower limit of the alarm threshold.


Increase the temperature of the rack.

Reduce the pre-set lower limit of the alarm threshold.

The alarm is eliminated, and the temperature in the equipment room and that of the rack are within the normal range.

House Temperature is Higher than High Threshold


Alarm code: 25858


Alarm description: The temperature in the equipment room exceeds the upper limit of the alarm threshold.

The temperature in the equipment room exceeds the pre-set upper limit of the alarm threshold.


Cool the equipment room.


The alarm is eliminated, and the temperature in the equipment room is within the normal range.

House Temperature is Lower than Low Threshold


Alarm code: 25859

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information




Alarm description: The temperature in the equipment room is lower than the lower alarm threshold.

The temperature in the equipment room is lower than the pre-set lower limit of the alarm threshold.


Increase the temperature in the equipment room.


The alarm is eliminated, and the temperature in the equipment room is within the normal range.

Voltage is Higher than High Threshold


Alarm code: 25860


Alarm description: Any line of voltage exceeds the upper limit of the alarm threshold.

One line of voltage exceeds the pre-set upper limit of the alarm threshold du variable performance of power supply equipment.


Try to reduce the voltage of this line.



Voltage is Lower than Low Threshold


Alarm code: 25861


Alarm description: Any line of voltage is lower than the lower limit of the alarm threshold.

One line of voltage is lower than the pre-set lower limit of the alarm threshold due to low voltage supply of power supply or shot circuit.


Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling



Try to increase the voltage of this line or check whether there is any short circuit.



Humidity is Higher than High Threshold


Alarm code: 25862


Alarm description: The humidity exceeds the upper limit of the alarm threshold.

The humidity in the equipment room exceeds the pre-set upper limit of the alarm threshold.


Try to reduce the humidity in the equipment room.



Humidity is Lower than Low Threshold


Alarm code: 25863


Alarm description: The humidity is lower than the lower limit of the alarm threshold.

The humidity in the equipment room is lower than the pre-set lower limit of the alarm threshold.


Try to increase the humidity in the equipment room.



Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification



Fan is Lower than Low Threshold


Alarm code: 25864


Alarm description: There are faults in the fan frame.

The fan is faulty.

Check the hardware fault in the fan.

The alarm is eliminated, and the fan work normally.

Alarm Because Of Door


Alarm code: 25865


Alarm description: access control alarm.

The access control of the corresponding rack is not closed.

Close the access control of the corresponding rack.


Alarm because of Fume


Alarm code: 25866


Alarm description: smog alarm.

The smog detector detects there is smog, which is generally caused by open fire, smolder or even smoking.

Clear smog in the equipment room and forbid smoking in the equipment room.


Alarm because of Infrared


Alarm code: 25867

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information




Alarm description: infrared alarm.

The infrared is too strong.

Reduce the intensity of the infrared in the equipment room.


Alarm because of Thunder


Alarm code: 25868


Alarm description: thunder alarm.

The weather is stormy, and equipment room is influenced by thunder stroke.

Take good protection measures.


Inner Media VLAN Communication Abnormal


Alarm code: 5396


Alarm description: Inner media VLAN communication abnormal.

Board packet lost percentage of inner media VLAN communication is more than the threshold (default 25%).

Check if trunk line or the BCM5615 port is normal.

E3S sub-card Transmitter Direction Loss of Signal


Alarm code: 2048


E3S sub-card transmitter direction loss of signal.

Cause

Handling

Verification

Alarm Information

Cause

Handling

Verification

Alarm Information

Cause

Handling

Alarm Information



Transmitter loss of signal is observed when no transitions are observed on transmit data for at least 32 consecutive clock cycles.

Reboot board.

E3S Sub-card Receive Direction Loss of Signal


Alarm code: 2049


Alarm Description: E3S sub-card receives direction loss of signal.

Receiver loss of signal is asserted when a continuous run of 128 consecutive 0s occurs; receiver loss of signal is de-asserted when minimum 1's density is at least 20%.

Check whether the cable impedance of our company meets with the corresponding node, the board DIP Switch is of the same type of cable and the pitch jump(female) of rear card is consistent with the type of cable.

Check whether the device's grounding signals on the two sides.

Out of Frame


Alarm code: 2050


Out of frame.

Out of frame error.

Check the cable impedance meets the requirements. The board DIP Switch is consistent with the type of cable and the pitch jumper (female) of rear card is consistent with the type of cable.

Check whether the device's grounding signals on the two sides.

Cause

Handling

Alarm Information

Cause

Handling

Alarm Information

Cause

Handling



Port not Work on the Configured Mode


Alarm code: 2050


Port not works on the configured mode.

The working mode of out port or chip performance is not proper or the other end linked has problem. The ports don't work on the mode set.

Check mode out port and also check chip of the corresponding port.

Alarm Information

Cause

Handling


A p p e n d i x A

Abbreviations

Abbreviation Full Name

1X EV 1X Evolution

1X EV-DO 1X Evolution Data Only

1X EV-DV 1X Evolution Data & Voice

3G The third generation mobile communications

3GPP2 3rd Generation Partnership Project 2

AAA Access, Authorization, and Accounting

APGW Access Point Gateway

API Application Programming Interface

ATM Asynchronous Transfer Mode

BCSN Backplane of Circuit Switch Network

BCTC Backplane of ConTrol Center

BER Bit Error Ratio

BPSN Backplane of Packet Switch Network

BS Base Station

BSC Base Station Controller

BSS Base Station System

BTS Base Transceiver Station

BUSN Backplane of Universal Switch Network

CACH Common AsSIGnment Channel

CAS Channel Associated SIGnaling

CBC Cell broadcast center

CCS Common Channel SIGnaling

CDMA Code Division MultIPle Access

CF all Call Forwarding services

CFB Call Forward Busy

CFBI Central Fiber Bus Interface




CFD Call Forward Default

CFNA Call Forward No Answer

CFNRc Call Forward No Reachable

CFNRy Call Forward No Reply

CFU Call Forward Unconditional

CIC Circuit IDentification Code

CKCD Central Clock and Communication Driver

CLKG CLOCK Generator CNIP Call Number IDentification Presentation

CNIR Call Number IDentification Restriction

CP Content ProvIDer

CPM Common SIGnaling Process Module

CPSN Central Power Switching Network

CRC Cyclic redundancy check

CSM Central Switching Module

DPC Destination SIGnaling Point Code

DTB Digital Trunk Board

DTI Digital Trunk Interface

DTU Digital Trunk Unit

ESME External Short Message Entity

FDMA Frequency Division MultIPle Access

FEP Front-End Processor

FN Fleet Number

FPGA Field Programmable Gate Array

FTAM File transfer access management

FTP File Transfer Protocol

GIF Graphics Interchange Format

GMSCe Gateway MSCe

GPRS General Packet Radio Service

GSM Global System for Mobile communications

GT Global Title

GUI Graphical User Interface

HDLC High level data link control

HLRe Home Location Register emulator

HTML Hyper Text MakeUP Language

HTTP Hypertext Transfer Protocol

Appendix A Abbreviations



HW High speed data Way

I/O Input/Output

IMSI International Mobile Subscriber IDentity

IPI IP bearer Interface

IRM International Roaming MIN

ISDN Integrated Service Digital Network

ISO International Standardization Organization

ISUP ISDN User Part

ISUP ISDN User Protocol

IWF InterWorking Function

kbps kilo-bits per second

LMSD Legacy Mobile Station Domain

MC Message Center

MDN Mobile Data Number

MGW Media Gateway

MIN Mobile Station IDentify Number

MNC Mobile Network Code

MNIC Multi-service Network Interface Card

MPB Main Processing Board MS Mobile Station

MSCe Mobile Switching Center emulator

MSID Mobile Station IDentifier

MSS Mobile Switching System

MTP Message Transfer Part

MTP1 Message Transfer Part-layer 1



NGN Next Generation Network

NMC Network Management Center

NMS Network Management Subsystem

OMC Operations & Maintenance Center

OMM Operation Maintenance Module

OPC Originating SIGnaling Point Code

OTA Over The Air

PDA Personal Digital Assistant

PDN Packet Data Network




PDSN Packet Data Serving Node

PDSS Packet Data Switching System

PN Personal Number

PPP Point to Point Protocol

PPPoE Point to Point Protocol over Ethernet

PSN Packet Switch Network

PSPDN Packet Switched Public Data Network

PSTN Public Switched Telephone Network

PTT Push-To-Talk

PWRD POWER Distributor

RADIUS Remote Authentication Dial In User Service

RAID Redundant Array of Independent Disks

SC Short message Center

SCCP SIGnaling connection control part

SCP Service control point

SCPe Service Control Point emulator

SDH Synchronous Digital Hierarchy

SDTB SONET Digital Trunk Board

SGW SIGnaling Gateway

SID system IDentify

SIO Service Information Octet

SIPI SIGnaling IP bearer Interface

SLS SIGnaling Link Selection

SME Short Message Entity

SMG Short Message Gateway

SMPP Short Message Peer-to-Peer protocol

SMS Short Message Service

SMTP Simple Message Transfer Protocol

SNM Service Network Module

SNMP Simple Network Management Protocol

SOAP Simple Object Access Protocol

SP Service ProvIDer

SPB SIGnaling Processing Board

STM Synchronous Transfer Mode

TDMA Time Division MultIPle Access

TLDN Temporary Location Digital Number

Appendix A Abbreviations



UBC all-User BroadCast

UIM User IDentity Module

VMSCe Visited MSCe

VPN Virtual Private Network

WAP Wireless Application Protocol

WDP Wireless Datagram Protocol

WDSS Wireless Data Services System

WIN Wireless Intelligent Network

WVPN Wireless Virtual Private Network





A p p e n d i x B

Collection of Alarm Information

Alarm Classification

Alarm Code

Alarm Name Alarm Level

Page No.

2 2 Optical module no light 2 22

3 256 Internet port physical link off 3 75

2 512 Trunk frame lose 1 55

2 513 Trunk signal lose 1 56

2 514 Trunk alarm indication 1 56

2 515 Trunk Multi-frame lose 1 56

2 516 Trunk receive Far end CRC Multi-frame Alarm Indication

1 57

2 517 Trunk receive Far end alarm 1 57

2 518 This trunk is used to CSU test 3 67

2 1024 Cell delimiter cannot synchronize

4 57

2 1025 Cell delimiter lose 4 58

2 1280 8K input clock lose 3 46

2 1281 16M input clock lose 3 46

2 1282 PP2S input clock lose 3 46

2 1283 32M Clock lost in TSNB 3 47

2 1284 8K,16M input clock no match 3 65

2 1792 SDH: Loss of signal 2 23

2 1793 SDH: Loss of frame 2 23

2 1795 SDH:Multiplex section alarm indication signal

2 36

1 1796 SDH: Multiplex section far end receive failure

3 15

2 1797 SDH: Signal failure 2 36




Alarm Code


Page No.

2 1798 SDH: Signal degrade 3 49

2 1799 SDH:AU-4 pointer lost 2 37

2 1800 SDH:AU-4 alarm indication signal

2 37

2 1801 SDH:VC-4 trace identifier mismatch

2 37

2 1802 SDH:VC-4 unequipped 2 38

2 1803 SDH: VC-4 channel payload mismatches

3 38

2 1804 SDH:VC-4 far end receive failure

2 50

2 1805 SDH:TU-12 loss of multi-frame

4 38

2 1806 SDH:TU-12 loss of pointer 4 58

2 1807 SDH:TU-12 alarm indication signal

4 58

2 1808 SDH:TU-12 remote defect indication

4 59

2 1809 SDH:TU-12 remote failure indication

4 59

2 1810 SDH:TU-12 trace identifier mismatch

4 60

2 1811 SDH:TU-12 Unequipped 4 60

2 1812 SDH:TU-12 payload mismatch 2 61

2 1814 HP_SF 3 39

2 1815 HP_SD 2 50

2 1821 VC_4 Far End Error Indication. 2 67

2 1822 High order Signal failure. 2 68

5 2048 E3S subcard transmitter direction loss of signal.

3 84

5 2049 E3S subcard receive direction loss of signal.

3 85

5 2050 Out of frame. 3 85

2 2051 E3S subcard receive alarm signal indication.

3 70

2 2052 Remote error indication. 3 71

2 2560 CPU rate is over threshold 2 39

5 2561 CPU temperature over Threshold

2 78

2 2562 MP PROC INST ERROR. 1 69

Appendix B Collection of Alarm Information



Alarm Code


Page No.

2 3073 Flash device initialize failed 3 39

2 5120 Fibers connect error 3 21

2 5121 GE link error 3 51

3 5122 The communication between the master and slaver is interrupted

3 76

2 5123 The DB config does not inconsistent with the hardware equipment

2 51

2 5124 TRUNK Link Error. 3 68

2 5376 Media port is abnormal 2 40

2 5378 Alarm RSMM HW loop error 2 40

2 5379 Board does not exist 2 21

2 5381 Input clock abnormal 2 41

2 5382 Communicate link of PWRD 485 is broken

1 41

1 5383 Bureau Number from database does not agree with the one in bootcfg.ini

2 13

1 5384 Area Number from database does not agree with the one in bootcfg.ini

2 4

1 5385 OMC MAC in database does not agree with the one in bootcfg.ini

2 5

1 5386 OMC IP in database does not agree with the one in bootcfg.ini

2 5

1 5387 MP Type in database does not agree with the one in bootcfg.ini

2 5

1 5388 Bootcfg.ini does not exist 2 6

2 5389 A (CPU) sub card is online, but is not configured by database

4 24

2 5390 A (CPU) sub card is not online, but has been configured by database

2 24

2 5391 OMP Gateway IP in BootCfg.ini file different from Dbs

2 24

2 5392 OMC Server IP in BootCfg.ini file different from Dbs

2 25

2 5393 Gateway Mask in BootCfg.ini file different from Dbs

2 25




Alarm Code


Page No.

2 5394 OMP config was changed 2 17

2 5395 The state of out port is down 2 26

5 5396 Inner media VLAN communication abnormal.

2 84

2 5632 Hard disk utilization ratio threshold warning

1 26

2 5633 The board's hard disk is bad 1 27

2 5634 TRUNK port down. 1 68

2 5635 The board's ENUM switch is turned on

1 3

1 5636 SMBUS error 1 3

2 5637 Back card error, Back and frontal card do not match

1 17

2 5638 LVDS signal is unlocked 2 27

1 5639 The bit error rate in a fiber is high.

2 6

2 5640 FPGA is abnormal 2 27

2 5641 The port link breaks. 1 18

2 5642 The hard disk’s reliability reduces.

2 28

2 5643 Phase lock loop work mode is abnormal.

3 47

2 5644 The channel in the sub-card is abnormal

3 48

2 5645 Sub-card is abnormal. 1 18

2 5646 Phase lock loop is unlocked 1 18

2 5647 The bit error rate in E1 link is high.

1 19

2 5648 Ctrl Port to UIM Error. 1 73

5 5649 Port not work on the configured mode.

2 86

2 5650 MAC address of the board conflicts

1 62

2 5651 OSS check out that IP&MAC address of the board conflicts.

1 69

2 5652 A Class Error of SETS. 1 68

2 5653 B Class Error of SETS. 2 68

2 5654 Powing Error of SETS. 1 66

2 5655 DSP automatic Check abnormal.

2 70

2 5656 Input clock of subcard is lost. 2 73




Alarm Code


Page No.

2 5658 Loop error of LVDS 129 time slot.

2 64

2 5659 Tone resource Board DSP Tone Type differ

2 63

2 5890 Function Epld Version Update Fail.

4 70

2 5891 BOOT/EPLD upgrade information.

4 66

2 5892 BOOT version synchronization information.

4 66

1 6400 The Status of Cx29704 is ERR 3 16

2 8256 SCCP Connect ID Less Than1000

4 74

2 14592 Dual attribution office has been blocked.

3 64

2 14593 Dual attribution link has been blocked.

3 65

2 14594 Dual attribution association has been blocked.

3 65

2 15360 The micro code is abnormal 1 19

2 15616 Receive bad packets 3 48

1 15873 The CSIX receptivity examination error surpasses the threshold.

1 3

2 15874 The link level flow control is unable to eliminate.

1 20

2 16640 2350 receive hardware error 2 73

2 18944 PVC fault 3 49

2 19200 Far End is in starting-up state 2 28

1 19201 FE Reports Unacceptable Configuration Parameters (M size)

2 6

1 19202

FE reports unacceptable configuration parameters(the symmetry between operation and configuration)

2 7

1 19203 FE reports unacceptable configuration parameters(IMA agreement version number)

2 8

1 19204 FE reports unacceptable configuration parameters

2 8

2 19205 FE is in blocked state 2 28

2 19206 FE is in insufficient links State 2 29

1 19207 NE is in Config_Aborted State 2 9




Alarm Code


Page No.

2 19208 FE transmit clock mode is different than the NE transmit clock mode

2 29

2 19209 NE Group is in insufficient links State

2 30

2 19210 FE RXLSM is in unusable State 2 73

2 19211 Implementation specific TX fault declared at the NE

2 30

2 19212 FE TX is mis-Connected 2 31

1 19213 Persistence of a LIF(Loss of IMA Frame) defect at the NE

2 9

1 19214 Persistence of a LODS(Link Out of Delay Synchronization) defect at the NE

2 10

1 19215 Persistence of an RDI-IMA defect at the NE

2 10

2 19216 Implementation specific Rx fault declared at the NE

2 31

2 19217 Implementation specific Rx failed declared at the NE

2 31

2 19218 NE TX is mis-Connected 2 32

2 19219 FE TXLSM is in Unusable State 2 32

2 19221 FE RX LSM can't turn to active state

2 71

2 19456 All HSSLS are out of sync 1 20

2 19712 APS protection channel mismatch

2 33

2 19713 APS protection mode mismatch

2 33

1 19714 APS reset 2 11

1 19968 L2FWDTBL get DB info fail 2 11

1 19969 L2FWDTBL get SCS info fail 2 12

1 19970 Resource board can not get L2FWD's information from UIM board

2 12

2 22784 The BFD session is Down 3 67

2 23296 The communication flow over alarmed threshold value

2 72

1 25600 Switch of Connection Check is turned off.

4 16

2 25601 Error connection on 129ts of T-net board.

2 64




Alarm Code


Page No.

5 25856 Rack temperature is higher than high threshold

3 79

5 25857 Rack temperature is lower than low threshold

3 80

5 25858 House temperature is higher than high threshold

3 80

5 25859 House temperature is lower than low threshold

3 80

5 25860 Voltage is higher than high threshold

3 81

5 25861 Voltage is lower than low threshold

3 81

5 25862 Humidity is higher than high threshold

82

5 25863 Humidity is lower than low threshold

3 82

5 25864 Fan is lower than low threshold

3 83

5 25865 Alarm because of Door 3 83

5 25866 Alarm because of Fume 3 83

5 25867 Alarm because of infrared 3 83

5 25868 Alarm because of thunder 3 84

2 26112 CLKG 32M output clock lost 2 34

2 26113 CLKG 32M8K output clock lost 2 34

2 26114 CLKG 16M output clock lost 2 34

2 26115 CLKG 16M8K output clock lost 2 34

2 26116 CLKG PP2S output clock lost 2 35

2 26117 CLKG PP2S clock base lost 2 35

2 26118 CLKG clock 16CHIP base lost 2 35

2 26127 Clock base lost third level(low)alarm

3 52

2 26128 Clock base lost second level(middle)alarm

2 42

2 26129 Clock base lost first level(high)alarm

1 22

2 26624 Spending of DSP has reached a dangerous degree

3 66

2 26626 DSP over load High Alarm 2 63

2 26627 DSP over load Middle Alarm 3 63

2 26628 DSP over load Low Alarm 4 63




Alarm Code


Page No.

4 50001 Expired Password Alarm 3 78

4 50002 Expired Password Notify 4 78

2 8392448

Abis Link Down. 2 72

1 8392705

SNTP client fails to get the network clock

3 16

2 8393985

OSS communication link off 2 42

3 8393988

Communication between MP and OMP error

2 77

2 8398848

SCCP SSN is invalid 1 52

2 8399104

SSCS congest 3 52

2 8399105

SSCS OVERLOAD 3 53

1 8399872

MTP2 Link sending traffic overload

2 13

1 8399873

MTP2 Link receiving traffic overload

2 13

2 8400128

Alarm of office unaccess from mtp3

2 43

2 8400129

Alarm of link unavailability 3 53

2 8400130

Cluster Unaccess 2 43

1 8400131

Mtp3 link congest 2 14

2 8400384

Alarm of office unaccess from m3ua

2 44

2 8401152

SUA subsystem is invalid 3 54

2 8401153

Cannot reach the office 2 45

2 8402177

M2PA link is broken 3 54

2 8402688

Association is congestive 3 55

2 8402690

Association Broken down 2 45

2 8402944

STC office unaccess. 2 71




Alarm Code


Page No.

2 8402945

STC office congest. 2 72

3 8407040

PPP_UID link down 2 74

3 8407041

PPP link down 2 75

1 8407296

The HDLC is unusable 4 61

1 8407297

The UID bind is unusable 4 62

2 8417537

Associate Path Break 3 71

1 16782146

Block or unblock office is not success

3 16

1 25166848

UTS HOST power fail 2 14

1 25166849

UTS HOST request NPL2TAB timeout

2 14

1 25166850

UTS HOST request security variable of timeout

3 15

4 25166851

INLP fail to request SCTP's load balancing table

3 77

3 25168128

IUA association is broken 3 76

3 58720256

The link between NE and server breaks

3 77





Tables

Table 1 Chapter Summary ....................................................i

Table 2 Typographical Conventions ....................................... ii

Table 3 Mouse Operation Conventions ................................... ii





Index

Association............ 45, 55, 100 clock .................................74 Frame ................ 9, 23, 60, 98 HW ........................ 11, 40, 95 Querying Alarms

Alarm Code ....................93 Alarm Level ................ 2, 93

Reset ..................... 11, 18, 48 Server

OMC ..............................25 Server

OMC ........................ 1, 2, 5 Server

OMC.............................. 95 Server

OMC.............................. 95 Server

OMC.............................. 95 SIGTRAN

AS ...........................44, 45 ASP............................... 44 SIO............................... 44

SSN......................45, 52, 100 Sub-card ......................18, 96 System Management

Restore.......................... 16

Documents

ZTE Media Gateway ZXC10