ZTE Media Gateway 2nd

ZXC10 MGW
cdma2000 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: doc@zte.com.cn
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 Jan. 30, 2008 Revision No. R1.0 Serial No. sjzl20080261 Reason for Issue 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 Product Version Serial No. ZXC10 MGW cdma2000 Media Gateway Alarm and Notification Information (2) V2.04.20 sjzl20080261 Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance) Good Your evaluation of this documentation Accessibility: (Contents, Index, Headings, Numbering, Glossary) Good Fair Average Poor Bad N/A Fair Average Poor Bad N/A Document Revision Number Equipment Installation Date R1.0
Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content) Good Fair Average Poor Bad N/A Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Improve the Contents Improve the organization Include more figures Your suggestions for improvement of this documentation Add more examples Add more detail 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 Postcode Telephone Company Address E-mail Make it more concise/brief Add more step-by-step procedures/tutorials Add more troubleshooting information Make it less technical Add more/better quick reference aids Improve the index
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 Cant Get TCB for Passive Listen ..................................... 31 BGP Cant 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 Neighbors 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 FirstCPU'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
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:
TABLE 1 CHAPTER SUMM ARY
Chapter Chapter 1, General Concept Chapter 2, Notification Information
Summary Introduces mechanism and general flow for handling alarms. Provides notification information, including alarm code, alarm name, handling methods, etc.
Confidential and Proprietary Information of ZTE CORPORATION
ZXC10 MGW cdma2000 Media Gateway Alarm and Notification Information (2)
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 Instruction cdma2000 Media Gateway Operating
ZXC10 MGW cdma2000 Media Gateway Alarm Monitoring ZXC10 MGW cdma2000 Media Gateway Configuration
Conventions
Typographical Conventions ZTE documents employ the following typographical conventions.
TABLE 2 TYPOGRAPHICAL CONVENTIONS
Typeface Italics Quotes Bold
Meaning References to other Manuals and documents. Links on screens. Menus, menu options, function names, input fields, radio button names, check boxes, dropdown lists, dialog box names, window names. Keys on the keyboard and buttons on screens and company name. 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.
CAPS Constant width [] {} |
Mouse Operation Conventions
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface Click Double-click Right-click Drag
Meaning Refers to clicking the primary mouse button (usually the left mouse button) once. Refers to quickly clicking the primary mouse button (usually the left mouse button) twice. Refers to clicking the secondary mouse button (usually the right mouse button) once. Refers to pressing and holding a mouse button and moving the mouse.
ii
About This Manual
How to Get in Touch

Customer Support 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 support@zte.com.cn. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830. Documentation Support 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 doc@zte.com.cn; 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.
iii
iv
Chapter
General Concept
Overview
Description 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

Description 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.
General Flow of Handling Notifications

Description 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.
Chapter
Notification Information
Overview
Description Notification information classifications: is divided into the following Handling error-related notification information Device-related notification information Communication-related notification information Service quality-related notification information Environment-related notification information Content A collection of notification information listed in ascending sequence of notification codes is provided in Appendix B Collection of Notification Informationat the end of the manual.
Handling Error Notification

Load Error
Notification Information Notification information has the following contents: Notification code: 5701 Notification description: The version failed to be loaded. Influence Cause The board cant 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.
Handling
DBs Table Load Failure

Notification Information Notification information has the following contents: Notification code: 8000 Notification description: When the foreground and the background data is synchronized, the MP loads data but a datasheet is failed to be loaded. Cause Handling 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 Information Notification information has the following contents: Notification code: 8001 Notification description: The master and the slave datasheet fail to be synchronized. Cause 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.
Handling
OMP to MP Sync Failure

Notification Information Notification information has the following contents: Notification code: 8002 Notification description: The data synchronization from OMP to the MP fails. Influence Cause Handling 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.
Chapter 2 Notification Information
MP to PP Sync Failure
Notification Information Notification information has the following contents: Notification code: 8003 Notification description: The data synchronization from the MP to PP fails. Cause Handling The MP synchronizes data to the PP. The PP gives a notification message, and the data synchronization failed. Handle the notification referring to the following operations: Check the data configuration. Check the link status between the MP board and PP board.
Failure of Saving One Table

Notification Information Notification information has the following contents: Notification code: 8004 Notification description: A single data table failed to be saved. Influence Cause 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.
Handling
DBs File-Buffer Overflow

Notification Information Notification information has the following contents: Notification code: 8005 Notification description: The capacity of the memory file buffer is insufficient, and the subsequent transferred records are discarded. Influence Cause 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.
Handling
If the Times of Sending Message go beyond the Limit, OAM Back Receives Notification Information about the Message
Notification Information Notification information has the following contents: Notification code: 8006 Notification description: If the notification for the data configuration modification (P_notify process) fails three time, this notification occurs. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 8007 Notification description: The data saving in one of the active and the standby directories fails. The additional message contains the path of saving failure. Influence Cause 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. Handling Handle the notification referring to the following operations: If the disk is full, clear up the disk to create enough available space. If the disk is faulty, maintain or replace it.
Loading Version-Table from File-Reg is Fail because of Nonexistent Domain or Incompatible Domain Type
Notification Information Notification information has the following contents: Notification code: 8008 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. Influence Cause 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 cant be loaded. This phenomenon is normal during the version upgrade. Use the latest background version tool to re-configure the version data.
Handling
DBS Require Configuration Failed

Notification Information Notification information has the following contents: Notification code: 8009 Notification description: The database configuration request is rejected. Cause 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.
Handling
SCCP GT Translation is Error

Notification Information Notification information has the following contents: Notification code: 10304 Notification description: GT translation failure. Influence Cause Message sending/receiving of this time fails. The notification occurs due to the following causes: There is no signaling point code and no GT number is configured.
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. Handling Check the GT configuration, or the statuses of the office direction and the subsystems.
NID is Unequipped
Notification Information Notification information has the following contents: Notification code: 10305 Notification description: NID not configured. Cause Handling 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 Information Notification information has the following contents: Notification code: 10306 Notification description: NID translation failure Cause The notification occurs due to the following causes: The database fails to translate the NID (which frequently happens). The database is exceptional. Handling Correctly configure the NID in the database.
ISNI Constrained Route Repeat

Notification Information Notification information has the following contents: Notification code: 10307 Notification description: There is repeated route information in the ISNI. Cause Handling 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.
ISNI cannot Support Route Indicator

Notification Information Notification information has the following contents: Notification code: 10308 Notification description: The ISNI does not support the route function. Cause Handling The ISNI does not support the route function. The upper-layer user should correctly enter route function indicator.
NID Identify Failure

Notification Information Notification information has the following contents: Notification code: 10309 Notification description: INID route prompt failure. Cause Handling 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 Information Notification information has the following contents: Notification code: 10822 Notification description: The MGW has been registered. Cause Handling The MGW has been registered. No special processing is required.
Registration Defeat
Notification Information Notification information has the following contents: Notification code: 10823 Notification description: The MGW is not registered in the MGC . Influence Cause Handling 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.
Failed to Configure Multi-channel Controller

Notification Information Notification information has the following contents: Notification code: 11328 Notification description: Failure in configuring the MTP2 multi-channel controller. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 11329 Notification description: Failure in configuring the MTP2 switching chip. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 11330 Notification description: MTP2 failed to get the configuration information from the database. Influence Cause Handling Related links become unavailable. MTP2 failed to get the configuration information from the database. Check the main processor on the foreground runs normally.
10
SUA GT Translation Failed

Notification Information Notification information has the following contents: Notification code: 12608 Notification description: GT translation fails. Influence Cause Signaling data cant 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. Handling 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 Information Notification information has the following contents: Notification code: 16193 Notification description: There is an exception when the SIG_IPI forwards the service message. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 17984 Notification description: Failed to get the route table head or entry.
11
Cause Handling
It is failed to get the route table head due to wrong configuration parameters. Handle the notification referring to the following operations: Configure route information again. Check whether the configured route parameters are correct.
Deletion Static Routing Clause defeat

Notification Information Notification information has the following contents: Notification code: 17985 Notification description: Failed to delete the static route entry. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 17987 Notification description: Failed to create or activate the IFB. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 17990 Notification description: The RPU receives the message of EPU port down reported by the SCS. Cause Handling The RPU receives the message of EPU port down reported by the SCS. Check the status of the reported board.
12
EPU Remove
Notification Information Notification information has the following contents: Notification code: 17991 Notification description: The RPU receives the message reported by the SCS that the EPU board has been deleted. Influence Cause Handling Precaution 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 Information Notification information has the following contents: Notification code: 17992 Notification description: Failed to add the static route entry. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 18240 Notification description: The TCP receives RST message. Cause Handling 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

