ZTE Media Gateway 2nd

ZXC10 MGWcdma2000 Media Gateway

Alarm and Notification Information (2)

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. 30, 2008 R1.0 sjzl20080261 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 (2)

Product Version V2.04.20 Document Revision Number R1.0

Serial No. sjzl20080261 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 Mechanism of Notification Generation ......................................1 General Flow of Handling Notifications......................................2

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

Notification Information..................................................3

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

Handling Error Notification................................................3 Load Error ...........................................................................3 DBs Table Load Failure ..........................................................4 Master to Slave Sync Failure...................................................4 OMP to MP Sync Failure .........................................................4 MP to PP Sync Failure ............................................................5 Failure of Saving One Table ....................................................5 DBs File-Buffer Overflow ........................................................5 If the Times of Sending Message go beyond the Limit, OAM Back Receives Notification Information about the Message .................6 Save File Fail in Master or Slave Path, Inform with Failed Path.....6 Loading Version-Table from File-Reg is Fail because of Nonexistent Domain or Incompatible Domain Type......................................7 DBS Require Configuration Failed ............................................7

SCCP GT Translation is Error .................................................. 7 NID is Unequipped................................................................ 8 NID Translation of NID Failed................................................. 8 ISNI Constrained Route Repeat .............................................. 8 ISNI cannot Support Route Indicator....................................... 9 NID Identify Failure .............................................................. 9 Registers Successfully........................................................... 9 Registration Defeat............................................................... 9 Failed to Configure Multi-channel Controller ............................10 Failed to Configure Digital Switch Chip ...................................10 Failed to Get Config Information from Database.......................10 SUA GT Translation Failed.....................................................11 SIG_IPI Transmits Packets Abnormal .....................................11 IP Fail to Get Route Table Head or Entry .................................11 Deletion Static Routing Clause defeat .....................................12 IP Create or Enable IFB Fail ..................................................12 EPU down...........................................................................12 EPU Remove.......................................................................13 IP OPR Static RTE Fail: Add SRTE. .........................................13 TCP Received RST Packet .....................................................13 PPP Detect Wrong While Receive UidIpInfoAck.........................13 PPP Detect Wrong While Receive BSCIP from DB......................14 PPP Detect Wrong While Receive UID UPD Config from DB.........14 Failed to Initialize PCM7389 ..................................................14 The Configuration Data about UID/HDLC Received by LDM from Database Error ...................................................................15 Configure Port Failed ...........................................................15 Creat Inner (Inter) Unilateral (Bi-Directional) Connection (Multi) PVC Failed..........................................................................16 Delete Inner (Inter) Unilateral (Bi-Directional) Connection (Multi) PVC Failed..........................................................................17 IMA Group Related Operation Failed.......................................17 IMA Link Related Operation Failed..........................................17 SFrame Mode Error is Serious ...............................................18 CFrame is doffed Because of Horizontal Check Error .................18 CFrame is doffed because of Vertical ......................................18 Cframe is doffed because of not Integrity................................19 Cframe is doffed because It is not Valid ..................................19 Cframe is Losted because of its Length is not Valid...................19 Frame is Losted because of out of Order .................................20

Frame is Losted because of CRC Check Error........................... 20 Configuration IXP2400 Failed................................................ 20 Configuration VSC872 Failed................................................. 21 Aps Switch......................................................................... 21 L2FWDTBL Init Fail.............................................................. 22 L2FWDTBL Init UIM Media eth Fail ......................................... 22 Brs Main Configure Request Timeout...................................... 22 Brs Main RPU Register Timeout ............................................. 23 Brs Protocol Process Power-on Fatal Failed.............................. 23 IP OFFLINE SET: Add Interface Address Failed ........................ 23 IP OFFLINE SET: Set DB Failed ............................................. 24 IP OFFLINE SET: Delete the IP Address Failed ......................... 24 IP OFFLINE SET: Add IP Route Failed ..................................... 24 IP OFFLINE SET: Delete Route Failed ..................................... 25 IP OFFLINE SET: Not Ethernet Interface ................................. 25 IP OFFLINE SET: a Same Prefix IP Address Exist...................... 25 IP OFFLINE SET: The Input Parameter is Null .......................... 25 IP OFFLINE Cfg: The IP Address Already Exists........................ 26 IP Offline Cfg: The IP Address Already Exists .......................... 26 Invalid Mask or Prefix .......................................................... 26 ARP Allocate Memory Instance Fail ........................................ 27 ARP Allocate Memory Fail for ARP Cache................................. 27 IP Address Collided with the Others ....................................... 27 Found Duplicate MAC Address in the ARP Packet...................... 27 RIP Configure Neighbor Fail .................................................. 28 RIP Interface Authentication Fail ........................................... 28 RIP Interface is Disabling ..................................................... 28 RIP Interface is Enabling ...................................................... 29 The Router Id in the HELLO Package which OSPF Received is same as the Router id of this ........................................................ 29 OSPF Virtual Interface Configure in Error ................................ 29 OSPF Interface Configure in Error.......................................... 30 OSPF Virtual Interface Authentication Fail ............................... 30 OSPF Interface authentication Fail ......................................... 30 Create BGP Instance Fail...................................................... 31 BGP Create Neighbor Fail ..................................................... 31 BGP Can’t Get TCB for Passive Listen ..................................... 31 BGP Can’t Get TCB for Active Connect.................................... 32 BGP Enable Passive Listen TCB Fail ........................................ 32

BGP Enable Active Connect TCB Fail .......................................32 BGP Add Neighbor to Group Fail ............................................32 BGP Interface is Down, and Neighbor Disconnects....................33 BGP Interface Address Changed, and Neighbor Disconnects.......33 BGP Neighbor Read Receive Buffer Fail ...................................33 BGP Neighbor Hold Timer Expired ..........................................34 Courier Create BGP Instance Fail ...........................................34 Courier Enable OSPF by the RTR_ID Fail .................................34 Courier Synch IP Route Table Error ........................................35 MAC Addreses Conflict While Computing or Deleting It..............35 Alarm Pool is Over in OAM Alarm Manager Process ...................35 OAM Agent Receive Refuse Alarm Inform................................36 Board Self-Checking Defeat ..................................................36 Board Initialization Defeat ....................................................36 Half Fixedly Connection Configuration Data is Error ..................37 Powering Information about Basic Process ..............................37 Base Invalid Reason Changed ...............................................37 Fail to Reset MSCe...............................................................38 Fail to Reset Circuit in MSCe .................................................38 Block CIC Failed ..................................................................38 Unblock CIC Failed ..............................................................38 Fail to Use Termination ........................................................38 BCM Long Bill .....................................................................39 IUA Receives the Notify Message ...........................................39 IUA Receives Error Message..................................................39 Base Station Erase ..............................................................39 The Process is in the Dead Lock State ....................................40

Device Notification ........................................................ 40 Trunk slip...........................................................................40 Global Underflow.................................................................40 Global Overflow ..................................................................41 Board Abnormally Resets......................................................41 HSSL Break Off between GLI and PSN ....................................41 485 Offline Set Fail ..............................................................41 DSP Runtime Error ..............................................................42 Backboard Switch Set Change ...............................................42 Version Error Occur on This Board .........................................42 Doc Space is not Enough to Save Version-File..........................43 IDE Files Synchronization Information ....................................43

SSCS no Response .............................................................. 43 M2PA Link is Congested ....................................................... 44 M2PA Processor is Outage .................................................... 44 Inform of the Change of ASP Status....................................... 44 Inform of the Change of AS Status ........................................ 45 Receiving ERROR Message ................................................... 45 Receiving NTFY Message ...................................................... 45 Association Establish Fail...................................................... 45 INFORM_MCS_2400_CONFIGERROR ...................................... 46 Configuration Data Received from Database is Abnormal or Error Happened when Updating Configuration Data.......................... 47 The NP C5 can't Get PVC from DBS or the PVC can't be Configured in C5's TLU ........................................................................ 48 The NP C5 Received AAL2 Establishing/Release Message, but C5 Operation Failed ................................................................. 48 Registers Successfully ......................................................... 49 IP Has no Match EPU Global Port ........................................... 49 ABPM board's PMC7389 is Reset............................................ 49 IP OFFLINE SET: The Interface is not Exist or is not an Ethernet Interface ........................................................................... 50 IP OFFLINE SET: No IP Unnumbered First ............................... 50 IP OFFLINE SET: Invalid Host Address.................................... 50 IP OFFLINE SET: Invalid Next Hop......................................... 51 IP OFFLINE SET: Inconsistent Address and Mask ..................... 51 IP OFFLINE SET: No Matching Route to Delete ........................ 51 IP OFFLINE SET: Next Hop Conflict ........................................ 51 IP OFFLINE SET: Next Hop not Directed ................................. 52 IP OFFLINE SET: IP Address not Exists................................... 52 IP OFFLINE SET: MAC beyond Valid Space .............................. 52 IP OFFLINE SET: DB MAC Operation-Type Invalid .................... 53 IP OFFLINE SET: Invalid IP Broadcast Address ........................ 53 IP OFFLINE SET: The Number of IP Address on this Port cannot Exceed 4 ........................................................................... 53 OSPF Virtual Link State Changed........................................... 53 OSPF Interface State Changed .............................................. 54 OSPF Virtual Neighbor State Change...................................... 54 OSPF Neighbor State Change................................................ 54 LSDB Overflow ................................................................... 55 OSPF Found LSAs with Same lS_ID........................................ 55 BGP Neighbor’s FSM Error .................................................... 55 BGP State Change............................................................... 56

