0% found this document useful (0 votes)

91 views

HLR Alarm Message Reference

This document provides a summary of communication and processing error alarms that may occur in the ZXUN USPP (Universal Subscriber Profile Platform). It includes 3 chapters that describe specific alarms related to communication issues, processing errors, and internal hardware/software issues. Each alarm is given a unique identification number and brief explanation. The document also provides contact information for technical support.

Uploaded by

Long Nguyen Thanh

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

91 views

HLR Alarm Message Reference

Uploaded by

Long Nguyen Thanh

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 204

ZXUN USPP

Universal Subscriber Profile Platform

HLR Alarm Message Reference

Version: V4.11.10

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION
Copyright © 2011 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

Revision No. Revision Date Revision Reason

R1.1 2011-06-10 Updated some alarm names.

R1.0 2011-04-15 First edition.

Serial Number: SJ-20110221160004-013

Publishing Date: 2011-06-10(R1.1)

Contents
About This Manual ......................................................................................... I
Declaration of RoHS Compliance ................................................................. I
Chapter 1 Introduction to Alarms ............................................................. 1-1
1.1 Functions and Applications ................................................................................. 1-1
1.2 Related Information ............................................................................................ 1-2

Chapter 2 Communication Alarms............................................................ 2-1

2.1 The Control Plane Retransfer Ratio over the Threshold (3841).............................. 2-2
2.2 Communication Abnormal Between RS485 Management Board and
Environmental Board (5382).............................................................................. 2-2
2.3 Communication of RAWMAC Channel Is Abnormal (5397).................................... 2-3
2.4 Sunit State Abnormal (5406) .............................................................................. 2-4
2.5 M3UA User Office Status Change (11840) ........................................................... 2-5
2.6 M2PA Processor Outage (13633) ........................................................................ 2-5
2.7 Association Establishment Failure (14144)........................................................... 2-6
2.8 Timing of Near-End IMA Group Fault (19208)....................................................... 2-7
2.9 Near-End Transmitting Link Disconnection (19212) .............................................. 2-7
2.10 LIF Alarm of Near-End Receiving Link (19213) ................................................... 2-8
2.11 LODS Alarm of Near-End Receiving Link (19214) ............................................... 2-9
2.12 RDI Alarm of Near-End Receiving Link (19215) ................................................ 2-10
2.13 Near-End Receiving Link Fault (19216)............................................................ 2-10
2.14 Near-End Receiving Link Disconnection (19218) ...............................................2-11
2.15 Near-End IMA Group Fault (19223) ................................................................. 2-12
2.16 Ethernet Link Fault Alarm (29952) ................................................................... 2-12
2.17 Near-End TC Link Fault (41737) ...................................................................... 2-13
2.18 Control Plane Communication Abnormal Between Board and Its Home Module
(8393985) ...................................................................................................... 2-14
2.19 Control Plane Communication Abnormal Between MP and OMP (8393988) ....... 2-14
2.20 SCCP Subsystem Unavailable (8398848) ........................................................ 2-15
2.21 MTP2 Link Sending Overload (8399872).......................................................... 2-17
2.22 MTP2 Link Reception Overload (8399873) ....................................................... 2-18
2.23 MTP3 Link Unavailable (8400129) ................................................................... 2-19
2.24 MTP3 Office Inaccessible (8400128) ............................................................... 2-20
2.25 MTP3 Cluster Inaccessible (8400130).............................................................. 2-20

I
2.26 M3UA Office Inaccessible (8400384) ............................................................... 2-21
2.27 SUA Subsystem Unavailable (8401152)........................................................... 2-22
2.28 SUA Office Inaccessible (8401153).................................................................. 2-24
2.29 Association Link Broken (8402690).................................................................. 2-25
2.30 PPP Link Broken (8407043) ............................................................................ 2-26
2.31 BFD Session Interrupted (8411392) ................................................................. 2-28
2.32 BFD Session Negotiation Failed (8411393) ...................................................... 2-30
2.33 Association Path Broken (8417537) ................................................................. 2-31
2.34 Bearer Network is Unavailable (8419073) ........................................................ 2-33
2.35 Bearer Network Get Worse (8419074) ............................................................. 2-34
2.36 Broadband Link Unavailable (8429568) ........................................................... 2-35
2.37 Link to Specified Node Broken (2534034688)................................................... 2-36
2.38 Link Broken Between NE and NM Server (2365981697) ................................... 2-36
2.39 Link Broken Between Alarm Box and NM Server (2365981698) ........................ 2-37

Chapter 3 Processing Error Alarms.......................................................... 3-1

3.1 CPU Utilization Over Alarm Limit (2560) .............................................................. 3-2
3.2 The System Brueau Changed (4357)................................................................... 3-4
3.3 Configuration Conflicts Between OMP and CMM (5381) ....................................... 3-4
3.4 Lack of Version (5908)........................................................................................ 3-5
3.5 Download Version Failed (5909).......................................................................... 3-6
3.6 Process Execute Failed (5910)............................................................................ 3-6
3.7 PVC Faults (18944) ............................................................................................ 3-7
3.8 Near-End IMA Group Configuration Failure (19207).............................................. 3-7
3.9 Protocol Stack Requested System Configuration Information Timeout (20225) ....... 3-8
3.10 The Number of Board Physical Alarms Exceeds the Threshold (23042) ............... 3-9
3.11 Connection Check Be Disabled in Board (25600).............................................. 3-10
3.12 Port is in Ethernet OAM Loopback State (29953).............................................. 3-10
3.13 clock synchronization over Alarm Limit (8392706) .............................................3-11
3.14 Request Time From SNTP Server Failed (8392707) ......................................... 3-12
3.15 Broadband Link Congestion (8399104) ............................................................ 3-12
3.16 Broadband Link Overload (8399105) ............................................................... 3-14
3.17 MTP3 Link Congestion (8400131) ................................................................... 3-15
3.18 MTP3 Link Sending Flow Control Alarm (8400132)........................................... 3-16
3.19 The Number of OMP Alarms Exceeds the Threshold (8411649) ........................ 3-16
3.20 The Number of Board Logical Alarms Exceeds the Threshold (8411651)............ 3-17
3.21 Internal Controlled Account Number and Password Will Expire Soon
(2365980929)................................................................................................. 3-18

II
3.22 Internal Controlled Account Number and Password Already Expired
(2365980930)................................................................................................. 3-20
3.23 Internal Controlled Account Number and Password Do Not Meet Requirements
(2365980931)................................................................................................. 3-21
3.24 3 Consecutive Wrong Passwords During Login (2365980932)........................... 3-22
3.25 License File Illegal (2365981441) .................................................................... 3-23
3.26 License File Unavailable (2365981443) ........................................................... 3-24
3.27 Multiple License Files Exist (2365981444)........................................................ 3-24
3.28 Loaded License File Expires (2365981445)...................................................... 3-25
3.29 Create Agent Diary File Failed (2533521408) ................................................... 3-26
3.30 Failed to Upload Agent Diary (2533521409) ..................................................... 3-26
3.31 MMDB Tuple Check Failed (2533968405) ........................................................ 3-27
3.32 MMDB Page Check Failed (2533968406) ........................................................ 3-27
3.33 Service PDB Occupation Alarm (2534019079) ................................................. 3-28
3.34 DBIO Server Is Overload (2534029312)........................................................... 3-28
3.35 DBIO Modified Local Agent Password Fail (2534029313).................................. 3-29
3.36 User Capacity Beyond License Capacity (2534029320) .................................... 3-29
3.37 Auth Capacity Beyond AdminDomani Capacity (2534029321) ........................... 3-30
3.38 HLR Has Failed Over to Other HLRs, the Links to Other NEs Are Blocking
(2534031360)................................................................................................. 3-30
3.39 HLR Can Provide Service for Other NEs, the Links to Other NEs Are
Unblocked. The BOSS Request Has Been Permitted (2534031361) .................. 3-32
3.40 HLR Has Provided Services for Standby Subscriber from Now (2534031362) ..... 3-34
3.41 HLR Stops to Provide Service for Standby Subscriber from Now
(2534031363)................................................................................................. 3-36
3.42 Serious Error Found, HLR Try to Block All Link to Other NEs, the Operation
Has Failed (2534031364) ................................................................................ 3-37
3.43 UDS Node Has Received too Many Messages Within a Time (2534033667) ...... 3-39
3.44 The User Capacity of Each DSA Node in DSA Group Has Been Full
(2534033668)................................................................................................. 3-40
3.45 Capacity of User Table Is Full (2534033920) .................................................... 3-41
3.46 Capacity of HLR User DB Is Full (2534033922) ................................................ 3-42
3.47 Percentage of Free Space on Logical Structures Beneath (2534033923) ........... 3-42
3.48 Disk Full (2534034176)................................................................................... 3-43
3.49 Problem With Operations Read/Write on the Physical Structures of the
Database (2534034177).................................................................................. 3-43
3.50 Resume Failed Because The Capacity of Backup Node Is Undersize
(2534034432)................................................................................................. 3-44
3.51 UDS Synch Power On Fail (2534034433) ........................................................ 3-45

III
3.52 Resume Failed Because The Capacity of Slave Node Is Less Than The High
Water in The Master Node (2534034434)......................................................... 3-45
3.53 Schema Control Module Failed to Check Configure Data Compatibility
(2534034689)................................................................................................. 3-46
3.54 The DR Synchronize Requests Can't Be Sent to Backup HLR in Time
(2534035457)................................................................................................. 3-47
3.55 the Occupancy of System CPU is Above Fatal Level (2535082240)................... 3-48
3.56 the Occupancy of System CPU Is above Serious Level (2536130816) ............... 3-49
3.57 the Occupancy of System CPU Is above Common Level (2537179392)............. 3-50

Chapter 4 QoS Alarms ............................................................................... 4-1

4.1 Association Congested (8402688) ....................................................................... 4-1
4.2 STC Office Congested (8402945)........................................................................ 4-2
4.3 Performance Qos Critical Alarm (2365980673)..................................................... 4-3
4.4 Performance Qos Major Alarm (2365980674) ...................................................... 4-4
4.5 Performance Qos Common Alarm (2365980675) ................................................. 4-6
4.6 Performance Qos Warning Alarm (2365980676) .................................................. 4-7
4.7 ITU TCAP Service Overload (2534025218).......................................................... 4-8
4.8 SMP Report SHLR NNI Interface Level 1 Overload Alarm (2539268097) ............... 4-9
4.9 SMP Report SHLR NNI Interface Level 2 Overload Alarm (2538219521) ............... 4-9
4.10 SMP Report SHLR NNI Interface Level 3 Overload Alarm (2537170945) ........... 4-10
4.11 SMP Report SHLR NNI Interface Level 4 Overload Alarm (2536122369)............ 4-10
4.12 SMP Report SHLR NNI Interface Level 5 Overload Alarm (2535073793) ............4-11
4.13 SMP Report MAP Interface Level 1 Overload Alarm (2539268096).....................4-11
4.14 SMP Report MAP Interface Level 2 Overload Alarm (2538219520).................... 4-12
4.15 SMP Report MAP Interface Level 3 Overload Alarm (2537170944).................... 4-12
4.16 SMP Report MAP Interface Level 4 Overload Alarm (2536122368).................... 4-13
4.17 SMP Report MAP Interface Level 5 Overload Alarm (2535073792).................... 4-13

Chapter 5 Equipment Alarms .................................................................... 5-1

5.1 OMC Port Link Is Down (256).............................................................................. 5-3
5.2 Trunk Frame Loss (512) ..................................................................................... 5-3
5.3 Trunk Signal Loss (513) ...................................................................................... 5-4
5.4 Trunk Alarm Indication (514) ............................................................................... 5-5
5.5 Trunk Multi-frame Loss (515) .............................................................................. 5-5
5.6 Far End Alarm (517) ........................................................................................... 5-6
5.7 Trunk Link Is Used for CSU Loopback Test (518).................................................. 5-6
5.8 Cell Delineation do not Synchronization About Cell on E1/T1 Link (1026)............... 5-7
5.9 Clock Board Is in Preheat Status (1285) .............................................................. 5-8

IV
5.10 Loss of Clock When Input to Board (1286) ......................................................... 5-8
5.11 CPU Resets on a Board in the Same Shelf (1600) .............................................. 5-9
5.12 FLASH Device Initialize Failed (3073) .............................................................. 5-10
5.13 The Configuration Does Not Supported (5123) ................................................. 5-10
5.14 Board Config Information not Compatible (5200) ...............................................5-11
5.15 Packet Test of Internal Media Plane Is Abnormal (5396).................................... 5-12
5.16 Clock Board Work Mode Is Abnormal (5405) .................................................... 5-13
5.17 The Hard Disk Used-Rate Is over Threshold (5632) .......................................... 5-13
5.18 The Hard Disk Becomes Error or not Exist (5633)............................................. 5-14
5.19 Sub Card Abnormal (5645) ............................................................................. 5-14
5.20 Phase-Lock Loop Unlock (5646)...................................................................... 5-15
5.21 Error Packets of MAC Is Higher than the Specified Threshold (5666) ................. 5-16
5.22 Oscillator Status Abnormal (5670) ................................................................... 5-17
5.23 MAC Port Link Is Down (5760) ........................................................................ 5-17
5.24 The Speed Mode of the Port Doesn't Match with Settings (5761) ....................... 5-18
5.25 One Frequency of Clock Is All Lost when Input to Board (5768)......................... 5-19
5.26 The Master and Slave Mode of the Port Doesn't Match with Settings (5769)....... 5-20
5.27 The OMP Board Doesn't Have OMC Port (5770) .............................................. 5-20
5.28 The Duplex Mode of the Port Doesn't Match with Settings (5771) ...................... 5-21
5.29 Board Device Fault (5772) .............................................................................. 5-22
5.30 High CRC Error Rate at E1 Bottom Layer (5773) .............................................. 5-22
5.31 High FAS Error Rate at E1 Bottom Layer (5774) ............................................... 5-23
5.32 High EBIT Error Rate at E1 Bottom Layer (5775).............................................. 5-23
5.33 Subcard is Formatting Flash (5786) ................................................................. 5-24
5.34 Subcard Works in Genernal Error (5787) ......................................................... 5-24
5.35 Subcard Works in Critical Error (5788) ............................................................. 5-25
5.36 Subcard Works in Fatal Error (5789)................................................................ 5-26
5.37 Functional Epld Update Fail (5890).................................................................. 5-26
5.38 Inner Port Error (7169).................................................................................... 5-27
5.39 Media Status Abnormal (15360) ...................................................................... 5-27
5.40 Too Many Bad Frames Received (15618)......................................................... 5-28
5.41 The Fan Tray Is Off (23050) ............................................................................ 5-29
5.42 The PEM Is Off (23051) .................................................................................. 5-29
5.43 Abnormal Half-Fixed Connection Changes (25602) .......................................... 5-30
5.44 RACK Temperature Is Higher than High Threshold (25856)............................... 5-30
5.45 RACK Temperature Is Lower than Low Threshold (25857) ................................ 5-31
5.46 Room Temperature Is Higher than High Threshold (25858) ............................... 5-32

V
5.47 Room Temperature Is Lower than Low Threshold (25859)................................. 5-33
5.48 Voltage Is Higher than High Threshold (25860)................................................. 5-34
5.49 Voltage Is Lower than Low Threshold (25861) .................................................. 5-35
5.50 Humidity Is Higher than High Threshold (25862)............................................... 5-36
5.51 Humidity Is Lower than Low Threshold (25863) ................................................ 5-36
5.52 Fault in Fan Plug-In Box (25864) ..................................................................... 5-37
5.53 Rack Door Access Control Alarm (25865) ........................................................ 5-38
5.54 Smoke Alarm (25866) ..................................................................................... 5-39
5.55 Infrared Alarm (25867).................................................................................... 5-40
5.56 Lightning Alarm (25868).................................................................................. 5-41
5.57 Power Switch Alarm (25869) ........................................................................... 5-41
5.58 Power Type Configured Does Not Accord with Physical (25870)........................ 5-43
5.59 Clock Reference Source Lost (Level 3 Alarm) (26127) ...................................... 5-43
5.60 Clock Reference Source Lost (Level 2 Alarm) (26128) ...................................... 5-44
5.61 Clock Reference Source Lost (Level 1 Alarm) (26129) ...................................... 5-45
5.62 Output Clock Lost (26133) .............................................................................. 5-45
5.63 Velocity of fan is Lower Than Lower-critical Threshold (30734) .......................... 5-46
5.64 Velocity of fan is Lower Than Lower-non-critical Threshold (30745) ................... 5-46
5.65 Velocity of fan is Lower Than Lower-non-recoverable Threshold (30746) ........... 5-47
5.66 IPMB State Change (IPMB-A Enable \ IPMB-B Disable) (30812) ....................... 5-48
5.67 IPMB State Change (IPMB-A Disable\IPMB-B Enable) (30813) ......................... 5-48
5.68 STC Office Inaccessible (8402944).................................................................. 5-49
5.69 NM Server CPU Usage Rate Exceeds Criterion (2365981185) .......................... 5-49
5.70 NM Server Memory Usage Rate Exceeds Criterion (2365981186) ..................... 5-51
5.71 NM Server Hard Disk Usage Rate Exceeds Criterion(Level 1 Alarm)
(2365981187) ................................................................................................. 5-52
5.72 NM Server Hard Disk Usage Rate Exceeds Criterion(Level 2 Alarm)
(2365981188) ................................................................................................. 5-53
5.73 NM Server Hard Disk Usage Rate Exceeds Criterion(Level 3 Alarm)
(2365981189) ................................................................................................. 5-55
5.74 NM Server Hard Disk Usage Rate Exceeds Criterion(Level 4 Alarm)
(2365981190) ................................................................................................. 5-57
5.75 Directory Usage Rate Exceeds Criterion (Level 1 Alarm) (2365981191) ............. 5-58
5.76 Directory Usage Rate Exceeds Criterion (Level 2 Alarm) (2365981192) ............. 5-60
5.77 Directory Usage Rate Exceeds Criterion (Level 3 Alarm) (2365981193) ............. 5-62
5.78 Directory Usage Rate Exceeds Criterion (Level 4 Alarm) (2365981194) ............. 5-64
5.79 Link Between DBIO and HSMAPP Node Broken (2534029328)......................... 5-66
5.80 HSMAPP Node Status Error (2535069704) ...................................................... 5-66

VI
Chapter 6 Environment Alarms................................................................. 6-1
6.1 Temperature Is Lower Than Lower-non-critical Threshold (30721) ......................... 6-1
6.2 Temperature Is Lower Than Lower-critical Threshold (30722)................................ 6-2
6.3 Temperature Is Lower Than Lower-non-recoverable Threshold (30723) ................. 6-2
6.4 Temperature Is Higher Than Upper-non-critical Threshold (30724) ........................ 6-3
6.5 Temperature Is Higher Than Upper-critical Threshold (30725) ............................... 6-4
6.6 Temperature Is Higher Than Upper-non-recoverable Threshold (30726) ................ 6-5
6.7 Voltage Is Lower Than Lower-non-critical Threshold (30727)................................. 6-5
6.8 Voltage Is Lower Than Lower-critical Threshold (30728) ....................................... 6-6
6.9 Voltage Is Lower Than Lower-non-recoverable Threshold (30729)......................... 6-7
6.10 Voltage Is Higher Than Upper-non-critical Threshold (30730) .............................. 6-7
6.11 Voltage Is Higher Than Upper-critical Threshold (30731) ..................................... 6-8
6.12 Voltage Is Higher Than Upper-non-Recoverable Threshold (30732)..................... 6-9
6.13 Filter Tray Is Present for Too Long (Non-Recoverable) (30735)............................ 6-9
6.14 Filter Tray Is Present for Too Long (Critical) (30736) ......................................... 6-10
6.15 Filter Tray Is Present for Too Long (Non-Critical) (30737) .................................. 6-10
6.16 State Is Abnormal (30738) ...............................................................................6-11

Glossary .......................................................................................................... I

VII
VIII
About This Manual
Purpose
This manual introduces the alarms related to ZXUN USPP (HLR), including communication
alarms, processing error alarms, QoS alarms, equipment alarms and environment
alarms. In addition, the basic information and causes of each alarm, the impacts of each
corresponding fault on the system, and the handling method for each alarm are provided.

Intended Audience
This manual is intended for engineers and technicians who perform maintenance activities
on ZXUN USPP (HLR).

Prerequisite Skill and Knowledge

To use this guide effectively, you should have a general understanding of wireless
telecommunications technology. Familiarity with the following is helpful:
l ZXUN USPP (HLR) system and its various components
l User interfaces on OMM/EMS Client

What is in This Manual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Introduction to Alarms Introduces the concepts about alarm messages, alarm
functions and related information about this manual.

Chapter 2, Communication Alarms Introduces the causes, impact on the system, and handling
methods for communication alarms.

Chapter 3, Processing Error Alarms Introduces the causes, impact on the system, and handling
methods for processing error alarms.

Chapter 4, QoS Alarms Introduces the causes, impact on the system, and handling
methods for QoS alarms.

Chapter 5, Equipment Alarms Introduces the causes, impact on the system, and handling
methods for equipment alarms.

Chapter 6, Environment Alarms Introduces the causes, impact on the system, and handling
methods for environment alarms.

FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions.

I
1. This device may not cause harmful interference.
2. This device must accept any interference received, including interference that may
cause undesired operation.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.

Conventions
ZTE documents employ the following typographical conventions.

Typeface Meaning

Italics References to other manuals or documents.

“Quotes” Links on screens.

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

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

Note: Provides additional information about a certain topic.

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

proceeding further.

Tip: Indicates a suggestion or hint to make things easier or more productive

for the reader.

II
Declaration of RoHS
Compliance
To minimize environmental impacts and take more responsibilities to the earth we live on,
this document shall serve as a formal declaration that ZXUN USPP (HLR) manufactured
by ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following
substances:
l Lead (Pb)
l Mercury (Hg)
l Cadmium (Cd)
l Hexavalent Chromium (Cr (VI))
l PolyBrominated Biphenyls (PBBs)
l PolyBrominated Diphenyl Ethers (PBDEs)

ZXUN USPP (HLR) manufactured by ZTE CORPORATION meets the requirements of EU

2002/95/EC; however, some assemblies are customized to client specifications. Addition of
specialized, customer-specified materials or processes which do not meet the requirements of
EU 2002/95/EC may negate RoHS compliance of the assembly. To guarantee compliance of the
assembly, the need for compliant product must be communicated to ZTE CORPORATION in written
form.
This declaration is issued based on our current level of knowledge. Since conditions of use are
outside our control, ZTE CORPORATION makes no warranties, express or implied, and assumes no
liability in connection with the use of this information.