Notification Information The notification information includes: Notification code: 18496
13
Notification description: PPP detects wrong information while applying UID IP from the database. Influence Cause Handling Powering on protocol stack process fails. The database configuration is not correct. Re-configure UID IP.
PPP Detect Wrong While Receive BSCIP from DB

Notification Information The notification information has the following contents: Notification code: 18497 Notification description: PPP detects wrong information while receiving BSCIP from the database. Cause Influence Handling The database configuration is not correct. Powering on protocol stack process fails. Re-configure BSC IP.
PPP Detect Wrong While Receive UID UPD Config from DB

Notification Information The notification information has the following contents: Notification code: 18498 Notification description: PPP detects wrong information while receiving UID UPD information from the database. Cause Handling Verification The database configuration is not correct. Re-configure the database data. The notification disappears.
Failed to Initialize PCM7389

Notification Information The notification information has the following contents: Notification code: 18752 Notification description: PMC7389 initialization fails. Cause Influence Handling There is error with the memory, chip configuration, etc. The system may get down. Reset or replace the board.
14
The Configuration Data about UID/HDLC Received by LDM from Database Error
Notification Information The notification information has the following contents: Notification code: 18753 Notification description: UID/HDLC configuration in database is incorrect. Cause 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.
Influence Handling
Configure Port Failed

Notification Information The notification information has the following contents: Notification code: 19008 Notification description: Failed to configure the port. Influence Cause 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. Handling 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.
15
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 (BiDirectional) Connection (Multi) PVC Failed

Notification Information The notification information has the following contents: Notification code: 19009 Notification description: Failed to create the inner-(inter)board signal-(both-) way unicast (multicast) PVC. Influence Cause 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. Handling 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 bothway 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.
16
Confirm that the service type mismatches with the flow type. Confirm that the to-be-created PVC does not exist.
Delete Inner (Inter) Unilateral (BiDirectional) Connection (Multi) PVC Failed

Notification Information The notification information has the following contents: Notification code: 19010 Notification description: Failed to delete the inner-(inter)board single-(both-) way unicast (multicast) PVC. Influence Cause Handling 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 Information The notification information has the following contents: Notification code: 19264 Notification description: The IMA-group-related operations initiated by the background fail. Influence Cause Handling 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. Handle the notification referring to the following operations: Check the parameters related with the initiated operations are correct. Check the steps in the operations are legal.
IMA Link Related Operation Failed

Notification Information The notification information has the following contents: Notification code: 19265 Notification description: The IMA-link-related initiated by the background fail. Influence operations
The specified resource does not exist on the foreground.
17
Cause Handling
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 Information The notification information has the following contents: Notification code: 19521 Notification description: The number of SFrames including frame format mode error exceeds the threshold. Influence Cause Handling 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 Information The notification information has the following contents: Notification code: 19522 Notification description: The number of CFrames discarded due to horizontal check error at the CSIX port N exceeds the threshold. Influence Cause Handling The system may discard some packets. Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
CFrame is doffed because of Vertical

Notification Information The notification information has the following contents: Notification code: 19523 Notification description: The number of CFrames discarded due to vertical check error at the CSIX port N exceeds the threshold. Influence The system may discard some packets.
18
Cause Handling
Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
Cframe is doffed because of not Integrity

Notification Information The notification information has the following contents: Notification code: 19524 Notification description: The number of CFrames discarded due to incomplete frame at the CSIX port N exceeds the threshold. Influence Cause Handling The system may discard some packets. Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
Cframe is doffed because It is not Valid

Notification Information The notification information has the following contents: Notification code: 19525 Notification description: The number of CFrames discarded due to invalid frame type at the CSIX port N exceeds the threshold. Influence Cause Handling The system may discard some packets. Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
Cframe is Losted because of its Length is not Valid

Notification Information The notification information has the following contents: Notification code: 19526 Notification description: The number of CFrames discarded due to invalid frame length at the CSIX port N exceeds the threshold.
19
Influence Cause Handling
The system may discard some packets. Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
Frame is Losted because of out of Order

Notification Information The notification information has the following contents: Notification code: 19527 Notification description: The number of frames discarded because out of order exceeds the threshold. Influence Cause Handling The system may discard some packets. Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
Frame is Losted because of CRC Check Error

Notification Information The notification information has the following contents: Notification code: 19528 Notification description: The number of frames discarded because CRC check error exceeds the threshold. Influence Cause Handling The system may discard some packets. Maybe there is a problem in the 872 chip. If the notification continuously occurs several times, restart the board.
Configuration IXP2400 Failed

Notification Information The notification information has the following contents: Notification code: 19529 Notification description: The flow control failed to perform initialization configuration on some flow control tables of the 2400. Influence TM process cant power on successfully, and consequently the board may reboot.
20
Cause Handling
It is failed to invoke the table operation interface. Restart the board.
Configuration VSC872 Failed

Notification Information The notification information has the following contents: Notification code: 19530 Notification description: The flow control failed to perform initialization configuration on some flow control parameters of the 872. Influence Cause Handling TM process cant power on successfully, and consequently the board could reboot. It is failed to invoke the OSS interface. Restart the board.
Aps Switch
Notification Information The notification information has the following contents: Notification code: 19777 Notification description: Aps switchover occurs. Cause 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. Handling 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 background initiates the forcible switchover. Switchover failure: the
21
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 Information The notification information has the following contents: Notification code: 20032 Notification description: forwarding table. Influence Cause Handling Services may be interrupted. Failed to allocate the memory and failed to get the physical address of this board. Restart the board. Failed to initialize the level-2
L2FWDTBL Init UIM Media eth Fail

Notification Information The notification information has the following contents: Notification code: 20033 Notification description: Failed to initialize the Ethernet port on the media plane of the UIM board. Influence Cause Handling 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 Information The notification information has the following contents: Notification code: 20288 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. Cause 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.
Handling
22
Brs Main RPU Register Timeout

Notification Information The notification information has the following contents: Notification code: 20289 Notification description: Timeout when registering in the RPU. Influence Cause Handling 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 Information The notification information has the following contents: Notification code: 20290 Notification description: The power-on of the protocol stack process failed Influence Cause Handling 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 Information The notification information has the following contents: Notification code: 20546 Notification description: IP offline configuration: Failure in adding an interface address. Influence Cause Handling 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.
23
IP OFFLINE SET: Set DB Failed

Notification Information The notification information has the following contents: Notification code: 20547 Notification description: IP offline configuration: Failure in writing the database. Influence Cause Handling This interface could be invalid. It is failed to write the database. Check the database.
IP OFFLINE SET: Delete the IP Address Failed

Notification Information The notification information has the following contents: Notification code: 20548 Notification description: IP offline configuration: Failure in deleting the IP address. Influence Cause Handling 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 Information The notification information has the following contents: Notification code: 20554 Notification description: IP offline configuration: Failure in adding a route. Influence Cause Handling The static route is invalid. Failed to add a route is configuration parameter problem. Check whether the configured parameters are correct.
24
IP OFFLINE SET: Delete Route Failed

Notification Information The notification information has the following contents: Notification code: 20556 Notification description: IP offline configuration: Failure in deleting a route. Cause Handling There may be errors in configuration. Check whether the configured parameters are correct.
IP OFFLINE SET: Not Ethernet Interface

Notification Information The notification information has the following contents: Notification code: 20561 Notification description: IP offline configuration: This is not an Ethernet port. Cause Handling This is not an Ethernet port. Check whether the database is correct.
IP OFFLINE SET: a Same Prefix IP Address Exist

Notification Information The notification information has the following contents: Notification code: 20564 Notification description: IP offline configuration: The same IP address in one network section has existed. Cause Handling The IP address to be added already existed in the same network section. Check whether the configured parameters are correct.
IP OFFLINE SET: The Input Parameter is Null

Notification Information The notification information has the following contents: Notification code: 20567
25
Notification description: IP offline configuration: parameter imported from the DB is null. Cause Handling
The
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 Information The notification information has the following contents: Notification code: 20568 Notification description: IP offline configuration: The IP address has existed. Cause Handling The IP address has existed. Check whether the configuration operation is correct.
IP Offline Cfg: The IP Address Already Exists

Notification Information The notification information has the following contents: Notification code: 20569 Notification description: The IP address already exists. Cause Influence Handling The IP address already exists. IP address configuration fails. Check whether the configured parameters are correct.
Invalid Mask or Prefix

Notification Information The notification information has the following contents: Notification code: 20570 Notification description: mask or prefix is invalid. Cause Influence Handling Sub-net mask or network prefix is invalid. Static routing configuration is not successful and has some eceptions. Check the configured parameters are correct.
26
ARP Allocate Memory Instance Fail

