SJ-20140122171518-015-ZXUN CSCF (V4.13.10) Call Session Control Function Alarm Handling

ZXUN CSCF
Call Session Control Function

Alarm Handling
Version: V4.13.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://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-02-25 First Edtion
Serial Number: SJ-20140122171518-015
Publishing Date: 2014-02-25 (R1.0)
SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview of Alarms and Notifications .................................... 1-1
1.1 Alarm Information............................................................................................... 1-1
1.2 Probable Cause ................................................................................................. 1-3
1.3 Impact on the System ........................................................................................ 1-3
1.4 Troubleshooting Suggestion................................................................................ 1-3
Chapter 2 Alarm Message Handling ......................................................... 2-1

2.1 170 The switch board occurred loopback port ...................................................... 2-5
2.2 256 OMC port's link is down................................................................................ 2-6
2.3 2560 CPU utilization over alarm limit ................................................................... 2-8
2.4 3584 Memory insufficient alarm ........................................................................... 2-9
2.5 5122 Loss of Active/standby communication link ................................................ 2-10
2.6 5123 The configuration is not supported .............................................................2-11
2.7 5200 Board configuration information is not compatible....................................... 2-14
2.8 5382 Environment monitor board communication is abnormal ............................. 2-15
2.9 5407 The board is power off.............................................................................. 2-16
2.10 5632 The hard disk used-rate is over threshold ................................................ 2-17
2.11 5633 File system is abnormal .......................................................................... 2-18
2.12 5634 The hard disk on board gets IO error ....................................................... 2-19
2.13 5673 The setting of the dial switch is changed.................................................. 2-20
2.14 5772 Board device fault .................................................................................. 2-23
2.15 5760 Ethernet port's link is down ..................................................................... 2-24
2.16 5761 The speed mode of Ethernet port doesn't match with settings ................... 2-26
2.17 5771 The duplex mode of Ethernet port doesn't match with settings .................. 2-27
2.18 5797 The hard disk is abnormal....................................................................... 2-29
2.19 5798 The RAID of hard disks is abnormal ........................................................ 2-32
2.20 5799 Hard disk online ..................................................................................... 2-34
2.21 5800 Hard disk offline ..................................................................................... 2-36
2.22 5801 Memory size is abnormal ........................................................................ 2-39
2.23 5909 Download version failed.......................................................................... 2-39
2.24 7168 Port trunk failed...................................................................................... 2-40
2.25 7172 Port physical state restore ...................................................................... 2-42
2.26 7174 Connect port loopback............................................................................ 2-42

2.27 23050 Fan device absent ................................................................................ 2-43
2.28 23051 Power unit absent ................................................................................ 2-45
2.29 25856 Rack temperature is higher than high threshold...................................... 2-47
2.30 25857 Rack temperature is lower than low threshold ........................................ 2-48
2.31 25858 Room temperature is higher than high threshold .................................... 2-50
2.32 25859 Room temperature is lower than low threshold ....................................... 2-51
2.33 25860 Voltage is higher than high threshold ..................................................... 2-52
2.34 25861 Voltage is lower than low threshold........................................................ 2-54
2.35 25862 Humidity is higher than high threshold ................................................... 2-55
2.36 25863 Humidity is lower than low threshold ...................................................... 2-56
2.37 25865 Rack door access control alarm or other monitor alarm........................... 2-57
2.38 25866 Smoke alarm ....................................................................................... 2-59
2.39 25867 Infrared alarm ...................................................................................... 2-60
2.40 25868 Lightning alarm .................................................................................... 2-61
2.41 25869 Power switch alarm .............................................................................. 2-61
2.42 25870 Electrical source configuration does not according with physical.............. 2-63
2.43 30722 Temperature is lower than lower-critical threshold................................... 2-64
2.44 30723 Temperature is lower than lower-non-recoverable threshold .................... 2-65
2.45 30725 Temperature is higher than upper-critical threshold................................. 2-66
2.46 30726 Temperature is higher than upper-non-recoverable threshold .................. 2-68
2.47 30728 Voltage is lower than lower-critical threshold .......................................... 2-69
2.48 30729 Voltage is lower than lower-non-recoverable threshold............................ 2-72
2.49 30731 Voltage is higher than upper-critical threshold ........................................ 2-75
2.50 30732 Voltage is higher than upper-non-recoverable threshold.......................... 2-78
2.51 30734 Velocity of fan is lower than lower-critical threshold................................. 2-81
2.52 30747 Module/Board device absent ................................................................. 2-83
2.53 30748 Power on failed due to S5 ..................................................................... 2-84
2.54 30808 Processor internal error ........................................................................ 2-84
2.55 30809 Processor thermal trip .......................................................................... 2-85
2.56 8392706 Time synchronization over alarm limit ................................................ 2-87
2.57 8392707 Request SNTP time failed ................................................................. 2-89
2.58 8393985 Control plane communication abnormal between board and its home
module........................................................................................................... 2-90
2.59 8393986 Control plane communication is abnormal between this board and
the active independent board .......................................................................... 2-92
2.60 8393987 Board offline..................................................................................... 2-93
2.61 8393988 Control plane communication abnormal between module and OMP ..... 2-94
2.62 8398848 SCCP subsystem unavailable ........................................................... 2-96
II

2.63 8400384 M3UA office inaccessible .................................................................. 2-97
2.64 8402688 Association congested .....................................................................2-101
2.65 8402690 Association broken ..........................................................................2-103
2.66 8417537 Association path broken...................................................................2-107
2.67 8419073 Bearer network is unavailable...........................................................2-109
2.68 8419074 Bearer network get worse ................................................................ 2-111
2.69 2365980673 Performance QoS Critical Alarm ................................................. 2-113
2.70 2365980674 Performance QoS Major Alarm ................................................... 2-115
2.71 2365980675 Performance QoS Common Alarm .............................................. 2-117
2.72 2365980676 Performance QoS Warning Alarm ............................................... 2-118
2.73 2365980929 Internal Controlled Account Number and Password Will Expire
Soon.............................................................................................................2-120
2.74 2365980930 Internal Controlled Account Number and Password Already
Expired .........................................................................................................2-122
2.75 2365980931 Internal Controlled Account Number and Password Do Not Meet
Requirements................................................................................................2-123
2.76 2365980932 3 Consecutive Wrong Passwords During Login ............................2-125
2.77 2365980934 Interface Inner Control Account Password Will Expire Soon..........2-126
2.78 2365980935 Interface Inner Control Account Password Already Expired...........2-127
2.79 2365980936 Interface Inner Control Account Password Do Not Meet
Requirements................................................................................................2-129
2.80 2365981185 OMM CPU Usage Rate Exceeds Criterion ...................................2-130
2.81 2365981186 OMM Memory Usage Rate Exceeds Criterion ..............................2-133
2.82 2365981187 OMM Hard Disk Usage Rate Exceeds Criterion(Level 1 Alarm) ......2-134
2.86 2365981191 Directory Usage Rate Exceeds Criterion (Level 1 Alarm) ..............2-143
2.90 2365981200 Data File Usage Rate Exceeds Criterion (Level 1 Alarm) ..............2-151
2.94 2365981441 License File Illegal .....................................................................2-155
2.95 2365981443 License File Unavailable.............................................................2-156
2.96 2365981444 Multiple License Files Exist.........................................................2-157
III

2.97 2365981445 Loaded License File Expires .......................................................2-158
2.98 2365981697 Link Broken Between NE and OMM ............................................2-159
2.99 2365981698 Link Broken Between Alarm Box and OMM .................................2-160
2.100 2365981699 OMM change over success.......................................................2-161
2.101 2365981700 Link Broken Between Independent Board and OMM...................2-162
2.102 2365981701 Slave OMM Server Unavailable ................................................2-165
2.103 2365981703 SNMP Configuration Inconsistent with Independent Board..........2-166
2.104 2365981704 Insufficient Space on OMM Hard Disk and Newly Reported Data
Will Be Dropped ............................................................................................2-167
2.105 2365981953 Link Broken Between NTP Server and OMM..............................2-168
2.106 2365981954 Time of NTP Server Unsynchronized.........................................2-170
2.107 2365981955 NTP Clock Offset Over Maximum Threshold ..............................2-171
2.108 2365981956 Synchronize NTP Time Failed...................................................2-172
2.109 2365982209 Automatic Backup Failed ..........................................................2-172
2.110 ALM-2399577346 Unavailable SIP Link ........................................................2-173
2.111 ALM-2399577349 SIP SCTP Association Not Established ..............................2-175
2.112 ALM-2399577351 Adjacent Host Unavailable ................................................2-176
2.113 ALM-2399839489 SIP Socket Error ..............................................................2-177
2.114 ALM-2399734018 DIAMETER Static Link Not Established or Link Broken .......2-179
2.115 ALM-2399734024 DIAMETER Dynamic Link Not Established or Link
Broken ..........................................................................................................2-180
2.116 ALM-2399799297 DIAMETER Protocol Stack Session Resource
Exhausted.....................................................................................................2-182
2.117 ALM-2399799305 DIAMETER Dialog Resource of Application Interface Is
Exhausted.....................................................................................................2-183
2.118 ALM-2399799808 Necessary Data Unavailable to DIAMETER Protocol
Stack ............................................................................................................2-184
2.119 ALM-2399842305 SIP Fails to Obtain Configuration During Power-on.............2-185
2.120 ALM-2399842306 Failed to Power on the SIP Process ..................................2-187
2.121 ALM-3154247681 Failed to Launch the System.............................................2-188
2.122 ALM-3154272256 Overstocking ACR Files....................................................2-189
2.123 ALM-3154272257 Insufficient ACR Storage Space ........................................2-192
2.124 ALM-3154272258 Disk Space for Overstocking ACR Files Reached Limit.......2-195
2.125 ALM-3154272272 Abnormal ACR Files.........................................................2-199
2.126 ALM-3154276352 License Usage Percentage Exceeds Threshold..................2-199
2.127 ALM-3154276353 AAS Statics Failure ..........................................................2-200
2.128 ALM-3154280448 Failed to Output Call History .............................................2-200
2.129 ALM-3154513933 HSS Host Bypassed.........................................................2-201
IV

2.130 ALM-3154513934 AS Host Bypassed ...........................................................2-204
2.131 ALM-3154513935 DNS Host Bypassed.........................................................2-206
2.132 ALM-3154513937 CCF Host Bypassed.........................................................2-208
2.133 ALM-3154513947 Failed to Load Common Upgrade Configuration Data .........2-210
2.134 ALM-3154534400 DNS Link Is Broken .......................................................... 2-211
2.135 ALM-3154776084 Traffic Control ..................................................................2-213
2.136 ALM-3154792450 Add IP Address to Anti-DOS Attack Black List....................2-214
2.137 ALM-3154792452 Add User to Anti-DOS Attack Black List .............................2-216
2.138 ALM-3154513936 DNS Signaling Link Disconnection ....................................2-218
2.139 ALM-3154534658 Charging Module Fails to Register to DIAMETER...............2-220
2.140 ALM-3154534672 CG Does Not Support Local NE DIAMETER Version ..........2-220
2.141 ALM-3154513931 Memory Allocation Failure ................................................2-221
2.142 ALM-3154513932 Data Area Memory Allocation Failure.................................2-222
2.143 ALM-3154513940 Adjacent Host Is Abnormal................................................2-224
2.144 ALM-3154513941 Host Group Quit Normal Status .........................................2-226
2.145 ALM-3154513946 Failed to Load Important Upgrade Configuration Data ........2-227
2.146 ALM-3154534656 Failed to Launch the Charging Module ..............................2-227
2.147 ALM-3154534661 CG Connection Failure .....................................................2-228
2.148 ALM-3154771972 Detect Extra-Long Call .....................................................2-229
2.149 ALM-3154771973 Release Extra-Long Call by Force .....................................2-230
2.150 ALM-3154776086 Exceed License Limit of Concurrent Session or Session
Unrelated Number .........................................................................................2-232
2.151 ALM-3154776107 The Capacity of the Classified Data Area Is Insufficient ......2-233
2.152 ALM-3154796672 Occupancy of Charging Pool Reached Threshold...............2-233
2.153 ALM-3162112257 CPU Load Control Level-1 Alarm.......................................2-235
2.157 ALM-3162116115 User Number Exceeds the License Number Threshold
Level-1..........................................................................................................2-240
2.158 ALM-3162116115 User Number Exceeds the License Number Threshold
Level-2..........................................................................................................2-241
2.159 ALM-3162116138 Data Area Capacity Level-1 Alarm .....................................2-242
2.162 ALM-3162132481 Anti-DOS Attack IP Address Capacity Level-1....................2-246

2.165 ALM-3162132483 Anti-DOS Attack User Capacity Level-1 .............................2-251
Chapter 3 Notification Message Handling................................................ 3-1

3.1 1600 CPU resets on a board in the same shelf..................................................... 3-2
3.2 4418 Logic CPU is power on successfully ............................................................ 3-3
3.3 4419 Logic CPU is power on failed ...................................................................... 3-4
3.4 5189 Board change over notice......................................................................... 3-14
3.5 5448 Environment parameters set fail................................................................ 3-16
3.6 5720 The CDM data was covered ..................................................................... 3-18
3.7 5983 Write back version information .................................................................. 3-18
3.8 5984 Check version information ........................................................................ 3-19
3.9 5985 Synchronize version information ............................................................... 3-20
3.10 6720 Notice of power-on status of C51 board/ Board soft reset.......................... 3-21
3.11 10048 Insufficient memory .............................................................................. 3-22
3.12 18241 TCP connection closed......................................................................... 3-23
3.13 20802 An IP address conflicts with another system on the subnet ..................... 3-25
3.14 20803 A MAC address conflicts with another system on the subnet ................... 3-27
3.15 30820 Memory inform reported by BIOS .......................................................... 3-28
3.16 2365980933 Subscriber Login Notification ....................................................... 3-31
3.17 2365981442 Loaded License File Will Expire ................................................... 3-32
3.18 2365981702 Wrong Independent Board Type................................................... 3-33
3.19 2365982210 Automatic Backup Succeeded ..................................................... 3-34
3.20 ALM-2399577347 SIP Link Blocked ................................................................ 3-35
3.21 ALM-2399577348 SIP Link Unblocked............................................................. 3-36
3.22 ALM-2399577350 Force to Terminated Call for Session-Timer Time Out ............ 3-37
3.23 ALM-2399577352 Dynamic Host with the Same Name Already Exists ............... 3-37
3.24 ALM-2399577353 Static Host with the Same Name Already Exists.................... 3-38
3.25 ALM-2399841026 Load Socket Configuration Fail ............................................ 3-39
3.26 ALM-3154509825 Illegal Registration .............................................................. 3-40
3.27 ALM-3154509826 Illegal Call .......................................................................... 3-42
3.28 ALM-3154509827 Emergency Call .................................................................. 3-43
3.29 ALM-3154509828 HSS/SLF Response Timeout ............................................... 3-44
3.30 ALM-3154509829 Unknown HSS Address ....................................................... 3-45
3.31 ALM-3154509830 Gq/Gq'/Rx Interface Response Timeout................................ 3-47
3.32 ALM-3154509831 E2 Interface Response Timeout ........................................... 3-50
3.33 ALM-3154509832 HSS User Data Exceeds System Capability.......................... 3-52
VI

3.34 ALM-3154509833 Shared iFC Configuration Error ............................................ 3-54
3.35 ALM-3154509834 Data Audit Function Found Exception Data........................... 3-55
3.36 ALM-3154509835 Data Audit Complete ........................................................... 3-56
3.37 ALM-3154509837 Detect Extra-long Call ......................................................... 3-57
3.38 ALM-3154509838 Release Extra-long Call by Force ......................................... 3-58
3.39 ALM-3154509839 Release Call Because of Subscriber Is Deleted..................... 3-60
3.40 ALM-3154509840 Route Reselection After Failure............................................ 3-61
3.41 ALM-3154509841 Default iFC Configuration Error ............................................ 3-62
3.42 ALM-3154513938 Adjacent Host Has Been Set Block....................................... 3-64
3.43 ALM-3154513939 Adjacent Host Has Been Set Unblock................................... 3-65
3.44 ALM-3154513942 Host Group Switches from Redundant Status to Abnormal
Status ............................................................................................................ 3-66
3.45 ALM-3154513943 Host Group Switches from Abnormal Status to Redundant
Status ............................................................................................................ 3-67
3.46 ALM-3154513944 Attribute of Host Group Changed ......................................... 3-68
3.47 ALM-3154513945 Routing Status of Host Changed .......................................... 3-68
3.48 ALM-3154534657 Charging Module Fails to Obtain Configuration ..................... 3-69
Glossary .......................................................................................................... I
VII

This page intentionally left blank.
VIII

About This Manual
Purpose
This manual provides users with operation guides by describing how to handle the alarms
and notifications.
Intended Audience
This manual is intended for:
l Debugging and testing engineers
l Maintenance engineers
l Network monitoring personnel
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
Chapter 1, Overview of Alarms and Describes the classification and concepts of alarms and
Notifications notifications.
Chapter 2, Alarm Message Handling Describes the alarm in details, including the causes, related
information, handling methods, and the consequences.
Chapter 3, Notification Message Describes the notification in details, including causes,

Handling related information, handling methods, and the
consequences.
Related Documentation
The following documentation is related to this manual:
l ZXUN CSCF Call Session Control Function Data Configuration Guide
l ZXUN CSCF Call Session Control Function Alarm Management Operation Guide
Conventions
This manual uses the following conventions:
Typeface Meaning
Italics Variables in commands. It may also refer to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
Constant Text that you type, program codes, filenames, directory names, and function names.
width

Typeface Meaning
[] Optional parameters.
{} Mandatory parameters.
| Separates individual parameters in a series of parameters.
Danger: indicates an imminently hazardous situation. Failure to comply can result in

death or critical injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result in

critical injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.
II

Chapter 1
Overview of Alarms and
Notifications
Fault management is responsible for collecting information of failures and events that occur
during system operation or service processing.
The information, in the form of alarm or notification, is stored in databases or displayed
on real-time basis by a user-oriented fault monitoring platform. Means such as
visual-interface monitor or history information query can be used to view current or
historical system operation and service processing status. Fault management enables
maintenance personnel to troubleshoot and take preventive measures to remove potential
faults and restore system and services as early as possible.
The fault that persists during system operation and affects system reliability and normal
services is referred to as an alarm. Alarm usually lasts until fault is cleared.
Due to its possible impact on normal system operation, alarm requires timely
troubleshooting in which alarm cause is identified, and the fault is located and handled.
Table of Contents
Alarm Information .......................................................................................................1-1
Probable Cause .........................................................................................................1-3
Impact on the System ................................................................................................1-3
Troubleshooting Suggestion .......................................................................................1-3
1.1 Alarm Information

Alarm ID
An alarm ID is the identifier which differentiates alarms.
An alarm ID is defined by a 32-bit field indicating the specific code value.
Alarm Name
An alarm name reflects such contents as fault causes and the fault phenomenon in a
simple and straightforward way.
Severity
There are four alarm levels, which are indicated in descending order of severity.
l Critical
1-1

ZXUN CSCF Alarm Handling
A critical alarm causes system breakdown and service interruption. It requires

immediate troubleshooting.
l Major
A major alarm significantly affects system operation or weakens network service

capability. It requires troubleshooting as soon as possible.
l Minor
A minor alarm affects system operation and network service capability in an
insignificant way. It requires timely troubleshooting to avoid severity escalation.
l Warning
A warning brings a potential hazard to system operations and the network service
capability. It requires troubleshooting at an appropriate time to avoid severity
escalation.
The degree of impact as described in the definition of alarm severity refers to the impact of
a single index, such as reliability and security. Once the impact on any of the index reaches
the specified threshold, the severity level of the alarm can be roughly determined. If an
alarm has an impact on multiple indices, alarm severity should be escalated accordingly.
Note:
l The alarm severity can be modified in the NetNumenM30 NM system if necessary.
l In general, the default alarm severity is reasonably set. Do not modify it without
permission.
In addition, the severity of a few alarms changes. You can define the severity of such
alarms.
Alarm Type
Alarms are classified into six types according to the alarm triggering condition and its
system impact.
l Communication alarm: related with information transmission (ITU-T Recommendation
X.733).
l Processing error alarm: related with software or process faults (ITU-T
Recommendation X.733).
l QoS alarm: related with degradation of QoS (ITU-T Recommendation X.733).
l Equipment alarm: related with the hardware of the equipment.
l Environment alarm: related with the environment where the equipment is located
(ITU-T Recommendation X.733).
1-2

Chapter 1 Overview of Alarms and Notifications
1.2 Probable Cause

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

The impact on the system refers to the impact that the alarm incurs on system or services.
1.4 Troubleshooting Suggestion

Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.
l After recording the fault phenomenon, O&M personnel may handle the fault step by
step as described in the Handling Suggestion Section of this manual. If the fault is
cleared (alarm restored) at any handling step, terminate the handling process. If the
fault is not cleared, go ahead to the next handling step.
l If the fault cannot be cleared, contact the ZTE technical support as soon as possible.
1-3

1-4

Chapter 2
Alarm Message Handling
Table of Contents
170 The switch board occurred loopback port ............................................................2-5
256 OMC port's link is down .......................................................................................2-6
2560 CPU utilization over alarm limit ..........................................................................2-8
3584 Memory insufficient alarm ..................................................................................2-9
5122 Loss of Active/standby communication link ......................................................2-10
5123 The configuration is not supported...................................................................2-11
5200 Board configuration information is not compatible ............................................2-14
5382 Environment monitor board communication is abnormal ..................................2-15
5407 The board is power off .....................................................................................2-16
5632 The hard disk used-rate is over threshold ........................................................2-17
5633 File system is abnormal ...................................................................................2-18
5634 The hard disk on board gets IO error ...............................................................2-19
5673 The setting of the dial switch is changed..........................................................2-20
5772 Board device fault............................................................................................2-23
5760 Ethernet port's link is down ..............................................................................2-24
5761 The speed mode of Ethernet port doesn't match with settings .........................2-26
5771 The duplex mode of Ethernet port doesn't match with settings.........................2-27
5797 The hard disk is abnormal ...............................................................................2-29
5798 The RAID of hard disks is abnormal.................................................................2-32
5799 Hard disk online...............................................................................................2-34
5800 Hard disk offline...............................................................................................2-36
5801 Memory size is abnormal.................................................................................2-39
5909 Download version failed...................................................................................2-39
7168 Port trunk failed ...............................................................................................2-40
7172 Port physical state restore ...............................................................................2-42
7174 Connect port loopback.....................................................................................2-42
23050 Fan device absent .........................................................................................2-43
23051 Power unit absent..........................................................................................2-45
25856 Rack temperature is higher than high threshold .............................................2-47
25857 Rack temperature is lower than low threshold................................................2-48
25858 Room temperature is higher than high threshold............................................2-50
25859 Room temperature is lower than low threshold ..............................................2-51
25860 Voltage is higher than high threshold .............................................................2-52
25861 Voltage is lower than low threshold ................................................................2-54
25862 Humidity is higher than high threshold ...........................................................2-55
25863 Humidity is lower than low threshold ..............................................................2-56
25865 Rack door access control alarm or other monitor alarm .................................2-57
2-1

25866 Smoke alarm .................................................................................................2-59

25867 Infrared alarm ................................................................................................2-60
25868 Lightning alarm ..............................................................................................2-61
25869 Power switch alarm .......................................................................................2-61
25870 Electrical source configuration does not according with physical....................2-63
30722 Temperature is lower than lower-critical threshold..........................................2-64
30723 Temperature is lower than lower-non-recoverable threshold ..........................2-65
30725 Temperature is higher than upper-critical threshold........................................2-66
30726 Temperature is higher than upper-non-recoverable threshold ........................2-68
30728 Voltage is lower than lower-critical threshold..................................................2-69
30729 Voltage is lower than lower-non-recoverable threshold ..................................2-72
30731 Voltage is higher than upper-critical threshold................................................2-75
30732 Voltage is higher than upper-non-recoverable threshold ................................2-78
30734 Velocity of fan is lower than lower-critical threshold........................................2-81
30747 Module/Board device absent .........................................................................2-83
30748 Power on failed due to S5..............................................................................2-84
30808 Processor internal error .................................................................................2-84
30809 Processor thermal trip....................................................................................2-85
8392706 Time synchronization over alarm limit ........................................................2-87
8392707 Request SNTP time failed..........................................................................2-89
8393985 Control plane communication abnormal between board and its home
module .....................................................................................................................2-90
8393986 Control plane communication is abnormal between this board and the
active independent board .........................................................................................2-92
8393987 Board offline ..............................................................................................2-93
8393988 Control plane communication abnormal between module and OMP...........2-94
8398848 SCCP subsystem unavailable....................................................................2-96
8400384 M3UA office inaccessible ...........................................................................2-97
8402688 Association congested .............................................................................2-101
8402690 Association broken ..................................................................................2-103
8417537 Association path broken...........................................................................2-107
8419073 Bearer network is unavailable ..................................................................2-109
8419074 Bearer network get worse ........................................................................ 2-111
2365980673 Performance QoS Critical Alarm ........................................................ 2-113
2365980674 Performance QoS Major Alarm .......................................................... 2-115
2365980675 Performance QoS Common Alarm..................................................... 2-117
2365980676 Performance QoS Warning Alarm ...................................................... 2-118
2365980929 Internal Controlled Account Number and Password Will Expire Soon .2-120
2365980930 Internal Controlled Account Number and Password Already Expired..2-122
2365980931 Internal Controlled Account Number and Password Do Not Meet
Requirements.........................................................................................................2-123
2365980932 3 Consecutive Wrong Passwords During Login..................................2-125
2365980934 Interface Inner Control Account Password Will Expire Soon...............2-126
2365980935 Interface Inner Control Account Password Already Expired................2-127
2-2

Chapter 2 Alarm Message Handling
2365980936 Interface Inner Control Account Password Do Not Meet

Requirements.........................................................................................................2-129
2365981185 OMM CPU Usage Rate Exceeds Criterion .........................................2-130
2365981186 OMM Memory Usage Rate Exceeds Criterion ....................................2-133
2365981187 OMM Hard Disk Usage Rate Exceeds Criterion(Level 1 Alarm)..........2-134
2365981191 Directory Usage Rate Exceeds Criterion (Level 1 Alarm)....................2-143
2365981200 Data File Usage Rate Exceeds Criterion (Level 1 Alarm) ...................2-151
2365981441 License File Illegal .............................................................................2-155
2365981443 License File Unavailable ....................................................................2-156
2365981444 Multiple License Files Exist ................................................................2-157
2365981445 Loaded License File Expires ..............................................................2-158
2365981697 Link Broken Between NE and OMM...................................................2-159
2365981698 Link Broken Between Alarm Box and OMM........................................2-160
2365981699 OMM change over success................................................................2-161
2365981700 Link Broken Between Independent Board and OMM ..........................2-162
2365981701 Slave OMM Server Unavailable .........................................................2-165
2365981703 SNMP Configuration Inconsistent with Independent Board.................2-166
2365981704 Insufficient Space on OMM Hard Disk and Newly Reported Data Will
Be Dropped............................................................................................................2-167
2365981953 Link Broken Between NTP Server and OMM .....................................2-168
2365981954 Time of NTP Server Unsynchronized .................................................2-170
2365981955 NTP Clock Offset Over Maximum Threshold ......................................2-171
2365981956 Synchronize NTP Time Failed............................................................2-172
2365982209 Automatic Backup Failed ...................................................................2-172
ALM-2399577346 Unavailable SIP Link .................................................................2-173
ALM-2399577349 SIP SCTP Association Not Established .....................................2-175
ALM-2399577351 Adjacent Host Unavailable.........................................................2-176
ALM-2399839489 SIP Socket Error........................................................................2-177
ALM-2399734018 DIAMETER Static Link Not Established or Link Broken .............2-179
ALM-2399734024 DIAMETER Dynamic Link Not Established or Link Broken.........2-180
ALM-2399799297 DIAMETER Protocol Stack Session Resource Exhausted .........2-182
ALM-2399799305 DIAMETER Dialog Resource of Application Interface Is
Exhausted ..............................................................................................................2-183
ALM-2399799808 Necessary Data Unavailable to DIAMETER Protocol Stack .......2-184
ALM-2399842305 SIP Fails to Obtain Configuration During Power-on....................2-185
ALM-2399842306 Failed to Power on the SIP Process ..........................................2-187
2-3

ALM-3154247681 Failed to Launch the System .....................................................2-188

ALM-3154272256 Overstocking ACR Files.............................................................2-189
ALM-3154272257 Insufficient ACR Storage Space.................................................2-192
ALM-3154272258 Disk Space for Overstocking ACR Files Reached Limit .............2-195
ALM-3154272272 Abnormal ACR Files ..................................................................2-199
ALM-3154276352 License Usage Percentage Exceeds Threshold.........................2-199
ALM-3154276353 AAS Statics Failure....................................................................2-200
ALM-3154280448 Failed to Output Call History ......................................................2-200
ALM-3154513933 HSS Host Bypassed ..................................................................2-201
ALM-3154513934 AS Host Bypassed.....................................................................2-204
ALM-3154513935 DNS Host Bypassed..................................................................2-206
ALM-3154513937 CCF Host Bypassed ..................................................................2-208
ALM-3154513947 Failed to Load Common Upgrade Configuration Data................2-210
ALM-3154534400 DNS Link Is Broken ................................................................... 2-211
ALM-3154776084 Traffic Control ............................................................................2-213
ALM-3154792450 Add IP Address to Anti-DOS Attack Black List ...........................2-214
ALM-3154792452 Add User to Anti-DOS Attack Black List.....................................2-216
ALM-3154513936 DNS Signaling Link Disconnection.............................................2-218
ALM-3154534658 Charging Module Fails to Register to DIAMETER......................2-220
ALM-3154534672 CG Does Not Support Local NE DIAMETER Version.................2-220
ALM-3154513931 Memory Allocation Failure .........................................................2-221
ALM-3154513932 Data Area Memory Allocation Failure.........................................2-222
ALM-3154513940 Adjacent Host Is Abnormal ........................................................2-224
ALM-3154513941 Host Group Quit Normal Status .................................................2-226
ALM-3154513946 Failed to Load Important Upgrade Configuration Data ...............2-227
ALM-3154534656 Failed to Launch the Charging Module ......................................2-227
ALM-3154534661 CG Connection Failure ..............................................................2-228
ALM-3154771972 Detect Extra-Long Call ..............................................................2-229
ALM-3154771973 Release Extra-Long Call by Force .............................................2-230
ALM-3154776086 Exceed License Limit of Concurrent Session or Session
Unrelated Number ..................................................................................................2-232
ALM-3154776107 The Capacity of the Classified Data Area Is Insufficient .............2-233
ALM-3154796672 Occupancy of Charging Pool Reached Threshold......................2-233
ALM-3162112257 CPU Load Control Level-1 Alarm ...............................................2-235
ALM-3162116115 User Number Exceeds the License Number Threshold Level-1..2-240
ALM-3162116115 User Number Exceeds the License Number Threshold Level-2..2-241
ALM-3162116138 Data Area Capacity Level-1 Alarm .............................................2-242
ALM-3162132481 Anti-DOS Attack IP Address Capacity Level-1 ...........................2-246
2-4

ALM-3162132483 Anti-DOS Attack User Capacity Level-1.....................................2-251

2.1 170 The switch board occurred loopback port

Alarm Description
This alarm is generated when the local port receives loop messages sent from its own.
Alarm Information
l Alarm Severity: Major
l Alarm Type: Equipment Alarm
l Auto Clear: Yes
Alarm Parameters
Parameter Description
Port ID Number of the physical interface that causes the

alarm.
Port type Indicates whether the interface that causes the

alarm is an intra-shelf interface or an inter-shelf
interface. The options are as follows:
l Out shelf
l In shelf
Slot number or cascading port number Slot number or cascading port number of the port
that causes the alarm.
Active/standby switching board Master/slave status of the board that causes the
alarm. The options are as follows:
l Master board
l Slave board
Alarm Cause
1. The cascading network in the shelf has a loop.
2. The switch that is connected to the debugging interface of this board has a loop.
3. The internal switching network of the shelf corresponding to the board has a loop.
Impact
This port will be blocked by the system automatically, messages on the port will be
discarded, and services may be interrupted.
2-5

Action
1. Check whether "Port type" in alarm detailed information is set to "In shelf".
l Yes -> Step 8.
l No -> Step 2.
2. Check whether the debug port on the switching board is plugged with a network cable.
The location of the debug port is as follows:
For SWBB1, it is the ETH-DBG interface on the panel or the 13th interface on the rear
board.
l Yes -> Step 3.
l No -> Step 6.
3. Remove the network cable, wait for two minutes, and then check whether the alarm is
cleared.
l Yes -> Step 4.
l No -> Step 6.
4. Replug the network cable to the debug port on the switching board. Contact the
maintenance personnel of the peer end to check whether the peer device has related
loop alarms.
l Yes -> Step 5.
l No -> Step 8.
5. Ask the maintenance personnel of the peer end to handle the faults, and check whether
the alarm is cleared.
l Yes -> End.
l No -> Step 8.
6. Replug the network cable to the debug port on the switching board. Check whether
the switching boards between shelves are connected as required.
l Yes -> Step 8.
l No -> Step 7.
7. Connect the cables as required, wait for two minutes, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 8.
8. Contact ZTE technical support.
2.2 256 OMC port's link is down

Alarm Description
This alarm is generated when the board detects that the link of the OMC port is
disconnected.
Alarm Information
l Alarm Severity: Warning
2-6

l Auto Clear: Yes
Alarm Cause
1. The OMC network interface is not connected or the cable connection of the OMC
network interface is incorrect.
2. The OMC network interface of the board is faulty.
3. The peer port is faulty.
4. The switching boards in the same shelf of the board are faulty.
Impact
1. If the board is in active status, the network management cannot manage the NE.
2. If the board is in standby status, this alarm has no influence on the system, but the
reliability of the system is reduced.
Action
1. Run the SET EOMMINTF command to check whether the OMM Attribute parameter
is set to External (OUTER).
l Yes -> Step 2.
l No -> Step 3.
2. Check whether the cable connection of the OMC port corresponding to the faulty board
is abnormal.
l Yes -> Step 4.
l No -> Step 6.
3. If the OMM Attribute parameter of the CMM module in the same shelf is set to
OMM_INNER_FABRIC, check whether the media plane switching board in the same
shelf of the rack operates improperly. If the OMM Attribute parameter of the CMM
module in the same shelf is set to OMM_INNER_BASE, check whether the control
plane switching board in the same shelf of the rack operates improperly.
l Yes -> Step 5.
l No -> Step 8.
4. Replace the cable, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
5. Handle the fault related to the switching board, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
6. Check whether the peer device connected to the port is normal.
l Yes -> Step 8.
l No -> Step 7.
7. Solve the fault of the peer device, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 8.
2-7

2.3 2560 CPU utilization over alarm limit

Alarm Description
This alarm is generated when the board detects that the CPU occupancy rate exceeds the
alarm threshold (by running the SHOW CPUTHR command).
Alarm Information
l Alarm Type: Processing Error Alarm
l Auto Clear: Yes
Alarm Parameters
CPU usage Indicates the CPU utilization (percentage).

Average utilization of system-level CPUs.
CPU utilization alarm type Indicates the overload level of the current CPU,
including high threshold alarm and low threshold
l Low limit alarm
l High limit alarm
CPU high threshold High-level overload threshold of the CPU.
CPU low threshold Low-level overload threshold of the CPU.
Process first Name of the process whose CPU occupation rate

is at the first level.
Process second Name of the process whose CPU occupation rate

is at the second level.
Process third Name of the process whose CPU occupation rate

is at the third level.
CPU usage of process first Occupation rate of the process whose CPU
occupation rate is at the first level.
CPU usage of process second Occupation rate of the process whose CPU
occupation rate is at the second level.
CPU usage of process third Occupation rate of the process whose CPU
occupation rate is at the third level.
Alarm Cause
1. The set alarm threshold is too low.
2. Many operations that exhaust lots of time occur concurrently.
3. Scheduled tasks with quantity of traffic are triggered.
2-8

Impact
The system runs slowly, so the system performance is affected.
Action
1. Check whether "Rate Low(%)" and "Rate High(%)" in the alarm information of the faulty
board meet the actual requirements.
l Yes -> Step 3.
l No -> Step 2.
2. In accordance with the physical location of the faulty board, run the SET CPUTHR
command to modify the CPU alarm threshold as required. Check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether there are a lot of subscribers accessing the service.
l Yes -> Step 6.
l No -> Step 4.
4. Check whether files are transmitted between the network management and the NE or
other manual operations are done on the network management.
l Yes -> Step 5.
l No -> Step 6.
5. Stop the file transmission or manual operations, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 6.
2.4 3584 Memory insufficient alarm

Alarm Description
This alarm is generated when the board detects that the memory usage exceeds the set
threshold.
Alarm Information
l Auto Clear: Yes
2-9

Alarm Parameters
Free memory of board (KB) Indicates the free space of the board (KB).
Memory alarm threshold (KB) Threshold for the "Memory insufficient alarm"
alarm (KB).
Alarm Cause
1. The set alarm threshold is too low.
2. Services are busy, so memory usage is high.
3. The board operates improperly.
4. The memory is damaged.
Impact
The system runs slowly, so the system performance is affected.
Action
1. Check whether "Memory alarm threshold (KB)" in alarm detailed information of the
faulty board meets the actual requirements.
l Yes -> Step 3.
l No -> Step 2.
2. In accordance with the physical location of the faulty board, run the SET CPUTHR
command to modify the memory alarm threshold as required. Check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether the traffic reaches the threshold of the network performance planning.
l Yes -> Contact the network optimization department to determine whether it is
necessary to perform network optimization.
l No -> Step 4.
2.5 5122 Loss of Active/standby communication link

Alarm Description
This alarm is generated on both the active and the standby boards respectively if the
communication between the active board and the standby board is abnormal.
Alarm Information
l Alarm Severity: Minor
l Alarm Type: Communication Alarm
l Auto Clear: Yes
2-10

Alarm Parameters
Logic CPU No. Indicates the logical number of the CPU that
causes the alarm.
Alarm Cause
1. The boards are in active and standby configuration, but only the active board is
installed. The standby board is unavailable or fails to be powered on.
2. The switching board on the control plane in the shelf is unavailable or faulty.
Impact
The communication between the active board and the standby board fails, and therefore,
data cannot be synchronized between them. The system reliability is affected.
Action
1. In accordance with the "Rack" number, "Shelf" number, and "Slot number" in alarm
detailed information, if the module information is reported, run the SHOW MODULE
command to query the slot number of the corresponding partner board (backup), if the
unit information is reported, run the SHOW UNIT command to query the slot number
of the corresponding partner board (backup), if the server information is reported, run
the SHOW BKSVR command to query the slot number of the corresponding partner
board (backup), and check whether the partner board has any of the following alarms:
8393985 Control plane communication abnormal between board and its home module
8393988 Control plane communication abnormal between module and OMP
l Yes -> Step 2.
l No -> Step 3.
2. Handle the above alarms, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Replace the faulty board with a new one (Board Replacement), wait for five to ten
minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.6 5123 The configuration is not supported

Alarm Description
This alarm is generated when the board detects that the hardware does not support the
configured parameters.
2-11

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Error type Indicates the error type. That is the detailed causes of the alarm.
The options are as follows:
l There is not this device, The configuration for port type is error.
l This configuration for the port is not support
l This configuration for E1/T1's frame is not support
l This configuration for E1/T1's signal is not support
l This configuration for T1's cable-length is not support
l This configuration for E1/T1's impedance is not support
l This configuration for E1/T1's coding is not support
l The configuration for the port is error
l There is not this optical port
l This configuration for J0 is not supported
l This configuration for S1 is not supported
l This configuration for SF is not supported
l This configuration for SD is not supported
l This configuration for CRC is not supported
l This configuration for loop-clock is not supported
l This configuration for J1 is not supported
l This configuration for C2 is not support
l This configuration for J2 is not support
l This configuration for V5 is not support
l This configuration for clock shelf function is not support
l The configuration Mac Port doesn't exist
l Work mode error
l Speed error
l Duplex error
l Cable error
l Master slave error
l The function type of the port is error
l This configuration for GPS is not support
l This configuration for synchronous Ethernet is not support
l This configuration for T-Net connect is not support
l The EC Sub card doesn't exist
l It is not supported to be configured as master clock shelf
function because there is no clock sub-card on this board.
2-12

l It is not supported to be configured as slave clock shelf function

because there is no clock sub-card on this board.
l It is not supported to be configured as cascade clock shelf
function because there is no clock sub-card on this board.
l Clock reference source does not support "Get from SSM".
l Unidirection mode is not support
l The board backup mode and lads channels between boards
doesn't match
l Flow control is not support
l Packaging cycle of transparent channel is not supported
l The configuration for board system clock source is not
supported
Device type Indicates the device type, including SDH, network interface, and
DSP. The options are as follows:
l Invalid value
l SDH/SONET device
l Device for E1/T1
l MAC port
l FABRIC port
l Rear port
l Front panel port
l EC Sub-card
l Lads channels between boards
l ETFS Sub-card
l Transparent channels
l Virtual external media port
l TDM port
l Ethernet port
l Clock
Primary device number Indicates the index of the primary device, such as the board,
sub-card, and optical port. If the index is 0, this parameter is invalid.
Secondary device number The index of the secondary device in the primary device. In general,
it refers to the DSP and the trunk.
Alarm Cause
1. The configuration is incorrect.
2. The hardware type is incorrect.
Impact
Some functions of the board are abnormal.
2-13

Action
Contact ZTE technical support.
2.7 5200 Board configuration information is not

compatible
Alarm Description
This alarm is generated if the system detects that the physical board type configured in
the database is different from the real board type, and they are not compatible with each
other.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Board configuration information is compatible or Indicates whether the compatibility is configured

not for the board that causes the alarm.
Configured board type Indicates the configuration type of the faulty

board.
Physical board type Indicates the physical type of the board that
causes the alarm.
Alarm Cause
1. The physical board type is configured incorrectly.
2. The slot is not installed with a correct board.
Impact
The board fails to operate properly.
Action
1. Check whether the board type is configured as required through the rack diagram.
l Yes -> Step 3.
l No -> Step 2.
2. Run the ADD MODULE, ADD UNIT, or ADD BKSVR command to configure the
physical board correctly as required, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2-14

3. Replace the faulty board with a new one (Board Replacement) as required, and check
whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.8 5382 Environment monitor board communication

is abnormal
Alarm Description
This alarm is generated if the CMM detects that the communication with the environment
monitoring board is abnormal.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Rack number Indicates the rack number of the environment

monitoring board that causes the alarm.
Alarm Cause
1. The environment monitoring board is not connected correctly or the DIP is not set
correctly.
2. The environment monitoring board hardware is faulty.
Impact
The power module of the rack and the environment status cannot be monitored.
Action
1. Check whether the "Rack" number in the alarm detailed information is correct.
l Yes -> Step 3.
l No -> Step 2.
2. Run DEL EPDUCFG command. Check whether the alarm is cleared.
l Yes -> End.
l No -> Step 8.
3. Check the cable connection of the environment monitoring board (Environment Monit
oring Cable), and check whether the connection meets the real requirement.
2-15

l Yes -> Step 5.

l No -> Step 4.
4. Connect cables to the environment monitoring board properly, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Check whether the DIP setting of the environment monitoring board is consistent with
the "Rack" number in alarm detailed information.
l Yes -> Step 7.
l No -> Step 6.
6. Modify the DIP setting as required, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
7. Replace the cable of the environment monitoring board, and check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 8.
2.9 5407 The board is power off

Alarm Description
This alarm is generated if the CMM detects that an OMU1, IGUS1/IGSU2, or SWBB1
board is powered off.
Alarm Information
l Auto Clear: Yes
Alarm Cause
1. A board's ejector lever is unlocked.
2. A board is powered off manually.
3. The board hardware is faulty.
Impact
The corresponding board cannot provide services.
Action
1. Run the SHOW CMDLOG command to check whether the board is manually powered
off by any maintenance personnel by checking EMS operation logs.
l Yes -> End.
2-16

l No -> Step 2.
2. Check whether any extractor of the board is open.
l Yes -> Step 3.
l No -> Step 4.
3. Close the board extractors, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
4. Power on the board, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Remove and install the board (Common Operations of Board Replacement), wait for
2 minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
2.10 5632 The hard disk used-rate is over threshold

Alarm Description
This alarm is generated if the board detects that the hard disk usage exceeds the threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Mount directory Mount directory of the used hard disk in the

system.
Hard disk full alarm level The hard disk alarm has three levels. This
parameter indicates the alarm level. The options
are as follows:
l Hard disk full alarm level 1
Hard disk usage (%) Use ratio of a hard disk.
Hard disk usage threshold level 1(%) First alarm threshold for the used ratio of a hard
disk.
2-17

Hard disk usage threshold level 2(%) Second alarm threshold for the used ratio of a
hard disk.
Hard disk usage threshold level 3(%) Third alarm threshold for the used ratio of a hard
disk.
Alarm Cause
1. The hard disk usage is too high.
2. The hard disk usage threshold is too low (in normal cases, it should not be less than
90%).
Impact
Data cannot be saved.
Action
1. Check whether "Hard disk usage (%)" in alarm detailed information exceeds 90%.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET DISKPARA command to modify the threshold of the hard disk, and check
l Yes -> End.
l No -> Step 3.
2.11 5633 File system is abnormal

Alarm Description
This alarm is generated if the board detects a file system fault.
Alarm Information
l Auto Clear: Yes
2-18

Alarm Parameters

system.
Reason of file system error Detailed causes of the file system fault. The
options are as follows:
l Failed to mount
l File system read only
Alarm Cause
1. The hard disk does not exist.
2. The hard disk is not formatted.
3. The file system is abnormal.
Impact
Data cannot be saved or read.
Action
1. Run the RESET NORMAL to reset the board in accordance with the "CPU" number
in alarm detailed information, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Replace the faulty board with a new one (Board Replacement), and check whether
l Yes -> End.
l No -> Step 3.
2.12 5634 The hard disk on board gets IO error

Alarm Description
This alarm is generated if the number of times that an error occurs during hard disk read
and write exceeds the threshold (20/hour).
Alarm Information
l Auto Clear: Yes
2-19

Alarm Parameters

system.
Alarm Cause
The number of times that a file fails to be read from or written to the hard disk exceeds the
threshold.
Impact
Action
1. Check whether the faulty board has any of the following alarms:
5797 The hard disk is abnormal
5798 The RAID of hard disks is abnormal
l Yes -> Step 2.

l No -> Step 3.
2. Handle the above alarms, wait for one hour, and check whether the alarms are cleared.
l Yes -> End.
l No -> Step 3.
3. Replace the hard disk (Replacing a Hard Disk), and check whether the alarm is
cleared.
Caution!
Note that important data must be backed up before the replacement.
l Yes -> End.

l No -> Step 4.
2.13 5673 The setting of the dial switch is changed

Alarm Description
This alarm is generated when the CMM board detects that the DIP of the shelf is changed.
2-20

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Valid bureau number Current bureau number of the system.
Valid rack number Current rack number of the system.
Valid shelf number Current shelf number of the system.
Bureau number in left CDM Bureau number in the left CDM when the alarm
is reported.
Rack number in left CDM Rack number in the left CDM when the alarm is
reported.
Shelf number in left CDM Shelf number in the left CDM when the alarm is
reported.
Bureau number in right CDM Bureau number in the right CDM when the alarm
is reported.
Rack number in right CDM Rack number in the right CDM when the alarm
is reported.
Shelf number in right CDM Shelf number in the right CDM when the alarm
is reported.
Diagnostic mode Diagnostic mode of the current system. The

l Diagnostic mode
l Non-diagnostic mode
Diagnostic mode in left CDM Diagnostic mode in the left CDM when the alarm
is reported. The options are as follows:
l Diagnostic mode
Diagnostic mode in right CDM Diagnostic mode in the right CDM when the alarm
is reported. The options are as follows:
l Diagnostic mode
Alarm Cause
The CDM jumper setting on the CMM board is changed.
2-21

Impact
Other boards in the shelf cannot be powered on successfully after the CMM board is
restarted.
Action
1. Check whether "Bureau number in left CDM", "Bureau number in right CDM", "Rack
number in left CDM", "Rack number in right CDM", "Shelf number in left CDM", "Shelf
number in right CDM", "Diagnostic mode in left CDM", and "Diagnostic mode in right
CDM" in alarm detailed information are the newest values and the left and right settings
correspond to each other.
l Yes -> Step 2.
l No -> Step 4.
2. Run the RESET NORMAL command to reset the CMM board. After the board is
powered on, forcedly reset other boards in the shelf. Check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether the left CDM settings are the newest ones in accordance with alarm
information.
l Yes -> Step 5.
l No -> Step 4.
4. Replace the left CDM with a new one (Replacement of Shelf Parts), and check whether
Note:
Before the replacement, configure the DIP on the left CDM in accordance with the
value range.
l Yes -> End.

l No -> Step 5.
5. Check whether the right CDM settings are the newest ones in accordance with alarm
information.
l Yes -> End.
l No -> Step 6.
6. Replace the right CDM with a new one (Replacement of Shelf Parts), and check
2-22

Note:
Before the replacement, configure the DIP on the right CDM in accordance with the
value range.
l Yes -> End.

l No -> Step 7.
2.14 5772 Board device fault

Alarm Description
This alarm is generated if the board detects a device hardware fault.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Device type Indicates the device type. The options are as

follows:
l FPGA
l VCXO oven
l EPLD
l EC chip
Configured board type Indicates the configured type of the board that
causes the alarm.
Alarm Cause
The board hardware is faulty.
Impact
The board does not operate properly, which may affect the corresponding services.
Action
1. Replace the faulty board with a new one (Board Replacement), and check whether
2-23

l Yes -> End.

l No -> Step 2.
2.15 5760 Ethernet port's link is down

Alarm Description
This alarm is generated when the board detects that the link of the Ethernet port is
disconnected.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Physical Location Physical location of the faulty port on the board.

l Front port
l Rear port
l Back panel base port
l Back panel fabric port
l Virtual port
l Virtual board port
l Panel port
l To slot in the shelf
l To card in the board
l Connection between master and slave
l Manage port
l Switch panel port
l Switch back card port
Port number Index of the port that causes the alarm.
Function type Function type of the Ethernet. That is the purpose

of the Ethernet. The options are as follows:
l Internal media port
l External media port
l OMC port
l Heart beat port
l Control port
2-24

l Master slave port

l Media to control port
l OMC bonding port
l Control bonding port
l Idle port
l Kernel port
l Panel media port
Alarm Cause
1. The local or the peer network port is faulty.
2. The cable connection is incorrect.
3. The network port configuration on the local end is not consistent with that on the peer
end.
Impact
Data cannot be transmitted through the port.
Action
1. Run the SHOW ENETPORTPARA command in accordance with "Physical Location"
and "Port number" in alarm detailed information to check whether the working
parameters ("Negotiate mode", "Speed", "Work mode", "Master", and "Cable") of the
network interface meet the real requirements.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET ENETPORTPARA command to modify the working parameters of the
port as required, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Contact the maintenance personnel of the peer device to check whether the working
parameters of the interconnected port are set as required.
l Yes -> End.
l No -> Step 4.
4. Modify the working parameters of the interconnected port, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Contact the maintenance personnel of the peer device to check whether the
interconnected port is faulty.
l Yes -> Step 6.
l No -> Step 7.
6. Resolve the interconnected port fault, and check whether the alarm is cleared.
l Yes -> End.
2-25

l No -> Step 7.
2.16 5761 The speed mode of Ethernet port doesn't

match with settings
Alarm Description
This alarm is generated if the board detects that the port's auto-negotiated rate is different
from the expected rate.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

l Front port
l Rear port
l Virtual port
l Panel port
l Manage port
l Switch panel port

l OMC port
l Heart beat port
l Control port
2-26

l Master slave port

l OMC bonding port
l Idle port
l Kernel port
l Panel media port
Alarm Cause
The auto-negotiated rate of the Ethernet port is different from the configured expected rate.
Impact
The transmission capability of the Ethernet port may be reduced.
Action
and "Port number" in alarm detailed information to check whether the configured speed
in auto-negotiation mode is consistent with the real speed.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SHOW ENETPORTPARA command to modify the speed of the port, and
check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Replace the cable with an operational one, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.17 5771 The duplex mode of Ethernet port doesn't

match with settings
Alarm Description
This alarm is generated if the board detects that the duplex configuration in
auto-negotiation mode is different from the expected value.
Alarm Information
l Auto Clear: Yes
2-27

Alarm Parameters

l Front port
l Rear port
l Virtual port
l Panel port
l Manage port
l Switch panel port

l OMC port
l Heart beat port
l Control port
l Master slave port
l OMC bonding port
l Idle port
l Kernel port
l Panel media port
Alarm Cause
The duplex configuration in auto-negotiation mode is different from the real configuration.
Impact
The transmission capability of the Ethernet port may be reduced.
2-28

Action
and "Port number" in alarm detailed information to check whether the duplex mode
configuration in auto-negotiation mode is consistent with the real configuration.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET ENETPORTPARA command to modify the duplex configuration of the
port, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Replace the cable with an operational one, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.18 5797 The hard disk is abnormal

Alarm Description
This alarm is generated if the board fails to detect the hard disk or the hard disk SMART
parameter is not correct.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Hard disk location Location of the hard disk that causes the alarm.
l Unknown
l HD1(upper or left)
l HD2(nether or right)
l HD1(upper or left) and HD2(nether or right)
l Disks are not in RAID mode
l Inside disk of CBHD Slot A1
2-29

l Outside disk of CBHD Slot A1

l Inside disk of CBHD Slot B1
l Outside disk of CBHD Slot B1
l Inside disk of CBHD Slot C1
l Outside disk of CBHD Slot C1
l Inside disk of CBHD Slot D1
l Outside disk of CBHD Slot D1
2-30


Reason of hard disk error Detailed causes of the hard disk fault. The
l Hard disk doesn't exist
l Smart is abnormal
l Smart can't be gotten
Disk Media Type Media type of the disk, including HDD and SSD.
l Invalid
l HDD
l SSD
Alarm Cause
1. The hard disk does not exist or cannot be identified.
2. The hard disk SMART is abnormal.
Impact
Action
1. Replace a hard disk (Replacing a Hard Disk) in accordance with the hard disk location
in alarm detailed information, and check whether the alarm is cleared.
Note:
If the hard disk of the board is hot swappable, the status indicator mark of the hard
disk is the same as the location mark of the hard disk in alarm detailed information. If
the hard disk is not hot swappable, the two marks are opposite to each other.
l Yes -> End.

l No -> Step 2.
2-31

2.19 5798 The RAID of hard disks is abnormal

Alarm Description
This alarm is generated if the board detects that the hard disk RAID is in abnormal status.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Reason of RAID error Detailed causes of the RAID fault. The options
are as follows:
l Unknown
l Degraded but not sync
l Failed
l Missing
l Inactive
l Unknown
2-32


2-33

Alarm Cause
1. Two hard disks of the board do not form the RAID.
2. In RAID, one hard disk is unavailable or does not operate properly.
3. Before the RAID is synchronized, the active hard disk becomes faulty or is removed.
4. The RAID information of the SAS controller is abnormal or the RAID information on
the two hard disks is different.
Impact
The hard disk may fail to operate properly.
Action
1. Check whether the hard disk has the following alarm in accordance with "Hard disk
location" in alarm detailed information:
5797 The hard disk is abnormal
l Yes -> Step 2.
l No -> Step 3.
2. Handle the above alarm, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
Note:
If the hard disk of the board is hot swappable, the status indicator mark of the hard
disk is the same as the location mark of the hard disk in alarm detailed information. If
the hard disk is not hot swappable, the two marks are opposite to each other.
2.20 5799 Hard disk online

Alarm Description
This alarm is generated if the board detects that a hard disk is installed.
Alarm Information
l Auto Clear: Yes
2-34

Alarm Parameters
l Unknown
2-35


Alarm Cause
1. A hard disk is installed.
2. The SAS controller is abnormal.
Impact
After a hard disk is installed, the board is restarted. In this period, services on the board
may be affected instantaneously.
Action
1. Wait for five minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2.21 5800 Hard disk offline

Alarm Description
This alarm is generated if the board detects that a hard disk becomes unavailable.
2-36

Alarm Information
l Auto Clear: Yes
Alarm Parameters
l Unknown
2-37


Alarm Cause
1. A hard disk is removed.
2. The SAS controller is abnormal.
Impact
After a hard disk is removed, the board is restarted. In this period, services on the board
may be affected instantaneously.
Action
1. Wait for five minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2-38

2.22 5801 Memory size is abnormal

Alarm Description
This alarm is generated if the board detects that the SPD memory capacity is different from
the available memory in the system.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
SPD memory size(MB) Memory size of SPD (MB).
Operating system memory size (MB) Memory size of the operating system.
Alarm Cause
The memory is faulty or loose.
Impact
If the available memory is insufficient, the board may fail to operate properly.
Action
1. Remove and install or replace the memory bar of the board with a new one (Replacing
a Memory Bar), and power on the board. Wait for three minutes, and check whether
l Yes -> End.
l No -> Step 2.
2. Replace the faulty board with a new one (Board Replacement), and power on the
board. Wait for three minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2.23 5909 Download version failed

Alarm Description
This alarm is generated if the board fails to download the version file from the OMP.
2-39

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Download version reason Causes of the version download failure of the

board. The options are as follows:
l Reason unknown
l Version file download failed
Logical CPU number Logical number of the CPU corresponding to the

alarm.
Alarm Cause
1. The control plane communication of the NE is abnormal.
2. The version file is damaged.
Impact
The board fails to operate properly.
Action
1. Check whether the board has any of the following alarms:
8393986 Control plane communication is abnormal between this board and the active
independent board
l Yes -> Step 2.
l No -> Step 3.
2. Handle the above alarms, wait for five minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2.24 7168 Port trunk failed

Alarm Description
This alarm is generated if the board detects that the internal Ethernet port connection is
not in normal status.
2-40

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Physical port index Number of the port that fails to be negotiated by

the board that causes the alarm.
Port type Type of the abnormal port on the faulty board.

l Unknown port
l Ctrl port
l Media port
l Other shelf
Alarm Cause
1. The Ethernet port hardware is faulty.
2. The switching board of the NE is faulty or unavailable.
3. The pin of the slot in which the board is installed is damaged.
Impact
If the ports of the same type on the board are all faulty, the services on the board are
interrupted.
Action
1. Check whether the alarm is generated on more than two boards in the same shelf in
accordance with the "Rack" number and "Shelf" number in alarm detailed information.
l Yes -> Step 2.
l No -> Step 5.
2. In the rack diagram, check whether the switching board that is in the same shelf as
the faulty board is operating properly.
l Yes -> Step 3.
l No -> Step 4.
3. Wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
4. Resolve the switching board fault, wait for five minutes, and then check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 5.
2-41

2.25 7172 Port physical state restore

Alarm Description
The board checks the STP, VLAN, and TRUNK status of the Ethernet port. This alarm is
generated if any of the status is abnormal.
Alarm Information
l Auto Clear: Yes
Alarm Cause
1. The Ethernet port STP status is abnormal.
2. The Ethernet port's PVLAN or VLAN property is incorrect.
3. The Ethernet port's TRUNK property is incorrect.
Impact
If the port cannot operate properly, the links on the control plane or the media plane are
not stable or even disconnected. Packets therefore get lost and NE services are affected.
Action
1. Wait for 30 seconds, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Run the RESET NORMAL command to reset the board, wait for 20 minutes, and
l Yes -> End.
l No -> Step 3.
3. Replace the faulty board with a new one (Board Replacement), wait for 20 minutes,
and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.26 7174 Connect port loopback

Alarm Description
This alarm is generated if the switching board detects that an interconnected port between
two shelves cannot operate properly because of a loopback on the port.
2-42

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Port number ID of the abnormal port that causes the alarm on

the board.
Port type Location of the abnormal port that causes the

alarm on the board. The options are as follows:
l Panel port
l Rear port
Alarm Cause
1. Two cascade ports in two shelves of the board are interconnected.
2. Two cascade ports in two shelves between the left and right switching boards are
interconnected.
3. A loopback is set on the port.
Impact
The system can shield the storm caused by the loopback. However, if the ports are
connected incorrectly, the communication between different shelves is disconnected,
which results in insufficient bandwidth and service interruption.
Action
1. Remove the fiber or network cable in accordance with the physical location and "Port
number" in alarm detailed information, and check whether the alarm is cleared.
l Yes -> Step 2.
l No -> Step 3.
2. Connect the fiber or network cable as required, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2.27 23050 Fan device absent

Alarm Description
This alarm is generated when the subrack of the fan is not present, or the communication
of the fan or the shelf management board is lost.
2-43

Alarm Information
l Auto Clear: Yes
Alarm Parameters
FRU ID Indicates the field replacement unit uniquely. It starts from 0.
Generic event state General event status, for example, the device is present/ not present. The
(8) options are as follows:
l Device Removed / Device Absent
l Device Inserted / Device Present
Sensor Name Name of the sensor that causes the alarm.
Alarm Cause
1. The subrack of the fan is not present.
2. The connection between the subrack of the fan and the rear board is poor.
3. The communication between the fan and the shelf management board is abnormal.
Impact
1. The subrack of the fan is not present, so the temperature of the board is increased,
and then the temperature of the board is increased. The hardware of the board is
affected, the useful time of the components corresponding to the board is reduced, so
the system cannot operate properly or steadily, and services may be affected.
2. The communication between the subrack of the fan and the shelf management module
is abnormal, so the fan management function is invalid, the speed of the fan is set to
the fast, the system noise is increased, and the useful time of the fan is reduced.
Action
1. Check whether the fan unit is properly installed in accordance with the "Rack" number,
"Shelf" number, and "Slot" number in alarm detailed information.
l Yes -> Step 2.
l No -> Step 3.
2. Remove and install the subrack of the fan in accordance with the "Rack" number,
"Shelf" number, and "Slot" number in alarm detailed information, and check whether
l Yes -> End.
l No -> Step 3.
3. Replace the subrack of the fan with a new one (Replacement of Shelf Parts) in
accordance with the "Rack" number, "Shelf" number, and "Slot" number in alarm
information, and check whether the alarm is cleared.
l Yes -> End.
2-44

l No -> Step 4.
4. Install the subrack of the fan (Replacement of Shelf Parts) in accordance with the
"Rack" number, "Shelf" number, and "Slot" number in alarm information, and check
l Yes -> End.
l No -> Step 5.
5. Run the SHOW INDBOARD command in accordance with the "Rack" number, and
"Shelf" number in alarm detailed information to obtain "Independent Board ID" of the
CMM board, run the SWP INDBORAD command in accordance with "Independent
Board ID" to switch the CMM board, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
6. Run the RESET LEFTINDB/RESET RIGHTINDB command in accordance with
the "Rack" number, "Shelf" number, and "Independent Board ID" in alarm detailed
information to reset the active/standby CMM board at the same time, and check
l Yes -> End.
l No -> Step 7.
2.28 23051 Power unit absent

Alarm Description
This alarm is generated when the power module is not present, or the communication of
the power supply or the shelf management board is lost.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Generic event state (8) General event status, for example, the device is present/ not present.
2-45

Alarm Cause
1. The power module is not present.
2. The connection between the power module and the rear board is poor.
3. The communication between the power supply and the shelf management board is
abnormal.
Impact
1. If one power supply is not present, the power supply of the shelf is not affected.
However, the redundancy and backup capability of the shelf power supply are lost. If
two power supplies are not present, the power supply of the whole shelf is down.
2. The communication between the power supply and the shelf management module are
abnormal, so the power supply management function is invalid, and the system fails
to detect the power supply fault.
Action
1. Check whether the power module is properly installed in accordance with the "Rack"
number, "Shelf" number, and "Slot" number in alarm detailed information.
l Yes -> Step 2.
l No -> Step 3.
2. Remove and install the power supply (Replacement of Shelf Parts) in accordance with
the "Rack" number, "Shelf" number, and "Slot" number in alarm detailed information,
l Yes -> End.
l No -> Step 3.
3. Replace the power supply with a new one (Replacement of Shelf Parts) in accordance
with the "Rack" number, "Shelf" number, and "Slot" number in alarm detailed
information, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
4. Install the power supply (Replacement of Shelf Parts) in accordance with the "Rack"
number, "Shelf" number, and "Slot" number in alarm detailed information, and check
l Yes -> End.
l No -> Step 5.
5. Run the SHOW INDBOARD command in accordance with the "Rack" number, and
"Shelf" number in alarm detailed information to obtain "Independent Board ID" of the
CMM board, run the SWP INDBORAD command in accordance with "Independent
Board ID" to switch the CMM board, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
6. Run the RESET LEFTINDB/RESET RIGHTINDB command in accordance with
the "Rack" number, "Shelf" number, and "Independent Board ID" in alarm detailed
information to reset the active/standby CMM board at the same time, and check
2-46

l Yes -> End.

l No -> Step 7.
2.29 25856 Rack temperature is higher than high

threshold
Alarm Description
This alarm is generated when the temperature of the rack exceeds the high threshold.
For the PDU whose "Volt Type" is 48V, the upper limit voltage range is 36V-72V, and the
recommended value is 57V.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Rack number Number of the rack that causes the alarm.
Temperature index Number of the temperature sensor that causes the alarm. The options
are as follows:
l Alarm is about rack temperature
l Alarm is about room temperature
Ambient temperature Current detected temperature.

detection value(℃)
Alarm Cause
1. The alarm threshold is not properly set.
2. The fan is faulty.
3. The ventilation of both the air intake and air outlet is not smooth.
4. The temperature of the equipment room is too high.
Impact
The real environmental temperature is too high, so the board may operate abnormally, the
components of the board may be damaged, and services may be affected.
2-47

Action
1. Run the SHOW PDU2CMM command in accordance with the "Rack" number in alarm
detailed information to query "CMM ID" of the PDU corresponding to the rack, and run
the SHOW EPDUCFG command in accordance with the "Rack" number and "CMM
ID" to check whether the upper limit temperature of the configured rack is proper
(recommended value is 70).
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command to modify the upper limit temperature of the rack,
and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether the shelf and fan in the rack has any of the following alarms in
accordance with the "Rack" number in alarm detailed information:
30734 Velocity of fan is lower than lower-critical threshold
23050 Fan device absent
l Yes -> Step 4.
l No -> Step 5.
4. Handle the above alarms, wait for 10-15 minutes, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 5.
5. Remove the shelf and the air filter of the cabinet (Replacement of Shelf Parts), and
check whether dust screen of the shelf and the cabinet are blocked.
l Yes -> Step 6.
l No -> Step 7.
6. Clean the dust screen of the shelf and the cabinet, wait for 10-15 minutes, and check
l Yes -> End.
l No -> Step 7.
7. Check the environment temperature of the shelf, ensure that the temperature is in the
range of 0℃ to 40℃, wait for five to ten minutes, and then check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 8.
2.30 25857 Rack temperature is lower than low

threshold
Alarm Description
This alarm is generated when the temperature of the rack is less than the low threshold.
2-48

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Temperature index Number of the temperature sensor that causes

the alarm. The options are as follows:
Ambient temperature detection value(℃) Current detected temperature.
Alarm Cause
2. The temperature of the equipment room is too low.
Impact
The real environmental temperature is too low, so the board may operate abnormally, the
Action
1. Run the SHOW PDU2CMM command in accordance with the "Rack" number in
alarm detailed information to query "CMM ID" of the PDU corresponding to the rack,
and run the SHOW EPDUCFG command in accordance with the "Rack" number and
"CMM ID" to check whether the low limit temperature of the configured rack is proper
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command to modify the low limit temperature of the rack, and
then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Check the environment temperature of the rack, ensure that the temperature is in the
is cleared.
l Yes -> End.
l No -> Step 4.
2-49

2.31 25858 Room temperature is higher than high

threshold
Alarm Description
This alarm is generated when the temperature of the equipment room exceeds the high
threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

Alarm Cause
2. The real temperature of the equipment room is too high.
Impact
The real environmental temperature is too high, so the board may operate abnormally, the
Action
ID" to check whether the configured upper limit temperature of the equipment room is
proper (recommended value is 40).
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command to modify the upper limit temperature of the
equipment room, and then check whether the alarm is cleared.
l Yes -> End.
2-50

l No -> Step 3.
3. Check the environment temperature in the equipment room, ensure that the tempera-
ture is in the range of 0℃ to 40℃, wait for five to ten minutes, and then check whether
l Yes -> End.
l No -> Step 4.
2.32 25859 Room temperature is lower than low

threshold
Alarm Description
This alarm is generated when the temperature of the equipment room is less than the low
threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

Alarm Cause
2. The real temperature of the equipment room is too low.
3. The temperature sensor is not connected.
Impact
The real environmental temperature is too low, so the board may operate abnormally, the
2-51

Action
1. In accordance with the actual situation and the "Rack" number in alarm information,
check whether the room temperature sensor on the rack needs to be connected.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command that controls the PDU of this rack to close the alarm
flag on the temperature and humidity of the equipment room, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 6.
ID" to check whether the configured low limit temperature of the equipment room is
proper (recommended value is 0).
l Yes -> Step 5.
l No -> Step 4.
4. Run the SET EPDUCFG command to modify the low limit temperature of the equipment
room, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Check the environment temperature in the equipment room, ensure that the
temperature is in the range of 0℃ to 40℃, wait for five to ten minutes, and then check
l Yes -> End.
l No -> Step 6.
2.33 25860 Voltage is higher than high threshold

Alarm Description
This alarm is generated when any voltage exceeds the high threshold.
Alarm Information
l Auto Clear: Yes
2-52

Alarm Parameters
Voltage index Number of the circuit that causes the alarm. The
l The first voltage
l The second voltage
l The third voltage
l The fourth voltage
l The fifth voltage
l The sixth voltage
Physical voltage value(V) Current detected voltage.
Alarm Cause
2. The real input voltage is too high.
Impact
The input voltage is too high, so the components of the board may be damaged, the board
cannot operate properly, and services are interrupted.
Action
ID" to check whether the configured upper limit voltage is proper (For the 48V power
supply, the recommended value is 57. For the 60V power supply, the recommended
value is 72).
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command corresponding to the PDU of the rack to modify the
upper limit voltage, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. In accordance with "Voltage index" in alarm detailed information, contact the power
induction department to examine and repair the corresponding power supply. Wait for
three minutes after the voltage is steady, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2-53

2.34 25861 Voltage is lower than low threshold

Alarm Description
This alarm is generated when any voltage is less than the low threshold.
For the PDU whose "Volt Type" is 48V, the lower limit voltage range is 36V-72V, and the
For the PDU whose "Volt Type" is 60V, the lower limit voltage range is 45V-75V, and the
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Voltage index Number of the circuit that causes the alarm. The
l The first voltage
l The second voltage
l The third voltage
l The fourth voltage
l The fifth voltage
l The sixth voltage
Physical voltage value(V) Current detected voltage.
Alarm Cause
2. The real input voltage is too low.
Impact
The board may be power off and services are interrupted.
Action
the SHOW EPDUCFG command in accordance with the "Rack" number and "CMM ID"
to check whether the configured low limit voltage is proper (For the 48V power supply,
2-54

the recommended value is 40. For the 60V power supply, the recommended value is
50).
l Yes -> Step 3.
l No -> Step 2.
low limit voltage, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. In accordance with "Voltage index" in alarm detailed information, contact the power
induction department to examine and repair the corresponding power supply. Wait for
three minutes after the voltage is steady, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.35 25862 Humidity is higher than high threshold

Alarm Description
This alarm is generated when the humidity of the equipment room exceeds the high
threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Ambient humidity detection value(%) Current detected humidity.
Alarm Cause
2. The real humidity of the equipment room is too high.
Impact
The equipment room is humid. If a device operates in the humid equipment room for a
long time, the board may operate improperly, and all service running on the board will be
interrupted.
2-55

Action
the SHOW EPDUCFG command in accordance with the "Rack" number and "CMM ID"
to check whether the configured upper limit humidity of the equipment room is proper
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command corresponding to the PDU of the rack to modify
the upper limit humidity of the equipment room, and then check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 3.
3. Check the actual room humidity, take effective actions if the humidity is too high, and
l Yes -> End.
l No -> Step 4.
2.36 25863 Humidity is lower than low threshold

Alarm Description
This alarm is generated when the humidity of the equipment room is less than the low
threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Ambient humidity detection value (%) Current detected humidity.
Alarm Cause
1. The threshold is not properly set.
2. The real humidity of the equipment room is too low.
3. The equipment humidity sensor is not connected.
2-56

Impact
The environment of the equipment room is dry, so static is easy to occur. If the device or
the antistatic measure is not ready during the operation and maintenance, the board may
be damaged.
Action
check whether the room humidity sensor on the rack needs to be connected.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET EPDUCFG command that controls the PDU of this rack to disable the
alarm flag on the temperature and humidity of the equipment room, and check whether
l Yes -> End.
l No -> Step 6.
ID" to check whether the configured low limit humidity of the equipment room is proper
l Yes -> Step 5.
l No -> Step 4.
low limit humidity of the equipment room, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Check the actual room humidity, take effective actions if the humidity is too high, and
l Yes -> End.
l No -> Step 6.
2.37 25865 Rack door access control alarm or other

monitor alarm
Alarm Description
1. This alarm is generated when the door of the rack is opened.
2. When this device is connected to the third-party's device, the third-party monitoring
alarm is generated.
Alarm Information
2-57


l Auto Clear: Yes
Alarm Parameters
Door index Number of the door that causes the alarm. The
l The first door
l The second door
l The third door
l The fourth door
l The fifth door
l The sixth door
Alarm Cause
1. The door of the rack is open.
2. The third-party device is faulty.
Impact
Safety risks may exist.
Action
check whether the door control or a third-party device needs to be connected.
l Yes -> Step 3.
l No -> Step 2.
2. Close the door control alarm switch for this rack by running the SET EPDUCFG
command that controls the PDU configuration in accordance with the "Rack" number
and "Door index", and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
3. Check whether the rack is properly closed in accordance with the "Rack" number and
"Door index" in alarm detailed information.
l Yes -> Step 5.
l No -> Step 4.
4. Close the door of the rack, and then check whether this alarm is cleared.
l Yes -> End.
l No -> Step 5.
2-58

2.38 25866 Smoke alarm

Alarm Description
This alarm is generated when smoke is in the equipment room.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Alarm Cause
1. The smoke in the equipment room exceeds the standard value.
2. The smoke sensor is faulty.
Impact
Safety risks may exist, and the equipment room is easy to catch fire.
Action
1. In accordance with the actual situation and the "Rack" number in alarm detailed
information, check whether the smoke sensor on the rack needs to be connected.
l Yes -> Step 3.
l No -> Step 2.
flag on the smoke of the rack, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
3. Check whether the equipment room has smoke.
l Yes -> Step 4.
l No -> Step 5.
4. Clean the smoke from the equipment room, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
5. Replace the smoke sensor, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
2-59

2.39 25867 Infrared alarm

Alarm Description
This alarm is generated when infrared-ray is nearby.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Alarm Cause
1. Heat source is around the sensor, including animals and person.
2. The sensor is faulty.
Impact
Safety risks may exist.
Action
1. In accordance with the actual situation and the "Rack" number in alarm detailed
information, check whether the infrared sensor on the rack needs to be connected.
l Yes -> Step 3.
l No -> Step 2.
flag on the infrared sensor of the rack, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
3. Check whether there is any heat source around the infrared sensor.
l Yes -> Step 4.
l No -> Step 5.
4. Remove the heat source, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
2-60

2.40 25868 Lightning alarm

Alarm Description
This alarm is generated when the lightning protection module is faulty.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Alarm Cause
The lightning protection device is faulty.
Impact
The lightning protection system is faulty, maybe the board may be damaged by the
lightning.
Action
1. Replace the lightning protection device and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2.41 25869 Power switch alarm

Alarm Description
This alarm is generated when the air-break switch is off.
Alarm Information
l Auto Clear: Yes
2-61

Alarm Parameters
Air switch index Number of the air switch that causes the alarm.
l The first air switch
l The second air switch
l The third air switch
l The fourth air switch
l The fifth air switch
l The sixth air switch
l The seventh air switch
l The eighth air switch
l The ninth air switch
l The tenth air switch
Air switch group number Number of the air switch group that causes the
l Invalid value
l Air switch group A
l Air switch group B
Alarm Cause
1. The air-break switch is open and the back end requires detecting this air-break switch.
2. The air-break switch is faulty.
Impact
The power supply of the shelf corresponding to the switch may be affected.
Action
1. In accordance with the "Rack" number, "Air switch group number", and "Air switch
index" in alarm detailed information, check whether the corresponding air switch
corresponding to the rack is connected.
l Yes -> Step 3.
l No -> Step 2.
2. In accordance with "Air switch group number" and "Air switch index", run the SET
EPDUCFG command that controls the PDU of the rack to close the detection alarm
flag on the air-break of the rack, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
3. Check whether the corresponding air switch is disconnected.
l Yes -> Step 4.
l No -> Step 5.
2-62

4. Close the air switch, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
2.42 25870 Electrical source configuration does not

according with physical
Alarm Description
This alarm is generated through the CMM board if the PDU detects that the power type
configuration is not consistent with the real type.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Configured voltage type Voltage type configured in the database. The options are
as follows:
l The Voltage is 48V
Physical voltage type Voltage type used at present. The options are as follows:
Alarm Cause
The power type configured in the database is not consistent with the real power type.
Impact
The NE may fail to operate properly.
Action
1. In accordance with the "Rack" number in alarm detailed information, run the SHOW
EPDUCFG command to check whether the "Volt Type" configuration is consistent with
the real requirements.
l Yes -> Step 3.
l No -> Step 2.
2-63

2. Run SET EPDUCFG command. Check whether the alarm is cleared.

l Yes -> End.
l No -> Step 3.
3. Check whether the voltage type of the rack is consistent with the real requirements. (
-48V power is used for normal area, and -60V power is used for special area.)
l Yes -> Step 5.
l No -> Step 4.
4. Replace the power supply for the rack as required. Check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
2.43 30722 Temperature is lower than lower-critical

threshold
Alarm Description
This alarm is generated when the temperature of the components (such as CPU or
memory) corresponding to the board is less than the "lower-critical" threshold. Handle
it as soon as possible.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
current value Current value of the sensor.
Threshold Value Each threshold of the sensor.
Unit Unit of the sensor. For the voltage, the unit is V.
Alarm Cause
The environment temperature of the system is lower than the normal range (lower than
10℃ below zero).
2-64

Impact
When the temperature is less than the "lower-critical" threshold, this fault has poor
influence on the hardware performance of the system. The system cannot operate
properly or unsteadily, and services may be affected.
Action
is cleared.
l Yes -> End.
l No -> Step 2.
2.44 30723 Temperature is lower than

lower-non-recoverable threshold
Alarm Description
memory) corresponding to the board is less than the "lower-non-recoverable" threshold.
Handle it as soon as possible.
Alarm Information
l Alarm Severity: Critical
l Auto Clear: Yes
Alarm Parameters
FRU ID Indicates the field replacement unit uniquely. It

starts from 0.
Alarm Cause
The environment temperature of the system is lower than the normal range (lower than
10℃ below zero).
2-65

Impact
When the temperature is less than the "lower-non-recoverable" threshold, the system
hardware may be damaged, even cannot be recovered, and services are affected.
Action
is cleared.
l Yes -> End.
l No -> Step 2.
2.45 30725 Temperature is higher than upper-critical

threshold
Alarm Description
memory) corresponding to the board is higher than the "upper-critical" threshold. Handle
it as soon as possible.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

starts from 0.
Alarm Cause
1. The environment temperature of the system is higher than the normal range (higher
than 40℃).
2. The fan of the shelf does not operate properly.
3. The air filter is not cleaned for a long time.
2-66

Impact
When the temperature is higher than the "upper-critical" threshold, this fault has poor
influence on the hardware performance of the system. The system cannot operate
properly or unsteadily, and services may be affected. If the alarm exists for a long time,
the corresponding components may be damaged.
Action
1. In accordance with the "Rack" number and "Shelf" number in alarm information,
confirm the shelf of the board with abnormal temperature, and check whether the fan
of this shelf has any of the following alarms:
l Yes -> Step 2.
l No -> Step 3.
2. Handle the above fan alarm. Wait for five to ten minutes, and check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 3.
is cleared.
l Yes -> End.
l No -> Step 4.
4. Check whether the free slot of the shelf is installed with a blank panel. If not, install a
blank panel, wait for five to ten minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
l Yes -> Step 6.
l No -> Step 5.
6. Clean the dust screen of the shelf and the cabinet, wait for five to ten minutes, and
l Yes -> End.
l No -> Step 7.
2-67

2.46 30726 Temperature is higher than

upper-non-recoverable threshold
Alarm Description
memory) corresponding to the board is higher than the "upper-non-recoverable" threshold.
Handle it immediately.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

starts from 0.
Alarm Cause
1. The environment temperature of the system is higher than the normal range (higher
than 40℃).
2. The fan of the shelf does not operate properly.
3. The air filter is not cleaned for a long time.
Impact
When the temperature is higher than the "upper-non-recoverable" threshold, the hardware
of the board may be damaged. The board may be powered off automatically. The system
cannot operate properly and services are affected.
Action
1. In accordance with the "Rack" number and "Shelf" number in alarm detailed
information, confirm the shelf of the board with abnormal temperature, and check
whether the fan of this shelf has any of the following alarms:
2-68

l Yes -> Step 2.

l No -> Step 3.
2. Handle the above fan alarm. Wait for five to ten minutes, and check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 3.
is cleared.
l Yes -> End.
l No -> Step 4.
4. Check whether the free slot of the shelf is installed with a blank panel. If not, install a
blank panel, wait for five to ten minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
l Yes -> Step 6.
l No -> Step 5.
l Yes -> End.
l No -> Step 7.
2.47 30728 Voltage is lower than lower-critical

threshold
Alarm Description
This alarm is generated if the voltage is lower than the lower-critical threshold. Handle the
fault as soon as possible.
Alarm Information
l Auto Clear: Yes
2-69

Alarm Parameters

starts from 0.
Alarm Cause
1. The output voltage of the shelf power module is abnormal.
2. The power module of a board is faulty.
3. The fan power is faulty.
4. A rear board is faulty.
5. The rack power is faulty.
Impact
This alarm is generated because the voltage is not stable. If the voltage is lower than the
critical-low threshold, the board may be powered off, the fan speed is reduced, and the
system cannot operate properly.
Action
1. Check whether the following alarm exists in accordance with the "Rack" number in
alarm detailed information.
25861 Voltage is lower than low threshold
l Yes -> Step 2.
l No -> Step 3.
2. Handle the alarm, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Run the SHOW SHELF command in accordance with the "Rack" number and "Shelf"
number in alarm detailed information, and check whether "Shelf type" is ETCA.
l Yes -> Step 4.
l No -> Step 8.
4. Check whether the "Rack" number and "Shelf" number where the alarm source is
located. In accordance with the "Rack" number and "Shelf" number in alarm detailed
information, check whether any of the following alarms with "Slot" number being "36
(shelf)" exists.
30728 Voltage is lower than lower-critical threshold
30729 Voltage is lower than lower-non-recoverable threshold
2-70

l Yes -> Step 5.

l No -> Step 12.
5. Measure the input voltage of the shelf with a multimeter (System Power-On). Check
whether the voltage is in the range of error tolerance (For -48 V voltage, the error
tolerance ranges from -40 V to -57 V. For -60 V voltage, the error tolerance ranges
from -50 V to -72 V.)
l Yes -> Step 6.
l No -> Step 7.
6. Replace a CDM module (Replacement of Shelf Parts) in accordance with the "Rack"
number, "Shelf" number, and "Slot" number in alarm detailed information. Check
l Yes -> End.
l No -> Step 12.
7. Contact the power supply department to check external circuits, and then check
whether the alarm is cleared after the voltage is steady.
l Yes -> End.
l No -> Step 12.
8. Check whether the following alarms with slot numbers being 34 and 35 (power supply)
exist in accordance with the "Rack" number and "Shelf" number in alarm detailed
information:
l Yes -> Step 9.
l No -> Step 12.
9. Measure the input voltage of the shelf with a multimeter. Check whether the voltage is
in the range of error tolerance (For -48 V voltage, the error tolerance ranges from -40
V to -57 V. For -60 V voltage, the error tolerance ranges from -50 V to -72 V.)
l Yes -> Step 10.
l No -> Step 11.
10. Replace an NPEM (Replacement of Shelf Parts) in accordance with the "Rack" number
and "Shelf" number in alarm detailed information. Wait for two minutes, and then check
l Yes -> End.
l No -> Step 12.
11. Contact the electric power department to examine and repair external circuits. After
the voltage is steady, check whether the alarm is cleared.
l Yes -> End.
l No -> Step 12.
12. Check whether "Slot" number in alarm detailed information is "31", "32", and "33" (fan).
l Yes -> Step 13.
l No -> Step 14.
13. Replace the subrack of the fan with a new one (Replacement of Shelf Parts ) in
2-71

information. Wait for two minutes. After the fan subrack operates properly (the RUN
indicator flashes at 1 Hz), check whether the alarm is cleared.
l Yes -> End.
l No -> Step 18.
14. Check whether "Slot" number in alarm detailed information is in the range of 1 to 28
(board).
l Yes -> Step 15.
l No -> Step 16.
15. Replace the faulty board with a new one (Board Replacement) in accordance with the
"Rack" number, "Shelf" number, and "Slot" number in alarm detailed information. Wait
for two minutes. After the board operates properly (the OK indicator flashes at 1 Hz),
l Yes -> End.
l No -> Step 16.
16. Check whether "Slot" number in alarm detailed information is either "29" or "30" (CMM
board).
l Yes -> Step 17.
l No -> Step 18.
17. Replace the CMM board (Replacement of Shelf Parts) in accordance with the "Rack"
number, "Shelf" number, and "Slot" number in alarm detailed information. Wait for
three minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 18.
2.48 30729 Voltage is lower than lower-non-recoverable

threshold
Alarm Description
This alarm is generated if the voltage is lower than the lower-non-recoverable threshold.
Handle the fault as soon as possible.
Alarm Information
l Auto Clear: Yes
2-72

Alarm Parameters

starts from 0.
Alarm Cause
Impact
This alarm is generated because the voltage is not stable. If the voltage is lower than the
lower-non-recoverable threshold, the board may be powered off, the fan speed is reduced,
and the system cannot operate properly.
Action
25861 Voltage is lower than low threshold
l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
l Yes -> Step 4.
l No -> Step 8.
(shelf)" exists.
l Yes -> Step 5.
2-73

l No -> Step 12.

from -50 V to -72 V.)
l Yes -> Step 6.
l No -> Step 7.
6. Replace the CDM module (Replacement of Shelf Parts) in accordance with the "Rack"
number and "Shelf" number in alarm detailed information. Check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
8. Check whether the following alarms with slot numbers being 34 and 35 (power supply)
exist in accordance with the "Rack" number and "Shelf" number in alarm detailed
information:
l Yes -> Step 9.

l No -> Step 12.
l Yes -> Step 10.
l No -> Step 11.
10. Replace the NPEM (Replacement of Shelf Parts )in accordance with the "Rack"
number and "Shelf" number in alarm detailed information. Wait for two minutes, and
l Yes -> End.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
12. Check whether "Slot" number in alarm detailed information are "31", "32", and "33"
(fan).
l Yes -> Step 13.
l No -> Step 14.
13. Replace the subrack of the fan with a new one (Replacement of Shelf Parts) in
2-74

l Yes -> End.
l No -> Step 18.
(board).
l Yes -> Step 15.
l No -> Step 16.
l Yes -> End.
l No -> Step 16.
board).
l Yes -> Step 17.
l No -> Step 18.
number, "Shelf" number, and "Slot" number in the alarm information. Wait for three
l Yes -> End.
l No -> Step 18.
2.49 30731 Voltage is higher than upper-critical

threshold
Alarm Description
This alarm is generated if the voltage is higher than the upper-critical threshold. Handle
the fault as soon as possible.
Alarm Information
l Auto Clear: Yes
2-75

Alarm Parameters

starts from 0.
Alarm Cause
Impact
This alarm is generated because the voltage is not stable. If the voltage is higher than the
upper-critical threshold, the component mat be damaged, and the system cannot operate
properly.
Action
25860 Voltage is higher than high threshold
l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
l Yes -> Step 4.
l No -> Step 8.
(shelf)" exists.
30731 Voltage is higher than upper-critical threshold
30732 Voltage is higher than upper-non-recoverable threshold
l Yes -> Step 5.
2-76

l No -> Step 12.

from -50 V to -72 V.)
Yes -> Step 6.
No -> Step 7.
number and "Shelf" number" in alarm detailed information. Check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
8. Check whether slots 34 and 35 (power supply) have the following alarms in accordance
with the "Rack" number and "Shelf" number in the alarm information:
l Yes -> Step 9.
l No -> Step 12.
l Yes -> Step 10.
l No -> Step 11.
l Yes -> End.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
(fan).
l Yes -> Step 13.
l No -> Step 14.
2-77

l Yes -> End.
l No -> Step 18.
(board).
l Yes -> Step 15.
l No -> Step 16.
l Yes -> End.
l No -> Step 16.
board).
l Yes -> Step 17.
l No -> Step 18.
l Yes -> End.
l No -> Step 18.
2.50 30732 Voltage is higher than

upper-non-recoverable threshold
Alarm Description
This alarm is generated if the voltage is higher than the upper-non-recoverable threshold.
Handle the fault as soon as possible.
Alarm Information
l Auto Clear: Yes
2-78

Alarm Parameters

starts from 0.
Alarm Cause
Impact
This alarm is generated because the voltage is not stable. If the voltage is higher than
the upper-non-recoverable threshold, the component mat be damaged, and the system
cannot operate properly.
Action
25860 Voltage is higher than high threshold
l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
l Yes -> Step 4.
l No -> Step 8.
(shelf)" exists.
l Yes -> Step 5.
2-79

l No -> Step 12.

from -50 V to -72 V.)
l Yes -> Step 6.
l No -> Step 7.
number, "Shelf" number, and "Slot" number in alarm detailed information. Check
l Yes -> End.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
8. Check whether slots 34 and 35 (power supply) have the following alarms in accordance
with the "Rack" number and "Shelf" number in the alarm information:

l Yes -> Step 9.
l No -> Step 12.
l Yes -> Step 10.
l No -> Step 11.
l Yes -> End.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
(fan).
l Yes -> Step 13.
l No -> Step 14.
2-80

l Yes -> End.

l No -> Step 18.
(board).
l Yes -> Step 15.
l No -> Step 16.
l Yes -> End.
l No -> Step 16.
board).
l Yes -> Step 17.
l No -> Step 18.
l Yes -> End.
l No -> Step 18.
2.51 30734 Velocity of fan is lower than lower-critical

threshold
Alarm Description
This alarm is generated when the speed of the fan is less than the " lower-critical" threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

starts from 0.
2-81

Alarm Cause
1. The voltage of the fan is insufficient because the rear board of the shelf is faulty.
2. The voltage of the fan is insufficient or unsteady because the external power is
abnormal.
3. The internal components in the fan are faulty, for example, the fan is damaged or the
circuit connection is poor.
Impact
1. If the speed of multiple fans is too slow, the heat dissipation of the system is affected.
Partial boards are powered off for the high temperature forcibly and the system
operates abnormally.
2. The speed of other fans may be accelerated, the system noise is increased, and the
useful life of the fan is reduced.
Action
1. In accordance with the "Rack" number and "Shelf" number in alarm information, check
whether slots 31, 32, and 33 (fan) have the following alarms:

l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
detailed information, remove and install the subrack of the fan (Replacement of Shelf
Parts). Wait for two minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
detailed information, install the subrack of the fan (Replacement of Shelf Parts). Wait
for two minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
2-82

2.52 30747 Module/Board device absent

Alarm Description
This alarm is generated if the CDM is unavailable.
Alarm Information
l Auto Clear: Yes
Alarm Parameters

starts from 0.
Generic event state (8) General event status, for example, the device is
present / not present. The options are as follows:
Alarm Cause
1. The CDM module is not present.
2. The connection between the CDM module and the rear board is poor.
Impact
If only one CDM module is unavailable, the system is not affected. If both CDM modules
are unavailable, the entire shelf cannot be started. The configuration information of the
shelf is in the CDM modules. This information is required when the shelf is started.
Action
1. Query the shelf sensor, and run the SHOW CDMSTATE command to check whether
"CDM1 Present" and "CDM2 Present" are set to "Not in place".
l Yes -> Step 2.
l No -> Step 3.
2. Install the CDM module (Replacement of Shelf Parts), and check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 3.
3. In accordance with the "Rack" number, "Shelf" number, and "CDM number" in alarm
detailed information, replace the CDM module with a new one (Replacement of Shelf
Parts), and then check whether the alarm is cleared.
2-83

l Yes -> End.

l No -> Step 4.
2.53 30748 Power on failed due to S5

Alarm Description
This alarm is generated if the board cannot be powered on because it is in S5 status.
Alarm Information
l Auto Clear: Yes
Alarm Cause
1. The board hardware is faulty.
2. The board firmware is improperly.
Impact
The board cannot be powered on and services cannot operate.
Action
1. Remove and install (Common Operations of Board Replacement) the board in
detailed information. Wait for two minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
for two minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2.54 30808 Processor internal error

Alarm Description
This alarm is generated when the internal processor of the board is faulty.
2-84

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Processor Event Type Type of processor-related events, for example, the internal error of
the processor, or the temperature of the processor is too high. The
l IERR
l Thermal Trip
Alarm Cause
The processor has an internal error.
Impact
If the internal processor is faulty, maybe the system will be done and services cannot
operate properly.
Action
1. Run the RESET FORCE command to reset the board in accordance with the "Rack"
number, "Shelf" number, and "Slot" number in alarm detailed information. Wait for five
to ten minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
for five to ten minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2.55 30809 Processor thermal trip

Alarm Description
This alarm is generated when the processor temperate of the board is too high.
2-85

Alarm Information
l Auto Clear: Yes
Alarm Parameters

starts from 0.
Processor Event Type Type of processor-related events, for example,

the internal error of the processor, or the
temperature of the processor is too high. The
l IERR
l Thermal Trip
Alarm Cause
The processor temperature is too high.
Impact
If the processor is overheated, the CPU may be damaged and the system may be down.
As a result, services cannot operate properly.
Action
1. In accordance with the "Rack" number and "Shelf" number in alarm information, locate
the shelf of the board with abnormal temperature, and check whether the fan of this
shelf has any of the following alarms:
l Yes -> Step 2.
l No -> Step 3.
2. Handle the above fan alarms. Wait for five to ten minutes, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether the overheated board has any of the following alarms in accordance
with the "Rack" number and "Shelf" number in alarm information:
30725 Temperature is higher than upper-critical threshold
30726 Temperature is higher than upper-non-recoverable threshold
2-86

l Yes -> Step 4.

l No -> Step 5.
4. Handle the above temperature alarms. Wait for five to ten minutes, and check whether
l Yes -> End.
l No -> Step 5.
is cleared.
l Yes -> End.
l No -> Step 6.
6. Check whether the empty slot of the shelf is installed with a blank panel. If not, install
a blank panel, wait for five to ten minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
check whether air filters of the shelf and the cabinet are blocked.
l Yes -> Step 8.
l No -> Step 9.
l Yes -> End.
l No -> Step 9.
9. Remove and install the board (Common Operations of Board Replacement) in
detailed information. Wait for five to ten minutes, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 10.
for five to ten minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 11.
2.56 8392706 Time synchronization over alarm limit

Alarm Description
This alarm is generated when the difference between the NE time and the time of the SNTP
server reaches the threshold during the time synchronization in OMP networking mode.
In OMP networking mode, the NE uses the OMP as the client of the SNTP, and obtains
the time from the SNTP server. Each board obtains the time from the OMP.
2-87

Alarm Information
l Auto Clear: Yes
Alarm Parameters
OMP time(GMT) Indicates the GMT obtained from the OMP in the
SNTP synchronization alarm.
Time(GMT) from the SNTP server Indicates the GMT obtained from the SNTP
server in the SNTP synchronization alarm.
The limit for alarm (ms) Threshold set for the "Time synchronization over
alarm limit" alarm in RPU networking mode (ms).
Time got from SNTP: millisecond part Millisecond part of time obtained from the SNTP
server.
SNTP alarm threshold Threshold set for the "Time synchronization over
alarm limit" alarm in OMP networking mode (ms).
OMP time(GMT) Indicates the GMT obtained from the OMP in the
SNTP synchronization alarm.
Time(GMT) from the SNTP server Indicates the GMT obtained from the SNTP
server in the SNTP synchronization alarm.
Alarm Cause
1. The set alarm threshold is low.
2. Time hopping occurs on the SNTP server.
3. Time hopping occurs on the NE.
Impact
The system time may be incorrect, so all functions relating to the time are affected (for
example, the performance statistics result is incorrect, and the alarm reporting time is
incorrect).
Action
1. Check whether "The limit for alarm (ms)" in alarm detailed information meets the actual
requirements.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SHOW SNTP command to modify the alarm threshold as required. Check
l Yes -> End.
2-88

l No -> Step 3.
3. Check " OMP time(GMT) " and "Time(GMT) from the SNTP server" in alarm detailed
information. Run the SHOW TIME command to obtain the NE time in accordance with
the physical address in alarm information to determine which time is more accurate.
l If the time (GMT) from the SNTP server is more accurate -> Step 4.
l If the OMP time (GMT) is more accurate -> Step 5.
l If there is no method for determining which time is more accurate -> Step 7.
4. Run the UPD TIME command to send an SNTP time synchronization request forcedly.
Wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
5. Contact the maintenance personnel of SNTP server to check whether related alarms
exist.
l Yes -> Step 6.
l No -> Step 7.
6. Wait for the maintenance personnel of SNTP server to solve related faults, and go to
Step 4.
2.57 8392707 Request SNTP time failed

Alarm Description
This alarm is generated if the NE receives no response or receives an error response from
the SNTP server after it sends a time synchronization request to the SNTP server during
the time synchronization.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
SNTP server IP address IP address of the SNTP server that fails to be

synchronized.
Alarm Cause
1. The IP address of the configured SNTP server does not exist, or the device with the
corresponding IP address is not enabled with the SNTP service.
2. The SNTP server operates improperly, or the time of the SNTP server is not
synchronized with its upper-level server.
3. The configured time synchronization period of the NE is less than 16 seconds.
2-89

Impact
The time fails to be synchronized from the SNTP server. The system time may be incorrect,
so all functions relating to the time are affected (for example, the performance statistics
result is incorrect, and the alarm reporting time is incorrect).
Action
1. Run the SHOW SNTP command to check the SNTP configuration, and confirm
whether "Primary SNTP Address" and "SNTP Synchronous Cycle (ms)" meet the
real requirements.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET SNTP command to modify the configuration of the SNTP server. Check
l Yes -> End.
l No -> Step 3.
3. Contact the maintenance personnel of SNTP server to check whether related alarms
exist.
l Yes -> Step 4.
l No -> Step 5.
4. After the maintenance personnel of the SNTP server solves the fault, run the UPD
TIME command to send an SNPT time synchronization request forcedly. Wait for one
minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
2.58 8393985 Control plane communication abnormal

between board and its home module
Alarm Description
This alarm is generated if the home module of the board detects that the communication
between the control plane of the board and the module is abnormal.
Alarm Information
l Auto Clear: Yes
2-90

Alarm Parameters
Physical address Physical address of the board that causes the alarm.
Logical address Logical address, including "Subsystem" number, "module"

number, "Unit" number, and the "Sub-unit" number, of the
board that causes the alarm.
Logical CPU number Number of the logical CPU that causes the alarm.
Alarm Cause
1. The board is offline.
2. The board fails to be powered on after reset.
4. The channel between the control plane of the board and its home module is abnormal,
for example, the switching board is removed.
Impact
The board is blocked, and all services running on the board are interrupted.
Action
1. Check whether the faulty board has the following alarm:
8393987 Board offline
l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
3. Check whether the switching board operates properly.
l Yes -> Step 5.
l No -> Step 4.
4. Resolve the switching board fault, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Check whether the following notification is generated after the alarm (determined in
accordance with the occurrence time).
4419 Logic CPU is power on failed

l Yes -> Step 6.
l No -> Step 7.
6. Handle the notification, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
2-91

7. Run the RESET NORMAL command to reset the board, wait for five to ten minutes,
l Yes -> End.
l No -> Step 8.
2.59 8393986 Control plane communication is abnormal

between this board and the active independent
board
Alarm Description
This alarm is generated if the active board detects that the communication between it and
the standby board is disconnected.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Physical address Physical address of the board that causes the

alarm.
Alarm Cause
4. The communication link between the active and standby boards is abnormal.
Impact
Because the active and standby boards cannot communicate with each other,
active/standby switchover cannot be implemented if the active board is faulty. This alarm
does not affect services, but the system availability may be reduced.
Action
2-92


l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
3. Press the EXCH key on the board to reset the board. Wait until the board is powered
on (the HOST indicator is flashing in green slowly at 1 Hz), and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.60 8393987 Board offline

Alarm Description
This alarm is generated if the OMP or the CMM detects that the board is offline.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Physical address Physical address of the offline board.
Alarm Cause
1. The configured board is unavailable.
2. The IPMC communication link between the CMM and the board is faulty.
Impact
This board cannot provide any services.
Action
1. Check whether the board where the alarm is generated is configured as required in
accordance with the physical location of the faulty board.
l Yes -> Step 3.
l No -> Step 2.
2. Check the board type from the rack diagram, and delete the boards in accordance
with the board type. For OMU1, IGUS1/IGSU2, and SWBB1 boards, set the slot type
2-93

to PP_Board on the CMM board. For other boards, delete them. Check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 7.
3. Check whether the board is present.
l Yes -> Step 5.
l No -> Step 4.
4. Install a board (Common Operations of Board Replacement) as required. Wait for 2
l Yes -> End.
l No -> Step 7.
5. Remove and install the board (Common Operations of Board Replacement), wait for
2 minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
6. Replace the faulty board with a new one (Board Replacement), wait for 2 minutes, and
l Yes -> End.
l No -> Step 7.
2.61 8393988 Control plane communication abnormal

between module and OMP
Alarm Description
This alarm is generated if the OMP detects that the communication between it and any
other control plane of other modules.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Physical address Physical address of the board that causes the

alarm.
Logical address Logical address, including "Subsystem" number,

"module" number, "Unit" number, and the
2-94

"Sub-unit" number, of the board that causes the

alarm.
Alarm Cause
4. The channel between the control plane of the board and the OMP is abnormal, for
example, the switching board is removed.
Impact
The board is blocked and the corresponding functions are unavailable, so all services of
the board are unavailable.
Action
1. Check whether the faulty board has the following alarm:
8393987 Board offline
l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
3. Check whether the switching board operates properly.
l Yes -> Step 5.
l No -> Step 4.
4. Resolve the switching board fault, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
l Yes -> Step 6.
l No -> Step 7.
l Yes -> End.
l No -> Step 7.
7. Run the RESET NORMAL command to reset the board, wait for five to ten minutes,
l Yes -> End.
l No -> Step 8.
2-95

2.62 8398848 SCCP subsystem unavailable

Alarm Description
This alarm is generated when the signaling processing module of the NE detects that the
SCCP subsystem is unavailable.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Office ID Number of the office that causes the alarm.
Subsystem number Number of the SCCP subsystem that causes the

alarm.
Alarm Cause
1. The office of the remote signaling point is unreachable.
2. The SCCP subsystem of the remote signaling point is out of service.
Impact
Services bearing on the SCCP subsystem are interrupted.
Action
1. Check whether "Office ID" and "Subsystem" number in alarm detailed information are
consistent with the real office ID and subsystem number.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET N7SSN command as required, wait for three minutes, and then check
l Yes -> End.
l No -> Step 3.
3. Check whether any of the following alarms exists in accordance with "Office ID" in
alarm detailed information:
8400128 MTP3 office inaccessible
l Yes -> Step 4.
l No -> Step 5.
2-96

l Yes -> End.
l No -> Step 5.
5. Contact the maintenance personnel of the peer end to check whether the SCCP
subsystem configuration is consistent with the real requirements or whether the
SCCP subsystem is disabled.
l Yes -> Step 6.
l No -> Step 7.
6. Contact the maintenance personnel of the peer end to handle related alarms, wait for
three minutes, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
2.63 8400384 M3UA office inaccessible

Alarm Description
This alarm is generated if the board detects that the M3UA office is inaccessible.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Alarm Cause Detailed causes of the "M3UA/SUA/STC office

inaccessible" alarm or the "STC office congested"
l Configuration is changed.
l Association link breakdown
l STC Office is not reachable due to DH block
(Make a report when unlocked)
l Communication breakdown between SMP
and OMP
l initialized Alarm for STC office unreachable
l Alarm for STC office unreachable or
congested because of changeover
l Slave to master
l AS ASP state changed
l Receive DUNA message
2-97

l Received DAVA message.

l Refreshing route
l Configuration change
l No active route
l AS recovery timer T(r) timed out.
l DHMM changeover
l Initialized Alarm for M3UA office unreachable
l M3UA office is deleted
l The office is administrated by another
module.
l M3UA office is unreachable when slave to
master
l Receive DRST message
l initialized Alarm for SUA office unreachable
l Alarm for office unreachable because the
status of asp/as changed
l Data config changed
l SUA Office not reachable due to DH block
down
l Refreshing route information after slave to
master changeover
l Office is not reachable due to received
DUNA message.
l No active route
l Office is unreachable when slave to master
l No alarm reason
l Unknown reason
Office type Type of the MTP3 office that causes the alarm.
l Local telephone office
l Long-distance telephone office in civil
l Long-distance telephone office overseas
l In the same region
l BSC
l RNC
l MGW
l WNP-SRF
l MSCE
l MSCSERVER
l PDE
l GMSCSERVER
l SGSN
l GGSN
2-98

l AGW/PDSN
l PCF
l SGW
l HA
l HLR/HLRe
l AUC
l SMC
l SCF
l SCP/SCPe
l GMLC
l MPC
l IP
l PSTN
l NGN
l NPDB
l R2 in civil
l R2 overseas
l OTAF
l ANU
l MGCF
l CSCF
l BGCF
l TMG
l TMSC1
l TMSC2
l DHCTRL
l IBSC SMLC
l BME
l AS
l TMSCS1
l TMSCS2
l ITC
l SAS
l MSC_CS
l DS
Alarm Cause
1. The association is disconnected or the AS does not enter service status.
2. The destination signaling point that receives the signaling transfer point notification is
inaccessible.
Impact
1. The upper level service cannot send or receive messages from a specific office.
2-99

2. New services under the office fail to access the network.

3. Existing services under the office are released abnormally.
Action
1. Run the SHOW ADJOFC command in accordance with "Office ID" in alarm detailed
information to check the network type and the signaling point code type, and run the
SHOW SIOLOCAS command in accordance with the query results to check whether
a route corresponding to the office is configured.
l Yes -> Step 3.
l No -> Step 2.
2. Run the ADD SIOLOCAS command to add a route configuration for the office, wait for
three minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Run the SHOW M3UART command in accordance with "ROUTEID" in route
configuration information to check the static route configuration, run the SHOW
M3UAAS command to query "ASP ID" in accordance with "AS ID" in the static route
configuration information, run the SHOW M3UAASP command in accordance with
"ASP ID" to query "SCTP ID" corresponding to the ASP configuration information,
and check whether the association has the following alarm:
8402690 Association broken
l Yes -> Step 4.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.
5. Run the SHOW M3UART command to query the static route configuration in
accordance with "ROUTEID" in the route configuration, and run the SHOW ASSTAT
command to query the AS status in accordance with ASID in the static route
configuration, and check whether the AS belonging to the office is activated.
l Yes -> Step 6.
l No -> Step 8.
6. Run the SHOW ADJOFC command in accordance with "Office ID" in alarm detailed
information to check whether " Association Type" is set to "Direct Connection Mode".
l Yes -> Step 13.
l No -> Step 7.
7. Contact the maintenance personnel of the peer device to check the connection
between the adjacent SP and destination SP. Ensure that the destination SP is
reachable from the point of the adjacent SP, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 13.
8. Run the SHOW M3UAASP command in accordance with the ASP that is not activated
to query the corresponding association configuration and obtain the association
2-100

identification corresponding to the ASP, run the SHOW SCTPSTAT command in

accordance with the association ID to check whether the association is activated.
l Yes -> Step 9.
l No -> Step 10.
9. Run the SHOW M3UAAS command to check the AS configuration and the SHOW
M3UAASP command to check the ASP configuration, and check whether the AS
configuration and the ASP configuration of the local end are consistent with those of
the peer end.
l Yes -> Step 13.
l No -> Step 11.
10. Run the REL SCTP command to deactivate the association in accordance with the
association ID, and run the EST SCTP command to activate the association, and check
whether the association is activated.
l Yes -> Step 12.
l No -> Step 13.
11. Run the SET M3UAAS command and the SET M3UAASP command to modify the
configurations as required, or contact the maintenance personnel of the peer end to
modify the configuration to ensure that the local configurations are consistent with
those of the peer end, wait for three minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 13.
12. Wait for three minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 13.
2.64 8402688 Association congested

Alarm Description
This alarm is generated if the messages transmitted by the association exceed 7/8 of the
cache capacity.
Alarm Information
l Alarm Type: QoS Alarm
l Auto Clear: Yes
Alarm Parameters
Association number ID of the association that causes the alarm.
SCTP Stream ID Stream ID of the SCTP association that causes

the "Association congested" alarm.
2-101

SSM upper-layer user Upper-layer user type of the association that

causes the alarm. The options are as follows:
l M2UA
l M2PA
l M3UA
l SUA
l H248
l BICC
l IUA
l DHCTRL
l SIP
l V5UA
l DHCTRL_CDMA
l H245
l NBAP
l A3A7APP
l IPCSP
l GWSC
l S1AP
l UBAS
l IPABIS
l SGs
l HNBAP
l RUA
l LOCRPT
l X2AP
l M3AP
l LCSAP
l TEST
Office ID Number of the MTP3 office that causes the alarm.
Alarm Cause
1. Too many services need to be processed, which causes the SCTP association to be
overloaded.
2. The SCTP associations are overloaded because some SCTP associations are faulty
or the routing is not well balanced.
3. Some networks are disconnected or the network bandwidth is insufficient.
Impact
Congestion may result in transmission delay. In normal cases, services are not affected.
In serious cases, congestion may result in call loss and reduced access rate.
2-102

Action
1. Check whether there is any fault on other associations that results in congestion of the
association. Check whether other associations have any of the following alarms:
8417537 Association path broken
8402690 Association broken
l Yes -> Step 2.
l No -> Step 3.
2. Handle the above alarms, wait for three minutes, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 3.
3. Check the traffic of this association in accordance with the traffic of SSM messages,
and check whether the number of bytes and the average sent traffic corresponding to
the sent subscriber messages is increased greatly.
l Yes -> Step 4.
l No -> Step 6.
4. Contact the network optimization personnel to check whether it is required to add the
carrier network bandwidth (by adding associations or send buffer).
l Yes -> Step 5.
l No -> Step 6.
5. Add associations. Wait for three minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
2.65 8402690 Association broken

Alarm Description
This alarm is generated when the association link is broken.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Module number Module number of the association that causes

the alarm.
2-103

Reason causes of association interruption. The options

are as follows:
l Unknown reason of SCTP
l Invalid instance ID
l Idle instance (instance not initialized)
l Association already exists, but is inactive
l Initialization timer timed out
l COOCKIE response timeout
l Initial acknowledgement length error
l Initial acknowledgement tag error
l Initial acknowledgement parameter error
l Initial acknowledgement address error
l Initialization acknowledgement cookie error
(parameter "cookie" missing for INIT ACK)
l Initialization acknowledgement COOKIE
damaged (COOKIE expiry)
l Sending msg failed to ULP
l Shutdown completeness received
l sending failed exceeding threshold
l Slave-to-master switchover failed
l Abort request from remote peer received
l All paths are inactive
l Association establishment failed while
master-to-slave
l The upper layer sends ABORT primitive.
l The upper layer sends SHUTDOWN
primitive.
l The upper layer sends DESTROY primitive.
l Establishment is prohibited by ULP
l Establishment timer timed out
l Send buffer error
l Receive buffer error
l Association restart
l SHUTDOWN Ack from the peer is received.
l Fail to initialize TCB Queue
l No respond to SHUTDOWN message for
several times
l The upper service closed
l Fail to request association link of ULP
l Association is offline state
l Peer abort establishment
l Fail to send data from upper user to SCTP
2-104

l No response from SCTP to status request of

upper user 3 times continuously
l Association status of SCTP layer is not same
as that of upper user
l Manually released
l ULP released
l Data configuration of association is modified
l Data configuration of association is deleted
l Dual homing block (DH process blocks
association request)
l Unknown reason
l Data configuration of ULP is modified
l ASP recovers to DOWN state.
l Association is released by ULP because
data is received on inactive ASP
l Query association state. Association ID is
not matching.
l ASP in the ASP-DOWN state received ASP
Inactive or ASP Active message
l SCTP association is in slave state for a
long time due to changeover, resulting in
association breakdown
l The proxy office has been unaccess,and the
SG block the related association
l ULP requests association status failed 3
times continuously
l Association status of ULP is not same as
that of underlayer
l ULP is invalid
l Association is offline state
l The Association already exists in other SIG
process
l The initialization cause of SCTP
broken,unknown reason
ULP type Protocol type of an association.
Alarm Cause
1. The association is released manually.
2. The association channel on both ends is faulty.
3. The association configuration on the local end is not consistent with that on the peer
end.
2-105

Impact
The association is interrupted, and upper-layer services of the association may be affected
(signaling link). For example, the signaling office is unreachable, so services of other
available associations are increased.
Action
1. Run the SHOW SCTP command in accordance with "Association number" in
alarm detailed information to check "Remote IP" and "Remote Port" meet the real
requirements.
l Yes -> Step 2.
l No -> Step 3.
2. Run the corresponding command to modify the association configuration in
accordance with the corresponding protocol type obtained by running the SHOW
SCTP command as required, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Contact the maintenance personnel of the peer end, and check whether the related
configuration of the peer end is consistent with the real requirement.
l Yes -> Step 5.
l No -> Step 4.
4. After the maintenance personnel of the peer end modifies the configuration as
required, check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Run the IPSTACK command to enter protocol stack mode, run the SHOW IP ROUTE
command in accordance with "Remote IP" in alarm detailed information to check the
route configuration meets the real requirements.
l Yes -> Step 7.
l No -> Step 6.
6. Run the ADD IP ROUTE/DEL IP ROUTE command to modify the corresponding route
configuration, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
7. Check whether "Reason" in alarm detailed information is "Establishment timer timed
out".
l Yes -> Step 10.
l No -> Step 8.
8. Check whether "Reason" in alarm detailed information is "All paths are inactive".
l Yes -> Step 10.
l No -> Step 9.
9. Check whether "Reason" in alarm detailed information is "Abort request from remote
peer received" and "Shutdown completeness received".
l Yes -> Step 13.
l No -> Step 15.
2-106

10. Run the SHOW IP ROUTE command in accordance with "Remote IP" in alarm
detailed information to confirm the logical information (port quintuplet) and the
physical information (rack-shelf-slot) of the corresponding egress interface board,
confirm the logical information and physical information of the ingress interface board
in accordance with "Local IP" in alarm detailed information and the real requirement
of the peer route, and check whether the ingress and egress interface boards relating
to the board and the alarm have any of the following alarms:
5760 Ethernet port's link is down
l Yes -> Step 11.
l No -> Step 12.
l Yes -> End.
l No -> Step 12.
12. Ping 1200 packets in accordance with "Remote IP" in alarm detailed information, and
check whether packet loss occurs.
l Yes -> Step 13.
l No -> Step 15.
13. Contact the maintenance personnel of the peer end to check whether the peer device
has related alarms.
l Yes -> Step 14.
l No -> Step 15.
l Yes -> End.
l No -> Step 10.
2.66 8417537 Association path broken

Alarm Description
This alarm is generated when the association path is broken.
Alarm Information
l Auto Clear: Yes
2-107

Alarm Parameters
Associated local IP Address Local IP address of an association.
Associated peer IP Address Peer IP address of an association.
Is Primary Path Indicates whether it is the primary path of the

configured association. The options are as
follows:
l not Primary Path
l Primary Path
Alarm Cause
1. The hardware of the board is faulty.
2. The SCTP channel on both ends is faulty.
3. The configuration on both ends is not matched.
Impact
This channel is unavailable, but services are not affected.
Action
1. Run the IPSTACK command to enter protocol stack mode, run the SHOW IP RO
UTE command in accordance with "Associated peer IP Address" in alarm detailed
information to check the route configuration meets the real requirements.
l Yes -> Step 3.
l No -> Step 2.
2. Run the ADD IP ROUTE/DEL IP ROUTE command to modify the corresponding route
l Yes -> Step 5.
l No -> End.
l Yes -> Step 4.
l No -> Step 5.
required, check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Run the SHOW IP ROUTE command in accordance with "Associated peer IP Address"
in alarm detailed information to confirm the logical information (port quintuplet) and
the physical information (rack-shelf-slot) of the corresponding egress interface board,
confirm the logical information and physical information of the ingress interface board
in accordance with "Associated local IP Address" in alarm detailed information and the
2-108

real requirement of the peer route, and check whether the ingress and egress interface
boards relating to the board and the alarm have any of the following alarms:
l Yes -> Step 6.
l No -> Step 7.
l Yes -> End.
l No -> Step 7.
7. Ping 1200 packets in accordance with "Associated peer IP Address" in alarm detailed
information, and check whether packet loss occurs.
l Yes -> Step 8.
l No -> Step 10.
has related alarms.
l Yes -> Step 9.
l No -> Step 10.
l Yes -> End.
l No -> Step 10.
2.67 8419073 Bearer network is unavailable

Alarm Description
This alarm is generated when the IP path detection function detects that packet loss occurs
on the bearer network continuously.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Task number ID of the PD detection task.
Next-hop and egress flag Whether the specified next hop and the outgoing
interface flag are set for the detection task.
2-109

Source IP Address Source IP address corresponding to a detection

task.
Destination IP Address Destination IP address corresponding to a

detection task.
Next hop address The specified next hop address of the detection
task.
Module number It refers to the corresponding module number

when the outgoing interface of the detection task
is specified.
Unit number It refers to the corresponding unit number when

the outgoing interface of the detection task is
specified.
Subunit number It refers to the corresponding the subunit number

is specified.
Subsystem number It refers to the corresponding subsystem number

is specified.
Local port It refers to the corresponding local port number

is specified.
Alarm Cause
The IP path detection function detects that the path is faulty.
Impact
Services corresponding to the path of the IP path detection function are interrupted.
Action
1. Run the IPSTACK command to enter protocol stack mode, and run the SHOW IP
ROUTE command in accordance with the "Destination IP Address" in alarm detailed
information to check whether the route configuration meets the real requirements.
l Yes -> Step 3.
l No -> Step 2.
2. Run the IPSTACK command to enter protocol stack mode, run the ADD IP ROUTE/D
EL IP ROUTE command to modify the corresponding route configuration as required,
l Yes -> End.
l No -> Step 3.
2-110

command in accordance with the "Destination IP Address" in alarm information
to confirm the logical information ("Port Quintuplet") and the physical information
(rack-shelf-slot) of the corresponding egress interface board, confirm the logical
information and physical information of the ingress interface board in accordance
with the "Source IP Address" in alarm information and the real requirement of the
peer route, and check whether the ingress and egress interface boards relating to the
board of the notification have any of the following alarms:
l Yes -> Step 4.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.
has related alarms.
l Yes -> Step 6.
l No -> Step 7.
l Yes -> End.
l No -> Step 7.
2.68 8419074 Bearer network get worse

Alarm Description
This alarm is generated when the IP path detection function detects that packet loss rate
on the bearer network exceeds the threshold.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Task number ID of the PD detection task.
Packet Loss Rate of the current next hop,Percent The quality of the link detected by the detection
task.
2-111

Next-hop and egress flag Whether the specified next hop and the outgoing
interface flag are set for the detection task.
Source IP Address Source IP address corresponding to a detection

task.
Destination IP Address Destination IP address corresponding to a

detection task.
Next hop address The specified next hop address of the detection
task.
Module number It refers to the corresponding module number

is specified.
Unit number It refers to the corresponding unit number when

the outgoing interface of the detection task is
specified.
Subunit number It refers to the corresponding subunit number

is specified.
Subsystem number It refers to the corresponding subsystem number

is specified.
Local port It refers to the corresponding local port number

is specified.
Alarm Cause
The IP path detection function detects that the QoS of the path is poor.
Impact
Services corresponding to the path of the IP path detection function may be affected.
Action
command in accordance with the "Destination IP Address" in alarm information
to confirm the logical information ("Port Quintuplet") and the physical information
information and physical information of the ingress interface board in accordance
with the "Source IP Address" in alarm information and the real requirement of the
2-112


l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
has related alarms.
l Yes -> Step 4.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.
2.69 2365980673 Performance QoS Critical Alarm

Alarm Description
The alarm is raised when the performance index value collected by the performance
measurement task reaches the monitoring threshold.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Task Name Name of a performance task of the critical alarm.
Task ID ID of a performance task of the critical alarm.
Index Name Name of an index of the critical alarm.
Index ID ID of an index of the critical alarm.
Index Value Value of an index of the critical alarm.
Measurement Object Type Name of the object type of the critical alarm.
Object Name Name of the object of the critical alarm.
Object ID ID of the object of the critical alarm.
Start Time Start time of the critical alarm.
2-113

End Time End time of the critical alarm.
Alarm Direction Alarm direction defined by a user.
Warning Alarm Threshold Threshold of a warning alarm level defined by a user.
Warning Alarm Oscillation Value Oscillation value of a warning alarm level defined by a user.
Minor Alarm Threshold Threshold of a minor alarm level defined by a user.
Minor Alarm Oscillation Value Oscillation value of a minor alarm level defined by a user.
Major Alarm Threshold Threshold of a major alarm level defined by a user.
Major Alarm Oscillation Value Oscillation value of a major alarm level defined by a user.
Critical Alarm Threshold Threshold of a critical alarm level defined by a user.
Critical Alarm Oscillation Value Oscillation value of a critical alarm level defined by a user.
Alarm Cause
The performance threshold alarm exceeds the monitoring index, and becomes a critical
alarm. The probable alarm causes are related to the preset monitored performance
indexes.
Impact
Impacts on the system depend on the monitoring thresholds and severity levels of indexes.
When alarms occur on some indexes, service quality is affected, for example:
1. Call completion ratio: If the ratio is smaller than 90%, this alarm is a critical alarm. This
alarm indicates a low call completion ratio.
2. Network bandwidth usage: If the usage exceeds 90%, the alarm is a critical alarm. If
the alarm cannot be cleared, the system is overloaded and requires hardware upgrade
to meet the requirements of normal system operation.
Action
1. Based on additional alarm information (task ID and index ID), run the SHOW PMMON
ITOR command to check whether the corresponding performance threshold settings
are the same with the plans.
l Yes -> Step 3.
l No -> Step 2.
2. Modify the corresponding performance task thresholds and oscillation in the OMM
performance management, and check whether the alarm is cleared after a task
collection period.
l Yes -> End.
l No -> Step 5.
3. Check counter or index expressions in conjunction with current counter values to see
whether the services are operating improperly.
l Yes -> Step 4.
2-114

l No -> Step 5.
4. Check the service operational status to troubleshoot the services based on service
models, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
2.70 2365980674 Performance QoS Major Alarm

Alarm Description
Alarm Information
l Auto clear: Yes
Alarm Parameters
Task Name Name of a performance task of the major alarm.
Task ID ID of a performance task of the major alarm.
Index Name Name of an index of the major alarm.
Index ID ID of an index of the major alarm.
Index Value Value of an index of the major alarm.
Measurement Object Type Name of the object type of the major alarm.
Object Name Name of the object of the major alarm.
Object ID ID of the object of the major alarm.
Start Time Start time of the major alarm.
End Time End time of the major alarm.
2-115

Critical Alarm Threshold Threshold of a critical alarm level defined by a user.
Critical Alarm Oscillation Value Oscillation value of a critical alarm level defined by a user.
Alarm Cause
The performance threshold alarm exceeds the monitoring index, and becomes a major
indexes.
Impact
1. Call completion ratio: If the ratio is smaller than 80%, this alarm is a major alarm. This
2. Network bandwidth usage: If the usage exceeds 70%, the alarm is a major alarm. If
Action
l Yes -> Step 3.
l No -> Step 2.
collection period.
l Yes -> End.
l No -> Step 5.
l Yes -> Step 4.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.
2-116

2.71 2365980675 Performance QoS Common Alarm

Alarm Description
Alarm Information
l Auto clear: Yes
Alarm Parameters
Task Name Name of a performance task of the minor alarm.
Task ID ID of a performance task of the minor alarm.
Index Name Name of an index of the minor alarm.
Index ID ID of an index of the minor alarm.
Index Value Value of an index of the minor alarm.
Measurement Object Type Name of the object type of the minor alarm.
Object Name Name of the object of the minor alarm.
Object ID ID of the object of the minor alarm.
Start Time Start time of the minor alarm.
End Time End time of the minor alarm.
Critical Alarm Threshold Threshold of a minor alarm level defined by a user.
Critical Alarm Oscillation Value Oscillation value of a minor alarm level defined by a user.
Alarm Cause
The performance threshold alarm exceeds the monitoring index, and becomes a minor
indexes.
2-117

Impact
1. Call completion ratio: If the ratio is smaller than 70%, this alarm is a minor alarm. This
2. Network bandwidth usage: If the usage exceeds 60%, the alarm is a minor alarm. If
Action
l Yes -> Step 3.
l No -> Step 2.
collection period.
l Yes -> End.
l No -> Step 5.
l Yes -> Step 4.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.
2.72 2365980676 Performance QoS Warning Alarm

Alarm Description
Alarm Information
l Auto clear: Yes
2-118

Alarm Parameters
Task Name Name of a performance task of the warning alarm.
Task ID ID of a performance task of the warning alarm.
Index Name Name of an index of the warning alarm.
Index ID ID of an index of the warning alarm.
Index Value Value of an index of the warning alarm.
Measurement Object Type Name of the object type of the warning alarm.
Object Name Name of the object of the warning alarm.
Object ID ID of the object of the warning alarm.
Start Time Start time of the warning alarm.
End Time End time of the warning alarm.
Critical Alarm Threshold Threshold of a warning alarm level defined by a user.
Critical Alarm Oscillation Value Oscillation value of a warning alarm level defined by a user.
Alarm Cause
The performance threshold alarm exceeds the monitoring index, and becomes a warning
indexes.
Link faults result in many calls failed to be connected.
For example, if the monitored performance index is call completion ratio (call completion
ratio = number of times of call completion / number of times of call attempts * 100%), the
probable alarm causes are as follows:
Impact
1. Call completion ratio: If the ratio is smaller than 60%, this alarm is a warning alarm.
This alarm indicates a low call completion ratio.
2-119

2. Network bandwidth usage: If the usage exceeds 50%, the alarm is a warning alarm. If
Action
l Yes -> Step 3.
l No -> Step 2.
collection period.
l Yes -> End.
l No -> Step 5.
l Yes -> Step 4.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.
2.73 2365980929 Internal Controlled Account Number

and Password Will Expire Soon
Alarm Description
The alarm is raised when an internal control account password is going to be expired.
Alarm Information
l Auto clear: Yes
2-120

Alarm Parameters
Account Type Internal control account type.

l Data File Account
l File Transfer Account
l OMP File Transfer Account
l OMP TELNET Account
Account Name Internal control account name.
Days Before The Password Is In- Days for reminding password expiry before the password
valid expires. The password expiry date depends on the last
password modification date and password validity period.
Password Valid Day Depends on the last password modification date and password
validity period.
Alarm Cause
The Send Alarm or Not When Password Expired parameter is set to Yes for the internal
control password policy, and the Reminding Days Before Password Expired parameter
is not 0. The duration since the last time when the administrator modifies an internal control
account password has reached the threshold.
Impact
This alarm has no impact on normal OMM operation, but reminds the administrator of
security activities. This policy can be disabled if necessary.
Action
1. Run the SHOW PASSWDTACTIC command to check whether the Send Alarm or
Not When Password Expired function is enabled in the internal control password
policy configuration.
l Yes -> Step 2.
l No -> Step 8.
2. Check whether the Send Alarm or Not When Password Expired function is required
based on actual conditions, for example, this function is recommended in a public
network.
l Yes -> Step 4.
l No -> Step 3.
3. Run the SET PASSWDTACTIC command to disable the Send Alarm or Not When
Password Expired function, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 8.
4. Check whether the Send Alarm or Not When Password Expired function is only
required when the password expires.
Yes -> Step 5.
2-121

No -> Step 6.
5. Run the SET PASSWDTACTIC command to set the Reminding Days Before
Password Expired parameter to 0, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
6. Check whether it is the first time to modify the internal control password.
l Yes -> Step 7.
l No -> Step 8.
7. Run the SET ACCOUNTPASSWD command to modify the internal control password.
This command is a dangerous command and cannot be executed with other operation
and maintenance items simultaneously. The initial password is the same as the
account. Wait for 30 seconds, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 8.

and Password Already Expired
Alarm Description
The alarm is raised when an internal control account password is expired.
Alarm Information
l Auto clear: Yes
Alarm Parameters

l Data File Account
Account Name Internal control name.
Days Before The Password Password validity days

Is Invalid
Expired Days The days since the password is expired, which depends on the last
2-122

Alarm Cause
The Send Alarm or Not When Password Expired parameter is set to Yes, but the
administrator does not modify the password before the password expires.
Impact
security activities. This policy can be disabled if necessary.
Action
1. Run the SHOW PASSWDTACTIC command to check whether the Send Alarm or
l Yes -> Step 2.
l No -> Step 6.
network.
l Yes -> Step 4.
l No -> Step 3.
3. Run the SET PASSWDTACTIC command to disable the Send Alarm or Not When
l Yes -> End.
l No -> Step 6.
4. Check whether it is the first time to modify the internal control password.
l Yes -> Step 5.
l No -> Step 6.
and maintenance items simultaneously. The initial password is the same as the
account. Wait for 30 seconds, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.

and Password Do Not Meet Requirements
Alarm Description
The alarm is raised when an internal control account password fails to meet the
requirements.
2-123

Alarm Information
l Auto clear: Yes
Alarm Parameters

l Data File Account
Detailed Password Policy not Meet Passwords that fail to meet the password policies.
Alarm Cause
1. The length of an interface internal control password is shorter than the Minimum
Length of Password parameter.
2. The length of an internal control password is longer than the Maximum Length of
Password parameter.
3. The password complexity policy is enabled, but an internal control password does not
meet the policy.
4. The password history function is enabled, but an internal control password is the
same as an old password set in the Count of Latest Passwords Cannot Be Reused
parameter.
Impact
This alarm has no impact on normal OMM operation, but reminds the administrator to
modify the inner-control password to meet the requirements.
Action
1. Run the SHOW PASSWDTACTIC command to show the Min Length of Password,
Max Length of Password, Weak Password Check, and Can Not Use Recently
Used Password Times parameters. Check whether the password meet the policy
requirements.
l Yes -> Step 3.
l No -> Step 2.
and maintenance items simultaneously. Enter the internal control password that meets
the requirements. Wait for 30 seconds, and check whether the alarm is cleared.
l Yes -> End.
2-124

l No -> Step 3.
2.76 2365980932 3 Consecutive Wrong Passwords

During Login
Alarm Description
The alarm is raised when a user enters wrong passwords for three times continuously.
Alarm Information
l Auto clear: Yes
Alarm Parameters
User Name Name of the user who is logged in.
Terminal Type Type of the terminal where the user is logged in.
l OMM Client
l Telnet Client
l EMS Client
l NDF Client
IP IP address of the terminal where the user is logged in.
Alarm Cause
A user has entered wrong passwords for three times.
Impact
When this alarm occurs on a client IP for many times, the client probably suffers from
malicious attacks of illegal users.
Action
1. Check whether an illegal user has attacked the system according to the User Name
and IP in the additional information of the alarm.
l Yes -> Step 2.
l No -> Step 3.
2. After running the SET USER command to set the password to be more complicated,
log in to the OMM system through correct username and password, and check whether
the alarm is cleared. To prevent account theft, modify the password periodically.
l Yes -> End.
2-125

l No -> Step 3.
2.77 2365980934 Interface Inner Control Account

Password Will Expire Soon
Alarm Description
The alarm is raised when an internal control account password of an interface is going
to be expired. Automatically created in the OMM system, the internal account is used for
data access in the system and file transmission as a public account. Accounts in the OMM
system are shared by several NEs.
Alarm Information
l Auto clear: Yes
Alarm Parameters

l UEP Account
l Admin Account
l NDF Account
l UMSFD Account
l Sysdba Account
Days Before The Password Is In- Days for reminding password expiry before the password
valid expires. The password expiry date depends on the last
Password Valid Day Depends on the last password modification date and password
validity period.
Alarm Cause
The Send Alarm or Not When Password Expired Is Or Not parameter is set to Yes for
the internal control password policy, and the Reminding Days Before Password Expired
parameter is not 0.The duration since the last time when the administrator modifies an
interface internal control account password has reached the threshold.
2-126

Impact
security activities.
Action
1. Run the SHOW IFPASSWDTACTIC command to check whether the Send Alarm or
l Yes -> Step 2.
l No -> Step 7.
network.
l Yes -> Step 4.
l No -> Step 3.
3. Run the SET IFPASSWDTACTIC command to disable the Send Alarm or Not When
l Yes -> End.
l No -> Step 7.
4. Check whether the Send Alarm or Not When Password Expired function is only
required when the password expires.
l Yes -> Step 5.
l No -> Step 6.
5. Run the SET IFPASSWDTACTIC command to set the Reminding Days Before
Password Expired parameter to 0, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
6. Run the SET IFACCOUNTPASSWD command to modify the internal control
password. This command is a dangerous command and cannot be executed with
other operation and maintenance items simultaneously. Wait for 30 seconds, and
check whether this alarm is cleared.
l Yes -> End.
l No -> Step 7.

Password Already Expired
Alarm Description
The alarm is raised when an internal control account password of an interface is expired.
Automatically created in the OMM system, the internal account is used for data access in
2-127

the system and file transmission as a public account. Accounts in the OMM system are
shared by several NEs.
Alarm Information
l Auto clear: Yes
Alarm Parameters

l UEP Account
l Admin Account
l NDF Account
l UMSFD Account
l Sysdba Account
Days Before The Password Is In- Password validity days

valid
Expired Days The days since the password is expired, which depends on the
last password modification date and password validity period.
Alarm Cause
The Send Alarm or Not When Password Expired Is Or Not parameter is set to Yes, but
the administrator does not modify the password before the password expires.
Impact
security activities.
Action
1. Run the SHOW IFPASSWDTACTIC command to check whether the Send Alarm or
l Yes -> Step 2.
l No -> Step 5.
network.
l Yes -> Step 4.
l No -> Step 3.
2-128

3. Run the SET IFPASSWDTACTIC command to disable the Send Alarm or Not When
l Yes -> End.
l No -> Step 5.
l Yes -> End.
l No -> Step 5.

Password Do Not Meet Requirements
Alarm Description
The alarm is raised when the internal control account password of an interface fails to meet
the requirements. Automatically created in the OMM system, the internal account is used
for data access in the system and file transmission as a public account. Accounts in the
OMM system are shared by several NEs.
Alarm Information
l Auto clear: Yes
Alarm Parameters

l UEP Account
l Admin Account
l NDF Account
l UMSFD Account
l Sysdba Account
Detailed Password Policy not Meet Passwords that fail to meet the password policies.
Alarm Cause
1. The length of an interface inner-control password is shorter than the Minimum Length
of Password parameter.
2-129

2. The length of an interface inner-control password is longer than the Maximum Length
of Password parameter.
3. The password complexity policy is enabled, but an interface internal control password
does not meet the policy.
4. The password history function is enabled, but an interface inner-control password is
the same as an old password that set in the Count of Latest Passwords Cannot Be
Reused parameter.
Impact
This alarm has no impact on normal OMM operation, but reminds the administrator to
modify the inner-control password to meet the requirements.
Action
1. Run the SHOW IFPASSWDTACTIC command to show the Min Length of Password,
Max Length of Password, Weak Password Check, and Can Not Use Recently
Used Password Times parameters. Check whether the password meet the policy
requirements.
l Yes -> Step 3.
l No -> Step 2.
l Yes -> End.
l No -> Step 3.
2.80 2365981185 OMM CPU Usage Rate Exceeds

Criterion
Alarm Description
The alarm is raised when the CPU usage of the OMM server exceeds the preset threshold.
Alarm Information
l Auto clear: Yes
2-130

Alarm Parameters
CPU Alarm CPU usage alarm threshold, which corresponds to the CPU Usage
Threshold Threshold(%) parameter queried by the SHOW CPUPARA command.
Current CPU Us- Current CPU usage. Use the average value if there are multiple usage values.
age Rate Unit:%.
Top 5 of CPU Us- Top five processes that have the highest CPU occupancy,
age such as CPURATE=6.0,PID=27759,COMMAND=omsser-
vice;CPURATE=1.0,PID=27996,COMMAND=fmservice;CPU-
RATE=0.0,PID=28958,COMMAND=bash;CPURATE=0.0,PID=28955,COM-
MAND=sshd;CPURATE=0.0,PID=28764,COMMAND=audispd. CPURate
indicates the current CPU usage of this process. PID indicates the process ID,
and COMMAND indicates the process name.
Alarm Cause
The monitoring switch of CPU resource monitoring parameters is enabled. This alarm
occurs when the number of times that the NMS CPU usage exceeds the preset threshold
for N times. N indicates Times of CPU Usage Exceeded Threshold which can be queried
by running the SET CPUPARA command.
1. Lots of performance statistics tasks are created in the OMM. The task statistics
granularity is too small, and task objects are too many.
2. Lots of alarms are reported.
3. The OMM is being backed up or recovered.
4. Too many maintenance operations on the OMM, for example, number allocations
through commands in batch mode.
5. At traffic peak, the CPU usage is high due to OMM server performance statistics and
signaling tracing.
6. The CPU monitoring parameter is configured improperly.
7. A signaling trace task that abundant messages are reported is created in the OMM.
Impact
This alarm may have the following impacts:
1. The OMM system fails to be installed or upgraded.
2. The OMM system cannot be logged in to.
3. The OMM system fails to record logs normally.
4. The OMM system fails to operate properly, which impacts operation and maintenance.
Action
1. Run the SHOW PMSYSTASK command to check whether there are lots of activated
performance tasks with small task granularities (5 minutes) and too many objects
(more than 500).
l Yes -> Step 2.
2-131

l No -> Step 3.
2. Run the SET PMSYSTASK to modify the performance statistics tasks based on actual
requirements to increase task granularities and reduce number of objects, and check
l Yes -> End.
l No -> Step 3.
3. Check whether a signaling tracing task containing mass messages (1000 per second)
is registered on the trace management page.
l Yes -> Step 4.
l No -> Step 5.
4. Stop or delete this task based on actual requirements, and check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 5.
5. Run SHOW CPUPARA command to Check whether the CPU Usage Threshold(%)
parameter (must be bigger than the CPU peak value because of other processes) is
set properly. The default threshold is 80%.
l Yes -> Step 7.
l No -> Step 6.
6. Run the SET CPUPARA command to modify the CPU alarm threshold, and check
l Yes -> End.
l No -> Step 7.
7. Check whether lots of alarms are reported on the fault management page.
l Yes -> Step 8.
l No -> Step 9
8. Recover the system based on reported faults, and check whether the alarm is cleared
after all fault symptoms disappear.
l Yes -> End.
l No -> Step 9
9. Check whether the number of NEs managed by the OMM server exceeds the planned
capacity defined in the system specification.
l Yes -> Step 10
l No -> Step 11
10. Modify the number of NEs in accordance with the system specification, and check
l Yes -> End.
l No -> Step 11
11. Check whether the CPU usage should be monitored. If high CPU usage is caused by
a special operation, the usage does not need to be monitored, for example, system
recovery and number allocation in batch mode.
l Yes -> Step 13
l No -> Step 12
12. Run the SET CPUPARA command to disable the Switch, and check whether the alarm
is cleared.
2-132

l Yes -> End.

l No -> Step 13
2.81 2365981186 OMM Memory Usage Rate Exceeds

Criterion
Alarm Description
The alarm is raised when the CPU usage of the OMM server exceeds the preset threshold.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Memory Alarm Threshold Memory usage alarm threshold, which corresponds to the
Memory Usage Threshold(%) parameter queried by the SHOW
MEMPARA command.
Current Memory Usage Rate Current memory usage, unit is %
Alarm Cause
The monitoring switch of memory resource monitoring parameters is enabled. This alarm
occurs when the number of times that the OMM memory usage exceeds the preset
threshold for N times. N indicates Times of Memory Usage Exceeded Threshold which
can be queried by running the SET MEMPARA command.
1. The memory monitoring parameter is configured improperly.

2. Number of NEs managed by the current OMM server exceeds the planned capacity
Impact
2-133

Action
1. Run SHOW MEMPARA command to Check whether the Memory Usage
Threshold(%) parameter (must be bigger than the memory peak value because of
other processes) is set properly. The default threshold is 80%.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET MEMPARA command to modify the Memory Usage Threshold(%), and
l Yes -> End.
l No -> Step 3.
3. Check whether the number of NEs managed by the OMM server exceeds the planned
capacity defined in the system specification.
l Yes -> Step 4.
l No -> Step 5.
4. Modify the configuration based on system requirements, and check whether the alarm
is cleared.
l Yes -> End.
l No -> Step 5.
5. Check whether the memory usage should be monitored. If high memory usage is
caused by a special operation, the usage does not need to be monitored, for example,
database backup and recovery.
l Yes -> Step 7.
l No -> Step 6.
6. Run the SET MEMPARA command to disable the Switch, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 7.
2.82 2365981187 OMM Hard Disk Usage Rate Exceeds

Criterion(Level 1 Alarm)
Alarm Description
The alarm is raised when the space usage of a specific partition exceeds the preset
threshold of the critical level.
Alarm Information
l Auto clear: Yes
2-134

Alarm Parameters
Partition Description Monitored object, which corresponds to the Partition Description parameter
queried by the SHOW PARTITIONPARA command.
Threshold(Critical) Monitoring threshold of the critical level, which corresponds to the Critical
Threshold parameter queried by the SHOW PARTITIONPARA command.
Usage Space Used space. If Monitoring by Absolution Value is selected from the
Monitoring Type list, this parameter corresponds to Usage Space(MB)
queried by the SHOW PARTITIONPARA command. If Monitoring by
Percentage is selected from the Monitoring Type list, this parameter
corresponds to Usage Space(MB)/Total Space(MB) queried by the SHOW
PARTITIONPARA command.
Alarm Cause
The monitoring switch is enabled in hard disk monitoring global parameter. For the
monitoring parameters of a partition, the Monitoring Type parameter is set to Monitoring
by Absolution Value (MB) or Monitoring by Percentage (%), and the Critical
Threshold parameter is not set to zero. When the system detects that the used space of
the partition exceeds the critical threshold value at the monitoring time, this alarm of the
partition is raised.
1. The performance data clearing period is set too long. The recommended clearing
period is seven days.
2. The alarm data cleanup period is set too long. The recommended cleanup period is
seven days.
3. The log data cleanup period is set too long. The recommended cleanup period is 60
days.
4. The Call History Record (CHR) saves logs for an overlong time.
5. Temporary files (performance files and alarm files) that are reported to the upper EMS
(for example, ZTE NetNumen) are saved for a long time.
6. The hard disk monitoring parameter is set improperly. The Critical Threshold is 90
% by default, which can be set by the SET PARTITIONPARA command.
Impact
Action
1. Run the SHOW PMCLEANPARA command to check whether the exporting and
clearing parameters of the performance data are set properly. If the performance data
2-135

query requires a long time, too much data is saved, and the Saving Days of Original
Data is set improperly. In this case, run the SET PMCLEANPARA command to
decrease the Saving Days of Original Data (Seven days is recommended). Check
whether the alarm is cleared after the daily scheduled data clearing task is performed.
l Yes -> End.
l No -> Step 2.
2. Run the SHOW FMCLEARPARA command to check whether the exporting and
clearing parameters of the alarm data are set properly. If the alarm data query
requires a long time, too much data is saved, and the Saving Days of Original Data
is set improperly. In this case, run the SET FMCLEANPARA command to decrease
the Saving Days of Original Data (30 days is recommended). Check whether the
alarm is cleared after the daily scheduled data clearing task is performed.
l Yes -> End.
l No -> Step 3.
3. Run the SHOW LOGCLEAR PARAM command to check whether the exporting and
clearing parameters of the log data are set properly. If the log data query requires a
long time, too much data is saved, and the Saving Days of Operation Log, Saving
Days of Security Log or Saving Days of System Log are set improperly. In this
case, run the SET LOGCLEANPARA command to decrease the saving days (60 days
is recommended). Check whether the alarm is cleared after the daily scheduled data
clearing task is performed.
l Yes -> End.
l No -> Step 4.
4. Run the SHOW PARTITIONPARA command to check whether the monitoring
thresholds for the hard disk partitions are set properly. (The Critical Threshold
threshold is 90% by default)
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET PARTITIONPARA command to modify the Critical Threshold, and
l Yes -> End.
l No -> Step 6.
6. Clear files on this disk to free disk space based on additional information and actual
requirements, ensure the hard disk usage is less than the Critical Threshold, and
l Yes -> End.
l No -> Step 7.
2-136


Alarm Description
threshold of the major level.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Threshold(Major) Monitoring threshold of the major level, which corresponds to the Critical
Alarm Cause
by Absolution Value (MB) or Monitoring by Percentage (%), and the Major Threshold
parameter is not set to zero. When the system detects that the used space of the partition
exceeds the major threshold value at the monitoring time, this alarm of the partition is
raised.
seven days.
days.
2-137

6. The hard disk monitoring parameter is set improperly. The Major Threshold is 90 %
by default, which can be set by the SET PARTITIONPARA command.
Impact
Action
l Yes -> End.
l No -> Step 2.
l Yes -> End.
l No -> Step 3.
l Yes -> End.
l No -> Step 4.
thresholds for the hard disk partitions are set properly. (The Major Threshold
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET PARTITIONPARA command to modify the Major Threshold, and check
l Yes -> End.
2-138

l No -> Step 6.
requirements, ensure the hard disk usage is less than the Major Threshold, and check
l Yes -> End.
l No -> Step 7.

Alarm Description
threshold of the minor level.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Threshold(Minor) Monitoring threshold of the minor level, which corresponds to the Critical
Alarm Cause
by Absolution Value (MB) or Monitoring by Percentage (%), and the Minor Threshold
parameter is not set to zero. When the system detects that the used space of the partition
exceeds the minor threshold value at the monitoring time, this alarm of the partition is
raised.
2-139

seven days.
days.
6. The hard disk monitoring parameter is set improperly. The Minor Threshold is 90 %
by default, which can be set by the SET PARTITIONPARA command.
Impact
Action
l Yes -> End.
l No -> Step 2.
l Yes -> End.
l No -> Step 3.
l Yes -> End.
2-140

l No -> Step 4.
4. Run the SHOW PARTITIONPARA command to check whether the monitoring thresh-
olds for the hard disk partitions are set properly. (The Minor Threshold threshold is
90% by default)
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET PARTITIONPARA command to modify the Minor Threshold, and check
l Yes -> End.
l No -> Step 6.
requirements, ensure the hard disk usage is less than the Minor Threshold, and check
l Yes -> End.
l No -> Step 7.

Alarm Description
threshold of the warning level.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Threshold(Warning) Monitoring threshold of the warning level, which corresponds to the Critical
2-141

Alarm Cause
by Absolution Value (MB) or Monitoring by Percentage (%), and the Warning
Threshold parameter is not set to zero. When the system detects that the used space of
the partition exceeds the warning threshold value at the monitoring time, this alarm of the
partition is raised.
seven days.
days.
6. The hard disk monitoring parameter is set improperly. The Warning Threshold is 90
% by default, which can be set by the SET PARTITIONPARA command.
Impact
Action
l Yes -> End.
l No -> Step 2.
l Yes -> End.
l No -> Step 3.
2-142

l Yes -> End.
l No -> Step 4.
thresholds for the hard disk partitions are set properly. (The Warning Threshold
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET PARTITIONPARA command to modify the Warning Threshold, and
l Yes -> End.
l No -> Step 6.
requirements, ensure the hard disk usage is less than the Warning Threshold, and
l Yes -> End.
l No -> Step 7.
2.86 2365981191 Directory Usage Rate Exceeds

Criterion (Level 1 Alarm)
Alarm Description
The alarm is raised when the size of files that meet the monitoring conditions in a specified
directory exceeds the preset monitoring threshold of the critical level.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Directory Description Monitoring object, which corresponds to Partition Description

2-143

File Type Monitored file type, which corresponds to File Type queried by the
SHOW DIRPARA command.
Is Include Sub-Directory Sets whether to include the files in sub-directories, which

corresponds to Whether Include Subdirectory queried by the
Threshold(Critical) Monitoring threshold of the critical level, which corresponds to the

Critical Threshold parameter queried by the SHOW DIRPARA
command.
Usage Space Total size of the files that meet the monitoring conditions. Unit: MB.
Alarm Cause
Configured in the monitoring parameter configuration of directory resources, a monitoring
object is uniquely defined by Directory Description, File Type, and Whether Include
Subdirectory. For a specific object, the Switch is On, and the Critical Threshold
parameter is not set to zero. When the system detects that the corresponding file size
exceeds the Critical Threshold parameter value at the monitoring time, this alarm is
generated for the object.
1. The usage of the directory that is being monitored is too high.
2. Directory monitoring parameters are configured improperly.
Impact
Impacts on the system depend on the monitored directories.
1. If the monitored directory is a system installation directory of the OMM system, this
alarm may have the following impacts:
l The OMM system fails to be installed or upgraded.
l The OMM system cannot be logged in to.
l The OMM system fails to record logs normally.
l The OMM system fails to operate properly, which impacts operation and
maintenance.
2. If the monitored directory is a data directory of the OMM system, the data may fail to be
recorded because of insufficient space, and thus the system cannot operate properly.
l If the data fails to be recorded, the data cannot be queried.
l If this alarm is caused by insufficient space, the subsequent addition, modification,
deletion, and query operation will fail.
3. If the monitored directory is a directory of other users, this alarm may result in data
modification and addition failures.
Action
1. Check the File Description in additional information. Run the SHOW DIRPARA
command to check whether the Switch of the directory resource monitoring parameter
of this directory is enabled, and whether the Period is set properly. The Period unit
2-144

is hour, and can be modified based on file variation status in monitoring directory. For
the directory that varies frequently, the monitoring period can be set shorter.
l Yes -> Step 2.
l No -> Step 7.
2. Check whether the directory resources are required to be monitored.
l Yes -> Step 4.
l No -> Step 3.
3. Run the SET DIRPARA command to disable the Switch in the corresponding
directory resource monitoring configuration (The directory resource monitoring is not
recommended to be disabled), and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
4. Run the SHOW DIRPARA command to check whether Critical Threshold of the
directory resource monitoring configuration are set properly based on monitoring
directory.
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET DIRPARA command to modify the Critical Threshold properly, and
l Yes -> End.
l No -> Step 6.
6. Clear files of a specified type in this directory to free disk space based on additional
information and actual requirements, ensure that the hard disk usage is less than the
Critical Threshold, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.

Alarm Description
directory exceeds the preset monitoring threshold of the major level.
Alarm Information
l Auto clear: Yes
2-145

Alarm Parameters

File Type Monitored file type, which corresponds to File Type queried by
the SHOW DIRPARA command.

Threshold(Major) Monitoring threshold of the major level, which corresponds

to the Major Threshold parameter queried by the SHOW
Usage Space Total size of the files that meet the monitoring conditions. Unit:
MB.
Alarm Cause
Subdirectory. For a specific object, the Switch is On, and the Major Threshold
exceeds the Major Threshold parameter value at the monitoring time, this alarm is
Impact
maintenance.
3. If the monitored directory is a directory of other users, this alarm may result in data
2-146

Action
l Yes -> Step 2.
l No -> Step 7.
l Yes -> Step 4.
l No -> Step 3.
l Yes -> End.
l No -> Step 7.
4. Run the SHOW DIRPARA command to check whether Major Threshold of the
directory.
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET DIRPARA command to modify the Major Threshold properly, and check
l Yes -> End.
l No -> Step 6.
Major Threshold, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.

Alarm Description
directory exceeds the preset monitoring threshold of the minor level.
Alarm Information
2-147

l Auto clear: Yes
Alarm Parameters
Directory Description Monitoring object, which corresponds to Partition Description queried

by the SHOW PARTITIONPARA command.
Is Include Sub-Directory Sets whether to include the files in sub-directories, which corresponds
to Whether Include Subdirectory queried by the SHOW DIRPARA
command.
Threshold(Minor) Monitoring threshold of the minor level, which corresponds to the

Minor Threshold parameter queried by the SHOW PARTITIONPARA
command.
Usage Space:%s Total size of the files that meet the monitoring conditions. Unit: MB.
Alarm Cause
Subdirectory. For a specific object, the Switch is On, and the Minor Threshold
exceeds the Minor Threshold parameter value at the monitoring time, this alarm is
Impact
maintenance.
3. If this monitoring directory is the directory of another user, user data may be added or
modified abnormally.
2-148

Action
l Yes -> Step 2.
l No -> Step 7.
l Yes -> Step 4.
l No -> Step 3.
l Yes -> End.
l No -> Step 7.
4. Run the SHOW DIRPARA command to check whether Minor Threshold of the
directory.
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET DIRPARA command to modify the Minor Threshold properly, and check
l Yes -> End.
l No -> Step 6.
Minor Threshold, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.

Alarm Description
directory exceeds the preset monitoring threshold of the warning level.
Alarm Information
2-149

l Auto clear: Yes
Alarm Parameters


Threshold(Warning) Monitoring threshold of the warning level, which corresponds

to the Warning Threshold parameter queried by the SHOW
Usage Space Total size of the files that meet the monitoring conditions. Unit:
MB.
Alarm Cause
Subdirectory. For a specific object, the monitoring Switch is On, and the Warning
Threshold parameter is not set to zero. When the system detects that the corresponding
file size exceeds the WWarning Threshold parameter value but is smaller than the Minor
Threshold parameter value at the monitoring time, this alarm is generated for the object.
Impact
maintenance.
2-150

3. If this monitoring directory is the directory of another user, this alarm may result in data
Action
l Yes -> Step 2.
l No -> Step 7.
l Yes -> Step 4.
l No -> Step 3.
l Yes -> End.
l No -> Step 7.
4. Run the SHOW DIRPARA command to check whether Warning Threshold of the
directory.
l Yes -> Step 6.
l No -> Step 5.
5. Run the SET DIRPARA command to modify the Warning Threshold properly, and
l Yes -> End.
l No -> Step 6.
Warning Threshold, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 7.
2.90 2365981200 Data File Usage Rate Exceeds

Alarm Description
Data file usage rate exceeds criterion (level 1 alarm)
2-151

Alarm Information
l Auto Clear: Yes
Alarm Cause
As for a particular object: the monitoring switch is ON, when the monitored corresponding
file size exceeds configured monitoring threshold of critical level at monitoring time spot,
it will trigger this level 1 alarm.
l Current data file size is too big.
l Storage time of temporary files is too long.
l The data file monitoring parameters are set improperly.
Impact
Too high data file usage leads to a decrease in query efficiency and data export efficiency.
Action
1. Check whether you set the parameters of exporting or clearing data properly, if too
long, set the monitoring threshold to a proper value.
l Yes->End.
l No-> Step 2.
2. Check whether you set the monitor thresholds properly by SHOW DBFILE PARA.
l Yes->Step 4.
l No-> Step 3.
3. Set the monitoring threshold to a proper value by SET DBFILE PARA.
l Yes->End.
l No-> Step 4.
4. Clear the data file to free sufficient space, and ensure it is smaller than the monitoring
threshold, and check whether the alarm is eliminated.
l Yes->End.
l No-> Step 5.

Alarm Description
Alarm Information
2-152


l Auto Clear: Yes
Alarm Cause
file size exceeds configured monitoring threshold of major level at monitoring time spot,
and it does not exceed the threshold of critical level (value 0 is not compared), it will trigger
this level 2 alarm.
Impact
Action
l Yes->End.
l No-> Step 2.
l Yes->Step 4.
l No-> Step 3.
l Yes->End.
l No-> Step 4.
l Yes->End.
l No-> Step 5.

Alarm Description
Alarm Information
2-153

l Auto Clear: Yes
Alarm Cause
file size exceeds configured monitoring threshold of common level at monitoring time spot,
and it does not exceed the threshold of major level (value 0 is not compared), it will trigger
this level 3 alarm.
Impact
Action
l Yes->End.
l No-> Step 2.
l Yes->Step 4.
l No-> Step 3.
l Yes->End.
l No-> Step 4.
l Yes->End.
l No-> Step 5.

Alarm Description
Alarm Information
l Auto Clear: Yes
2-154

Alarm Cause
file size exceeds configured monitoring threshold of warning level at monitoring time spot,
and it does not exceed the threshold of minor level (value 0 is not compared), it will trigger
this level 4 alarm.
Impact
Action
l Yes->End.
l No-> Step 2.
l Yes->Step 4.
l No-> Step 3.
l Yes->End.
l No-> Step 4.
l Yes->End.
l No-> Step 5.
2.94 2365981441 License File Illegal

Alarm Description
The alarm is raised when any of the following license files exists in the $ZXHOME/%NE%/
server/conf/license directory of the OMM server.
1. The user information in the license file is not the same as the license file name (suffix
not included).
2. The MAC address in the license file cannot match that of the OMM server network
card.
3. The license files that are not generated by license tools are in illegal format.
4. A damaged license file.
2-155

Alarm Information
l Auto clear: Yes
Alarm Cause
1. The user information in the license file is not the same with the license file name (suffix
not included).
2. The MAC address in the license file cannot match that of the OMM server network
card.
3. The license files that are not generated by license tools are in illegal format.
4. A damaged license file.
Impact
The license fails to be loaded, and all OMM or service functions controlled by the license
are unavailable.
Action
Contact ZTE technical support to provide another license file.
2.95 2365981443 License File Unavailable

Alarm Description
The alarm is raised when no license file exists in the $ZXHOME/%NE%/server/conf/l
icense directory of the OMM server.
Alarm Information
l Auto clear: Yes
Alarm Cause
The license file does not exist in the specified server directory.
Impact
are unavailable.
2-156

Action
1. Run the LOAD LICENSE command to import the license file, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Run the ls command to check whether the license file exists in the $ZXHOME/%NE%/
server/conf/license directory on the OMM server. The license file is in .lrc or
.LCS format.
l Yes -> Step 4.
l No -> Step 3.
3. Contact ZTE to obtain the license file again, upload the license file to the $ZXHOME/%N
E%/server/conf/license directory, run the LOAD LICENSE command to import
the license file, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.96 2365981444 Multiple License Files Exist

Alarm Description
When running the LOAD LICENSE command to load a license file, you find that multiple
licenses files exist in the $ZXHOME/%NE%/server/conf/license directory of the OMM
server, and this alarm is raised.
Alarm Information
l Auto clear: Yes
Alarm Cause
There are multiple license files in the specified server directory.
Impact
are unavailable.
Action
1. Run the ls command to check whether several license files exist in the $ZXHOME/%N
E%/server/conf/license directory on the OMM server. License files are in .lrc or
.LCS format.
l Yes -> Step 2.
l No -> Step 4.
2-157

2. Run the SHOW LICENSE command to query the license information, "User Info"
corresponds to correct license file name. Check whether the license name is the same
as that queried in Step 1.
l Yes -> Step 3.
l No -> Step 4.
3. Run the RM command to delete other license files in the license directory, and run
the LOAD LICENSE command to re-load the license. After running the commands,
l Yes -> End.
l No -> Step 4.
2.97 2365981445 Loaded License File Expires

Alarm Description
If a loaded license file expires, this alarm is raised when a client logs in to the OMM system
or at five 'o clock in the morning of the next day.
Alarm Information
l Auto clear: Yes
Alarm Cause
A license file loaded in the OMM system is expired
Impact
The license is unavailable, and all OMM or service functions controlled by the license are
unavailable.
Action
1. Run the SHOW LICENSE command to query the detailed license information, and
check whether the license is expired.
l Yes -> Step 2.
l No -> Step 3.
2. The license is expired. Contact ZTE technical support to upgrade the license file.
2-158

2.98 2365981697 Link Broken Between NE and OMM

Alarm Description
The alarm is raised when the OMM system detects that the link between the NE and the
OMM server is broken.
Alarm Information
l Alarm Type: Communications Alarm
l Auto clear: Yes
Alarm Parameters
opposite end IP IP address configured by the CREATE OMSLINK command.
port Port configured by the CREATE OMSLINK command.
Alarm Cause
1. The physical link between the OMM server and the NE is broken.
2. The IP address or the port of the NE configured on the OMM system is wrong.
Impact
The link between the NE and the OMM server is broken, and the OMM fails to perform
operation and maintenance on the NE. Meanwhile, the performance and alarm data of the
NE fails to be reported to the OMM.
Action
1. Based on the opposite end IP in the additional information, ping the opposite end
IP on the OMM server, and check whether the link between the OMM server and the
peer NE is normal.
l Yes -> Step 3.
l No -> Step 2.
2. Fix the physical network connection fault, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Run the SHOW OMSLINK command to query the node link information of the local
NE in the OMM system, and check whether the configured IP address and port are
the same as those of the connected peer NE.
l Yes -> Step 5.
l No -> Step 4.
4. Run the DELETE OMSLINK command to delete the wrong link, and run the CREATE
OMSLINK command to create a correct link. Check whether the alarm is cleared.
2-159

l Yes -> End.

l No -> Step 5.
2.99 2365981698 Link Broken Between Alarm Box and

OMM
Alarm Description
The alarm is raised when the OMM system detects that the link between the alarm box
and the OMM server is broken.
Alarm Information
l Auto clear: Yes
Alarm Parameters
AlarmBox IP Physical IP address of the peer alarm box connecting to the OMM system.
Alarm Cause
1. The alarm box is not connected.
2. The communication between the alarm box and the OMM server is interrupted.
Impact
Alarms cannot be displayed on the alarm box.
Action
1. Check whether the physical network connection between the disconnected node and
the OMM is normal.
l Yes -> Step 3.
l No -> Step 2.
2. Fix the physical network connection fault, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Run the SHOW ALARMBOX command to check whether the Server Port configured
on the OMM server is occupied, whether the alarm box address is consistent with the
Alarm Box IP on the OMM server, and whether the alarm box address is occupied.
l Yes -> Step 4.
l No -> Step 5.
2-160

4. Run the SET ALARMBOX command to modify the Server Port, and then check
l Yes -> End.
l No -> Step 5.
5. Run the SET ALARMBOX command to chage the Status to disable the alarm box on
the OMM server, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
2.100 2365981699 OMM change over success

Alarm Description
The alarm is raised when the OMM servers switch over. OMM servers may be switchover
manually or when the dual-server cluster software detects that the active OMM server is
faulty.
Alarm Information
l Auto clear: Yes
Alarm Parameters
None.
Alarm Cause
1. The administrator manually triggers the OMM server switchover by the dual-server
cluster software.
2. The cluster software detects a resource fault that cannot be removed, and triggers the
server switchover.
Impact
During the switchover, the data that the NE reports to the OMM may be lost, and OMM
commands cannot be executed on the EMS. If the switchover is successful, the system is
not affected.
Action
1. Access the Web page (http://xx.xx.xx.xx:29003, xx.xx.xx.xx is the IP address of the
OMM server) of the cluster management software through the IE browser. Check
whether the switchover is performed manually.
l Yes -> End.
l No -> Step 2.
2-161

2. Check the switchover causes on the Web page, and check whether the alarm is cleared
after troubleshooting the active server faults.
l Yes -> End.
l No -> Step 3.
2.101 2365981700 Link Broken Between Independent

Board and OMM
Alarm Description
An independent board refers to a functional board independent of NEs. For example, the
hardware management CMM board, clock board, and switch board. The alarm is raised
when the link between an independent board and the OMM server is broken.
Alarm Information
l Auto clear: Yes
Alarm Parameters
CMM IP IP address of the CMM board.
Alarm Cause
1. The physical link between the independent board and the OMM server is broken, for
example, the network interface fault, front and back board fault, the independent board
is not installed, or the network cable is not connected.
2. The independent board parameters are configured improperly.
3. The related independent board parameters are configured improperly on the OMM
system,
4. The independent board operates improperly.
Impact
The link between an independent board (such as CMM and switch board) and the OMM
system is broken, the board fails to report alarms, notification, and other information.
Action
1. Check whether the physical link between the independent board and the OMM server
is normal, for example, the network interface fault, front and back board fault, the
independent board is not installed, or the network cable is not connected.
2-162

l Yes -> Step 3.

l No -> Step 2.
2. Troubleshoot the link fault between the local OMM server and the independent board.
Wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Based on the independent board location in the additional alarm, run the SHOW
CMM command to check whether the board configuration is the same as the actual
configuration on the local maintenance terminal.
l Yes -> Step 5.
l No -> Step 4.
4. Run the SET CMM command to modify the CMM configuration. Wait for one minute,
l Yes -> End.
l No -> Step 5.
5. Check whether the independent board is operating properly. If The types of
independent boards are 11U, 14U, or 5U, refer to scheme A. If the types are 13U or
15U, refer to scheme B.
scheme A
1. Run the ping command to ping the independent board IP address on the OMM server
after querying the IP address by running SHOW FMSNMPCFG command. Access
the port 24 of the independent board by telnet with the username and password being
root, and check whether the OMM server can be pinged.
l Yes -> Step 2.
l No -> Verify that the network is normal.
2. Check whether the group name is the same with that of the independent board
configuration. Access the independent board by telnet, run the commands
one by one. Press the ? key to query the help information. For example,
run the following command for "CLI(ddm-snmp)#show ?": CLI(ddm-snmp)#show
snmp_community_config 128.0.0.0, which queries whether group name is the same
with that of the actual configuration.
l Yes -> Step 4.
l No -> Step 3.
3. Run the SET FMSNMPCFG command to modify the group name of the corresponding
independent board. Wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
4. Run the CLI(ddm-snmp)#show snmp_trap_address1_config command to query
the port (of the independent board) where traps message are reported. Traps
messages can be sent up to five IP addresses (snmp_trap_address1_config,
snmp_trap_address2_config, snmp_trap_address3_config,
snmp_trap_address4_config and snmp_trap_address5_config). Check whether a
configuration item for trap message reports exists on port 162 of the OMM server.
l Yes -> Step 6.
2-163

l No -> Step 5.
5. Run the CLI(ddm-snmp)#snmp_trap_address1_config 10.44.129.43 162 command to the
configuration item for trap message reports on port 162. Wait for one minute, and
l Yes -> End.
l No -> Step 6.
6. Run the CLI(ddm-snmp)#show snmp_trap_enable_config command to check whether
the trap function is available. If TRAP_ENABLE is returned, the function is available.
l Yes -> Step 8.
l No -> Step 7.
7. Run the CLI(ddm-snmp)#snmp_trap_enable_config TRAP_ENABLE command to
configure the trap availability. Wait for one minute, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 8.
scheme B
13U/15U independent boards need to be restarted to make configuration effective. As a
result, you are recommended to restart the board after all configurations are confirmed.
1. Run the ping command to ping the independent board IP address on the OMM
server after querying the Independent Board IP by running SHOW FMSNMPCFG
command. Access the independent board by telnet without specifying the port (Both
the username and password are zte), ping the OMM server to check whether it can
be pinged.
l Yes -> Step 2.
l No -> Verify that the network is normal.
2. In the configuration file /FLASH0/snmp/conf/snmpd.conf, check whether the
corresponding network section of IP addresses used for communication between the
NMS and independent boards is existed. The network section should be configured
in the following format: com2sec mynetwork NetworkSection/BitsOfMask
CommunityName (for examle, com2sec mynetwork 129.1.1.0/24 public).
NetworkSection is the network section used for communication between the NMS
and independent boards. For example, the NMS address is 129.1.1.1/255.255.255.0
(An OMM server may have several addresses, this address must be abled to
pinged on the CMM), NetworkSection/BitsOfMask should be 129.1.1.0/24.
CommunityName is the actual community name.
l Yes -> Step 4.
l No -> Step 3.
3. Add an address of the OMM server. Add com2sec mynetwork
NetworkSection/BitsOfMask CommunityName below the com2sec mynetwork
……in the configuration file. CommunityName must be the same as SNMP Read
Comunity queried by the SHOW FMSNMPCFG command, and public is not
recommended.
2-164

4. Check /FLASH0/snmp/conf/snmpd.conf to see whether the configuration

file has configured to report trap messages to the OMM server in the format of
trapsink NMSAddress:TrapReportPortID (for examle, trapsink 129.1.1.1:162 ).
NMSAddress is the IP address of the OMM server used for communication between
the OMM server and the independent board.
l Yes -> End.
l No -> Step 5.
5. Add the configuration that trap messages are sent to the OMM server in
configuration files, which means to add trapsink NMSAddress:TrapReportPortID.
TrapReportPortID is usually set to 162, which can be modified based on actual
conditions.
Note:
Trap messages can be sent up to five addresses. If a sixth address is set, this address
is unavailable.
6. Restart the independent board. Wait for one minute, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 7.
2.102 2365981701 Slave OMM Server Unavailable

Alarm Description
The standby OMC server is unavailable.
Alarm Information
l Alarm Type: Communication alarm
l Auto Clear: Yes
Alarm Cause
l The standby OMC server does not operate properly.
l Power is not supplied to the standby OMC server or the standby OMC server is
removed.
l Communication with the standby OMC server is abnormal.
l The cluster software does not operate properly.
2-165

Impact
The standby OMC server is unavailable. Reliable services cannot be provided through
active/standby switchover, and daily operation and maintenance is affected.
Action
1. Check whether the power supply of the standby server blade is down.
l Yes -> Step 2.
l No -> Step 3.
2. Supply power to the standby server blade. Wait 2–3 minutes, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether the cluster networking mode complies with the plan. If not, modify the
cluster networking mode. Wait 2–3 minutes, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.103 2365981703 SNMP Configuration Inconsistent

with Independent Board
Alarm Description
The alarm is raised when the SNMP group name or the type of the independent board
is not the same as that configured on the independent board. You can query the SNMP
board information by running the ADD FMSNMPCFG or SET FMSNMPCFG command.
Alarm Information
l Auto clear: Yes
Alarm Cause
1. The IP address or the read community name of the independent board is inconsistent
with the SNMP configuration on the board.
2. The SNMP configuration on the board is wrong. The OMM server is not allowed to
access the board.
Impact
This configuration is used by the fault management module to initiatively obtain information
from independent boards. If the SNMP is configured improperly, alarms cannot be
2-166

synchronized with this board, and thus alarms of this board displayed on the OMM do not
disagree with the actual alarms.
Action
1. Based on the IP address of the independent board in addition information, run the
SHOW CMM command to query CMM configuration, and then run the SHOW FMSNM
PCFG command to query the SNMP configurations. Check whether the IP addresses,
SNMP read community names, and independent board types of the two commands
are the same.
l Yes -> Step 3.
l No -> Step 2.
2. If the community name is wrong, run the SET FMSNMPCFG command to correct the
community name. If the IP address is wrong, run the DEL FMSNMPCFG command to
delete the wrong board configuration, and then run the ADD FMSNMPCFG command
to add the correct one. Wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
2.104 2365981704 Insufficient Space on OMM Hard

Disk and Newly Reported Data Will Be Dropped
Alarm Description
New reported OMM data is not saved when the space of the hard disk where historical
OMM data is saved is insufficient.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Hard Disk Partition Name Name of the partition of the faulty OMM hard disk.
Size Left(Unit:M) Remaining space of the partition of the faulty partition.
Discard Data Type of the data discarded on the partition.

l Cleared Alarms and Notifications
l Performance Data
2-167

Alarm Cause
The remaining space of the hard disk where OMM server data is saved is insufficient. By
default, this alarm is raised when the remaining space is 1 G. At this time, the performance
and alarm data cannot be written into the database.
Impact
The corresponding data of the discard policy of the additional information is not saved. For
example, if the discarded data is a historical alarm and notification, all subsequent reported
notifications will not be saved into the notification database since the alarm occurs, and
all cleared alarms will not be saved into the historical alarm database until the remaining
space exceeds the preset monitoring threshold. Unsaved data cannot be queried.
Action
1. According to the partition information shown in the additional information of this alarm,
run the rm command to delete useless files (not the OMM system data) in the partition,
restart the NMS, and then check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2.105 2365981953 Link Broken Between NTP Server

and OMM
Alarm Description
The alarm is raised when the link between the OMM server and the upper-layer NTP server
is broken.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Failed NTP IP IP address of the peer NTP server where an alarm occur.
Port Port associated with the IP address of the upper-layer NTP service.
Alarm Cause
Cannot receive the NTP acknowledgement messages from the upper-layer NTP server.
The probable causes are as follows:
2-168

1. The NTP service of the NTP server is not started.

2. A fault occurs on the network between the local OMM server and the upper-layer OMM
server.
3. The NTP client parameters are configured incorrectly on the local maintenance termi-
nal, such as the upper-layer NTP server address, and port number.
4. The firewall setting of the local OMM server or that of the upper-layer OMM server is
wrong.
Impact
The local system time cannot be updated, and thus the time of related functional modules
depending on the system time is asynchronized.
Action
1. Based on the NTP server information in the additional information, contact upper-layer
NTP server maintenance personnel to check whether the NTP server is operating
properly.
l Yes -> Step 3.
l No -> Step 2.
2. Start the NTP service of the upper-layer NTP server, and run the SYNC NTPTIME
command to forcibly synchronize the NTP time. Check whether the alarm is cleared.
l Yes -> End.
l No -> Step 3.
3. Check whether the link between the local OMM server and the upper-layer NTP server
is normal.
l Yes -> Step 5.
l No -> Step 4.
4. Verify that the link is normal, and run the SYNC NTPTIME to forcibly synchronize the
NTP time. Check whether the alarm is cleared.
l Yes -> End.
l No -> Step 5.
5. Run the SHOW SNTPCLNT command to check the NTP client configuration on the
OMM server is the same as that on the peer NTP server.
l Yes -> Step 7.
l No -> Step 6.
6. Run the SET SNTPCLNT command to modify the NTP client configuration, run the
SYNC NTPTIME command to forcibly synchronize the NTP time, and check whether
l Yes -> End.
l No -> Step 7.
7. Check whether the firewall of the local OMM server or that of the upper-layer network
management server restricts the IP address and port number configured for the NTP
client.
l Yes -> Step 8.
l No -> Step 9.
2-169

8. Modify the firewall settings, and cancel the restriction on IP and ports. Run the SYNC
NTPTIME command to forcibly synchronize the NTP time, and check whether the
alarm is cleared.
l Yes -> End.
l No -> Step 9.
2.106 2365981954 Time of NTP Server Unsynchronized

Alarm Description
The alarm is raised when the system detects that the NTP server sends back a status
message, indicating that the server is in asynchronous time status.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Failed NTP Server IP IP address of the peer NTP server where an alarm occur.
Alarm Cause
The link between the OMM server and the superior NTP server is normal, but the NTP
server time goes out of sync with the external clock source.
Impact
Action
1. Based on the NTP server information in the additional information, contact upper-layer
NTP server maintenance personnel to recover the NTP service and synchronize
external clock resources. Run the SYNC NTPTIME command to forcibly synchronize
the NTP time, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2. Run the SHOW SYSLOG:FUNCNAME="NTP" command to check whether there is a
detailed error description of the NTP time unsynchronized.
l Yes -> Step 3.
l No -> Step 4.
2-170

3. Handle the alarm based on the log descriptions, and check whether the alarm is
cleared.
l Yes -> End.
l No -> Step 4.
2.107 2365981955 NTP Clock Offset Over Maximum

Threshold
Alarm Description
The alarm is raised when the NTP time deviation on the OMM server exceeds the maximum
threshold.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Failed NTP Server IP IP address of the peer NTP server where time is synchronized.
Max Threshold Maximum difference of the local time.
Current Time Offset Time difference between the local time and the time of the upper-layer
NTP server of the specified IP address.
Alarm Cause
The probable alarm causes are as follows:
1. The local OMM server time is not calibrated.
2. The upper-layer NTP server time hops.
3. The local OMM server time hops.
Impact
Action
1. On the local maintenance terminal, run the SYNC NTPTIME to forcibly synchronize
the NTP time, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 2.
2-171

2. Run the SHOW SYSLOG:FUNCNAME="NTP" command to check whether there is a

detailed error description of the maximum threshold of the NTP time deviation.
l Yes -> Step 3.
l No -> Step 4.
3. Run the SET SNTPCLNT command to modify the Minimum Threshold and
Maximum Threshold of the local NTP client parameters. Run the SYNC NTPTIME
command forcibly synchronize the NTP time, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 4.
2.108 2365981956 Synchronize NTP Time Failed

Alarm Description
Synchronize NTP time failed.
Alarm Information
l Alarm Type: Equipment alarm
l Auto Clear: Yes
Alarm Cause
The superior NTP server fails, and the superior standby NTP server is switched to the
current superior NTP server automatically.
Impact
The superior NTP server fails.
Action
Check the communication link and service state of the faulty superior NTP server. Run the
SHOW SYSLOG:FUNCNAME="NTP"; command on the command terminal to check the
detailed descriptions.
2.109 2365982209 Automatic Backup Failed

Alarm Description
The alarm is raised when the OMM server fails to perform the automatic task backup
function.
2-172

Alarm Information
l Auto clear: Yes
Alarm Parameters
Log ID Unique log backup ID, which corresponds to the input

parameter queried by the SHOW BAKLOG command.
Automatic Backup Task ID Unique automatic backup task ID, which corresponds to the
input parameter queried by the SHOW AUTO STRATEGY
command.
Alarm Cause
An automatic backup task of the OMM server fails.
Impact
An automatic backup task fails.
Action
Based on the backup Log ID in additional information, run the SHOW BAKLOG command
to query the causes of automatic backup failure, and Contact ZTE technical support.
2.110 ALM-2399577346 Unavailable SIP Link

Alarm Description
The SIP link is unavailable
Alarm Property
Alarm ID Alarm Level Alarm System Type Alarm Type
2399577346 Minor alarm NE alarm Communication alarm
Impact on the System

You can configure several SIP links between CSCF NE and its opposite NE. When one
SIP link is faulty, messages on it will be moved to other links for handling, and then CSCF
can communicate with its opposite NE normally. In case of abundant registration and
calls, available links become less, which results in low data transmission capacity and low
system reliability.
2-173

If all SIP links are faulty, CSCF fails to communicate with its opposite NE, and registration
and calls will be failed.
Probable Causes
l Route between local entity and opposite equipment is failed.
l The network cable is loose or connects improperly.
l The SIP link data is set improperly.
l The remote equipment is abnormal.
Troubleshooting Suggestions
1. Enter the protocol mode by running the IPSTACK command, and check whether
network connection to the opposite network is normal by running the PING command
and exit this mode by running the EXIT MODE command.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Check whether the network cables between rear boards, switch and OMP board are
loose or detached, if so, insert the cable into position, and check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether the SIP link configuration complies with the planning by running the SH
OW SIP LINK command. Pay much attention to the bearer protocol type, connection
ID, and adjacent host ID.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Modify the SIP link by running the SET SIP LINK command, and check whether the
alarm is cleared.
l Y->End.
l N->Go to Step 5.
5. Check whether Link Blocked is set to Yes in SIP link configuration by running the
SHOW SIP LINK command.
l Y->Go to Step 7.
l N->Go to Step 6.
6. Check whether it is necessary to block the link.
l Y->End.
l N->Go to Step 7.
7. Modify Link Blocked to Yes in SIP link configuration by running the SET SIP LINK
command. Check whether the alarm is cleared.
l Y->End.
l N->Go to Step 8.
8. Modify Heartbeat Mode to Voluntary in SIP link configuration by running the SET SIP
LINK command. Select Signaling Trace > Trace by Link to check whether any local
NE sends the OPTIONS message and the peer NE returns response 200.
l The local end does not send an OPTIONS message->Go to Step 9.
2-174

l The peer end does not return a 200 response->Go to Step 11.
9. Check whether the configured SIP access address complies with the planning by
running the SHOW SIP ACCADDR command.
l Y->Go to Step 12.
l N->Go to Step 10.
10. Delete the old configuration by running the DEL SIP ACCADDR command. Add SIP
access address configuration according to the planning by running the ADD SIP ACC
ADDR command. Check whether the alarm is cleared.
l Y->End.
l N->Go to Step 12.
11. Modify the configuration of the peer NE. Check whether the alarm is cleared.
l Y->End.
l N->Go to Step 12.
2.111 ALM-2399577349 SIP SCTP Association Not

Established
Alarm Description
The SIP SCTP association is not established
Alarm Property

Link will be disconnected, and SIP messages cannot be transferred between local CSCF
NE and specified opposite equipment, which impacts normal registration and calls.
Probable Causes
l Route between local entity and opposite equipment is failed.
l The network cable is loose or connects improperly.
l The SIP SCTP data is configured improperly.
l The remote equipment is abnormal.
1. Enter the protocol stack mode by running the IPSTACK command, and check opposite
network connection by running the PING command, for example, opposite IP address
is 10.6.6.21, PING:ADDRESS="10.6.6.21";, and exit this mode by running the EXIT
MODE command.
l Y->Go to Step 3.
2-175

l N->Go to Step 2.
2. Check whether the network cables between rear boards, switch and OMP board are
loose or detached, if so, insert the cable into position, and check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether the opposite IP address, opposite port ID and protocol type agree with
the planned value by running the SHOW SIPSCTP command.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Modify the SCTP association to the planned values by running the SET SIPSCTP
command and check whether the alarm is restored.
l Y->End.
l N->Go to Step 5.
5. Check whether the SCTP configuration of the opposite equipment is consistent with
the planning.
l Y->Go to Step 7.
l N->Go to Step 6.
6. Modify related SCTP configuration of the opposite equipment, and check whether the
alarm is cleared.
l Y->End.
l N->Go to Step 7.
2.112 ALM-2399577351 Adjacent Host Unavailable

Alarm Description
The adjacent host is unavailable.
Alarm Property
Alarm ID Alarm Severity Alarm System Type Alarm Type

The adjacent host is unavailable.
Probable Causes
l The adjacent host name is set, but the static link is not associated, and the adjacent
host is unavailable.
l The adjacent host found by the DNS dynamically is unavailable.
2-176

1. On the Local Maintenance Terminal page, select Professional Maintenance > Host
Maintenance > Show Adjacent Host Information, set Adjacent Host Name and
check whether the physical status in the command result is available.
l Y->Go to Step 9.
l N->Go to Step 2.
2. Select Configuration Management > Topology Configuration > Adjacent Host
Configuration > Show Adjacent Host, check whether the host name in the command
result agrees with that of the planning.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Modify the configurations according to the planning, and check whether the status is
available.
l Y->End.
l N->Go to Step 4.
4. Check whether the DNS server is configured properly.
l Y->Go to Step 5.
l N->Go to Step 6.
5. Enable the heartbeat function, and select Signalling Trace > Trace by User, check
whether the heartbeat detection receives the 200 OK response of the configuration
(Times of Successful Detection to Judge Host Available).
l Y->Go to Step 8.
l N->Go to Step 7.
6. Contact maintenance personnel of the DNS server to modify its configurations.
l Y->Go to Step 4.
l N->Go to Step 9.
7. Contact the maintenance personnel of the opposite NE, check whether the opposite
NE is configured properly, if not, modify the configuration.
l Y->Go to Step 5.
l N->Go to Step 9.
8. The heartbeat detection receives 200 OK response, check whether the status
becomes available.
l Y->End.
l N->Go to Step 9.
2.113 ALM-2399839489 SIP Socket Error

Alarm Description
The SIP socket port is unavailable
2-177

Alarm Property

The socket port in abnormal status is unavailable.
Probable Causes
l The SIP access address is inconsistent with the planning.
l The TCP configuration is inconsistent with the planning.
l The UDP configuration is inconsistent with the planning.
1. Check whether SIP access address is consistent with the planning by SHOW SIP AC
CADDR.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Remove previous settings by DEL SIP ACCADDR, and configure the SIP access
address according to the planning by ADD SIP ACCADDR, and check whether the
alarm is eliminated.
l Y->End.
l N->Go to Step 3.
3. Check whether TCP configuration is consistent with the planning by SHOW TCPCON
N.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Modify TCP configuration according to the planning by SET TCPCONN, and check
whether the alarm is eliminated.
l Y->End.
l N->Go to Step 5.
5. Check whether UDP configuration is consistent with the planning by SHOW UDPCO
NN.
l Y->Go to Step 7.
l N->Go to Step 6.
6. Modify UDP configuration according to the planning by SET UDPCONN, and check
l Y->End.
l N->Go to Step 7.
2-178

2.114 ALM-2399734018 DIAMETER Static Link Not

Established or Link Broken
Alarm Description
The DIAMETER link is established in failure or interrupted.
Alarm Property
2399734018 Critical alarm NE alarm Communication alarm

Messages cannot be received or sent between CSCF and CG, which results in CG fails
to carry out normal charging function. When the subscribers wait to be charged, CG will
not charge them, which cause commercial loss. Meanwhile, P-CSCF cannot send AAR
requests to PCRF for IMS service control.
Probable Causes
l The network communication is interrupted.
l The connection data configuration is inaccurate, such as host name, address, and
capability.
l The link is blocked.
1. Check network connections.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Troubleshoot network connection, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether the DIAMETER link is configured properly by running the SHOW DIM
LINK command.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Modify the DIAMETER link configuration by running the SET DIM LINK command,
refer to instruction of DIAMETER link configuration, and check whether the alarm is
restored.
l Y->End.
l N->Go to Step 5.
5. Check whether common capacity or special capacity match that of the remote end by
running the SHOW DIM LINKCNMON command and SHOW DIM LINKSPECIFIC
command.
2-179

l Y->Go to Step 7.
l N->Go to Step 6.
6. Modify common capacity or special capacity by running the SHOW DIM LINKCNMO
N command and SET DIM LINKSPECIFIC command, and check whether the alarm
is cleared.
l Y->End.
l N->Go to Step 7.
7. Check whether the link is blocked by running the SHOW DIMLNKSTAT command.
l Y->Go to Step 8.
l N->Go to Step 9.
8. Check whether it is required to unblock the link, if so, unblock the link by running the
UNBLOCK DIMLINK command, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 9.
2.115 ALM-2399734024 DIAMETER Dynamic Link Not

Established or Link Broken
Alarm Description
DIAMETER dynamic link not established or link broken.
Alarm Property
Alarm Code Alarm Severity System Type Alarm Type
2399734024 Critical alarm NE alarm Communication alarm

The DIAMETER link is broken, and the service messages based on the DIAMETER
protocol stack fail to be sent or received between the CSCF NE and CG NE. The CG
NE cannot receive charging request messages from the CSCF NE. As a result, charging
cannot be performed, which may cause commercial loss. The P-CSCF NE cannot send
AAR requests to the PCRF for IMS service control.
Probable Causes
l The network communication is interrupted.
l The connection data configuration is inaccurate, such as host name, address,
capability and etc.
1. Check network connections.
l Y->Go to Step 3.
2-180

l N->Go to Step 2.
2. Troubleshoot network connection, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 3.
3. Check whether the local for the client.
l Y->Go to Step 4.
l N->Go to Step 8.
4. Check whether the DIAMETER link is configured properly by SHOW DIM LINK.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Modify the DIAMETER link configuration by SET DIM LINK, refer to instruction of
DIAMETER link configuration, and check whether the alarm is restored.
l Y->End.
l N->Go to Step 6.
6. Check whether common capacity and special capacity match that of the remote end
by SHOW DIM LINKCOMMON and SHOW DIM LINKSPECIFIC.
l Y->Go to Step 12.
l N->Go to Step 7.
7. Modify common capacity and special capacity by SET DIM LINKCOMMON and SET
DIM LINKSPECIFIC, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 12.
8. Check whether the DIAMETER link is configured properly by SHOW DIM DYNLINK
CFG and SHOW DIM DYNPEER.
l Y->Go to Step 10.
l N->Go to Step 9.
9. Modify the DIAMETER link configuration by SET DIM DYNLINKCFG and SET DIM
DYNPEER, refer to instruction of DIAMETER link configuration, and check whether
the alarm is restored.
l Y->End.
l N->Go to Step 10.
10. Check whether local end capacity match that of the remote end by SHOW DIM LOC
CAP.
l Y->Go to Step 12.
l N->Go to Step 11.
11. Modify local end capacity by SET DIM LOCCAP, and check whether the alarm is
eliminated.
l Y->End.
l N->Go to Step 12.
2-181

2.116 ALM-2399799297 DIAMETER Protocol Stack

Session Resource Exhausted
Alarm Description
The DIAMETER protocol stack session resource is exhausted
Alarm Property
2399799297 Critical alarm NE alarm Processing error alarm

The DIAMETER protocol stack fails to operate temporarily, the CG fails to perform
charging, and the PCRF fails to control the IMS services.
The CSCF sends a charging ACR request message to the DIAMETER protocol stack, and
meantime, the protocol stack session resources is exhausted. As a result, the protocol
stack fails to accept or handle new messages, the CG NE cannot receive the ACRs and
thus cannot perform the charging functions, which finally results in commercial loss.
Likewise, the P-CSCF NM fails to send the AAR request to PCRF for IMS service control.
Probable Causes
l After a burst traffic peak, the DIAMETER protocol stack resource is exhausted.
l The DIAMETER protocol stack saves too much long sessions, including IMS service
control and charging session.
à The session resources will stay in the DIAMETER protocol stack for the charging
service. If the charging session number generated by the CSCF NE exceeds the
maximum session resource capacity of the protocol stack, this alarm is raised.
à The session resources will stay in the DIAMETER protocol stack for the IMS
control service. If the IMS service control session number generated by the
PCSCF NE exceeds the maximum session resource capacity of the protocol
stack, this alarm is raised.
l The CSCF NE fails to release the DIAMETER protocol stack session.

à If you want to complete a charging session, the CSCF NE will send messages
to the DIAMETER protocol stack for session release, and the released session
resources will be re-allocated. If CSCF fails to send the release message to
the protocol stack, the session will remain existing, you can only release the call
by handling the protocol timeout. If there are too many sessions unreleased,
the newly-generated sessions could reach the alarm threshold and an alarm is
raised.
2-182

à If you want to finish the IMS control service session, the PCSCF NE will send
messages to the DIAMETER protocol stack for session release, and the released
session resources will be re-allocated. If CSCF fails to send the release message
to the protocol stack, the session will remain existing, you can only release the
call by handling the protocol timeout. If there are too many sessions unreleased,
the newly-generated sessions could reach the alarm threshold and an alarm is
raised.
1. Check whether the traffic rises suddenly in the performance statistics.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Wait for the end of the burst traffic peak, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 3.
3. There is a timer detection in the default protocol stack configuration. If a call times out,
the call will be released. There is no need for manual intervention. Wait for 10 minutes
after the traffic peak ends, check whether the alarm is cleared.
l Y->End.
l N->Go to Step 4.
2.117 ALM-2399799305 DIAMETER Dialog Resource of

Application Interface Is Exhausted
Alarm Description
The Diameter DEP dialog resource of application interface is exhausted.
Alarm Property
2399799305 Major alarm NE alarm Processing error alarm

Before the session resource is released, the Diameter protocol stack fails to handle the
session establishment request of this application interface.
Probable Causes
The number of the sessions created by the system reach the upper limit threshold.
2-183

1. Check whether the traffic rises suddenly in the performance statistics.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Wait for the end of the burst traffic peak, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 3.
3. There is a timer detection in the default protocol stack configuration, and no need for
manual intervention. Wait for 10 minutes after the traffic peak ends, check whether
l Y->End.
l N->Go to Step 4.
4. Increase the session capacity percentage of the application interface by running the
SET DIM APPTYPECAPA command, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 5.
5. Extend capacity by running the SET MODCAPA command, restart the system, and
l Y->End.
l N->Go to Step 6.
2.118 ALM-2399799808 Necessary Data Unavailable to

DIAMETER Protocol Stack
Alarm Description
The Diameter protocol cannot obtain the necessary data.
Alarm Property
2399799808 Major alarm NE alarm Communication alarm

The DIAMETER protocol stack cannot operate properly. DIAMETER links cannot be
established. Messages cannot be sent or received between the CSCF and the CG. The
CG cannot perform the charging function successfully because it does not receive a
charging request from the CSCF, which results in commercial loss. The PCSCF cannot
send an AAR to the PCRF for IMS service control.
Probable Cause
l The DIAMETER protocol stack is not configured with product information data.
2-184

l The DIAMETER protocol stack is not configured with link data.

l The DIAMETER protocol stack is not configured with route data.
Handling Suggestions
1. Check whether the Diameter protocol is configured properly by running the SHOW
DIM GLOBAL command.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Add or modify the configuration of the Diameter protocol by running the ADD DIM
GLOBAL command or SET DIM GLOBAL command. Check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether the Diameter link is configured properly by running the SHOW DIM
LINK command.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Add or modify the configuration of the Diameter link configuration by running the AD
D DIM LINK command or SET DIM LINK command. Check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 5.
5. Check whether the Diameter route is configured properly by running the SHOW DIM
ROUTE command.
l Y->Go to Step 7.
l N->Go to Step 6.
6. Add or modify the configuration of the Diameter route configuration by running the ADD
DIM ROUTE command or SET DIM ROUTE command. Check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 7.
7. Contact the ZTE technical support.
2.119 ALM-2399842305 SIP Fails to Obtain

Configuration During Power-on
Alarm Description
The SIP fails to obtain configuration during power-on
Alarm Property
2399842305 Critical alarm NE alarm Equipment alarm
2-185


This alarm will result in SIP module launching failure, the CSCF NE fails to operate properly
and related SIP processes cannot exchange messages. Moreover, all SIP-related services
cannot be carried out and the system is not operating. You cannot use related SIP signaling
tracing or failure observation.
Probable Causes
Configuration error
l The related SIP data area capacity is configured to 0, for example, the SIP TULEG
data area is set to 0.
l Communication between NM server and OMP module is abnormal, which results in
NM data failed to be synchronized to the OMP module.
1. Check communication between NM server and OMP module, and check whether
ALM-2365981697 Link Broken Between NE and OMM is reported.
l Y->Refer to the troubleshooting suggestions of the ALM-2365981697 Link
Broken Between NE and OMM.
l N->Go to Step 2.
2. Query corresponding module capacity configurations by SHOW MODCAPA command
according to the module number in logic resource location information, and check
whether the capacity parameter is consistent with the planned values.
l Y->Go to Step 4.
l N->Go to Step 3.
3. Modify the module capacity configuration according to the plan by running the SET
MODCAPA command. Restart the board by running the RESET NORMAL command
l Y->End.
l N->Go to Step 4.
Warning!
Restart the board to make above configurations effective. Do not restart the board
during busy hours.
2-186

2.120 ALM-2399842306 Failed to Power on the SIP

Process
Alarm Description
Failed to power on the SIP process
Alarm Property

SIP process power-on failure will result in SIP module launching failure, the CSCF NE fails
to operate properly and related SIP processes cannot exchange messages. Moreover, all
SIP-related services cannot be carried out and the system is not operating. You cannot
use related SIP signaling tracing or failure observation.
Probable Causes
l The module capacity is set too large (exceeds the planned configuration), and thus
the occupied memory exceeds the available board memory. When powering on the
system, you find the memory is insufficient during launching the charging module. An
alarm is raised.
l The module data area capacity is set too large (exceeds the planned configuration),
and thus the occupied memory exceeds the available board memory. When powering
on the system, you find the memory is insufficient during launching the charging
module. An alarm is raised.
l The physical memory hardware is damaged. Failed to find the memory or the memory
is insufficient during system power-on, the system fails to be started. This alarm is
raised.
1. Query corresponding module capacity configuration by SHOW MODCAPA command
l Y->Go to Step 3.
l N->Go to Step 2.
MODCAPA command. Restart the board by running the RESET NORMAL command,
l Y->End.
l N->Go to Step 3.
2-187

Warning!
Restart the board to make above configurations effective. Do not restart the board in
busy hours.
2.121 ALM-3154247681 Failed to Launch the System

Alarm Description
System boot failure
Alarm Property

Each module implements different functions independently. The entire system can
realize various services required by customers on condition that every module operate
properly. Each module is deployed with many processes in which the functional data
area implements the services. "Failed to Launch the System" indicates that one or more
modules fail to be launched. If the modules belong to special service module rather than
general modules, the special services cannot be implemented, such as session control
service; if this module belongs to general module, even the basic services cannot be
implemented either.
Probable Causes
l The module capacity is set too large (exceeds the planned configuration), and thus
charging module, you find the memory is insufficient during launching the charging
l The module data area is set too large (exceeds the planned configuration), and thus
the system occupied memory exceeds the available board memory. When powering
on the system, you find the memory is insufficient during launching the charging
l Physical memory hardware is damaged. Failed to find the memory or the memory
is insufficient during system power-on, the system fails to be started. This alarm is
raised.
2-188

l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 3.
Warning!
busy hours.
2.122 ALM-3154272256 Overstocking ACR Files

Alarm Description
The system produces the backlog ACR files.
Alarm Property
3154272256 Warning alarm NE alarm Processing error alarm
Alarm-Related Information
File Directory The directory saving the backlog ACR files

Written into files, the offline charging ACRs cannot be sent to the CCF charging module
timely, which causes commercial loss.
Probable Causes
l Charging links between local NE and the CG are unavailable, and thus ACRs cannot
be sent to the CG.
2-189

l The module capacity is configured too larger and exceeds the system capacity.
l Level-1 or level-2 session buffering area capacity is smaller than the planning, which
weakens the ACR buffering capacity of the charging module.
1. Check if there are charging-related alarms, CCF link-related alarms, CCF host-related
alarms, and CCF host group-related alarms.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Handle these alarms by referring to related troubleshooting suggestions, wait for
10 minutes after the related alarms are eliminated, and check whether the alarm is
eliminated.
l Y->End.
l N->Go to Step 3.
3. Check whether SCTP/TCP association between this NE and CG is existing by SHOW
DIMSCTP and SHOW TCPCONN.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Add SCTP/TCP association between this NE and CG by ADD DIMSCTP or ADD TC
PCONN, send configured data to the foreground by SYNA, and check whether the
l Y->End.
l N->Go to Step 5.
5. Check whether the DIAMETER link between this NE and CG is existing by SHOW
DIM LINK.
l Y->Go to Step 7.
l N->Go to Step 6.
Note:
You can query the host name by SHOW HOST, and query Destination Host Name
by SHOW ADJHOST.
6. Configure DIAMETER link between this NE and CG by ADD DIM LINK, set
Destination Host Name and Destination Realm, SCTP/TCP Bearer Link ID set in
step 2, set Bearer Protocol Type, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 7.
7. Check whether the DIAMETER route between this NE and CG is existing by SHOW
DIM ROUTE.
l Y->Go to Step 9.
l N->Go to Step 8.
2-190

8. Configure DIAMETER route between this NE and CG by ADD DIM ROUTE, Link ID
is the link ID set in step 4, Route Application ID is Rf, and check whether the alarm
is eliminated.
l Y->End.
l N->Go to Step 9.
9. Check whether the overstocking ACR files are sent by executing SHOW ACR FILE
many times.
l Y->Go to Step 10.
l N->Go to Step 11.
Note:
After executing SHOW ACR FILE many times, if you find File Count or File Total
Size(MB) is decreasing, the ACR files are being sent, otherwise, the files are not sent.
10. Wait until all the overstocking ACR files are sent, and check whether the alarm is
eliminated.
l Y->End.
l N->Go to Step 11.
Note:
Check whether all the overstocked ACR files are sent by SHOW ACR FILE, if File
Count is 0, then all the ACRs are sent.
11. Query corresponding user capacity configuration by SHOW USERCAPA according to

the module number in logic resource location information, and check whether the user
capacity is consistent with the planned values.
l Y->Go to Step 13.
l N->Go to Step 12.
12. Modify the user capacity configuration according to the plan by SET USERCAPA.
Reset the board by RESET NORMAL and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 13.
Note:
Reset the board to make above configurations effective, try to reset the board with the
guide of ZTE service personnel.
2-191

13. Check whether the data area capacity is calculated automatically according to
parameters of traffic model or configured manually.
l Calculate automatically->Go to Step 14.
l Configure manually->Go to Step 16.
Note:
Generally, if we can find this module number by SHOW MODCAPA, then the data
area capacity is configured manually.
14. Query the system ability configuration by SHOW SYSCAPA and check whether the
parameters of traffic model are consistent with the planned values.
l Y->Go to Step 16.
l N->Go to Step 15.
15. Modify the corresponding parameters of traffic model according to the plan by SET
SYSCAPA. Reset the board by RESET NORMAL and check whether the alarm is
eliminated.
l Y->End.
l N->Go to Step 16.
Note:
2.123 ALM-3154272257 Insufficient ACR Storage Space

Alarm Description
ACR storage space is insufficient
Alarm Property

Charging data will be lost, which cause commercial loss. There will be no room remaining,
which causes unexpected system problem.
2-192

Probable Causes
l The charging link between this NE and CG is unavailable, and ACR cannot be sent
to CG, and thus the system produces overstocking ACR files.
l The module user capacity is set too large, which exceeds system capacity, and thus
the system produces abundant overstocking ACR files.
l Level-1 session buffering area capacity or Level-2 session buffering area capacity are
set too small, which impact the capacity the charging module saves ACR, and thus
the system produces abundant overstocking ACR files.
l Other files occupy hard disk space, which leaves insufficient space in the hard disk.
l Y->Go to Step 2.
l N->Go to Step 3.
eliminated.
l Y->End.
l N->Go to Step 3.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 5.
DIM LINK.
l Y->Go to Step 7.
l N->Go to Step 6.
Note:
You can query the host name by SHOW HOST, and query Destination Host Name by
SHOW ADJHOST.
2-193

l Y->End.
l N->Go to Step 7.
DIM ROUTE.
l Y->Go to Step 9.
l N->Go to Step 8.
is eliminated.
l Y->End.
l N->Go to Step 9.
many times.
l Y->Go to Step 10.
l N->Go to Step 11.
Note:
eliminated.
l Y->End.
l N->Go to Step 11.
Note:
Check whether all the overstocking ACR files are sent by SHOW ACR FILE, if File

l Y->Go to Step 13.
l N->Go to Step 12.
l Y->End.
l N->Go to Step 13.
2-194

Note:
Note:
l Y->Go to Step 16.
l N->Go to Step 15.
eliminated.
l Y->End.
l N->Go to Step 16.
Note:
2.124 ALM-3154272258 Disk Space for Overstocking

ACR Files Reached Limit
Alarm Description
No more space for saving the backlog ACR files
2-195

Alarm Property

There is no space for storing the backlog ACR files, and the offline charging is failed, which
causes commercial loss.
Probable Causes
l The charging link between this NE and CG is unavailable, and ACR cannot be sent
to CG, and thus system produces overstocking ACR files.
l The module user capacity is set too large, which exceeds system capacity, and thus
the system produces abundant backlog ACR files.
l Level-1 session buffering area capacity or level-2 session buffering area capacity is
set too small, which impacts the capacity the charging module saves ACR, and thus
the system produces overstocking ACR files.
l Other files occupy hard disk space, which leaves insufficient space in the hard disk.
l Y->Go to Step 2.
l N->Go to Step 3.
eliminated.
l Y->End.
l N->Go to Step 3.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 5.
DIM LINK.
l Y->Go to Step 7.
l N->Go to Step 6.
2-196

Note:
You can query the host name by SHOW HOST, and query Destination Host Name by
SHOW ADJHOST.
l Y->End.
l N->Go to Step 7.
DIM ROUTE.
l Y->Go to Step 9.
l N->Go to Step 8.
is eliminated.
l Y->End
l N->Go to Step 9.
many times.
l Y->Go to Step 10.
l N->Go to Step 11.
Note:
eliminated.
l Y->End.
l N->Go to Step 11.
Note:
Check whether all the overstocking ACR files are sent by SHOW ACR FILE, if File
2-197


l Y->Go to Step 13.
l N->Go to Step 12.
l Y->End.
l N->Go to Step 13.
Note:
Note:
l Y->Go to Step 16.
l N->Go to Step 15.
eliminated.
l Y->End.
l N->Go to Step 16.
Note:
2-198

2.125 ALM-3154272272 Abnormal ACR Files

Alarm Description
Exceptional ACR file is generated.
Alarm Property

Offline charging cannot be made.
Probable Causes
l Offline charging cannot be made because of internal errors of the local NE.
l The ACR message content contains an error. Thus the CCF rejects to accept the
message.
2.126 ALM-3154276352 License Usage Percentage

Exceeds Threshold
Alarm Description
License usage percentage exceeds the threshold
Alarm Property
3154276352 Minor alarm NE alarm Processing error alarm

You cannot add the configuration data control by this license item to the system. This topic
provides an example of Registered User Number item, when the alarm is raised and
license name is Registered User Number, you cannot add registered user any more.
2-199

Probable Causes
License usage percentage exceeds the threshold
1. Query license usage number and purchase number in additional alarm information.
check whether license alarm percentage is proper by running the SHOW LIC ALER
TTHRESHOLD command. The recommended alarm threshold is 80%.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify the alarm percentage by running the SET LIC ALERTTHRESHOLD
command, and check whether the alarm is cleared.
l Y->End
l N->Go to Step 3.
3. Purchase more Licenses by contacting ZTE.
2.127 ALM-3154276353 AAS Statics Failure

Alarm Description
AAS Statics Failure.
Alarm Property
3154276353 Minor Alarm OMM System Alarm QoS Alarm

The accuracy of the AAS statistical results may be affected.
Probable Causes
l AAS statistical results cannot be calculated from the call messages.
l AAS statistical results cannot be stored.
2.128 ALM-3154280448 Failed to Output Call History

Alarm Description
Failed to output call history record
2-200

Alarm Property
3154280448 Minor alarm OMM system alarm Processing error alarm

The call history record data is incomplete.
Probable Causes
l The NM server disk space is insufficient.
l The disk is damaged.
l The allocated directory operation permission is insufficient.
1. Check whether related hard disk utilization alarm is existing on the NM server hard
disk.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Handle the alarms according to associated alarm suggestions, and check whether the
alarm is cleared.
l Y->End.
l N->Go to Step 3.
2.129 ALM-3154513933 HSS Host Bypassed

Alarm Description
The HSS enables the bypass function.
Alarm Property

The HSS host is bypassed. Another HSS host is selected, or an S-CSCF host is selected
based on the local configuration.
Probable Causes
l The Bypass policy is set to manual mode.
l The Bypass policy is set to auto mode. The links between CSCF and host are broken.
l The Bypass policy is set to auto mode. This host has no links.
2-201

l The Bypass policy is set to auto mode. This host is blocked.

l The Bypass policy is set to auto mode. The opposite equipment is abnormal.
l The Bypass policy is set to auto mode. The links are configured improperly.
1. Check whether the HSS host enables the bypass function by running the SHOW ADJ
HOST command based on the host name in additional alarm information, and obtain
corresponding adjacent host ID and select proper handling steps based on startup
modes.
l Manual startup->End.
l Auto startup->Go to Step 2.
2. Check whether HSS Forced Blocking is blocked by running the SHOW ADJHOST
command.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Set Forced Blocking to Default to unblock HSS by running the SET ADJHOST
l Y->End.
l N->Go to Step 4.
4. Enter the protocol stack mode by running the IPSTACK command, and check network
connection between CSCF and HSS by running the PING command, run EXIT MODE
command to exit the protocol stack mode.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Check whether the network cables are installed into position, and check network route
configuration, troubleshoot the network, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 6.
6. Query the DIAMETER link information by running the SHOW DIM LINK command,
check whether the opposite host name and host name in additional alarm information
are consistent, you can obtain ConnectId and Protocol.
l Y->Go to Step 8.
l N->Go to Step 7.
7. Add the DIAMETER link of the HSS host by running the ADD DIM LINK command,
l Y->End.
l N->Go to Step 8.
8. Select proper MML command based on the obtained Connect Id and Protocol in step
6, proceed to step 9.
l Protocol is TCP, obtain Local IP Address, Module, Local Port, Peer IP Address
and Peer Port by running the SHOW TCPCONN command.
l Protocol is SCTP, obtain Local IP Address, Module, Local Port, Peer IP
Address and Peer Port by running the SHOW TCPCONN command.
2-202

9. Query the IP distribution list by running the SHOW IPV4DISP/SHOW IPV6DISP

command, and obtain Local IP Address, check whether it is consistent with the
address obtained in step 8. Meanwhile check whether the Local Port is within the
local port range.
l Y->Go to Step 11.
l N->Go to Step 10.
10. Configure the distribution list by running the ADD IPV4DISP/ADD IPV6DISP
l Y->End.
l N->Go to Step 11.
Note:
Refer to the manuel ZXUN CSCF Data Configuration Guide for detailed parameter
descriptions.
11. Check the configured distribution information in step 9, check whether the Module is
consistent with the Module obtained in step 8.
l Y->Go to Step 13.
l N->Go to Step 12.
12. Delete the distribution list configuration by running the DEL IPDISPV4/DEL IPDISPV6
command, re-configure it according to step 10 and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 13.
13. Check whether Peer IP Address and Peer Port obtained in Step 8 comply with the
planning.
l Y->Go to Step 15.
l N->Go to Step 14.
14. Modify the DIAMETER link by running the SET DIM LINK command, and set Peer
IP Address and Peer Port to be the actual values, and check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 15.
15. Check whether the DIAMETER link is blocked by running the SHOW DIMLNKSTAT
command.
l Y->Go to Step 16.
l N->Go to Step 17.
16. Unblock the DIAMETER link by running the UNBLOCK DIMLNK command, and
l Y->End.
l N->Go to Step 17.
2-203

2.130 ALM-3154513934 AS Host Bypassed

Alarm Description
The AS enables the bypass function.
Alarm Property

The AS host is bypassed, and another AS host is selected.
Probable Causes
l The Bypass policy is set to auto mode. The opposite device is abnormal.
l The Bypass policy is set to disable mode. The links between CSCF and host are
broken.iFC flow trigger.
l The Bypass policy is set to disable mode. This host is blocked.iFC flow trigger.
1. Obtain bypass mode and host configure type by SHOW AJHOST INFO based on the
host name in additional alarm information, and select proper handling steps based on
bypass mode.
l Manual->End.
l Automatic or Disable->Go to Step 2.
2. Check whether the opposite NE is started up normally.
l Y->Go to Step 4.
l N->Go to Step 3.
3. Start the opposite AS NE, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 4.
4. Enter the protocol mode by running the IPSTACK command, and check whether the
physical link status is normal by running the PING command and exit this mode by
running the EXIT MODE command.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Troubleshoot the network connection and check network cable connection and router
l Y->End.
2-204

l N->Go to Step 6.
6. The adjacent host ID obtained in Step 1 is the link No., you can check whether this
No. and opposite NE link configuration are consistent with the planning by running the
SHOW SIP LINK command.
l Y->Go to Step 8.
l N->Go to Step 7.
Note:
Dynamic DNS Query: go to Step 12.
7. Modify the link configuration between local NE and opposite NE according to the
planning by running the SET SIP LINK command, and check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 8.
8. Check the protocol type in link configuration in Step 6, select proper MML command to
check whether opposite IP address, port configuration are consistent with the planning.
l UPD: SHOW UDPCONN
l TCP: SHOW TCPCONN
l SCTP: SHOW SIPSCTP
l Y->Go to Step 10.
l N->Go to Step 9.
9. Check the protocol type in link configuration in step 6, select proper MML command
to modify configuration of opposite NE, and check whether the alarm is cleared.
l UPD: SET UDPCONN
l TCP: SET TCPCONN
l SCTP: SET SIPSCTP
l Y->End.
l N->Go to Step 10.
10. Check whether the link block status is Yes by SHOW SIP LINK with the adjacent host
ID.
l Y->Go to Step 11.
l N->Go to Step 14.
11. Modify link block status to No by SET SIP LINK, and check whether the alarm is
eliminated.
l Y->End.
l N->Go to Step 14.
12. Check whether the Dynamic host block by SHOW DYADJHOSTINFO.
l Y->Go to Step 13.
l N->Go to Step 14.
13. Dynamic host unblock by SET DYADJHOSTINFO, and check whether the alarm is
eliminated.
2-205

l Y->End.
l N->Go to Step 14.
2.131 ALM-3154513935 DNS Host Bypassed

Alarm Description
The DNS enables the bypass function.
Alarm Property

The DNS host is bypassed, and another DNS host is selected.
Probable Causes
l The Bypass policy is set to auto mode. The opposite equipment is abnormal.
1. Check whether the DNS host enables the bypass function by running the SHOW ADJ
HOST command based on the host name in additional alarm information, and obtain
corresponding adjacent host ID and select proper handling steps based on startup
modes.
2. Based on the host name in additional alarm information, check whether Forced
Blocking is Block by running the SHOW ADJHOST command.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Set Forced Blocking to Default to unblock DNS by running the SET ADJHOST
l Y->End.
l N->Go to Step 4.
2-206

4. Enter the protocol mode by running the IPSTACK command, and check whether the
physical link status is normal by running the PING command and exit this mode by
running the EXIT MODE command.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Check whether the network cables are installed into position, and check network route
configuration, troubleshoot the network, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 6.
6. Query the DNS link configuration by running the SHOW DNSLNK command. Obtain
Link ID and check whether it is consistent with the link ID in step 1, and obtain Module
No., Local IP Address, Local Port No., Peer IP Address and Peer Port No..
l Y->Go to Step 8.
l N->Go to Step 7.
7. Configure related DNS links according to the planning by running the ADD DNSLNK
l Y->End.
l N->Go to Step 8.
8. Query the IP distribution list by running the SHOW IPV4DISP/SHOW IPV6DISP
command, and obtain Local IP Address, check whether it is consistent with the
address obtained in Step 6. Meanwhile check whether the Local Port No. is within
the local port range.
l Y->Go to Step 10.
l N->Go to Step 9.
9. Configure the distribution list by running the ADD IPV4DISP/ADD IPV6DISP
l Y->End.
l N->Go to Step 10.
Note:
Refer to ZXUN CSCF Data Configuration Guide for detailed parameter
descriptions.
10. Check the configured distribution information in step 7, check whether the Module No.
is consistent with the Module No. obtained in step 6.
l Y->Go to Step 12.
l N->Go to Step 11.
11. Delete the distribution list configuration by running the DEL IPDISPV4/DEL IPDISPV6
command, re-configure it according to step 9 and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 12.
2-207

12. Check whether Peer IP Address and Peer Port No. in step 6 are in compliance with
the planning.
l Y->Go to Step 14.
l N->Go to Step 13.
13. Modify the DNS link by running the SET DNSLNK command, and then Peer IP Ad-
dress and Peer Port No. are consistent with those of the DNS server, check whether
l Y->End.
l N->Go to Step 14.
14. Check whether Link Block is Block by running the SHOW DNSLNK command.
l Y->Go to Step 15.
l N->Go to Step 16.
15. Modify Link Block to Unblock by running the SET DNSLNK command, and check
l Y->End.
l N->Go to Step 16.
2.132 ALM-3154513937 CCF Host Bypassed

Alarm Description
The CCF enables the bypass function.
Alarm Property

The CCF host is bypassed, and another CCF host is selected.
Probable Causes
l The Bypass policy is set to auto mode. The opposite device is abnormal.
2-208

1. Check whether the CCF host enables the bypass function by SHOW ADJHOST based
on the host name in additional alarm information, and obtain corresponding adjacent
host ID and select proper handling steps based on startup modes.
2. Check whether CCF Forced Blocking is blocked by SHOW ADJHOST.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Set Forced Blocking to Default to unblock CCF by SET ADJHOST, and check whether
the alarm is eliminated.
l Y->End.
l N->Go to Step 4.
4. Type in IPSTACK to enter the protocol stack mode, and check network connection
between CSCF and CCF by PING, type in EXIT MODE to exit the protocol stack
mode.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Check whether the network cables are inserted into position, and check network route
configuration, troubleshoot the network, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 6.
6. Query the DIAMETER link information by SHOW DIM LINK, check whether the
opposite host name and host name in additional alarm information are consistent,
you can obtain Connect ID and Protocol.
l Y->Go to Step 8.
l N->Go to Step 7.
7. Add the DIAMETER link of the CCF host by ADD DIM LINK, and check whether the
l Y->End.
l N->Go to Step 7.
8. Select proper MML command based on the obtained Connect Id and Protocol in step
6, proceed to step 9.
l Protocol is TCP, obtain Local IP Address, Module No., Local Port No., Peer IP
Address and Peer Port No. by running the SHOW TCPCONN command.
l Protocol is SCTP, obtain Local IP Address, Module No., Local Port No., Peer
IP Address and Peer Port No. by running the SHOW TCPCONN command.
9. Query the IP distribution list by SHOW IPV4DISP/SHOW IPV6DISP, and obtain
Local IP Address, check whether it is consistent with the address obtained in step 8.
Meanwhile check whether the Local Port No. is within the local port range.
l Y->Go to Step 11.
l N->Go to Step 10.
10. Configure the distribution list by ADD IPV4DISP/ADD IPV6DISP, and check whether
the alarm is eliminated.
2-209

l Y->End.
l N->Go to Step 11.
Note:
Refer to ZXUN CSCF Data Configuration Guide for detailed parameter descriptions.
11. Check the configured distribution information in step 9, check whether the Module No.
is consistent with the Module No. obtained in step 8.
l Y->Go to Step 13.
l N->Go to Step 12.
12. Delete the distribution list configuration by DEL IPDISPV4/DEL IPDISPV6,
re-configure it according to step 10 and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 13.
13. Check whether Peer IP Address and Peer Port No. obtained in step 8 comply with
the planning.
l Y->Go to Step 15.
l N->Go to Step 14.
14. Modify the DIAMETER link by SET DIM LINK, and set Peer IP Address and Peer
Port No. to be the actual values, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 15.
15. Check whether the DIAMETER link is blocked by SHOW DIMLNKSTAT.
l Y->Go to Step 16.
l N->Go to Step 17.
16. Unblock the DIAMETER link by UNBLOCK DIMLNK, and check whether the alarm
is eliminated.
l Y->End.
l N->Go to Step 17.
2.133 ALM-3154513947 Failed to Load Common

Upgrade Configuration Data
Alarm Description
The DNS server does not respond.
2-210

Alarm Property

Minor upgrade configuration data cannot be loaded when the board is started. The loading
of some data is aborted.
Probable Causes
The minor upgrade configuration data is abnormal.
2.134 ALM-3154534400 DNS Link Is Broken

Alarm Description
The DNS link is broken.
Alarm Property

The DNS link is broken, and the DNS query messages cannot be processed on the link.
Probable Causes
l DNS Link configuration is not correct.
l The Network connection between CSCF and DNS server is broken.
l IP dispatch configuration is not correct.
l DNS Server is abnormal
1. Query DNS link information by SHOW DNSLNK and obtain Module, Local IP
Address, Local Port, Peer IP Address, Peer Port, Protocol, and Local Role.
Proceed to step 2.
2. Check whether the link information obtained in step 1 are in compliance with the
planning.
l Y->Go to Step 4.
2-211

l N->Go to Step 3.
3. Modify the DNS link by SET DNSLNK, and make sure that Peer IP Address and Peer
Port are consistent with those of the DNS server, and the Protocol is the same as
DNS server. If the Protocol is TCP, make sure the Local Role is correct, and check
l Y->End.
l N->Go to Step 4.
4. Input IPSTACK to enter the IP stack mode, and check network connection between
CSCF and DNS server by PING, input EXIT MODE to exit the IP stack mode.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Check whether the network cables are inserted into position, and check network route
configuration, troubleshoot the network, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 6.
6. Query the IP dispatch list by SHOW IPV4DISP/SHOW IPV6DISP, and obtain Local
IP Address, check whether it is consistent with the address obtained in step 1.
Meanwhile check whether the Local Port of DNS link is within the local port range.
l Y->Go to Step 8.
l N->Go to Step 7.
7. Configure the dispatch list by ADD IPV4DISP/ADD IPV6DISP, send configured data
to the foreground by SYNA,and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 9.
Note:
Refer to ZXUN CSCF Data Configuration Guide for detailed parameter descriptions.
8. Check the configured dispatch information in step 6, check whether the Module No.
is consistent with the module obtained in step 1.
l Y->Go to Step 10.
l N->Go to Step 9.
9. Delete the dispatch list configuration by DEL IPDISPV4/DEL IPDISPV6, reconfigure
it according to step 7 ,send configured data to the foreground by SYNA,and check
l Y->End.
l N->Go to Step 10.
10. Contact the maintenance personnel of the DNS server to recover the device and check
l Y->End.
l N->Go to Step 11.
2-212

2.135 ALM-3154776084 Traffic Control

Alarm Description
The traffic control alarm.
Alarm Property

The service is failed because of local NE traffic control and backward NE traffic control.
This alarm is raised once the traffic exceeds the traffic control threshold. After a while, the
alarm will be cleared if the traffic is lower than the threshold for a long time. If the alarm
exists, and current traffic does not exceed the threshold, the NE can handle new service
requests, but the services will be failed if the traffic exceeds the threshold. If the alarm
persists for a long time. check whether local NE or backward NE reaches its performance
upper limit. Adjust the traffic control policy based on alarm content.
Probable Causes
l Based on the CallGaping policy, the incoming traffic reaches a value.
l Based on the congestion traffic control policy of the destination code, the outgoing
traffic reaches a value.
1. Check whether the alarm information contains the CallGaping policy ID and SIP
methods.
l Y->Go to Step 2.
l N->Go to Step 4.
2. Based on the CallGaping policy and SIP methods, query corresponding CallGaping
traffic control policy configuration by the SHOW CGPLC command, and check whether
the parameters are set according to the planning.
l Y->End.
l N->Go to Step 3.
3. Modify the CallGaping traffic control policy configuration by the SET CGPLC
command. Wait for the next statistical period, and check whether the alarm is cleared.
l Y->End.
l N->End. It is recommended to expand the system capacity or optimize the
performance.
2-213

Note:
Implemented inside the system, a statistical period lasts for 15 minutes.
4. Based on the traffic control policy ID, SIP method and traffic control level in alarm
information, query corresponding congestion traffic control policy of the destination
code by the SHOW DCCCPLC command, and check whether the parameters are set
according to the planning.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Modify congestion traffic control policy of the destination code by the SET DCCCPLC
command according to the planning. Wait for the next statistical granularity of the
traffic, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 6.
Note:
Show the statistical traffic granularity by the SHOW DCCCGLB command.
6. Check whether mass failure response are received from the backward NE.
l Y->Analyze the fault causes of the backward NE.
l N->Go to Step 7.
2.136 ALM-3154792450 Add IP Address to Anti-DOS

Attack Black List
Alarm Description
Add IP address to anti-DOS attack blacklist
Alarm Property

DOS (Denial of Service) attack to P-CSCF affects normal service handling, such as calls
and registrations. The system will collapse under severe condition.
2-214

Probable Causes
l When the PCSCF NE receives mass malicious attack messages from different IP
addresses.
l Improper anti-DOS attack configuration of dynamic IP address. You are suggested to
use the default configuration. (The default statistics time interval is 30 secs, message
upper limit times is 1440.)
l Configured static IP address anti-DOS attack blacklist.
1. Check whether the anti-DOS attack function is used.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Set Switch to Disabled by running the SET ANTIDOSCFG command to disable the
anti-DOS attack function, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 6.
Warning!
You can not perform anti-DOS attack after disabling this function, refer to the
System Influence for possible results.
3. View the IP address list by running the SHOW IPLIST command. Check IP status
in anti-DOS attack function by running the CHECK DOSIPV4INFO command, and
check whether to add the IP address to the whitelist, delete static IP address blacklist
or disconnect the physical attack source.
l Disconnect the physical attack source ->Go to Step 4.
l Add the IP address to the whitelist ->Go to Step 5.
l Delete static IP address blacklist ->Go to Step 6.
4. Check IP address attack source, disconnect the physical link with the attack source,
check whether the alarm is cleared after the aging time (default time is 10 minutes),
you can check the aging time by running the SHOW ANTIDOSCFG command.
l Y->End.
l N->Go to Step 7.
5. Add corresponding IP address in the whitelist by running the ADD STCIPANTIDOS
command and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 7.
2-215

Warning!
The messages from the added IP address will be regarded trustworthy, and the
system will not detect the anti-DOS attack on these messages.
6. Delete static IP address blacklist by running the DEL STCIPANTIDOS command, and
l Y->End.
l N->Go to Step 7.
2.137 ALM-3154792452 Add User to Anti-DOS Attack

Black List
Alarm Description
Add user to anti-DOS attack blacklist
Alarm Property

DOS (Denial of Service) attack to P-CSCF affects normal service handling, such as calls
and registrations. The system will collapse under severe condition.
Probable Causes
l The current P-CSCF NE receives mass malicious attack messages from a subscriber.
l Improper anti-DOS attack configuration of dynamic subscriber. The default
configuration statistics time interval is 30s, message upper limit times is 600.)
l Configured the user's blacklist.
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 6.
2-216

Warning!
You can not perform anti-DOS attack after disabling this function, refer to the
System Influence for possible results.
3. Obtain the subscriber list by running the SHOW USERLIST command. Check IP status
in anti-DOS attack function by running the CHECK DOSUSERINFO command, and
check whether to add the IP address to the whitelist, delete static IP address blacklist
or disconnect the physical attack source.
l Disconnect the physical attack source ->Go to Step 4.
l Add the IP address to the whitelist ->Go to Step 5.
l Delete static IP address blacklist ->Go to Step 6.
l Y->End.
l N->Go to Step 7.
5. Based on user type, select proper MML, such as ADD BWURIANA command, ADD
BWTELANA command or ADD BWANYANA command. Add corresponding users
to the whitelist, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 7.
Warning!
After the users are added, their messages are regarded as trustworthy and will
be not tested by the anti-DOS attack.
BWTELANA command or ADD BWANYANA command. Delete corresponding users
blacklist, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 7.
2-217

2.138 ALM-3154513936 DNS Signaling Link

Disconnection
Alarm Description
All the DNS signaling links are disconnected.
Alarm Property
3154513936 Major alarm NE alarm Communication alarm

In most circumstances, a CSCF system has several DNS servers for the purpose of
disaster recovery. When all the links in a DNS server are disconnected, the DNS query
messages will be processed by other DNS servers. Thus the communication between
the CSCF system and the DNS server will not be affected, and therefore, services will not
be affected. However, the reduction of the links can result in reduced data transmission
capability, and thus system reliability can also be reduced. When this alarm is raised,
the DNS links for a DNS server are all disconnected. The CSCF system can continue to
provide services through reading the Cache memory record or the internal DNS server
configuration. When the Cache memory record is not available, and the DNS server is
not configured, if the DNS links for all DNS servers are disconnected, services cannot
be provided. The CSCF system cannot operate normally. Registration and calls will be
affected.
Probable Causes
l A DNS server is not associated with DNS links.
l The communication between the CSCF system and a DNSDNS Server is
disconnected.
l The IP dispatch table is not configured or not configured correctly.
l DNS links are not configured properly.
l The remote equipment does not operate normally.
1. Check the information for the alarm; whether it is "The DNS host is not associated with
the corresponding DNS links"
l Y->Go to Step 2.
l N->Go to Step 3.
2. Configure the association by running the SET DNSLNK command. Check whether
l Y->End
l N->Go to Step 3.
2-218

3. Check whether the communication between the CSCF system and the DNS server is
in normal state by running the Ping command.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Check whether the equipment are connected through cables; whether the route is
configured correctly. Remove the corresponding faults and restore the network. Check
l Y->End.
l N->Go to Step 5.
5. Query the information of a DNS link, including the DNS server ID, source address,
source port, destination address and destination port by running the SHOW DNSLNK
command. For the links of a DNS server, go to step 6.
6. Query the IP dispatch table, whether the "Local IP Address" parameter is configured
with the "Source Address" in step 5, and whether the source port in step 5 is in the
allowed port range by running the SHOW IPV4DISP command or SHOW IPV6DISP
command.
l Y->Go to Step 8.
l N->Go to Step 7.
7. Configure the IP dispatch table by running the ADD IPV4DISP command or the ADD
IPV6DISP command, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 8.
8. Check the dispatch table configured in step 6; whether the module in the table is the
module that processes the DNS server.
l Y->Go to Step 10.
l N->Go to Step 9.
9. Delete the dispatch table by running the DEL IPV4DISP command or the DEL IPV6D
ISP command, and configure it again. Check whether the alarm is cleared.
l Y->End.
l N->Go to Step 10.
10. Check whether the destination address and destination port queried in step 5 are
consistent with the planned ones.
l Y->Go to Step 12.
l N->Go to Step 11.
11. modify the DNS link configuration by running the SET DNSLNK command. When the
destination address and the destination port are consistent with the real ones, check
l Y->End.
l N->Go to Step 12.
12. Contact the related personnel who is responsible for maintaining the DNS server to
restore the DNS equipment. Check whether the alarm is cleared.
l Y->End.
l N->Go to Step 13.
2-219

2.139 ALM-3154534658 Charging Module Fails to

Register to DIAMETER
Alarm Description
The charging module fails to register to DIAMETER protocol.
Alarm Property
3154534658 Major alarm NE alarm Equipment alarm

Probable Causes
l When the system is powered on, the DIAMETER module fails to be started. Thus the
registration request from the charging module cannot be accepted.
l You fail to make the basic DIAMETER protocol configuration. Thus the registration
request from the charging module cannot be accepted.
1. Wait for 3 to 5 minutes and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 2.
2. Check whether the DIAMETER protocol has been configured by running the SHOW
DIM GLOBAL command. If it has, whether it is configured correctly.
l Y->Go to Step 4.
l N->Go to Step 3.
3. Add or modify the configuration of the DIAMETER protocol by running the ADD DIM
GLOBAL command or SET DIM GLOBAL command. Check whether the alarm is
cleared.
l Y->End.
l N->Go to Step 4.
2.140 ALM-3154534672 CG Does Not Support Local NE

DIAMETER Version
Alarm Description
CCF does not support the DIAMETER version of the NE.
2-220

Alarm Property

Probable Causes
The DIAMETER protocol version of the CCF and that supported by the local NE are not
consistent with each other. When the CCF receives the offline charging ACR message
sent by the local NE, it returns an ACA message whose Result-Code is 5011.
2.141 ALM-3154513931 Memory Allocation Failure

Alarm Description
Failed to allocate memory when establishing a processing database
Alarm Property

properly. Each module is deployed with many processes in which the functional data area
implements the services. "Memory Allocation Failure" indicates that one or more modules
fail to be allocated with memory. If the modules belong to special service module rather
than general modules, the special services cannot be implemented, such as session
control service. If this module belongs to general module, even the basic services cannot
be implemented either, such as registration and call.
Probable Causes
l The module user capacity is set too large (exceeds the planned configuration), and
thus the occupied memory exceeds the available board memory. When powering on
the system, you find the memory is insufficient. Therefore, failed to create a process
database, an alarm is raised.
2-221

system, you find the memory is insufficient. Therefore, a process database fails to be
created, an alarm is raised.
l The board physical memory is damaged. The system detects that the memory is
insufficient or cannot find the memory during powering on the system. Therefore, the
system fails to create a process database, an alarm is raised.
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 3.
Warning!
busy hours.
2.142 ALM-3154513932 Data Area Memory Allocation

Failure
Alarm Description
Failed to allocate memory for the data area when establishing a process base
Alarm Property

2-222

properly. Each module is deployed with many processes in which the functional data area
implements the services. "Data Area Memory Allocation Failure" indicates that one or
more modules fail to be allocated with memory. If the modules belong to special service
module rather than general modules, the special services cannot be implemented, such
as session control service. If this module belongs to general module, even the basic
services cannot be implemented either, such as registration and call.
Probable Causes
the system, you find the memory is insufficient. Therefore, the data area memory fails
to be allocated, an alarm is raised.
system, you find the memory is insufficient. Therefore, the data area memory fails to
be allocated, an alarm is raised.
insufficient or cannot find the memory during powering on the system. Therefore, the
system fails to create a process database, an alarm is raised.
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 3.
Warning!
busy hours.
2-223

2.143 ALM-3154513940 Adjacent Host Is Abnormal

Alarm Description
An adjacent host is manually set blocked in the NM system.
Alarm Properties
Alarm Code Alarm Level System Type Alarm Type
3154513940 Critical alarm NE alarm Processing error

alarm

The adjacent host is physically faulty. The registration flow or call flow is blocked because
of the host is unavailable.
Probable Causes
The adjacent host is faulty.
1. Execute the MML SHOW AJHOST INFO to check the value of Host Configure
Type, Host Type and Physical Status according to the host name in the additional
information of the corresponding alarm. Then transform the host type to protocol type
(SIP hosts including MGCF, AS, Proxy, AGCF, P-CSCF, I-CSCF, S-CSCF, BGCF,
E-CSCF and Unknown; DIAMETER hosts including HSS, SLF, CCF and ECF; DNS
Server host), and handle them separately based on the protocol type.
l SIP protocol type->Go to Step 2.
l DIAMETER protocol type->Go to Step 6.
l DNS protocol type->Go to Step 11.
2. Check whether the physical status of SIP hosts is Unavailable.
l Yes->Go to Step 3.
l No->Go to Step 14.
3. For SIP hosts, handle them separately based on the host configuration type (Static
Configuration or Dynamic DNS Query).
l Static Configuration->Go to Step 4.
l Dynamic DNS Query->Go to Step 14.
4. For SIP hosts with static configuration, execute SHOW SIP LINK to get all SIP links,
then select the SIP links whose Adjacent Host ID is same with the host ID in the
additional information of this alarm (More than one SIP link may be related with a
host).Then execute the MML SHOW SIP LINK STATUS to check whether the status
of all the selected links is Unavailable or Blocked.
2-224

5. If the status of the SIP link is Blocked, execute SET SIP LINK:STATUS="NO"; to
unblock the link; If the status of the SIP link is Unavailable, handle it according to
the suggestion of SIP Link Status Alarm. Then execute the MML SHOW SIP LINK
STATUS to check whether the link status is restored to Available or Default.
6. Check whether the physical status of the DIAMETER host is Unavailable.
l The physical status is Unavailable->Go to Step 7.
l The physical status is Default->Go to Step 9.
l The physical status is Available->Go to Step 14.
7. For DIAMETER hosts, execute SHOW DIM LINK to get all DIAMETER links, then
select the DIAMETER links whose Remote Hostname is same with the alarm host.
Then execute MML SHOW DIMLNKSTAT to check whether the status of all the
selected links is unavailable (Unstable, Removed, Blocked, Failover, Initial Value
and Unavailable are unavailable status. Established and Failback are available
status).
8. Check and handle the DIAMETER link fault according to the suggestion of the
DIAMETER Link Not Established or Link Broken alarm. Then execute the MML
SHOW DIMLNKSTAT to check whether the link status is restored to available
(Established or Failback).
9. For DIAMETER hosts, execute SHOW DIM LINK to get all DIAMETER links, then
check whether the alarm host is related to any DIAMETER link (if the Remote
Hostname of the DIAMETER link is the appointed host).
10. The DIAMETER link may be deleted by the DEL DIM LINK operation before.
Determine whether to add a DIAMETER link to the host according to the planning.
After adding the DIAMETER link, check whether the physical status of the host is
restored to Available.
l Yes->End.
l No->Go to Step 7.
11. For the DNS protocol host, execute SHOW DNSLNK to get all DNS links. Then select
the DNS links whose Adjacent Host ID is same with the host ID in the additional
information of this alarm (More than one DNS link may be related with a host). Then
execute the MML SHOW DNS LINK STATUS to check whether the logic status of all
the selected links is Unavailable or Blocked.
12. If the logic status of the link is Blocked, execute SET DNSLNK:BLCKFLG="NO"; to
unblock the link; If the logic status of the link is Unavailable, check and handle the
link fault (according to the suggestion of the ALM-3154534400 DNS Link Is Broken
2-225

alarm). Then execute the MML SHOW DNS LINK STATUS to check whether the link
status is restored to Available.
13. Execute the MML SHOW AJHOST INFO to check whether the physical status of the
host is restored to Available.
l Yes->End.
14. Contact ZTE Corporation.
2.144 ALM-3154513941 Host Group Quit Normal Status

Alarm Description
Host group quit normal status.
Alarm Property
3154513941 Critical alarm NE alarm Processing error

alarm

The host group enters disaster recovery status or fault status from normal status. Disaster
recovery is performed. A part of or all telephone traffic is blocked.
Probable Causes
Host group quit normal status.
1. Check if the redundant host group is in redundant status or abnormal status according
to MML SHOW STATICDR INFO or SHOW DYNAMICDR INFO.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Use the same MML to query the specific information of the redundant host group, and
check if it is able to find the reason of host group entering redundant status or abnormal
status.
l Y->End.
l N->Go to Step 3.
2-226

2.145 ALM-3154513946 Failed to Load Important

Upgrade Configuration Data
Alarm Description
The link between an NE and the OMC server is broken.
Alarm Property
3154513946 Critical alarm NMS alarm Processing error alarm

Important upgrade configuration data cannot be loaded when the board is started. The
original data is loaded.
Probable Causes
The important upgrade configuration data is abnormal.
2.146 ALM-3154534656 Failed to Launch the Charging

Module
Alarm Description
Failed to launch the charging module
Alarm Property

Failed to launch the charging module when the system is powered on, and thus failed to
perform offline charging, which results in commercial loss.
Probable Causes
2-227

the charging module, you find the memory is insufficient during launching the charging
module.
l The module data area capacity is set too large (exceeds the planned configuration),
and thus the occupied memory exceeds the available board memory. When powering
on the charging module, you find the memory is insufficient during launching the
charging module.
insufficient during launching the charging module, and an alarm is raised.
1. Query corresponding module capacity configuration by running the SHOW MODCA
PA command according to the module number in logic resource location information,
and check whether the capacity parameter is consistent with the planned values.
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 3.
Warning!
busy hours.
2.147 ALM-3154534661 CG Connection Failure

Alarm Description
A CG link is faulty.
Alarm Property

The system cannot send ACRs to the CG in time. ACRs are constantly written into a file
until the hard disk space occupied by the file reaches a limit, and then the offline charging
2-228

records produced later are discarded. Thus, charging fails and offline charging cannot
be implemented, causing commercial loss. However, the problem does not affect call,
registration, and subscription functions.
Probable Causes
The number of times that the CSCF retransmits an ACR message to the CG reaches the
“maximum retransmission times of ACR” in the offline charging policy, so the CG does not
respond.
1. Check whether an ACR message can be routed to the CG.
l Y->Go to Step 2.
l N->Verify the network environment.
2. Check whether the CG can send an ACA response.
l Y->Go to Step 4.
l N->Go to Step 3.
3. Check the CG state. After the CG sends an ACA response, check whether the alarm
is cleared.
l Y->End.
l N->Go to Step 4.
2.148 ALM-3154771972 Detect Extra-Long Call

Alarm Description
Detect extra-long call.
Alarm Property

The call is extra-long.
Probable Causes
1. Confirm with the carrier whether you want the extral-long call detection function.
l Y->Go to Step 3.
l N->Go to Step 2.
2-229

2. Modify Extral-Long Call Detection Duration(m) by running the SET LONGCALLPL

C: MONITORTIMER= 0; to disable this function.
Note:
New setting will be effective in the follow-up calls, and the existing alarm is cleared
after the user finishes the call.
3. Check whether Extral-Long Call Detection Duration(m) is too short by running the
SHOW LONGCALLPLC command, recommended value is 720 minutes.
l Y->Go to Step 4.
l N->Go to Step 5.
4. Modify Extral-Long Call Detection Duration(m) to a properly value by running the
SET LONGCALLPLC command.
Note:
New setting will be effective in the follow-up calls, and the existing alarm is cleared
after the user finishes the call.
5. Contact this user and check whether this user is using this function properly.
l Y->End.
l N->Go to Step 6.
2.149 ALM-3154771973 Release Extra-Long Call by

Force
Alarm Description
Release extra-long call by force.
Alarm Property

No impact on system and service.
2-230

Probable Causes
l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify Extral-Long Call Detection Duration(m) by running the SET LONGCALLPL
C:MONITORTIMER=0; to disable this function.
Note:
New setting will be effective in the follow-up calls.
3. Check whether Extral-Long Call Detection Duration(m) is too short by running the
SHOW LONGCALLPLC command, the recommended value is 720 minutes.
l Y->Go to Step 4.
l N->Go to Step 5.
4. Modify Extral-Long Call Detection Durationr(m) to a properly value by running the
SET LONGCALLPLC command.
Note:
5. Confirm with the carrier whether you want the call release for the extral-Long calls.
l Y->End.
l N->Go to Step 6.
6. Modify the HANDLEPOLICY to Keep Call by running the SET LONGCALLPLC
command.
Note:
2-231

2.150 ALM-3154776086 Exceed License Limit of

Concurrent Session or Session Unrelated Number
Alarm Description
Exceed license limit of concurrent session or session unrelated number.
Alarm Property
3154776086 Major alarm NE alarm QoS alarm

Concurrent requests fail if the number of the concurrent requests exceeds the license limit
of the concurrent sessions or session-unrelated number.
Probable Causes
Exceed license limit of concurrent session or session unrelated number.
1. Judge whether there is a traffic peak.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Wait for the end of traffic peak, and check whether the alarm is restored.
l Y->End.
l N->Go to Step 3.
3. Check whether the purchased number of corresponding concurrent session or session
unrelated license is consistent with the plan.
l Y->Go to Step 5.
l N->Go to Step 4.
Note:
Whether concurrent session or session unrelated can be queried by the alarm

information.
4. Re-purchase the corresponding concurrent session or session unrelated License.

2-232

2.151 ALM-3154776107 The Capacity of the Classified

Data Area Is Insufficient
Alarm Description
The capacity of the classified data area is insufficient.
Alarm Property

Calls fail, and the system may break down.
Probable Causes
The capacity of the Classified Data Area is insufficient:
l The data area classified proportion may be incorrect.

l The capacity of the module configuration is insufficient.
1. Judge whether there is a burst traffic peak.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Wait until the burst traffic peak ends, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 3.
2.152 ALM-3154796672 Occupancy of Charging Pool

Reached Threshold
Alarm Description
Occupancy of charging pool reached threshold.
Alarm Property
2-233


The occupancy of the offline charging data area is high. If the call processing mode is
set to "reject" when the occupancy of the CDR pool reaches the threshold, calls may be
released.
Probable Causes
l Communication with CG is broken, or CG is faulty.
l The data area capacity is configured too small, which results in insufficient data area
resources.
l The occupancy of CSCF_DA_BILL_PRIMBUF data area reached threshold of
charging pool occupation ratio in charging pool control policy configuration.
l Y->Go to Step 2.
l N->Go to Step 3.
eliminated.
l Y->End.
l N->Go to Step 3.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 5.
Note:
Restart the board to make above configurations effective, try to make above operation
with the guide of ZTE support personnel.
2-234

2.153 ALM-3162112257 CPU Load Control Level-1

Alarm
Alarm Description
CPU load control level-1 alarm
Alarm Property
3162112257 Critical alarm NE Alarm QoS Alarm

The module internal process speed becomes slow, which prolongs the response delay of
the external messages, even timeout.
The system will control calling/registering messages by the preset overload policy, this
alarm influences normal services and even result in system collapse. This alarm results
in the load control percentage (such as call rejection ratio) exceeds 30% and increases to
99%.
Probable Causes
l Too much service traffic are processed on this module, which exceeds the load control
level-1 threshold preset by the administrator, for example, at the calling peak, the
consumed CPU resource exceeds the level-1 threshold, you should control the calls
according to the load control policy.
l Load is not balanced on each module, service load on one module is much heavier,
which results in the CPU load control level-1 alarm.
l The load control level-1 threshold is set improperly, you are suggested to use default
configuration (Level-1 threshold is 95, level-2 threshold is 90, level-2 lower limit
threshold is 85, level-3 upper limit threshold is 80, level-3 lower limit threshold is 75,
level-4 upper limit threshold is 70 and level-4 lower limit threshold is 65.)
1. Check whether the load control threshold value is set properly by running the SHOW
LOADCFG command.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify the load control threshold to default value by running the SET LOADCFG
command, such as SET LOADCFG command:LOADTYPE="CPU",DPTH=90;, and
l Y->End.
l N->Go to Step 3.
2-235

3. Check whether the load control percentage in the overload policy configuration is
proper by running the SHOW SIPOLPLC command.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Modify the load control percentage by running the SET SIPOLPLC command, and
l Y->End.
l N->Go to Step 5.
5. Query the historical performance data on the local maintenance terminal, and compare
with "Average CPU Utilization" in "CPU and Memory Statistics by Module", check
whether the tolerance of above two values exceeds 15%.
l Y->Go to Step 6.
l N->Go to Step 7.
l Y->End.
l N->Go to Step 7.

Alarm
Alarm Description
Alarm Property
3162112257 Major alarm NE alarm QoS alarm

Interior module capacity speed becomes slowly, which increases delay frequency of
external message response, even timeout. The system will control the calling and
registration messages based on the configured overload policy. As a result, the load
control percentage reaches 30%.
Probable Causes
l The module distribution is improper, one module is distributed with too much service
load, which result in CPU load control level-2 alarm.
2-236

1. Check whether the CPU load control threshold is set properly by running the SHOW
LOADCFG command.
l Y->Go to Step 3.
l N->Go to Step 2.
command, such as SET LOADCFG command :LOADTYPE="CPU",UPTH1=90,LWT
H1=85;, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether the load control percentage in the load policy configuration is proper
by running the SHOW SIPOLPLC command.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Modify the load control percentage in the load policy configuration by running the SET
SIPOLPLC command, wait for 2 to 3 minutes, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 5.
l Y->Go to Step 6.
l N->Go to Step 7.
l Y->End.
l N->Go to Step 7.

Alarm
Alarm Description
Alarm Property
3162112257 Minor alarm NE alarm QoS alarm
2-237


Probable Causes
LOADCFG command.
l Y->Go to Step 3.
l N->Go to Step 2.
command, such as SET LOADCFG command:LOADTYPE="CPU",UPTH2=80,LWT
l Y->End.
l N->Go to Step 3.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 5.
l Y->Go to Step 6.
l N->Go to Step 7.
l Y->End.
l N->Go to Step 7.
2-238


Alarm
Alarm Description
Alarm Property
3162112257 Warning alarm NE alarm QoS alarm

Probable Causes
LOADCFG command.
l Y->Go to Step 3.
l N->Go to Step 2.
command, such as SET LOADCFG command:LOADTYPE="CPU",UPTH3=70,LWT
l Y->End.
l N->Go to Step 3.
2-239

l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 5.
l Y->Go to Step 6.
l N->Go to Step 7.
l Y->End.
l N->Go to Step 7.
2.157 ALM-3162116115 User Number Exceeds the

License Number Threshold Level-1
Alarm Description
User number exceeds the license number threshold level-1.
Alarm Property

The current number of online users in the system exceeds the number of bought licenses.
If license control is not used, new registeration requests still can be processed within the
system processing capability. If license control is used, new registeration requests will be
rejected. If the level 1 alarm exists for a long time, it is recommended that you buy new
licenses.
Probable Causes
1. Gusty traffic peak causes too many on-line users.
2. The system bears too much traffic, which causes the number of current users exceeds
the License value.
3. The number of purchased Licenses is inconsistent with the actual traffic scenario.
2-240

1. Use the man-machine command SHOW USERNUM to query the number of users;use
the man-machine command SHOW LICENSE to query the License value to check if
the number of users exceeds the License value.
l Y->Go to Step 2.
l N->Go to Step 6.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Wait for the end of traffic peak, check whether the alarm is restored.
l Y->End.
l N->Go to Step 4.
4. Check whether the number of purchased Licenses is inconsistent with the plan.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Re-purchase License.
2.158 ALM-3162116115 User Number Exceeds the

License Number Threshold Level-2
Alarm Description
User number exceeds the license number threshold level-2.
Alarm Property

The number of online users of the system exceeds the level 2 alarm threshold
(configurable, default: 90%) of the number of bought licenses. The system still can
process new registeration requests. If this alarm message is displayed for multiple times,
the traffic that the system bears or the traffic model is changed.
Probable Causes
l Gusty traffic peak causes too many on-line users.
l The system bears too much traffic, which causes the number of current users exceeds
the License value.
l The number of purchased Licenses is inconsistent with the actual traffic scenario.
2-241

1. Use the man-machine command SHOW USERNUM to query the number of users;use
the man-machine command SHOW LICENSE to query the License value to check if
the number of users exceeds the Level-2 License value threshold.
l Y->Go to Step 2.
l N->Go to Step 6.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Wait for the end of traffic peak, check whether the alarm is restored.
l Y->End.
l N->Go to Step 4.
4. Check whether the number of purchased Licenses is inconsistent with the plan.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Re-purchase License.
2.159 ALM-3162116138 Data Area Capacity Level-1

Alarm
Alarm Description
Data area capacity level-1 alarm
Alarm Property

properly. Each module is deployed with many processes in which the functional data
area implements the services. ALM-3162116138 Data Area Capacity Level-1 Alarm
indicates that current data area reaches 95% of the capacity, if the alarm persists for a
long time, new call or new services will be failed, and the call abandonment ratio may
reach 50%.
Probable Causes
l The burst traffic peak results in current data area consumes too many resources
temporarily.
2-242

l Too large borne traffic volume or too many subscribers result in current data area
consumes too many resources (95%)
l The data area is configured too small, which results in insufficient data area resource.
l Y->Go to step 2.
l N->Go to step 3.
2. Wait for the end of the burst traffic peak, and check whether the alarm is eliminated.
l Y->End.
l N->Go to step 3.
3. Query corresponding module capacity configuration by SHOW MODCAPA according
to the module number in logic resource location information, and check whether the
capacity parameter is consistent with the planned values.
l Y->Go to step 5.
l N->Go to step 4.
4. Modify the module capacity configuration according to the plan by SET MODCAPA.
Reboot the board by RESET NORMAL and check whether the alarm is eliminated.
l Y->End.
l N->Go to step 5.
Warning!
Restart the board to make above configurations effective, try to restart the board with
the guide of ZTE service personnel.

Alarm
Alarm Description
Alarm Property
2-243


ZTE IMS products implement various functions based on modular design. Each module
implements different functions independently. The entire system can realize various
services required by customers on condition that every module operate properly. Each
module is deployed with many processes in which the functional data area implements the
services. ALM-3162116138 Data Area Capacity Level-2 Alarm indicates that current
data area reaches 85% of the capacity. This alarm only indicates the system bears too
much traffic which results in too many data area resources are consumed. Nevertheless,
the system can keep operating without impact on the services. Once this alarm is raised
for several times, the traffic and the traffic model in the system will vary.
Probable Causes
temporarily.
l Too large traffic volume or too many subscribers result in current data area consumes
too many resources.
l The data area capacity is not configured adequately, which results in insufficient data
area resources.
l Y->Go to Step 2.
l N->Go to Step 3.
2. After the peak ends, check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 3.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 5.
Warning!
Restart the board after above modification to make configuration effective. Try to
modify configuration with the guide of ZTE support personnel.
2-244


Alarm
Alarm Description
Alarm Property

ZTE IMS products implement various functions based on modular design. Each module
implements different functions independently. The entire system can realize various
services required by customers on condition that every module work properly. Each
module is deployed with many processes in which the functional data area implements the
services. ALM-3162116138 Data Area Capacity Level-3 Alarm indicates that current
data area reaches 80% of the capacity. This alarm only indicates the system bears too
much traffic which results in too much data area resources are consumed. Nevertheless,
the system can keep operating without impact on the services. Once this alarm is raised
for several times, the traffic and the traffic model in the system will vary.
Probable Causes
temporarily.
l The system beats too much traffic or too many users, which consumes too much data
area resource.
l The data area capacity is set too small, which results in insufficient data area resource.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Wait until the burst traffic peak ends, and check whether the alarm is eliminated.
l Y->End.
l N->Go to Step 3.
l Y->Go to Step 5.
l N->Go to Step 4.
2-245

l Y->End.
l N->Go to Step 5.
Warning!
Restart the board to make module capacity modification effective, try to make above
operation with the guide of ZTE support personnel.
2.162 ALM-3162132481 Anti-DOS Attack IP Address

Capacity Level-1
Alarm Description
Anti-DOS attack IP address capacity level-1
Alarm Property

Regarding the Denial of Service (DOS) attack, if the IP address number (address for
detecting DOS attack, default value is 10000) reaches level-1 alarm threshold (default
value is 100%), the system will perform DOS attack for 10000 IP addresses. PCSCF
cannot perform the DOS attack, the following-up attack to PCSCF will impact normal
service handling, such as normal call and failed registration. The most sever cases result
in system collapse.
Probable Causes
l Usage of black/white lists of the anti-DOS attack IP address reaches level-1 alarm
threshold.
l When the PCSCF NE receives mass malicious attack messages from different IP
addresses.
2-246

l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 7.
Warning!
You can not perform anti-DOS attack after disabling this function, refer to the Impact
on the System for possible results.
3. View the IP address list by running the SHOW IPLIST command. Check IP status
in anti-DOS attack function by running the CHECK DOSIPINFO command, and
determine whether to add the IP address to the white list.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 6.
5. Add corresponding IP address to the white list by running the ADD STCIPANTIDOS
l Y->End.
l N->Go to Step 6.
Warning!
Be careful when adding IP addresses to the white list, because the messages from
the added IP address will be regarded trustworthy, and thus the system will not detect
the anti-DOS attack on these messages.
6. Extend the anti-DOS attack IP address capacity by running the SET ANTIDOSCFG
command, and restart the board by running the RESET NORMAL command to check
l Y->End.
l N->Go to Step 7.
2-247

Warning!
busy hours.

Capacity Level-2
Alarm Description
Alarm Property

Regarding the anti-DOS (Denial of Service) attack, if the IP address number (address for
value is 90%), the system will perform anti-DOS attack for 9000 IP addresses.
Anti-DOS attack will consume too much resources, which will impact normal service
handling.
Probable Causes
l Usage of black/whitelists of the anti-DOS attack IP address reaches level-2 alarm
threshold.
l When the P-CSCF NE receives mass malicious attack messages from different IP
addresses.
l Y->Go to Step 3
l N->Go to Step 2.
2-248

l Y->End.
l N->Go to Step 7.
Warning!
3. View the IP address list by running the SHOW IPLIST command. Check IP status in
anti-DOS attack function by running the CHECK DOSIPV4INFO command, and check
whether to add the IP address to the whitelist.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 6.
l Y->End.
l N->Go to Step 6.
Warning!
The messages from the added IP address will be regarded trustworthy, and the system
will not detect the anti-DOS attack on these messages.
command, and restart the board to check whether the alarm is cleared.
l Y->End.
l N->Go to Step 7.
Warning!
Do not restart the board after above modification to make configuration effective in
busy hours.
2-249


Capacity Level-3
Alarm Description
Alarm Property

Regarding the anti-DOS (Denial of Service) attack, if the IP address number (address
for detecting DoS attack, default value is 10000) reaches level-3 alarm threshold (default
value is 80%), the system will perform anti-DoS attack for 8000 IP addresses.
Anti-DoS attack will consume too much resources, which will impact normal service
handling. The fault affect calls and registrations.
Probable Causes
l Usage of black/whitelists of the anti-DoS attack IP address reaches level-3 alarm
threshold.
l When the P-CSCF NE receives mass malicious attack messages from different IP
addresses.
l Improper anti-DoS attack configuration of dynamic IP address. You are suggested to
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 7.
Warning!
You can not perform anti-DoS attack after disabling this function, refer to the Impact
2-250

3. View the IP address list by running the SHOW IPLIST command. Check IP status in
anti-DOS attack function by running the CHECK DOSIPV4INFO command, and check
whether to add the IP address to the whitelist.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 6.
command and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 6.
Warning!
The messages from the added IP address will be regarded trustworthy, and the system
will not detect the anti-DoS attack on these messages.
l Y->End.
l N->Go to Step 7.
Warning!
Restart the board to make above configuration effective.Do not perform this operation
in busy hours.
2.165 ALM-3162132483 Anti-DOS Attack User Capacity

Level-1
Alarm Description
Anti-DOS attack user capacity level-1
2-251

Alarm Property

Regarding the anti-DOS (Denial of Service) attack, if the subscriber number (for detecting
DOS attack, default value is 10000) reaches level-1 alarm threshold (default value is
100%), the system will perform anti-DOS attack for 10000 subscribers. PCSCF cannot
prevent the DOS attack, the following-up attack to PCSCF will impact normal service
handling, such as normal call and failed registration. The most severe case will result in
system collapse.
Probable Causes
l The used capacity of the anti-DOS attack subscriber reaches level-1 alarm threshold.
l The current P-CSCF NE receives mass malicious attack messages from different
subscribers.
l Improper anti-DOS attack configuration of dynamic subscriber. Default configuration
values are not used. (The default configuration statistics time interval is 30 secs,
message upper limit times is 600.)
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 7.
Warning!
check whether to add the IP address to the white list.
l Y->Go to Step 5.
l N->Go to Step 4.
2-252

l Y->End.
l N->Go to Step 6.
to the white list, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 6.
Warning!
Be careful when adding users to the whitelist, because after the users are added, their
messages are regarded as trustworthy and will be not tested by the anti-DOS attack.
6. Extend the anti-DOS attack IP user capacity by running the SET ANTIDOSCFG
command, and restart the board by running the RESET NORMAL command to check
l Y->End.
l N->Go to Step 7.
Warning!
busy hours.

Level-2
Alarm Description
Alarm Property
2-253


value is 90%), the system will perform anti-DOS attack for 9000 IP addresses.
Probable Causes
l The current P-CSCF NE receives mass malicious attack messages from different sub-
scribers.
configuration statistics time interval is 30 secs, message upper limit times is 600.)
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 7.
Warning!
check whether to add the IP address to the whitelist.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 6.
l Y->End.
l N->Go to Step 6.
2-254

Warning!
After the users are added, their messages are regarded as trustworthy and will be not
tested by the anti-DOS attack.
l Y->End
l N->Go to Step 7.
Warning!
Do not restart the board after above modification to make configuration effective in
busy hours

Level-3
Alarm Description
Alarm Property

value is 80%), the system will perform anti-DOS attack for 8000 IP addresses. Anti-DOS
attack consumes too many P-CSCF resources, which affects normal service processing,
such as calls and registrations.
Probable Causes
l The current P-CSCF NE receives mass malicious attack messages from different
subscribers.
2-255


configuration statistics time interval is 30s, message upper limit times is 600.)
l Y->Go to Step 3.
l N->Go to Step 2.
l Y->End.
l N->Go to Step 7.
Warning!
check whether to add the IP address to the whitelist.
l Y->Go to Step 5.
l N->Go to Step 4.
l Y->End.
l N->Go to Step 6.
l Y->End.
l N->Go to Step 6.
Warning!
After the users are added, their messages are regarded as trustworthy and will be not
tested by the anti-DOS attack.
l Y->End.
2-256

l N->Go to Step 7.
Warning!
Restart the board to make above configuration effective.Do not perform this operation
in busy hours.
2-257

2-258

Chapter 3
Notification Message
Handling
Table of Contents
1600 CPU resets on a board in the same shelf...........................................................3-2
4418 Logic CPU is power on successfully ..................................................................3-3
4419 Logic CPU is power on failed.............................................................................3-4
5189 Board change over notice ................................................................................3-14
5448 Environment parameters set fail ......................................................................3-16
5720 The CDM data was covered ............................................................................3-18
5983 Write back version information.........................................................................3-18
5984 Check version information ...............................................................................3-19
5985 Synchronize version information ......................................................................3-20
6720 Notice of power-on status of C51 board/ Board soft reset ................................3-21
10048 Insufficient memory........................................................................................3-22
18241 TCP connection closed..................................................................................3-23
20802 An IP address conflicts with another system on the subnet ............................3-25
20803 A MAC address conflicts with another system on the subnet .........................3-27
30820 Memory inform reported by BIOS ..................................................................3-28
2365980933 Subscriber Login Notification................................................................3-31
2365981442 Loaded License File Will Expire ...........................................................3-32
2365981702 Wrong Independent Board Type...........................................................3-33
2365982210 Automatic Backup Succeeded .............................................................3-34
ALM-2399577347 SIP Link Blocked ........................................................................3-35
ALM-2399577348 SIP Link Unblocked .....................................................................3-36
ALM-2399577350 Force to Terminated Call for Session-Timer Time Out ..................3-37
ALM-2399577352 Dynamic Host with the Same Name Already Exists .....................3-37
ALM-2399577353 Static Host with the Same Name Already Exists ..........................3-38
ALM-2399841026 Load Socket Configuration Fail ....................................................3-39
ALM-3154509825 Illegal Registration .......................................................................3-40
ALM-3154509826 Illegal Call....................................................................................3-42
ALM-3154509827 Emergency Call ...........................................................................3-43
ALM-3154509828 HSS/SLF Response Timeout .......................................................3-44
ALM-3154509829 Unknown HSS Address ...............................................................3-45
ALM-3154509830 Gq/Gq'/Rx Interface Response Timeout.......................................3-47
ALM-3154509831 E2 Interface Response Timeout...................................................3-50
ALM-3154509832 HSS User Data Exceeds System Capability ................................3-52
ALM-3154509833 Shared iFC Configuration Error ...................................................3-54
3-1

ALM-3154509834 Data Audit Function Found Exception Data .................................3-55

ALM-3154509835 Data Audit Complete ...................................................................3-56
ALM-3154509837 Detect Extra-long Call..................................................................3-57
ALM-3154509838 Release Extra-long Call by Force ................................................3-58
ALM-3154509839 Release Call Because of Subscriber Is Deleted ...........................3-60
ALM-3154509840 Route Reselection After Failure ...................................................3-61
ALM-3154509841 Default iFC Configuration Error....................................................3-62
ALM-3154513938 Adjacent Host Has Been Set Block..............................................3-64
ALM-3154513939 Adjacent Host Has Been Set Unblock..........................................3-65
ALM-3154513942 Host Group Switches from Redundant Status to Abnormal
Status.......................................................................................................................3-66
ALM-3154513943 Host Group Switches from Abnormal Status to Redundant
Status.......................................................................................................................3-67
ALM-3154513944 Attribute of Host Group Changed.................................................3-68
ALM-3154513945 Routing Status of Host Changed..................................................3-68
ALM-3154534657 Charging Module Fails to Obtain Configuration............................3-69
3.1 1600 CPU resets on a board in the same shelf

Alarm Description
This notification is generated when the CMM board detects that boards in other slots of
the same shelf are reset.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
"Slot" number Indicates the "Slot" number of the reset board.
"CPU" number Indicates the "CPU" number of the reset board.
Alarm Cause
1. The board is reset abnormally.
2. The board is reset manually.
Impact
Services fail to bear on the board during the board reset.
3-2

Chapter 3 Notification Message Handling
Action
1. Check the operation logs (Checking Log Files), and check whether the board is reset
by the network management system.
l Yes -> End.
l No -> Step 2.
3.2 4418 Logic CPU is power on successfully

Alarm Description
This notification is generated when the board detects that all processes under the logical
CPU are powered on successfully. This notification indicates that the logical entity is
powered on successfully, and is in operating status.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Rack No. Indicates the "Rack" number of the powered-on

board.
Shelf No. Indicates the shelf number of the powered-on

board.
Slot No. Indicates the "Slot" number of the powered-on

board.
Logic CPU No. Indicates the logical "CPU" number of the

powered-on board.
Alarm Cause
All processes under the logical CPU are powered on successfully.
Impact
None.
Action
No action is required.
3-3

3.3 4419 Logic CPU is power on failed

Alarm Description
This notification is generated when the board detects that one or more processes under
the logical CPU fails to be powered on or a timeout occurs when one or more processes
under the logical CPU is powered on.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Rack No. Indicates the "Rack" number of the powered-on

board.
Shelf No. Indicates the shelf number of the powered-on

board.
Slot No. Indicates the "Slot" number of the powered-on

board.
Logic CPU No. Indicates the logical "CPU" number of the

powered-on board.
Power-on failure type Indicates the JOB type that fails to be powered
on. The options are as follows:
l power on failed
l power on timeout
Name of failed process Name of the process to which the failed power
on JOB belongs.
Power-on failure JOB number Indicates the JOB that fails to be powered on.
Power-on failure code Indicates the error code for the power-on failure
of the JOB. The options are as follows:
l Operating system configuration JOB: Failed
to save the predefined timer.
l SNMP process starting communication
thread failure
l Get power on reason fail.
l Initialize multi db control area fail.
l Master/slave save buffer memory allocation
failed.
3-4

l ACK or TEMP buffer memory allocation

failed.
l Create receive instance fail.
l Create transmit instance fail.
l Allocate buf fail.
l Failed to synchronize receiving process
buffer allocation
l Record level storage global information
buffer allocation failure
l VMM JOB: Initialize failed
l VMM JOB: Initialize physical configure
database failed
l VMM JOB: Get logic address failed
l VMM JOB: Get board position failed
l VMM JOB: Start service task failed
l VMM JOB: Initialize dependent version list
failed
l VMY JOB: Initialize failed
l VMY JOB: Get logic address failed
l VMY JOB: Get board position failed
l VMY JOB: Get board IP failed
l VM_ZDB_VER JOB: Create version
database failed
l VM_ZDB_VER JOB: Load version database
from local failed
l VM_VER_ACCESS JOB: Register failed
l VML JOB: Initialize failed
l VML JOB: Get physical address failed
l VML JOB: Get self JID failed
l VML JOB: Load configure library failed
l VML JOB: Initialize configure library failed
l VML JOB: Get JID by JNO failed
l VML JOB: Send asynchronous message
failed
l Fault management: JOB initialization failure
l Card management: JOB initialization failure
l Control panel check: JOB initialization failure
l Control panel check: Wait for the database's
reply to the data change notification
registration request. Setting timer fails.
l Control panel check: Database returns a
data change notification registration failure
message.
3-5

l Control panel check: The database's reply

to the data change notification registration
request is not received.
l Medium panel check: JOB initialization
failure
l Status management agent: JOB initialization
failure
l Status management agent: Configuration
management initialization failure
l Status management agent: Failed to send
the data change notification registration
request to the database.
l Status management agent: Wait for the
database's reply to the data change
notification registration request. Setting timer
fails.
l Status management agent: The database's
reply to the data change notification
registration request is not received.
l Status management service: JOB
initialization failure
l PHY: Failed to get logical address
l PHY: Failed to create PLAT_DB
l PHY: Failed to load PLAT_DB
l PHY: Synchronize data timeout
l PHY: Failed to synchronize data
l PHYACCESS: Failed to initialize PHYLIB
l SYSCFG: Failed to get JID
l SYSCFG: Failed to initialize PHYLIB
l SYSCFG: Failed to overload PHYLIB
l SYSCFG: Failed to call VMM register
function
l SYSCFG: Received failure register message
from VMM
l SYSCFG: Can't receive success register
message from VMM
l SYSCFG: Failed to call OAM register
function
l Signalling data JOB: Request for
configuration field failure
l Signalling data JOB: Failed to obtain relevant
configurations from the protocol stack
process
3-6

l Signalling data JOB: Failed to invoke

database interface to trigger configuration
modification
l Signalling data JOB: Failed to obtain the
instance number of the current process
l Signalling data JOB: Failed to register CLI
l Signalling data JOB: Failed to initialize the
physical configuration library handle
l Signalling data JOB: Failed to connect the
platform database
l Signalling data JOB: Failed to invoke
database interface to register a dynamic
database
l Signalling data JOB: Failed to create a table
l Signalling data JOB: Failed to set the key
process
l Signalling data JOB: Failed to register the
dynamic multicast of a database
l Signalling data JOB: Failed to initialize the
table handle
l Signalling data JOB: Failed to write the
maximum configuration information table of
the association
l Signalling data JOB: Failed to send power-on
success message to the main control
l Signalling data JOB: Failed to create the
signalling database
l Signalling data JOB: The standby board fails
to get power-on data from the active board.
l Microcode maintenance process hardware
l Microcode maintenance process starting
medium panel failure
l Microcode maintenance process
synchronization timeout processing
failure
l Microcode maintenance process updating
hardware unit configuration failure
l Microcode maintenance process starting
network processor microcode failure
l Microcode table agent creating configuration
file request timer failure
3-7

l Microcode table agent sending configuration

file request failure
l Microcode table agent initialization failure
l Microcode table agent configuration file
request timer timeout (less than 10 times)
l Microcode table agent configuration file
request timer timeout (more than or equal
to 10 times)
l Microcode test process creating timer failure
l Microcode test process starting check timer
failure
l Microcoded processor configuring JOB
l Microcode resource management JOB
power-on initialization failure
l Microcode configuration service initialization
failure
l Microcode configuration service obtaining
database information from the dynamic
database failure
l Microcode configuration service initializing
private database area failure
l Microcode configuration service obtaining
OAM JNO failure
l Microcode configuration service registering
JOB on OAM failure
l Microcode configuration service creating a
database failure
l Microcode configuration service loading a
database or table handle failure
l Microcode configuration service loading
table trigger failure
l Microcode configuration service re-writing
data failure
l Microcode configuration service localizing
protocol stack handle failure
l Microcode configuration service localizing
physical configuration handle failure
l Microcode configuration service sending the
registration change notification message to
the database failure
l Microcode configuration service writing the
table to buffer from the database failure
3-8

l Microcode configuration service starting

check timer failure
timer failure
l Microcode configuration service processing
active/standby synchronization response
failure
l Microcode configuration service
synchronization for three times failure
check timer failure
l Failed to initialize inner media interface
l Failed to initialize outer interface
l Failed to initialize the 1st sub-module of
route management
l Failed to malloc l2 forward table
l Failed to initialize the 1st sub-module of trust
unicast
configuration management module
l Failed to initialize timer management module
l Failed to initialize the 2nd sub-module of
route management
l Failed to initialize the 3rd sub-module of
route management
l Failed to initialize the 4th sub-module of
route management
route management
route management
interface management module
thread management module
route management
route management
3-9


trust unicast
l Failed to allocate SOCKET memory
l Failed to initialize SOCKET timer
l Failed to read parameter configuration file
route management
l Failed to allocate ZERO-COPY memory
l Failed to initialize the global variable of
COURIER
l Failed to initialize the global variable IP
instance of COURIER
l Failed to initialize the member parameter of
global variable IP instance of COURIER
l Failed to enable the global variable IP
instance of COURIER
l Failed to initialize the VPN manager of
COURIER
l Failed to initialize the global variable of OSPF
3-10

l Failed to initialize the global variable of BGP

l Failed to initialize the global variable of
VRRP
route management
l Failed to initialize message compatibility
module
l Failed to create cycle timer for receiving
internal media packets
l Failed to join in the multicast group
l Failed to initialize RAWMAC diagnosis
l Failed to register with SCS
l Failed to synchronize data
l Failed to query board type
l Failed to query port type
l Failed to open dynamic lib
l Failed to initialize the lower-layer drive
l Failed to get board address
l Failed to set FTP function
l Failed to initialize physical configure
l Failed to notify the database of registration
configuration modification
l Failed to get gate configure info
l Failed to reqest for QoS configuration
l Failed to initialize intergmp
l Failed to load port agent library
l Failed to load the dynamic library
l Failed to get power on reason
l Failed to get process id
l Failed to set the lower-layer drive queue
power-on cause
l Failed to initialize config manage
l Failed to create thread
l Failed to register callback function
l Failed to query slot type
3-11

l Failed to malloc memory

l Failed to create semaphore for ARP list
l Failed to create semaphore for the linked list
l IMA chip initialization fail
l Failed to allocate memory
l Failed to load dynamic library
l Failed to manage initialization local variables
at ATM layer
l IPOA get invalid board type
l IPOA initialize local variables fail
l Failed to get physical address
l Failed to get ATM job's id
l Failed to send registration request message
to system control
l Succeeded to send registration request
message to system control. No response
(reserved).
l The response from system control is
received. However, the message is null.
l Failed to create ATM configuration file
information sharing memory
l Failed to obtain ATM configuration file (three
possibilities: 1. Response message fault; 2.
Configuration information error; 3. Read file
failure)
l Failed to register overloaded function
l ATM configuration file information sharing
memory does not exist.
l Failed to set table handle of ATM local
l Failed to get the logical address of this board
l Failed to create power-on label sharing
memory
l Failed to create configuration modification
notification label sharing memory after IMA
is powered on
notification label sharing memory after ATM
is powered on
notification label sharing memory after IPOA
is powered on
l Failed to register ATM database callback
function dynamic database
3-12

l Failed to create tables of ATM

l Failed to create temp tables of ATM
l Failed to load data from database storage file
l Failed to synchronize data
l Waiting SCS_PHY power on
l Waiting ATM first instance power on
l Failed to request data
l Data synchronization request. Database
management process replies Failure.
l Failed to create ATM database
l Failed to connect ATM database
l Unknowable reason
l
Alarm Cause
1. One or more processes under the logical CPU fail to be powered on.
2. A timeout occurs when one or more processes under the logical CPU fail to be pow-
ered on.
Impact
The logical board fails to operate properly.
Action
1. Check whether the board is OMP ("Module" number is 1, and "Unit" number is 65535)
in accordance with the "Module" number and "Unit" number in alarm information.
l Yes -> Step 2.
l No -> Step 4.
2. Check whether the master OMP module operates properly from the rack diagram.
l Yes -> Step 10.
l No -> Step 3.
3. Wait for the master OMP to operate properly, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 10.
4. Run the SHOW MODULE command to query the corresponding standby "Slot"
number in accordance with the "Rack" number, "Shelf" number, and "Slot" number in
the alarm information, and check whether the partner board operates properly from
the rack diagram (New Chassis Management Module).
l Yes -> Step 6.
l No -> Step 5.
5. Wait for the partner board to operate properly, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 6.
3-13

6. Check whether the master OMP module operates properly from the rack diagram.
l Yes -> Step 8.
l No -> Step 7.
7. Wait for the OMP to operate properly, and check whether the alarm is cleared.
l Yes -> End.
l No -> Step 8.
8. Check whether the following alarms exist:
l Yes -> Step 9.
l No -> Step 10.
l Yes -> End.
l No -> Step 10.
3.4 5189 Board change over notice

Alarm Description
This notification is generated after the board active/standby handover completes.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Result of changeover Indicates the changeover result, successful and failed. The options
are as follows:
l CPU change over to master
l CPU change over fail
Failure reason Indicates the detailed causes when the current changeover fails.
l None
l Master board change over forbidden
l Slave board change over forbidden
l Slave board pre change over fail
l Slave board change over fail
l Master board change over fail
l Board is not master-slave configuration
3-14

l Mate board is not online

l Board is not master
l Board is not in work
l Communication between master and slave is abnormal
Change over reason Indicates the specified causes of the current changeover. The
l Changeover of the debugging function
l Mate board offline
l Mate board give up master
l DSP error
l IPMC reset CPU
l Board power off
l OMC port error
l IDE abnormal
l Push EXCH
l Board power off
l Clock lost
l PLL error
l Board clock abnormal
l EC chip error
l Internal media port error
l OMC port all error
l External media port error
l External media port error
l Slot priority master configuration
l Inner media plane trunk error
l Control plane port down
l Control plane of board is island
l TIPC message retransmission rate exceeds the threshold level
1 fault
l TIPC message retransmission rate exceeds the threshold level
2 fault
l RAWMAC communication check fail
l Media communication check fail
l T network switching card SERDES link fault
l T net fiber FPGA error
l T network switching card control shelf SERDES connected
FPGA device fault
l T net shelf HW error
l Board HW loop check error
l RAWMAC check failed for 5 minutes
l RAWMAC check failed for 20 seconds
3-15

l Sending or receiving packets between administration port and

CPU control port failed
l Board self loop check abnormal
l T net matrix check error
l T network switching card active/standby SERDES link fault
l TDM link check error
l TDM SERDES check error
l Half-fix connection error
l File system read only
l Hard disk can't be used
l Smart is abnormal or can't be gotten
l RAID abnormal
l Optical port and APS channel are both error
l MML normal change over request
l MML force change over request
l Board BFD link down
l Board port receive bad frames
l Queue overload
l Half amount of IPMCs in the shelf lost communication with CMM
l IMA group abnormal
l Service fault
Changeover duration (ms) Duration used by the current active/standby changeover.
Alarm Cause
The board handover operation is performed automatically or manually.
Impact
None.
Action
3.5 5448 Environment parameters set fail

Alarm Description
This notification is generated if the CMM fails to set environment monitoring parameters
on the monitoring board.
3-16

Alarm Information
l Auto Clear: Yes
Alarm Parameters
Rack number Indicates the "Rack" number of the environment

monitoring board that causes the alarm.
Flag of failed configuration (bits from left to Type of an environment parameter that fails to
right mean: m alarm suppression identifier; be set.
rack over/under temperature threshold; room
over/under temperature threshold; room
over/under humidity threshold; fan speed control
threshold; over/under voltage threshold): 0
means setting succeeds; 1 means setting failure;
Alarm Cause
1. The communication between the CMM and the environment monitoring board is
abnormal.
2. The environment monitoring board is faulty.
Impact
The configured environment parameters are not effective, and the monitoring result may
differ from the real circumstance. No impact on service.
Action
1. Check whether the following alarm exists:
5382 Environment monitor board communication is abnormal

l Yes -> Step 2.
l No -> Step 3.
l Yes -> End.
l No -> Step 3.
3. Run the RESET NORMAL command to reset the board, and check whether the
notification still exists.
l Yes -> Step 4.
l No -> End.
3-17

3.6 5720 The CDM data was covered

Alarm Description
This notification is generated if a board detects that the information stored in the right and
left CDMs is different, and then it synchronizes the information.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Type of CDM data cover Type of the CDM data cover, including from right to left and from left to
right. The options are as follows:
l CDM data cover from left to right
l CDM data cover from right to left
Result of CDM data cover Indicates whether the CDM data cover is successful.
Alarm Cause
The information stored in the right and left CDMs is different.
Impact
None.
Action
3.7 5983 Write back version information

Alarm Description
This notification is raised if the operating version is saved to a storage device in file format
from the peer end or the memory after the board is powered on for five minutes.
Alarm Information
l Auto Clear: Yes
3-18

Alarm Parameters
Reason for version Version write-back information of the board. The options are as follows:
write-back l Write back version started
l Write back version finished and successful
l Write back version finished and failed
Alarm Cause
1. The version write-back starts.
2. The version write-back ends successfully.
3. The version write-back ends but failed.
Impact
If the version write-back fails, the device may fail to be started after it is shut down.
Action
3.8 5984 Check version information

Alarm Description
This notification is raised if the version file information of the board is consistent with that
configured in the database.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Reason for version check Version check information of the board. The options are as
follows:
l Check version started
l Check version finished and successful
l Check version finished and failed
Alarm Cause
1. The version check starts.
2. The version is checked successfully.
3-19

3. The version check failed.
Impact
None.
Action
3.9 5985 Synchronize version information

Alarm Description
This notification is raised when the version files on the active and standby boards are
synchronized.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Reason for version Version synchronization information of the board. The options are
synchronization as follows:
l Synchronize version started
l Synchronize version finished and successful
l Has in process
l Synchronize version finished, mate board may leave position
l Synchronize version finished, inquire database failed
l Synchronize version finished and failed
Alarm Cause
1. The version synchronization begins.
2. The version synchronization ends successfully.
3. The version is being synchronizing.
4. The version synchronization ends, but the peer board may be offline.
5. The version synchronization ends, but the database fails to be queried.
6. The version synchronization ends but failed.
3-20

Impact
When the active/standby board fails to synchronize version files, the version files of the
active/standby board may be inconsistent with each other or incomplete. In this case, the
system has potential risks.
Action
3.10 6720 Notice of power-on status of C51 board/

Board soft reset
Alarm Description
This notification is generated if the environment monitoring board is powered on
successfully, or it is reset successfully.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Rack number Number of the rack where the faulty board is located.
Alarm Cause
The environment monitoring board is powered on successfully, or the soft reset on the
board is successful.
Impact
None.
Action
3-21

3.11 10048 Insufficient memory

Alarm Description
During the operation of the board's real-time database, it requests for dynamic memory
with the increase of the user number. During this process, if the memory usage reaches
the threshold, this alarm is generated.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
JOB ID ID of a JOB that fails to be executed when the alarm is generated.
database name Name of a database to which the alarm data belongs.
Type of memory request failure Type of database application failures when the alarm is generated.
l new page fail
l new pages fail
l new block fail
l extend mem fail
Number of pages Number of applied memory pages when the alarm is generated.
Alarm Cause
1. The physical memory of the board is insufficient.
2. The database space is not enough.
Impact
Services may be affected.
Action
1. Check whether the following alarm exists:
3584 Memory insufficient alarm
l Yes -> Step 2.
l No -> Step 3.
2. After the related alarm is handled, check whether this alarm still exists.
l Yes -> Step 3.
l No -> End.
3-22

3.12 18241 TCP connection closed

Alarm Description
This alarm is generated when the status of the TCP link is changed from establish to close
or the local end that acts as the TCP client fails to establish a link for a long time.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Local Port Local port number for a TCP link.
Peer port number Peer port number for a TCP link.
Local host IP Address Local IP address for a TCP link.
Peer host IP Address Peer IP address for a TCP link.
ucReason Causes of TCP link interruption. The options are as

follows:
l SYN waiting timeout
l FIN waiting timeout
l retransmission timeout
l RST is received.
Alarm Cause
1. The hardware of the board is faulty.
2. The TCP channel on both ends is faulty.
3. The configuration on both ends is not matched.
Impact
The TCP connection is interrupted, and services may be affected.
Action
command in accordance with "Peer host IP Address" in alarm information to check the
route configuration meets the real requirements.
l Yes -> Step 3.
l No -> Step 2.
3-23

2. Run the IPSTACK command to enter protocol stack mode, run the ADD IP ROUTE/D
EL IP ROUTE command to modify the corresponding route configuration as required,
and check whether the notification still exists.
l Yes -> Step 3.
l No -> End.
l Yes -> Step 4.
l No -> Step 5.
required, check whether the notification still exists.
l Yes -> Step 5.
l No -> End.
command in accordance with "Peer host IP Address" in notification information
to confirm the logical information (port quintuplet ) and the physical information
information and physical information of the ingress interface board in accordance with
"Local host IP Address" in notification information and the real requirement of the
l Yes -> Step 6.
l No -> Step 7.
6. Handles the above alarms and check whether the notification still exists.
l Yes -> Step 7.
l No -> End.
7. Check whether "Reason" in alarm information is "SYN waiting timeout".
l Yes -> Step 10.
l No -> Step 8.
8. Check whether "Reason" in notification information is "retransmission timeout".
l Yes -> Step 10.
l No -> Step 9.
9. Check whether "Reason" in alarm information is "RST is received".
l Yes -> Step 11.
l No -> Step 13.
10. Run the IPSTACK command to enter protocol stack mode, run the PING command
on 1200 packets in accordance with "Peer host IP Address" in alarm information to
check whether packet loss occurs.
l Yes -> Step 11.
l No -> Step 13.
has related alarms.
3-24

l Yes -> Step 12.

l No -> Step 13.
the notification still exists.
l Yes -> Step 13.
l No -> End.
3.13 20802 An IP address conflicts with another system

on the subnet
Alarm Description
This notification is generated when this board detects that the IPv4 address in the IP subnet
is conflicted.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Conflicted source IP address Conflicted source IP address of the ARP item

Source MAC address Source MAC address of the ARP message that
causes the alarm.
Port Quintuplet Number of the port that causes the alarm. The
port number is in form of a port quintuplet,
including the "Module" number, "Unit" number,
"Subunit" number, "Subsystem" number, and
"Port" number of the faulty port.
ARP packet type Type of the ARP message that causes the alarm,
including request ARP and reply ARP. The
l Request ARP packet
l Reply ARP packet
Destination IP address Description IP address of the ARP message that

causes the alarm.
3-25

Destination MAC address Description MAC address of the ARP message

VLAN ID of duplicate port VLAN ID of the duplicate port that causes the
alarm.
Alarm Cause
1. The IP address configuration for the network interface of this board is incorrect.
2. The IPv4 addresses in the IP subnet are conflicted.
3. The Ethernet that is connected to the network interface of this board has a loopback.
4. The VLAN configuration is wrong.
Impact
Services corresponding to the conflicted IP address of this port are interrupted.
Action
INTERFACE VLAN command to check whether "sub-interface VLAN ID" in the
configuration meets the real requirements.
l Yes -> Step 3.
l No -> Step 2.
2. Run the INTERFACE command to enter interface mode in accordance with "Port
Quintuplet" in notification information, run the SUBINTERFACE command to enter
sub-interface configuration mode, and run the ADD VLAN/DEL VLAN command to
modify "sub-interface VLAN ID". Wait for 1 minute, and check whether the notification
still exists.
l Yes -> Step 3.
l No -> End.
3. Run the SHOW IP INTERFACE BRIEF command in accordance with "Port
Quintuplet"and "Conflicted source IP address" in alarm information to confirm whether
the configured IPv4 meets the real requirements.
l Yes -> Step 5.
l No -> Step 4.
4. Run the ADD IP ADDRESS/DEL IP ADDRESS command in accordance with "Port
Quintuplet" in alarm information to modify the IP address of the port as required. End
the handling.
5. Contact the maintenance personnel of the peer end, and check whether the IPv4 and
the VLAN ID are consistent with the real requirement.
l Yes -> Step 7.
l No -> Step 6.
6. Ask the maintenance personnel of the peer end to modify the IPv4 and the VLAN ID
as required. End the handling.
3-26

7. Contact the maintenance personnel of the peer end to check whether there is a
loopback in the network.
l Yes -> Step 8.
l No -> Step 9.
8. Ask the maintenance personnel of the peer end to handle the faults. End the handling.
3.14 20803 A MAC address conflicts with another

system on the subnet
Alarm Description
This notification is generated when this board detects that the MAC address in the IP
subnet is conflicted.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
Source IP Address Source IP address of the ARP message that causes the alarm.
Conflicted source MAC Conflicted source MAC address of the ARP item that causes the alarm.
address
Port Quintuplet Number of the port that causes the alarm. The port number is in form of a
port quintuplet, including the "Module" number, "Unit" number, "Subunit"
number, "Subsystem" number, and "Port" number of the faulty port.
ARP packet type Type of the ARP message that causes the alarm, including request ARP
and reply ARP. The options are as follows:
l Request ARP packet
l Reply ARP packet
Destination IP address Description IP address of the ARP message that causes the alarm.
Destination MAC Description MAC address of the ARP message that causes the alarm.
address
VLAN ID of duplicate VLAN ID of the duplicate port that causes the alarm.
port
Alarm Cause
1. The MAC address configuration for the network interface of this board is incorrect.
3-27

2. The MAC addresses in the IP subnet are conflicted.

3. The Ethernet that is connected to the network interface of this board has a loopback.
4. The VLAN configuration is wrong.
Impact
Services corresponding to the port are interrupted.
Action
INTERFACE command to check whether the configured MAC address meets the real
requirements.
l Yes -> Step 3.
l No -> Step 2.
2. In accordance with "Port Quintuplet" in alarm detailed information, run the INTERF
ACE command to enter interface mode, and then run the SET IP MAC command to
modify the MAC address of the local port as required. End alarm handling.
3. Contact the peer maintenance personnel to check whether the MAC address is the
same with the actual requirements.
l Yes -> Step 5.
l No -> Step 4.
4. Ask the maintenance personnel of the peer end to modify the MAC address as
required. End alarm handling.
5. Contact the maintenance personnel of the peer end to check whether there is a
loopback in the network.
l Yes -> Step 6.
l No -> Step 7.
6. Ask the maintenance personnel of the peer end to handle the faults. End alarm
handling.
3.15 30820 Memory inform reported by BIOS

Alarm Description
This alarm is generated when the BIOS of the board detects the memory check error.
Alarm Information
l Auto Clear: Yes
Alarm Parameters
3-28

BIOS memory event type Type of the BIOS MEM events, such as the ECC
error. The options are as follows:
l Correctable ECC error
l Uncorrectable ECC error
Memory location Location of the faulty memory. The options are

as follows:
l DIMM 1
l DIMM 2
l DIMM 3
l DIMM 4
l DIMM 5
l DIMM 6
l DIMM 7
l DIMM 8
l DIMM 9
l DIMM 10
l DIMM 11
l DIMM 12
l DIMM 13
l DIMM 14
l DIMM 15
l DIMM 16
l DIMM 17
l DIMM 18
l DIMM 19
l DIMM 20
l DIMM 21
l DIMM 22
l DIMM 23
l DIMM 24
l DIMM 25
l DIMM 26
l DIMM 27
l DIMM 28
l DIMM 29
l DIMM 30
l DIMM 31
l DIMM 32
l DIMM 33
l DIMM 34
l DIMM 35
l DIMM 36
l DIMM 37
3-29

l DIMM 38
l DIMM 39
l DIMM 40
l DIMM 41
l DIMM 42
l DIMM 43
l DIMM 44
l DIMM 45
l DIMM 46
l DIMM 47
l DIMM 48
l DIMM 49
l DIMM 50
l DIMM 51
l DIMM 52
l DIMM 53
l DIMM 54
l DIMM 55
l DIMM 56
l DIMM 57
l DIMM 58
l DIMM 59
l DIMM 60
l DIMM 61
l DIMM 62
l DIMM 63
l DIMM 64
l X1
l X2
l X3
l X4
l X5
l X6
l X7
l X8
l X9
l X 10
l X 11
l X 12
l X 13
l X 14
l X 15
l X 16
3-30

Alarm Cause
1. The memory has a correctable error.
2. The memory has multiple correctable errors.
Impact
1. If a correctable error occurring frequently on the memory bank escalates into multiple
correctable errors, services of the board are affected.
2. If a correctable error occurs on the memory bank frequently, the memory access rate
may be reduced, and services may be affected.
Action
1. Check whether the same notification occurs twice in the same location within 24 hours.
l Yes -> Step 2.
l No -> End.
2. Remove and install the board (Common Operations of Board Replacement) in
information. Check whether this notification appears within 24 hours.
l Yes -> Step 3.
l No -> End.
3. Replace the memory bar of the board (Replacing a Memory Bar) in accordance with
the "Rack" number, "Shelf" number, "Slot" number, and "Memory location" in alarm
information, and then check whether this notification appears within 24 hours.
l Yes -> End.
l No -> Step 4.
4. Replace the faulty board with a new one (Board Replacement) in accordance with
the "Rack" number, "Shelf" number, and "Slot" number in alarm information, and then
check whether this notification appears within 24 hours.
l Yes -> Step 5.
l No -> End.
3.16 2365980933 Subscriber Login Notification

Alarm Description
The notification is raised when a user logs in to the OMM system successfully.
Alarm Information
l Auto clear: Yes
3-31

Alarm Parameters
User Name Name of the user who is logged in.
Terminal Type Type of the terminal where the user is logged in.
l OMM Client
l Telnet Client
l EMS Client
l NDF Client
l SSH Client
IP IP address of the terminal where the user is logged in.
Time Time when the user logs in to the terminal.
Auth Type Authentication mode used for login. The LDAP mode is used when the
user is authenticated through the LDAP server. Common modes are
used for others.
Alarm Cause
A user logs in.
Impact
None.
Action
3.17 2365981442 Loaded License File Will Expire

Alarm Description
The alarm is raised when a license file in the $ZXHOME/%NE%/server/conf/license
directory of the OMM server is going to be expired. By default, this notification is sent 15
days before the license file expires.
Alarm Information
l Auto clear: Yes
3-32

Alarm Parameters
There are %u days of the present Remaining days before the license expires. Maximum value:
License about to expire. 15.
Alarm Cause
A license file loaded in the OMM system is going to be expired. This notification is reported
15 days before the expiry date.
Impact
The system is not affected. A new license file should be loaded before the license expires.
Otherwise, some service functions are available.
Action
1. Run the SHOW LICENSE command to query the detailed license information, and
check whehter the Remain Days in the additional information of the alarm is correct..
l Yes -> Step 2.
l No -> Step 3.
2. The license is going to be expired, Contact ZTE technical support to upgrade the
license file to ensure normal system operation.
3.18 2365981702 Wrong Independent Board Type

Alarm Description
The alarm is raised when the independent board type is mistakenly configured, for
example, the group name configured by running the ADD FMSNMPCFG command is not
the same as that of the corresponding SNMP board queried by running the SHOW CMM
command, or the board type is not the same as the actual type. The board type can be
determined by the shelf size, for example, a 11 U board corresponds to a 11 inch shelf.
Alarm Information
l Auto clear: Yes
Alarm Parameters
CMM IP IP address of the CMM board.
3-33

Alarm Cause
1. The actual board type is different from that queried by the SHOW FMSNMPCFG
command.
2. The independent board type is determined by the shelf size, for example, the
independent board in a 11U shelf corresponds to the independent board type with
11U.
Impact
When the type of the independent board is wrong, the board alarms cannot be reported
even for the communication links are operating normally.
Action
1. Based on the independent board location in the additional alarm, run the SHOW
CMM command to check whether the board configuration is the same as the actual
configuration on the local maintenance terminal.
l Yes -> Step 3.
l No -> Step 2.
2. Run the SET CMM command to modify the CMM configuration. Wait for one minute,
l Yes -> End.
l No -> Step 3.
3.19 2365982210 Automatic Backup Succeeded

Alarm Description
The alarm is raised when the OMM server performs the automatic task backup function
successfully.
Alarm Information
l Auto clear: Yes
Alarm Parameters
Log ID Unique log backup ID, which corresponds to the input parameter
queried by the SHOW BAKLOG command.
Automatic Backup Task ID Unique automatic backup task ID, which corresponds to the input
parameter queried by the SHOW AUTO STRATEGY command.
3-34

Alarm Cause
An automatic backup task of the OMM server succeeds.
Impact
None.
Action
3.20 ALM-2399577347 SIP Link Blocked

Alarm Description
The SIP link is blocked
Alarm Property
2399577347 Notification NE alarm Communication alarm
Bearer ID Node ID
Protocol Type -
Detailed Information -

Corresponding links of the CSCF NE is disconnected, as a result, CSCF cannot transmit
SIP messages between local CSCF and specified opposite device, which impact normal
registrations and calls.
Probable Causes
This notification will happen when the link or port is blocked manually.
1. Check whether Link Blocked status is set to Blocked in the SIP link configuration by
running SHOW SIP LINK command.
l Y->Go to Step 2.
l N->Go to Step 3.
3-35

2. Check whether to unblock corresponding SIP link, modify Forced Blocking to No by

running SET SIP LINK command, and check whether the ALM-2399577348 SIP Link
Unblocked alarm is raised.
l Y->End.
l N->Go to Step 3.
3.21 ALM-2399577348 SIP Link Unblocked

Alarm Description
Unblock the SIP link
Alarm Property
Bearer ID Node ID
Protocol Type -
Detailed Information -

The corresponding SIP link of the CSCF NE becomes available from the blocked status,
and then it can transmit SIP messages between local CSCF and specified opposite device.
Probable Causes
The corresponding SIP link is unblocked manually.
1. Check whether Link Block status is set to Blocked in the SIP link configuration by
l Y->Go to Step 2.
l N->Go to Step 3.
2. Check whether to unblock corresponding SIP link, modify Forced Blocking to No by
running SET SIP LINK command, and check whether the ALM-2399577348 SIP Link
Unblocked alarm is raised.
l Y->End.
l N->Go to Step 3.
3-36

3.22 ALM-2399577350 Force to Terminated Call for

Session-Timer Time Out
Alarm Description
The session timer times out, which terminates a call
Alarm Property

The call will be released by force, which influences users' experience.
Probable Causes
l The session refresh timer configuration fails to comply with the planning.
l The terminal fault times out, and the terminal fails to send UPDATE messages to the
CSCF NE.
1. Check whether the session refresh timer configuration complies with the planning by
running SHOW SIP GLOSESSIONTIMER command.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify the session refresh timer according to the planning by SET SIP
GLOSESSIONTIMER, and check whether the alarm is cleared.
l Y->End.
l N->Go to Step 3.
3. Select Signaling Trace > Trace by User to check whether corresponding client reports
session refresh messages within a given time.
l Y->Go to Step 4.
l N ->check terminal configuration
3.23 ALM-2399577352 Dynamic Host with the Same

Name Already Exists
Alarm Description
Dynamic host with the same name already exists.
3-37

Alarm Property
2399577352 Notification NE alarm Equipment alarm

The configured dynamic adjacent host cannot be used.
Probable Causes
Dynamic host with the same name already exists.
1. Get the dynamic host name list by SHOW DYADJHOSTINFO, and then check whether
the host name in additional alarm information is included.
l Y->Go to Step 2.
l N->End.
2. Get the static host name list by SHOW ADJHOST, and then check whether the host
name in additional alarm information is included.
l Y->Go to Step 3.
l N->End.
3. Delete the host name in additional alarm information from the static adjacent host list
by DEL ADJHOST.
3.24 ALM-2399577353 Static Host with the Same Name

Already Exists
Alarm Description
Static host with the same name already exists.
Alarm Property

The configured static adjacent host cannot be used.
Probable Causes
Static host with the same name already exists.
3-38

1. Get the dynamic host name list by SHOW DYADJHOSTINFO, and then check whether
the host name in additional alarm information is included.
l Y->Go to Step 2.
l N->End.
2. Get the static host name list by SHOW ADJHOST, and then check whether the host
name in additional alarm information is included.
l Y->Go to Step 3.
l N->End.
3. Delete the host name in additional alarm information from the static adjacent host list
by DEL ADJHOST.
3.25 ALM-2399841026 Load Socket Configuration Fail

Alarm Description
Reading SIP SOCKET configuration fails.
Alarm Property

Probable Causes
1. Run the SHOW SIP ACCADDR command to check whether the configuration complies
with the plan.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Run the SET SIP ACCADDR command to modify the configuration according to the
plan.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Run the SHOW TCPCONN command to check whether the configuration complies
with the plan.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Run the SET TCPCONN command to modify the configuration according to the plan.
3-39

l Y->Go to Step 5.
5. Run the SHOW SIPSCTP command to check whether the configuration complies with
the plan.
l Y->Go to Step 7.
l N->Go to Step 6.
6. Run the SET SIPSCTP command to modify the configuration according to the plan.
l Y->Go to Step 7.
7. Check whether the notification of failure to read SIP SOCKET configuration is reported
again.
l Y->Go to Step 8.
l N->End.
3.26 ALM-3154509825 Illegal Registration

Alarm Description
Illegal registration
Alarm Property
3154509825 Notification NE alarm Processing error alarm

The user cannot register, re-register or de-register, which influences users' experience.
Probable Causes
l PVI or PUI are not allocated on the HSS in the initial registration/refresh
registration/de-registration messages.
l PVI or PUI are not associated on the HSS in the initial registration/refresh
registration/de-registration messages.
l HSS receives a de-registration request initiated by the user. The request carries
information that user's registration status is unregistered .
l The Public User Identity is barred on HSS.
l The Public User Identity is not allowed to roam in the visited network on HSS.
1. Select proper handling approach based on the alarm causes in alarm information.
l Unknown PVI/PUI ->Go to Step 2.
l PVI and PUI are not matched ->Go to Step 4.
l The unregistered user originates the de-registration->Go to Step 7.
l The Public User Identity is barred ->Go to Step 8.
3-40

l Roaming restriction ->Go to Step 9.

2. Judge whether the Private User Identity or Public User Identity is served in the IMS
subsystem.
l Y->Go to Step 3.
l N->End.
3. Check whether the Private User Identity and the Public User Identity are configured
on HSS.
l Y->Go to Step 4.
l N->Go to Step 5.
4. Check whether the Private User Identity and the Public User Identity are matched on
HSS.
l Y->Go to Step 10.
l N->Go to Step 6.
Note:
If mass IMS users report this notification because the PVI and the PUI are not
configured or matched, check number allocation on HSS, there may be missing
or wrong numbers in the plan.
5. Configure and then associate the PVI and the PUI, the user re-originates a registration
request, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 10.
6. Associate the PVI and the PUI on HSS, the user resends a registration request, and
check whether the notification is cleared.
l Y->End.
l N->Go to Step 10.
7. View users' registration information by running SHOW REG command and check
whether the user originating the de-registration is registered.
l Y->Go to Step 10.
l N->End.
Note:
Do not de-register a user before he/she is registered.
8. Check whether the Public User Identity is barred on HSS.

l Y ->Go to Step 10.
l N->End. (decide whether to remove the restriction on user registration)
9. Check whether network visited ID is in the trusted network list on HSS.
3-41

l Y->Go to Step 10.

l N->End. (decide whether to add the network visited ID to the allowable visited
network list)
3.27 ALM-3154509826 Illegal Call

Alarm Description
Illegal call
Alarm Property

The unregistered users, number-unallocated users and barred users are forbidden to
make a common call in the IMS system, if above users make a call, their requests are
rejected and a notification is reported for each call. Mass illegal calls will impact system
performance.
Probable Causes
l Unknown Public User Identity
l Unregistered user makes a call
l Barred user makes a call.
1. Select proper handling approach based on the alarm causes in alarm information.
l Unknown Public User Identity->Go to Step 2.
l An unregistered user makes a call ->Go to Step 3.
l A barred user makes a call ->Go to Step 5.
2. Check whether this Public User Identity exists on HSS.
l Y->Go to Step 3.
l N->Go to Step 4.
3. Query user registration information by running SHOW REG command to check
whether this user is registered.
l Y->Go to Step 6.
l N->Go to Step 5.
4. Check whether the PUI carried in messages from the terminal is correct.
l Y->Go to Step 6.
l N->End.
5. Check whether this user is barred on HSS.
3-42

l Y->End.
l N->Go to Step 6.
3.28 ALM-3154509827 Emergency Call

Alarm Description
Emergency call
Alarm Property

An urgent call means a user dials the urgent call number, such as 112 and 911, in case of
emergency, and the carrier identifies this call as an urgent call, and assigns higher priority
and resources for this call, and finally forwards the call to adjacent urgent call center based
on terminal location information in the call.
Probable Causes
There is an urgent call.
1. Check the called number in additional alarm information. tel:112 to judge whether this
call should be regarded as an urgent call.
l Y->End.
l N->Go to Step 2.
2. Obtain the access IP address of the call by package capturing or signaling tracing,
proceed to step 3.
3. Query the entrance configuration policy by SHOW ENTPLC command, and obtain the
service group index based on Subnet and Subnet Mask, and proceed to step 4.
4. Based on the service group index obtained in step 3, obtain the router selector by
running SHOW SVCGRP command, and proceed to step 5.
5. Select proper handling steps based on number type.
l The called number is in TEL format, such as tel:112 ->Go to Step 6.
l The called number is in SIP format, such as sip: 112@zte.com.cn ->Go to Step 8.
l The called number is in URN format, such as urn:service:sos.police ->Go to Step
10.
6. Obtain the property analysis record and TEL analysis number by running SHOW TE
LANA command, such as SHOW TELANA:DIGIT="112",RTSEL BEGIN=1; (DIGIT:
called number, RTSEL BEGIN: router selector) ->Go to Step 7.
3-43

7. Modify this called number to non-urgent call number by running SET TELANA
command, such as SET TELANA:ID=1,SRVATTR="COMM"; (ID: TEL analysis
number in step 6, SRVATTR: service attribute COMM means a common call) ->End.
8. Obtain the property analysis record and URI analysis number by running SHOW UR
IANA command, such as SHOW URIANA:URI="112@zte.com.cn",RTSEL BEGIN=1;
(URI: called number, RTSEL BEGIN: router selector) ->Go to Step 9.
9. Modify this called number to non-urgent call number by running SET URIANA
command, such as SET URIANA:ID=1,SRVATTR="COMM"; (ID: URI analysis
number in step 8, SRVATTR: service attribute COMM means a common call) ->End.
10. Obtain the property analysis record and URN analysis number by running SHOW EMG
URNANA command, such as SHOW EMGURNANA:URN="service:sos.police"; (URN:
called number) ->Go to Step 11.
11. Modify this called number to non-urgent call number by running SET EMGURNANA
command, such as SET EMGURNANA:ID=1,SRVATTR="COMM"; (ID: URN analysis
number in step 10, SRVATTR: service attribute COMM means a common call)
3.29 ALM-3154509828 HSS/SLF Response Timeout

Alarm Description
HSS/SLF response timeout
Alarm Property

All subscription data are saved on HSS. During user registration and calls, CSCF
downloads user data from HSS directly or after redirected from SLF through Cx/Dx
interfaces. Interactive requests include UAR/LIR/MAR/SAR, if SLF/HSS makes no
UAA/LIA/MAA/SAA response or makes slow response to these requests, this notification
occurs, and mass notification will impact user's experience.
Probable Causes
SLF/HSS makes no response or makes slow response to UAR/LIR/MAR/SAR.
1. Check whether the UAR/LIR/MAR/SAR request messages are sent successfully by
DIAMETER signaling tracing or package capturing.
l Y->Go to Step 2.
l N->Go to Step 3.
3-44

2. Check whether CSCF receives the UAA/LIA/MAA/SAA response from SLF/HSS by

DIAMETER signaling tracing or package capturing.
l Y->Go to Step 9.
l N->Go to Step 3.
Note:
Waiting time for the response message UAA/LIA is 16s constantly, and for
MAA/SAA is 12s constantly.
3. Check whether the DIAMETER link is normal by running SHOW DIMLNKSTAT

command.
l Y->Go to Step 9.
l N->Go to Step 4.
4. Enter the protocol mode by running IPSTACK command, and check whether
communication between local NE and opposite NE is normal by PING and exit this
mode by running EXIT MODE command.
l Y->Go to Step 7.
l N->Go to Step 5.
5. Troubleshoot the network connection, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 6.
6. Troubleshoot the opposite NE, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 7.
7. Query the SCTP association configuration by running SHOW DIMSCTP command,
and check whether the configuration matches the HSS configuration.
l Y->Go to Step 9.
l N->Go to Step 8.
8. Modify the SCTP association configuration according to the planning by running SET
DIMSCTP command, transmit data by running SYN command, and check whether the
notification is cleared.
l Y->End.
l N->Go to Step 9.
3.30 ALM-3154509829 Unknown HSS Address

Alarm Description
The HSS address is unknown
3-45

Alarm Property

This notification will result in the following problem. Mass notification will impact user’s
experience greatly.
l ICSCF fails to obtain the HSS address (HSS host name/domain name), and thus it
fails to query HSS, or obtains home SCSCF and authentication information, which
results in registration and session failure.
l SCSCF fails to obtain the HSS address, and then fails to obtain authentication
information and user data, which finally result in registration or calling failure.
Probable Causes
l The HSS host name is not configured on SLF interconnected to ICSCF or SCSCF.
l The HSS host name is illegal or ultra-long on SLF interconnected to ICSCF or SCSCF.
l When the PUI is in TEL format, you have not configure the Home Domain Name in
TEL digit analysis on ICSCF or SCSCF.
1. Check whether you have configured HSS host name on SLF interconnected to ICSCF
or SCSCF.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Configure or modify corresponding HSS host name, and check whether the notification
is cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether the UAA/LIA/MAA/SAA response contain HSS host name and whether
the HSS host name in the Rediect-Host AVP exceeds the restricted 127 bytes in length
by Diameter signaling tracing or package capturing.
l Y->Go to Step 6.
l N->Go to Step 4.
4. Query TEL number analysis by running SHOW TELANA command, check whether
you have configured accurate Home Domain Name in the HSS route analysis.
l Y->Go to Step 7.
l N->Go to Step 5.
5. Set accurate Home Domain Name in TEL number analysis by running SET TELANA
command, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 7.
6. Modify the HSS address on SLF if too long, or troubleshoot the opposite SLF NE fault.
3-46

3.31 ALM-3154509830 Gq/Gq'/Rx Interface Response

Timeout
Alarm Description
Gq/Gq'/Rx interface response times out
Alarm Property

As the interface definition of the 3GPP protocol earlier than the R6 version, the Gq interface
controls the QoS resources through interconnection between P-CSCF and PDF.
Instead of the Gq interface, the 3GPP R7 version and later uses the Rx interface to control
the QoS resources. The Rx interface is located between P-CSCF and PCRF.
If Gq/Gq/Rx interface responses time out, the QoS service and the calling service cannot
be carried out, which influences the user's experience.
Probable Causes
l Network communication between P-CSCF and PDF/SPDF/PCRF is disconnected.
l The Gq/Gq'/Rx query policies are configured improperly.
l The DIAMETER route is configured improperly.
l The opposite PDF/SPDF/PCRF are abnormal.
1. Enter the protocol stack mode by running IPSTACK command. Check network status
between PCSCF and PDF/SPDF/PCRF by running PING command, and exit this
mode by running EXIT MODE command.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Check the network cable connection and route configuration, troubleshoot the network,
and check whether the notification is cleared when triggering the Gq/Gq'/Rx interface
query.
l Y->Go to Step 3.
l N->End.
3-47

3. Query the Bearer Policy ID by running SHOW BPLC command and obtain Subnet,
Subnet Mask and Bearer Policy ID which matches P-CSCF address section, select
proper handling steps based on the bearer policy.
l No need to trigger bearing ->Go to Step 4.
l Access Network Category is Radio, Interface Type is Gq, and Bearer Control
Policy ID is not 65535, trigger the Gq interface->Go to Step 5.
l Access Network Category is Fixed, Interface Type is Gq(TISPAN), Access
Network Category is DSL, Bearer Control Policy ID is not 65535, trigger the
Gq’ interface->Go to Step 8.
l Access Network Category is Radio, Interface Type is Rx ->Go to Step 9.,
Bearer Policy ID is not 65535, trigger the Rx interface->Go to Step 9.
4. Modify the Bearer Control Policy ID in step 3 to 65535 by running SET BPLC
command, such as SET BPLC:ID=1,BCPLCID=65535;, and check whether the
l Y->End.
l N->Go to Step 20.
5. Query the Gq bearer policy based on the Bearer Policy ID in step 3 by running SHOW
GQBCPLC command, and check whether there is a Bearer Interface Group ID that
is not 65535.
l Y->Go to Step 6.
l N->Go to Step 20.
6. Based on the Bearer Interface Group ID, query the bearer control interface group by
running SHOW BIFGRP command, and check whether there is a Bearer Interface ID
1 that is not 65535.
l Y->Go to Step 7.
l N->Go to Step 20.
7. Based on the Bearer Interface ID 1, query the bearer control interface configuration by
running SHOW BIF command, and check whether there is non-empty PDF Address.
l Y->Go to Step 10.
l N->Go to Step 20.
8. Based on the Bearer Control Policy ID in step 3, query the Gq' bearer policy
configuration by running SHOW GQTBCPLC command and check whether this
policy is existing.
l Y->Go to Step 11.
l N->Go to Step 20.
9. Based on the Bearer Control Policy ID in step 3, query the Rx bearer policy
configuration by running SHOW RXBCPLC command and check whether there is a
non-empty PCRF Realm.
l Y->Go to Step 10.
l N->Go to Step 20.
10. Check whether corresponding DIAMETER route configuration of the Gq interface is
existing by running SHOW DIM ROUTE command. (Local ProcessId is Relay,
Route ApplicationId is Gq, Dst URI is the PDF address in step 7), and obtain
MasterLinkNo.
l Y->Go to Step 13.
3-48

l N->Go to Step 20.

11. Check whether corresponding DIAMETER route configuration of the Gq' interface is
Route ApplicationId is Gq, Dst URI is RACS), and obtain MasterLinkNo.
l Y->Go to Step 13.
l N->Go to Step 20.
Note:
The E2 and Gq' interfaces are defined in the NASS architecture. You should
obtain the SPDF address for controlling QoS through the E2 interface. P-CSCF
interconnects to CLF through UDR/UDA messages. You should trigger the E2
interface before triggering the Gq' interface, because CLF requires the SPDF
address after replying a UDA message (carries RACS-Contact-Point AVP) to
P-CSCF.
12. Check whether corresponding DIAMETER route configuration of the Gq' interface is
Route ApplicationId is Rx, Dst URI is the PCRF address in step 9), and obtain
MasterLinkNo.
l Y->Go to Step 13.
l N->Go to Step 20.
13. Based on MasterLinkNo, you can check whether the DIAMETER link is configured
properly by running SHOW DIM LINK command. (Local Hostname and Local
Realm are the PCSCF host name and domain name. For a Gq interface, Remote
Hostname and Remote Realm are the PDF host name and domain name; for a Gq'
interface, Remote Hostname and Remote Realm are the SPDF host name and
domain name; for an Rx interface, RemoteHostname and Remote Realm are the
PCRF host name and domain name)
l Y->Go to Step 15.
l N->Go to Step 14.
14. Modify the DIAMETER link configuration by running SET DIM LINK command, and
l Y->End.
l N->Go to Step 15.
15. Select proper handling steps based on Protocol in step 13.
l Protocol is TCP ->Go to Step 16.
l Protocol is SCTP ->Go to Step 18.
16. Based on the ConnectId obtained in step 13, query the TCP bearer configuration by
running SHOW TCPCONN command and check whether local and opposite IP/PORT
are consistent with the CLF link configuration.
l Y->Go to Step 20.
l N->Go to Step 17.
3-49

17. Modify the TCP bearer configuration by running SET TCPCONN command according
to the planning, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 20.
18. Based on the ConnectId obtained in step 13, query the SCTP bearer configuration by
running SHOW DIMSCTP command and check whether local and opposite IP/PORT
l Y->Go to Step 20.
l N->Go to Step 19.
l Y->End.
l N->Go to Step 20.
3.32 ALM-3154509831 E2 Interface Response Timeout

Alarm Description
E2 interface response times out
Alarm Property

As an interface type defined in the NASS architecture, the E2 interface can be used to
query CLF by AF and then obtain location information. (Refer to ETSI ES 283 035). When
the home domain authenticates the users in NBA mode, the users must query location
information through querying CLF on the access PCSCF. E2 interface response timeout
will result in authentication failure on the home domain, and all the services are failed,
which influences user's experience.
Probable Causes
l Network communication between PCSCF and CLF is interrupted.
l The CLF query policy is configured improperly.
l The DIAMETER route is configured improperly.
l The opposite CLF is abnormal.
3-50

1. Enter the protocol stack mode by running IPSTACK command. Check network status
between PCSCF and CLF by running PING command, and exit this mode by running
EXIT MODE command.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Check whether the network cables are inserted into position and the router
configuration is proper. Troubleshoot the network, and check whether the notification
is cleared.
l Y->End.
l N->Go to Step 3.
3. Check whether there is a CLF query policy by running SHOW BPLC command, that is,
Subnet and Subnet Mask match the PCSCF address section configuration, Access Ne
twork Type is DSL, Interface Type is Gq(TISPAN) and CLF Policy Id is a non-65535
value. Obtain corresponding bearer policy ID.
l Y->Go to Step 5.
l N->Go to Step 4.
4. Add a CLF query policy by running ADD BPLC command, and check whether the
l Y->End.
l N->Go to Step 5.
5. Check whether you need to query CLF.
l Y->Go to Step 7.
l N->Go to Step 6.
6. Based on the bearer decision ID obtained in step 3, modify CLF Policy Id to 65535
by running SET BPLC command, such as SET BPLC:ID=1,CLFPLCID=65535;, and
l Y->End.
l N->Go to Step 17.
7. Based on CLF Policy Id obtained in step 3, query the CLF policy by running SHOW
CLFPLC command and obtain CLF Realm->Go to Step 8.
8. Check whether corresponding DIAMETER route configuration of the E2 interface is
Route ApplicationId is E2, Dst URI is CLF domain name), and obtain MasterLinkNo.
l Y->Go to Step 10.
l N->Go to Step 9.
9. Add a DIAMETER route of the E2 interface according to the planning by running ADD
DIM ROUTE command, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 10.
10. Based on MasterLinkNo obtained in step 8, check whether the DIAMETER link is
configured properly by running SHOW DIM LINK command. Correct configuration
should be: Local Hostname is PCSCF NE host name, Local Realm is PCSCF NE
3-51

domain name, Dst Hostname is CLF host name and Dst Realm is CLF domain name.
You obtain LinkNo and Protocol.
l Y->Go to Step 12.
l N->Go to Step 11.
11. Modify the DIAMETER link configuration by running SET DIM LINK command, and
l Y->End.
l N->Go to Step 12.
12. Select proper handling steps based on the Protocol obtained in step 10.
l Protocol is TCP ->Go to Step 13.
l Protocol is SCTP ->Go to Step 15.
13. Based on the ConnectId obtained in step 10, query the TCP bearer configuration by
running SHOW TCPCONN command and check whether local and opposite IP/PORT
l Y->Go to Step 17.
l N->Go to Step 14.
14. Modify the TCP bearer configuration by running SET TCPCONN command according
to the planning, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 17.
15. Based on the ConnectId obtained in step 10, query the SCTP bearer configuration by
running SHOW DIMSCTP command and check whether local and opposite IP/PORT
l Y->Go to Step 17.
l N->Go to Step 16.
l Y->End.
l N->Go to Step 17.
3.33 ALM-3154509832 HSS User Data Exceeds System

Capability
Alarm Description
HSS user data exceeds system capacity
Alarm Property
3-52


If the user subscription data exceeds system capacity, this notification is raised. This failure
could result in registration and call failure, which influences user's experience.
Probable Causes
l When CSCF downloads data from HSS, the character string length is ultra-long in the
user data.
l When CSCF downloads data from HSS, the data exceeds system processing ca-
pacity.
l When CSCF downloads data from HSS, the PUI number in the implicit registration set
or SP exceeds system processing capacity.
l When CSCF downloads data from HSS, the ServiceProfile in the subscription data
exceeds system processing capacity.
l When CSCF downloads data from HSS, the iFC number or shared iFC number in the
subscription data exceeds system processing capacity.
1. Check whether the PUI number in the implicit registration set of user subscription data
configuration exceeds 8.
l Y->Go to Step 2.
l N->Go to Step 3.
2. Reduce the PUI number and check whether the problem persists.
l Y->Go to Step 3.
l N->End.
3. Check whether the Service Profiles number in each IMS Subscription exceeds 8.
l Y->Go to Step 4.
l N->Go to Step 5.
4. Reduce the Service Profiles number in each IMS Subscription and check whether the
problem persists.
l Y->Go to Step 5.
l N->End.
5. Check whether the shared iFC number of each Service Profiles exceeds 8 on HSS.
l Y->Go to Step 6.
l N->Go to Step 7.
6. Reduce the shared iFC number of each Service Profiles, and check whether the
problem persists.
l Y->Go to Step 7.
l N->End.
7. Check whether the shared SIFC and iFC number of each Service Profiles exceeds 32
on HSS.
l Y->Go to Step 8.
l N->End.
8. Reduce the number of Service Profiles iFC, and check whether the problem persists.
l Y->Go to Step 9.
3-53

l N->End.
9. Check whether the user data is ultra long on HSS and the iFC data exceeds 8K.
l Y->Go to Step 10.
l N->Go to Step 11.
10. Reduce overall length or the iFC data length, and check whether the problem persists.
l Y->Go to Step 11.
l N->End.
3.34 ALM-3154509833 Shared iFC Configuration Error

Alarm Description
Shared iFC configuration error
Alarm Property

Because the subscription data are saved on HSS and several users can share an iFC
triggering template, we can configure the same share iFC template on HSS and CSCF to
reduce the downloaded subscription data from HSS. CSCF and HSS interconnect to each
other by transmitting the shared iFC number, which enhances the network performance
especially under mass iFC data situation. This notification indicates that the shared iFC
format/capacity is configured improperly or the shared iFC data on HSS and CSCF are
consistent, which results in service triggering failure.
Probable Causes
l The shared iFC No. downloaded from HSS is not configured on CSCF, and then you
cannot obtain the shared iFC data.
l The SPT template associated with the share iFC does not comply with the protocol
format, which results in iFC format error.
l The share iFC number and the common iFC number share the same priority, which
results in priority conflict.
l The shared iFC configuration items are excessive or iFC content exceeds system
capacity.
1. View the shared iFC set by running SHOW SIFC command and whether it configures
the corresponding local shared iFC data of the shared iFC set ID.
l Y->Go to Step 3.
3-54

l N->Go to Step 2.
2. Add a shared iFC set by running ADD SIFC command, and check whether the problem
persists.
l Y->Go to Step 3.
l N->End.
3. View the shared iFC set by running SHOW SIFC command and query the SPT ID,
proceed to step 4.
4. Based on this SPT ID, query SPT by running SHOW SPT command, and check
whether the iFC content format is correct in this iFC set, and whether data length is
shorter than 1023.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Modify iFC content of SPT by running SET SPT command, and check whether the
problem persists.
l Y->Go to Step 6.
l N->End.
6. View the shared iFC set by running SHOW SIFC command and check whether there
is priority conflict between share iFCs and between the share iFC and common iFC.
l Y->Go to Step 7.
l N->Go to Step 8.
7. Modify priority of the shared iFC set by running SET SIFC command, and check
whether the problem persists.
l Y->Go to Step 8.
l N->End.
8. View the iFC configuration, and check whether the total number of common iFC and
shared iFC exceeds 32.
l Y->Go to Step 9.
l N->Go to Step 10.
9. Reduce the number of shared iFC and common iFC, and check whether the problem
persists.
l Y->Go to Step 10.
l N->End.
3.35 ALM-3154509834 Data Audit Function Found

Exception Data
Alarm Description
Data audit function found exception data.
3-55

Alarm Property

The data audit function can retrieve data when the data is abnormal. Once enabled, this
function will be executed periodically, which impacts system performance. This notification
indicates abnormal data and the system will retrieve data automatically.
Probable Causes
l The data audit is configured to be consistency audit and the user data is inconsistent.
l The data audit is configured to be integrity audit and the user data is incomplete.
No need to handle it, when this notification is reported, the system has already retrieved
the abnormal data.
1. Query the data audit type by running SHOW USERDATAADT command, and select
properly handling steps according to different data audit type.
l Consistency audit ->Go to Step 2.
l Integrity audit ->Go to Step 3.
2. Check whether This record is added or deleted is added in additional alarm
information.
l Y->End.
l N->Go to Step 3.
3. Check the PUI in additional alarm information, re-register the user and check whether
this user is registered successfully.
l Y->End.
l N->Go to Step 4.
3.36 ALM-3154509835 Data Audit Complete

Alarm Description
Data audit is complete
Alarm Property
3-56


The data audit function can retrieve data when the data is abnormal. Once enabled, this
function will be executed periodically. This notification indicates a new audit is complete,
you are suggested to disable this audit function.
Probable Causes
l The data audit is configured to be consistency audit and an audit period ends.
l The data audit is configured to be integrity audit and an audit period ends.
1. Check whether the data audit is required.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify Audit Control Flag to ADTOFF by running SET USERDATAADT command,
and check whether the notification is cleared.
l Y->End.
l N->Go to Step 5.
3. Confirm whether an audit period ends and whether the notification is required.
l Y->End.
l N->Go to Step 4.
4. Modify Audit Control Flag to ADTON_ALMOFF by running SET USERDATAADT
command, and check whether the notification is cleared.
l Y->End.
l N->Go to Step 5.
3.37 ALM-3154509837 Detect Extra-long Call

Alarm Description
Alarm Property

The call is extra-long.
Probable Causes
3-57

l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify Extral-Long Call Detection Durationr(m) by running SET LONGCALLPL
Note:
New setting will be effective in the follow-up calls, and the existing alarm can be
recovered after the user finishes the call.
3. Check whether Extral-Long Call Detection Durationr(m) is too short by running SH

OW LONGCALLPLC command, recommended value is 720 mins.
l Y->Go to Step 4.
l N->Go to Step 5.
4. Modify Extral-Long Call Detection Durationr(m) to a properly value by running SET
LONGCALLPLC command. The recommEnd.ed value is 720 mins, such as SET
LONGCALLPLC:MONITORTIMER=720;.
Note:
New setting will be effective in the follow-up calls, and the existing alarm can be
recovered after the user finishes the call.
5. Contact this user and check whether this user is using this function properly.
l Y->End.
l N->Go to Step 6.
3.38 ALM-3154509838 Release Extra-long Call by Force

Alarm Description
Alarm Property
3-58


No impact on the system.
Probable Causes
1. Confirm with the carrier whether you want the extra-long call detection function.
l Y->Go to Step 3.
l N->Go to Step 2.
2. Modify Extral-Long Call Detection Durationr(m) by running SET LONGCALLPL
Note:
3. Check whether Extra-Long Call Detection Durationr(m) is too short by running SH

OW LONGCALLPLC command, the recommended value is 720 mins.
l Y->Go to Step 4.
l N->Go to Step 5.
4. Modify Extra-Long Call Detection Durationr(m) to a properly value by running SET
LONGCALLPLC command. The recommended value is 720 mins, such as SET LO
NGCALLPLC:MONITORTIMER=720;.
Note:
5. Confirm with the carrier whether you want the call release for the extra-long calls.
l Y->End.
l N->Go to Step 6.
6. Modify the HANDLEPOLICY to Keep Call by running SET LONGCALLPLC
command.
Note:
3-59

3.39 ALM-3154509839 Release Call Because of

Subscriber Is Deleted
Alarm Description
Delete a user to release a call compulsively
Alarm Property

No impact on the system. This notification indicates the call is released because you
have run a command to remove the user on the CSCF NM, or the user is logged out or
de-registered on HSS, or the registration times out. This alarm indicates the call will be
release by force, which impact user’s experience.
Probable Causes
l You have run a command to delete a user on NM.
l You have run a logout or de-registration command on HSS.
l The registration times out, but the user is not re-registered on the terminal.
l Network fault results in re-registration information is lost.
1. Check whether you have run DEL REG command to remove user's registration
information.
l Y->End.
l N->Go to Step 2.
2. Select proper handling steps according to the alarm reasons.
l Registration timer times out, but the user terminal does not sEnd. a new
registration request. -> proceed to 3
l Abnormal device or network fault results in the loss of registration request
message during transmission in the network. -> proceed to 3
l HSS releases a de-registration command -> proceed to 7
3. Check whether other devices like PCSCF and ICSCF are working properly. Enter the
protocol stack mode by running IPSTACK command. Check network status between
CSCF devices by running PING command, and exit this mode by running EXIT MODE
command.
l Y->Go to Step 4.
l N->Go to Step 6.
4. Check whether this notification is reported frequently.
l Y->Go to Step 8.
3-60

l N->Go to Step 5.
5. Check whether some user terminals are faulty.
6. Check whether the network cables are inserted into position and the router
configuration is proper. Troubleshoot the network, and check whether the notification
is cleared.
l Y->End.
l N->Go to Step 8.
7. Contact the administrator to confirm whether HSS delivers a de-registration command.
l Y->End.
l N->Go to Step 6.
3.40 ALM-3154509840 Route Reselection After Failure

Alarm Description
Re-select a route after it fails to work
Alarm Property

SCSCF failure re-selection during registration indicates the home SCSCF is faulty, and
the users will be registered on other SCSCF. SCSCF failure re-selection during calling
indicates the home SCSCF is faulty, and you should enable the SCSCF disaster recovery
flow and complete calls through other SCSCF.
No redundant SCSCF will result in registration and call failure. With a redundant SCSCF,
the system transfers all the registration and call information to this SCSCF, which places
great load on the redundant S-CSCF.
Probable Causes
l Communication between ICSCF and SCSCF is abnormal.
l The SCSCF host returns a failure response.
1. Based on additional notification information, check whether communication between
ICSCF and SCSCF is abnormal or the SCSCF host returns a failure response by SIP
signaling tracing or package capturing tools.
l Abnormal communication ->Go to Step 2.
l Failure response ->Go to Step 8.
3-61

2. Check whether the bearer configuration used in the SIP link configuration is a planned
configuration by running SHOW SIP LINK command.
l Y->Go to Step 4.
l N->Go to Step 3.
3. Modify the SIP link by running SET SIP LINK command, modify the bearer
configuration to plan configuration. Make registration or calls again, and check
whether the notification is cleared.
l Y->Go to Step 4.
l N->End.
4. Check the connection to the opposite End. by the PING command, and exit this mode
by running Exit Mode command.
l Y->Go to Step 6.
l N->Go to Step 5.
5. Troubleshooting the physical connection. Make registration or calls again, and check
whether the notification persists.
l Y->Go to Step 6.
l N->End.
6. Check whether Link Block Status is set to Block in the SIP link configuration by
l Y->Go to Step 7.
l N->Go to Step 9.
7. Modify the SIP link by running SET SIP LINK command, set Link Block status to
Default, and check whether the notification persists.
l Y->Go to Step 9.
l N->End.
8. Check the reason whether SCSCF returns a failure code. Troubleshooting the SCSCF.
Make registration or calls again, and check whether the notification is cleared.
l Y->Go to Step 9.
l N->End.
3.41 ALM-3154509841 Default iFC Configuration Error

Alarm Description
Default iFC configuration error
Alarm Property
3154509841 Notification NE Alarm Processing Error Alarm
3-62


The default iFC data is configured on the CSCF. By associating default iFCs to the
default iFC set, users can read out the data in the default iFC set in accordance with the
configuration. If the Default iFC configuration error notification is raised, it indicates that
an error occurs to default iFC format or capacity configured in the system, which may
lead to a failure in triggering a service.
Probable Causes
l The SPT template associated with the default iFC does not comply with the protocol
format, which results in iFC format error.
l The different default iFC number share the same priority, which results in priority
conflict.
l The Default iFC configuration items are excessive or iFC content exceeds system
capacity.
l The number of default iFC exceeds system capacity.
1. View the Default iFC set by SHOW DEFIFCPLC, and check whether the total number
of Default iFC exceeds 4.
l Y->Go to Step 2
l N->Go to Step 3
2. Reduce the number of default iFC, and check whether the problem persists.
l Y->Go to Step 3
l No->End
3. View the default iFC set by SHOW DEFIFCPLC and query the default iFC ID, proceed
to step 4.
4. Based on this default iFC ID, view the Default iFC by SHOW DEFIFC, proceed to step
5.
5. Based on this SPT ID, query SPT by SHOW SPT, and check whether the iFC content
format is correct in this iFC set, and whether data length is shorter than 1024.
l Y->Go to Step 7
l N->Go to Step 6
6. Modify iFC content of SPT by SET SPT, and check whether the problem persists.
l Y->Go to Step 7
l No->End
7. Check the iFC, whether RequestURI SPT length is shorter than 256.
l Y->Go to Step 9
l N->Go to Step 8
l Y->Go to Step 9
l No->End
9. Check the iFC, whether Method SPT length is shorter than 64.
l Y->Go to Step 11
l N->Go to Step 10
3-63

l Y->Go to Step 11
l No->End
11. Check the iFC, whether Header (of SIPHeader SPT) length is shorter than 64 and
Content (of SIPHeader SPT) length is shorter than 128.
l Y->Go to Step 13
l N->Go to Step 12
l Y->Go to Step 13
l No->End
13. Check the iFC, whether the value of SessionCase SPT is smaller than 5.
l Y->Go to Step 15
l N->Go to Step 14
l Y->Go to Step 15
l No->End
15. Check the iFC , whether Line of SessionDescription SPT is shorter than 64 and Content
of SessionDescription SPT is shorter than 128.
l Y->Go to Step 17
l N->Go to Step 16
l Y->Go to Step 17
l No->End
17. View the Default iFC set by SHOW DEFIFCPLC and check whether there is priority
conflict between Default iFCs.
l Y->Go to Step 18
l N->Go to Step 19
18. Modify priority of the Default iFC set by SET DEFIFC, and check whether the problem
persists.
l Y->Go to Step 19
l No->End
3.42 ALM-3154513938 Adjacent Host Has Been Set

Block
Alarm Description
An adjacent host is manually set blocked in the network management system.
3-64

Alarm Properties
3154513938 Notification NE alarm Processing error

alarm

The adjacent host is manually set blocked, which is unavailable, resulting in the registration
flow or call flow unreachable.
Probable Causes
An adjacent host is manually blocked.
1. Run the SHOW ADJHOST MML command (if the adjacent host is dynamic, run the
SHOW DYADJHOSTINFO command) to query the adjacent host. In accordance with
the host name contained in the additional information of the notification, obtain the
adjacent host ID. Check whether Forced Blocking is configured to Yes.
l No->Go to Step 4.
2. Determine whether the adjacent host needs to be unblocked.
l Yes->Go to Step 3
l No->Go to Step 4
3. Run the SET ADJHOST MML command (if the adjacent host is dynamic, run the SET
DYADJHOSTINFO command) to modify Forced Blocking to No. The adjacent host
is unblocked. Check whether the alarm still exists.
l No->End.
3.43 ALM-3154513939 Adjacent Host Has Been Set

Unblock
Alarm Description
An adjacent host is manually set unblocked in the NM system.
Alarm Properties
Alarm code Alarm Level System Type Alarm Type

alarm
3-65


The adjacent host is manually set unblocked. The host may be available.
Probable Causes
The adjacent host is manually set unblocked.
1. Run the SHOW ADJHOST MML command (if the adjacent host is dynamic, run the
SHOW DYADJHOSTINFO command) to query the adjacent host. In accordance with
the host name contained in the additional information of the notification, obtain the
adjacent host ID. Check whether Forced Blocking is configured to No.
l Yes->End
l No->Go to Step 2.
3.44 ALM-3154513942 Host Group Switches from

Redundant Status to Abnormal Status
Alarm Description
An adjacent host is manually set blocked in the NM system.
Alarm Properties

alarm

The host group switches from the redundant status to the abnormal status. Part of or the
entire traffic is probably interrupted.
Probable Causes
The host group switches from the redundant status to the abnormal status.
1. Run the SHOW STATICDR INFO MML command (if the disaster tolerance host
group is dynamic, run the SHOW DYNAMICDR INFO command). Check whether
the disaster tolerance host group is set as Abnormal Status.
l Yes->Go to Step 2
l No->Go to Step 3
2. Locate the cause for host group faults. Check whether the host for routing is faulty.
3-66

l Yes->Locate the cause for host faults. Troubleshoot faults with reference to
ALM-3154513940 Adjacent Host is abnormal.
l No->Go to Step 3.
3.45 ALM-3154513943 Host Group Switches from

Abnormal Status to Redundant Status
Alarm Description
The host group switches from the abnormal status to the redundant status.
Alarm Properties

alarm

The host group switches from the abnormal status to the redundant status. The traffic is
not affected.
Probable Causes
The host group switches from the abnormal status to the redundant status.
1. Run the SHOW STATICDR INFO MML command (if the disaster tolerance host
group is dynamic, run the SHOW DYNAMICDR INFO command). Check whether
the disaster tolerance host group is set as Redundant Status.
l No->Go to Step 3.
2. Locate the cause for host group switching to the redundant status. Check whether the
host for routing is the desired host for initial configuration and the status of the host is
normal.
l Yes->Troubleshoot the desired host that is initially configured with reference to
ALM-3154513940 Adjacent Host is abnormal.
l No->Go to Step 3.
3-67

3.46 ALM-3154513944 Attribute of Host Group Changed

Alarm Description
Attribute of host group changed.
Alarm Property

alarm

The component attributes of the host group are changed, which causes that the host group
enters normal status from abnormal status.
Probable Causes
l The disaster redundancy policy of the host group has changed.
l The priority or weight of the host in the host group has changed.
l Some hosts have been added into or deleted from the host group.
1. Check if the redundant host group is in normal status according to MML SHOW STA
TICDR INFO or SHOW DYNAMICDR INFO.
l Y->End.
l N->Go to Step 2.
3.47 ALM-3154513945 Routing Status of Host Changed

Alarm Description
Routing status of host changed
Alarm Property

alarm

The routing status of the host is changed (from routing to nonrouting, or from nonrouting to
routing), which may cause that different hosts are selected for registerations or sessions.
3-68

Probable Causes
l The physical status of the host has changed.
l The manual status of the host has changed.
l The changeover mode or changeback mode of the host group which the host be-
longed to has changed.
1. Check if the routing status of the host is corresponding to the NOTICE information
according to MML SHOW STATICDR INFO or SHOW DYNAMICDR INFO.
l Y->End.
l N->Go to Step 2.
3.48 ALM-3154534657 Charging Module Fails to Obtain

Configuration
Alarm Description
The charging module fails to obtain configuration
Alarm Property

Failed to perform offline charging, which results in commercial loss.
Probable Causes
l Local NE host name is not configured, which results in the charging module fails to
obtain the local NE host name.
l Local NE domain name is not configured, which results in the charging module fails
to obtain the local NE domain name.
l The offline charging policy is not configured, which results in the charging module fails
to obtain the offline charging policy.
1. Select proper handling steps based on exception configuration information in
additional information.
l Failed to read the host name ->Go to Step 2.
l Failed to read local domain name ->Go to Step 4.
l Failed to read the charging policy ->Go to Step 6.
3-69

2. View host configuration by running SHOW HOST command and check whether you
have configured the host name correctly.
l Y->Go to Step 8.
l N->Go to Step 3.
3. Add or modify the host configuration by running ADD HOST command or SET HOST
command.
l Y->End.
l N->Go to Step 8.
4. View domain configuration by running SHOW DOMAIN command and check whether
you have configured the domain.
l Y->Go to Step 8.
l N->Go to Step 5.
5. Add a domain by running ADD DOMAIN command.
l Y->End.
l N->Go to Step 6.
6. View the charging policy configuration by running SHOW ACCTPLC command and
check whether you have configured the offline charging policy.
l Y->Go to Step 8.
l N->Go to Step 7.
7. Add a charging policy by running ADD ACCTPLC command according to the planning.
l Y->End.
l N->Go to Step 8.
3-70

Glossary
AAS
- Adapt Antenna System
ACA
- Accounting Answer
ACR
- Accounting Requests
AS
- Application Server
CCF
- Charging Collection Function
CG
- Charging Gateway
CPU
- Central Processing Unit
CSCF
- Call Session Control Function
DEP
- Diameter Execute Point
DNS
- Domain Name Server
DNS
- Domain Name System
DOS
- Disk Operating System
HSS
- Home Subscriber Server
ID
- Identification
IMS
- IP Multimedia Subsystem
IP
- Internet Protocol
MML
- Man Machine Language

NE
- Network Element
NM
- Network Management
OMP
- Operation & Maintenance Processor
P-CSCF
- Proxy-Call Session Control Function
PCRF
- Policy and Charging Rules Function
PUI
- Public User Identity
PVI
- Private User Identity
QoS
- Quality of Service
SCTP
- Stream Control Transmission Protocol
SIP
- Session Initiation Protocol
TCP
- Transmission Control Protocol
UDP
- User Datagram Protocol
II

SJ-20140122171518-015-ZXUN CSCF (V4.13.10) Call Session Control Function Alarm Handling

Загружено:

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

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

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

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

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

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

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

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

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

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

SJ-20140122171518-015-ZXUN CSCF (V4.13.10) Call Session Control Function Alarm Handling

Загружено:

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

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

ZXUN CSCF

Call Session Control Function

Revision No. Revision Date Revision Reason

R1.0 2014-02-25 First Edtion

Serial Number: SJ-20140122171518-015

Publishing Date: 2014-02-25 (R1.0)

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

Chapter 2 Alarm Message Handling ......................................................... 2-1

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

Chapter 3 Notification Message Handling................................................ 3-1

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 3, Notification Message Describes the notification in details, including causes,

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

| Separates individual parameters in a series of parameters.

Danger: indicates an imminently hazardous situation. Failure to comply can result in

Warning: indicates a potentially hazardous situation. Failure to comply can result in

Caution: indicates a potentially hazardous situation. Failure to comply can result in

Note: provides additional information about a topic.

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

1.1 Alarm Information

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

A critical alarm causes system breakdown and service interruption. It requires

A major alarm significantly affects system operation or weakens network service

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

1.2 Probable Cause

1.3 Impact on the System

1.4 Troubleshooting Suggestion

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

25866 Smoke alarm .................................................................................................2-59

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

2365980936 Interface Inner Control Account Password Do Not Meet

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

ALM-3154247681 Failed to Launch the System .....................................................2-188

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

ALM-3162132483 Anti-DOS Attack User Capacity Level-1.....................................2-251

2.1 170 The switch board occurred loopback port

Port ID Number of the physical interface that causes the

Port type Indicates whether the interface that causes the

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

2.2 256 OMC port's link is down

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

l Auto Clear: Yes

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

2.3 2560 CPU utilization over alarm limit

CPU usage Indicates the CPU utilization (percentage).

CPU high threshold High-level overload threshold of the CPU.

CPU low threshold Low-level overload threshold of the CPU.

Process first Name of the process whose CPU occupation rate

Process second Name of the process whose CPU occupation rate

Process third Name of the process whose CPU occupation rate

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

2.4 3584 Memory insufficient alarm

SJ-20140122171518-015|2014-02-25 (R1.0) ZTE Proprietary and Confidential

2.5 5122 Loss of Active/standby communication link