I
II
Chapter 1
Introduction to Alarms
Table of Contents
Functions and Applications.........................................................................................1-1
Related Information ....................................................................................................1-2

1.1 Functions and Applications

Functions and Applications
The alarm management system performs real-time monitoring on the running status
of the entire system. When a fault occurs, it provides the fault information for the
administrators on screens and informs administrators of the system abnormalities. The
system administrators can locate and eliminate the faults according to the content and
level of a alarm. The system stability is thus ensured.

Basic Concepts
l Alarm Message
Alarm messages are prompts provided upon the concurrence of problems or faults
during the running of each NE equipment.
Alarms persist till all corresponding problems or faults have been removed.
l Alarm Type
This manual introduces the following types of alarms:
à Communication alarms: alarms related to the information transmission process.
à Processing error alarms: alarms related to software and process errors.

à QoS alarms: alarms related to QoS.

à Equipment alarms: alarms related to equipment faults.

à Environment alarms: alarms related to the environment where the equipment is

located.
l Alarm Code

An alarm code identifies an alarm message. The combination of an alarm code and
a system type can uniquely distinguish an alarm message from others in the alarm
system.
l System Type

1-1

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

System types indicate the locations where the alarm messages occur. The system
types involved in the alarm messages include:
à NE Alarm: alarms reported by network element.
à OMM System Alarm: alarms reported by the OMM system.
à Peripheral Node Alarm: alarms reported by the peripheral node.
l Alarm Level
Alarms can be divided into four levels in term of severities:
à The Critical level indicates that a service affecting condition has occurred and an
immediate corrective action is required.
à The Major level indicates that a service affecting condition has developed and an
urgent corrective action is required.
à The Minor level indicates the existence of a non-service affecting fault condition
and that corrective action should be taken in order to prevent a more serious (for
example, service affecting) fault.
à The Warning level indicates the detection of a potential or impending service
affecting fault, before any significant effects have been felt. Action should be
taken to further diagnose (if necessary) and correct the problem in order to
prevent it from becoming a more serious service affecting fault.
If the alarm level of an alarm is not known, that means the alarm is used as a threshold
alarm, whose level dynamically varies.

1.2 Related Information

Alarm Information
The manual provides alarm information, causes, impacts on the system, and handling
methods for each alarm.
l The alarm information includes the alarm code, type, level and description of each
alarms.
l Causes refer to the possible causes for the generated alarms.
l Impacts on the system refer to the probable influences on the system after an alarm
is generated.
l Handling methods refer to the methods used to eliminate faults after the alarms are
generated.

For alarm management operations, refer to:

l ZXUN USPP Universal Subscriber Profile Platform Alarm Management Operation
Guide (EMS Volume)
l ZXUN USPP Universal Subscriber Profile Platform Alarm Management Operation
Guide (OMM Volume)

1-2

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 1 Introduction to Alarms

Introduction to Network Construction of NMS

The network of the ZXUN USPP (HLR) product is constructed in single layer or in
distributed mode.
l In the distributed mode, the NMS is composed of EMS and OMM, and the MML
commands are distributed on both OMM and EMS.
l In single layer, the NMS is composed of OMM, and the MML commands are distributed
on only OMM.
The MML commands used for the distributed network construction and single-layer
network construction are identical, except that the commands are in different paths.
This manual takes the distributed network construction as an example to introduce the
alarm handling process.

1-3

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

This page intentionally left blank.

1-4

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2
Communication Alarms
Table of Contents
The Control Plane Retransfer Ratio over the Threshold (3841)...................................2-2
Communication Abnormal Between RS485 Management Board and Environmental
Board (5382) ..............................................................................................................2-2
Communication of RAWMAC Channel Is Abnormal (5397).........................................2-3
Sunit State Abnormal (5406) .....................................................................................2-4
M3UA User Office Status Change (11840) .................................................................2-5
M2PA Processor Outage (13633) ...............................................................................2-5
Association Establishment Failure (14144) .................................................................2-6
Timing of Near-End IMA Group Fault (19208).............................................................2-7
Near-End Transmitting Link Disconnection (19212) ....................................................2-7
LIF Alarm of Near-End Receiving Link (19213)...........................................................2-8
LODS Alarm of Near-End Receiving Link (19214) ......................................................2-9
RDI Alarm of Near-End Receiving Link (19215)........................................................2-10
Near-End Receiving Link Fault (19216) ....................................................................2-10
Near-End Receiving Link Disconnection (19218)......................................................2-11
Near-End IMA Group Fault (19223)..........................................................................2-12
Ethernet Link Fault Alarm (29952) ............................................................................2-12
Near-End TC Link Fault (41737)...............................................................................2-13
Control Plane Communication Abnormal Between Board and Its Home Module
(8393985).................................................................................................................2-14
Control Plane Communication Abnormal Between MP and OMP (8393988).............2-14
SCCP Subsystem Unavailable (8398848) ................................................................2-15
MTP2 Link Sending Overload (8399872) ..................................................................2-17
MTP2 Link Reception Overload (8399873) ...............................................................2-18
MTP3 Link Unavailable (8400129)............................................................................2-19
MTP3 Office Inaccessible (8400128) ........................................................................2-20
MTP3 Cluster Inaccessible (8400130) ......................................................................2-20
M3UA Office Inaccessible (8400384)........................................................................2-21
SUA Subsystem Unavailable (8401152) ...................................................................2-22
SUA Office Inaccessible (8401153) ..........................................................................2-24
Association Link Broken (8402690) ..........................................................................2-25
PPP Link Broken (8407043) .....................................................................................2-26
BFD Session Interrupted (8411392)..........................................................................2-28
BFD Session Negotiation Failed (8411393) ..............................................................2-30
Association Path Broken (8417537) .........................................................................2-31
Bearer Network is Unavailable (8419073).................................................................2-33
Bearer Network Get Worse (8419074)......................................................................2-34

2-1

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Broadband Link Unavailable (8429568)....................................................................2-35

Link to Specified Node Broken (2534034688)...........................................................2-36
Link Broken Between NE and NM Server (2365981697) ..........................................2-36
Link Broken Between Alarm Box and NM Server (2365981698) ...............................2-37

2.1 The Control Plane Retransfer Ratio over the

Threshold (3841)
Alarm Information
l Alarm code: 3841
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The control plane retransfer ratio succeeds the threshold.

Causes
l Boards are badly connected in the environment. As a result, retransmission of control
plane messages is increased.
l An Ethernet communication device works improperly on the board or switching board.
l Addresses of TIPC nodes conflict.

Impact on the System

The inter-board control-plane messages may be sent after a delay.

Handling
Record the current alarm information and contact ZTE.

2.2 Communication Abnormal Between RS485

Management Board and Environmental Board
(5382)
Alarm Information
l Alarm code: 5382
l System type: NE alarm
l Alarm level: Major
l Alarm description: The 485 communication of the environment monitoring board is
interrupted.

2-2

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

Causes
l The connection between the switching board and the environment monitoring board
is unavailable, or the connection cable is faulty.
l The rack No. configured for the rack where the switching board resides is inconsistent
with the rack No. set on the DIP switches of the environment monitoring board.

Impact on the System

The power status and environmental status cannot be monitored. This poses severe
hidden troubles but does not affect services.

Handling
1. Reconnect the 485 cable between the environment monitoring board and the switching
board.
2. Ensure that the rack No. configured for the rack where the switching board resides is
consistent with the rack No. set on the DIP switches of the environment monitoring
board.

2.3 Communication of RAWMAC Channel Is Abnormal

(5397)
Alarm Information
l Alarm code: 5397
l System type: NE alarm
l Alarm level: Major
l Alarm description: The communication over the RAWMAC channel is abnormal.

Cause
The packet loss rate of the RAWMAC channel internal the board exceeds the preset
threshold (5% by default).

Note:

This alarm rarely occurs.

Impact on the System

The RAWMAC channel cannot transmit data properly.

2-3

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Handling
1. On the Fault Management view of NMS, check whether a relevant alarm is reported
on the switching board in the same shelf.
l Yes: Handle the problem according to the handling suggestions of the relevant
alarm.
l No: Go to step 2.
2. Replace the board with the alarm, and observe whether the alarm disappears.
l Yes: End.
l No: Go to step 3.
3. Replace the switching board in the same shelf, and observe whether the alarm
disappears.
l Yes: End.
l No: Go to step 4.
4. Plug the faulty board in another slot, and observe whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

2.4 Sunit State Abnormal (5406)

Alarm Information
l Alarm code: 5406
l System type: NE alarm
l Alarm level: Major
l Alarm description: The subunit is in abnormal state and unavailable.

Causes
l The process for reporting the sub-unit status runs improperly.
l The device corresponding to the sub-unit works improperly.

Impact on the System

Some system resources are unavailable.

Handling
1. Restart the board. Check whether the alarm disappears.
l Yes: End.
l No: Go to Step 2.
2. Replace the faulty board. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

2-4

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

2.5 M3UA User Office Status Change (11840)

Alarm Information
l Alarm code: 11840
l System type: NE alarm
l Alarm level: Major
l Alarm description: The M3UA user office status has changed.

Cause
The status of the AS to the office has changed.

Impact on the System

Services of the user on the office may be interrupted when the office is unreachable.

Handling
1. Check whether SIO location data has been configured for the user.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the user's SIO location data, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check whether the AS is active.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Activate the AS, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Contact ZTE.

2.6 M2PA Processor Outage (13633)

Alarm Information
l Alarm code: 13633
l System type: NE alarm
l Alarm level: Major
l Alarm description: It is the notification for M2PA processor fault.

Causes
l Local processor is faulty.
l The local MTP3 and the local M2PA fail to communicate.
l The peer-end processor is faulty.

2-5

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Handling
Check whether the IMA chip works properly and whether each link connects the
remote-end IMA group.
l Yes: Contact ZTE.
l No: Perform configurations to make sure that the chip and all links work properly, and
check whether the alarm disappears.
à Yes: End.
à No: Contact ZTE.

2.10 LIF Alarm of Near-End Receiving Link (19213)

Alarm Information
l Alarm code: 19213
l System type: NE alarm
l Alarm level: Major
l Alarm description: LIF alarm of the near-end receiving link

Cause
The E1/T1 link has physical faults.

Impact on the System

The IMA link is interrupted. If the associated IMA group has only one link, all services over
this IMA group will be interrupted. Otherwise only the bandwidth of the IMA group will be
affected. The number of the accesses of the upper-layer service related to the IMA group
will decrease, but the service will not be interrupted.

Handling
1. Check whether the E1/T1 link is correctly connected according to the network
construction plan.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Rectify the connection and observe whether the alarm disappears.
l Yes: End.

2-8

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l No: Go to Step 3.
3. In the alarm management view of NMS, check whether any E1/T1 link alarm exists on
the board.
l Yes: Handle the alarm according to the handling suggestions of the related
alarms. If the alarm still exists, go to Step 4.
l No: Go to Step 4.
4. Contact ZTE.

2.11 LODS Alarm of Near-End Receiving Link (19214)

Alarm Information
l Alarm code: 19214
l System type: NE alarm
l Alarm level: Major
l Alarm description: LODS alarm of the near-end receiving link

Causes
l Access clock is abnormal.
l The link transmission quality is bad.

Impact on the System

Handling
1. Check whether the clock indicators on the SWI2 board are in normal working status.
l Yes: Go to Step 2.
l Yes: Go to Step 3.
2. Check whether the clock access source is proper.
l Yes: Go to Step 4.
l No: Handle the alarms according to the alarm handling suggestions on the Fault
Management view of NMS. If the alarm still exists, go to Step 4.
3. Restart or replace SWI2 to check whether the alarm disappears.
l Yes: End.
l Yes: Go to Step 2.
4. Check whether there are any alarms for the E1/T1 link on the Fault Management view
of NMS.
l Yes: Handle the alarm according to relevant alarm handling suggestions.
l No: Contact ZTE.

2-9

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2.12 RDI Alarm of Near-End Receiving Link (19215)

Alarm Information
l Alarm code: 19215
l System type: NE alarm
l Alarm level: Major
l Alarm description: RDI alarm of the near-end receiving link

Causes
l IMA link on remote end is not in activated status.
l The receiving direction of the remote link is faulty.

MP and OMP (8393988)
Alarm Information
l Alarm code: 8393988

2-14

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l System type: NE alarm

l Alarm level: Major
l Alarm description: The control plane communication between MP and OMP is abnor-
mal.

Causes
l The MP board is configured in the database but not powered on.
l The MP board is powered on but the control plane link to the OMP is broken.

Impact on the System

l The inter-board control-plane communication is abnormal, which may cause loss of
control-plane messages.
l After the communication between the MP and OMP is interrupted, the status of the
units affiliated to this MP is unknown.

Handling
1. Check whether the switch board in the same shelf and the switch board where OMP
is positioned work improperly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Restore the above boards to normal working status, and observe whether the alarm
disappears.
l Yes: End.
l No: Go to Step 5.
3. Check whether the board is successfully powered on.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Successfully switch on the board and observe whether the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Contact ZTE.

2.20 SCCP Subsystem Unavailable (8398848)

Alarm Information
l Alarm code: 8398848
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The SCCP subsystem is invalid

2-15

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Causes
l The peer-end subsystem exits the service, and the peer end blocks the local
subsystem of the peer end or other factors at the peer end cause the subsystem to
be unavailable.
l The peer-end signaling point is unreachable.
l The peer-end MTP3 or M3UA user configurations do not include SCCP users.
l The local end blocks the related subsystem.
l The configuration data at the local end includes the configuration data of the peer-end
subsystem. However, the peer end does not have local subsystem configuration
information.
l The subsystem test message initiated by the local end is not sent to the peer end
normally, or the peer end does not normally process the subsystem test message
initiated by the local end.

Impact on the System

Users fail to send messages to or receive messages from the subsystem, new services
fail to access the office corresponding to the subsystem, and the existing services are
abnormal and may be released.

Handling
1. On the Fault Management view of NMS, check whether there is any alarm prompting
this adjacent office inaccessible.
l Yes: If there are alarms prompting inaccessible MTP3 office or M3UA office,
handle the alarms by following the alarm handling suggestions in 2.24 MTP3
Office Inaccessible (8400128) or 2.26 M3UA Office Inaccessible (8400384).
l No: Go to Step 2.
2. Check the local data configuration to see whether the SSN is correctly configured in
local office configuration and adjacent office configuration.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Configure the SSN and check whether the alarm disappears after configuring the SSN.
l Yes: End.
l No: Go to Step 4.
4. Check the peer-end data configuration to see whether the SSN is correctly configured
in its local office configuration and adjacent office configuration.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Contact the peer-end personnel to configure the SSN and check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 6.
6. Back up the following data and contact ZTE.
l Configuration data related to local office and peer-end office.

2-16

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2.24 MTP3 Office Inaccessible (8400128)

Alarm Information
l Alarm code: 8400128
l System type: NE alarm
l Alarm level: Major
l Alarm description: MTP3 office is inaccessible.

Causes
l The office or route configuration is incorrect.
l The link is broken.

Impact on the System

The subscribers fail to send/receive messages to/from the relevant office.

Handling
1. Check whether the static route settings of the destination office are correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure or modify related static route. Check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Query the status of the link in the route list through the back-end dynamic management
to check whether any link is available.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Check alarms on the NMS to see whether there are alarms prompting no link available.
l Yes: Handle the alarms by following the alarm handling suggestions in 2.23 MTP3
Link Unavailable (8400129).
l No: Go to Step 5.
5. Record the following information and contact ZTE.
l Configuration data of the local office and peer-end office.
l History alarms, history notifications, and current alarms of the local office and
peer-end office.

2.25 MTP3 Cluster Inaccessible (8400130)

Alarm Information
l Alarm code: 8400130
l System type: NE alarm
l Alarm level: Major

2-20

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l Alarm description: The MTP3 cluster is inaccessible.

Causes
l The cluster and route configuration is incorrect.
l The link is broken.

Impact on the System

The subscribers fail to send/receive messages to/from the relevant office.

Handling
1. Check whether the static route configuration of the cluster is correct.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure or modify related static route. Check whether the cluster is accessible.
l Yes: End.
l No: Go to Step 3.
3. Query the link status in the route table through the dynamic management on NMS to
check whether there are available links.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Check alarms on the NMS to see whether there are alarms prompting that there are
no available MTP3 links.
l Yes: Handle the alarms by following the alarm handling suggestions in 2.23 MTP3
Link Unavailable (8400129).
l No: Go to Step 5.
5. Back up the following data and contact ZTE.
l Configuration data related to local office and peer-end office.
l History alarms, current alarms, and notifications that are related to the local office
and peer-end office.

2.26 M3UA Office Inaccessible (8400384)

Alarm Information
l Alarm code: 8400384
l System type: NE alarm
l Alarm level: Major
l Alarm description: The M3UA office is inaccessible.

Causes
l The association link is released or the AS has not entered serving state, which causes
office inaccessibility.

2-21

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l The peer office of the association link reports DUNA (destination signaling point is
unavailable) so that the office is unconnectable.

Impact on the System

Users fail to send messages to or receive messages from the office, new services cannot
access the office, and the existing services are abnormally released.

Handling
1. Check the configuration data to see whether SIO location of the office is configured.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the SIO location data and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check the data configuration to see whether the AS corresponding to the SIO location
of the office is activated.
l Yes: Go to Step 6.
l No: Go to Step 4.
4. Check whether ASPs on this AS are activated.
l Yes: If there are ASPs activated on this AS and the number of them exceeds the
necessary number, go to Step 7.
l No: If there is no ASP activated on this AS or the number of activated ASPs does
not reach the necessary number, go to Step 5.
5. Check whether the association of ASP is activated.
l Yes: If the association corresponding to the ASP is activated but the ASP is not
activated, go to Step 6.
l No: If the association corresponding to the ASP is not activated, perform further
handling according to the alarm for association unavailable.
6. Deactivate and then activate the associations serving the office, and check whether
the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Back up the following data and contact ZTE.
l Configuration data related to local office and peer office.
l History alarms, current alarms, and notifications that are related to the local office
and peer office.

2.27 SUA Subsystem Unavailable (8401152)

Alarm Information
l Alarm code: 8401152
l System type: NE alarm
l Alarm level: Minor

2-22

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l Alarm description: The SUA SSN is invalid.

Causes
l A signaling point subsystem exits the services.
l The association or AS is not in serving state, which causes signaling point
inaccessibility.
l SSN location AS is not configured.

Impact on the System

The subscriber fails to send/receive messages to/from the relevant subsystem.

Handling
1. On the Fault Management view of NMS, check whether there are corresponding
alarms for adjacent office inaccessibility.
l Yes: If there are alarms for SUA office inaccessibility, handle the alarms by
following the alarm handling suggestions in 2.28 SUA Office Inaccessible
(8401153).
l No: Go to Step 2.
2. Check configuration data of the local office to see whether the corresponding
subsystem is configured in local office configuration and adjacent office configuration.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Configure the subsystem and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Check configuration data of the peer-end adjacent office to see whether the
corresponding subsystem is configured in Local Office Configuration and Adjacent
Office Configuration.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. Contact the personnel of the peer-end office to configure the data. Check whether the
alarm disappears after the peer-end configuring the subsystem.
l Yes: End.
l No: Go to Step 6.
6. Record the following information and contact ZTE.
l Configuration data of the local office and peer-end office.
l History alarms, history notifications, and current alarms of the local office and
peer-end office.

2-23

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2.28 SUA Office Inaccessible (8401153)

Alarm Information
l Alarm code: 8401153
l System type: NE alarm
l Alarm level: Major
l Alarm description: The SUA office is inaccessible.

Causes
l The association or AS is not in serving state, which causes signaling point
inaccessible.
l No SSN location AS to all the subsystems of the office is configured.

Impact on the System

The subscriber fails to send/receive messages to/from the relevant office.

Handling
1. Check configuration data to see whether SSN location of the office is configured.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Configure the SSN location data and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check the data configuration to see whether the AS corresponding to the SSN location
of the office is activated.
l Yes: Go to Step 6.
l No: Go to Step 4.
4. Check whether ASPs on this AS are activated.
l Yes: If there are ASPs activated on this AS and the number of them exceeds the
necessary number, go to Step 7.
l No: If there is no ASP activated on this AS or the number of activated ASPs does
not reach the necessary number, go to Step 5.
5. Check whether the association of ASP is activated.
l Yes: If the association corresponding to the ASP is activated but the ASP is not
activated, go to Step 6.
l No: If the association corresponding to the ASP is not activated, perform further
handling according to the alarm for association unavailable.
6. Deactivate and then activate the associations serving the office, and check whether
the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Record the following information and contact ZTE.
l Configuration data of the local office and peer-end office.

2-24

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l History alarms, history notifications, and current alarms of the local office and
peer-end office.

2.29 Association Link Broken (8402690)

Alarm Information
l Alarm code: 8402690
l System type: NE alarm
l Alarm level: Major
l Alarm description: Association link is broken.

Causes
l The association link is manually released.
l All paths specified in association link configuration are interrupted, or the maximum
retransmission count of the association link is greater than the protocol attribute
configured for the association link.
l Other causes excluding association deletion cause the association interruption. For
specific causes, see additional information of the alarm.

Impact on the System

The association link is interrupted, and stops transmitting any data. In addition, the
upper-layer services may be affected. For example, the signaling office may be
unreachable, and the other available association links of the same office may be
congested.

Handling
1. On the Terminal or MML Terminal view of NMS, run the SHOW SCTP command
according to the association link number indicated in the additional alarm information
to check whether the association link configuration is correct. Check whether the
configured local port number, peer port number, IP addresses, and other items are
consistent on both ends, and whether the configured association client and server are
matched.
l Yes: Go to Step 3.
l No: Go to Step 2.

Note:

Table 2-1 shows an example of correct association link configuration.

2-25

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Table 2-1 Association Configuration

Association Local IP Local Port Remote IP Remote Port Applica-

tion At-
tribute

Local association a.b.c.d Port A w.x.y.z Port B Client

configuration

Remote w.x.y.z Port B a.b.c.d Port A Server

association
configuration

2. Run the SET SCTP command to modify the configuration data, synchronize the data,
and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check the alarm cause in the additional alarm information, so as to determine whether
the association link is manually blocked.
l Yes: Activate the association link by running ACT LNK command.
l No: Go to Step 4.
4. Check whether there is bottom layer transmission alarm.
l Yes: Forward the problem to a transmission engineer for further handling.
l No: Go to Step 5.
5. Record the following information and contact ZTE.
l Configuration data of the local office and peer-end office.
l History alarms, history notifications, and current alarms of the local office and
peer-end office.

2.30 PPP Link Broken (8407043)