Notification Information The notification information has the following contents: Notification code: 20800 Notification description: Failure in allocating memory for the ARP table instance. Cause Handling It is failed to allocate memory for the ARP table instance. Check the OSS memory configuration.
ARP Allocate Memory Fail for ARP Cache

Notification Information The notification information has the following contents: Notification code: 20801 Notification description: Failure in allocating memory for the ARP table cache. Cause Handling Failed to allocate memory for the ARP table cache. Check the OSS memory configuration.
IP Address Collided with the Others

Notification Information The notification information has the following contents: Notification code: 20802 Notification description: The configured IP address conflicts with the address of other host in the network. Influence Cause 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)
Handling
Found Duplicate MAC Address in the ARP Packet

Notification Information The notification information has the following contents: Notification code: 20803
27
Notification description: In the received ARP message, the source MAC address is same with that of the interface receiving the ARP message. Cause Handling 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 Information The notification information has the following contents: Notification code: 21059 Notification description: RIP neighbor configuration error. Influence Cause Handling Precautions Some dynamic routes can not be established. During adding a neighbor, the address mismatches with that of the interface. of the neighbor
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 Information The notification information has the following contents: Notification code: 21060 Notification description: Error in RIP port verification. Influence Cause Handling RIP messages can not be received correctly. The authentication code is wrong. Cancel the verification verification code. on the port, or re-configure the
RIP Interface is Disabling

Notification Information The notification information has the following contents: Notification code: 21063 Notification description: The RIP port is forbidden. Influence Cause Handling RIP messages can not be sent from this interface. Receiving message port is down. Check if the posrt is blocked, enable the port again.
28
RIP Interface is Enabling

Notification Information The notification information has the following contents: Notification code: 21064 Notification description: The RIP port is enabled. Cause Handling 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 Notification information has the following contentss: Notification code: 21312 Notification description: The router ID in the Hello package received is same as the ID of this router. Cause Influence Handling 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 Information Notification information has the following contents: Notification code: 21319 Notification description: configuration. Influence Cause Handling The virtual link cant work. There are errors in virtual link configuration. Check the HelloInterval, DeadInterval, parameters of the virtual link. Options and other Error in OSPF virtual link
29
OSPF Interface Configure in Error

Notification Information Notification information has the following contentss: Notification code: 21320 Notification description: Error in OSPF interface configuration. Influence Cause Handling The two routers couldnt establish adjacency relation. There are errors in interface configuration. Check the HelloInterval, DeadInterval, parameters of the interface. Options and other
OSPF Virtual Interface Authentication Fail

Notification Information Notification information has the following contentss: Notification code: 21324 Notification description: Failure in OSPF virtual interface authentication. Influence Cause Handling The virtual link cant work and user authentication could be disturbed. The authentication information configured for the virtual link is incorrect. Check the authentication configuration. item of the virtual interface
OSPF Interface authentication Fail

Notification Information Notification information has the following contentss: Notification code: 21325 Notification description: authentication. Influence Cause Handling Failure in OSPF interface
The two routers couldnt establish adjacency relation. The the authentication information configuration is incorrect or has some wrong parameters in interface configuration. Check the authentication item of the interface configuration.
30
Create BGP Instance Fail

Notification Information Notification information has the following contentss: Notification code: 21568 Notification description: The BGP Failed to create the BGP instance. Influence Cause Handling BGP protocol cant work. The memory allocation for the instance is failed. Check the free space of the memory is sufficient.
BGP Create Neighbor Fail

Notification Information Notification information has the following contentss: Notification code: 21570 Notification description: Failed to create the BGP neighbor. Influence Cause Handling 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 Cant Get TCB for Passive Listen

Notification Information Notification information has the following contentss: Notification code: 21572 Notification description: Failed to get TCB when the BGP connection is passively opened Influence Cause Handling BGP connection can not be established. 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.
31
BGP Cant Get TCB for Active Connect

Notification Information Notification information has the following contentss: Notification code: 21573 Notification description: Failed to get TCB when the BGP connection is actively opened. Cause Handling It is failed to get TCB due to the source address, the source port and other reasons. Check the source configurations. address, the source port and other
BGP Enable Passive Listen TCB Fail

Notification Information Notification information has the following contentss: Notification code: 21575 Notification description: Failed to get the TCB when the local BGP connection is passively opened. Influence Cause Handling BGP connection can not be established. The started TCB is greater than the maximum threshold. Reduce the number of started TCB connections.
BGP Enable Active Connect TCB Fail

Notification Information Notification information has the following contentss: Notification code: 21576 Notification description: Failed to get the TCB when the local BGP connection is actively opened. Influence Cause Handling BGP connection can not be established. The started TCB is greater than the maximum threshold. Reduce the number of started TCB connections.
BGP Add Neighbor to Group Fail

Notification Information Notification information has the following contentss: Notification code: 21579
32
Notification description: The BGP Failed to add a neighbor to the group. Cause Handling 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 Information Notification information has the following contents: Notification code: 21580 Notification description: BGP interface is down, and the link between BGP and its adjacent switch is broken Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 21581 Notification description: The IP address of BGP interface changed, and the link with the adjacent switch is interrupted. Influence Cause Handling 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 Information Notification information has the following contentss: Notification code: 21582 Notification description: The BGP Failed to read the receiving buffer. Influence Cause BGP can not process the messages received from the peer. The returned cache length is incorrect while reading messages.
33
Handling
Use the packet capture tool to check the received BGP message.
BGP Neighbor Hold Timer Expired

Notification Information Notification information has the following contentss: Notification code: 21584 Notification description: The BGP neighbor Hold timer times out. Influence Cause Handling 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 Information Notification information has the following contentss: Notification code: 21825 Notification description: Courier failed to create a BGP instance. Influence Cause Handling BGP cant be used. There is no router ID or the router ID is inaccessible. Check the router configuration. ID configuration and the interface IP
Courier Enable OSPF by the RTR_ID Fail

Notification Information Notification information has the following contentss: Notification code: 21831 Notification description: Failed to create an OSPF instance by using one RTR_ID. Influence Cause Handling BGP cant 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.
34
Courier Synch IP Route Table Error

Notification Information Notification information has the following contentss: Notification code: 21837 Notification description: Failed to synchronize the IP route table. Influence Cause Handling 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 Information Notification information has the following contentss: Notification code: 22336 Notification description: The MAC address conflicts when calculating or deleting the MAC. Influence Cause 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.
Handling
Alarm Pool is Over in OAM Alarm Manager Process

Notification Information Notification information has the following contentss: Notification code: 23104 Notification description: The alarm pool of the foreground OAM is full. Influence Cause Handling 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.
35
OAM Agent Receive Refuse Alarm Inform

Notification Information Notification information has the following contentss: Notification code: 23105 Notification description: The OAM alarm management module frequently receives alarms and notifications. Influence Cause Handling 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 Information Notification information has the following contentss: Notification code: 23106 Notification description: The board failed to self check itself. Influence Cause Handling This board can not start up successfully. The OAM alarm management module receives the board seftcheck 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 Information Notification information has the following contentss: Notification code: 23107 Notification description: The board failed to be initialized. Influence Cause Handling 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.
36
Half Fixedly Connection Configuration Data is Error

Notification Information Notification information has the following contentss: Notification code: 25665 Notification description: There is an error in the half-fixed connection data configuration. Influence Cause Handling 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 Information Notification information has the following contentss: Notification code: 5193 Notification description: Notification of the power-on status of the basic process. Influence Cause Handling 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 Information Notification information has the following contentss: Notification code: 26179 Notification description: The reference clock failure reason is changed. Influence Cause Handling Exception in clock-related operations. The reference clock becomes invalid. Check the ICM board and the software.
37
Fail to Reset MSCe

Notification Information Notification information has the following contents: Notification code: 16777792 Notification description: Resetting of MSCe fails. Cause Handling Resetting of MSCe fails. Reset MSCe again manually.
Fail to Reset Circuit in MSCe

Notification Information Notification information has the following contents: Notification code: 16777793 Notification description: Fail to reset circuit in MSCe. Cause Handling Fail to reset circuit in MSCe. Reset MSCe circuit manually.
Block CIC Failed

Notification Information Notification information has the following contents: Notification code: 16777795 Notification description: Manually blocking fails. Cause Manually blocking fails.
Unblock CIC Failed

Notification Information Notification information has the following contents: Notification code: 16777796 Notification description: Manually unblocking fails. Cause Unblocking fails.
Fail to Use Termination

Notification Information Notification information has the following contents: Notification code: 16778048 Notification description: The resource usage is abnormal. Cause The resource usage is abnormal.
38
Handling
Check the occupancy and fault of the hardware resource.
BCM Long Bill