Half-Fixed Connection is Changed Abnormally .........................56 Disk is Full .........................................................................56 GE Port Config not Match......................................................57 UIM CS Changeover.............................................................57 Master and Slave Change over ..............................................57 FE Port State Change from Up state to Down...........................58 UIM TFS Port State Change...................................................58 Board's Workmode is not Supported.......................................58 CLK Base Change ................................................................59 CLKG Frequence Base Quality Changed ..................................59 CLKG Work Mode Changed ...................................................59 Circuit is not Set Up in MSCe.................................................60 OMP Restart .......................................................................60 Exception of CPU Loop .........................................................60 Tone DSP CPU and DSP Version Differ ....................................60 HP Server Power Supply Power off .........................................61 ABPM Board's PMC7389 is Reset ............................................61 HP Server Power Supply Power ON ........................................61 Alarm When Data Configuration MNIC/2 Physical Board-related is Error .................................................................................61 Error Occurs During MCU Running..........................................62 Timer for ISIS Creates Fail ...................................................62 ISIS Hello Packet Authentication Fail ......................................62 ISIS LSP Packet Authentication Fail........................................62 ISIS SNP Packet Authentication Fail .......................................63 Ignored Packet for Differ Interface Version..............................63 Stack Overflow ...................................................................63 Configure BFD Session Fails ..................................................63 Ec of Index Configed as Signal Link be Informed Enable............64 Tone File System Initialization Failure.....................................64 Setting Work Mode of Outport is Forbid in This Board ...............64 Multi-CPU Board ,Unittype in R_unit is Inconsistent with First-CPU's Functype in R_CPUVERMAPE ........................................64 DBS Power on Fail ...............................................................65 User Office of M3UA States Modify Inform...............................65 RIP Failed to Create RIP Instance ..........................................65 OSPFV3 Routerid Conflict......................................................66 OSPFV3 Virtual Interface State Change...................................66 OSPFV3 Interface State Change ............................................66 OSPFV3 Virtual Interface Configure Error ................................66

OSPFV3 Interface Configure Error.......................................... 67 OSPFV3 Virtual Neighbor State Change .................................. 67 OSPFV3 Neighbor State Change ............................................ 67 OSPFV3 Routerid Invalid ...................................................... 67 OSPFV3 Instance Create Failure ............................................ 68 80G Chip Error ................................................................... 68 CS Fiber Change Over ......................................................... 68 Switch Version Fail .............................................................. 68 OMP Version Check Infomation ............................................. 69 DBS MALLOC Memory Fail .................................................... 69 RIPng Interface is Disable .................................................... 69 RIPng Failed to Create RIP Instance....................................... 69 LAN91 Error ....................................................................... 70 Some HSSLS are Out of Sync ............................................... 70 IP OFFLINE SET: NO IP Unnumbered First .............................. 70

Communication Notification ............................................ 70

Work Mode Difference with DB Trunk Configuration.................. 70 TCP Connection Aborted....................................................... 71 IUA AS State Transform....................................................... 71 IUA ASP State Transform ..................................................... 71

Appendix A.....................................................................73

Abbreviations.................................................................73

Appendix B.....................................................................79

Collection of Notification Information...........................79

Tables.............................................................................87

Index..............................................................................89


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

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 telecommunications technology. 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, Notification Information

Provides notification information, including alarm code, alarm name, handling methods, etc.

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

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

Notification management system implements centralized monitoring on the running status of the whole system. The system collects in real time abnormal information of each part, e.g. each board, link, database, server, and other necessary units. When a notification occurs, the notification management system generates notification message to inform the maintenance engineer about the occurred event. So it is easy for the engineers to hsndle that event to ensure the stability of the system.

Mechanism of Notification Generation

A notification occures when there is a fault or abnormal event. Notification system monitors the whole system in real time. When an event occurs int any part of the system, the notification service process of the applied server sends messages to OMC server. Thus generates notification information.

A notification is originated against an event. Notification information occurs during the daily running of the system to aware the maintenance personnel about the system running status. 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 this information. Notification stands for occurrence of an event, but not of a potential danger. Besides, notification information does not need subsequent restoration.

Description

Description


2 Confidential and Proprietary Information of ZTE CORPORATION

General Flow of Handling Notifications

Notification level indicates the level of the notification. Notification information is prompting information displayed by OMC when the system finds an eception during running. Notification usually lasts for a specific time and disappears after clearing the corresponding exception. Notifications should be cleared in time, otherwise, the result may be critical.

Generally, notifications are cleared according to the following flow:

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

2. Analyse the cause for the notification and effect on the system.

3. Decide the handling method or follow the hints given in the next chapter to handle the notification.

4. Handle the notification.

Description


C h a p t e r 2

Notification Information

Overview Notification information is divided into the following classifications:

Handling error-related notification information

Device-related notification information

Communication-related notification information

Service quality-related notification information

Environment-related notification information

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

Handling Error Notification Load Error

Notification information has the following contents:

Notification code: 5701

Notification description: The version failed to be loaded.

The board can’t start up.

The board failed to load the version from OMP during RELEASE BOOT because the version does not exist in OMP or the database configuration is incorrect.

Check the version exists on the OMP or the database configuration is incorrect and then load the version again.

Description

Content


Influence

Cause

Handling



DBs Table Load Failure



Notification description: When the foreground and the background data is synchronized, the MP loads data but a datasheet is failed to be loaded.

The data configuration on the background is incorrect; therefore the datasheet of the foreground fails to be loaded.

Check the data configuration and transfer the data again.

Master to Slave Sync Failure



Notification description: The master and the slave datasheet fail to be synchronized.

The failure in synchronizing the master datasheet with the slave fails dut to inconsostentsy in the version of master and salave board. It can be further analysed from the returned error ID.

Handle the notification referring to the following operations:

Check whether the versions of the master board and the slave one are consistent.

Check whether the master link and the slave one are normal.

OMP to MP Sync Failure



Notification description: The data synchronization from OMP to the MP fails.

OMP can not update online.

The MP generates a data synchronization failure notification message.

Modify the data according to the notification information and retransmit them.


Cause

Handling


Cause

Handling


Influence

Cause

Handling

Chapter 2 Notification Information


MP to PP Sync Failure



Notification description: The data synchronization from the MP to PP fails.

The MP synchronizes data to the PP. The PP gives a notification message, and the data synchronization failed.


Check the data configuration.

Check the link status between the MP board and PP board.

Failure of Saving One Table



Notification description: A single data table failed to be saved.

The system data restores after restarting if data saving fails.

When the table structure is inconsistent with that in ZDB, or the ZDB file structure is incomplete, a single data table fails to be saved.

Save all the tables through the background.

DBs File-Buffer Overflow



Notification description: The capacity of the memory file buffer is insufficient, and the subsequent transferred records are discarded.

The records overflowed would be discarded.

The transferred data records exceed the maximum capacity of the table, and the capacity of the foreground memory file buffer is insufficient.

Check whether the background data configuration exceeds the maximum capacity of the table. If yes, re-configure the data and re-transfer it.


Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



If the Times of Sending Message go beyond the Limit, OAM Back Receives Notification Information about the Message



Notification description: If the notification for the data configuration modification (P_notify process) fails three time, this notification occurs.

The data in the database is inconsistent with the board or module which the destination process dwells on.

If the notification for the data configuration modification (P_notify process) fails three time the target unit is abnormal.

Check target unit status, or the manual data synchronization is necessary.

Save File Fail in Master or Slave Path, Inform with Failed Path



Notification description: The data saving in one of the active and the standby directories fails. The additional message contains the path of saving failure.

The board can not get right data from ZDB in disk after the board reboots.

The notification occurs due to the following causes:

The disk is full.

The media is faulty.


If the disk is full, clear up the disk to create enough available space.

If the disk is faulty, maintain or replace it.


Influence

Cause

Handling


Influence

Cause

Handling



Loading Version-Table from File-Reg is Fail because of Nonexistent Domain or Incompatible Domain Type



Notification description: Tthe board memory version table has newly-added fields or type-incompatible fields as compared to ZDB, which causes failure in loading the version table records.

The old records in version table and RELEASE files could be lost.

if the new version has newly-added fields or type-incompatible fields while OMP loads the new version, and, the version table should can’t be loaded.

This phenomenon is normal during the version upgrade. Use the latest background version tool to re-configure the version data.

DBS Require Configuration Failed



Notification description: The database configuration request is rejected.

The database configuration request is rejected due to inconsistent module type and the NE type and the data should be loaded at the local end.

Confirm the module type and the NE type. If they are inconsistent delete CfgTable.ZDB and restart the board.

SCCP GT Translation is Error



Notification description: GT translation failure.

Message sending/receiving of this time fails.


There is no signaling point code and no GT number is configured.


Influence

Cause

Handling


Cause

Handling


Influence

Cause



The GT number indicator is incorrect.

The corresponding subsystem of the called GT number is unavailable.

The corresponding signaling point of the called GT number is inaccessible.

The called GT number is not configured in the database.

Check the GT configuration, or the statuses of the office direction and the subsystems.

NID is Unequipped



Notification description: NID not configured.

When the NID is translated, it is not configured in the database.

Correctly configure the NID in the database.

NID Translation of NID Failed



Notification description: NID translation failure


The database fails to translate the NID (which frequently happens).

The database is exceptional.

Correctly configure the NID in the database.

ISNI Constrained Route Repeat



Notification description: There is repeated route information in the ISNI.

There is repeated route information in the ISNI provided by the upper layer.

The SCCP upper-layer user should correctly enter the ISNI parameter, without repeated route information.

Handling


Cause

Handling


Cause

Handling


Cause

Handling



ISNI cannot Support Route Indicator



Notification description: The ISNI does not support the route function.

The ISNI does not support the route function.

The upper-layer user should correctly enter route function indicator.

NID Identify Failure



Notification description: INID route prompt failure.

The NID route prompt data is not configured correctly.

There are too many message path NIDs, so it is suggested to correctly configure the NID data.

Registers Successfully



Notification description: The MGW has been registered.

The MGW has been registered.

No special processing is required.

Registration Defeat



Notification description: The MGW is not registered in the MGC .

Calls can not be initiated.

The system is just powered on, the office direction inaccessible, or there is an error in the configuration.

Check the SERVER and the MGW configurations.


Cause

Handling


Cause

Handling


Cause

Handling


Influence

Cause

Handling



Failed to Configure Multi-channel Controller



Notification description: Failure in configuring the MTP2 multi-channel controller.

Related links could not be available.

The multi-channel controller of the MTP2 processor failed to be configured.

Replace the sub-card of the corresponding SPB board.

Failed to Configure Digital Switch Chip



Notification description: Failure in configuring the MTP2 switching chip.

Related links become unavailable.

The MTP2 switching chip failed to be configured.