Alarm Information
l Alarm code: 8407043
l System type: NE alarm
l Alarm level: Major
l Alarm description: The PPP link is broken.

Causes
l The physical link is broken or the link transmission quality degrades.
l A PPP port is created or modified.
l The active board is powered on or the standby board is successfully switched to the
active board.
l Modification of PPP link parameters causes link re-negotiation.
l The peer end of the link initiates negotiation again.
l The ports configured at both ends of the link are not consistent.

2-26

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

Impact on the System

Services are interrupted.

Handling
1. Wait a while and then check whether the system automatically recovers.
l Yes: End.
l No: Go to Step 2.
2. Check the PPP port number in the alarm information. Check whether the cable
between the devices at both ends is disconnected or loose.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Unplug and plug the cables, or replace the cables. Check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 4.
4. According to your network construction plan, check whether the E1/T1 cable is
incorrectly connected.
l Yes: Go to Step 5.
l No: Go to Step 6.
5. Re-connect the cable according to the network construction plan. Check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 6.
6. Check whether the configuration of the E1/T1 interface is inconsistent with the
configuration of the peer-end equipment connected by the physical cable.
l Yes: Go to Step 7.
l No: Go to Step 8.
7. Modify the configuration to make sure consistency between both ends. Check whether
the alarm disappears.
l Yes: End.
l No: Go to Step 8.
8. Check whether the connection relationship of the PPP ports at both ends is consistent.
l Yes: Go to Step 10.
l No: Go to Step 9.
9. Modify the configuration to make sure that the connection relations of the PPP ports
at both ends is consistent. Observe whether the alarm disappears.
l Yes: End.
l No: Go to Step 10.
10. Contact ZTE.

2-27

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2.31 BFD Session Interrupted (8411392)

Alarm Information
l Alarm code: 8411392
l System type: NE alarm
l Alarm level: Minor
l Alarm description: BFD session is interrupted.

Cause
l The BFD session is deleted at the peer end.
l The software for running the BFD session is faulty.
l The physical link where the BFD session runs is faulty.
l The device interface where the BFD session runs is faulty.
l There is congestion or packet loss on the link where the BFD session runs.

Impact on the System

BFD is used for reachability and link quality detection between the NE and the peer-end
device. BFD interruption indicates disconnection of the link to the peer-end device. All the
static routes that use the peer-end device as the next hop will be disconnected or switched.
If there is a standby route to the next hop, switching may occur. Otherwise, services are
interrupted.

Handling
1. Observe the alarm for some time and check whether the alarm automatically
disappears.
l Yes: No handling is required (BFD negotiation failure at the beginning may be
caused by the difference of the time configured at both ends. To further analyze
the fault, go to Step 11).
l No: Go to Step 2.
2. Check whether the physical connection indicators at both the source address interface
and the destination address interface of the BFD session are on.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Replace the network cable, or check all the network cables on the link where the
BFD session runs and plug them in place. Wait about 30 seconds. And again check
whether the physical connection indicators at both the source address interface and
the destination address interface of the BFD session are on, and whether the alarm
disappears.
l Yes: End.
l No: Go to Step 4.
4. On the Terminal or MML Terminal view of NMS, run the SHOW IP INTERFACE BRIE
F command to check whether the source and destination interfaces of the BFD session
are up.

2-28

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l Yes: Go to Step 5.
l No: Go to Step 12.
5. Check the packet transceiving performance statistics of the device where the BFD
session runs by using the performance statistics tool. Check whether the packet flow
between devices is too large and causes congestion or packet loss (there may be
malicious attacks).
l Yes: Go to Step 6.
l No: Go to Step 7.
6. Configure a packet filter policy (according to the actual networking and service
features) on the device to filter out useless packets. Wait about 30 seconds to check
whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. On the Terminal or MML Terminal view of NMS, run the PING command to check
whether the source and destination addresses of the BFD session can be successfully
connected using the ping command from each other.
l Yes: Go to Step 8.
l No: Go to Step 13.
8. Run the corresponding command at the peer end to check whether there is a session
corresponding to the BFD session at the local end.
l Yes: Go to Step 10.
l No: Go to Step 9.
9. Run the corresponding command at the peer end to configure the corresponding BFD
session. wait about 30 seconds to check whether the alarm disappears.
l Yes: End.
l No: Go to Step 10.
10. Check whether the BFD-related configurations were once modified.
l Yes: Go to Step 11.
l No: Go to Step 13.
11. On the Terminal or MML Terminal view of NMS, run the SHOW BFD GLOBAL PROP
command to check whether the BFD session parameter configurations and the BFD
session global configurations are correct according to the BFD configuration manual.
If authentication is configured, the authentication database configurations at both ends
must be consistent. If multiple hops are used, multiple hops should be configured at
both ends. And the BFD global attributes need to be set to Enable.
l Yes: Go to Step 13.
l No: Go to Step 12.
12. Modify incorrect BFD parameters according to the BFD configuration manual. wait
about 30 seconds to check whether the alarm disappears.
l Yes: End.
l No: Go to Step 13.
13. Contact ZTE.

2-29

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2.32 BFD Session Negotiation Failed (8411393)

Communications fail between the MP and the interface board Go to Step 3

Communications fail between the interface board and Go to Step 5

intermediate devices

Communications fail between intermediate devices Go to Step 7

3. Check whether the route configuration information is correct.

l Yes: Go to Step 5.
l No: Go to Step 4.
4. Modify the route configuration information, and then check the local segment is normal.
l Yes: End if the alarm disappears. Otherwise, go to Step 5.
l No: Go to Step 5.
5. Check whether the ports on the interface board are down.
l Yes: Go to Step 6.
l No: Go to Step 10.
6. Replace the network cables, and check whether the ports are up.

2-33

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Yes: End if the alarm disappears. Otherwise, go to Step 7.

l No: Go to Step 10.
7. Check whether the configuration information of the intermediate devices such as the
switch is correct.
l Yes: Go to Step 9.
l No: Go to Step 8.
8. Modify the configuration information, and then check the local segment is normal.
l Yes: End if the alarm disappears. Otherwise, go to Step 10.
l No: Go to Step 9.
9. Replace the intermediate devices, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 10.
10. Contact ZTE.

2.35 Bearer Network Get Worse (8419074)

Alarm Information
l Alarm code: 8419074
l System type: NE alarm
l Alarm level: Minor
l Alarm description: IPPD detects that packet lost rate of bearer network exceeds the
threshold.

Causes
l Packet loss occurs on any intermediate device.
l Packet loss occurs on a section of environment between both ends.

Impact on the System

Services on the bearer network may be affected.

Handling
1. Check whether any intermediate device is faulty:
l Yes: Go to Step 4.
l No: Go to Step 2.
2. Check whether network ports of the board work properly:
l Yes: Contact ZTE.
l No: Go to Step 3.
3. Check whether any hardware reason causes failure of network ports:
l Yes: Go to Step 4.
l No: Contact ZTE.
4. Replace the faulty device and check whether the link is normal:
l Yes: End.

2-34

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

l No: Go to Step 2.

2.36 Broadband Link Unavailable (8429568)

Alarm Information
l Alarm code: 8429568
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Alarm of SSCOP link in out of service.

Causes
l The bottom-layer physical transmission fails.
l The link initiated by the peer end is broken.
l Too many protocol-unmatched messages or error packets are received.

Impact on the System

The office direction may be unreachable and other available links may be congested.

Handling
1. Check whether the link data is newly configured or already modified.
l Yes: Go to Step 2.
l No: Go to Step 4.
2. Check the configuration of link data is consistent, especially the VPI and VCI of both
ends and the connecting ports.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Modify the configuration and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Check whether the bottom-layer transmission incurs any alarm.
l Yes: Deliver this problem to transmission engineers for handling.
l No: Go to Step 5.
5. Perform physical self-loop operations on the DDF for the devices at both ends of the
link. Check whether the link self-loop alarm disappears.
l Yes: Check the bottom-layer transmission and deliver the problem to transmission
engineers for handling.
l No: Go to Step 6.
6. Record the detailed information and contact ZTE.
l Back up related configuration data of the local and peer offices.
l Back up related history alarms, history notifications, and current alarms of the
local and peer offices.

2-35

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2.37 Link to Specified Node Broken (2534034688)

Alarm Information
l Alarm code: 2534034688
l System type: NE alarm
l Alarm level: Major
l Alarm description: The link is disconnected.

Cause
The physical link is disconnected.

Impact on the System

The communication is interrupted.

Handling
Check the physical link to the specified node.

2.38 Link Broken Between NE and NM Server

(2365981697)
Alarm Information
l Alarm code: 2365981697
l System type: OMM system alarm
l Alarm level: Critical
l Alarm description: The links between the NE and the OMM server are interrupted.

Cause
The OMM server detects that all the links between the node and the OMM server are
abnormal.

Impact on the System

NE data cannot be reported to the OMM, and configuration commands cannot be sent
from the OMM to the NE.

Handling
1. Check whether the physical connection between the disconnected node and the OMM
server is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.

2-36

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 2 Communication Alarms

2. Check whether the alarm disappears after confirming that the physical connection is
normal.
l Yes: End.
l No: Go to Step 3.
3. On the Terminal or MML Terminal view of NMS, run the SHOW OMPLNKSTAT
command to check whether the IP address and port of the node configured on the
OMM server have been occupied.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. On the Terminal or MML Terminal view of NMS, run the SET OMP command to
recreate OMM socket links, and then delete the wrongly configured link using the
DELETE OMSLINK command. After that, check whether the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Contact ZTE.

2.39 Link Broken Between Alarm Box and NM Server

(2365981698)
Alarm Information
l Alarm code: 2365981698
l System type: OMM system alarm
l Alarm level: Minor
l Alarm description: The link to the alarm box fails.

Cause
The communication link between the alarm box and the OMM server is broken.

Impact on the System

The alarm box is not connected and thus cannot report alarms to the OMM.

Handling
1. Check whether the physical connection between the disconnected node and the OMM
server is normal.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Check whether the alarm disappears after confirming that the physical connection is
normal.
l Yes: End.
l No: Go to Step 3.
3. On the Terminal or MML Terminal view of NMS, run the SHOW ALARMBOX
command to check whether the service-end monitoring port configured on the OMM

2-37

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

server is occupied, whether the alarm box address is consistent with that set on the
OMM server, and whether the alarm box address is not occupied.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. On the Terminal or MML Terminal view of NMS, run the SET ALARMBOX command
to modify the alarm box port settings, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Determine whether this alarm needs to be temporarily ignored.
l Yes: Go to Step 6.
l No: Go to Step 7.
6. On the Terminal or MML Terminal view of NMS, run the SET ALARMBOX command
to set Status to NO in the alarm settings of the OMM server, and then check whether
the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

2-38

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3
Processing Error Alarms
Table of Contents
CPU Utilization Over Alarm Limit (2560) .....................................................................3-2
The System Brueau Changed (4357) .........................................................................3-4
Configuration Conflicts Between OMP and CMM (5381).............................................3-4
Lack of Version (5908) ...............................................................................................3-5
Download Version Failed (5909).................................................................................3-6
Process Execute Failed (5910)...................................................................................3-6
PVC Faults (18944)....................................................................................................3-7
Near-End IMA Group Configuration Failure (19207) ...................................................3-7
Protocol Stack Requested System Configuration Information Timeout (20225)...........3-8
The Number of Board Physical Alarms Exceeds the Threshold (23042) .....................3-9
Connection Check Be Disabled in Board (25600) .....................................................3-10
Port is in Ethernet OAM Loopback State (29953) .....................................................3-10
clock synchronization over Alarm Limit (8392706) ....................................................3-11
Request Time From SNTP Server Failed (8392707).................................................3-12
Broadband Link Congestion (8399104) ....................................................................3-12
Broadband Link Overload (8399105) ........................................................................3-14
MTP3 Link Congestion (8400131) ............................................................................3-15
MTP3 Link Sending Flow Control Alarm (8400132) ..................................................3-16
The Number of OMP Alarms Exceeds the Threshold (8411649) ...............................3-16
The Number of Board Logical Alarms Exceeds the Threshold (8411651) .................3-17
Internal Controlled Account Number and Password Will Expire Soon (2365980929) .3-18
Internal Controlled Account Number and Password Already Expired (2365980930) .3-20
Internal Controlled Account Number and Password Do Not Meet Requirements
(2365980931)...........................................................................................................3-21
3 Consecutive Wrong Passwords During Login (2365980932) .................................3-22
License File Illegal (2365981441) .............................................................................3-23
License File Unavailable (2365981443)....................................................................3-24
Multiple License Files Exist (2365981444)................................................................3-24
Loaded License File Expires (2365981445)..............................................................3-25
Create Agent Diary File Failed (2533521408) ...........................................................3-26
Failed to Upload Agent Diary (2533521409) .............................................................3-26
MMDB Tuple Check Failed (2533968405) ................................................................3-27
MMDB Page Check Failed (2533968406).................................................................3-27
Service PDB Occupation Alarm (2534019079) .........................................................3-28
DBIO Server Is Overload (2534029312) ...................................................................3-28
DBIO Modified Local Agent Password Fail (2534029313).........................................3-29
User Capacity Beyond License Capacity (2534029320) ...........................................3-29

3-1

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Auth Capacity Beyond AdminDomani Capacity (2534029321)..................................3-30

HLR Has Failed Over to Other HLRs, the Links to Other NEs Are Blocking
(2534031360)...........................................................................................................3-30
HLR Can Provide Service for Other NEs, the Links to Other NEs Are Unblocked.
The BOSS Request Has Been Permitted (2534031361)...........................................3-32
HLR Has Provided Services for Standby Subscriber from Now (2534031362)..........3-34
HLR Stops to Provide Service for Standby Subscriber from Now (2534031363) .......3-36
Serious Error Found, HLR Try to Block All Link to Other NEs, the Operation Has
Failed (2534031364) ................................................................................................3-37
UDS Node Has Received too Many Messages Within a Time (2534033667)............3-39
The User Capacity of Each DSA Node in DSA Group Has Been Full (2534033668) .3-40
Capacity of User Table Is Full (2534033920) ............................................................3-41
Capacity of HLR User DB Is Full (2534033922)........................................................3-42
Percentage of Free Space on Logical Structures Beneath (2534033923) .................3-42
Disk Full (2534034176) ............................................................................................3-43
Problem With Operations Read/Write on the Physical Structures of the Database
(2534034177)...........................................................................................................3-43
Resume Failed Because The Capacity of Backup Node Is Undersize (2534034432) .3-44
UDS Synch Power On Fail (2534034433).................................................................3-45
Resume Failed Because The Capacity of Slave Node Is Less Than The High Water
in The Master Node (2534034434) ...........................................................................3-45
Schema Control Module Failed to Check Configure Data Compatibility
(2534034689)...........................................................................................................3-46
The DR Synchronize Requests Can't Be Sent to Backup HLR in Time
(2534035457)...........................................................................................................3-47
the Occupancy of System CPU is Above Fatal Level (2535082240) .........................3-48
the Occupancy of System CPU Is above Serious Level (2536130816) .....................3-49
the Occupancy of System CPU Is above Common Level (2537179392)...................3-50

3.1 CPU Utilization Over Alarm Limit (2560)

Alarm Information
l Alarm code: 2560
l System type: NE alarm
l Alarm level: Major
l Alarm description: CPU use is too high.

Cause
The following factors may result in an excessively high CPU rate:
l Data has been synchronized and saved.
l The version has been upgraded and it is necessary to save the upgraded version.
l The board has been restarted. It needs to be initialized, obtain data, and synchronize
data before entering the working status again.

3-2

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

l Services are busy and quite a number of calls need to be processed.

Impact on the System

l For a board where the CMM or OMP module is deployed, it may not respond to
man-machine commands in time when the alarm occurs.
l For other boards, call drop may be caused because the currently processed calls are
not handled in time, or new calls may fail to be connected.

Handling
l A board where the OMP or other module is deployed
1. Make sure whether data synchronization, saving and version upgrade operations
are performed, or the device is restarted before the alarm.
à Yes: Go to Step 2.
à No: Go to Step 3.
2. Wait 2 to 3 minutes to check whether the alarm disappears.
à Yes: End.
à No: Go to Step 3.
3. Confirm the board with an excessively high CPU rate according to the physical
location of the alarm information, and determine whether the high CPU rate is
caused by exceptions according to the three processes with the highest CPU rate
as indicated in the alarm information.
à Yes: Go to Step 7.
à No: Go to Step 4.
4. On the Terminal or MML Terminal view of NMS, run the SHOW CPUTHR
command to check the CPU rate threshold information and determine whether
the alarm is caused because the threshold value is too small.
à Yes: Go to Step 5.
à No: Go to Step 6.
5. Run the SET CPUTHR command under the guidance of ZTE technical support
personnel to reset the CPU rate threshold, and then check whether the alarm
disappears.
à Yes: End.
à No: Go to Step 6.
6. Contact ZTE technical support personnel to adjust the service structure and
migrate some of the services on the boards with an excessively high CPU rate to
other boards, and then check whether the alarm disappears.
à Yes: End.
à No: Go to Step 7.

3-3

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

7. Contact ZTE.
l A board where the CMM module is deployed.
1. Make sure whether data synchronization, saving and version upgrade operations
are performed, or the device is restarted before the alarm.
à Yes: Go to Step 2.
à No: Go to Step 3.
2. Wait 2 to 3 minutes, and then check whether the alarm disappears.
à Yes: End.
à No: Go to Step 3.
3. The board processing capability does not meet the requirements. Contact ZTE
technical support personnel in time to reduce the system capacity or add boards.

3.2 The System Brueau Changed (4357)

Alarm Information
l Alarm code: 4357
l System type: NE alarm
l Alarm level: Major
l Alarm description: The system bureau is changed.

Causes
The configuration of system bureau is changed.

Impact on the System

Restart system to validate the changed bureau configuration.

Handling
Restart the system, wait 30 seconds, check if the alarm is eliminated.
l Yes: End.
l No: Record the alarm information and contact ZTE.

3.3 Configuration Conflicts Between OMP and CMM

(5381)
Alarm Information
l Alarm code: 5400
l System type: NE alarm
l Alarm level: Major

3-4

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

l Alarm description: The data set through OMP itself is conflicting with the data set
through CMM.

Causes
l A slot is set to the OMP on the CMM, but the slot is not set to the OMP in the OMP
database.
l A slot is not set to the OMP on the CMM, but the slot is set to OMP in the OMP
database.

Impact on the System

The communication with the OMP fails.

Handling
Re-configure the physical address of the OMP on the OMP, or re-configure data on the
CMM according to the physical address configured on the OMP. Restart the OMP.
l Yes: End.
l No: Contact ZTE.

3.4 Lack of Version (5908)

Alarm Information
l Alarm code: 5908
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The version information returned by the version server is
incomplete.

Cause
The version information returned by the version server is incomplete.

Impact on the System

Certain board functions are lost.

Handling
Check the version server logs to find the missing version, and then add and activate the
version.

3-5

3-11

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

5. Check whether the NTP server time was once adjusted near the time of alarm
occurrence.
l Yes: The alarm is normal. If the alarm still exists after a clock synchronization
interval, go to Step 7.
l No: Go to Step 5.
6. Reset the clock synchronization interval of the foreground system, ensuring that it is
shorter than the current clock synchronization interval. After a clock synchronization
interval, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

3.14 Request Time From SNTP Server Failed (8392707)

Alarm Information
l Alarm code: 8392707
l System type: NE alarm
l Alarm level: Major
l Alarm description: The system fails to request time information from the SNTP server.

Cause
The system fails to request time information from the SNTP server.

Impact on the System

The system cannot synchronize time with the SNTP server.

Handling
1. Check whether the configurations of the SNTP server are correct and whether the
SNTP server works properly.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Reconfigure correct SNTP server information, perform a forced synchronization
operation, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Record the alarm information, and contact ZTE.

3.15 Broadband Link Congestion (8399104)

Alarm Information
l Alarm code: 8399104

3-12

Threshold (8411649)
Alarm Information
l Alarm code: 8411649

3-16

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

l System type: NE alarm

l Alarm level: Major
l Alarm description: The number of the OMP alarms exceeds the threshold.

Cause
Too many NE alarms exist. The number of NE alarms exceeds the threshold of the NE
alarm pool.

Impact on the System

Alarms are lost, and thus the alarm information cannot really reflect the running status of
the equipment. This does not affect user services.

Handling
1. On the Fault Management view of NMS, check whether there are plenty of NE alarms.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Remove all other alarms except for the alarm according to the suggestions on NE
alarm handling, wait about three to five minutes, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

3.20 The Number of Board Logical Alarms Exceeds the

Threshold (8411651)
Alarm Information
l Alarm code: 8411651
l System type: NE alarm
l Alarm level: Major
l Alarm description: The number of board logical alarms exceeds the threshold.

Cause
The board has too many alarm messages. As a result, the alarm pool for storing alarm
messages is full.

Impact on the System

Alarms are lost, and thus the alarm information cannot really reflect the running status of
the equipment. This does not affect user services.

3-17

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Handling
1. On the Fault Management view of NMS check whether there are plenty of alarms
about the board.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Remove all other alarms except for the alarm according to the suggestions on board
alarm handling, wait about three to five minutes, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

3.21 Internal Controlled Account Number and

Password Will Expire Soon (2365980929)
Alarm Information
l Alarm code: 2365980929
l System type: OMM system alarm
l Alarm level: Warning
l Alarm description: The password of the inner account is about to expire.

Cause
The function of password expiry alert is enabled in the inner account password policy,
and the value of Days Before The Password Is Invalid is not 0. The time since the
administrator's last modification of an inner account password reaches the time for
password expiry alert.

Note:

The Password Valid Day of an inner account can be queried with the SHOW ACCOUNT
INFO command in the Terminal or MML Terminal view of NMS.

Impact on the System

This alarm does not affect the normal running of the NMS. It is simply a security alert to
the administrator. You can also disable this policy if the alert is unnecessary.

3-18

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Handling
1. On the Terminal or MML Terminal view of NMS, run the SHOW PASSWDTACTIC
command to check whether Need To Send Alarm When Invalid is set to Yes in the
inner account password policy of the system.
l Yes: Go to Step 2.
l No: Go to Step 9.
2. Confirm whether it is necessary to set a password expiry alert policy. For example,
it is recommended that a password expiry alert policy be set in a public network
environment.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. On the Terminal or MML Terminal view of NMS, run the SET PASSWDTACTIC
command to change the settings of Need To Send Alarm When Invalid to No, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
4. Confirm whether to send the alert only at the time of password expiry.
l Yes: Go to Step 5.
l No: Go to Step 6.
5. On the Terminal or MML Terminal view of NMS, run the SET ACCOUNTPASSWD
command to change the value of Days Before The Password Is Invalid to 0, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 6.
6. Check whether it is the first time to change the inner account password.
l Yes: Go to Step 7.
l No: Go to Step 8.