Notification Information Notification information has the following contents: Notification code: 16778049 Notification description: BCM outputs 30 minutes billing CDRs more than specified threshold. Cause Handling 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 Information Notification information has the following contents: Notification code: 16779584 Notification description: IUA receives the notify message. Cause Handling Verification IUA receives the notify message. Check the corresponding notification. The notification is eliminated.
IUA Receives Error Message

Notification Information Notification information has the following contents: Notification code: 16779585 Notification description: IUA receives error message. Cause Handling IUA receives error message. Check the correspondent error.
Base Station Erase

Notification Information Notification information has the following contents: Notification code: 16778052 Notification description: Base station erase. Cause Handling Base station erases. No special processing is required.
39
The Process is in the Dead Lock State

Notification Information Notification information has the following contents: Notification code: 2625. Notification description: The process is in the dead lock state. Cause Handling The process is in the dead lock state. Reset the board.
Device Notification
Description This section introduces the following notifications:
Trunk slip
Notification Information Notification information has the following contents: Notification code: 576 Notification information: E1 trunk slip. Influence Cause Handling 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 Notification information has the following contents: Notification code: 832 Notification information: MCC underflow. Influence Cause Handling 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.
40
Global Overflow
Notification Information Notification information has the following contents: Notification code: 833 Notification description: MCC overflow. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 1600 Notification description: CPU of a board in the frame is restarted. Cause Handling 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 Information Notification information has the following contents: Notification code: 5441 Notification description: The port status on the GLI media plane is changed. Cause Handling The status of the GLI optical interface is changed. This notification just alerts users and needs no processing.
485 Offline Set Fail

Notification Information Notification information has the following contents: Notification code: 5448 Notification description: Failure in setting 485 offline.
41
Cause
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.
Handling
DSP Runtime Error

Notification Information Notification information has the following contents: Notification code: 5700 Notification description: The DSP halts during normal running, and the handshaking fails. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 5703 Notification description: The setting of the DIP switch on the backboard has been changed. Influence Cause Handling Abnormities on other boards The setting of the DIP switch on the backboard has some exceptions. Handle the notification referring to the following operations: 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 Information Notification information has the following contents: Notification code: 5956 Notification description: An error occurs when the external board requests for the version download/load. Influence Cause Handling The board can not get version file and may not work. The board version is inconsistent. Load the board version again.
42
Doc Space is not Enough to Save Version-File

Notification information Notification information has the following contents: Notification code: 5957 Notification description: The DOC space on the OMP is insufficient, and the version file cannot be downloaded to the DOC. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 5958 Notification information. Cause description: IDE version synchronization
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.
Handling
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 Information Notification information has the following contents: Notification code: 10560 Notification description: There is no message response in the SSCS link for a long time. Influence Cause The link does not work. There is no message response in the SSCS link for a long time, because of physical layer problem.
43
Handling
Check whether the physical link (such as optical interface and optical fiber) is fine.
M2PA Link is Congested

Notification Information Notification information has the following contents: Notification code: 13632 Notification description: Notification due to M2PA signaling link congestion. Cause Causes for this notification include the followings: Local congestion. Local congestion removed. Remote congestion. Remote congestion removed. Handling It is just notification information, which needs no processing.
M2PA Processor is Outage

Notification Information Notification information has the following contents: Notification code: 13633 Notification description: Notification due to faults in the M2P processor. Cause 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. Handling It is just a notification to inform the operator, which needs no processing.
Inform of the Change of ASP Status

Notification Information Notification information has the following contents: Notification code: 13888 Notification description: The ASP status is changed. Cause Handling The ASP status is changed It is just a notification to inform the operator, which needs no processing.
44
Inform of the Change of AS Status

Notification Information Notification information has the following contents: Notification code: 13889 Notification description: The AS status is changed. Cause Handling The AS status is changed It is just a notification to inform the operator, which needs no processing.
Receiving ERROR Message

Notification Information Notification information has the following contents: Notification code: 13890 Notification description: Notification due to receiving error messages. Cause Handling Error messages are received. Check the configuration according to error codes.
Receiving NTFY Message

Notification Information Notification information has the following contents: Notification code: 13891 Notification description: Received the notification message of the ASASP status. Cause Handling The notification message is received. No special processing is required.
Association Establish Fail

Notification Information Notification information has the following contents: Notification code: 14144 Notification description: Failed to create the association. Influence 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
45
Check the physical link. Check each configuration item of the association.
INFORM_MCS_2400_CONFIGERR OR
Notification Information Notification information has the following contents: Notification code: 15936 Notification description: Error in the 2400 configuration data returned from the database. Cause 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. Handling Handle the notification referring to the following operations: 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.
46
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 Information Notification information has the following contents: Notification code: 16192 Notification description: Exception in the configuration data returned from the database or error in configuration data update. Influence Cause Handling 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.
47
Check the IPI internal forwarding table; check whether the IPI internal forwarding table configuration message imported from the database is correct. Check VIG configuration database is correct. message imported from the
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 Information Notification information has the following contents: Notification code: 16448 Notification description: There is an error in configuring the PVC of the C5 microcode module. Cause 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. Handling 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 Information Notification information has the following contents: Notification code: 16449 Notification description: Failed to configure the AAL2 link on the C5 microcode module.
48
Cause
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).
Handling
Check the additional reason and restart the board.
Registers Successfully
Notification Information Notification information has the following contents: Notification code: 10822 Notification description: The MGW has been registered. Cause Handling The MGW has been registered. No special processing is required.
IP Has no Match EPU Global Port

Notification Information Notification information has the following contents: Notification code: 17986 Notification description: No matched EPU network port. Cause Handling There is no matched EPU network port. Handle the notification referring to the following operations: Check the configured route parameters are correct. Check the EPU is successfully powered on.
ABPM board's PMC7389 is Reset

Notification Information Notification information has the following contents: Notification code: 18754 Notification description: ABPM board's PMC7389 is reset. Cause Handling The remained value in the chunk buffer on ABPM board cannot be cleared off. If system running abnormally, contact maintenance personnel of ZTE Corporation.
49
IP OFFLINE SET: The Interface is not Exist or is not an Ethernet Interface

Notification Information Notification information has the following contents: Notification code: 20544 Notification interface. Cause Handling description: IP offline configuration: invalid
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 Information Notification information has the following contents: Notification code: 20545 Notification description: IP offline processing at the interface is invalid. Influence Cause Handling This interface is invalid. Use the no ip unnumbered command to make IP processing at the invalid interface. Check whether the configured parameters are correct. configuration: IP
IP OFFLINE SET: Invalid Host Address

Notification Information Notification information has the following contents: Notification code: 20549 Notification description: ip offline configuration: Invalid host address. Influence Cause Handling This interface is invalid. The host address configuration is invalid. Check the configured parameters are correct.
50
IP OFFLINE SET: Invalid Next Hop

Notification Information Notification information has the following contents: Notification code: 20550 Notification description: IP offline configuration: Invalid next hop. Influence Cause Handling The static route is invalid. The next hop has invalid or configuration parameters are wrong. Check the configured parameters are correct.
IP OFFLINE SET: Inconsistent Address and Mask

Notification Information Notification information has the following contents: Notification code: 20553 Notification description: IP offline configuration: Inconsistent IP address and subnet mask. Influence Cause Handling The static route is invalid. The IP address and the subnet mask are inconsistent. Check the configured parameters are correct.
IP OFFLINE SET: No Matching Route to Delete

Notification Information Notification information has the following contents: Notification code: 20555 Notification description: IP offline configuration: Failure in finding the matched route to be deleted. Cause Handling It is failed to find the matched route to be deleted due to wrong parameteres. Check whether the configured parameters are correct.
IP OFFLINE SET: Next Hop Conflict

Notification Information Notification information has the following contents: Notification code: 20557
51
Notification description: IP offline configuration: Next hop conflict. Influence Cause Handling The static route is invalid. The next hop conflicts with current first one. Check whether the configured parameters are correct.
IP OFFLINE SET: Next Hop not Directed

Notification Information Notification information has the following contents: Notification code: 20558 Notification description: IP offline configuration: The next hop is not directly connected. Influence Cause Handling The static route is invalid. The next hop is not directly connected or is not through due to some exceptions. Check whether the configured parameters are correct.
IP OFFLINE SET: IP Address not Exists

Notification Information Notification information has the following contents: Notification code: 20559 Notification description: IP offline configuration: The IP address does not exist. Cause Handling The IP address does not exist or not configured properly. Check whether the configured parameters are correct.
IP OFFLINE SET: MAC beyond Valid Space

Notification Information Notification information has the following contents: Notification code: 20562 Notification description: IP offline configuration: The MAC address exceeds the range. Cause Handling The MAC address exceeds the range. Check whether the configured parameters are correct.
52
IP OFFLINE SET: DB MAC Operation-Type Invalid