Replace the sub-card of the corresponding SPB board.

Failed to Get Config Information from Database



Notification description: MTP2 failed to get the configuration information from the database.

Related links become unavailable.

MTP2 failed to get the configuration information from the database.

Check the main processor on the foreground runs normally.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



SUA GT Translation Failed



Notification description: GT translation fails.

Signaling data can’t be sent and received from the relevant subsystem.

Causes leading to the notification may include:

When the called address has no signaling point code and is not configured with GT codes.

The input GT code indicator of the called address is incorrect.

The corresponding subsystem of the called GT code is unavailable.

The corresponding signaling point of the called GT code is unreachable.

The called GT code is not configured in the database.

Check the GT configuration or the statuses of the office direction and the subsystem (SSN) (by using the probe).

SIG_IPI Transmits Packets Abnormal



Notification description: There is an exception when the SIG_IPI forwards the service message.

SCTP/SIP link may be influenced.

There is an exception when the SIG_IPI forwards the service message.

Restart the board.

IP Fail to Get Route Table Head or Entry



Notification description: Failed to get the route table head or entry.


Influence

Cause

Handling


Influence

Cause

Handling




It is failed to get the route table head due to wrong configuration parameters.


Configure route information again.

Check whether the configured route parameters are correct.

Deletion Static Routing Clause defeat



Notification description: Failed to delete the static route entry.

Equivalent routes become invalid.

It is failed to delete the static route entry that could be due to wrong configuration parameters.

Check whether the configured route parameters are correct.

IP Create or Enable IFB Fail



Notification description: Failed to create or activate the IFB.

Dynamic routes can not be activated.

Failed to create or activate the IFB.

Check whether the size of the configuration file exceeds the configured capacity.

EPU down



Notification description: The RPU receives the message of EPU port down reported by the SCS.

The RPU receives the message of EPU port down reported by the SCS.

Check the status of the reported board.。

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Cause

Handling



EPU Remove



Notification description: The RPU receives the message reported by the SCS that the EPU board has been deleted.

Protocol stack information of this board could be cleared.

The RPU receives the message that the EPU board has been deleted.

Check whether the board has been correctly deleted.

This notification may clear all the protocol stack messages on the board.

IP OPR Static RTE Fail: Add SRTE.



Notification description: Failed to add the static route entry.

Equivalent routes become invalid.

It is failed to add the static route entry.

Check that the configured route parameters are correct.

TCP Received RST Packet



Notification description: The TCP receives RST message.

The TCP receives the RST message from the opposite end.

Check the reason why the TCP module on the opposite end reset the link.

PPP Detect Wrong While Receive UidIpInfoAck

The notification information includes:



Influence

Cause

Handling

Precaution


Influence

Cause

Handling


Cause

Handling




Notification description: PPP detects wrong information while applying UID IP from the database.

Powering on protocol stack process fails.

The database configuration is not correct.

Re-configure UID IP.

PPP Detect Wrong While Receive BSCIP from DB

The notification information has the following contents:


Notification description: PPP detects wrong information while receiving BSCIP from the database.


Powering on protocol stack process fails.

Re-configure BSC IP.

PPP Detect Wrong While Receive UID UPD Config from DB



Notification description: PPP detects wrong information while receiving UID UPD information from the database.


Re-configure the database data.

The notification disappears.

Failed to Initialize PCM7389



Notification description: PMC7389 initialization fails.

There is error with the memory, chip configuration, etc.

The system may get down.

Reset or replace the board.

Influence

Cause

Handling


Cause

Influence

Handling


Cause

Handling

Verification


Cause

Influence

Handling



The Configuration Data about UID/HDLC Received by LDM from Database Error



Notification description: UID/HDLC configuration in database is incorrect.

Accessing the database timeout is usually caused by message loss due to the broken communication link, or the database configuration error may lead to this notification.

Newly configured data is unavailable.

Handle the notification referring to the following actions:

Check the the broken communication link. Ask SCS to diagnose this fault.

If the database configuration has error, check the background data, and then check foreground data in OMP is correct through probe.

Configure Port Failed



Notification description: Failed to configure the port.

ATM can not work.

This notification may be caused due to the following:

Problem in the chip port.

Wrong port rate configuration.

There are PVCs on the port when the port is deleted.

The MAXVPI or the MAXVCI of the port is illegal.

The number of PVCs on the board exceeds 62K.

Check the configuration parameters of the port, and the following points should be noted.

Confirm the port rate. The port rate can not exceed the maximum band width ofof port when creating the port. When modifying the port rate, the newly-set port rate must not be lower than the current one.

Confirm there is no PVC configuration on the port when the port is deleted.


Cause

Influence

Handling


Influence

Cause

Handling



Confirm the MAXVPI and the MAXVCI values are legal. The values must be nth power of 2 on IMAB and APBE. For the MAXVCI, 6=<N<=14; for the MAXVPI on the UNI port, 1=<N<=8; for the MAXVPI on the NNI port, 1=<N<=9.

Confirm that the number of PVCs of the whole board does not exceed 62K after configuring this port.

Creat Inner (Inter) Unilateral (Bi-Directional) Connection (Multi) PVC Failed



Notification description: Failed to create the inner-(inter-)board signal-(both-) way unicast (multicast) PVC.

The upper link is broken.

The causes leading to the notification may include:

The PVCID is illegal.

The PVC crosses the board.

The incoming direction and the outgoing direction of the both-way PVC conflicts with each other.

The flow parameters are illegal.

The VCI is less than 32.

The port is illegal.

The service type mismatches with the flow type.

The PVC that is being created already exist.

Check the following points:

The range of the PVCID is 1~12600, and the incoming direction and the outgoing direction of the PVC should be on the same board.

Confirm that the incoming and the outgoing VPIs of the both-way VP connection do not conflict with each other, and the incoming and the outgoing VPIs of the both-way VP connection do not conflict with the VCI.

Confirm that the flow parameters of the PVC on the IMAB and the APBE are in the flow range of the APC chip.

The VCI value must be greater than or equal to 32.

Confirm that the PVC-related port configuration is correct and that the VPI and the VCI of the PVC do not exceed the MAXVPI and the MAXVCI of the port respectively.


Influence

Cause

Handling



Confirm that the service type mismatches with the flow type.

Confirm that the to-be-created PVC does not exist.

Delete Inner (Inter) Unilateral (Bi-Directional) Connection (Multi) PVC Failed



Notification description: Failed to delete the inner-(inter-)board single-(both-) way unicast (multicast) PVC.

The upper link is broken.

It is failed due to bottom-layer chip of the faulty board.

If the bottom-layer chip works normally. Restart or replace the board.

IMA Group Related Operation Failed



Notification description: The IMA-group-related operations initiated by the background fail.

The specified resource does not exist on the foreground.

In general, the reason is that the group parameters are incorrect when the operations are initiated.


Check the parameters related with the initiated operations are correct.

Check the steps in the operations are legal.

IMA Link Related Operation Failed



Notification description: The IMA-link-related operations initiated by the background fail.

The specified resource does not exist on the foreground.


Influence

Cause

Handling


Influence

Cause

Handling


Influence



In general, the reason is that the link parameters are incorrect when the operations are initiated.

Handle the notification referring to the followings:

Check whether the parameters related with the initiated operations are correct.

Check whether the steps in the operations are legal.

SFrame Mode Error is Serious



Notification description: The number of SFrames including frame format mode error exceeds the threshold.

The system may discard some packets.

Maybe there is a problem in the 872 chip.

Restart the board.

CFrame is doffed Because of Horizontal Check Error



Notification description: The number of CFrames discarded due to horizontal check error at the CSIX port N exceeds the threshold.



If the notification continuously occurs several times, restart the board.

CFrame is doffed because of Vertical



Notification description: The number of CFrames discarded due to vertical check error at the CSIX port N exceeds the threshold.


Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Influence





Cframe is doffed because of not Integrity



Notification description: The number of CFrames discarded due to incomplete frame at the CSIX port N exceeds the threshold.




Cframe is doffed because It is not Valid



Notification description: The number of CFrames discarded due to invalid frame type at the CSIX port N exceeds the threshold.




Cframe is Losted because of its Length is not Valid



Notification description: The number of CFrames discarded due to invalid frame length at the CSIX port N exceeds the threshold.

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling







Frame is Losted because of out of Order



Notification description: The number of frames discarded because out of order exceeds the threshold.




Frame is Losted because of CRC Check Error



Notification description: The number of frames discarded because CRC check error exceeds the threshold.




Configuration IXP2400 Failed



Notification description: The flow control failed to perform initialization configuration on some flow control tables of the 2400.

TM process can’t power on successfully, and consequently the board may reboot.

Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Influence



It is failed to invoke the table operation interface.

Restart the board.

Configuration VSC872 Failed



Notification description: The flow control failed to perform initialization configuration on some flow control parameters of the 872.

TM process can’t power on successfully, and consequently the board could reboot.

It is failed to invoke the OSS interface.

Restart the board.

Aps Switch



Notification description: Aps switchover occurs.

There are IOS notifications in the optical interface:

The ENUM is lighted

The clock is lost

The HW and the FE are broken

The opposite end initiates switchover

The background initiates the forcible switchover.

If it can be judged from the additional information that the switchover is from the protective board to the working board, check the flowing two cases of the working board. If the switchover is from the working board to the protective board, check the status of the protective board.

Switchover success: Check whether the following :

Check IOS notifications in the optical interface

Check the ENUM light

Check the clock

Check the HW and the FE

Check the opposite end initiates switchover the background initiates the forcible switchover.

Switchover failure:

Cause

Handling


Influence

Cause

Handling


Cause

Handling



Check whether the standby board is reset

Whether the ABPE board is halted

Whether the background initiates the forcible switchover due to hardware problem in the APBE board

L2FWDTBL Init Fail



Notification description: Failed to initialize the level-2 forwarding table.

Services may be interrupted.

Failed to allocate the memory and failed to get the physical address of this board.

Restart the board.

L2FWDTBL Init UIM Media eth Fail



Notification description: Failed to initialize the Ethernet port on the media plane of the UIM board.

UIM can not send link-check packet.

It is failed to initialize the Ethernet port on the media plane of the UIM board.