Caution!
The SET ACCOUNTPASSWD command is dangerous. Do not perform any other
OMM operations while changing the inner account password with this command.

7. On the Terminal or MML Terminal view of NMS, run the SET ACCOUNTPASSWD
command to change the inner account password (the initial password is the account
name), wait about 30 seconds, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 9.
8. On the Terminal or MML Terminal view of NMS, run the SET ACCOUNTPASSWD
command to change the inner account password, wait about 30 seconds, and then
check whether the alarm disappears.
l Yes: End.
l No: Go to Step 9.

3-19

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

9. Contact ZTE.

3.22 Internal Controlled Account Number and

Password Already Expired (2365980930)
Alarm Information
l Alarm code: 2365980930
l System type: OMM system alarm
l Alarm level: Minor
l Alarm description: The password of the inner account has expired.

Cause
The function of password expiry alert is enabled in the inner account password policy, and
the administrator does not change the inner account password within the validity period of
the password.

Impact on the System

This alarm does not affect the normal running of the OMM. It is simply a security alert to
the administrator. You can also disable this policy if the alert is unnecessary.

Handling
1. On the Terminal or MML Terminal view of NMS, run the SHOW PASSWDTACTIC
command to check whether Need To Send Alarm When Invalid is set to Yes in the
inner account password policy of the system.
l Yes: Go to Step 2.
l No: Go to Step 7.
2. Confirm whether it is necessary to set a password expiry alert policy. For example,
it is recommended that a password expiry alert policy be set in a public network
environment.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. On the Terminal or MML Terminal view of NMS, run the SET PASSWDTACTIC
command to change the settings of Need To Send Alarm When Invalid to No, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
4. Check whether it is the first time to change the inner account password.
l Yes: Go to Step 5.
l No: Go to Step 6.
5.

3-20

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Caution!
The SET ACCOUNTPASSWD command is dangerous. Do not perform any other
OMM operations while changing the inner account password with this command.

On the Terminal or MML Terminal view of NMS, run the SET ACCOUNTPASSWD
command to change the inner account password (the initial password is the account
name), wait about 30 seconds, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
6. On the Terminal or MML Terminal view of NMS, run the SET ACCOUNTPASSWD
command to change the inner account password, wait about 30 seconds, and then
check whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

3.23 Internal Controlled Account Number and

Password Do Not Meet Requirements (2365980931)
Alarm Information
l Alarm code: 2365980931
l System type: OMM system alarm
l Alarm level: Warning
l Alarm description: The password of the inner account does not meet the password
policy requirements.

Causes
l The password of an inner account is shorter than the Min Length Of The Password
specified in the inner account password policy.
l The password of an inner account is longer than the Max Length Of The Password
specified in the inner account password policy.
l A password complexity policy is enabled in the inner account password policy, but
the password of an inner account does not meet the requirements of the password
complexity policy.
l The password of an inner account is the same as an old password of Password
Repeat Count set in the inner account password policy.

3-21

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

This alarm does not affect the normal running of the OMM, but is simply an alert reminding
you to modify the inner account password according to relevant requirements.

Handling
1. On the Terminal or MML Terminal view of NMS, run the SHOW PASSWDTACTIC
command to check the settings of Min Length Of The Password, Max Length Of
The Password, Weak Password Check, and Password Repeat Count in the inner
account password policy of the system, and confirm whether the settings meet the
password policy requirements.
l Yes: Go to Step 3.
l No: Go to Step 2.

Caution!
The SET ACCOUNTPASSWD command is dangerous. Do not perform any other
OMM operations while changing the inner account password with this command.

2. On the Terminal or MML Terminal view of NMS, run the SET ACCOUNTPASSWD
command to modify the inner account password (the initial password is the account
name if it is the first time to modify the password), enter an inner account password
meeting the password policy requirements, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

3.24 3 Consecutive Wrong Passwords During Login

(2365980932)
Alarm Information
l Alarm code: 2365980932
l System type: OMM system alarm
l Alarm level: Warning
l Alarm description: The user-input password is wrong for three consecutive times.

Cause
The user-input password is wrong for three consecutive times.

3-22

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Impact on the System

When this alarm occurs for plenty of times at a client, the system is probably suffering
from malicious attacks from illegal users. If the account locking policy is enabled, the user
account will be temporarily or permanently locked after the number of consecutive login
times reaches the value of Max Length Of The Password in account policy setting. Then
the user account needs to be unlocked by the administrator before it can normally log in
again.

Handling
1. Check the user name and login IP address indicated in the alarm information, and then
determine whether any illegal user is waging malicious attacks to the system.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Set a complex password to prevent the account information from being disclosed and
to periodically change the password.
3. Log in using the correct user password.

3.25 License File Illegal (2365981441)

Alarm Information
l Alarm code: 2365981441
l System type: OMM system alarm
l Alarm level: Major
l Alarm description: The License file is illegal.

Cause
This alarm is reported when you restart the NMS or load a License file that is illegal. A
License file is illegal in the following conditions:

l The user information in the License file is inconsistent with the License file name
(excluding the suffix).
l The MAC address in the License file cannot match with any of the MAC addresses of
the network adapters on the current NMS server.
l The text format of the License file is illegal, and the License file is not generated by
the license tool.

Impact on the System

License loading fails, and all NMS functions or service functions under License control may
be unavailable.

Handling
1. Contact ZTE technical support personnel to make a new License file.

3-23

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2. Place the new License file into the $ZXHOME/$NE/server/conf/license

directory, restart the NMS or load the License file, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

3.26 License File Unavailable (2365981443)

Alarm Information
l Alarm code: 2365981443
l System type: OMM system alarm
l Alarm level: Major
l Alarm description: The license file does not exist.

Cause
There is no license file in the $ZXHOME/$NE/server/conf/license directory.

Note:
The license file is suffixed with ".lic" or ".LCS".

Impact on the System

License loading fails, and all NMS functions or service functions under license control may
be unavailable.

Handling
1. Contact ZTE to purchase a license file.
2. Place the new license file into the $ZXHOME/$NE/server/conf/license directory,
restart the NMS or load the license file, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

3.27 Multiple License Files Exist (2365981444)

Alarm Information
l Alarm code: 2365981444
l System type: OMM system alarm

3-24

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

l Alarm level: Major

l Alarm description: Multiple license files exist.

Cause
There are multiple license files in the $ZXHOME/$NE/server/conf/license directory.

Note:
A license file is suffixed with ".lic" or ".LCS".

Impact on the System

License loading fails, and all NMS functions or service functions under license control may
be unavailable.

Handling
1. Delete the excessive license files in the $ZXHOME/$NE/server/conf/license
directory on the NMS server, so that there is only one license file in the directory.
2. Restart the NMS or reload the license file, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

3.28 Loaded License File Expires (2365981445)

Alarm Information
l Alarm code: 2534029312
l System type: NE alarm
l Alarm level: Minor
l Alarm description: DBIO server is overload.

Cause
Uncertain cause.

Impact on the System

The requests for provision with excessive load are rejected.

Handling
No handling is needed.

3-28

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

3.35 DBIO Modified Local Agent Password Fail

(2534029313)
Alarm Information
l Alarm code: 2534029313
l System type: NE alarm
l Alarm level: Minor
l Alarm description: DBIO failed to modify the local agent password.

Cause
DBIO failed to update the configuration memory DB.

Impact on the System

None.

Handling
It can make agent password difference between OMM and DBIO. To solve this problem,
you should send agent configuration data to DBIO from OMM Client.

3.36 User Capacity Beyond License Capacity

(2534029320)
Alarm Information
l Alarm code: 2534029320
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The subscriber capacity exceeds the administration domain
capacity.

Cause
The number of subscribers exceeds the administration domain capacity.

Impact on the System

None.

Handling
Expand capacity to increase the subscriber capacity.

3-29

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

3.37 Auth Capacity Beyond AdminDomani Capacity

(2534029321)
Alarm Information
l Alarm code: 2534029321
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The authentication capacity exceeds the administrative domain
capacity.

Cause
The number of users exceeds the administrative domain capacity.

Impact on the System

Users cannot be added to the administrative domain for authentication. The capacity of
the administrative domain needs to be expanded.

Handling
l Expand the user capacity of the administrative domain.
l Delete certain users from the administrative domain.

3.38 HLR Has Failed Over to Other HLRs, the Links to

Other NEs Are Blocking (2534031360)
Alarm Information
l Alarm code: 2534031360
l System type: NE alarm
l Alarm level: Major
l Alarm description: The ZXUN USPP (HLR) has failed over due to disaster recovery
and its signaling links with other NEs have been blocked.

Causes
l A major fault occurs on the active ZXUN USPP (HLR) in DRSync disaster recovery
mode. The device cannot continue normal operation and has disconnected from the
network automatically. The fault may be caused by the following factors:
à Eighty percent of the service processing modules in the active ZXUN USPP (HLR)
are not powered on or are exceptional. They cannot process most of the signaling
service requests.

3-30

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

à Database operations of eighty percent of the service processing modules in the

active ZXUN USPP (HLR) fail, and the failure count reaches the preset threshold
within the preset time.
à Service message sending of eighty percent of the service processing modules
in the active ZXUN USPP (HLR) fails, and the failure count reaches the preset
threshold within the preset time.
l In DRSync disaster recovery mode, run the FAIL OVER command on the Terminal
or MML Terminal view of NMS to manually instruct the surveillance center to fail over
the active ZXUN USPP (HLR). The active ZXUN USPP (HLR) responds to the manual
failover request of the operator, and the failover operation succeeds.

Impact on the System

A major fault occurs on the active ZXUN USPP (HLR). The device cannot continue normal
operation and has disconnected from the network.
The active ZXUN USPP (HLR) system is switched from normal status to failover status.
The external service signaling links of the device are all disabled to prohibit receipt of all
signaling service requests, and the external transaction interfaces of the device are all
disabled to prohibit all transaction operations. It is necessary to automatically or manually
initiate the takeover of the standby ZXUN USPP (HLR) immediately to ensure normal
service and transaction. If the fault is not handled in time, the system will be interrupted.

Handling
1. Run the SHOW DR STATE command in the Terminal or MML Terminal view of NMS
of the standby ZXUN USPP (HLR), and check whether the standby ZXUN USPP (HLR)
is in Take Overed status.
l Yes: The standby ZXUN USPP (HLR) is in takeover status, and it can process
service requests from signaling links and process transactions. ZXUN USPP
(HLR) runs in standby mode without impacting services.
l No: Go to Step 2.

Caution!

The next step is risky. Contact ZTE technical support personnel for confirmation
before operation.

2. On the Terminal or MML Terminal view of NMS of the standby ZXUN USPP (HLR)
(if there are multiple standby ZXUN USPP (HLR)s, select the one with the same
number as that queried with the SHOW DR STATE command on the OMM of the
active ZXUN USPP (HLR)), run the TAKE OVER command to initiate the takeover of
the standby ZXUN USPP (HLR) immediately, and set the ZXUN USPP (HLR) to the
standby working mode.

3-31

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

3. The standby working mode is a temporary running status of the ZXUN USPP (HLR).
It is necessary to check the fault of the active ZXUN USPP (HLR) immediately and
contact ZTE technical support personnel to assist in fault troubleshooting of the active
ZXUN USPP (HLR).

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

4. After the fault is cleared from the active ZXUN USPP (HLR), run the RECLAIM
command on the Terminal or MML Terminal view of NMS of the active ZXUN USPP
(HLR) to conduct manual reclamation. Check whether the reclamation operation
succeeds.
l Yes: Go to Step 5.
l No: The external signaling link fault is not cleared completely. It is necessary to
clear the fault completely before performing reclamation operation.
5. On the Terminal or MML Terminal view of NMS of the active ZXUN USPP (HLR), run
the SHOW DR STATE command to check whether the active ZXUN USPP (HLR) is
in Not Fail Overed status. Make sure the device runs in active mode.

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

6. On the Terminal or MML Terminal view of NMS of the standby ZXUN USPP (HLR) (if
there are multiple standby ZXUN USPP (HLR)s, select the one with the same number
as that queried with the SHOW DR STATE command on the OMM of the active ZXUN
USPP (HLR)), run the GIVE BACK command to manually give back the standby ZXUN
USPP (HLR) and stop the standby ZXUN USPP (HLR).

3.39 HLR Can Provide Service for Other NEs, the Links
to Other NEs Are Unblocked. The BOSS Request
Has Been Permitted (2534031361)
Alarm Information
l Alarm code: 2534031361
l System type: NE alarm

3-32

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

l Alarm level: Major

l Alarm description: The ZXUN USPP (HLR) is reclaimed due to disaster recovery and
its signaling links with other NEs have been unblocked. BOSS transaction is recov-
ered.

Cause
In DRSync disaster recovery mode, run the RECLAIM command on the Terminal or MML
Terminal view of NMS to manually instruct the surveillance center to reclaim the active
ZXUN USPP (HLR). The active ZXUN USPP (HLR) responds to the manual reclamation
request of the operator and the reclamation operation succeeds.

Impact on the System

The active ZXUN USPP (HLR) is disconnected from the network for some time due to a
major fault on it.
The active ZXUN USPP (HLR) is switched from the takeover status back to the normal
status. Its external service links have all been unblocked to receive all signaling service
requests, and its external transaction interfaces have all been enabled to allow all
transaction operations. Functions of the active ZXUN USPP (HLR) are all recovered and
the system runs normally.

Handling
1. On the Terminal or MML Terminal view of NMS of the standby ZXUN USPP (HLR),
run the SHOW DR STATE command to check whether the standby ZXUN USPP (HLR)
is in Not Take Overed status.
l Yes: The standby ZXUN USPP (HLR) is disabled, and the ZXUN USPP (HLR)
device runs in active mode.
l No: Go to Step 2.

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation
before operation.

2. If the standby ZXUN USPP (HLR) is in Take Overed status, it indicates the active
and standby ZXUN USPP (HLR)s are running. It is necessary to run the GIVE BACK
command on the Terminal or MML Terminal view of NMS of the standby ZXUN USPP
(HLR) (if there are multiple standby ZXUN USPP (HLR)s, select the one with the same
number as that queried with the SHOW DR STATE command on the OMM of the active
ZXUN USPP (HLR)) to give back the standby ZXUN USPP (HLR) back and stop the
standby ZXUN USPP (HLR).
3. Check whether there is any other exception on the active ZXUN USPP (HLR) and
whether all the faults are cleared. If there is an abnormal alarm, contact ZTE.

3-33

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

3.40 HLR Has Provided Services for Standby

Subscriber from Now (2534031362)
Alarm Information
l Alarm code: 2534031362
l System type: NE alarm
l Alarm level: Major
l Alarm description: The ZXUN USPP (HLR) has taken over due to disaster recovery
and starts to provide services to some standby subscribers.

Causes
l In DRSync disaster recovery mode, run the TAKE OVER command in the Terminal
or MML Terminal view of NMS to manually instruct the surveillance center to initiate
the takeover of the standby ZXUN USPP (HLR). The standby ZXUN USPP (HLR)
responds to the manual takeover request of the operator and the takeover operation
succeeds.
l In DRSync disaster recovery mode, the external signaling link of the active ZXUN
USPP (HLR) is faulty, and service request messages cannot be sent to the signaling
service processing board of the active ZXUN USPP (HLR). The external NE enables
the standby route mode to send service request messages to the standby ZXUN
USPP (HLR). The standby ZXUN USPP (HLR) not yet taken over detects that the
service message flow reaches the preset threshold within the preset time, and
then automatically triggers takeover to ensure the success of the signaling service
requests.

Impact on the System

Since the active ZXUN USPP (HLR) is disconnected from the external signaling link, a
service request is sent to the standby ZXUN USPP (HLR) to request the standby ZXUN
USPP (HLR) to process the service. The standby ZXUN USPP (HLR) system is switched
from non-takeover status to takeover status. The external signaling request processing
capability of the device is activated, and the external transaction interface of the device is
enabled to allow all transaction operations. It is necessary to automatically or manually
initiate the failover of the active ZXUN USPP (HLR) immediately to ensure that the ZXUN
USPP (HLR) device runs in the standby mode.

Handling
1. On the Terminal or MML Terminal view of NMS of the active ZXUN USPP (HLR), run
the SHOW DR STATE command to check whether the active ZXUN USPP (HLR) is
in Fail Overed status.
l Yes: The active ZXUN USPP (HLR) is in Fail Overed status, all the external
signaling links are disconnected, all signaling service requests are forwarded
to the standby office for processing, transaction operations are disabled, and

3-34

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

transaction requests are forwarded to the standby office for processing. The
ZXUN USPP (HLR) runs in standby mode without impacting services.
l No: Go to Step 2.

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

2. On the Terminal or MML Terminal view of NMS of the active ZXUN USPP (HLR),
run the FAIL OVER command to manually fail over the active ZXUN USPP (HLR)
immediately, and set the ZXUN USPP (HLR) to standby mode.
3. The standby mode is a temporary running status of the ZXUN USPP (HLR). It is
necessary to check the fault of the active ZXUN USPP (HLR) immediately and contact
ZTE technical support personnel to assist in fault troubleshooting of the active ZXUN
USPP (HLR).

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

6. On the Terminal or MML Terminal view of NMS of the standby ZXUN USPP (HLR) (if
there are multiple standby ZXUN USPP (HLR)s, select the one with the same number

3-35

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

as that queried with the SHOW DR STATE command on the OMM of the active ZXUN
USPP (HLR)), run the GIVE BACK command to manually give back the standby ZXUN
USPP (HLR) and stop the standby ZXUN USPP (HLR).

3.41 HLR Stops to Provide Service for Standby

Subscriber from Now (2534031363)
Alarm Information
l Alarm code: 2534031363
l System type: NE alarm
l Alarm level: Major
l Alarm description: HLR is switched back due to disaster recovery and no longer
provides access service to related subscribers for the other NEs.

Cause
In DRSync disaster recovery mode, run the GIVE BACK command in the Terminal or
MML Terminal view of NMS to manually instruct the surveillance center to switch back
the standby ZXUN USPP (HLR). The active ZXUN USPP (HLR) responds to the manual
giveback request of the operator and the switchback operation succeeds.

Impact on the System

The ZXUN USPP (HLR) once runs in standby mode, and the standby ZXUN USPP (HLR)
takes over the work of the active ZXUN USPP (HLR) that is seriously faulty. Currently, the
standby ZXUN USPP (HLR) system is switched from takeover status back to non-takeover
status. The device can no longer receive any external signaling service requests, and
the external transaction interfaces of the device are all disabled to prohibit all transaction
operations. Functions of the standby ZXUN USPP (HLR) are all disabled so that the
system can restore the active working mode.

Handling
1. On the Terminal or MML Terminal view of NMS of the active ZXUN USPP (HLR), run
the SHOW DR STATE command to check whether the active ZXUN USPP (HLR) is
in Not Fail Overed status.
l Yes: The active ZXUN USPP (HLR) is normal and can process service signaling
requests and transaction data. The ZXUN USPP (HLR) device is running in active
mode, and everything is normal.
l No: Go to Step 2.
2. Check whether the active ZXUN USPP (HLR) is abnormal and whether all the faults
are cleared. If there is an abnormal alarm, contact ZTE technical support personnel
immediately for help.

3-36

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

3. After the fault is cleared from the active ZXUN USPP (HLR), run the RECLAIM
command on the Terminal or MML Terminal view of NMS of the active ZXUN
USPP (HLR) to manually reclaim the active ZXUN USPP (HLR). Check whether the
reclamation operation succeeds.
l Yes: End.
l No: Go to Step 3.
4. If the active ZXUN USPP (HLR) is still in Fail Overed status, initiate the takeover of
the standby ZXUN USPP (HLR), and restore the ZXUN USPP (HLR) to the standby
working mode to ensure normal service and transaction.
5. The standby working mode is a temporary running status of the ZXUN USPP (HLR).
Contact ZTE immediately.

3.42 Serious Error Found, HLR Try to Block All Link to

Other NEs, the Operation Has Failed (2534031364)
Alarm Information
l Alarm code: 2534031364
l System type: NE alarm
l Alarm level: Major
l Alarm description: A major fault occurs on the ZXUN USPP (HLR). The ZXUN USPP
(HLR) has attempted to block the signaling link in order to switch the service over to
the disaster recovery ZXUN USPP (HLR). However, the blocking operation fails.

Cause
A major fault occurs on the active ZXUN USPP (HLR) in DRSync disaster recovery mode.
The device cannot continue normal operation. It attempts to automatically disconnect from
the network, but it fails to disconnect and is still running. The major fault may be caused
by the following:
l Eighty percent of the service processing modules in the active ZXUN USPP (HLR)
are not powered on or are exceptional. They cannot process most of the signaling
service requests.
l Database operations of eighty percent of the service processing modules in the active
ZXUN USPP (HLR) fail, and the failure count reaches the preset threshold within the
preset time.

3-37

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Service message sending of eighty percent of the service processing modules in the
active ZXUN USPP (HLR) fails, and the failure count reaches the preset threshold
within the preset time.

Impact on the System

The device cannot continue normal operation due to a major fault on the active ZXUN
USPP (HLR). The active ZXUN USPP (HLR) attempts to disconnect from the network.
But it is still in the working status due to external signaling link block failure.
The external service signaling link of the device is faulty. The device prohibits receipt
of some signaling service requests. The external transaction interface of the device is
enabled and allows all transaction operations. It is necessary to troubleshoot the signaling
link fault immediately, and manually initiate the failover of the active ZXUN USPP (HLR)
and the takeover of the standby ZXUN USPP (HLR) to ensure normal service and
transaction. If the fault is not handled in time, the system will be interrupted.

Handling

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

1. To ensure normal service and transaction, it is necessary to set the ZXUN USPP (HLR)
to standby mode.
a. On the Terminal or MML Terminal view of NMS of the active ZXUN USPP (HLR),
run the FAIL OVER command to manually switch the active ZXUN USPP (HLR)
to the failover status.
b. On the Terminal or MML Terminal view of NMS of the standby ZXUN USPP (HLR)
(if there are multiple standby ZXUN USPP (HLR)s, select the one with the same
number as that queried with the SHOW DR STATE command on the OMM of the
active ZXUN USPP (HLR)), run the TAKE OVER command to manually switch
the standby ZXUN USPP (HLR) to the takeover status.

2. The standby working mode is a temporary running status of ZXUN USPP (HLR). It is
necessary to check the fault of the active ZXUN USPP (HLR) immediately and contact
ZTE technical support personnel to assist in major fault troubleshooting of the active
ZXUN USPP (HLR).