Notification Information Notification information has the following contents: Notification code: 20563 Notification description: IP offline configuration: The MAC configuration type provided by the database is incorrect. Cause Handling The MAC configuration type configured in the database is incorrect. Check whether the configured parameters are correct.
IP OFFLINE SET: Invalid IP Broadcast Address

Notification Information Notification information has the following contents: Notification code: 20565 Notification description: IP offline configuration: Invalid broadcast address. Cause Handling The broadcast address configuration is invalid. Check whether the configured parameters are correct.
IP OFFLINE SET: The Number of IP Address on this Port cannot Exceed 4

Notification Information Notification information has the following contents: Notification code: 20566 Notification description: IP offline configuration: interface can configure maximum of four IP addresses. Cause Handling One
IP address conflict because interface can configured maximum of four IP addresses. Check whether the configured parameters are correct.
OSPF Virtual Link State Changed

Notification Information Notification information has the following contents:
53
Notification code: 21315 Notification description: The status of the OSPF virtual interface is changed. Influence Cause Handling The virtual link couldnt 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 Information Notification information has the following contents: Notification code: 21316 Notification description: The status of the OSPF interface is transferred. Influence Cause Handling The two routers couldnt establish adjacency relation. 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 Information Notification information has the following contents: Notification code: 21326 Notification description: The status of the OSPF virtual neighbor is transferred. Influence Cause Handling If the neighbors state is synchronized between them. down, database can not be
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 Information Notification information has the following contents: Notification code: 21327 Notification description: The status of the OSPF neighbor is transferred.
54
Influence Cause Handling
If the neighbors state is synchronized between them.
down,
database
can
not
be
The status of the neighbor of the interface is changed. Check the physical link and the configuration parameters of the neighbor.
LSDB Overflow
Notification Information Notification information has the following contents: Notification code: 21329 Notification description: The LSDB (Link Status DataBase) overflows. Cause Handling 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 Information Notification information has the following contents: Notification code: 21328 Notification description: OSPF finds there are LSAs with same lS_ID. Cause Handling 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 Neighbors FSM Error

Notification Information Notification information has the following contents: Notification code: 21586 Notification description: Error in the BGP neighbor limited status machine. Influence Cause Handling BGP cant connect to the peer successfully. There are errors in the limit of neighbor status machine. Check the BGP event.
55
BGP State Change

Notification Information Notification information has the following contents: Notification code: 21607 Notification description: The status of the BGP is transferred. Cause Handling The status machine is changed. Check the BGP connection status.
Half-Fixed Connection is Changed Abnormally

Notification Information Notification information has the following contents: Notification code: 25664 Notification description: abnormally changed. Influence Cause The half-fixed connection is
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.
Handling
Handle the notification referring to the following operations: 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 Information Notification information has the following contents: Notification code: 3136 Notification description: The disk is full. Cause 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.
56
Handling
Release the space of the disk after backing up the data.
GE Port Config not Match

Notification Information Notification information has the following contents: Notification code: 5187 Notification description: The configuration of connected to the fiber of the GLI is inconsistent. Influence Cause Handling Media layer is down. The fiber connection between the GLI and inconsistent with the background configuration. the UIM is the port
Check the GLI optical interface connection relation on the background, and modify the fiber connection according to the configuration.
UIM CS Changeover
Notification Information Notification information has the following contents: Notification code: 5188 Notification description: The big T-net of the UIM switches over. Cause Handling 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 Information Notification information has the following contents: Notification code: 5189 Notification description: master/slave switchover. Influence Cause Handling 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.
57
FE Port State Change from Up state to Down

Notification Information Notification information has the following contents: Notification code: 5190 Notification description: The FE routing port is broken. Cause Influence Handling 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 Information Notification information has the following contents: Notification code: 5191 Notification description: The status of the UIM TFS optical interface has changed. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 5192 Notification description: The board does not support the working mode. Influence Cause Boards 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.
58
Such reasons as FPGA not loading cause that there are errors in setting the working mode for the board. Handling 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 Information Notification information has the following contents: Notification code: 26176 Notification description: The clock reference is changed. Influence Cause Handling 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 Information Notification information has the following contents: Notification code: 26177 Notification description: The reference quality of the CLKG board is changed. Influence Cause Handling Exception in clock-related operations. The reference quality of the CLKG board is changed. Check the CLKG board.
CLKG Work Mode Changed

Notification Information Notification information has the following contents: Notification code: 26178 Notification description: The working mode of the clock of the CLKG board changes. Influence Cause Handling Exception in clock-related operations. The clock work mode of the CLKG board is changed. Check the clock.
59
Circuit is not Set Up in MSCe

Notification Information Notification information has the following contents: Notification code: 16777794. Notification description: Circuit is not set up in MSCe. Cause Handling MSCe do not have installed circuit. Handle the notification referring to the following operations: Check the trunk configuration. Add available trunking system.
OMP Restart
Notification Information Notification information has the following contents: Notification code: 50331712. Notification description: OMP restarts. Cause Handling OMP system restarts automatically. Observe the relevant alarms and notifications while restart of the system and clear the fault.
Exception of CPU Loop

Notification Information Notification information has the following contents: Notification code: 2880. Notification description: Exception of CPU loop. Cause Handling Procedure is on the hook of dead loop. Check the process code has endless loop.
Tone DSP CPU and DSP Version Differ

Notification Information Notification information has the following contents: Notification code: 5709. Notification description: Tone DSP CPU and DSP Version Differ. Cause Handling Tone DSP CPU and DSP Version Differ. Instead DSP Version.
60
HP Server Power Supply Power off

Notification Information Notification information has the following contents: Notification code: 58720257. Notification description: HP server power supply power off. Cause Handling HP Server power supply status changed. Check HP server power supply.
ABPM Board's PMC7389 is Reset

Notification Information Notification information has the following contents: Notification code: 18754. Notification description: ABPM board's PMC7389 is reset. Cause Handling 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 Information Notification information has the following contents: Notification code: 58720258. Notification description: HP Server power supply power on. Cause Handling HP Server power supply status changed. Check HP server power supply.
Alarm When Data Configuration MNIC/2 Physical Board-related is Error

Notification Information Notification information has the following contents: Notification code: 16704. Notification description: Data configuration MNIC/2 physical board-related has error that has created an alarm. Cause Handling Alarm when data configuration MNIC/2 physical board-related is error. Reboot the system.
61
Error Occurs During MCU Running

Notification Information Notification information has the following contents: Notification code: 5705. Notification description: Error occurs during MCU running. Cause Handling Error occurs during MCU board has some exceptions. Check the status of the board and MCU.
Timer for ISIS Creates Fail

Notification Information Notification information has the following contents: Notification code: 22592. Notification description: Timer for ISIS creates fail. Cause Handling Timer for ISIS creates fail. Please restart ISIS.
ISIS Hello Packet Authentication Fail

Notification Information Notification information has the following contents: Notification code: 22593. Notification description: ISIS Hello packet authentication fail. Cause Handling ISIS Hello packet authentication fails due to some configuration exceptions. Change the configuration under interface.
ISIS LSP Packet Authentication Fail

Notification Information Notification information has the following contents: Notification code: 22594. Notification description: ISIS LSP packet authentication fail. Cause Handling ISIS LSP packet authentication confguration has some exeptions. Change the configuration of ISIS.
62
ISIS SNP Packet Authentication Fail

Notification Information Notification information has the following contents: Notification code: 22595. Notification description: ISIS SNP packet authentication fail. Cause Handling ISIS SNP packet authentication fails. Change the configuration of ISIS.
Ignored Packet for Differ Interface Version

Notification Information Notification information has the following contents: Notification code: 21065. Notification description: Ignored packet for differ interface version. Cause Handling Ignored packet for differ interface version. Modified RIP interface version.
Stack Overflow
Notification Information Notification information has the following contents: Notification code: 2624. Notification description: Stack Overflow. Cause Handling Stack Overflow. Increase stacks size.
Configure BFD Session Fails

Notification Information Notification information has the following contents: Notification code: 22848. Notification description: Configure BFD Session Fails. Cause Handling A problem in the configuration has affected BFD Session Fails. Check the BFD configuration.
63
Ec of Index Configed as Signal Link be Informed Enable

Notification Information Notification information has the following contents: Notification code: 25666. Notification description: EC of Index configed as signal link be informed enable. Cause Handling EC of Index configed as signal link be informed enable. Check trunk and signal configure.
Tone File System Initialization Failure

Notification Information Notification information has the following contents: Notification code: 5707. Notification description: Tone file system initialization failure. Cause Handling Flash unlawful data, file systum initialization failure. Format the flash disk.
Setting Work Mode of Outport is Forbid in This Board