Restart the board.

Brs Main Configure Request Timeout



Notification description: The timer of the protocol stack for requesting for the system configuration information from the background database and the configuration data times out.

There is no response to the protocol configuration request from the MP and RPU of the configuration module and the configuration request timer times out for 3 times.

Check the MP and the RPU of the configuration module work normally.


Influence

Cause

Handling


Influence

Cause

Handling


Cause

Handling



Brs Main RPU Register Timeout



Notification description: Timeout when registering in the RPU.

The protocol stack could not enter working state.

There is no response from the EPU registering the RPU, and the timer times out for 3 times.

Check whether the MP and the RPU of the module configuration work normally.

Brs Protocol Process Power-on Fatal Failed



Notification description: The power-on of the protocol stack process failed

The protocol stack could not enter working state.

There is no response when the board is registered in the RPU, and the timer times out for 3 times.

Restart the board.

IP OFFLINE SET: Add Interface Address Failed



Notification description: IP offline configuration: Failure in adding an interface address.

This interface is invalid.

Failure in adding an address route causes failure in adding an interface address.

Check whether the number of routes has reached the maximum.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



IP OFFLINE SET: Set DB Failed



Notification description: IP offline configuration: Failure in writing the database.

This interface could be invalid.

It is failed to write the database.

Check the database.

IP OFFLINE SET: Delete the IP Address Failed



Notification description: IP offline configuration: Failure in deleting the IP address.

This interface could be invalid.

It is failed to delete the IP address.

Check whether the configured parameters are correct.

IP OFFLINE SET: Add IP Route Failed



Notification description: IP offline configuration: Failure in adding a route.

The static route is invalid.

Failed to add a route is configuration parameter problem.



Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



IP OFFLINE SET: Delete Route Failed



Notification description: IP offline configuration: Failure in deleting a route.

There may be errors in configuration.


IP OFFLINE SET: Not Ethernet Interface



Notification description: IP offline configuration: This is not an Ethernet port.

This is not an Ethernet port.

Check whether the database is correct.

IP OFFLINE SET: a Same Prefix IP Address Exist



Notification description: IP offline configuration: The same IP address in one network section has existed.

The IP address to be added already existed in the same network section.


IP OFFLINE SET: The Input Parameter is Null




Cause

Handling


Cause

Handling


Cause

Handling




Notification description: IP offline configuration: The parameter imported from the DB is null.

The parameter imported from the DB is null due to configuration exception.

Check whether the configuration operation is correct.

IP OFFLINE Cfg: The IP Address Already Exists



Notification description: IP offline configuration: The IP address has existed.

The IP address has existed.

Check whether the configuration operation is correct.

IP Offline Cfg: The IP Address Already Exists



Notification description: The IP address already exists.

The IP address already exists.

IP address configuration fails.


Invalid Mask or Prefix



Notification description: mask or prefix is invalid.

Sub-net mask or network prefix is invalid.

Static routing configuration is not successful and has some eceptions.

Check the configured parameters are correct.

Cause

Handling


Cause

Handling


Cause

Influence

Handling


Cause

Influence

Handling



ARP Allocate Memory Instance Fail



Notification description: Failure in allocating memory for the ARP table instance.

It is failed to allocate memory for the ARP table instance.

Check the OSS memory configuration.

ARP Allocate Memory Fail for ARP Cache



Notification description: Failure in allocating memory for the ARP table cache.

Failed to allocate memory for the ARP table cache.

Check the OSS memory configuration.

IP Address Collided with the Others



Notification description: The configured IP address conflicts with the address of other host in the network.

The network communication is abnormal.

The IP address (including virtual addresses in the same network section) configured for this gateway is already being used inte in the network.

Modify the duplicated IP address (including virtual addresses in the same network section)

Found Duplicate MAC Address in the ARP Packet




Cause

Handling


Cause

Handling


Influence

Cause

Handling




Notification description: In the received ARP message, the source MAC address is same with that of the interface receiving the ARP message.

The MAC address of this network is same with other MAC address in the associated network.

Modify the duplicated MAC addresses.

RIP Configure Neighbor Fail



Notification description: RIP neighbor configuration error.

Some dynamic routes can not be established.

During adding a neighbor, the address of the neighbor mismatches with that of the interface.

Check the address of the interface and re-configure the RIP neighbor.

Due to this notification static rout to eh neighbor cannot be created.

RIP Interface Authentication Fail



Notification description: Error in RIP port verification.

RIP messages can not be received correctly.

The authentication code is wrong.

Cancel the verification on the port, or re-configure the verification code.

RIP Interface is Disabling



Notification description: The RIP port is forbidden.

RIP messages can not be sent from this interface.

Receiving message port is down.

Check if the posrt is blocked, enable the port again.

Cause

Handling


Influence

Cause

Handling

Precautions


Influence

Cause

Handling


Influence

Cause

Handling



RIP Interface is Enabling



Notification description: The RIP port is enabled.

Received message of port is up.

It is an notification, which needs no processing.

The Router Id in the HELLO Package which OSPF Received is same as the Router id of this

Notification information has the following contentss:


Notification description: The router ID in the Hello package received is same as the ID of this router.

The router ID in the Hello package received is same as the ID of this router.

The relation of OSPF with the adjacent office has some exception.

Modify the IP address of the interface, and further modify the router ID.

OSPF Virtual Interface Configure in Error



Notification description: Error in OSPF virtual link configuration.

The virtual link can’t work.

There are errors in virtual link configuration.

Check the HelloInterval, DeadInterval, Options and other parameters of the virtual link.


Cause

Handling


Cause

Influence

Handling


Influence

Cause

Handling



OSPF Interface Configure in Error



Notification description: Error in OSPF interface configuration.

The two routers couldn’t establish adjacency relation.

There are errors in interface configuration.

Check the HelloInterval, DeadInterval, Options and other parameters of the interface.

OSPF Virtual Interface Authentication Fail



Notification description: Failure in OSPF virtual interface authentication.

The virtual link can’t work and user authentication could be disturbed.

The authentication information configured for the virtual link is incorrect.

Check the authentication item of the virtual interface configuration.

OSPF Interface authentication Fail



Notification description: Failure in OSPF interface authentication.


The the authentication information configuration is incorrect or has some wrong parameters in interface configuration.

Check the authentication item of the interface configuration.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



Create BGP Instance Fail



Notification description: The BGP Failed to create the BGP instance.

BGP protocol can’t work.

The memory allocation for the instance is failed.

Check the free space of the memory is sufficient.

BGP Create Neighbor Fail



Notification description: Failed to create the BGP neighbor.

BGP connection can not be established.

The IP instance is empty or address configuration is not correct.

Check the network configuration and check whether the IP address of the neighbor can be successfully pinged.

BGP Can’t Get TCB for Passive Listen



Notification description: Failed to get TCB when the BGP connection is passively opened


The destination address, the destination port are not correct or has some problem.

Check all the destination addresses and destination ports occupying the TCP connection.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



BGP Can’t Get TCB for Active Connect



Notification description: Failed to get TCB when the BGP connection is actively opened.

It is failed to get TCB due to the source address, the source port and other reasons.

Check the source address, the source port and other configurations.

BGP Enable Passive Listen TCB Fail



Notification description: Failed to get the TCB when the local BGP connection is passively opened.


The started TCB is greater than the maximum threshold.

Reduce the number of started TCB connections.

BGP Enable Active Connect TCB Fail



Notification description: Failed to get the TCB when the local BGP connection is actively opened.


The started TCB is greater than the maximum threshold.

Reduce the number of started TCB connections.

BGP Add Neighbor to Group Fail




Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling




Notification description: The BGP Failed to add a neighbor to the group.

BGP failed to create a group; BGP failed to enable a group due error in BGP configuration.

Check the BGP configuration.

BGP Interface is Down, and Neighbor Disconnects



Notification description: BGP interface is down, and the link between BGP and its adjacent switch is broken

Link between BGP and its adjacent switch breaks.

Messages about the down local interface are received.

Enable this interface.

BGP Interface Address Changed, and Neighbor Disconnects



Notification description: The IP address of BGP interface changed, and the link with the adjacent switch is interrupted.

The link of BGP with the adjacent switch is interrupted.

The IP address of the interface is changed due to exterior causes.

Re-configure BGP according to the changed IP address.

BGP Neighbor Read Receive Buffer Fail



Notification description: The BGP Failed to read the receiving buffer.

BGP can not process the messages received from the peer.

The returned cache length is incorrect while reading messages.

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause



Use the packet capture tool to check the received BGP message.

BGP Neighbor Hold Timer Expired



Notification description: The BGP neighbor Hold timer times out.

BGP connection unavailable

The neighbor hold timer times out, that caused the change of the neighbor status.

Check the BGP connection is normal.

Courier Create BGP Instance Fail



Notification description: Courier failed to create a BGP instance.

BGP can’t be used.

There is no router ID or the router ID is inaccessible.

Check the router ID configuration and the interface IP configuration.

Courier Enable OSPF by the RTR_ID Fail



Notification description: Failed to create an OSPF instance by using one RTR_ID.

BGP can’t be used.

It is failed to create OSPF-related timers and tables.

Check the timer and the memory of the protocol stack. Use the debugging functions “Brs_CourierMemPrintfShow” and “Brs_MemPrintfShow” in shell of RPU to check the utilization condition of the memory; use “courier_show_timerq_info” to check the courier clock information.

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



Courier Synch IP Route Table Error



Notification description: Failed to synchronize the IP route table.

New route entry can not be created.

The IP forwarding table failed to create routes.

Check the memory of the system.

MAC Addreses Conflict While Computing or Deleting It



Notification description: The MAC address conflicts when calculating or deleting the MAC.

Link between the two ports can not be established

In general, the reason is the inconsistence between the protocol stack and the database. The data is saved in the protocol stack before being saved in the database. But it fails to be saved in the database because of memory application failure.

Configure the MAC of the port again.

Alarm Pool is Over in OAM Alarm Manager Process



Notification description: The alarm pool of the foreground OAM is full.

The alarm system may discard some alarms and the system may be down.

The alarm pool of the OAM alarm management module is full.

Restart the system.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