3-38

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

3. After all major faults are cleared from the active ZXUN USPP (HLR), run the
RECLAIM command on the Terminal or MML Terminal view of NMS of the active
ZXUN USPP (HLR) to conduct manual reclamation. Check whether the reclamation
operation succeeds.
l Yes: Go to Step 4.
l No: The external signaling link fault is not cleared completely. It is necessary to
clear the fault completely before performing reclamation operation.
4. Run the SHOW DR STATE command on the Terminal or MML Terminal view of NMS
of the active ZXUN USPP (HLR) to check whether the active ZXUN USPP (HLR) is in
Not Fail Overed status.

Caution!
The next step is risky. Contact ZTE technical support personnel for confirmation before
operation.

5. Run the GIVE BACK command on the Terminal or MML Terminal view of NMS of the
standby ZXUN USPP (HLR) (if there are multiple standby ZXUN USPP (HLR)s, select
the one with the same number as that queried with the SHOW DR STATE command
on the OMM of the active ZXUN USPP (HLR)) to manually give back the standby
ZXUN USPP (HLR).

3.43 UDS Node Has Received too Many Messages

Within a Time (2534033667)
Alarm Information
l Alarm code: 2534033667
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The UDS receives excessive service messages.

Cause
The DSA node has received too many LDAP or DSP request messages within a unit of
time.

3-39

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

The DSA node may discard some service requests, which results in the failure of some
services.

Handling
1. Log in to the EMS client and open the MML Terminal view. Execute the SHOW DSA
NODEOPT command under the Global Equipment Configuration to check whether
the value of The Max Number of Received Message Per Second (that is, MAXMSG)
is much less than the recommended value 2000.
l Yes: Set The Max Number of Received Message Per Second to the
recommended value and transfer the changed table to validate the setting. Then
check whether the alarm disappears.
à Yes: End.
à No: Go to Step 2.

l No: Go to Step 2.
2. Log in to the EMS client and open the MML Terminal view. Execute the SHOW DS
ANODE STATUS command to check whether other DSA nodes in the DSA cluster of
the DSA node with alarms are off-line or faulty.
l Yes: Change the status of the other DSAs to online status or eliminate the faults
on the other DSAs so that the other DSAs can share the service load.
l No: Go to Step 3.
3. Check whether the TCP connections between the DSA with the alarm and the other
nodes in the cluster are normal.
l Yes: Contact ZTE.
l No: After eliminating the link faults, check whether the alarm disappears.

à Yes: End.
à No: Contact ZTE.

3.44 The User Capacity of Each DSA Node in DSA

Group Has Been Full (2534033668)
Alarm Information
l Alarm code: 2534033668
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The user list of each DSA node in DSA group has been full.

Cause
The number of the user lists of all DSAs in the DSA group will reach the upper limit.

3-40

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Impact on the System

None.

Handling
Expand the capacity of the user list and restart DSA.

3.45 Capacity of User Table Is Full (2534033920)

Alarm Information
l Alarm code: 2534033920
l System type: NE alarm
l Alarm level: Major
l Alarm description: The subscriber table is full.

Cause
The current capacity of the subscriber table reaches the upper limit of the configured
capacity.

Impact on the System

The system is unable to add subscribers.

Handling
1. On the Performance Management view of the NMS, create a measurement job
to query the total current subscriber capacity in the system. On the License
Management view of the NMS, query the upper limit of the subscriber capacity
specified by the License, and check whether the value of the current subscriber
capacity is close or equals to the upper limit of the subscriber capacity specified by
the License.
l Yes: Contact ZTE to expand the capacity.
l No: Go to Step 2.
2. On the Performance Management view of NMS, create a measurement job to query
the current subscriber capacity of each administration domain. On the MML Terminal
or Terminal view of the NMS, check the setting of the subscriber capacity by running
the SHOW VHLRCAP command to see if the set value is close or equals to the current
subscriber capacity of the administration domain.
l Yes: Modify the setting of the administration domain capacity and then
synchronize the data. After that, check whether the alarm disappears.
à Yes: End.

à No: Go to Step 3.
l No: Go to Step 3.

3-41

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

3. Check the capacity of each DSA cluster involved in each DSA group to see if it reaches
the upper limit of the configured capacity.
l Yes: Contact ZTE to combine DSA groups or add more DSAs.
l No: Go to Step 4.
4. Check whether the configuration of the subscriber table capacity proportion is rational.
If it is not proper, the table could be full.
l Yes: Modify the configuration and then synchronize the data. Then check whether
the alarm disappears.
l No: Contact ZTE.

3.46 Capacity of HLR User DB Is Full (2534033922)

Alarm Information
l Alarm code: 2534033922
l System type: NE alarm
l Alarm level: Major
l Alarm description: Capacity of HLR user DB is Full.

Cause
The user database is full.

Impact on the System

All the table operations fail.

Handling
Expand the database capacity.

3.47 Percentage of Free Space on Logical Structures

Beneath (2534033923)
Alarm Information
l Alarm code: 2534033923
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The percentage of free data space on the node is too low.

Cause
The user table capacity is to reach the configured upper limit.

3-42

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

Impact on the System

Data insertion may fail.

Handling
Expand the user table capacity, and then restart the DSA.

3.48 Disk Full (2534034176)

Alarm Information
l Alarm code: 2534034176
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The disk is full.

Cause
Insufficient disk space.

Impact on the System

l Creating of the log files failed.
l Creating of the data files failed.
l Expansion of the data files failed.
l Backup of files failed.

Handling
1. Check the backup data directory of the DST to see if the backup data are not deleted
in time so that the disk space is insufficient.
l Yes: Manually delete the backup data that were generated a long time ago and
re-create the scheduled data backup task to shorten the backup data reservation
duration.
l No: Go to Step 2.
2. Check whether the disk has faulty tracks.
l Yes: Change the hard disk.
l No: Contact ZTE.

3.49 Problem With Operations Read/Write on the

Physical Structures of the Database (2534034177)
Alarm Information
l Alarm code: 2534034177
l System type: NE alarm

3-43

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Alarm level: Critical

l Alarm description: The reading/writing on the physical storage is abnormal.

Causes
l The physical storage is faulty, for example, the disk is damaged or the hardware ages.
l The operating system is faulty, and thus files cannot be read or written.

Impact on the System

When the local file storage switches from the durable status to the faulty status, the DSA
node cannot read or write local files. Consequently, the data of the services newly handled
cannot be backed up. In addition, data may be lost if the node is faulty.

Handling
1. Run the fsck command to check whether the disk is faulty. Contact ZTE technical
support personnel to replace the disk if the disk is faulty.
2. It is maybe the operating system is faulty, contact ZTE.

3.50 Resume Failed Because The Capacity of Backup

Node Is Undersize (2534034432)
Alarm Information
l Alarm code: 2534034432
l System type: NE Alarm
l Alarm level: Critical
l Alarm description: The online recovery fails because the capacity of the standby node
is too low.

Cause
The online recovery standby node has too less a table capacity.

Impact on the System

The online recovery function of the system may be affected, thus the data on the standby
node and the data on the active node are different.

Handling
1. Modify the configuration of the table capacity. Then synchronize the data and check
whether the alarm disappears.
l Yes: End.
l No: Go to Step 2.
2. Contact ZTE.

3-44

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 3 Processing Error Alarms

3.51 UDS Synch Power On Fail (2534034433)

Alarm Information
l Alarm code: 2534034433
l System type: NE Alarm
l Alarm level: Critical
l Alarm description: The asynchronous duplication failed due to the too less table
capacity of the standby node.

Cause
The asynchronous duplication standby node has too less a table capacity.

Impact on the System

The asynchronous duplication function of the system is affected and the duplication may
fail.

Handling
1. Modify the configuration of the table capacity and synchronize the data. Check
whether the alarm disappears.
l Yes: End.
l No: Go to Step 2.
2. Contact ZTE.

3.52 Resume Failed Because The Capacity of Slave

Node Is Less Than The High Water in The Master
Node (2534034434)
Alarm Information
l Alarm code: 2534034434
l System type: NE Alarm
l Alarm level: Critical
l Alarm description: The online recovery fails because the capacity of the standby node
is lower than the higher level of the active node.

Cause
The online recovery standby node has too less a table capacity.

3-45

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

The online recovery function of the system may be affected, thus the data on the standby
node and the data on the active node are different.

Handling
1. Modify the configuration of the table capacity to be higher than the higher level of
the active node at least. Then synchronize the data and check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 2.
2. Contact ZTE.

3.53 Schema Control Module Failed to Check Configure

Data Compatibility (2534034689)
Alarm Information
l Alarm code: 2534034689
l System type: NE alarm
l Alarm level: Critical
l Alarm description: The schema control module finds that the configuration data before
and after data synchronization are incompatible.

Cause
Key configuration data are changed, which changes the node role and the service types
and capabilities provided by the node. Configuration data that may have been modified
are as follows:
l DSA node ID. For example, the original node ID is 111 and then it is changed to 121.
The node reports this alarm when the changed configuration data are sent to the node.
l DSA node type. For example, the original node type is DSA and then it is changed to
SAVE. The node reports this alarm when the changed configuration data are sent to
the node.
l Home DSA cluster of the DSA node. For example, the original cluster to which the
node belongs is cluster 1 and then it is changed to cluster 2. The node reports this
alarm when the changed configuration data are sent to the node.
l Storage node associated with the DSA node. For example, the original associated
storage node is 180 and then it is changed to 181. The node reports this alarm when
the changed configuration data are sent to the node.
l Home DSA type of the DSA node. For example, the original home DSA type is IDSA
and then it is changed to PDSA. The node reports this alarm when the changed
configuration data are sent to the node.

3-46

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Impact on the System

The fault has no impact on the system in a short term.

Handling
1. Wait until the alarm disappears automatically. If it has not disappeared for a long time,
go to Step 2.
2. On the Fault Management view of the NMS, perform alarm synchronization and clear
the alarm manually. Then check whether the system still reports this alarm.
l Yes: Contact ZTE to expand the capacity.
l No: End.

3-50

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 4
QoS Alarms
Table of Contents
Association Congested (8402688)..............................................................................4-1
STC Office Congested (8402945)...............................................................................4-2
Performance Qos Critical Alarm (2365980673)...........................................................4-3
Performance Qos Major Alarm (2365980674) ............................................................4-4
Performance Qos Common Alarm (2365980675) .......................................................4-6
Performance Qos Warning Alarm (2365980676) ........................................................4-7
ITU TCAP Service Overload (2534025218) ................................................................4-8
SMP Report SHLR NNI Interface Level 1 Overload Alarm (2539268097) ...................4-9
SMP Report SHLR NNI Interface Level 2 Overload Alarm (2538219521) ...................4-9
SMP Report SHLR NNI Interface Level 3 Overload Alarm (2537170945) .................4-10
SMP Report SHLR NNI Interface Level 4 Overload Alarm (2536122369) .................4-10
SMP Report SHLR NNI Interface Level 5 Overload Alarm (2535073793) .................4-11
SMP Report MAP Interface Level 1 Overload Alarm (2539268096) ..........................4-11
SMP Report MAP Interface Level 2 Overload Alarm (2538219520) ..........................4-12
SMP Report MAP Interface Level 3 Overload Alarm (2537170944) ..........................4-12
SMP Report MAP Interface Level 4 Overload Alarm (2536122368) ..........................4-13
SMP Report MAP Interface Level 5 Overload Alarm (2535073792) ..........................4-13

4.1 Association Congested (8402688)

Alarm Information
l Alarm code: 8402688
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The association is congested.

Causes
l Bottom-layer link has bad transmission quality, which leads to association congestion.
l Heavy traffic.
l Uneven load among associations.
l Insufficient association resources.

4-1

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

Congestion will lead to transmission delay, even packet loss when the congestion is
serious. Generally services will not be affected. If the congestion becomes serious, call
loss will occur or the PS service access success rate will decrease.

Handling
1. Make no manual intervention and just wait until the system recovers. Check whether
the alarm disappears after 30 seconds.
l Yes: End.
l No: Go to Step 2.
2. Check whether network cable is well connected. Ensure the network cable is securely
inserted and observe whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check whether the system has a heavy traffic.
l Yes: Go to Step 4.
l No: Go to Step 7.
4. Check whether there are sufficient association resources.
l Yes: Go to Step 5.
l No: Go to Step 6.
5. Check whether load are evenly shared among associations.
l Yes: Go to Step 1.
l No: Go to Step 7.
6. Add new associations and check whether this alarm disappears.
l Yes: End.
l No: Go to Step 5.
7. Record the following information and contact ZTE.
l Configuration data of the local office and peer-end office.
l History alarms, history notifications, and current alarms of the local office and
peer-end office.

4.2 STC Office Congested (8402945)

Alarm Information
l Alarm code: 8402945
l System type: NE alarm
l Alarm level: Minor
l Alarm description: STC office is congested.

Cause
At least one association of the office is in congestion status.

4-2

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 4 QoS Alarms

Impact on the System

Congestion will lead to transmission delay and generally does not affect services.
Heavy congestion may result in message loss, call loss or even association interruption.

à Yes: End.
à No: Go to Step 5.
4. Check whether there is association congestion.
l Yes: Troubleshoot association congestion by following the 4.1 Association
Congested (8402688) alarm handling suggestions.
l No: Go to Step 5.
5. Back up the following data and contact ZTE.
l Configuration data related to local office and peer-end office.
l History alarms, current alarms, and notifications that are related to the local office
and peer-end office.

4.3 Performance Qos Critical Alarm (2365980673)

Alarm Information
l Alarm code: 2365980673
l System type: OMM system alarm
l Alarm level: Critical
l Alarm description: Level-1 performance QoS alarm

Cause
An object for QoS alarm monitoring is uniquely determined by the threshold ID of the
measurement task and the measurement object ID associated with the threshold. For
a specific monitored object, if the counter value or index value detected at the data report
time point exceeds the set monitoring threshold of the critical level, a level-1 performance
QoS alarm is triggered.

4-3

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Note:
l Task threshold
Task thresholds are a set of performance QoS thresholds set for a specific
measurement task, including the thresholds of four levels: critical, major, minor, and
warning. They must be associated with a certain counter or counter-based indexes.
l Measurement object ID
If the measurement task involves measurement objects, the task thresholds must be
associated with one or multiple of the measurement objects. Otherwise, the task
thresholds need not be associated with any measurement object.
l Data report time point
When the time granularity of a measurement task is up, the service node in the
foreground reports statistical data.

Impact on the System

This alarm may affect service QoS, depending on threshold definitions and the severity of
the alarm.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW PMMONITOR
command with the additional alarm information to check whether the corresponding
performance threshold is properly set.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. On the MML Terminal or Terminal view of the NMS, run the SET PMMONITOR
command to modify the threshold value (do not modify it unless really necessary),
and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
3. Check the service running status based on the specific counter or index type, remove
the service fault, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Contact ZTE.

4.4 Performance Qos Major Alarm (2365980674)

Alarm Information
l Alarm code: 2365980674

4-4

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 4 QoS Alarms

l System type: OMM system alarm

l Alarm level: Major
l Alarm description: Level-2 performance QoS alarm

Cause
An object for QoS alarm monitoring is uniquely determined by the threshold ID of the
measurement task and the measurement object ID associated with the threshold. For
a specific monitored object, if the counter value or index value detected at the data report
time point exceeds the set monitoring threshold of the major level, a level-2 performance
QoS alarm is triggered.

Impact on the System

This alarm may affect service QoS, depending on threshold definitions and the severity of
the alarm.

4-5

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

3. Check the service running status based on the specific counter or index type, remove
the service fault, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Contact ZTE.

4.5 Performance Qos Common Alarm (2365980675)

Alarm Information
l Alarm code: 2365980675
l System type: OMM system alarm
l Alarm level: Minor
l Alarm description: Level-3 performance QoS alarm

Cause
An object for QoS alarm monitoring is uniquely determined by the threshold ID of the
measurement task and the measurement object ID associated with the threshold. For
a specific monitored object, if the counter value or index value detected at the data report
time point exceeds the set monitoring threshold of the minor level, a level-3 performance
QoS alarm is triggered.

l Data report time point

When the time granularity of a measurement task is up, the service node in the
foreground reports statistical data.

Impact on the System

This alarm may affect service QoS, depending on threshold definitions and the severity of
the alarm.

4-6

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 4 QoS Alarms

4.6 Performance Qos Warning Alarm (2365980676)

Alarm Information
l Alarm code: 2365980676
l System type: OMM system alarm
l Alarm level: Warning
l Alarm description: Level-4 performance QoS alarm

Cause
An object for QoS alarm monitoring is uniquely determined by the threshold ID of the
measurement task and the measurement object ID associated with the threshold. For
a specific monitored object, if the counter value or index value detected at the data report
time point exceeds the set monitoring threshold of the warning level, a level-4 performance
QoS alarm is triggered.

4-7

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

This alarm may affect service QoS, depending on threshold definitions and the severity of
the alarm.

4.7 ITU TCAP Service Overload (2534025218)

Alarm Information
l Alarm code: 2534025218

4-8

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 4 QoS Alarms

l System type: NE alarm

l Alarm level: Minor
l Alarm description: ITU TCAP service overload.

Cause
The alarm is reported when the traffic gets overloaded, and is cleared up when the traffic
load gets normal.

Impact on the System

May cause intelligent service failure.

Handling
Reduce the traffic.

4.8 SMP Report SHLR NNI Interface Level 1 Overload

Alarm (2539268097)
Alarm Information
l Alarm code: 2539268097
l System type: NE alarm
l Alarm level: Minor
l Alarm description: SMP report SHLR NNI interface level 1 overload alarm.

Cause
The alarm is reported when the traffic gets overloaded, and is cleared up when the traffic
load gets normal.

Impact on the System

May cause service failure.

Handling
Reduce the traffic.

4.9 SMP Report SHLR NNI Interface Level 2 Overload

Alarm (2538219521)
Alarm Information
l Alarm code: 2538219521
l System type: NE alarm

4-9

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Alarm level: Minor

l Alarm description: SMP report SHLR NNI interface level 2 overload alarm.

Cause
The alarm is reported when the traffic gets overloaded, and is cleared up when the traffic
load gets normal.

Impact on the System

May cause service failure.

Handling
Reduce the traffic.

4.10 SMP Report SHLR NNI Interface Level 3 Overload

Alarm (2537170945)
Alarm Information
l Alarm code: 2537170945
l System type: NE alarm
l Alarm level: Warning
l Alarm description: SMP report SHLR NNI interface level 3 overload alarm.

Cause
The alarm is reported when the traffic gets overloaded, and is cleared up when the traffic
load gets normal.

Impact on the System

May cause service failure.

Handling
Reduce the traffic.

4.11 SMP Report SHLR NNI Interface Level 4 Overload

Alarm (2536122369)
Alarm Information
l Alarm code: 2536122369
l System type: NE alarm
l Alarm level: Warning

4-10

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Cause
The alarm is reported when the traffic gets overloaded, and is cleared up when the traffic
load gets normal.

Impact on the System

May cause service failure.

Handling
Reduce the traffic.

4-14

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5
Equipment Alarms
Table of Contents
OMC Port Link Is Down (256).....................................................................................5-3
Trunk Frame Loss (512) .............................................................................................5-3
Trunk Signal Loss (513) .............................................................................................5-4
Trunk Alarm Indication (514) ......................................................................................5-5
Trunk Multi-frame Loss (515)......................................................................................5-5
Far End Alarm (517)...................................................................................................5-6
Trunk Link Is Used for CSU Loopback Test (518) .......................................................5-6
Cell Delineation do not Synchronization About Cell on E1/T1 Link (1026)...................5-7
Clock Board Is in Preheat Status (1285).....................................................................5-8
Loss of Clock When Input to Board (1286) .................................................................5-8
CPU Resets on a Board in the Same Shelf (1600) .....................................................5-9
FLASH Device Initialize Failed (3073) ......................................................................5-10
The Configuration Does Not Supported (5123) .........................................................5-10
Board Config Information not Compatible (5200) ......................................................5-11
Packet Test of Internal Media Plane Is Abnormal (5396)...........................................5-12
Clock Board Work Mode Is Abnormal (5405) ............................................................5-13
The Hard Disk Used-Rate Is over Threshold (5632) .................................................5-13
The Hard Disk Becomes Error or not Exist (5633) ....................................................5-14
Sub Card Abnormal (5645).......................................................................................5-14
Phase-Lock Loop Unlock (5646)...............................................................................5-15
Error Packets of MAC Is Higher than the Specified Threshold (5666) .......................5-16
Oscillator Status Abnormal (5670) ............................................................................5-17
MAC Port Link Is Down (5760) .................................................................................5-17
The Speed Mode of the Port Doesn't Match with Settings (5761) .............................5-18
One Frequency of Clock Is All Lost when Input to Board (5768) ...............................5-19
The Master and Slave Mode of the Port Doesn't Match with Settings (5769) ............5-20
The OMP Board Doesn't Have OMC Port (5770)......................................................5-20
The Duplex Mode of the Port Doesn't Match with Settings (5771).............................5-21
Board Device Fault (5772)........................................................................................5-22
High CRC Error Rate at E1 Bottom Layer (5773)......................................................5-22
High FAS Error Rate at E1 Bottom Layer (5774).......................................................5-23
High EBIT Error Rate at E1 Bottom Layer (5775) .....................................................5-23
Subcard is Formatting Flash (5786)..........................................................................5-24
Subcard Works in Genernal Error (5787)..................................................................5-24
Subcard Works in Critical Error (5788) .....................................................................5-25
Subcard Works in Fatal Error (5789) ........................................................................5-26
Functional Epld Update Fail (5890) ..........................................................................5-26

5-1

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Inner Port Error (7169) .............................................................................................5-27