Notification Information Notification information has the following contents: Notification code: 5706. Notification description: Setting work mode of outport is forbid in this board and is not accessible. Cause Handling 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

Notification Information Notification information has the following contents: Notification code: 8010.
64
Notification description: Multi-cpu board, unittype in r_unit is inconsistent with first-cpu's functype in r_cpuvermap. Cause Handling 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 Information Notification information has the following contents: Notification code: 8011. Notification description: DBS power on fail. Cause 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. Handling Select different action according to the causation.
User Office of M3UA States Modify Inform

Notification Information Notification information has the following contents: Notification code: 11840. Notification description: modification information. Cause Handling Siolocas is down. Active the SIO LOC as. User office of M3UA states
RIP Failed to Create RIP Instance

Notification Information Notification information has the following contents: Notification code: 21066. Notification description: RIP failed to create RIP instance. Cause Handling RIP failed to allocate memory. Please check the memory allocation.
65
OSPFV3 Routerid Conflict

Notification Information Notification information has the following contents: Notification code: 28224. Notification description: OSPFV3 routerid conflict. Cause Handling Router ID in Hello packet matches this router's Router ID. Modify the router's Router ID.
OSPFV3 Virtual Interface State Change

Notification Information Notification information has the following contents: Notification code: 28225. Notification change. Cause Handling description: OSPFV3 virtual interface state
OSPFV3 virtual interface state change. Check for the physical connection and configuration.
OSPFV3 Interface State Change

Notification Information Notification information has the following contents: Notification code: 28226. Notification description: OSPFV3 interface state change. Cause Handling OSPFV3 interface state changes due to some problem in configuration. Check for the physical connection configuration.
OSPFV3 Virtual Interface Configure Error

Notification Information Notification information has the following contents: Notification code: 28227. Notification description: OSPFV3 virtual interface configure error. Cause OSPFV3 virtual link configuration parameters are invalid or physical link problem.
66
Handling
Check for the hello interval, dead interval and option parameter on the interface.
OSPFV3 Interface Configure Error

Notification Information Notification information has the following contents: Notification code: 28228. Notification description: OSPFV3 interface configure error. Cause Handling OSPFV3 interface configuration interface is damaged in error. parameters are invalid or
Check for the hello interval, dead interval and option parameter on the interface.
OSPFV3 Virtual Neighbor State Change

Notification Information Notification information has the following contents: Notification code: 28229. Notification change. Cause Handling description: OSPFV3 virtual neighbor state
OSPFV3 virtual link neighbor state changed. Check for the physical connection and configuration.
OSPFV3 Neighbor State Change

Notification Information Notification information has the following contents: Notification code: 28230. Notification description: OSPFV3 neighbor state change. Cause Handling OSPFV3 virtual link neighbor state. Check for the physical connection and configuration.
OSPFV3 Routerid Invalid

Notification Information Notification information has the following contents: Notification code: 28231. Notification description: OSPFV3 routerid invalid. Cause OSPFV3: Configuration of Router ID has some exception.
67
Handling
Configure the router's RouterID.
OSPFV3 Instance Create Failure

Notification Information Notification information has the following contents: Notification code: 28232. Notification description: OSPFV3 instance failure. Cause Handling OSPFV3: Create OSPFV3 instance is failed due to low memory. Add More Memory.
80G Chip Error

Notification Information Notification information has the following contents: Notification code: 28736. Notification description: 80g chip error. Cause Handling 80g test some gliqp has down or 80g chip error. If err happened frequently,reboot psn8p.
CS Fiber Change Over

Notification Information Notification information has the following contents: Notification code: 5194. Notification description: CS Fiber changes over it state. Cause 1. Server Send CMD_FIBER_CHANGEOVER MML Command To GUIM Board. 2. CS Fiber Por Error and auto ChangeOver. Handling 1. Check Server Send CMD_FIBER_CHANGEOVER Command To GUIM Board MML
2. Check GUIM Board Fiber Port Act Light 3. Check 5191 Inform.
Switch Version Fail

Notification Information Notification information has the following contents: Notification code: 5960. Notification description: Switch version fail. Cause Handling Slave board has master process when upgrade EPLD. Switch master process in slave board to slave process.
68
OMP Version Check Infomation

Notification Information Notification information has the following contents: Notification code: 5961. Notification description: OMP version check infomation. Cause Handling The version file recorded in DB doesnt exist. Add the requisite version file and remove the unused.
DBS MALLOC Memory Fail

Notification Information Notification information has the following contents: Notification code: 8012. Notification description: Dbs malloc memory fails. Cause Handling OSS malloc memory failure results in DBS malloc memory failure. Select different action according to the cause.
RIPng Interface is Disable

Notification Information Notification information has the following contents: Notification code: 29505. Notification description: RIPng interface is no accessible. Cause Handling 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 Information Notification information has the following contents: Notification code: 29507. Notification description: RIPng failed to create RIP instance. Cause Handling RIPng failed to allocate memory. Please check the memory allocation.
69
LAN91 Error
Notification Information Notification information has the following contents: Notification code: 26692. Notification description: LAN91 Error. Cause Handling LAN91 Error. Re-Initialize LAN91 chip.
Some HSSLS are Out of Sync

Notification Information Notification information has the following contents: Notification code: 19520. Notification description: Some HSSLS are out of sync. Cause Handling 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 Information Notification information has the following contents: Notification code: 20545. Notification description: IP OFFLINE SET: No IP unnumbered first. Cause Handling IP OFFLINE SET is due to wrong configuration parameters. Check the configuration parameters are correct.
Communication Notification
Description This section introduces the following notifications:
Work Mode Difference with DB Trunk Configuration

Notification information Notification information has the following contents: Notification code: 5702
70
Notification description: The trunk configuration inconsistent with the function of the board. Influence Cause Handling The board resets automatically.
is
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 information Notification information has the following contents: Notification code: 18241 Notification description: The TCP connection is broken. Cause Handling Connecting/re-transmitting times out or the invalid TCP message is received. Check the corresponding link is accessible.
IUA AS State Transform

Notification Information Notification information has the following contents: Notification code: 16779586 Notification description: The state of IUA AS has changed. Cause Handling The state of IUA AS has changed. Check the IUA AS working.
IUA ASP State Transform