OAM Agent Receive Refuse Alarm Inform



Notification description: The OAM alarm management module frequently receives alarms and notifications.

Some alarm messages may be lost.

The OAM alarm management module frequently receives alarms and notifications.

It is just notification information, which needs no processing.

Board Self-Checking Defeat



Notification description: The board failed to self check itself.

This board can not start up successfully.

The OAM alarm management module receives the board seft-check failure message from the OSS.

Find out the reason of self-check failure according to the additional information of this notification, and restart the board after confirming the reason.

Board Initialization Defeat



Notification description: The board failed to be initialized.

This board can not work.

The OAM alarm management module receives the board initialization failure message from the OSS.

Find out the reason of board initialization failure according to the additional information of this notification, and restart the board after confirming the reason.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



Half Fixedly Connection Configuration Data is Error



Notification description: There is an error in the half-fixed connection data configuration.

Half-fixed channel can not be established.

There is an error in the half-fixed connection data configuration.

Check the data configuration. Check whether the corresponding HW and TS of each HDLC link,, delete the extra signaling link, and re-configure the correct data.

Powering Information about Basic Process



Notification description: Notification of the power-on status of the basic process.

Board is reset if a certain basic process powers failed or timeout.

The board is powered on, and the notification occurs according to the power-on status.

If the board is successfully powered on, the notification is normal.

If the power-on of the basic process failed or timeout, check the failure or timeout reason and power on the board again.

Base Invalid Reason Changed



Notification description: The reference clock failure reason is changed.

Exception in clock-related operations.

The reference clock becomes invalid.

Check the ICM board and the software.


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



Fail to Reset MSCe



Notification description: Resetting of MSCe fails.

Resetting of MSCe fails.

Reset MSCe again manually.

Fail to Reset Circuit in MSCe



Notification description: Fail to reset circuit in MSCe.

Fail to reset circuit in MSCe.

Reset MSCe circuit manually.

Block CIC Failed



Notification description: Manually blocking fails.

Manually blocking fails.

Unblock CIC Failed



Notification description: Manually unblocking fails.

Unblocking fails.

Fail to Use Termination



Notification description: The resource usage is abnormal.

The resource usage is abnormal.


Cause

Handling


Cause

Handling


Cause


Cause


Cause



Check the occupancy and fault of the hardware resource.

BCM Long Bill



Notification description: BCM outputs 30 minutes billing CDRs more than specified threshold.

BCM outputs too many 30 minutes billing CDRs.

Check the user is has used the resources or there is an error in builing tickets.

IUA Receives the Notify Message



Notification description: IUA receives the notify message.

IUA receives the notify message.

Check the corresponding notification.

The notification is eliminated.

IUA Receives Error Message



Notification description: IUA receives error message.

IUA receives error message.

Check the correspondent error.

Base Station Erase



Notification description: Base station erase.

Base station erases.


Handling


Cause

Handling


Cause

Handling

Verification


Cause

Handling


Cause

Handling



The Process is in the Dead Lock State


Notification code: 2625.

Notification description: The process is in the dead lock state.

The process is in the dead lock state.

Reset the board.

Device Notification This section introduces the following notifications:

Trunk slip



Notification information: E1 trunk slip.

Trunk data service or signaling channel fault

The E1 slips.

Check there is frequency difference between the clock of the E1 line and the local receiving clock.

Global Underflow



Notification information: MCC underflow.

No channel can transmit or receive data.

The MCC encounters underflow.

Pull out the board to totally discharge it for 5s, and then plug it again.


Cause

Handling

Description


Influence

Cause

Handling


Influence

Cause

Handling



Global Overflow



Notification description: MCC overflow.

No channel can transmit or receive data.

The MCC encounters overflow.

Pull out the board to totally discharge it for 5s, and then plug it again.

Board Abnormally Resets



Notification description: CPU of a board in the frame is restarted.

CPU of the board in the frame is exceptional.

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

HSSL Break Off between GLI and PSN



Notification description: The port status on the GLI media plane is changed.

The status of the GLI optical interface is changed.

This notification just alerts users and needs no processing.

485 Offline Set Fail



Notification description: Failure in setting 485 offline.


Influence

Cause

Handling


Cause

Handling


Cause

Handling




No 485 response is received when setting the related parameters of the CLKG, TFI and PWRD due to connection line probolem.

Check whether the 485 connection line is correct.

DSP Runtime Error



Notification description: The DSP halts during normal running, and the handshaking fails.

DSP-related functions may become unavailable.

The DSP halts when running normally.

Replace the board, if the notification still exists after replacing the board, check the software or contact R & D engineer.

Backboard Switch Set Change



Notification description: The setting of the DIP switch on the backboard has been changed.

Abnormities on other boards

The setting of the DIP switch on the backboard has some exceptions.


Plug the uim/UIM_2/GUIM board tightly to the slot again.

Replace the backboard in the frame.

Version Error Occur on This Board



Notification description: An error occurs when the external board requests for the version download/load.

The board can not get version file and may not work.

The board version is inconsistent.

Load the board version again.

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



Doc Space is not Enough to Save Version-File



Notification description: The DOC space on the OMP is insufficient, and the version file cannot be downloaded to the DOC.

OMP can not update online.

The DOC space on the OMP is insufficient, and the version file cannot be downloaded to the DOC.

Clear up the DOC space on the OMP, deleting the trash files and useless old version files, and restart the board.

IDE Files Synchronization Information



Notification description: IDE version synchronization information.

The causes for this notification may include:

The standby OMP board is not in the availabe or has some errors, and the synchronization cannot be performed.

The version synchronization is finished.

Check there are the corresponding files on the hard disks of the active and the standby boards. Contact the related person to perform further processing.

SSCS no Response



Notification description: There is no message response in the SSCS link for a long time.

The link does not work.

There is no message response in the SSCS link for a long time, because of physical layer problem.

Notification information

Influence

Cause

Handling


Cause

Handling


Influence

Cause



Check whether the physical link (such as optical interface and optical fiber) is fine.

M2PA Link is Congested



Notification description: Notification due to M2PA signaling link congestion.

Causes for this notification include the followings:

Local congestion.

Local congestion removed.

Remote congestion.

Remote congestion removed.

It is just notification information, which needs no processing.

M2PA Processor is Outage



Notification description: Notification due to faults in the M2P processor.

Causes for this notification include:

The local processor is faulty.

The faults in the local processor are eliminated.

The remote processor is faulty.

The faults in the remote M2P processor are eliminated.

It is just a notification to inform the operator, which needs no processing.

Inform of the Change of ASP Status



Notification description: The ASP status is changed.

The ASP status is changed


Handling


Cause

Handling


Cause

Handling


Cause

Handling



Inform of the Change of AS Status



Notification description: The AS status is changed.

The AS status is changed


Receiving ERROR Message



Notification description: Notification due to receiving error messages.

Error messages are received.

Check the configuration according to error codes.

Receiving NTFY Message



Notification description: Received the notification message of the ASASP status.

The notification message is received.


Association Establish Fail



Notification description: Failed to create the association.

The non-established association directly result in incorrect status (down) of ASP, and in some case the status of AS and office may be not correct.

The SCTP failed to create the association.

Handle the fault referring to the following operations:


Cause

Handling


Cause

Handling


Cause

Handling


Influence

Cause

Handling



Check the physical link.

Check each configuration item of the association.

INFORM_MCS_2400_CONFIGERROR



Notification description: Error in the 2400 configuration data returned from the database.

The causes leading to this notification may include:

The data in the message body returned from the database is empty.

The number of the returned records exceeds the limit of the table.

There are errors in the data configuration of the dispatching weight value table.

There are errors in data of the slot VOQ mapping table.

There are errors in data of the simple QOS mapping relation table.

There are errors in data of the system QOS mapping relation table.

The returned data do not conform to the actual situation.


Check the response message returned from the database to confirm that the table data is not empty.

Check the response message from the database to confirm that the number of the returned table items does not exceed the total number of the table items.

Check the records in the dispatching weight value table in the database to confirm whether there is any error in record configuration.

Check the records in the slot VOQ mapping table in the database to confirm whether there is any error in record configuration.

Check the records in the simple QOS mapping relation table in the database to confirm whether there is any error in record configuration.

Check the records in the system QOS mapping relation table in the database to confirm whether there is any error in record configuration.


Cause

Handling



Check the response message returned from the database to confirm that the table name field (ucTableNo) is one of the four tables in the request.

Configuration Data Received from Database is Abnormal or Error Happened when Updating Configuration Data



Notification description: Exception in the configuration data returned from the database or error in configuration data update.

Board function failure

There are errors in the configuration data.

Adopt different steps according to different number of the additional information.

Check the lawful distribution configuration message imported from the database is correct.

Check the IPLINK configuration message imported from the database is correct.

Check the SCTP distribution configuration message imported from the database is correct.

Check the IP of the control interface imported from the protocol stack is 0; check whether the control interface has 4 IP addresses; check the MTU imported from the protocol stack is 0.

Check the HDLC configuration; check whether the HDLC configuration message imported from the database is correct.

Check the BTS2BCTMP module configuration; check whether the BTS2BCTMP module configuration message imported from the database is correct.

Check the OSI signaling distribution table; check whether the OSI signaling distribution configuration message imported from the database is correct.

Check the OSI network management Port configuration; check whether the OSI network management Port configuration message imported from the database is correct.

Check the exception duration threshold setting; check whether the exception duration threshold configuration message imported from the database is correct.


Influence

Cause

Handling



Check the IPI internal forwarding table; check whether the IPI internal forwarding table configuration message imported from the database is correct.

Check VIG configuration message imported from the database is correct.

Restart the board, and check whether the association configuration, network connection and the equipment on the opposite end are normal.

The NP C5 can't Get PVC from DBS or the PVC can't be Configured in C5's TLU



Notification description: There is an error in configuring the PVC of the C5 microcode module.

The causes leading to this notification may include:

Failed to get the valid PVC from the database

The PVC service type is wrong (because there is an error in configuring the data).

The PVC direction is wrong (because there is an error in configuring the data).

The PVC flow is not correctly set in the table operations.

Failed to add PVC table items in the table operations.