Media Status Abnormal (15360) ...............................................................................5-27
Too Many Bad Frames Received (15618).................................................................5-28
The Fan Tray Is Off (23050) .....................................................................................5-29
The PEM Is Off (23051)............................................................................................5-29
Abnormal Half-Fixed Connection Changes (25602) ..................................................5-30
RACK Temperature Is Higher than High Threshold (25856)......................................5-30
RACK Temperature Is Lower than Low Threshold (25857) .......................................5-31
Room Temperature Is Higher than High Threshold (25858) ......................................5-32
Room Temperature Is Lower than Low Threshold (25859)........................................5-33
Voltage Is Higher than High Threshold (25860) ........................................................5-34
Voltage Is Lower than Low Threshold (25861) ..........................................................5-35
Humidity Is Higher than High Threshold (25862) ......................................................5-36
Humidity Is Lower than Low Threshold (25863) ........................................................5-36
Fault in Fan Plug-In Box (25864) ..............................................................................5-37
Rack Door Access Control Alarm (25865) ................................................................5-38
Smoke Alarm (25866) ..............................................................................................5-39
Infrared Alarm (25867) .............................................................................................5-40
Lightning Alarm (25868) ...........................................................................................5-41
Power Switch Alarm (25869) ....................................................................................5-41
Power Type Configured Does Not Accord with Physical (25870) ..............................5-43
Clock Reference Source Lost (Level 3 Alarm) (26127) .............................................5-43
Clock Reference Source Lost (Level 2 Alarm) (26128) .............................................5-44
Clock Reference Source Lost (Level 1 Alarm) (26129) .............................................5-45
Output Clock Lost (26133)........................................................................................5-45
Velocity of fan is Lower Than Lower-critical Threshold (30734).................................5-46
Velocity of fan is Lower Than Lower-non-critical Threshold (30745)..........................5-46
Velocity of fan is Lower Than Lower-non-recoverable Threshold (30746) .................5-47
IPMB State Change (IPMB-A Enable \ IPMB-B Disable) (30812)..............................5-48
IPMB State Change (IPMB-A Disable\IPMB-B Enable) (30813)................................5-48
STC Office Inaccessible (8402944) ..........................................................................5-49
NM Server CPU Usage Rate Exceeds Criterion (2365981185) .................................5-49
NM Server Memory Usage Rate Exceeds Criterion (2365981186)............................5-51
NM Server Hard Disk Usage Rate Exceeds Criterion(Level 1 Alarm) (2365981187) .5-52
NM Server Hard Disk Usage Rate Exceeds Criterion(Level 2 Alarm) (2365981188) .5-53
NM Server Hard Disk Usage Rate Exceeds Criterion(Level 3 Alarm) (2365981189) .5-55
NM Server Hard Disk Usage Rate Exceeds Criterion(Level 4 Alarm) (2365981190) .5-57
Directory Usage Rate Exceeds Criterion (Level 1 Alarm) (2365981191) ...................5-58
Directory Usage Rate Exceeds Criterion (Level 2 Alarm) (2365981192) ...................5-60
Directory Usage Rate Exceeds Criterion (Level 3 Alarm) (2365981193) ...................5-62
Directory Usage Rate Exceeds Criterion (Level 4 Alarm) (2365981194) ...................5-64
Link Between DBIO and HSMAPP Node Broken (2534029328) ...............................5-66
HSMAPP Node Status Error (2535069704) ..............................................................5-66

5-2

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

5.1 OMC Port Link Is Down (256)

Alarm Information
l Alarm code: 256
l System type: NE alarm
l Alarm level: Warning
l Alarm description: The OMC link is down.

Cause
The NMS link is broken.

Impact on the System

The NMS link is broken.

Handling
Check whether the link is connected.

5.2 Trunk Frame Loss (512)

Alarm Information
l Alarm code: 512
l System type: NE alarm
l Alarm level: Major
l Alarm description: Trunk frames are lost.

Causes
l The two ends are not connected to the same ground.
l The clock is not synchronous.
l The transmission device is faulty

Impact on the System

Receiving of trunk signals on this trunk is interrupted.

Handling
1. Check whether the cable impedance matches the local device, and whether the type
of rear card jumper is consistent with the DIP switch of the board (cable type).
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Reset the DIP switch of the board or the rear card jumper. Check whether the alarm
disappears.

5-3

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Yes: End.
l No: Go to Step 3.
3. Check whether grounding signals are reliable between the devices at both ends by
using a multimeter.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Make sure the grounding signals are reliable between both devices. Check whether
the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Check whether the clock subcard on the switching board works in tracing state (the
tracing/capturing state light indicator marked with T/C corresponding to the clock
subcard on the switching board keeps on always).
l Yes: Go to Step 6.
l No: Check the clock reference and make sure that clock reference is locked. Then
go to Step 6.
6. Check whether the clock reference is consistent between the NEs or nodes at both
ends.
l Yes: Go to Step 8.
l No: Go to Step 7.
7. Modify the clock reference to make sure that it is consistent between the NEs or nodes
at both ends. Check whether the alarm disappears.
l Yes: End.
l No: Go to Step 8.
8. Ask for the maintenance personnel of transmission devices to check whether
transmission devices are faulty. Identify the fault source through level-by-level
physical loopback tests. If the alarm still remains, contact ZTE.

5.3 Trunk Signal Loss (513)

Receiving of trunk signals is interrupted.

Handling
At least one alarm is reported on the peer device among LOS, AIS, and LOF. Therefore,
check and record alarms reported on the peer device. Check whether any intermediate
transmission device on the trunk link fails.
l Yes: Contact transmission engineer to handle the problem.
l No: Contact ZTE.

5.7 Trunk Link Is Used for CSU Loopback Test (518)

Alarm Information
l Alarm code: 518
l System type: NE alarm

5-6

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l Alarm level: Minor

l Alarm description: This trunk link is used to CSU loopback test.

Cause
Device A sends a CSU link establishment code to device B, and device B creates loopback
on the trunk link for CSU tests. This alarm will not be reported if the trunk link is not used
for CSU loopback tests.

Impact on the System

The configured trunk link may be blocked.

Handling
Perform diagnosis tests and send a command for canceling CSU loopback from device A
to device B.

5.8 Cell Delineation do not Synchronization About Cell

on E1/T1 Link (1026)
Alarm Information
l Alarm code: 1026
l System type: NE alarm
l Alarm level: Minor
l Alarm description: ATM cell synchronization failed.

Cause
The cell header HEC is damaged, and thus cells cannot be delineated from physical
layer frames. In general, this alarm is triggered by a bottom-layer fault, or simply caused
because the local equipment and the peer equipment handle the cell HEC in different
ways.

Impact on the System

Data receiving fails, and signaling link interruption occurs.

Handling
1. Check whether other physical layer alarms exist.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Check whether the alarm disappears after confirming that there are no other physical
alarms.
l Yes: End.
l No: Go to Step 3.

5-7

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

3. Unplug and plug the board to perform a hardware reset, and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Contact ZTE.

5.9 Clock Board Is in Preheat Status (1285)

Alarm Information
l Alarm code: 1285
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Clock board is in preheating status.

Cause
When a board is reset, the SETS chip and constant-temperature crystal oscillator should
be fully preheated.

Impact on the System

The output clock is unstable.

Handling
This is normal after a board is powered on. Make sure that preheating of the clock board
terminates before clock performance tests.

5.10 Loss of Clock When Input to Board (1286)

Alarm Information
l Alarm code: 1286
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Loss of the input clock of the board.

Causes
l The boards are not securely positioned in the slots.
l The clock wire is not connected.
l One of the clock boards in the same shelf is faulty.
l The board goes faulty.

5-8

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

Impact on the System

5.14 Board Config Information not Compatible (5200)

Alarm Information
l Alarm code: 5200
l System type: NE alarm
l Alarm level: Major
l Alarm description: The board configuration information is incompatible with the board
type.

Cause
The obtained board configuration information is incompatible with the board type.

Impact on the System

The board is incompatible, and cannot be powered on.

Handling
1. Check whether the board configuration information matches with the board.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Modify the board configuration information, or replace the board with a matching board,
and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Contact ZTE.

5-11

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

5.15 Packet Test of Internal Media Plane Is Abnormal

(5396)
Alarm Information
l Alarm code: 5396
l System type: NE alarm
l Alarm level: Major
l Alarm description: The test on the media-plane messages internal the board is
abnormal.

Cause
The loss rate of the media-plane packets internal the board exceeds the preset threshold
(5% by default).

Note:
This alarm rarely occurs.

Impact on the System

Media streams cannot be transmitted.

Handling
1. On the Fault Management view of NMS, check whether an alarm related to CPU
overload is reported on the switching board, co-shelf switching board, or the board.
l Yes: Handle the problem according to the handling suggestions of the alarm.
l No Go to Step 2.
2. On the Fault Management view of NMS, check whether an alarm is reported to prompt
abnormal inter-shelf media plane links.
l Yes: Handle the problem according to the handling suggestions of the alarm.
l No Go to Step 3.
3. Replace the board and observe whether the alarm disappears.
l Yes: End.
l No Go to Step 4.
4. Plug the board in another slot and observe whether the alarm disappears.
l Yes: End.
l No Go to Step 5.
5. Replace the co-shelf switching board and observe whether the alarm disappears.
l Yes: End.
l No Contact ZTE.

5-12

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

5.16 Clock Board Work Mode Is Abnormal (5405)

Alarm Information
l Alarm code: 5405
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The clock board has an abnormal work mode.

Causes
l No reference source is available.
l The clock distribution line is incorrect or self-loop exists.
l A stratum-2 clock locks a stratum-3 clock.

Impact on the System

A specified reference clock cannot be phase-locked.

Handling
1. Check whether the clock reference is correctly connected.
l Yes: Replace the board and go to Step 2.
l No: Correctly connect the clock reference and go to Step 2.
2. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.17 The Hard Disk Used-Rate Is over Threshold (5632)

Alarm Information
l Alarm code: 5632
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The hard disk use rate exceeds the threshold.

Cause
The used capacity of the hard disk exceeds the alarm threshold.

Impact on the System

The hard disk cannot work properly.

Handling
Check whether the used capacity of hard disk is too high.

5-13

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Yes: Sort out the space of hard disk to make sure that the used capacity is lower than
the threshold.
l No: Contact ZTE.

5.18 The Hard Disk Becomes Error or not Exist (5633)

Alarm Information
l Alarm code: 5633
l System type: NE alarm
l Alarm level: Major
l Alarm description: The hard disk has become error or does not exist.

Cause
The hard disk is damaged or fails to be detected by the system.

Impact on the System

The hard disk cannot be used, and the storage capability of the system is influenced. The
system does not have any storage capability if there is only one hard disk.

Handling
1. Check whether the user-enabled hard disk exists.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Repair or replace the hard disk, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
3. Insert a hard disk, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Contact ZTE.

5.19 Sub Card Abnormal (5645)

Alarm Information
l Alarm code: 5645
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The subcard is abnormal.

Cause
The subcard is abnormal or the subcard Flash memory is being formatted.

5-14

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

Impact on the System

The subcard cannot work properly.

Handling
1. Check whether the Flash memory is being formatted.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Check whether the alarm disappears after the formatting is over.
l Yes: End.
l No: Go to Step 3.
3. Check whether the subcard is faulty.
l Yes: Go to Step 4.
l No: Go to Step 5.
4. Replace the subcard, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Contact ZTE.

5.20 Phase-Lock Loop Unlock (5646)

Alarm Information
l Alarm code: 5646
l System type: NE alarm
l Alarm level: Critical
l Alarm description: Phase-lock loop cannot be locked.

Causes
l The clock extracting reference is switched. In specific, the interface board disables
clock output when an optical interface fails, thus causing input changes to the clock
board. Or the NMS sets another optical interface to extract the clock.
l The input of the clock board changes, thus causing output changes.
l Hardware failure occurs on the phase-lock loop.

Impact on the System

The service clock of the board where the phase-lock loop is unlocked is not synchronous
with the system clock. As a result, services carried on the board are interrupted.

Handling
1. On the Fault Management view of NMS, check whether a relevant clock alarm is
reported.

5-15

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Yes: Handle the problem according to the handling suggestions of the relevant
alarm.
l No: Go to Step 2.
2. On the Fault Management view of NMS, check whether a relevant alarm is reported
on the optical interface that extracts the clock.
l Yes: Handle the problem according to the handling suggestions of the relevant
alarm.
l No: Go to Step 3.
3. Check NMS operation and maintenance logs. Check whether an operator of changing
the loop clock extracting reference exists.
l Yes: This alarm is a normal phenomenon and cannot be neglected.
l No: Go to Step 4.
4. Switch the clock board (that is, the switching board). Check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 5.
5. Replace the board. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.21 Error Packets of MAC Is Higher than the Specified

Threshold (5666)
Alarm Information
l Alarm code: 5666
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Error MAC packets exceeds the threshold.

Cause
The packet error rate of the MAC port exceeds the threshold.

Impact on the System

The MAC port cannot be used or traffic is limited.

Handling
1. Check whether the local port is correctly connected with the peer port.
l Yes: Go to Step 2.
l No: Check the physical cable. If it is damaged, replace it with a good one. Check
whether the alarm disappears.

à Yes: End.

5-16

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

à No: Go to Step 2.
2. Replace the local board or the peer interface. Check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Replace the peer board or the local interface. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.22 Oscillator Status Abnormal (5670)

Alarm Information
l Alarm code: 5670
l System type: NE alarm
l Alarm level: Critical
l Alarm description: Oscillator status abnormal.

Cause
The crystal oscillator stops working or frequency deviation occurs.

Impact on the System

Because the crystal oscillator is an important component, the board cannot work after the
oscillator is damaged.

Handling
Replace the board. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.23 MAC Port Link Is Down (5760)

Alarm Information
l Alarm code: 5760
l System type: NE alarm
l Alarm level: Warning
l Alarm description: MAC port link is down.

Cause
The MAC port link is broken.

5-17

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

The MAC port link is broken.

Handling
1. Check whether the link works properly.
l Yes: Go to Step 2.
l No: Solve the link problem. Check whether the alarm disappears.
à Yes: End.
à No: Go to Step 2.
2. Check whether the port mode is reasonably configured.
l Yes: Go to Step 3.
l No: Modify the port mode. Check whether the alarm disappears.
à Yes: End.
à No: Go to Step 3.
3. Contact ZTE.

5.24 The Speed Mode of the Port Doesn't Match with

Settings (5761)
Alarm Information
l Alarm code: 5761
l System type: NE alarm
l Alarm level: Major
l Alarm description: The speed mode of the port doesn't match with settings.

Cause
The chip performance is not successfully configured on the local or peer end. As a result,
the setting of working mode of the external port does not take effect, and the port fails to
work in the configured speed mode.

Impact on the System

The network port fails to work in the configured speed mode.

Handling
1. Check whether the speed mode of the peer end is correctly configured to match the
local end.
l Yes: Go to Step 2.
l No: Modify the speed mode of the peer end to make it match the local end. Check
whether the alarm disappears.

5-18

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

à Yes: End.
à No: Go to Step 2.
2. Check whether the speed mode of the local end is correctly configured.
l Yes: Contact ZTE.
l No: Modify the speed mode of the local end. Check whether the alarm disappears.
à Yes: End.
à No: Contact ZTE.

5.25 One Frequency of Clock Is All Lost when Input

to Board (5768)
Alarm Information
l Alarm code: 5768
l System type: NE alarm
l Alarm level: Major
l Alarm description: All input clocks of the boards at a frequency are lost.

Causes
l The board is not tightly inserted in the slot.
l Two clock boards in the same shelf have no output signals.
l The clock board fails.
l The clock line fails.
l The board fails.

Impact on the System

The board cannot synchronize with the system clock or work properly. As a result, users
cannot access the board and services carried on the board are interrupted.

Handling
1. Check whether the clock board and clock line work properly in the local shelf.
l Yes: Got to Step 2.
l No: Solve the clock board and clock line problem. Check whether the alarm
disappears.

à Yes: End.

à No: Got to Step 2.

2. Replace the board. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5-19

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

5.26 The Master and Slave Mode of the Port Doesn't

Match with Settings (5769)
Alarm Information
l Alarm code: 5769
l System type: NE alarm
l Alarm level: Major
l Alarm description: The master and slave mode of the port doesn't match with settings.

Cause
The master/slave mode does not match the configuration.

Impact on the System

The network port fails to work in the configured master/slave mode.

Handling
1. Check whether the master/slave mode of the peer end is correctly configured to match
the local end.
l Yes: Go to Step 2.
l No: Modify the master/slave mode of the peer end to make it match the local end.
Check whether the alarm disappears.
à Yes: End.

à No: Go to Step 2.
2. Check whether the master/slave mode of the local end is correctly configured.
l Yes: Contact ZTE.
l No: Modify the master/slave mode of the local end. Check whether the alarm
disappears.
à Yes: End.
à No: Contact ZTE.

5.27 The OMP Board Doesn't Have OMC Port (5770)

Alarm Information
l Alarm code: 5770
l System type: NE alarm
l Alarm level: Warning
l Alarm description: The OMP board doesn't have OMC port.

5-20

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

Cause
l The rear card has incorrect model or is not well inserted.
l The board does not support the OMC port.

Impact on the System

The OMP cannot communicate through an OMC port.

Handling
1. Check the rear card to make sure that it has correct model and is correctly inserted.
2. Check the board hardware to make sure it supports the OMC port.

5.28 The Duplex Mode of the Port Doesn't Match with

Cause
The E1/T1 link or the uplink equipment has faults.

Alarm Information
l Alarm code: 5788
l System type: NE alarm
l Alarm level: Major
l Alarm description: The subcard works with critical errors.

The EPLD version is not upgraded.

Handling
1. Check whether the switching boards in the same shelf as the board and the switching
board co-existing in the shelf where OMP is plugged work properly.

5-26

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l Yes: Go to Step 2.
l No: Restore the preceding board to normal working status.
à Yes: Go to Step 2.
à No: Contact ZTE.
2. Upgrade the EPLD again. Check whether a new EPLD version runs on the preceding
board.
l Yes: End.
l No: Contact ZTE.

5.38 Inner Port Error (7169)

Alarm Information
l Alarm code: 7169
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The speed or the duplex mode of the inner ports is abnormal. Inner
ports include the ports connected to the other slots on the switching board and the
network ports provided on the PP board (the board without the OMP module).

Causes
l The duplex mode of an internal port for connecting other intra-shelf slots on the
switching board is abnormal and cannot be self-healed.
l The speed mode of an internal port for connecting other intra-shelf slots on the
switching board is abnormal and cannot be self-healed.
l The duplex mode of a network interface on the PP board is abnormal and cannot be
self-healed.
l The speed mode of a network interface on the PP board is abnormal and cannot be
self-healed.

Impact on the System

l The PP board cannot communicate.
l The switching board cannot communicate with the boards in the intra-shelf slots.

Handling
Restart the board with the alarm.

5.39 Media Status Abnormal (15360)

Alarm Information
l Alarm code: 15360

5-27

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l System type: NE alarm

l Alarm level: Major
l Alarm description: The network processing components such as the media-plane
processor kernel, the micro-engine, or APP650/APP100 run improperly or cannot be
continuously kept activated.

Cause
The network processing components such as the media-plane processor kernel, the
micro-engine, or APP650/APP100 run improperly or cannot be continuously kept
activated.

Impact on the System

The media plane fails to work properly, thus affecting the entire system.

Handling
Because this problem is mostly caused by failure of board hardware, replace the board if
this alarm is repeatedly reported.

5.40 Too Many Bad Frames Received (15618)

Alarm Information
l Alarm code: 15618
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Too many bad frames received during a certain period of time.

Cause
Within a period of time, the number of bad frames received by the media plane interface
exceeds the threshold. The reason is that components are faulty or the connection of
fibers and network cables is broken.

Impact on the System

The communication quality is affected.

Handling
Check the connection of fibers and network cables. If the alarm is repeatedly reported,
replace the board.

5-28

Chapter 5 Equipment Alarms

l System type: NE alarm

l Alarm level: Minor
l Alarm description: The RACK temperature is higher than the alarm threshold.

Cause
l The threshold is unreasonably set.
l The real rack temperature is too high.

Impact on the System

l Services are not influenced if the threshold is unreasonably set.
l The board may fail to work properly and the services borne on the board may be
interrupted if the actual temperature is too high.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW ENVIOR
command to check whether the higher temperature threshold of the rack is reasonably
set.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Run the SET ENVIOR command to modify the higher temperature threshold of the
rack, and synchronize the data, then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Decrease the rack temperature, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.

5.45 RACK Temperature Is Lower than Low Threshold

(25857)
Alarm Information
l Alarm code: 25857
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The RACK temperature is lower than the lower threshold.

Causes
l The preset rack temperature threshold is unreasonable.
l The real temperature is too low.

5-31

l Services are not influenced if the threshold is unreasonably set.
l If the humidity is too high, the equipment may fail to work properly and the services
on the equipment may be interrupted.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW ENVIOR
command to check whether the equipment room humidity threshold is reasonably set.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Run the SET ENVIOR command to modify the equipment room humidity threshold (to
90), and synchronize the data, then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Lower the equipment room humidity, and check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.51 Humidity Is Lower than Low Threshold (25863)

Alarm Information
l Alarm code: 25863
l System type: NE alarm
l Alarm level: Minor

5-36

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l Alarm description: Humidity is lower than low threshold

Causes
l The equipment room humidity threshold is unreasonably set.
l The humidity in equipment room is lower than the lower limit of the alarm threshold.
l The humidity sensor of the equipment room is wrongly connected.

Impact on the System

l Services are not influenced if the threshold is unreasonably set.
l The board may fail to work properly and the services borne on the board may be
interrupted if the actual equipment room humidity is too low.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW ENVIOR
command to check whether the low-humidity threshold is reasonably set.
l Yes: Go to Step 3.
l No: Go to Step 2.
2. Run the SHOW ENVIOR command to modify the equipment room low-humidity
threshold, synchronize the data to the foreground, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Raise the rack humidity, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Check whether the sensor is correctly connected.
l Yes: Contact ZTE.
l No: Go to Step 5.
5. Properly connect the sensor, and then check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.52 Fault in Fan Plug-In Box (25864)

Alarm Information
l Alarm code: 25864
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The fans in the rack are faulty.

Causes
l The fan shelf is loosely inserted.

5-37

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

This alarm does not affect services, but may cause potential safety risk.

Handling
Check whether there is smoke in the equipment room.
l Yes: Dispel the smoke, and check whether the alarm disappears.

à Yes: End.

5-39

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

à No: Contact ZTE.

l No: Contact ZTE.

5.55 Infrared Alarm (25867)

Alarm Information
l Alarm code: 25867
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Infrared alarm

Causes
l There is heat source approaching, including animals and human beings.
l The infrared sensor settings are incorrect.
l The sensor is faulty.
l The sensor is wrongly connected.

Impact on the System

l If the infrared alarm is caused by incorrect setting of the infrared sensor, it has no
impact on the system.
l If the infrared in the equipment room exceeds the threshold value, there is potential
safety risk.

Handling
1. Check whether there is creature around the infrared sensor.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Keep the creature away from the sensor, and then check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 3.
3. Check whether the infrared sensor is correctly set.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Properly set the infrared sensor, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Check whether the infrared sensor is faulty.
l Yes: Go to Step 6.
l No: Go to Step 7.
6. Replace the infrared sensor, and then check whether the alarm disappears.
l Yes: End.