Notification Information Notification information has the following contents: Notification code: 16779587 Notification description: The state of IUA ASP has changed. Cause Handling The state of IUA ASP has changed. Check the of IUA ASP.
71
72
Appendix
Abbreviations
Abbreviation 1X EV 1X EV-DO 1X EV-DV 3G 3GPP2 AAA APGW API ATM BCSN BCTC BER BPSN BS BSC BSS BTS BUSN CACH CAS CBC CCS CDMA CF CFB CFBI Full Name 1X Evolution 1X Evolution Data Only 1X Evolution Data & Voice The third generation mobile communications 3rd Generation Partnership Project 2 Access, Authorization, and Accounting Access Point Gateway Application Programming Interface Asynchronous Transfer Mode Backplane of Circuit Switch Network Backplane of ConTrol Center Bit Error Ratio Backplane of Packet Switch Network Base Station Base Station Controller Base Station System Base Transceiver Station Backplane of Universal Switch Network Common AsSIGnment Channel Channel Associated SIGnaling Cell broadcast center Common Channel SIGnaling Code Division MultIPle Access all Call Forwarding services Call Forward Busy Central Fiber Bus Interface
73
Abbreviation CFD CFNA CFNRc CFNRy CFU CIC CKCD CLKG CNIP CNIR CP CPM CPSN CRC CSM DPC DTB DTI DTU ESME FDMA FEP FN FPGA FTAM FTP GIF GMSCe GPRS GSM GT GUI HDLC HLRe HTML HTTP
Full Name Call Forward Default Call Forward No Answer Call Forward No Reachable Call Forward No Reply Call Forward Unconditional Circuit IDentification Code Central Clock and Communication Driver CLOCK Generator Call Number IDentification Presentation Call Number IDentification Restriction Content ProvIDer Common SIGnaling Process Module Central Power Switching Network Cyclic redundancy check Central Switching Module Destination SIGnaling Point Code Digital Trunk Board Digital Trunk Interface Digital Trunk Unit External Short Message Entity Frequency Division MultIPle Access Front-End Processor Fleet Number Field Programmable Gate Array File transfer access management File Transfer Protocol Graphics Interchange Format Gateway MSCe General Packet Radio Service Global System for Mobile communications Global Title Graphical User Interface High level data link control Home Location Register emulator Hyper Text MakeUP Language Hypertext Transfer Protocol
74
Appendix A Abbreviations
Abbreviation HW I/O IMSI IPI IRM ISDN ISO ISUP ISUP IWF kbps LMSD MC MDN MGW MIN MNC MNIC MPB MS MSCe MSID MSS MTP MTP1 MTP2 MTP3 NGN NMC NMS OMC OMM OPC OTA PDA PDN
Full Name High speed data Way Input/Output International Mobile Subscriber IDentity IP bearer Interface International Roaming MIN Integrated Service Digital Network International Standardization Organization ISDN User Part ISDN User Protocol InterWorking Function kilo-bits per second Legacy Mobile Station Domain Message Center Mobile Data Number Media Gateway Mobile Station IDentify Number Mobile Network Code Multi-service Network Interface Card Main Processing Board Mobile Station Mobile Switching Center emulator Mobile Station IDentifier Mobile Switching System Message Transfer Part Message Transfer Part-layer 1 Message Transfer Part-layer 2 Message Transfer Part-layer 3 Next Generation Network Network Management Center Network Management Subsystem Operations & Maintenance Center Operation Maintenance Module Originating SIGnaling Point Code Over The Air Personal Digital Assistant Packet Data Network
75
Abbreviation PDSN PDSS PN PPP PPPoE PSN PSPDN PSTN PTT PWRD RADIUS RAID SC SCCP SCP SCPe SDH SDTB SGW SID SIO SIPI SLS SME SMG SMPP SMS SMTP SNM SNMP SOAP SP SPB STM TDMA TLDN
Full Name Packet Data Serving Node Packet Data Switching System Personal Number Point to Point Protocol Point to Point Protocol over Ethernet Packet Switch Network Packet Switched Public Data Network Public Switched Telephone Network Push-To-Talk POWER Distributor Remote Authentication Dial In User Service Redundant Array of Independent Disks Short message Center SIGnaling connection control part Service control point Service Control Point emulator Synchronous Digital Hierarchy SONET Digital Trunk Board SIGnaling Gateway system IDentify Service Information Octet SIGnaling IP bearer Interface SIGnaling Link Selection Short Message Entity Short Message Gateway Short Message Peer-to-Peer protocol Short Message Service Simple Message Transfer Protocol Service Network Module Simple Network Management Protocol Simple Object Access Protocol Service ProvIDer SIGnaling Processing Board Synchronous Transfer Mode Time Division MultIPle Access Temporary Location Digital Number
76
Appendix A Abbreviations
Abbreviation UBC UIM VMSCe VPN WAP WDP WDSS WIN WVPN
Full Name all-User BroadCast User IDentity Module Visited MSCe Virtual Private Network Wireless Application Protocol Wireless Datagram Protocol Wireless Data Services System Wireless Intelligent Network Wireless Virtual Private Network
77
78
Appendix
Collection of Notification Information