Failed to delete PVC table items in the table operations.

The pointer of the configuration message is empty.

Check whether the MP database table “R_ATM_PVC” is correctly configured and whether the APBE board works normally. Check the additional reason.

The NP C5 Received AAL2 Establishing/Release Message, but C5 Operation Failed



Notification description: Failed to configure the AAL2 link on the C5 microcode module.


Cause

Handling




Causes leading to this notification include:

Failed to add AAL2 link table items in the table operations (that seldom happens).

Failed to delete AAL2 links in the table operations (that seldom happens).

The pointer of the configuration message is empty (that seldom happens).

Check the additional reason and restart the board.

Registers Successfully



Notification description: The MGW has been registered.

The MGW has been registered.


IP Has no Match EPU Global Port



Notification description: No matched EPU network port.

There is no matched EPU network port.


Check the configured route parameters are correct.

Check the EPU is successfully powered on.

ABPM board's PMC7389 is Reset



Notification description: ABPM board's PMC7389 is reset.

The remained value in the chunk buffer on ABPM board cannot be cleared off.

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

Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



IP OFFLINE SET: The Interface is not Exist or is not an Ethernet Interface



Notification description: IP offline configuration: invalid interface.

The interface does not exist or is damages.

Check the configured parameters are correct according to the notification reason.

IP OFFLINE SET: No IP Unnumbered First



Notification description: IP offline configuration: IP processing at the interface is invalid.


Use the “no ip unnumbered” command to make IP processing at the invalid interface.


IP OFFLINE SET: Invalid Host Address



Notification description: ip offline configuration: Invalid host address.


The host address configuration is invalid.



Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



IP OFFLINE SET: Invalid Next Hop



Notification description: IP offline configuration: Invalid next hop.


The next hop has invalid or configuration parameters are wrong.


IP OFFLINE SET: Inconsistent Address and Mask



Notification description: IP offline configuration: Inconsistent IP address and subnet mask.


The IP address and the subnet mask are inconsistent.


IP OFFLINE SET: No Matching Route to Delete



Notification description: IP offline configuration: Failure in finding the matched route to be deleted.

It is failed to find the matched route to be deleted due to wrong parameteres.


IP OFFLINE SET: Next Hop Conflict




Influence

Cause

Handling


Influence

Cause

Handling


Cause

Handling




Notification description: IP offline configuration: Next hop conflict.


The next hop conflicts with current first one.


IP OFFLINE SET: Next Hop not Directed



Notification description: IP offline configuration: The next hop is not directly connected.


The next hop is not directly connected or is not through due to some exceptions.


IP OFFLINE SET: IP Address not Exists



Notification description: IP offline configuration: The IP address does not exist.

The IP address does not exist or not configured properly.


IP OFFLINE SET: MAC beyond Valid Space



Notification description: IP offline configuration: The MAC address exceeds the range.

The MAC address exceeds the range.


Influence

Cause

Handling


Influence

Cause

Handling


Cause

Handling


Cause

Handling



IP OFFLINE SET: DB MAC Operation-Type Invalid



Notification description: IP offline configuration: The MAC configuration type provided by the database is incorrect.

The MAC configuration type configured in the database is incorrect.


IP OFFLINE SET: Invalid IP Broadcast Address



Notification description: IP offline configuration: Invalid broadcast address.

The broadcast address configuration is invalid.


IP OFFLINE SET: The Number of IP Address on this Port cannot Exceed 4



Notification description: IP offline configuration: One interface can configure maximum of four IP addresses.

IP address conflict because interface can configured maximum of four IP addresses.


OSPF Virtual Link State Changed



Cause

Handling


Cause

Handling


Cause

Handling





Notification description: The status of the OSPF virtual interface is changed.

The virtual link couldn’t work if its state is down.

The status of the virtual link is changed.

Check the physical link of the virtual link and the configuration parameters of the virtual interface.

OSPF Interface State Changed



Notification description: The status of the OSPF interface is transferred.


The status of the interface is changed.

Check the physical link and the configuration parameters of the virtual interface.

OSPF Virtual Neighbor State Change



Notification description: The status of the OSPF virtual neighbor is transferred.

If the neighbor’s state is down, database can not be synchronized between them.

The status of the neighbor on the opposite end of the virtual link is changed.

Check the physical link and the configuration parameters of the virtual link.

OSPF Neighbor State Change



Notification description: The status of the OSPF neighbor is transferred.

Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling




If the neighbor’s state is down, database can not be synchronized between them.

The status of the neighbor of the interface is changed.

Check the physical link and the configuration parameters of the neighbor.

LSDB Overflow



Notification description: The LSDB (Link Status DataBase) overflows.

The LSDB overflows of itself or receiving lots of LSAs flooding from the neighbor causes that the LSDB overflows.

Configure route aggregation to reduce the number of LSAs.

OSPF Found LSAs with Same lS_ID.



Notification description: OSPF finds there are LSAs with same lS_ID.

The OSPF finds there are LSAs with same ls_id during the course of re-allocating routes.

Check the route configuration or collection configuration.

BGP Neighbor’s FSM Error



Notification description: Error in the BGP neighbor limited status machine.

BGP can’t connect to the peer successfully.

There are errors in the limit of neighbor status machine.

Check the BGP event.

Influence

Cause

Handling


Cause

Handling


Cause

Handling


Influence

Cause

Handling



BGP State Change



Notification description: The status of the BGP is transferred.

The status machine is changed.

Check the BGP connection status.

Half-Fixed Connection is Changed Abnormally



Notification description: The half-fixed connection is abnormally changed.

TDM channel transient interruption

The causes for this notification include:

The line clock of the frame where this board is located jitters.

There is a hardware fault in the switching chip of this board.


Check the clock source to see whether the indicator on the CLKG panel providing the clock to this board is in the “CATCH” status. At the same time, input the command “SCSShowRTData” through telnet to see the “BOARD Clock Status” in the lost status in the printed debugging information.

Replace the connection chip of this board.

Disk is Full



Notification description: The disk is full.

When a process performs the file operation, the free space of the disk is not enough for this file operation. In this case, the notification is sent to the OAM agent.

The frequency of this Notification depends on how often the operation file of the platform interface is invoked.


Cause

Handling


Influence

Cause

Handling


Cause



Release the space of the disk after backing up the data.

GE Port Config not Match



Notification description: The configuration of the port connected to the fiber of the GLI is inconsistent.

Media layer is down.

The fiber connection between the GLI and the UIM is inconsistent with the background configuration.

Check the GLI optical interface connection relation on the background, and modify the fiber connection according to the configuration.

UIM CS Changeover



Notification description: The big T-net of the UIM switches over.

The CS domain of the UIM switches over.

Check the reason why the CS domain of the UIM switches over through the CS active/standby indicator on the board panel.

Master and Slave Change over



Notification description: master/slave switchover.

Board that changes over failed to reset or board has some exceptions.

Master/slave switchover occurs in the board.

Check whether the master/slave switchover is successful and the check the switchover reason according to the additional information.

Handling


Influence

Cause

Handling


Cause

Handling


Influence

Cause

Handling



FE Port State Change from Up state to Down



Notification description: The FE routing port is broken.

The status of the UIM/CHUB routing is changed from UP to DOWN.

Control layer is down.

Handle this notification referring to the following:

Change the network cable of the corresponding port to confirm whether the network cable is faulty.

Check whether the opposite-end board connected to this port is restarted.

There are hardware faults in the port.

UIM TFS Port State Change



Notification description: The status of the UIM TFS optical interface has changed.

T net transmits incorrect data

The status of the UIM TFS optical interface has changed.

Check the status change reason (through the additional information of the notification) or the optical interface is abnormal.

Board's Workmode is not Supported



Notification description: The board does not support the working mode.

Board’s master/slave information may be wrong.

The causes for this notification may include:

The working mode configured in the board does not compatible with the board.


Cause

Influence

Handling


Influence

Cause

Handling


Influence

Cause



Such reasons as FPGA not loading cause that there are errors in setting the working mode for the board.

Handle the notification according to the following operations:

Check the background configuration, and it is required to configure the working mode the board supports.

Use TestMenu to check whether the FPGA loading is normal.

Power on the board again.

CLK Base Change



Notification description: The clock reference is changed.

Exception in clock-related operations

The clock reference is changed.

It is an important notification, which needs no processing.

CLKG Frequence Base Quality Changed



Notification description: The reference quality of the CLKG board is changed.


The reference quality of the CLKG board is changed.

Check the CLKG board.

CLKG Work Mode Changed



Notification description: The working mode of the clock of the CLKG board changes.


The clock work mode of the CLKG board is changed.

Check the clock.

Handling


Influence

Cause

Handling


Influence

Cause

Handling


Influence

Cause

Handling



Circuit is not Set Up in MSCe



Notification description: Circuit is not set up in MSCe.

MSCe do not have installed circuit.


Check the trunk configuration.

Add available trunking system.

OMP Restart



Notification description: OMP restarts.

OMP system restarts automatically.

Observe the relevant alarms and notifications while restart of the system and clear the fault.

Exception of CPU Loop



Notification description: Exception of CPU loop.

Procedure is on the hook of dead loop.

Check the process code has endless loop.

Tone DSP CPU and DSP Version Differ



Notification description: Tone DSP CPU and DSP Version Differ.

Tone DSP CPU and DSP Version Differ.

Instead DSP Version.


Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



HP Server Power Supply Power off



Notification description: HP server power supply power off.

HP Server power supply status changed.

Check HP server power supply.

ABPM Board's PMC7389 is Reset



Notification description: ABPM board's PMC7389 is reset.

ABPM board's PMC7389 is reset.

Fail to clear the residual value in the CHUNK BUFFER on the ABPM board.

HP Server Power Supply Power ON



Notification description: HP Server power supply power on.

HP Server power supply status changed.

Check HP server power supply.

Alarm When Data Configuration MNIC/2 Physical Board-related is Error



Notification description: Data configuration MNIC/2 physical board-related has error that has created an alarm.

Alarm when data configuration MNIC/2 physical board-related is error.

Reboot the system.


Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



Error Occurs During MCU Running



Notification description: Error occurs during MCU running.

Error occurs during MCU board has some exceptions.