5-40

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l No: Go to Step 7.
7. Check whether the infrared sensor is correctly connected.
l Yes: Go to Step 9.
l No: Go to Step 8.
8. Properly connect the infrared sensor, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 9.
9. Contact ZTE.

5.56 Lightning Alarm (25868)

Alarm Information
l Alarm code: 25868
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Lightning alarm

Causes
l The equipment room is influenced by thunder strike in bad weather.
l The lightning protection sensor is wrongly connected.

Impact on the System

The equipment may suffer from lightning stroke and thus fail to work properly. Then the
services on the abnormal equipment will be interrupted.

Handling
1. Check whether there is lightning hazard.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Take protection measures, and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check whether the sensor is correctly connected.
l Yes: Go to Step 4.
l No: Reconnect the sensor.
4. Contact ZTE.

5.57 Power Switch Alarm (25869)

Alarm Information
l Alarm code: 25869

5-41

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l System type: NE alarm

l Alarm level: Minor
l Alarm description: Air switch alarm.

Causes
l This air switch is not switched on, but the configuration on the NMS needs to enable
the air switch detection.
l The air switch sensor is wrongly connected.

Impact on the System

This alarm influences the power supply of the shelf. All boards in the shelf will fail to work
properly, and the services provided by the boards will be interrupted.

Handling
l If you use the shelf:
1. Check whether the air switch is switched on, and whether the ALM indicator is
normal.
à Yes: Go to Step 3.
à No: Go to Step 2.
2. Switch on the air switch, and then check whether the alarm disappears.
à Yes: End.
à No: Go to Step 3.
3. Check whether the sensor is working properly.
à Yes: Go to Step 5.
à No: Go to Step 4.
4. Correctly connect the sensor, confirm that the sensor works properly, and then
check whether the alarm disappears.
à Yes: End.
à No: Go to Step 5.
5. Contact ZTE.
l If you do not use the shelf:
1. On the MML Terminal or Terminal view of the NMS, run the SHOW ENVIOR
command to check whether the air switch is shielded.
à Yes: Go to Step 3.
à No: Go to Step 2.
2. Run the SET ENVIOR command to change the switch to NO, and then check
whether the alarm disappears.
à Yes: End.

5-42

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

à No: Go to Step 3.
3. Contact ZTE.

5.58 Power Type Configured Does Not Accord with

Physical (25870)
Alarm Information
l Alarm code: 25870
l System type: NE alarm
l Alarm level: Minor
l Alarm description: Power type configured does not accord with physical.

Cause
The device type configured in the database is not consistent with the board hardware.

Impact on the System

The board cannot work properly.

Handling
1. According to the additional alarm information, check the configuration on the NMS to
see whether the configuration information is consistent with the board hardware.
l Yes: Go to Step 2.
l No: Modify the configuration according to the hardware and power on the board
again. The alarm disappears.
2. Contact ZTE.

5.59 Clock Reference Source Lost (Level 3 Alarm)

(26127)
Alarm Information
l Alarm code: 26127
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The clock reference source is lost (Level 3 alarm).

Cause
The duration in which the input reference is in invalid status is less than 10 minutes.
Possible causes include:
l The clock reference input is abnormal.

5-43

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l The configured clock reference does not exist.

Impact on the System

When all references configured in the system are lost, the clock board enters the free
running or holding status. The output clock precision is determined by the crystal oscillator
of the clock board and does not affect services.

Handling
1. Check whether the corresponding clock reference is correctly led in.
l Yes: Replace the board, and then go to Step 2.
l No: Correctly lead in the clock reference and go to Step 2.
2. Check whether the alarm disappears.
l Yes: End.
l No: Contact ZTE.

5.60 Clock Reference Source Lost (Level 2 Alarm)

(26128)
Alarm Information
l Alarm code: 26128
l System type: NE alarm
l Alarm level: Major
l Alarm description: The clock reference source is lost (Level 2 alarm).

Cause
The duration in which the input reference is in invalid status is larger than 10 minutes less
than 24 hours. Possible causes include:
l The clock reference input is abnormal.
l The configured clock reference does not exist.

Impact on the System

Handling
1. Check whether the corresponding clock reference is correctly led in.
l Yes: Replace the board, and then go to Step 2.
l No: Correctly lead in this clock reference, and then go to Step 2.
2. Check whether this alarm disappears.
l Yes: End.

5-44

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l No: Contact ZTE.

5.61 Clock Reference Source Lost (Level 1 Alarm)

(26129)
Alarm Information
l Alarm code: 26129
l System type: NE alarm
l Alarm level: Critical
l Alarm description: The clock reference source is lost (Level 1 alarm).

Cause
The duration in which the input reference is in invalid status is larger than 24 minutes.
Possible causes include:
l The clock reference input is abnormal.
l The configured clock reference does not exist.

Impact on the System

5.62 Output Clock Lost (26133)

Alarm Information
l Alarm code: 26133
l System type: NE alarm
l Alarm level: Major
l Alarm description: Loss of the output clock

Cause
There are hardware faults in the board.

5-45

The temperature in the shelf increases so that the hardware in the shelf is damaged.

Handling
Replace the fan, and then check whether the alarm disappears.
l Yes: Clear all foreign substances from the fan, so that the fan works properly.
l No: Record the abnormality, and then contact ZTE.

5-47

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

5.66 IPMB State Change (IPMB-A Enable \ IPMB-B

Disable) (30812)
Alarm Information
l Alarm code: 30812
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The IPMB state changes (IPMB-A enabled \IPMB-B disabled).

Cause
The IPMB-A is enabled and the IPMB-B is disabled.

Impact on the System

CMM may fail to control the equipment, which may be damaged.

Handling
Contact ZTE.

5.67 IPMB State Change (IPMB-A Disable\IPMB-B

Enable) (30813)
Alarm Information
l Alarm code: 30813
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The IPMB state changes (IPMB-A disabled \IPMB-B enabled).

Cause
The IPMB-A is disabled and the IPMB-B is enabled.

Impact on the System

CMM may fail to control the equipment, which may be damaged.

Handling
Contact ZTE.

5-48

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

5.68 STC Office Inaccessible (8402944)

Alarm Information
l Alarm code: 8402944
l System type: NE alarm
l Alarm level: Major
l Alarm description: The STC office is inaccessible.

Cause
No SCTP association to the office is available.

Impact on the System

Users fail to receive or send messages from or to the office, new service accessing to this
office fails, and some services are abnormally released.

Handling
1. Check whether there are any alarms for disconnected associations.
l Yes: Handle the alarm according to the handling suggestions in 2.29 Association
Link Broken (8402690).
l No: Go to Step 2.
2. On the MML Terminal or Terminal view of the NMS, check whether related association
is configured for the office.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. Add the association configuration of the office and check whether the alarm
disappears.
l Yes: End.
l No: Go to Step 4.
4. Record the following information and contact ZTE.
l Configuration data of the local office and peer-end office.
l History alarms, history notifications, and current alarms of the local office and
peer-end office.

5.69 NM Server CPU Usage Rate Exceeds Criterion

(2365981185)
Alarm Information
l Alarm code: 2365981185
l System type: OMM system alarm
l Alarm level: Major
l Alarm description: The OMM server CPU utilization exceeds the set threshold.

5-49

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Cause
Of the CPU resource monitoring parameters, Switch is set to Close. If the OMM server
CPU utilization detected at a monitoring time point exceeds the set CPU utilization
threshold for N consecutive times (N = Consecutive CPU utilization out-of-limit alarm
threshold), this alarm is triggered.