Notifica tion Classifi cation 2 2 2 2 2 1 2 2 2 2 2 2 2 2 1 2 2 2 2 1 Notifi cation Code 576 832 833 1600 2624 2625 2880 3136 5187 5188 5189 5190 5191 5192 5193 5194 5441 5448 5700 5701
Notification Name
P.No.
Trunk slip Global Underflow Global Overflow Board Abnormally Resets Stack Overflow The Process is in the Dead Lock Exception of CPU Loop Disk is Full GE Port Config not Match UIM CS Changeover Master and Slave Change over FE Port State Change from Up state to Down UIM TFS Port State Change Board's Workmode is not Supported Powering Information about Basic Process CS Fiber Change Over HSSL Break Off between GLI and PSN 485 Offline Set Fail DSP Runtime Error Backboard Switch Set Change
40 40 41 41 63 40 60 56 57
57 58 58 58 37 68 41 41 42 42
79
Notifica tion Classifi cation 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1
Notifi cation Code 5702 5703 5705 5706 5707 5709 5956 5957 5958 5960 5961 8000 8001 8002 8003 8004 8005
Notification Name
P.No.
Work Mode Difference with DB Trunk Configuration Backboard Switch Set Change Error Occurs During MCU Setting Work Mode of Outport is Forbid in This Board Tone File System Initialization Failure Tone DSP CPU and DSP Version Differ Version Error Occur on This Board Doc Space is not Enough to Save Version-File IDE Files Synchronization Information Switch Version OMP Version Check DBs Table Load Failure Master to Slave Sync Failure OMP to MP Sync Failure MP to PP Sync Failure Failure of Saving One Table DBs File-Buffer Overflow If the Times of Sending Message go beyond the Limit, OAM Back Receives Notification Information about the Message Save File Fail in Master or Slave Path, Inform with Failed Path Loading Version-Table from File-Reg is Fail because of Nonexistent Domain or Incompatible Domain Type DBS Require Configuration Failed Multi-CPU Board ,Unittype in R_unit is Inconsistent with First-CPU's Functype in R_CPUVERMAPE DBS Power on DBS MALLOC Memory SCCP GT Translation is Error NID is Unequipped NID Translation of NID Failed ISNI Constrained Route
70 42 62 64 64 60 42 43 43 68 69 4 4 4 5 5 5
8006
8007
1 1 2 2 2 1 1 1 1
8008 8009 8010 8011 8012 10304 10305 10306 10307
7 7 64 65 69 7 8 8 8
80
Appendix B Collection of Notification Information
Notifica tion Classifi cation 1 1 2 1 1 1 1 1 2 1 2 2 2 2 2 2 2 2 2 1 2
Notifi cation Code 10308 10309 10560 10822 10823 11328 11329 11330 11840 12608 13632 13633 13888 13889 13890 13891 14144 15936 16192 16193 16448
Notification Name
P.No.
ISNI cannot Support Route Indicator NID Identify Failure SSCS no Response Registers Registration Defeat Failed to Configure Multi-channel Controller Failed to Configure Digital Switch Chip Failed to Get Config Information from Database User Office of M3UA States Modify Inform SUA GT Translation Failed M2PA Link is Congested M2PA Processor is Outage Inform of the Change of ASP Status Inform of the Change of AS Status Receiving ERROR Message Receiving NTFY Message Association Establish Fail INFORM_MCS_2400_CONFIGERROR Configuration Data Received from Database is Abnormal or Error Happened when Updating Configuration Data SIG_IPI Transmits Packets Abnormal The NP C5 can't Get PVC from DBS or the PVC can't be Configured in C5's TLU The NP C5 Received AAL2 Establishing/Release Message, but C5 Operation Alarm When Data Configuration MNIC/2 Physical Board-related is IP Fail to Get Route Table Head or Entry Deletion Static Routing Clause defeat IP Has no Match EPU Global Port IP Create or Enable IFB Fail EPU down EPU Remove
9 9 43 9 9 10 10 10 65 11 44 44 44 45 45 45 45 46 47 11 48
16449
48
2 1 1 2 1 1 1
16704 17984 17985 17986 17987 17990 17991
61 11 12 49 12 12 13
81
Notifica tion Classifi cation 1 1 3 1 1 1 1 1 2 2 1 1
Notifi cation Code 17992 18240 18241 18496 18497 18498 18752 18753 18754 18754 19008 19009
Notification Name
P.No.
IP OPR Static RTE Fail: Add SRTE. TCP Received RST Packet TCP Connection Aborted PPP Detect Wrong While Receive UidIpInfoAck PPP Detect Wrong While Receive BSCIP from DB PPP Detect Wrong While Receive UID UPD Config from DB Failed to Initialize The Configuration Data about UID/HDLC Received by LDM from Database Error ABPM board's PMC7389 is ABPM Board's PMC7389 is Configure Port Failed Creat Inner (Inter) Unilateral (BiDirectional) Connection (Multi) PVC Failed Delete Inner (Inter) Unilateral (BiDirectional) Connection (Multi) PVC Failed IMA Group Related Operation Failed IMA Link Related Operation Failed Some HSSLS are Out of SFrame Mode Error is Serious CFrame is doffed Because of Horizontal Check Error CFrame is doffed because of Vertical Cframe is doffed because of not Integrity Cframe is doffed because It is not Valid Cframe is Losted because of its Length is not Valid Frame is Losted because of out of Order Frame is Losted because of CRC Check Error Configuration IXP2400 Failed Configuration VSC872 Failed Aps Switch L2FWDTBL Init Fail
13 13 71 1314 14 14 14 15 49 61 15 16
1 1 1 2 1 2 2 2 1 1 1 1 1 1 1 1
19010 19264 19265 19520 19521 19522 19523 19524 19525 19526 19527 19528 19529 19530 19777 20032
17 17 17 70 18 18 18 19 19 19 20 20 20 21 21 22
82
Notifica tion Classifi cation 1 1 1 1 2 2 2 1 1 1 2 2 2 1 2 1 2 2 2 1 2 2 1 2 2 1
Notifi cation Code 20033 20288 20289 20290 20544 20545 20545 20546 20547 20548 20549 20550 20553 20554 20555 20556 20557 20558 20559 20561 20562 20563 20564 20565 20566 20567
Notification Name
P.No.
L2FWDTBL Init UIM Media eth Fail Brs Main Configure Request Timeout Brs Main RPU Register Timeout Brs Protocol Process Power-on Fatal Failed IP OFFLINE SET: The Interface is not Exist or is not an Ethernet Interface IP OFFLINE SET: No IP Unnumbered First IP OFFLINE SET: NO IP Unnumbered IP OFFLINE SET: Add Interface Address Failed IP OFFLINE SET: Set DB Failed IP OFFLINE SET: Delete the IP Address Failed IP OFFLINE SET: Invalid Host Address IP OFFLINE SET: Invalid Next Hop IP OFFLINE SET: Inconsistent Address and Mask IP OFFLINE SET: Add IP Route Failed IP OFFLINE SET: No Matching Route to Delete IP OFFLINE SET: Delete Route Failed IP OFFLINE SET: Next Hop Conflict IP OFFLINE SET: Next Hop not IP OFFLINE SET: IP Address not Exists IP OFFLINE SET: Not Ethernet Interface IP OFFLINE SET: MAC beyond Valid Space IP OFFLINE SET: DB MAC OperationType Invalid IP OFFLINE SET: a Same Prefix IP Address Exist IP OFFLINE SET: Invalid IP Broadcast Address IP OFFLINE SET: The Number of IP Address on this Port cannot Exceed 4 IP OFFLINE SET: The Input Parameter is Null
22 22 23 23 50 50 70 23 24 24 50 51 51 24 51 25 51 52 52 25 52 53 25 53 53 25
83
Notifica tion Classifi cation 1 1 1 1 1 1 1 1 1 1 1 2 2 1 2 2 1 1 1 1 2 2 2 1 1 1 1 1 1 1
Notifi cation Code 20568 20569 20570 20800 20801 20802 20803 21059 21060 21063 21064 21065 21066 21312 21315 21316 21319 21320 21324 21325 21326 21327 21329 21568 21570 21572 21573 21575 21576 21579
Notification Name
P.No.
IP OFFLINE Cfg: The IP Address Already Exists IP Offline Cfg: The IP Address Already Exists Invalid Mask or ARP Allocate Memory Instance Fail ARP Allocate Memory Fail for ARP Cache IP Address Collided with the Others Found Duplicate MAC Address in the ARP Packet RIP Configure Neighbor Fail RIP Interface Authentication Fail RIP Interface is Disabling RIP Interface is Enabling Ignored Packet for Differ Interface RIP Failed to Create RIP The Router Id in the HELLO Package which OSPF Received is same as the Router id of OSPF Virtual Link State Changed OSPF Interface State Changed OSPF Virtual Interface Configure in Error OSPF Interface Configure in Error OSPF Virtual Interface Authentication Fail OSPF Interface authentication Fail OSPF Virtual Neighbor State Change OSPF Neighbor State Change LSDB Overflow Create BGP Instance Fail BGP Create Neighbor Fail BGP Cant Get TCB for Passive Listen BGP Cant Get TCB for Active Connect BGP Enable Passive Listen TCB Fail BGP Enable Active Connect TCB Fail BGP Add Neighbor to Group Fail
26 26 26 27 27 27 27 28 28 28 29 63 65 29 53 54 29 30 30 30 54 54 55 31 31 31 32 32 32 32
84
Notifica tion Classifi cation 2 2 1 1 1 1 1 1 1 1 2 2 2 2 2 1 1 1 1 2 1 2 2 2 2 1 2 2 2 2
Notifi cation Code 21580 21581 21582 21584 21586 21607 21825 21831 21837 22336 22592 22593 22594 22595 22848 23104 23105 23106 23107 25664 25665 25666 26176 26177 26178 26179 26692 28224 28225 28226
Notification Name
P.No.
BGP Interface is Down, and Neighbor Disconnects BGP Interface Address Changed, and Neighbor Disconnects BGP Neighbor Read Receive Buffer Fail BGP Neighbor Hold Timer Expired BGP Neighbors FSM Error BGP State Change Courier Create BGP Instance Fail Courier Enable OSPF by the RTR_ID Fail Courier Synch IP Route Table Error MAC Addreses Conflict While Computing or Deleting It Timer for ISIS Creates ISIS Hello Packet Authentication ISIS LSP Packet Authentication ISIS SNP Packet Authentication Configure BFD Session Fails Alarm Pool is Over in OAM Alarm Manager Process OAM Agent Receive Refuse Alarm Inform Board Self-Checking Defeat Board Initialization Defeat Half-Fixed Connection is Changed Abnormally Half Fixedly Connection Configuration Data is Error Ec of Index Configed as Signal Link be Informed Enable CLK Base Change CLKG Frequence Base Quality Changed CLKG Work Mode Changed Base Invalid Reason Changed LAN91 Error OSPFV3 Routerid OSPFV3 Virtual Interface State OSPFV3 Interface State
33 33 33 34 55 56 34 34 35 35 62 62 62 63 63 35 36 36 36 56 37 64 59 59 59 37 70 66 66 66
85
Notifica tion Classifi cation 2 2 2 2 2 2 2 2 2 1 1 2 1 1 3 1 1 1 1 3 3 2 2 2
Notifi cation Code 28227 28228 28229 28230 28231 28232 28736 29505 29507 167777 92 167777 93 167777 94 167777 95 167777 96 167780 48 167780 49 167780 52 167795 84 167795 85 167795 86 167795 87 503317 12 587202 57 587202 58
Notification Name
P.No.
OSPFV3 Virtual Interface Configure OSPFV3 Interface Configure OSPFV3 Virtual Neighbor State OSPFV3 Neighbor State OSPFV3 Routerid OSPFV3 Instance Create 80G Chip RIPng Interface is RIPng Failed to Create RIP Fail to Reset MSCe Fail to Reset Circuit in MSCe Circuit is not Set Up in MSCe Block CIC Failed Unblock CIC Failed Fail to Use BCM Long Bill Base Station IUA Receives the Notify Message IUA Receives Error Message IUA AS State Transform IUA ASP State Transform OMP Restart HP Server Power Supply Power off HP Server Power Supply Power
66 67 67 67 67 68 68 69 69 38 38 60 38 38 38 39 39 39 39 71 71 60 61 61
86
Tables
Table 1 Chapter Summary ....................................................i Table 2 Typographical Conventions ....................................... ii Table 3 Mouse Operation Conventions ................................... ii
87
88
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
89

ZTE Media Gateway 2nd

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE Media Gateway 2nd

Загружено:

Авторское право:

Доступные форматы

ZXC10 MGW

cdma2000 Media Gateway

Alarm and Notification Information (2)

ZTE CORPORATION Values Your Comments & Suggestions!

This page is intentionally blank.

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

Chapter 2.......................................................................... 3 Notification Information.................................................. 3

Device Notification ........................................................ 40

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

This page is intentionally blank.

About This Manual

Prerequisite Skill and Knowledge

What is in This Manual

Chapter Chapter 1, General Concept Chapter 2, Notification Information

Confidential and Proprietary Information of ZTE CORPORATION

Typeface Italics Quotes Bold

CAPS Constant width [] {} |

Mouse Operation Conventions

TABLE 3 MOUSE OPERATION CONVENTIONS

Typeface Click Double-click Right-click Drag

Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

How to Get in Touch

Confidential and Proprietary Information of ZTE CORPORATION

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Mechanism of Notification Generation

Confidential and Proprietary Information of ZTE CORPORATION

General Flow of Handling Notifications

Confidential and Proprietary Information of ZTE CORPORATION

Handling Error Notification

Confidential and Proprietary Information of ZTE CORPORATION

DBs Table Load Failure

Master to Slave Sync Failure

OMP to MP Sync Failure

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Notification Information

Failure of Saving One Table

DBs File-Buffer Overflow

Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Notification Information

DBS Require Configuration Failed

SCCP GT Translation is Error

Confidential and Proprietary Information of ZTE CORPORATION

NID Translation of NID Failed

ISNI Constrained Route Repeat

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Notification Information

ISNI cannot Support Route Indicator

NID Identify Failure

Confidential and Proprietary Information of ZTE CORPORATION

Failed to Configure Multi-channel Controller

Failed to Configure Digital Switch Chip

Failed to Get Config Information from Database

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2 Notification Information

SUA GT Translation Failed

SIG_IPI Transmits Packets Abnormal

IP Fail to Get Route Table Head or Entry

Confidential and Proprietary Information of ZTE CORPORATION

Deletion Static Routing Clause defeat

IP Create or Enable IFB Fail

Confidential and Proprietary Information of ZTE CORPORATION