Check the status of the board and MCU.

Timer for ISIS Creates Fail



Notification description: Timer for ISIS creates fail.

Timer for ISIS creates fail.

Please restart ISIS.

ISIS Hello Packet Authentication Fail



Notification description: ISIS Hello packet authentication fail.

ISIS Hello packet authentication fails due to some configuration exceptions.

Change the configuration under interface.

ISIS LSP Packet Authentication Fail



Notification description: ISIS LSP packet authentication fail.

ISIS LSP packet authentication confguration has some exeptions.

Change the configuration of ISIS.


Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



ISIS SNP Packet Authentication Fail



Notification description: ISIS SNP packet authentication fail.

ISIS SNP packet authentication fails.

Change the configuration of ISIS.

Ignored Packet for Differ Interface Version



Notification description: Ignored packet for differ interface version.

Ignored packet for differ interface version.

Modified RIP interface version.

Stack Overflow



Notification description: Stack Overflow.

Stack Overflow.

Increase stacks size.

Configure BFD Session Fails



Notification description: Configure BFD Session Fails.

A problem in the configuration has affected BFD Session Fails.

Check the BFD configuration.


Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



Ec of Index Configed as Signal Link be Informed Enable



Notification description: EC of Index configed as signal link be informed enable.

EC of Index configed as signal link be informed enable.

Check trunk and signal configure.

Tone File System Initialization Failure



Notification description: Tone file system initialization failure.

Flash unlawful data, file systum initialization failure.

Format the flash disk.

Setting Work Mode of Outport is Forbid in This Board



Notification description: Setting work mode of outport is forbid in this board and is not accessible.

Flash unlawful data failure, file system initialization failure..

Change the board.

Multi-CPU Board ,Unittype in R_unit is Inconsistent with First-CPU's Functype in R_CPUVERMAPE




Cause

Handling


Cause

Handling


Cause

Handling




Notification description: Multi-cpu board, unittype in r_unit is inconsistent with first-cpu's functype in r_cpuvermap.

Multi-cpu board, unittype in r_unit is inconsistent with first-cpu's functype in r_cpuvermap.

Please configure it again.

DBS Power on Fail



Notification description: DBS power on fail.

1. System initialization is failed.

2. Loading data from flash is failed.

3. Load capacity table is failed.

4. Get configuration is failed.

5. Datd sync fails.

6. Load data fails after sync.

Select different action according to the causation.

User Office of M3UA States Modify Inform



Notification description: User office of M3UA states modification information.

Siolocas is down.

Active the SIO LOC as.

RIP Failed to Create RIP Instance



Notification description: RIP failed to create RIP instance.

RIP failed to allocate memory.

Please check the memory allocation.

Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



OSPFV3 Routerid Conflict



Notification description: OSPFV3 routerid conflict.

Router ID in Hello packet matches this router's Router ID.

Modify the router's Router ID.

OSPFV3 Virtual Interface State Change



Notification description: OSPFV3 virtual interface state change.

OSPFV3 virtual interface state change.

Check for the physical connection and configuration.

OSPFV3 Interface State Change



Notification description: OSPFV3 interface state change.

OSPFV3 interface state changes due to some problem in configuration.

Check for the physical connection configuration.

OSPFV3 Virtual Interface Configure Error



Notification description: OSPFV3 virtual interface configure error.

OSPFV3 virtual link configuration parameters are invalid or physical link problem.


Cause

Handling


Cause

Handling


Cause

Handling


Cause



Check for the hello interval, dead interval and option parameter on the interface.

OSPFV3 Interface Configure Error



Notification description: OSPFV3 interface configure error.

OSPFV3 interface configuration parameters are invalid or interface is damaged in error.

Check for the hello interval, dead interval and option parameter on the interface.

OSPFV3 Virtual Neighbor State Change



Notification description: OSPFV3 virtual neighbor state change.

OSPFV3 virtual link neighbor state changed.


OSPFV3 Neighbor State Change



Notification description: OSPFV3 neighbor state change.

OSPFV3 virtual link neighbor state.


OSPFV3 Routerid Invalid



Notification description: OSPFV3 routerid invalid.

OSPFV3: Configuration of Router ID has some exception.

Handling


Cause

Handling


Cause

Handling


Cause

Handling


Cause



Configure the router's RouterID.

OSPFV3 Instance Create Failure



Notification description: OSPFV3 instance failure.

OSPFV3: Create OSPFV3 instance is failed due to low memory.

Add More Memory.

80G Chip Error



Notification description: 80g chip error.

80g test some gliqp has down or 80g chip error.

If err happened frequently,reboot psn8p.

CS Fiber Change Over



Notification description: CS Fiber changes over it state.

1. Server Send CMD_FIBER_CHANGEOVER MML Command To GUIM Board.

2. CS Fiber Por Error and auto ChangeOver.

1. Check Server Send CMD_FIBER_CHANGEOVER MML Command To GUIM Board

2. Check GUIM Board Fiber Port Act Light 3. Check 5191 Inform.

Switch Version Fail



Notification description: Switch version fail.

Slave board has master process when upgrade EPLD.

Switch master process in slave board to slave process.

Handling


Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



OMP Version Check Infomation



Notification description: OMP version check infomation.

The version file recorded in DB doesn’t exist.

Add the requisite version file and remove the unused.

DBS MALLOC Memory Fail



Notification description: Dbs malloc memory fails.

OSS malloc memory failure results in DBS malloc memory failure.

Select different action according to the cause.

RIPng Interface is Disable



Notification description: RIPng interface is no accessible.

RIPng receive a message that the status of the interface has is down from system.

Examin the interface and restart it.

RIPng Failed to Create RIP Instance



Notification description: RIPng failed to create RIP instance.

RIPng failed to allocate memory.

Please check the memory allocation.


Cause

Handling


Cause

Handling


Cause

Handling


Cause

Handling



LAN91 Error



Notification description: LAN91 Error.

LAN91 Error.

Re-Initialize LAN91 chip.

Some HSSLS are Out of Sync



Notification description: Some HSSLS are out of sync.

Some HSSLS are out of sync.

It is recommended to restart the board if this phenomenon continues to occur again and again.

IP OFFLINE SET: NO IP Unnumbered First



Notification description: IP OFFLINE SET: No IP unnumbered first.

IP OFFLINE SET is due to wrong configuration parameters.

Check the configuration parameters are correct.

Communication Notification This section introduces the following notifications:

Work Mode Difference with DB Trunk Configuration




Cause

Handling


Cause

Handling


Cause

Handling

Description




Notification description: The trunk configuration is inconsistent with the function of the board.

The board resets automatically.

The data configuration is incorrect or the board is incorrectly inserted.

Check the data configuration of the trunk board, or replace the board.

TCP Connection Aborted



Notification description: The TCP connection is broken.

Connecting/re-transmitting times out or the invalid TCP message is received.

Check the corresponding link is accessible.

IUA AS State Transform



Notification description: The state of IUA AS has changed.

The state of IUA AS has changed.

Check the IUA AS working.

IUA ASP State Transform



Notification description: The state of IUA ASP has changed.

The state of IUA ASP has changed.

Check the of IUA ASP.

Influence

Cause

Handling


Cause

Handling


Cause

Handling


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

Notification Classification

Notifi cation Code

Notification Name P.No.

2 576 Trunk slip 40

2 832 Global Underflow 40

2 833 Global Overflow 41

2 1600 Board Abnormally Resets 41

2 2624 Stack Overflow 63

1 2625 The Process is in the Dead Lock 40

2 2880 Exception of CPU Loop 60

2 3136 Disk is Full 56

2 5187 GE Port Config not Match 57

2 5188 UIM CS Changeover

2 5189 Master and Slave Change over 57

2 5190 FE Port State Change from Up state to Down

58

2 5191 UIM TFS Port State Change 58

2 5192 Board's Workmode is not Supported 58

1 5193 Powering Information about Basic Process

37

2 5194 CS Fiber Change Over 68

2 5441 HSSL Break Off between GLI and PSN 41

2 5448 485 Offline Set Fail 41

2 5700 DSP Runtime Error 42

1 5701 Backboard Switch Set Change 42




Notifi cation Code


3 5702 Work Mode Difference with DB Trunk Configuration

70

2 5703 Backboard Switch Set Change 42

2 5705 Error Occurs During MCU 62

2 5706 Setting Work Mode of Outport is Forbid in This Board

64

2 5707 Tone File System Initialization Failure 64

2 5709 Tone DSP CPU and DSP Version Differ 60

2 5956 Version Error Occur on This Board 42

2 5957 Doc Space is not Enough to Save Version-File

43

2 5958 IDE Files Synchronization Information 43

2 5960 Switch Version 68

2 5961 OMP Version Check 69

1 8000 DBs Table Load Failure 4

1 8001 Master to Slave Sync Failure 4

1 8002 OMP to MP Sync Failure 4

1 8003 MP to PP Sync Failure 5

1 8004 Failure of Saving One Table 5

1 8005 DBs File-Buffer Overflow 5

1 8006

If the Times of Sending Message go beyond the Limit, OAM Back Receives Notification Information about the Message

6

1 8007 Save File Fail in Master or Slave Path, Inform with Failed Path

6

1 8008 Loading Version-Table from File-Reg is Fail because of Nonexistent Domain or Incompatible Domain Type

7

1 8009 DBS Require Configuration Failed 7

2 8010 Multi-CPU Board ,Unittype in R_unit is Inconsistent with First-CPU's Functype in R_CPUVERMAPE

64

2 8011 DBS Power on 65

2 8012 DBS MALLOC Memory 69

1 10304 SCCP GT Translation is Error 7

1 10305 NID is Unequipped 8

1 10306 NID Translation of NID Failed 8

1 10307 ISNI Constrained Route 8

Appendix B Collection of Notification Information



Notifi cation Code


1 10308 ISNI cannot Support Route Indicator 9

1 10309 NID Identify Failure 9

2 10560 SSCS no Response 43

1 10822 Registers 9

1 10823 Registration Defeat 9

1 11328 Failed to Configure Multi-channel Controller

10

1 11329 Failed to Configure Digital Switch Chip 10

1 11330 Failed to Get Config Information from Database

10