Note:
When the CPU utilization is lower than 1%, the monitoring process returns a CPU utilization
of 1%. In other cases, the monitoring process directly returns the integer of the calculated
CPU utilization (instead of rounding up or down the CPU utilization. For example, the
monitoring process returns 6% if the calculation result of the current CPU utilization is
6.3% or 6.9%.
Monitoring time point: If Switch among the CPU resource monitoring parameters is set
to Open when the running environment monitoring thread is started, a CPU resource
monitoring timer is triggered. This timer will be triggered again at an interval (user-specified
monitoring period), and the system will read a new monitoring period (that is, changes to
the monitoring period do not take effect in real time but the monitoring period is updated at
the monitoring time point only). Monitoring is performed each time the monitoring timer is
triggered. Therefore, alarm recovery does not take effect in real time and the alarm of the
corresponding level is recovered only when the CPU utilization detected at the monitoring
time point is lower than the set threshold.

Impact on the System

The normal running of the OMM may be influenced.

Handling
1. Run the top command on the NMS server to find the COMMAND in the rows where
the value of %CPU is large and check whether the processes are expected ones.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Kill the processes with high CPU utilization as required, or open the MML Terminal or
Terminal view of the NMS and run the SET CPUPARA command to change Switch
to Close, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
3. Confirm whether the processes are normal, take proper actions to remove faults, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Contact ZTE.

5-50

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

5.70 NM Server Memory Usage Rate Exceeds Criterion

(2365981186)
Alarm Information
l Alarm code: 2365981186
l System type: OMM system alarm
l Alarm level: Major
l Alarm description: The OMM server memory utilization exceeds the set threshold.

Cause
Of the memory resource monitoring parameters, Switch is set to Open. If the OMM server
memory utilization detected at the monitoring time point exceeds the set memory utilization
threshold for N consecutive times (N = Consecutive memory utilization out-of-limit alarm
threshold), this alarm is triggered.

Note:
When the memory utilization is lower than 1%, the monitoring process returns a memory
utilization of 1%. In other cases, the monitoring process directly returns the integer of the
calculated memory utilization (instead of rounding up or down the memory utilization. For
example, the monitoring process returns 6% if the calculation result of the current memory
utilization is 6.3% or 6.9%.
Monitoring time point: If Switch among the memory resource monitoring parameters is set
to Open when the running environment monitoring thread is started, a memory resource
monitoring timer is triggered. This timer will be triggered again at an interval (user-specified
monitoring period), and the system will read a new monitoring period (that is, changes to
the monitoring period do not take effect in real time but the monitoring period is updated
at the monitoring time point only). Monitoring is performed each time the monitoring timer
is triggered. Therefore, alarm recovery does not take effect in real time and the alarm
of the corresponding level is recovered only when the memory utilization detected at the
monitoring time point is lower than the set threshold.

Impact on the System

The normal running of the OMM may be influenced.

Handling
1. Run the top command on the NMS server to find the COMMAND in the rows where
the value of %MEM is large and check whether the processes are expected ones.
l Yes: Go to Step 2.
l No: Go to Step 3.

5-51

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

2. Kill the processes with high memory utilization as required, or open the MML Terminal
or Terminal view of the NMS and run the SET MEMPARA command to change Switch
to Close, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
3. Confirm whether the processes are normal, take proper actions to remove faults, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Contact ZTE.

5.71 NM Server Hard Disk Usage Rate Exceeds

Criterion(Level 1 Alarm) (2365981187)
Alarm Information
l Alarm code: 2365981187
l System type: OMM system alarm
l Alarm level: Critical
l Alarm description: The OMM server hard disk utilization exceeds the set level-1 alarm
threshold.

Cause
Of the global hard disk monitoring parameters, Switch is set to Open. For a specific
partition, Monitor Type is set to Absolute Value Monitor(M) or Percentage Monitor(%)
whereas Threshold-Critical is set to a non-0 value. If the hard disk utilization detected at
the monitoring time point exceeds the set monitoring threshold of the critical level, a level-1
alarm about the hard disk utilization of the partition is triggered.

Note:
Hardware partitions are monitored on the CGSL system.

Monitoring time point: If Switch among the global hard disk monitoring parameters is set
to Open when the running environment monitoring thread is started, a hard disk resource
monitoring timer is triggered. This timer will be triggered again at an interval (user-specified
monitoring period), and the system will read a new monitoring period (that is, changes to
the monitoring period do not take effect in real time but the monitoring period is updated
at the monitoring time point only). Monitoring is performed each time the monitoring timer
is triggered. Therefore, alarm recovery does not take effect in real time and the alarm of
the corresponding level is recovered only when the hard disk utilization detected at the
monitoring time point is lower than the set threshold.

5-52

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

Impact on the System

The normal running of the OMM may be influenced.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW HDPARA
command to check whether Switch among the global hard disk monitoring parameters
is set to Open and whether the monitoring period is reasonably set.
l Yes: Go to Step 2.
l No: Go to Step 7.
2. Check whether to enable hard disk monitoring.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. On the MML Terminal or Terminal view of the NMS, run the SET HDPARA command
to change Switch among the global hard disk monitoring parameters to Close (it is
not recommended that hard disk monitoring be disabled), and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
4. On the MML Terminal or Terminal view of the NMS, run the SHOW PARTITIONPAR
A command to check whether Threshold-Critical is properly set among the hard disk
partition monitoring parameters.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. On the MML Terminal or Terminal view of the NMS, run the SET PARTITIONPARA
command to change the settings of Threshold-Critical to a reasonable value, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 6.
6. Clear the files on the hard disk according to the alarm information and actual needs to
evacuate a sufficient space and ensure that the directory utilization is lower than the
monitoring threshold of the corresponding alarm level, and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

5.72 NM Server Hard Disk Usage Rate Exceeds

Criterion(Level 2 Alarm) (2365981188)
Alarm Information
l Alarm code: 2365981188
l System type: OMM system alarm

5-53

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Alarm level: Major

l Alarm description: The OMM server hard disk utilization exceeds the set level-2 alarm
threshold.

Cause
Of the global hard disk monitoring parameters, Switch is set to Open. For a specific
partition, Monitor Type is set to Absolute Value Monitor(M) or Percentage Monitor(%)
whereas Threshold-Major is set to a non-0 value. If the hard disk utilization detected at
the monitoring time point exceeds the set monitoring threshold of the major level, a level-2
alarm about the hard disk utilization of the partition is triggered.

Note:
Hardware partitions are monitored on the CGSL system.
Monitoring time point: If Switch among the global hard disk monitoring parameters is set
to Open when the running environment monitoring thread is started, a hard disk resource
monitoring timer is triggered. This timer will be triggered again at an interval (user-specified
monitoring period), and the system will read a new monitoring period (that is, changes to
the monitoring period do not take effect in real time but the monitoring period is updated
at the monitoring time point only). Monitoring is performed each time the monitoring timer
is triggered. Therefore, alarm recovery does not take effect in real time and the alarm of
the corresponding level is recovered only when the hard disk utilization detected at the
monitoring time point is lower than the set threshold.

Impact on the System

The normal running of the OMM may be influenced.

5-54

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l No: Go to Step 7.
4. On the MML Terminal or Terminal view of the NMS, run the SHOW PARTITIONPA
RA command to check whether Threshold-Major is properly set among the hard disk
partition monitoring parameters.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. On the MML Terminal or Terminal view of the NMS, run the SET PARTITIONPARA
command to change the settings of Threshold-Major to a reasonable value, and then
check whether the alarm disappears.
l Yes: End.
l No: Go to Step 6.
6. Clear the files on the hard disk according to the alarm information and actual needs to
evacuate a sufficient space and ensure that the directory utilization is lower than the
monitoring threshold of the corresponding alarm level, and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

5.73 NM Server Hard Disk Usage Rate Exceeds

Criterion(Level 3 Alarm) (2365981189)
Alarm Information
l Alarm code: 2365981189
l System type: OMM system alarm
l Alarm level: Minor
l Alarm description: The OMM server hard disk utilization exceeds the set level-3 alarm
threshold.

Cause
Of the global hard disk monitoring parameters, Switch is set to Open. For a specific
partition, Monitor Type is set to Absolute Value Monitor(M) or ercentage Monitor(%)
whereas Threshold-Minor is set to a non-0 value. If the hard disk utilization detected
at the monitoring time point exceeds the set monitoring threshold of the minor level but
does not reach the monitoring thresholds of the major and critical levels (the value 0 is not
compared), a level-3 alarm about the hard disk utilization of the partition is triggered.

5-55

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

The normal running of the NMS may be influenced.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW HDPARA
command to check whether Switch among the global hard disk monitoring parameters
is set to Open and whether the monitoring period is reasonably set.
l Yes: Go to Step 2.
l No: Go to Step 7.
2. Determine whether to enable hard disk monitoring.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. On the MML Terminal or Terminal view of the NMS, run the SET HDPARA command
to change Switch among the global hard disk monitoring parameters to Open (it is
not recommended that hard disk monitoring be disabled), and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
4. On the MML Terminal or Terminal view of the NMS, run the SHOW PARTITIONPA
RA command to check whether Threshold-Minor is properly set among the hard disk
partition monitoring parameters.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. On the MML Terminal or Terminal view of the NMS, run the SET PARTITIONPARA
command to change the settings of Threshold-Minor to a reasonable value, and then
check whether the alarm disappears.
l Yes: End.
l No: Go to Step 6.

5-56

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

6. Clear the files on the hard disk according to the alarm information and actual needs to
evacuate a sufficient space and ensure that the directory utilization is lower than the
monitoring threshold of the corresponding alarm level, and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

5.74 NM Server Hard Disk Usage Rate Exceeds

Criterion(Level 4 Alarm) (2365981190)
Alarm Information
l Alarm code: 2365981190
l System type: OMM system alarm
l Alarm level: Warning
l Alarm description: The OMM server hard disk utilization exceeds the set level-4 alarm
threshold.

Cause
Of the global hard disk monitoring parameters, Switch is set to Open. For a specific
partition, Monitor Type is set to Absolute Value Monitor(M) or Percentage Monitor(%)
whereas Threshold-Warning is set to a non-0 value. If the hard disk utilization detected at
a monitoring time point exceeds the set monitoring threshold of the warning level but does
not reach the monitoring thresholds of the minor, major, and critical levels (the value 0 is
not compared), a level-4 alarm about the hard disk utilization of the partition is triggered.

Note:
Hardware partitions are monitored on the CGSL system.

5-57

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

Impact on the System

The normal running of the OMM may be influenced.

Handling
1. On the MML Terminal or Terminal view of the NMS, run the SHOW HDPARA
command to check whether Switch among the global hard disk monitoring parameters
is set to Open and whether the monitoring period is reasonably set.
l Yes: Go to Step 2.
l No: Go to Step 7.
2. Check whether to enable hard disk monitoring.
l Yes: Go to Step 4.
l No: Go to Step 3.
3. On the MML Terminal or Terminal view of the NMS, run the SET HDPARA command
to change Switch among the global hard disk monitoring parameters to Close (it is
not recommended that hard disk monitoring be disabled), and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
4. On the MML Terminal or Terminal view of the NMS, run the SHOW PARTITIONP
ARA command to check whether Threshold-Warning is properly set among the hard
disk partition monitoring parameters.
l Yes: Go to Step 6.
l No: Go to Step 5.
5. On the MML Terminal or Terminal view of the NMS, run the SET PARTITIONPARA
command to change the settings of Threshold-Warning to a reasonable value, and
then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 6.
6. Clear the files on the hard disk according to the alarm information and actual needs to
evacuate a sufficient space and ensure that the directory utilization is lower than the
monitoring threshold of the corresponding alarm level, and then check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Contact ZTE.

5.75 Directory Usage Rate Exceeds Criterion (Level 1

Alarm) (2365981191)
Alarm Information
l Alarm code: 2365981191
l System type: OMM system alarm

5-58

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

l Alarm level: Critical

l Alarm description: The directory utilization exceeds the level-1 alarm threshold.

Cause
A monitored object in directory resource monitoring parameter configuration is uniquely
determined by Directory Description, File Type, and Is Include Sub-Directory. For a
specific object, Switch is set to Open whereas Threshold-Critical(M) is set to a non-0
value. When the file size detected at the monitoring time point exceeds the set monitoring
threshold of the critical level, a level-1 alarm about the directory utilization of the object is
triggered.

Note:
l File size
The file size refers to the total size of files of the specified file type in the set Directory
Description. If the file type is "*", all types of files are monitored. If Is Include
Sub-Directory is set to Yes, all files in this directory and all its subdirectories are
monitored. Otherwise, only the files in the directory are monitored.
l Monitoring time point
If Switch is set to Open for an object when the running environment monitoring
thread is started, a directory resource monitoring timer is triggered. This timer will be
triggered again at an interval (user-specified monitoring period), and the system will
read a new monitoring period (that is, changes to the monitoring period do not take
effect in real time but the monitoring period is updated at the monitoring time point
only). Monitoring is performed each time the monitoring timer is triggered. Therefore,
alarm recovery does not take effect in real time and the alarm of the corresponding
level is recovered only when the directory utilization detected at the monitoring time
point is lower than the set threshold.

The normal running of the OMM may be influenced.

5-65

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

5.79 Link Between DBIO and HSMAPP Node Broken

(2534029328)
Alarm Information
l Alarm code: 2534029328
l System type: NE alarm
l Alarm level: Major
l Alarm description: Link between DBIO and HSMAPP node broken.

Cause
The link between the modules DBIO and HSMAPP is interrupted.

Impact on the System

Because HSM encryption and decryption cannot be done, the operations involving HSM
encryption and decryption cannot be done properly.

Handling
The network is abnormal. Check the network connection between DBIO and HSMAPP.

5.80 HSMAPP Node Status Error (2535069704)

Alarm Information
l Alarm code: 22535069704
l System type: NE alarm
l Alarm level: Major
l Alarm description: HSMAPP node status error.

5-66

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 5 Equipment Alarms

Cause
The HSMAPP module is in abnormal status and alarms are generated.

Impact on the System

The requests for provision with excessive load are rejected.

Handling
HSMAPP is abnormal. Check the status of HSMAPP.

5-67

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

This page intentionally left blank.

5-68

Threshold (30724)
Alarm Information
l Alarm code: 30724
l System type: NE alarm
l Alarm level: Warning
l Alarm description: The environmental temperature is relatively high.

Causes
l The environmental temperature is higher than the normal value.
l The velocity of the fan is lower than the normal value.
l The filter tray is dusty.

Impact on the System

(Non-critical) A part of services on the equipment are interrupted.

Handling
1. Wait until the alarm disappears. After a period, check whether the alarm disappears.
l Yes: End.
l No: Go to Step 2.
2. Check whether the temperature of the equipment room is high.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Reduce the temperature in the equipment room. After a period, check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Check whether the velocity of the fan is low
l Yes: Go to Step 5.
l No: Go to Step 6.
5. Increase the velocity of the fan. After a period, check whether the alarm disappears.

6-3

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Yes: End.
l No: Go to Step 6.
6. Check whether the filter tray is dusty.
l Yes: Go to Step 7.
l No: Go to Step 8.
7. Clean the filter tray. After a period, check whether the alarm disappears.
l Yes: End.
l No: Go to Step 8.
8. Record the alarm and contact ZTE.

6.5 Temperature Is Higher Than Upper-critical

Threshold (30725)
Alarm Information
l Alarm code: 30725
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The environmental temperature is too high.

Causes
l The environmental temperature is too high.
l The velocity of the fan is too low.
l The filter tray is very dusty.

Impact on the System

(Critical) A part of services on the equipment are interrupted.

Handling
1. Wait until the alarm disappears. After a period, check whether the alarm disappears.
l Yes: End.
l No: Go to Step 2.
2. Check whether the temperature of the equipment room is too high.
l Yes: Go to Step 3.
l No: Go to Step 4.
3. Reduce the temperature in the equipment room. After a period, check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 4.
4. Check whether the velocity of the fan is too low
l Yes: Go to Step 5.
l No: Go to Step 6.
5. Increase the velocity of the fan. After a period, check whether the alarm disappears.

6-4

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 6 Environment Alarms

l Yes: End.
l No: Go to Step 6.
6. Check whether the filter tray is too dusty.
l Yes: Go to Step 7.
l No: Go to Step 8.
7. Clean the filter tray. After a period, check whether the alarm disappears.
l Yes: End.
l No: Go to Step 8.
8. Record the alarm and contact ZTE.

6.6 Temperature Is Higher Than Upper-non-recoverable

Threshold (30726)
Alarm Information
l Alarm code: 30726
l System type: NE alarm
l Alarm level: Major
l Alarm description: The environmental temperature is extremely high.

Causes
l The environmental temperature is extremely high.
l The velocity of the fan is extremely low.
l The filter tray is extremely dusty.

Impact on the System

The equipment is damaged and the system functions are disabled.

Handling
1. Wait two minutes, and then check whether the alarm disappears.
l Yes: End.
l No: Go to Step 2.
2. Take off the device from the shelf, and contact ZTE.

6.7 Voltage Is Lower Than Lower-non-critical Threshold

(30727)
Alarm Information
l Alarm code: 30727
l System type: NE alarm
l Alarm level: Warning

6-5

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

l Alarm description: The voltage is relatively low.

Causes
l The voltage fluctuates.
l The resistance is invalid.
l The equipment payload fluctuates.
l The voltage deviates because of the improper temperature of the shelf’s environment.

Impact on the System

A part of services on the equipment are interrupted.

Handling
1. Wait until the alarm disappears. If the alarm still exists after a long period, go to Step
2.
2. Check whether the power supply of the equipment room is abnormal.
l Yes: Contact the power supply engineer.
l No: Record the alarm and contact ZTE.

6.8 Voltage Is Lower Than Lower-critical Threshold

(30728)
Alarm Information
l Alarm code: 30728
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The voltage is low.

Causes
l The voltage fluctuates.
l The resistance is invalid.
l The equipment payload fluctuates.
l The voltage deviates because of the improper temperature of the shelf’s environment.

Impact on the System

Most or even all of the services on the equipment are interrupted.

Handling
1. Wait until the alarm disappears. If the alarm still exists after a long period, go to Step
2.
2. Check whether the power supply of the equipment room is abnormal.

The heat dissipation of the shelf is bad.

Handling
Take off the filter tray and change it or clean it.

6-10

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Chapter 6 Environment Alarms

6.16 State Is Abnormal (30738)

Alarm Information
l Alarm code: 30738
l System type: NE alarm
l Alarm level: Minor
l Alarm description: The sensor state is improper.

Causes
l The voltage of the voltage regulating circuit is too high.
l The voltage regulating circuit is out of work.
l The switch of the power supply is turned on.
l The battery is too low.

Impact on the System

A part of the services on the equipment are interrupted.

Handling
1. Check whether the air switch of the power supply is on.
l Yes: Go to Step 2.
l No: Go to Step 3.
2. Switch off the air switch for power and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 3.
3. Check whether the power supply of the equipment room is normal.
l Yes: Go to Step 5.
l No: Go to Step 4.
4. Make sure the power supply of the equipment room is normal and check whether the
alarm disappears.
l Yes: End.
l No: Go to Step 5.
5. Check whether the battery has too low capacity.
l Yes: Go to Step 6.
l No: Go to Step 7.
6. Replace the battery and check whether the alarm disappears.
l Yes: End.
l No: Go to Step 7.
7. Record the alarm and contact ZTE.

6-11

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

ZXUN USPP HLR Alarm Message Reference

This page intentionally left blank.

6-12

SJ-20110221160004-013|2011-06-10(R1.1) ZTE Proprietary and Confidential

Glossary
ALM
- ALarM
AS
- Application Server
ASP
- Application Server Process
BFD
- Bidirectional Forwarding Detection
BOSS
- Business and Operation Support System
CC
- Continuity Check
CMM
- Chassis Management Module
CPU
- Central Processing Unit

CSU
- Control and Storage Unit

DB
- DataBase
DBIO
- DataBase Input & Output
DDF
- Digital Distribution Frame
DSA
- Directory System Agent
DSP
- Directory System Protocol
DST
- Data Storage Transfer

EMS
- Network Element Management System
EPLD
- Erasable Programmable Logic Device

I
ZXUN USPP HLR Alarm Message Reference

EPU
- Epilogue Process Unit
FAS
- Frame Alignment Signal
HEC
- Header Error Check
HLR
- Home Location Register
ICP
- Internet Content Provider
IMA
- Inverse Multiplexing over ATM
IP
- Internet Protocol
LDAP
- Lightweight Directory Access Protocol

LIF
- Loss of IMA Frame
LODS
- Link Out of Delay Synchronization defect
M2PA
- MTP2-User Peer-to-Peer Adaptation Layer Protocol
M3UA
- MTP3-User Adaptation layer protocol
MP
- Main Processor
MTP2
- Message Transfer Part layer 2

MTP3
- Message Transfer Part layer 3
NE
- Network Element
NMS
- Network element Management System
NTP
- Network Time Protocol

OAM
- Operation, Administration and Maintenance

II
Glossary

OMC
- Operation & Maintenance Center
OMM
- Operation & Maintenance Module
OMP
- Operation & Maintenance Processor
PEM
- Power Entry Module
PP
- Peripheral Processor
PPP
- Point to Point Protocol
PS
- Packet Switched
PVC
- Permanent Virtual Channel

QoS
- Quality of Service
RDI
- Remote Defect Indication
RPU
- Router Process Unit
SCCP
- Signaling Connection Control Part
SCTP
- Stream Control Transmission Protocol
SETS
- Synchronous Equipment Timing Source

SIO
- Service Information Octet
SLC
- Signaling Link Code
SNTP
- Simple Network Time Protocol
SSCOP
- Service Specific Connection Oriented Protocol

SSN
- Sub-System Number

III
ZXUN USPP HLR Alarm Message Reference

STC
- Signaling Transport Converter
SUA
- SCCP User Adaptation
TC
- Trunk Circuit
TIPC
- Transparent Interprocess Communication
UDS
- Universal Directory Server
VCI
- Virtual Channel Identifier
VPI
- Virtual Path Identifier
ZTE
- Zhongxing Telecommunications Equipment

Sean Griffith - Jessica Erickson - David H Webber - Verity Winship - Research Handbook On Representative Shareholder Litigation-Edward Elgar Publishing (2018)
No ratings yet
Sean Griffith - Jessica Erickson - David H Webber - Verity Winship - Research Handbook On Representative Shareholder Litigation-Edward Elgar Publishing (2018)
553 pages
My Law Internal Assessment (Ia)
0% (1)
My Law Internal Assessment (Ia)
24 pages
3JL03001BTAAPCZZA01 - V1 - 5529 IDM Release 9.7 Installation Administration and User Guide
No ratings yet
3JL03001BTAAPCZZA01 - V1 - 5529 IDM Release 9.7 Installation Administration and User Guide
136 pages
SJ-20201130103457-003-ZXMW (V3.05.03) Maintenance Guide - 1013679
No ratings yet
SJ-20201130103457-003-ZXMW (V3.05.03) Maintenance Guide - 1013679
68 pages
Spectrum Web Api PDF
No ratings yet
Spectrum Web Api PDF
73 pages
ZXWN MGW&IM-MGW Product Description
No ratings yet
ZXWN MGW&IM-MGW Product Description
38 pages
Introduction To ZXSDR Products (GSM)
100% (7)
Introduction To ZXSDR Products (GSM)
68 pages
BSC6900 UMTS Commissioning Guide (V900R018C10 Draft A) (PDF) - EN PDF
No ratings yet
BSC6900 UMTS Commissioning Guide (V900R018C10 Draft A) (PDF) - EN PDF
123 pages
02 ZXWR RNC Structure and Principle - PPT-52
100% (1)
02 ZXWR RNC Structure and Principle - PPT-52
77 pages
25-IsDN BRA, PRA User Enablement Guide
No ratings yet
25-IsDN BRA, PRA User Enablement Guide
25 pages
SJ-20100414142254-018-ZXG10 IBSC (V6.20.21) Base Station Controller Ground Parameter Reference
No ratings yet
SJ-20100414142254-018-ZXG10 IBSC (V6.20.21) Base Station Controller Ground Parameter Reference
395 pages
SJ-20120306200658-007-ZXUN uMAC (V4.11.20) GNGP SGSN Genera
No ratings yet
SJ-20120306200658-007-ZXUN uMAC (V4.11.20) GNGP SGSN Genera
111 pages
ZXG10 IBSC Architacture, Hardware Detail, System Discription
100% (1)
ZXG10 IBSC Architacture, Hardware Detail, System Discription
117 pages
ZXMW SR10 S340 (V2.0) Software Upgrade Guide
No ratings yet
ZXMW SR10 S340 (V2.0) Software Upgrade Guide
44 pages
HLR9820 COMMON Feature Description
No ratings yet
HLR9820 COMMON Feature Description
56 pages
Automatic OMCH Establishment (SRAN12.0 - 01)
No ratings yet
Automatic OMCH Establishment (SRAN12.0 - 01)
125 pages
ZXG10 IBSC Product Description
No ratings yet
ZXG10 IBSC Product Description
22 pages
NTC - Internship Report: National Telecommunication Corporation
No ratings yet
NTC - Internship Report: National Telecommunication Corporation
34 pages
CEN Workshop Agreement CWA 16008-7
No ratings yet
CEN Workshop Agreement CWA 16008-7
17 pages
01 ZXG10 BSC (V2.95) GuideToDocumentation PDF
No ratings yet
01 ZXG10 BSC (V2.95) GuideToDocumentation PDF
29 pages
ZXWN MGW Alarm and Notification Information PDF
No ratings yet
ZXWN MGW Alarm and Notification Information PDF
259 pages
Sjzl20070303-ZXWN MGW (V3.06) Media Gateway Technical Manual
No ratings yet
Sjzl20070303-ZXWN MGW (V3.06) Media Gateway Technical Manual
119 pages
SJ-20160530141220-001-ZXSDR R8852 (V1.0) Product Description - 891963
No ratings yet
SJ-20160530141220-001-ZXSDR R8852 (V1.0) Product Description - 891963
30 pages
SJ-20100211152857-002-ZXWN MSCS (V3.09.21) MSC Server Technical Description
No ratings yet
SJ-20100211152857-002-ZXWN MSCS (V3.09.21) MSC Server Technical Description
336 pages
IMS-ZXUN CSCF-A-EN-Maintenance & Troubleshooting-System Maintenance-Routine Operations Guide-1-TM-201010-73
No ratings yet
IMS-ZXUN CSCF-A-EN-Maintenance & Troubleshooting-System Maintenance-Routine Operations Guide-1-TM-201010-73
73 pages
Presentacion Pgibt
100% (1)
Presentacion Pgibt
140 pages
EDS Technical Reference Guide 9.1
No ratings yet
EDS Technical Reference Guide 9.1
90 pages
SJ-20100511105923-001-ZXSDR BS8900A C100 (HV2.0) Hardware Installation Guide - 448709
No ratings yet
SJ-20100511105923-001-ZXSDR BS8900A C100 (HV2.0) Hardware Installation Guide - 448709
121 pages
RPG 400 User's Guide
No ratings yet
RPG 400 User's Guide
571 pages
MOF Functional Overview 12 NSN
No ratings yet
MOF Functional Overview 12 NSN
25 pages
SJ-20110927150233-015-Unitrans ZXCTN 6200&6300&6220 (V2.00) Feature Configuration Guide (U31 Mode) PDF
100% (3)
SJ-20110927150233-015-Unitrans ZXCTN 6200&6300&6220 (V2.00) Feature Configuration Guide (U31 Mode) PDF
417 pages
SJ-20160328171815-023-ZXUR 9000 UMTS (V4.15.10.20) Calling Trace Operation Guide
No ratings yet
SJ-20160328171815-023-ZXUR 9000 UMTS (V4.15.10.20) Calling Trace Operation Guide
74 pages
SJ-20111107090012-008 ZXR10 M6000 (V1.00.60) Carrier-Class Router Initial Configuration Guide
No ratings yet
SJ-20111107090012-008 ZXR10 M6000 (V1.00.60) Carrier-Class Router Initial Configuration Guide
74 pages
ZTE UMTS UR14 NodeB Uplink Interference Cancellation Feature Guide
No ratings yet
ZTE UMTS UR14 NodeB Uplink Interference Cancellation Feature Guide
32 pages
Reset Password of OMU Portal (Espace VCN3000) - Huawei Enterprise Support Community
No ratings yet
Reset Password of OMU Portal (Espace VCN3000) - Huawei Enterprise Support Community
6 pages
CA Spectrum - 10.2 and 10.2.1 - ENU - Customizing - 20170403 PDF
No ratings yet
CA Spectrum - 10.2 and 10.2.1 - ENU - Customizing - 20170403 PDF
311 pages
ZXG10 IBSC (V6.10) Technical Manual
No ratings yet
ZXG10 IBSC (V6.10) Technical Manual
87 pages
BSC6900 GU V900R015C00SPC529 Used Reserved Parameter List
No ratings yet
BSC6900 GU V900R015C00SPC529 Used Reserved Parameter List
1,145 pages
HUAWEI USG6000 Series & NGFW Module V100R001 Administrator Guide 04
No ratings yet
HUAWEI USG6000 Series & NGFW Module V100R001 Administrator Guide 04
4,895 pages
ZXUN USPP (V4.13.20) Universal Subscriber Profile Platform Parts Replacement Guide
100% (1)
ZXUN USPP (V4.13.20) Universal Subscriber Profile Platform Parts Replacement Guide
84 pages
Netman 4000 OMC-A: Network Management System System Overview
No ratings yet
Netman 4000 OMC-A: Network Management System System Overview
35 pages
ZTE WCDMA Radio Parameter Planning Technical Guide
100% (3)
ZTE WCDMA Radio Parameter Planning Technical Guide
19 pages
HUAWEI USG6600 Series Next-Generation Firewall Brochure
No ratings yet
HUAWEI USG6600 Series Next-Generation Firewall Brochure
2 pages
TMF642 Alarm Management API User Guide v4.0.0
No ratings yet
TMF642 Alarm Management API User Guide v4.0.0
134 pages
04-BSC6900V900R011 GO Data Configuration ISSUE2.0-20100506-B
100% (1)
04-BSC6900V900R011 GO Data Configuration ISSUE2.0-20100506-B
61 pages
SmartAX MA5300
No ratings yet
SmartAX MA5300
501 pages
Automatic OMCH Establishment (SRAN9.0 - 01) PDF
No ratings yet
Automatic OMCH Establishment (SRAN9.0 - 01) PDF
131 pages
Board Manual PDF
No ratings yet
Board Manual PDF
395 pages
zxr10 m6000 PDF
No ratings yet
zxr10 m6000 PDF
57 pages
SJ-20120319104909-013-ZXUR 9000 UMTS (V4.11.20) MML Command Reference
No ratings yet
SJ-20120319104909-013-ZXUR 9000 UMTS (V4.11.20) MML Command Reference
463 pages
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
Installing SQL Server 2012 Step by Step
From Everand
Installing SQL Server 2012 Step by Step
Stephen Thomas
No ratings yet
DeviceNet The Ultimate Step-By-Step Guide
From Everand
DeviceNet The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
Siebel Insurance 8 Guide
From Everand
Siebel Insurance 8 Guide
Mohammed Azizuddin Aamer
4/5 (2)
ZXDSL 931wii Vdsl2 Manual
No ratings yet
ZXDSL 931wii Vdsl2 Manual
138 pages
SJ-20120319104909-009-ZXUR 9000 UMTS (V4.11.20) Radio Parameter Constraints Reference
No ratings yet
SJ-20120319104909-009-ZXUR 9000 UMTS (V4.11.20) Radio Parameter Constraints Reference
123 pages
SJ-20101126132257-010-ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Alarm and Notification Message Reference
No ratings yet
SJ-20101126132257-010-ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Alarm and Notification Message Reference
143 pages
SJ-20130416095742-019-ZXUN ICX (MSCS) (V4.13.10) MSC Server Troubleshooting Guide - 504807
No ratings yet
SJ-20130416095742-019-ZXUN ICX (MSCS) (V4.13.10) MSC Server Troubleshooting Guide - 504807
65 pages
ZTE Hardware Description
100% (1)
ZTE Hardware Description
124 pages
ZXONE 5800 Maintenance Guide
No ratings yet
ZXONE 5800 Maintenance Guide
89 pages
SJ-20120217144018-002-ZXSS10 B200 (V2.00.61) Broadband Gateway Product Description
No ratings yet
SJ-20120217144018-002-ZXSS10 B200 (V2.00.61) Broadband Gateway Product Description
69 pages
SJ-20210330092309-004-ZXMW (V3.05.04) Alarm and Notification Handling Reference
No ratings yet
SJ-20210330092309-004-ZXMW (V3.05.04) Alarm and Notification Handling Reference
1,043 pages
SNMP Software User Manual
No ratings yet
SNMP Software User Manual
40 pages
Open Source Software Declaration
No ratings yet
Open Source Software Declaration
105 pages
Pinocchio
No ratings yet
Pinocchio
169 pages
Software Installation Guide
No ratings yet
Software Installation Guide
306 pages
ZTE Hardware Description
No ratings yet
ZTE Hardware Description
182 pages
Nddi2 LS - GS - 3ba23173
No ratings yet
Nddi2 LS - GS - 3ba23173
27 pages
TNMS Imn
No ratings yet
TNMS Imn
136 pages
PCM2 - 3ba23064
No ratings yet
PCM2 - 3ba23064
20 pages
Intel® Desktop Board D975XBX2: Technical Product Specification
No ratings yet
Intel® Desktop Board D975XBX2: Technical Product Specification
106 pages
Business and Transfer Reviewer
No ratings yet
Business and Transfer Reviewer
11 pages
Assessment and Legal Education: What Is Assessment, and What The # Does It Have To Do With The Challenges Facing Legal Education?
No ratings yet
Assessment and Legal Education: What Is Assessment, and What The # Does It Have To Do With The Challenges Facing Legal Education?
26 pages
Accountancy Ii: Definition of The Statement of Financial Position and Its Elements
No ratings yet
Accountancy Ii: Definition of The Statement of Financial Position and Its Elements
40 pages
Circular to Clients -Rbz Foreign Exchange Directive Fxd No. 1-2025
No ratings yet
Circular to Clients -Rbz Foreign Exchange Directive Fxd No. 1-2025
2 pages
Important Banking Awareness Questions
No ratings yet
Important Banking Awareness Questions
9 pages
1 Chronicles 13:8-10
No ratings yet
1 Chronicles 13:8-10
3 pages
State Wise Quarantine Regulation
No ratings yet
State Wise Quarantine Regulation
15 pages
Tủ từ vựng 9+ (Tặng tập thể nhóm)
No ratings yet
Tủ từ vựng 9+ (Tặng tập thể nhóm)
8 pages
03 - Stephen D. White - The Feudal Revolution. Debate II (Past and Present, 152, 1996)
No ratings yet
03 - Stephen D. White - The Feudal Revolution. Debate II (Past and Present, 152, 1996)
19 pages
Guide Legal Dictionaries and Thesauri
No ratings yet
Guide Legal Dictionaries and Thesauri
5 pages
Oceanic Wireless Network, Inc. V. Cir G.R. NO. 148380 December 9, 2005 Facts
No ratings yet
Oceanic Wireless Network, Inc. V. Cir G.R. NO. 148380 December 9, 2005 Facts
2 pages
Payslip PT Total English Learning Green Lake Des 2022 Fajar Kurniawan
No ratings yet
Payslip PT Total English Learning Green Lake Des 2022 Fajar Kurniawan
1 page
The Art of Personal Finance Budget Project Worksheet - Income
No ratings yet
The Art of Personal Finance Budget Project Worksheet - Income
7 pages
2022 Ballb End Term Sem 5-2
No ratings yet
2022 Ballb End Term Sem 5-2
8 pages
Saudi Arabia Tax Rules For Regional Headquarters.
No ratings yet
Saudi Arabia Tax Rules For Regional Headquarters.
7 pages
Account Details: Invoice/Statement Date
No ratings yet
Account Details: Invoice/Statement Date
3 pages
Arcrete SP157: High-Range Water Reduce For Ultimate Early and Final Strengths
No ratings yet
Arcrete SP157: High-Range Water Reduce For Ultimate Early and Final Strengths
2 pages
HCL 37 %
No ratings yet
HCL 37 %
7 pages
Environmental Impact Assessment (Eia) Studies For Coal/Lignite Based Power Plants Status As On February, 2012
No ratings yet
Environmental Impact Assessment (Eia) Studies For Coal/Lignite Based Power Plants Status As On February, 2012
4 pages
Delgado & Stefancic - Critical Race Theory & Criminal Justice-3
No ratings yet
Delgado & Stefancic - Critical Race Theory & Criminal Justice-3
14 pages
PERCENTAGE & VAT TAX
No ratings yet
PERCENTAGE & VAT TAX
6 pages
Geneva Accords
No ratings yet
Geneva Accords
13 pages
New Form 6
No ratings yet
New Form 6
4 pages
F To G: 1 To 2: Spreadsheets To BS 8110 & EC2
No ratings yet
F To G: 1 To 2: Spreadsheets To BS 8110 & EC2
5 pages
Female Foreign National Sues UC-Berkeley For Due Process Violations in Title IX Case
No ratings yet
Female Foreign National Sues UC-Berkeley For Due Process Violations in Title IX Case
92 pages
Declaration and Attestation: Last Name First Name Middle Name (Mm/dd/yy)
No ratings yet
Declaration and Attestation: Last Name First Name Middle Name (Mm/dd/yy)
1 page
Ebook Ebook PDF Criminal Justice Mainstream and Crosscurrents 3Rd Edition All Chapter PDF Docx Kindle
100% (40)
Ebook Ebook PDF Criminal Justice Mainstream and Crosscurrents 3Rd Edition All Chapter PDF Docx Kindle
41 pages