2 11840 User Office of M3UA States Modify Inform

65

1 12608 SUA GT Translation Failed 11

2 13632 M2PA Link is Congested 44

2 13633 M2PA Processor is Outage 44

2 13888 Inform of the Change of ASP Status 44

2 13889 Inform of the Change of AS Status 45

2 13890 Receiving ERROR Message 45

2 13891 Receiving NTFY Message 45

2 14144 Association Establish Fail 45

2 15936 INFORM_MCS_2400_CONFIGERROR 46

2 16192 Configuration Data Received from Database is Abnormal or Error Happened when Updating Configuration Data

47

1 16193 SIG_IPI Transmits Packets Abnormal 11

2 16448 The NP C5 can't Get PVC from DBS or the PVC can't be Configured in C5's TLU

48

2 16449 The NP C5 Received AAL2 Establishing/Release Message, but C5 Operation

48

2 16704 Alarm When Data Configuration MNIC/2 Physical Board-related is

61

1 17984 IP Fail to Get Route Table Head or Entry 11

1 17985 Deletion Static Routing Clause defeat 12

2 17986 IP Has no Match EPU Global Port 49

1 17987 IP Create or Enable IFB Fail 12

1 17990 EPU down 12

1 17991 EPU Remove 13




Notifi cation Code


1 17992 IP OPR Static RTE Fail: Add SRTE. 13

1 18240 TCP Received RST Packet 13

3 18241 TCP Connection Aborted 71

1 18496 PPP Detect Wrong While Receive UidIpInfoAck

1314

1 18497 PPP Detect Wrong While Receive BSCIP from DB

14

1 18498 PPP Detect Wrong While Receive UID UPD Config from DB

14

1 18752 Failed to Initialize 14

1 18753 The Configuration Data about UID/HDLC Received by LDM from Database Error

15

2 18754 ABPM board's PMC7389 is 49

2 18754 ABPM Board's PMC7389 is 61

1 19008 Configure Port Failed 15

1 19009 Creat Inner (Inter) Unilateral (Bi-Directional) Connection (Multi) PVC Failed

16

1 19010 Delete Inner (Inter) Unilateral (Bi-Directional) Connection (Multi) PVC Failed

17

1 19264 IMA Group Related Operation Failed 17

1 19265 IMA Link Related Operation Failed 17

2 19520 Some HSSLS are Out of 70

1 19521 SFrame Mode Error is Serious 18

2 19522 CFrame is doffed Because of Horizontal Check Error

18

2 19523 CFrame is doffed because of Vertical 18

2 19524 Cframe is doffed because of not Integrity 19

1 19525 Cframe is doffed because It is not Valid 19

1 19526 Cframe is Losted because of its Length is not Valid

19

1 19527 Frame is Losted because of out of Order 20

1 19528 Frame is Losted because of CRC Check Error

20

1 19529 Configuration IXP2400 Failed 20

1 19530 Configuration VSC872 Failed 21

1 19777 Aps Switch 21

1 20032 L2FWDTBL Init Fail 22




Notifi cation Code


1 20033 L2FWDTBL Init UIM Media eth Fail 22

1 20288 Brs Main Configure Request Timeout 22

1 20289 Brs Main RPU Register Timeout 23

1 20290 Brs Protocol Process Power-on Fatal Failed

23

2 20544 IP OFFLINE SET: The Interface is not Exist or is not an Ethernet Interface

50

2 20545 IP OFFLINE SET: No IP Unnumbered First

50

2 20545 IP OFFLINE SET: NO IP Unnumbered 70

1 20546 IP OFFLINE SET: Add Interface Address Failed

23

1 20547 IP OFFLINE SET: Set DB Failed 24

1 20548 IP OFFLINE SET: Delete the IP Address Failed

24

2 20549 IP OFFLINE SET: Invalid Host Address 50

2 20550 IP OFFLINE SET: Invalid Next Hop 51

2 20553 IP OFFLINE SET: Inconsistent Address and Mask

51

1 20554 IP OFFLINE SET: Add IP Route Failed 24

2 20555 IP OFFLINE SET: No Matching Route to Delete

51

1 20556 IP OFFLINE SET: Delete Route Failed 25

2 20557 IP OFFLINE SET: Next Hop Conflict 51

2 20558 IP OFFLINE SET: Next Hop not 52

2 20559 IP OFFLINE SET: IP Address not Exists 52

1 20561 IP OFFLINE SET: Not Ethernet Interface 25

2 20562 IP OFFLINE SET: MAC beyond Valid Space

52

2 20563 IP OFFLINE SET: DB MAC Operation-Type Invalid

53

1 20564 IP OFFLINE SET: a Same Prefix IP Address Exist

25

2 20565 IP OFFLINE SET: Invalid IP Broadcast Address

53

2 20566 IP OFFLINE SET: The Number of IP Address on this Port cannot Exceed 4

53

1 20567 IP OFFLINE SET: The Input Parameter is Null

25




Notifi cation Code


1 20568 IP OFFLINE Cfg: The IP Address Already Exists

26

1 20569 IP Offline Cfg: The IP Address Already Exists

26

1 20570 Invalid Mask or 26

1 20800 ARP Allocate Memory Instance Fail 27

1 20801 ARP Allocate Memory Fail for ARP Cache 27

1 20802 IP Address Collided with the Others 27

1 20803 Found Duplicate MAC Address in the ARP Packet

27

1 21059 RIP Configure Neighbor Fail 28

1 21060 RIP Interface Authentication Fail 28

1 21063 RIP Interface is Disabling 28

1 21064 RIP Interface is Enabling 29

2 21065 Ignored Packet for Differ Interface 63

2 21066 RIP Failed to Create RIP 65

1 21312 The Router Id in the HELLO Package which OSPF Received is same as the Router id of

29

2 21315 OSPF Virtual Link State Changed 53

2 21316 OSPF Interface State Changed 54

1 21319 OSPF Virtual Interface Configure in Error 29

1 21320 OSPF Interface Configure in Error 30

1 21324 OSPF Virtual Interface Authentication Fail

30

1 21325 OSPF Interface authentication Fail 30

2 21326 OSPF Virtual Neighbor State Change 54

2 21327 OSPF Neighbor State Change 54

2 21329 LSDB Overflow 55

1 21568 Create BGP Instance Fail 31

1 21570 BGP Create Neighbor Fail 31

1 21572 BGP Can’t Get TCB for Passive Listen 31

1 21573 BGP Can’t Get TCB for Active Connect 32

1 21575 BGP Enable Passive Listen TCB Fail 32

1 21576 BGP Enable Active Connect TCB Fail 32

1 21579 BGP Add Neighbor to Group Fail 32




Notifi cation Code


2 21580 BGP Interface is Down, and Neighbor Disconnects

33

2 21581 BGP Interface Address Changed, and Neighbor Disconnects

33

1 21582 BGP Neighbor Read Receive Buffer Fail 33

1 21584 BGP Neighbor Hold Timer Expired 34

1 21586 BGP Neighbor’s FSM Error 55

1 21607 BGP State Change 56

1 21825 Courier Create BGP Instance Fail 34

1 21831 Courier Enable OSPF by the RTR_ID Fail 34

1 21837 Courier Synch IP Route Table Error 35

1 22336 MAC Addreses Conflict While Computing or Deleting It

35

2 22592 Timer for ISIS Creates 62

2 22593 ISIS Hello Packet Authentication 62

2 22594 ISIS LSP Packet Authentication 62

2 22595 ISIS SNP Packet Authentication 63

2 22848 Configure BFD Session Fails 63

1 23104 Alarm Pool is Over in OAM Alarm Manager Process

35

1 23105 OAM Agent Receive Refuse Alarm Inform 36

1 23106 Board Self-Checking Defeat 36

1 23107 Board Initialization Defeat 36

2 25664 Half-Fixed Connection is Changed Abnormally

56

1 25665 Half Fixedly Connection Configuration Data is Error

37

2 25666 Ec of Index Configed as Signal Link be Informed Enable

64

2 26176 CLK Base Change 59

2 26177 CLKG Frequence Base Quality Changed 59

2 26178 CLKG Work Mode Changed 59

1 26179 Base Invalid Reason Changed 37

2 26692 LAN91 Error 70

2 28224 OSPFV3 Routerid 66

2 28225 OSPFV3 Virtual Interface State 66

2 28226 OSPFV3 Interface State 66




Notifi cation Code


2 28227 OSPFV3 Virtual Interface Configure 66

2 28228 OSPFV3 Interface Configure 67

2 28229 OSPFV3 Virtual Neighbor State 67

2 28230 OSPFV3 Neighbor State 67

2 28231 OSPFV3 Routerid 67

2 28232 OSPFV3 Instance Create 68

2 28736 80G Chip 68

2 29505 RIPng Interface is 69

2 29507 RIPng Failed to Create RIP 69

1 16777792

Fail to Reset MSCe 38

1 16777793

Fail to Reset Circuit in MSCe 38

2 16777794

Circuit is not Set Up in MSCe 60

1 16777795

Block CIC Failed 38

1 16777796

Unblock CIC Failed 38

3 16778048

Fail to Use 38

1 16778049

BCM Long Bill 39

1 16778052

Base Station 39

1 16779584

IUA Receives the Notify Message 39

1 16779585

IUA Receives Error Message 39

3 16779586

IUA AS State Transform 71

3 16779587

IUA ASP State Transform 71

2 50331712

OMP Restart 60

2 58720257

HP Server Power Supply Power off 61

2 58720258

HP Server Power Supply Power 61


Tables

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

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

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





Index

Address IP Address24, 25, 26, 27, 52,

53, 83, 84 MAC Address ............ 27, 84

Association................... 45, 81 Backboard............... 42, 79, 80 Changeover........................57 Frame ......................... 20, 82 HW ............................. 21, 37 Message .... 6, 7, 39, 40, 45, 80 MGC....................................9

Querying Notification Notification Code............. 79

Reset ...........................14, 38 Server

OMC............................ 1, 2 SIGTRAN

AS ................45, 71, 81, 86 ASP...............44, 71, 81, 86 SCTP ............................. 11

SSN.................................. 11

Documents

ZTE Media Gateway 2nd