ZXSS10 SS1b

SoftSwitch Control Equipment

Alarm And Notification
Handling Manual---Notification

Version V2.0.1.06.1

ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2009-9-20 First Edition

Serial Number: sjzl20092692

Contents

About This Manual.............................................. i

Safety Instructions............................................1
Overview....................................................................... 1
Safety Statement ........................................................... 1
Safety Signs .................................................................. 4
Alarm and Notification Overview .......................7
Overview....................................................................... 7
Classification by Maintenance Contents.............................. 7
General Meaning of Alarm and Notification ......................... 8
Cause of Alarm and Notification ........................................ 9
Handling Method of Alarm and Notification ........................10
Notification Information and Relevant
Handling.......................................................... 13
Overview......................................................................13
Notification Information Processing ..................................13
Failed to Select Trunk(1).............................................13
Emergency Call Service Notification(4) .........................14
Immediate Malicious Call(5) ........................................14
Continuity Successful(6) .............................................14
Continuity Failure: Looping Failed(7) ............................15
Continuity Failure: Mg Returning Result Failed(8) ...........15
Continuity Failure: Waiting for The Answer of Continuity
Request Times Out(9) ........................................16
Continuity Failure: Waiting for Continuity Result Times
Out(10)............................................................16
Continuity Failure: Playing Continuity Test Tune
Failed(11).........................................................17
Continuity Failure: SS7 Release Message Is
Received(12) ....................................................17
Long Call Alarm(13) ...................................................17
Ringing Didn”T Answer(16) .........................................18
Instant Malicious Call Alarm(17) ..................................18
Number of Pulses Exceeds Threshold(18)......................19
Recover SPC Board Based on The Configuration in
Fail-Manager Options(19) ...................................19
Reset SPC Board Based on The Configuration in
Fail-Manager Options(20) ...................................19
All The DR SPC Protocol Process Is Normal(23) ..............20
The Alarm Business Overtime(24)................................20
Alarm for Immediate Malicious Call(25) ........................20
High Level Call Gapping Alarm(512) .............................21
Low Level Call Gapping Alarm(513)..............................21
High Level Call Gapping Detail Alarm(514) ....................22
Low Level Call Gapping Detail Alarm(515).....................22
Interaction with SHLR Times Out(4102)........................22
Register Message Expire(4103) ...................................23
AG112 Incremental Backup Alarm(5662) ......................23
AG112 Full Backup Alarm(5663) ..................................24
Userline Already Exist in SS(5668) ...............................24
Uncorrect Data Length in SHLR(5669) ..........................24
Ctx Not Exist in SS(5670) ...........................................25
Mls Not Exist in SS(5671) ...........................................25
ISDN User Not Exist in SS(5672) .................................25
Userline Not Exist in SS(5673) ....................................26
Zone Or Node Or Card Not Exist in SS(5674).................26
Database Error When Modify Data in SS(5675) ..............26
Node Autoselect Error in SS(5676)...............................27
Tollnum Not Match(5677) ...........................................27
Inadequate Capacity of Node/ Zone Configuration of
SS(5680) .........................................................27
Oracle Error(5681) ....................................................28
Write Drsrc Failer(5682) .............................................28
The Field Number of Table in Dict Has Overed
Length(5888)....................................................28
The Length of Field”S Name Has Overed
Length(5889)....................................................29
Executing Sql Statement Failed(6402) ..........................29
Synchronous Transfer Failure(6403) .............................29
Inserting Data Table Failure At Startup(6914) ................30
It Is Found At Startup That The Data Table Field Is
Lost(6916) .......................................................30
Traffic Dredge Through Route Link(7335) ......................31
Subscriber Port Is Manually Unblocked(7392) ................31
Trunk Circuit Group Is Manually Blocked(7393)..............32
All Circuits in The Trunk Group Are Busy(7394)..............32
Disaster Recovery Gateway Registration(7400) ..............32
Disaster Recovery Gateway Quits Registra-
tion(7401) ........................................................33
Voice Resource of The Gateway Exceeds Level-1
Threshold(7501)................................................33
Voice Resource of The Gateway Exceeds Level-2
Threshold(7502)................................................34
Voice Resource of The Gateway Exceeds Level-3
Threshold(7503)................................................34
Voice Resource of The Gateway Exceeds Level-4
Threshold(7504)................................................34
Voice Resource of The Gateway Exceeds Level-5
Threshold(7505)................................................35
Voice Resource of The Gateway Exceeds Level-6
Threshold(7506)................................................35
Conference Resource of The Gateway Exceeds Level-1
Threshold(7507)................................................36
Conference Resource of The Gateway Exceeds Level-2
Threshold(7508)................................................36
Conference Resource of The Gateway Exceeds Level-3
Threshold(7509)................................................37
Conference Resource of The Gateway Exceeds Level-4
Threshold(7510)................................................37
Conference Resource of The Gateway Exceeds Level-5
Threshold(7511)................................................38
Conference Resource of The Gateway Exceeds Level-6
Threshold(7512)................................................38
Vtca Resource of The Gateway Exceeds Level-1
Threshold(7513)................................................39
Vtca Resource of The Gateway Exceeds Level-2
Threshold(7514)................................................39
Vtca Resource of The Gateway Exceeds Level-3
Threshold(7515)................................................39
Vtca Resource of The Gateway Exceeds Level-4
Threshold(7516)................................................40
Vtca Resource of The Gateway Exceeds Level-5
Threshold(7517)................................................40
Vtca Resource of The Gateway Exceeds Level-6
Threshold(7518)................................................41
Tln Resource of The Gateway Exceeds Level-1
Threshold(7519)................................................41
Tln Resource of The Gateway Exceeds Level-2
Threshold(7520)................................................42
Tln Resource of The Gateway Exceeds Level-3
Threshold(7521)................................................42
Tln Resource of The Gateway Exceeds Level-4
Threshold(7522)................................................42
Tln Resource of The Gateway Exceeds Level-5
Threshold(7523)................................................43
Tln Resource of The Gateway Exceeds Level-6
Threshold(7524)................................................43
CPU Utilization of Gateway MP Board Exceeds Level-1
Threshold(7525)................................................44
CPU Utilization of Gateway MP Board Exceeds Level-2
Threshold(7526)................................................44
CPU Utilization of Gateway MP Board Exceeds Level-3
Threshold(7527)................................................45
CPU Utilization of Gateway MP Board Exceeds Level-4
Threshold(7528)................................................45
CPU Utilization of Gateway MP Board Exceeds Level-5
Threshold(7529)................................................45
CPU Utilization of Gateway MP Board Exceeds Level-6
Threshold(7530)................................................46
CPU Utilization of Gateway PP Board Exceeds Level-1
Threshold(7531)................................................46
CPU Utilization of Gateway PP Board Exceeds Level-2
Threshold(7532)................................................47
CPU Utilization of Gateway PP Board Exceeds Level-3
Threshold(7533)................................................47
CPU Utilization of Gateway PP Board Exceeds Level-4
Threshold(7534)................................................47
CPU Utilization of Gateway PP Board Exceeds Level-5
Threshold(7535)................................................48
CPU Utilization of Gateway PP Board Exceeds Level-6
Threshold(7536)................................................48
Traffic of Gateway IPI Network Interface Exceeds
Level-1 Threshold(7537) ....................................49
Traffic of Gateway IPI Network Interface Exceeds
Level-2 Threshold(7538) ....................................49
Traffic of Gateway IPI Network Interface Exceeds
Level-3 Threshold(7539) ....................................50
Traffic of Gateway IPI Network Interface Exceeds
Level-4 Threshold(7540) ....................................50
Traffic of Gateway IPI Network Interface Exceeds
Level-5 Threshold(7541) ....................................50
Traffic of Gateway IPI Network Interface Exceeds
Level-6 Threshold(7542) ....................................51
Packet Loss Ratio of Gateway IPI Network Interface
Exceeds Level-1 Threshold(7543) ........................51
Packet Loss Ratio of Gateway IPI Network Interface
Exceeds Level-2 Threshold(7544) ........................52
Packet Loss Ratio of Gateway IPI Network Interface
Exceeds Level-3 Threshold(7545) ........................52
Packet Loss Ratio of Gateway IPI Network Interface
Exceeds Level-4 Threshold(7546) ........................53
Packet Loss Ratio of Gateway IPI Network Interface
Exceeds Level-5 Threshold(7547) ........................53
Packet Loss Ratio of Gateway IPI Network Interface
Exceeds Level-6 Threshold(7548) ........................54
Synchronization-To-Desynchronization Conversion
Failure(7549) ....................................................54
Obtaining The Logic Board Number of Synchronization
Record Failed(7550)...........................................54
MMLReturns Data Area Index Error(7551).....................55
This Record Does Not Need to Be Synchronized
Because The Board Is Offline(7552) .....................55
Handle of The Synchronous Module Database Becomes
Invalid(7553) ....................................................56
MMLError Message Is Received by Synchronous
Module(7554) ...................................................56
Foreground MMLModule Times Out(7555) .....................57
FTP Operation Failure(7556) .......................................57
Unauthorized User Tttempts to Log in to The
System(8448) ...................................................57
Log Alarm([Alarm Code])............................................58
Log Database Connection Alarm(8705) .........................58
Usage of Trunk Group Crosses Upper Thresh-
old(8971) .........................................................59
Usage of Trunk Group Crosses Lower Thresh-
old(8972) .........................................................59
Average Seizure Time of Trunk Group Crosses Upper
Threshold(8973)................................................59
Average Seizure Time of Trunk Group Crosses Lower
Threshold(8974)................................................60
Average Answer Time of Trunk Group Crosses Upper
Threshold(8975)................................................60
Average Answer Time of Trunk Group Crosses Lower
Threshold(8976)................................................61
Answer/Seizure Ratio of Trunk Group Crosses Lower
Threshold(8977)................................................61
Answer/Call Attempt Ratio of Trunk Group Crosses
Lower Threshold(8978) ......................................62
Call Attempts of One Circuit of Trunk Group Crosses
Upper Threshold(8979) ......................................62
Seizure Time of One Circuit of Trunk Group Crosses
Upper Threshold(8980) ......................................63
Voice Quality of The Gateway Exceeds The
Threshold(8981)................................................63
Length of Call Info Message Is Wrong(9013) .................63
Circuit Board State Change Notification(9217) ...............64
Unreasonable Board/Shelf Number Received by The
Alarm Module(9218) ..........................................64
Recover SPC Board Based on The Configuration in
Alarm-Manager Options(9219) ............................65
Reset SPC Board Based on The Configuration in
Alarm-Manager Options(9220) ............................65
Notification Database Record Overflow(9456) ................65
History Alarm Database Record Overflow(9457).............66
Server Reboot Notification(9458) .................................66
Clearing All The Signaling Tracing Tasks Due to
Overhigh CPU Utilization(9459) ...........................67
SC Startup Succeeds(9470) ........................................67
Disaster Recovery Tcp Link Re-Building(12846)..............67
HLR Inserting User Data Is Invalid(12847) ....................68
Configured User Data Space Is Insufficient(12848) .........68
Map Version Supported by SHLR Is Earlier Than That of
SS(12856)........................................................69
Capacity Overflow After Mapping Disaster Recovery
Node(12857) ....................................................69
Uni-User Meter Is Reset(13200) ..................................69
Billing Server Windows Login Notification(13338)...........70
Billing Server System User Login Notifica-
tion(13339) ......................................................70
Billing Server Starting Service Notification(13340) .........71
Billing Server Windows Port Filtering Notifica-
tion(13341) ......................................................71
Billing Server System Log Notification(13342) ...............71
Billing Server Background Login User Notifica-
tion(13343) ......................................................72
Billing Server Network Traffic Alarm(13344) ..................72
Billing Server Network Filtering Alarm(13345) ...............73
Billing Server Exceptional Alarm Notifica-
tion(13348) ......................................................73
There Are Same Name Files on The Billing
Server(13353) ..................................................73
Task Message Processing Exception(16385)...................74
Active/Standby Boards Switchover(16647)....................74
Board Startup Notification(16648) ...............................75
Board Holder Status Notification(16649) .......................75
System Clock Is Being Changed on Pur-
pose(16708) .....................................................75
Board Reset Notification(16709) ..................................76
Traffic of The Equipment Exceeds The System
Configuration(16710) .........................................76
Address Clash(16780) ................................................76
Ping Gateway of Nic Does Not Work(16799) ..................77
H248 Inter-Process Communication Recov-
ery(20491) .......................................................77
H248 Inter-Process Communication Fail-
ure(20492) .......................................................78
Ph248 Transaction Re-Transfer Times Out
And No Answer Is Received From The
Gateway(20495) ...............................................78
Power-on Registration Message of The Gateway Is
Received(20501) ...............................................79
SS Block The Trunk Circuit Because Mg Return 431
Error Code(20515).............................................79
Ph248 Transaction Request Over Time,Iad No
Reply.(20518) ...................................................79
Ph248 Received Srvchg From Iad Belonged Other
SS(20519)........................................................80
Mrs Disaster Recovery Registration(20741) ...................80
UDP Socket Creation Error(20993) ...............................80
UDP Socket Binding Error(20994) ................................81
UDP Socket Is Normal(20995) .....................................81
IP Socket Creation Error(20996)..................................82
IP Socket Binding Error(20997) ...................................82
IP Socket Is Normal(20998)........................................83
CIC Number Does Not Exist(21249) .............................83
Office Direction Number Does Not Exist(21250) .............84
Message Discarding(21251) ........................................84
Connection Errors Reach The Threshold(21259) .............84
Deletion Operation Is Executed in Data-
base(21281) .....................................................85
Invoking Data Interface Failure At SIP Module
Startup(21515) .................................................85
SIP Register Dispatch Fail(21516) ................................86
SIP Register Adduser Fail(21517).................................86
SIP Register Deluser Fail(21518) .................................86
Illegal SDP Alarm(21519) ...........................................87
SS7: Waiting for Block-Acknowledgment Times
Out(21840) ......................................................87
SS7: Waiting for Unblock-Acknowledgment Times
Out(21841) ......................................................87
SS7: Signaling Block Due to Waiting for
Reset-Acknowledgment Times Out(21842) ............88
SS7: SC Data Area Allocation Failure(21843) ................88
SS7: Waiting for Gra Times Out(21844) .......................89
SS7 : Waiting for Cgba Times Out(21845) ....................89
SS7:Waiting for Cgua Times Out(21846) ......................89
SS7: Cg Data Area Allocation Failure(21847) ................90
SS7:Call Data Area Allocation Failure(21848) ................90
SS7up Unexpected Message(21849) ............................91
SS7: Reachable Indication of The Signaling Point of
The Data Is Received(21850) ..............................91
Unreachable Indication of The Signaling Point of The
Data Is Received(21853) ....................................92
A Certain Circuit Operation in The Trunk Group Times
Out(21854) ......................................................92
Subsystem Congestion(22274) ....................................93
Subsystem Failure(22275) ..........................................93
Route Hop(22280) .....................................................93
Unknown Route(22281)..............................................94
Reassembling Timeout(22282) ....................................94
Reassembling Sequence Error(22283) ..........................95
No Space for Reassembling(22284)..............................95
Riar Timeout(22285)..................................................95
Connection Reset(22286) ...........................................96
Message Oversize(22287)...........................................96
Connection-Oriented Resource Is Not Released
Completely(22288) ............................................97
Section Division Unsupported(22289)...........................97
Section Division Failure(22290) ...................................97
Reassembling Failure(22291) ......................................98
SCCP Startup on Busy(22293).....................................98
SCCP Startup Congestion(22294) ................................98
SCCP Stop([Alarm Code]) ...........................................99
System Error Supported(22296) ..................................99
Service Syntax Error(22299).......................................99
M3UA Syntax Error(22300) ....................................... 100
Message Decode Error(22301) .................................. 100
Subsystem Prohibition Started(22302) ....................... 100
Subsystem Prohibited Finished(22303) ....................... 101
Prohibition Message of The Subsystem Is
Received(22304) ............................................. 101
Subsystem Congestion(22305) .................................. 101
Subsystem Rejection(22306) .................................... 102
Grant Message Is Received(22307) ............................ 102
Permission Message of The Subsystem Is
Received(22308) ............................................. 102
Utilization of Connecting Data Resources Exceeds
80%(22309) ................................................... 103
Utilization of Connecting Data Resources Exceeds
96%(22310) ................................................... 103
 Utilization of XUDTS Data Resources Exceeds
80%(22311) ................................................... 104
Utilization of XUDTS Data Resources Exceeds
96%(22312) ................................................... 104
Utilization of XUDT Data Resources Exceeds
96%(22313) ................................................... 105
Utilization of XUDT Data Resources Exceeds
80%(22314) ................................................... 105
Utilization of Connection Resources Exceeds
96%(22315) ................................................... 106
Utilization of Connection Resources Exceeds
80%(22316) ................................................... 106
Registering to GK Failed(22790) ................................ 106
Registering to GK Succeeded(22791) ......................... 107
Unregistered User(22792) ........................................ 107
Broadband Resources Are Exhausted(22793) .............. 107
Call Channel Resources Are Exhausted(22794) ............ 108
Device Resources Are Exhausted in Local
Zone(22795)................................................... 108
Device Resources Are Exhausted in Adjacent
Zone(22796)................................................... 108
Access Table Resources Are Exhausted(22797) ............ 109
Service Resources Are Exhausted in Local
Zone(22798)................................................... 109
Service Resources Are Exhausted in Adjacent
Zone(22799)................................................... 110
Failed to Add Dynamic Configuration Data(22800) ......... 110
Failed to Delete Dynamic Configuration
Data(22801) ................................................... 110
Failed to Modify Dynamic Configuration
Data(22802) ................................................... 111
Tables ........................................................... 113
 About This Manual

Purpose ZXSS10 SS1b SoftSwitch Control Equipment Alarm & Notification

Handling Manual describes how to handle notifications and alarms
of the ZXSS10 SS1b SoftSwitch control equipment (hereinafter
referred to as the ZXSS10 SS1b). In more details, the manual de-
scribes the causes and handling methods of various notifications
and alarms, which help the troubleshooting of the SoftSwitch of-
fice.
Intended This manual is intended for all the operation and maintenance per-
Audience sonnel and persons on duty in the equipment room who have basic
technical knowledge. It is also intended as a reference for all per-
sons involved in the maintenance process.
Prerequisite Skill To use this manual effectively, users should have a general under-
and Knowledge standing of softswitch technology.
� ZXSS10 SS1b system and its various components
� User interfaces of ZXSS10 SS1b
� Local operating procedures of ZXSS10 SS1b
What Is in This This manual contains the following chapters:
Manual
TABLE 1 CHAPTER SUMMARY

Chapter Summary

Chapter This chapter deals with the operation safety

1 Safety instructions and the description of some related signs
Instructions of the ZXSS10 SS1b.

Chapter 2
This chapter describes the classification of the ZXSS10
Alarm and
SS1b equipment maintenance, the general meaning,
Notification
cause, and handling method of notification and alarm.
Overview

Chapter 3 This chapter summarizes notifications of the ZXSS10

Notification SS1b and describes the meaning, cause, related
Information information, handling method, and precautions of
and Relevant each notification.
Handling

Confidential and Proprietary Information of ZTE CORPORATION i

 ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Related The following documentation is related to this manual:

Documentation
� ZXSS10 SS1b Softswitch Control Equipment Alarm And Notifi-
cation Handling Manual---Critical Alarm
� ZXSS10 SS1b Softswitch Control Equipment Alarm And Notifi-
cation Handling Manual---Major Alarm
� ZXSS10 SS1b Softswitch Control Equipment Alarm And Notifi-
cation Handling Manual---Minor Alarm
� ZXSS10 SS1b Softswitch Control Equipment Alarm And Notifi-
cation Handling Manual---Warining Alarm
� ZXSS10 SS1b Softswitch Control Equipment Alarm And Notifi-
cation Handling Manual---Notification
� ZXSS10 SS1b Softswitch Control Equipment Maintenance
Guide---Routine Maintainence
� ZXSS10 SS1b Softswitch Control Equipment Maintenance
Guide---Troubleshooting

ii Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 1

Safety Instructions

Table of Contents
Overview........................................................................... 1
Safety Statement ............................................................... 1
Safety Signs ...................................................................... 4

Overview
Introduction This chapter deals with the operation safety instructions and the
description of some related signs of the ZXSS10 SS1b. Please
read the contents below carefully before conducting operation &
maintenance to the device.

Safety Statement
Description Some operations to the ZXSS10 SS1b media gateway are con-
ducted in a dangerous indoor working environment such as high
temperature and high voltage, so it is required to comply with all
the safety regulations throughout the process. Only well-trained
and fully-qualified professional personnel are allowed to conduct
relevant operation and maintenance.
Please observe the local safety regulations and relevant operation
procedures during the operation and maintenance of the ZXSS10
SS1b media gateway so as to avoid personal injuries or damage
to the device. ZTE Corporation assumes no responsibilities for
any consequences resulting from violation of the general safety
operation requirements or of the safety standards for the design,
production and use of the device.
Safety precautions The safety precautions given below are only supplementary to the
local safety regulations.
1. Electric shock

Power cables and electric facilities usually suggest the most

common dangers.

Confidential and Proprietary Information of ZTE CORPORATION 1

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

During operations to the hardware, make sure to wear the

rubber-soled shoes and remove all the metal jewels and orna-
ments. Do not expose yourself to electric shocks on purpose or
put your hands on the terminal to check if it is fed with power.
2. Lightning stroke

Do not assume the lightning protection system runs in a

reliable state all the time, especially during reconstruction of
buildings, because the lightning protection system may be
damaged or not finished yet.
In case of thunder storms, guard against the danger of light-
ning stroke while working on the indoor cables connected with
outdoor ones.
3. Raised floor

Raised floor usually is part of the HVAC (heating, ventilation

and air-conditioning) distribution system. When the floor is
removed, dust and dirt will fly at the working personnel due
to release from stress. So it is necessary to put on protective
glasses or even filter masks.
The base of the floor is often made of metal. If floors are not
connected with the stringer, all the floors in a row cannot be
removed at a time. Make necessary marks before removing
the floors, including the installation positions and directions
for convenient restoration.
4. Aerial path

Avoid climbing or walking on the beam or the bracket. When

working on the aerial path, make sure to wear a safety protec-
tion device.
Do not throw anything from above. If user cannot reach things
with your hands, use a fishing line or a bag to transfer articles
downward or vice versa.
5. Crawl space

Telecom cables are usually distributed on the ceiling or under

the raised floor; these places are generally called the crawl
space.

2 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 1 Safety Instructions

When entering the crawl channel, wear a hard helmet to pro-

tect head from being hurt by stiff and sharp articles. Ensure
ample lighting; use flashlights or other lamps for lighting when
necessary.
If dust, fiber-like insulation materials or other materials that
may lead to respiration problems exist in the crawl space, make
sure to wear a filter mask.
While moving in the crawl space, walk or crawl on the special
surface or bracket designed for walking or crawling.
Do not throw anything from the ceiling while working on it. If
user cannot reach things with your hands, use a fishing line or
a bag to transfer articles downward or vice versa. Never place
anything on the ceiling.
6. Optical fiber

Do not peep at the end of the optical fiber, as the rays trans-
mitted by most optical fibers are invisible.
Bare optical fibers can pierce the skin.
Waste fiber scraps may enter in to eyes. When optical fibers
are twisted, jumping or falling down, the bare fibers may injure
the eyes.
7. ESD prevention

Electrostatic discharge occurs when our body moves or rubs

with clothes or when we move in chairs or walk on the floor.
ESD can affect the operation of the device or even damage
relevant components.
It is required to wear ESD-preventive wrist straps during the
maintenance work, including plugging/unplugging a board,
holding a board in hands and any body contact. The ESD-pre-
ventive wrist strap must be connected to the ESD-preventive
wrist strap jack on the rack.

Confidential and Proprietary Information of ZTE CORPORATION 3

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Safety Signs
Safety signs The safety signs used in this manual are shown in Table 2. These
signs are indications of the safety precautions to be observed in
device installation, operation and maintenance.

TABLE 2 SAFETY SIGNS AND THEIR MEANINGS

Safety
Sign Meaning

Be aware of safety

Caution against static electricity

Caution against electricity

Caution against laser

Caution against microwave

Safety indications Safety indications involve four levels: danger, warning, caution,
alert. The statement for each safety level is on the right of the
sign; while a detailed description of the safety contents is below
the sign. They are arranged in such a format:

Danger:
Casualties or a major accident like device damage may occur if
one ignore this safety warning.

Warning:
A major or severe accident or device damage may occur if one
ignore this safety warning.

4 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 1 Safety Instructions

Caution:
A severe accident or device damage may occur if one ignore this
safety warning.

Note:
Note, Hint, Tip…:
The remarks, hints and tips in addition to those about safety signs

Confidential and Proprietary Information of ZTE CORPORATION 5

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

This page is intentionally blank.

6 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2

Alarm and Notification

Overview

Table of Contents
Overview........................................................................... 7
Classification by Maintenance Contents.................................. 7
General Meaning of Alarm and Notification ............................. 8
Cause of Alarm and Notification ............................................ 9
Handling Method of Alarm and Notification ............................10

Overview
Introduction This chapter describes the classification of the ZXSS10 SS1b
equipment maintenance, the general meaning, cause, and han-
dling method of notification and alarm.

Classification by
Maintenance Contents
Introduction Maintenance of the ZXSS10 SS1b can be divided into the following
three parts:
1. Routine maintenance
According to the maintenance cycle, maintenance of the
ZXSS10 SS1b is divided into daily routine maintenance and
periodical routine maintenance. The proper routine mainte-
nance of the ZXSS10 SS1b system is significant. It serves to
check the running state of the device periodically and solve
the detected problem in time, for the purpose of detecting
hidden troubles, preventing accidents, locating faults in time
and conducting troubleshooting as early as possible. For
the details of routine maintenance of ZXSS10 SS1b, refer
to the ZXSS10 SS1b SoftSwitch Control Equipment Routine
Maintenance Manual.
2. Notification and alarm
ZXSS10 SS1b is a powerful Softswitch product. Besides the ap-
plications and service processing capacity, the ZXSS10 SS1b is

Confidential and Proprietary Information of ZTE CORPORATION 7

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

also featured with the self-contained fault notification system

and functions, namely, alarms and notifications of the ZXSS10
SS1b. To note that the system is configured with the auto-
matic error correction mechanism to handle some reported
faults, therefore no human involvement is needed. For de-
tails of alarms and notifications of the ZXSS10 SS1b, refer to
the description in the following chapters.

Tip:
For the alarm content, levels, and related operations, refer
to the ZXSS10 SS1b SoftSwitch Control Equipment Operation
Manual, Alarm Operation.

3. Troubleshooting
The SoftSwitch (SS) system is very different from the tradi-
tional PSTN system. Thanks to the separation of the service
layer, control layer, and core layer, the SS is more powerful
and easy to be expanded. However, as a system built on the
network packet switching, most of the SS faults are related
to the network. For more details, refer to the ZXSS10 SS1b
SoftSwitch Control Equipment Troubleshooting Manual.

General Meaning of Alarm

and Notification
Introduction The alarm information of the ZXSS10 SS1b is classified into the
following two sorts:
1. Alarms
Alarms of the ZXSS10 SS1b are used to define the tangible
and removable faults happened on the system. The alarms are
classified into four levels based on the severity of the faults:
i. Critical (Level-1) alarm means there is a nearly fatal fault
happened on the system and the system cannot normally
run, such as the system data area utilization ratio is 100%,
the connection link of the billing server is broken and so on.
ii. Major (Level-2) alarm means there is a critical fault hap-
pened on the system. The system still works but some
important functions of the system cannot be performed.
iii. Minor (Level-3) alarm means there is a common fault hap-
pened on the system. The system still works well in terms
of its framework but partial function is affected to a certain
extent.
iv. Warning (Level-4)alarm means there is a minor fault hap-
pened on the system. It does not affect the normal running
and functions of the system, but it will grow into a higher
level problem if not handled for a long time.
2. Notifications

8 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2 Alarm and Notification Overview

Notifications of the ZXSS10 SS1b are used to define the shape-

less and irremovable faults. They are usually used to notify the
background system about the current state change. The level
is the slightest and no recovery is needed.

Cause of Alarm and

Notification
Introduction Alarm and the notification messages can be generated due to the
following reasons:
1. Hardware fault
i. Board fault Boards such as the SC, SPC, and NIC become
faulty.
ii. Other hardware fault For example, the system power fault,
fan fault, and hard disk access fault.
iii. Hardware insufficiency The existing hardware, such as
boards, CPU, memory, hard disks and so on cannot meet
the continuous increase of actual needs.
2. Software and system breakdown
i. Operating system fault The SoftSwitch is installed in the
Sun Solaris platform, while the billing system is installed in
the Windows platform. Each kind of operating system often
has some memory management and security problems to
a certain extent.
ii. Database fault The system database is installed in the Ora-
cle platform, while the billing system is installed on the SQL
Server. Each kind of database configuration and misusage
will lead to many kinds of usage and security problems.
iii. Software fault The SoftSwitch control equipment software
unavoidably has some problems. Most of the time alarms
are generated due to inconsistent software version up-
grade.
3. Alarms due to environmental change
i. The reliable running of the system requires a proper envi-
ronment. When the temperature and humidity exceed the
threshold values, the system will generate alarms.
ii. Natural disaster or accidental occurrence can generate
alarms. For example, thunder and lightning, the fire
and infrared cause the system to generate corresponding
alarms.
4. Alarms due to setup and configuration fault
i. Setup fault The interface among devices and the definitions
of the system authentication, file or directory.
ii. Configuration fault The system performance degradation
and capacity decrease caused by the wrong or improper
configuration cannot meet the requirements of the system.

Confidential and Proprietary Information of ZTE CORPORATION 9

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

If the alarm threshold is defined by the subscriber, perform

the proper configuration.
iii. Command error The improper command is entered or the
grogram with wrong script is executed.
5. Alarms due to network fault
i. Local connection cannot be performed. The board is in-
serted to the improper slot or improperly inserted, the con-
tact problem of the cable and interface, and configuration
errors of the IP address, submask, default gateway, and
route often lead to the local connection faults.
ii. Network device faults, including those happen at the office,
and various route, switch equipment, and intermediate link
faults on the Internet.
iii. Network application fault Services needed by SS such as
the FTP and NTP services are unavailable, faults caused
by the network security congestion caused by the network
storm, and the voice quality problems.
6. Event notifications and status reports, such as the following:
i. Critical event report A series of critical events happen in the
system, and it is needed to let the administrator know what
happened, such as, registration of important gateways and
disaster recovery events.
ii. Various status report This report is generated when certain
events are successfully completed, the system fault is re-
moved, or other status change.
7. The peer-end equipment becomes faulty, resulting in a series
of alarms generated in the system.

Handling Method of Alarm

and Notification
Introduction 1. Frequently used alarm analysis methods:
i. Read carefully the alarm information, fault description, and
related causes reported by the system. View the related
contents of Chapter 3 through Chapter 7. If there are re-
lated MML commands, run them to obtain from the system
more meaningful information to facilitate the alarm analy-
sis.
ii. With regard to the network faults, turn to running various
network commands such as ping, telnet, netstat, ipco
nfig/ifconfig, route, and trace/tracert to facilitate the
alarm analysis.
iii. With regard to the OS or database faults, turn to running
system or file commands to view the file path, script config-
uration, system process and state. In terms of the security
faults, use the third-party tools to check whether the sys-
tem has viruses or security vulnerabilities.

10 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2 Alarm and Notification Overview

iv. With regard to the setup, configuration or performance

faults directly go to view the related data configuration.
Check whether the items are improperly configured or not
configured, or the wrong items are configured.
v. For the tough faults, turn to the protocol trace and analysis
tools carried by the system, or catch the data packets to
analyze the possible reasons.
vi. With regard to the possible hardware faults, usually, the
replacement method is used, that is, replace the probably
faulty device with a proper one to swiftly locate the fault,
to tell whether the fault is a “soft” or “hard” one.
2. General alarm handling methods:
i. For the hardware fault, if it can be restored, restore it; if
not, replace it. With regard to the “insufficient hardware”
fault, add the hardware or replace it with high performance
one. With regard to the problem of insufficient storage
space, delete the unused or redundant data. Make sure
the data can be deleted before the operation, or back up
the data.
ii. For the software or system fault, if it concerns the security
of the operating system, patch the system in time, or kill
viruses and strengthen the system password and so on.
For the system software or version fault, upgrade it.
iii. For the alarm caused by the environment change, analyze
and handle the fault based on the alarm phenomena and
information. Try to avoid or decrease the direct and physi-
cal damage on the equipment caused by the environment.
iv. For the system setup and configuration fault, detect in
where the fault is located and modify and optimize the
faulty configuration. For the alarm caused by the com-
mand input error, view the online command help or refer
to the related manuals to modify the command error and
execute again.
v. For the network fault, perform the following operations
based on the alarm phenomena: modify the wrong net-
work configuration, reconnect the board and the cable, re-
place or repair the damaged office equipment, reboot the
FTP service, or re-specify the IP address of the system NTP
service. For the faults on the Internet, use the other trunk
or route to handle the fault.
vi. For the event notification or status report, usually, no han-
dling is needed. Sometimes it is needed for the manage-
ment staff to pay attention to the causes of the alarm. If
it is confirmed there is a fault, handle it based on the phe-
nomena and the previously mentioned methods, or refer
to the ZXSS10 SS1b SoftSwitch Control Equipment Trou-
bleshooting Manual.
vii.For the faults of the peer-end equipment, notice initiatively
the peer-end about the alarm and help them handle the
fault. After the handling, check and notice the peer-end to
see whether the fault is removed.
3. Alarms cannot be resolved by users:

Confidential and Proprietary Information of ZTE CORPORATION 11

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

If subscribers cannot handle the fault, contact the SS1b

experts of ZTE, or directly dial the hotlines such as
0755-26770800, 800-8301118, and 4008301118 of the ZTE
customer center for help.
4. Sequential procedures after the alarm handling:
i. Verify that the alarm is successfully removed. Usually, the
following methods are used: the alarm does not continue
or an alarm is reported to show that the system is normal;
rebooting the board or module, the fault information does
not appear again, and the traffic state changes from ab-
normal to normal and so on.
ii. Record them in details, including the alarm phenomena,
cause, handling method, and so on. “Alarm handling logs”
make it convenient to handle the similar or further fault.

12 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3

Notification Information
and Relevant Handling

Table of Contents
Overview..........................................................................13
Notification Information Processing ......................................13

Overview
Introduction Notifications of the ZXSS10 SS1b are used to define the shapeless
and irremovable faults. They are usually used to notify the back-
ground system about the current state change.

Notification Information
Processing
Failed to Select Trunk(1)
Alarm Code 1
Cause Failed to select trunk
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Failed to select trunk
alarm
Handling method Trunk circuit not available. Solution:
1. Use 4103 to check the trunk status, then unblock the trunk.
2. Check data configuration.
3. Add new trunk circuit.
4. Check the remotely connected equipment.

Confidential and Proprietary Information of ZTE CORPORATION 13

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Emergency Call Service

Notification(4)
Alarm Code 4
Cause Urgent and special service such as 119,110
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Emergency call service notification
alarm
Handling method Emergency call notification. The call information including
caller,called,call time etc are recorded for query.Not need to
handle.

Immediate Malicious Call(5)

Alarm Code 5
Cause Immediate malicious call
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Immediate Malicious Call
alarm
Handling method Immediate malicious call notification.Information such as
caller,called,malicious call route or source are recorded. Notify
related department or person

Continuity Successful(6)
Alarm Code 6
Cause Continuity test succeeded
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity successful
alarm

14 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Handling method Not need to handle.

Continuity Failure: Looping Failed(7)

Alarm Code 7
Cause COT fail:COT loop failure
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity failure: Looping failed
alarm
Handling method Please contact the related ZTE technical experts.

Continuity Failure: Mg Returning

Result Failed(8)
Alarm Code 8
Cause The check between the SoftSwitch and the switch is to notify the
peer-end office through the signaling to build the loop. Playing
the announcement when the continuity is performed. The an-
nouncement is sent to the switch from TG that is ordered by the
SS through the H248 signaling. TG returns the continuity result. If
the result is a failure, an alarm is reported to show the continuity
failure.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity failure: MG returning result failed
alarm
Handling method 1. Check the detailed cause of the failure, which is returned by
the continuity result. With the help of signaling tracing on
H248/MGCP, find out why the continuity fails.
2. If the cause is unclear based on the returned result, turn to
the switch side to seek together why the loop building fails.

Confidential and Proprietary Information of ZTE CORPORATION 15

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Continuity Failure: Waiting for The

Answer of Continuity Request Times
Out(9)
Alarm Code 9
Cause The SS service sends the continuity request to the gateway
through the H248 message and waits for the answer. If the
answer is not received, SS considers that the continuity cannot be
performed. Then, an alarm is generated to show the continuity
failure.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity failure: Waiting for the answer of continuity request
alarm times out
Handling method 1. Run the Ping packet command to check the status of the net-
work between the SS and gateway.
2. Check whether the time duration set by the timer (T124)is too
short. Usually, the time duration is 2 seconds.
3. Perform the protocol tracing on the SS7, or invite the gateway
side to help with finding out why the continuity failure happens.

Continuity Failure: Waiting for

Continuity Result Times Out(10)
Alarm Code 10
Cause The SS service sends the continuity request to the gateway
through the H248 message, and the continuity result will be
sent by the gateway to the SS through H248. If the result is
not received and time is out, an alarm is generated to show the
continuity failure.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity failure: Waiting for continuity result times out
alarm
Handling method 1. Run the Ping packet command to check the status of the net-
work between the SS and gateway.
2. Check whether the time duration set by the timer (T124)is too
short. Usually, the time duration is 2 seconds.
3. Perform the H248/MGCP protocol tracing, or invite the gateway
side to help with finding out why the continuity failure happens.

16 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Continuity Failure: Playing Continuity

Test Tune Failed(11)
Alarm Code 11
Cause After sending the signaling of the continuity test, SS requires the
gateway or media server to play the continuity test tune. If the
gateway fails to play the test tune, an alarm is reported to the SS.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity failure: Playing continuity test tune failed
alarm
Handling method 1. Check whether the tune number under the SS is correct and
whether the media server has the processing of the tune num-
ber.
2. Check the failure reason reported by the media server to locate
and handle the fault.

Continuity Failure: SS7 Release

Message Is Received(12)
Alarm Code 12
Cause In the process of continuity test, the service notifies the SS7 to
send the continuity-related signaling, while the SS7 needs to wait
for the continuity result and transfer it to the peer-end switch. If
the SS7 sends the release primitive to the service, the continuity
process stops at once. The circuit is released, resulting in the
alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Continuity failure: SS7 release message is received
alarm
Handling method This is a release initiated by the SS7 protocol. It is needed to
trace the SS7 protocol to check why the release message is sent.
Usually, to find out the cause, the help of the SS7 side is needed.

Long Call Alarm(13)

Alarm Code 13

Confidential and Proprietary Information of ZTE CORPORATION 17

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Cause Long call alarm

System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Long call alarm
alarm
Handling method The call hold time is ultra-long. For example, it reaches or exceeds
more than two hours. View the state of the related client and
subscriber. If the client or subscriber is really in the normal state
of conversation, no handling is needed. Otherwise, forcibly release
the call in case that the wrong bill is generated.

Ringing Didn”T Answer(16)

Alarm Code 16
Cause Ringing didn”t answer twice
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Ringing didn”t answer
alarm
Handling method Please contact the related ZTE technical experts.

Instant Malicious Call Alarm(17)

Alarm Code 17
Cause The called rings and requests to record the caller number to trace
the current malicious call.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Instant malicious call alarm
alarm
Handling method This is a malicious call service notification. Record the related
information such as the caller, called, and path or source of the
malicious call. Notify the related department or individual.

18 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Number of Pulses Exceeds

Threshold(18)
Alarm Code 18
Cause The number of pulse exceeding threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Number of pulses exceeds threshold
alarm
Handling method The pulses of 16kc calls acumulate to reach or exceed the thresh-
old value. Doesn’t influence call service.Not need to handle.

Recover SPC Board Based on

The Configuration in Fail-Manager
Options(19)
Alarm Code 19
Cause Recover SPC board based on the configuration in Fail-Manager op-
tions
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Recover SPC board based on the configuration in Fail-Manager op-
alarm tions
Handling method The Board is blocked, you must reboot the board.

Reset SPC Board Based on The

Configuration in Fail-Manager
Options(20)
Alarm Code 20
Cause Reset SPC board based on the configuration in Fail-Manager op-
tions
System Style of Foreground NE Device Alarm
Alarm

Confidential and Proprietary Information of ZTE CORPORATION 19

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Style notification

Alarm Report SC,SPC
Object
Aftermath of the Reset SPC board based on the configuration in Fail-Manager op-
alarm tions
Handling method No need to care. The board will recover automatically.

All The DR SPC Protocol Process Is

Normal(23)
Alarm Code 23
Cause All the DR SPC protocol process is normal
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the All the DR SPC protocol process is normal
alarm
Handling method Each protocol of board can be enabled normal, no need to handle.

The Alarm Business Overtime(24)

Alarm Code 24
Cause The alarm business error
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the The alarm business overtime
alarm
Handling method Indicate alarm call service but no answer. Not need to handle.

Alarm for Immediate Malicious

Call(25)

Alarm Code 25
Cause User register immediate malicious call,send this alarm when ring-
ing

20 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Alarm for Immediate Malicious call
alarm
Handling method Indicate Immediate Malicious callNot need to handle.

High Level Call Gapping Alarm(512)

Alarm Code 512

Cause High level call gapping alarm
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the High level call gapping alarm
alarm
Handling method Check whether the number of controlled teminated No. is correct,
if so, neglect this alarm.

Low Level Call Gapping Alarm(513)

Alarm Code 513
Cause Low level call gapping alarm
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Low level call gapping alarm
alarm
Handling method 1. Perform session control to ensure the normal operations of the
board.
2. Contact the experts for capacity expansion to diffluence the
traffic of this board.

Confidential and Proprietary Information of ZTE CORPORATION 21

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

High Level Call Gapping Detail

Alarm(514)
Alarm Code 514
Cause High level call gapping detail alarm
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the High level call gapping detail alarm
alarm
Handling method Analyze whether the controlled terminated No. should be con-
trolled, neglect it if it’s correct.

Low Level Call Gapping Detail

Alarm(515)
Alarm Code 515
Cause Low level call gapping detail alarm
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Low level call gapping detail alarm
alarm
Handling method 1. Perform session control to ensure the normal operations of the
board.
2. Contact the experts for capacity expansion to diffluence the
traffic of this board.

Interaction with SHLR Times

Out(4102)
Alarm Code 4102
Cause The SHLR server is faulty.The network is faulty If the fault lies in
the SS side, probably because the SS is suspended.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification

22 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Alarm Report SC,SPC

Object
Aftermath of the Interaction with SHLR times out
alarm
Handling method 1. Check whether the SHLR server is started and whether it works
well.
2. The GT translation configuration of the SHLR is wrong and no
message can be returned. Check whether the GT translation
configuration of the SHLR is correct.
3. As for the network failure, run the Ping packet command to
check the network state between SHLR and SS. Usually, con-
tact the technical gurus for handling.

Register Message Expire(4103)

Alarm Code 4103
Cause Register message expire
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Register message expire
alarm
Handling method Check the refresh-time configuration of CSCF or SBC

AG112 Incremental Backup

Alarm(5662)
Alarm Code 5662
Cause AG112 all backup failed
System Style of System Management
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the AG112 incremental backup alarm
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

Confidential and Proprietary Information of ZTE CORPORATION 23

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

AG112 Full Backup Alarm(5663)

Alarm Code 5663
Cause Threshold 3:Service licenses will be used up,need to order it
System Style of System Management
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the AG112 full backup alarm
alarm
Handling method Please refere to the additional information and purchase immedi-
ately.

Userline Already Exist in SS(5668)

Alarm Code 5668
Cause In the message send from shlr to ss,the userline already exist in
ss and is belong to another psid.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Userline already exist in ss
alarm
Handling method Search userline in SHLR,remove the incorrect PSID and reserve
the right one.

Uncorrect Data Length in

SHLR(5669)
Alarm Code 5669
Cause Uncorrect data length
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Uncorrect data length in shlr
alarm
Handling method Modify user information in shlr,send the message again

24 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Ctx Not Exist in SS(5670)

Alarm Code 5670
Cause Ctx not exist in ss,add new ctx to ss and resend the message again.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Ctx not exist in ss
alarm
Handling method Add new ctx to SS and resend the message again.

Mls Not Exist in SS(5671)

Alarm Code 5671
Cause Mls not exist in ss,add new mls to ss and resend the message
again.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Mls not exist in ss
alarm
Handling method Add new mls to SS and resend the message again.

ISDN User Not Exist in SS(5672)

Alarm Code 5672
Cause ISDN user not exist in ss,add new ISDN user to ss and resend the
message again.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the ISDN user not exist in ss
alarm
Handling method Add ISDN user to SS and resend the message again.

Confidential and Proprietary Information of ZTE CORPORATION 25

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Userline Not Exist in SS(5673)

Alarm Code 5673
Cause In the message send from shlr to ss,userline is not correct.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Userline not exist in ss
alarm
Handling method Modify useline to be correct or add noc and abcd information in
SS.

Zone Or Node Or Card Not Exist in

SS(5674)
Alarm Code 5674
Cause Zone or node or card not exist in ss
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Zone or node or card not exist in ss
alarm
Handling method Modify zone or node or card in SS.

Database Error When Modify Data in

SS(5675)
Alarm Code 5675
Cause Database error when modify data in ss
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Database error when modify data in ss
alarm
Handling method Modify user service in SHLR,and send message again.

26 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Node Autoselect Error in SS(5676)

Alarm Code 5676
Cause SS node autoselect error
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Node autoselect error in ss
alarm
Handling method Modify zone of the user and keep only one node in this zone.

Tollnum Not Match(5677)

Alarm Code 5677
Cause Tollnum in userline not match with tollnum of the user
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Tollnum not match
alarm
Handling method Modify tollnum in userline to be correct

Inadequate Capacity of Node/ Zone

Configuration of SS(5680)
Alarm Code 5680
Cause DR Sync:Node or zone configuration inadequate capacity, can not
accommodate the nodeid or, the zone after mapping.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Inadequate capacity of NODE/ ZONE configuration of SS
alarm
Handling method Save the alarm content,and call the maintenance engineer.

Confidential and Proprietary Information of ZTE CORPORATION 27

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Oracle Error(5681)
Alarm Code 5681
Cause DR Sync:Catch oracle error when written synchronous data in SS-
BAK.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Oracle error
alarm
Handling method Save the alarm content,and call the maintenance engineer.

Write Drsrc Failer(5682)

Alarm Code 5682
Cause Carry Sync:write drsrc faler
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Write drsrc failer
alarm
Handling method Save the alarm content,and call the maintenance engineer.

The Field Number of Table in Dict

Has Overed Length(5888)
Alarm Code 5888
Cause The field number of table in dict has overed length
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the The field number of table in dict has overed length
alarm

28 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Handling method Restrict the field number of the table

The Length of Field”S Name Has

Overed Length(5889)

Alarm Code 5889

Cause The length of field”s name has overed length
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the The length of field”s name has overed length
alarm
Handling method Redefine the name of the field

Executing Sql Statement

Failed(6402)

Alarm Code 6402

Cause The syntax of the SQL statement is wrong.The scripts of the fore-
ground and background are inconsistent with each other.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Executing SQL statement failed
alarm
Handling method 1. Check whether the syntax of the SQL statement is wrong.
2. Check whether t scripts of the foreground and background are
consistent with each other. Replace the inconsistent scripts of
the foreground and background.

Synchronous Transfer Failure(6403)

Alarm Code 6403
Cause � The network is faulty.
� The table record is invalid.

Confidential and Proprietary Information of ZTE CORPORATION 29

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

� On the board where the MT attributes are consistent, the ver-

sions are inconsistent. As a result, the transfer fails.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Synchronous transfer failure
alarm
Handling method 1. In the first place, run the Ping packet to check whether the
network is faulty.
2. Check whether the table record is valid and whether the data
configured at the interface is within the range defined by the
table.i
3. Check the MT attributes of the background and foreground are
distributed to which boards and whether they are consistent.
4. Perform the synchronous transfer once again. Check whether
the alarm disappears.
5. If the fault cannot be handled, contact the technical gurus.

Inserting Data Table Failure At

Startup(6914)
Alarm Code 6914
Cause � There is invalid data on the background database;
� The table capacity of the foreground database exceeds the up-
per threshold.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Inserting data table failure at startup
alarm
Handling method Check the data and data tables on the foreground and background:
1. If there is invalid data on the background database, no han-
dling is needed. Reboot the system.
2. If the table capacity of the foreground database exceeds the
upper threshold, usually, contact the technical gurus for han-
dling.

It Is Found At Startup That The Data

Table Field Is Lost(6916)
Alarm Code 6916

30 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Cause Data table and data error

System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the It is found at startup that the data table field is lost
alarm
Handling method Check the data tables and data on the foreground and back-
ground;Reboot the system. Usually, contact the technical gurus
for handling.

Traffic Dredge Through Route

Link(7335)
Alarm Code 7335
Cause If the outgoing call duration to an operator in a certain month
reaches the preset value, the system can automatically route the
surplus traffic to the circuits of other operators.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Traffic statistics
Object
Aftermath of the Traffic Dredge Through Route Link
alarm
Handling method Traffic control automatically selects other operators to route the
traffic. This is a prompt. No handling is needed.

Subscriber Port Is Manually

Unblocked(7392)
Alarm Code 7392
Cause The subscriber port is manually unblocked.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subscriber port is manually unblocked
alarm
Handling method This is system prompt. No handling is needed.

Confidential and Proprietary Information of ZTE CORPORATION 31

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Trunk Circuit Group Is Manually

Blocked(7393)
Alarm Code 7393
Cause Trunk circuit was blocked by MML
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Trunk circuit group is manually blocked
alarm
Handling method Contact expert for support.

All Circuits in The Trunk Group Are

Busy(7394)
Alarm Code 7394
Cause The number of online subscribers in the trunk group is too big.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the All circuits in the trunk group are busy
alarm
Handling method If this situation occasionally happens and lasts not too long, no
handling is needed. If it happens frequently, optimize the trunk
group and route configuration, or add hardware to the system and
expand the capacity. For more details, refer to the Trunk Data Con-
figuration and Route Data Configuration sections in the ZXSS10
SS1b SoftSwitch Control Equipment Data Configuration Manual,
Trunk and ZXSS10 SS1b SoftSwitch Control Equipment Data Con-
figuration Manual, Route.

Disaster Recovery Gateway

Registration(7400)
Alarm Code 7400
Cause Backup gateway register
System Style of Foreground NE Device Alarm
Alarm

32 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Alarm Style notification

Alarm Report SC,SPC
Object
Aftermath of the Disaster recovery gateway registration
alarm
Handling method Contact expert for support

Disaster Recovery Gateway Quits

Registration(7401)
Alarm Code 7401
Cause Backup gateway quit register
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Disaster recovery gateway quits registration
alarm
Handling method Contact expert for support

Voice Resource of The Gateway

Exceeds Level-1 Threshold(7501)
Alarm Code 7501
Cause MG tone resource beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice resource of the gateway exceeds level-1 threshold
alarm
Handling method The gateway tone resourse exceeds the first level threshold.
1. Use traffic control to ensure the tone resource useage for the
important subscribers.
2. Add new tone resource hardware, to ensure enough availability
of tone resources.

Confidential and Proprietary Information of ZTE CORPORATION 33

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Voice Resource of The Gateway

Exceeds Level-2 Threshold(7502)
Alarm Code 7502
Cause MG tone resource beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice resource of the gateway exceeds level-2 threshold
alarm
Handling method The gateway tone resourse exceeds the second level threshold.
1. Use traffic control to ensure the tone resource useage for the
important subscribers.
2. Add new tone resource hardware, to ensure enough availability
of tone resources.

Voice Resource of The Gateway

Exceeds Level-3 Threshold(7503)
Alarm Code 7503
Cause MG tone resource beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice resource of the gateway exceeds level-3 threshold
alarm
Handling method The gateway tone resourse exceeds the third level threshold.
1. Use traffic control to ensure the tone resource useage for the
important subscribers.
2. Add new tone resource hardware, to ensure enough availability
of tone resources.

Voice Resource of The Gateway

Exceeds Level-4 Threshold(7504)
Alarm Code 7504
Cause MG tone resource beyond threshold 4

34 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice resource of the gateway exceeds level-4 threshold
alarm
Handling method The gateway tone resourse exceeds the fourth level threshold.
1. Use traffic control to ensure the tone resource useage for the
important subscribers.
2. Add new tone resource hardware, to ensure enough availability
of tone resources.

Voice Resource of The Gateway

Exceeds Level-5 Threshold(7505)
Alarm Code 7505
Cause MG tone resource beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice resource of the gateway exceeds level-5 threshold
alarm
Handling method The gateway tone resourse exceeds the fifth level threshold.
1. Use traffic control to ensure the tone resource useage for the
important subscribers.
2. Add new tone resource hardware, to ensure enough availability
of tone resources.

Voice Resource of The Gateway

Exceeds Level-6 Threshold(7506)
Alarm Code 7506
Cause MG tone resource beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice resource of the gateway exceeds level-6 threshold
alarm
Handling method The gateway tone resourse exceeds the sixth level threshold.

Confidential and Proprietary Information of ZTE CORPORATION 35

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

1. Use traffic control to ensure the tone resource useage for the
important subscribers.
2. Add new tone resource hardware, to ensure enough availability
of tone resources.

Conference Resource of The

Gateway Exceeds Level-1
Threshold(7507)
Alarm Code 7507
Cause MG conference resource beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Conference resource of the gateway exceeds level-1 threshold
alarm
Handling method The gateway conference resourse exceeds the first level threshold.
1. Use traffic control to ensure the conference resource useage
for the important subscribers.
2. Add new conference resource hardware, to ensure enough
availability of conference resources.

Conference Resource of The

Gateway Exceeds Level-2
Threshold(7508)
Alarm Code 7508
Cause MG conference resource beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Conference resource of the gateway exceeds level-2 threshold
alarm
Handling method The gateway conference resourse exceeds the second level thresh-
old.
1. Use traffic control to ensure the conference resource useage
for the important subscribers.
2. Add new conference resource hardware, to ensure enough
availability of conference resources.

36 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Conference Resource of The

Gateway Exceeds Level-3
Threshold(7509)
Alarm Code 7509
Cause MG conference resource beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Conference resource of the gateway exceeds level-3 threshold
alarm
Handling method The gateway conference resourse exceeds the third level thresh-
old.
1. Use traffic control to ensure the conference resource useage
for the important subscribers.
2. Add new conference resource hardware, to ensure enough
availability of conference resources.

Conference Resource of The

Gateway Exceeds Level-4
Threshold(7510)
Alarm Code 7510
Cause MG conference resource beyond threshold 4
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Conference resource of the gateway exceeds level-4 threshold
alarm
Handling method The gateway conference resourse exceeds the fourth level thresh-
old.
1. Use traffic control to ensure the conference resource useage
for the important subscribers.
2. Add new conference resource hardware, to ensure enough
availability of conference resources.

Confidential and Proprietary Information of ZTE CORPORATION 37

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Conference Resource of The

Gateway Exceeds Level-5
Threshold(7511)
Alarm Code 7511
Cause MG conference resource beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Conference resource of the gateway exceeds level-5 threshold
alarm
Handling method The gateway conference resourse exceeds the fifth level threshold.
1. Use traffic control to ensure the conference resource useage
for the important subscribers.
2. Add new conference resource hardware, to ensure enough
availability of conference resources.

Conference Resource of The

Gateway Exceeds Level-6
Threshold(7512)
Alarm Code 7512
Cause MG conference resource beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Conference resource of the gateway exceeds level-6 threshold
alarm
Handling method The gateway conference resourse exceeds the sixth level thresh-
old.
1. Use traffic control to ensure the conference resource useage
for the important subscribers.
2. Add new conference resource hardware, to ensure enough
availability of conference resources.

38 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Vtca Resource of The Gateway

Exceeds Level-1 Threshold(7513)
Alarm Code 7513
Cause MG VTCA resource beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the VTCA resource of the gateway exceeds level-1 threshold
alarm
Handling method The gateway VTCA resourse exceeds the first level threshold.
1. Use traffic control to ensure the VTCA resource useage for the
important subscribers.
2. Add new VTCA resource hardware, to ensure enough availabil-
ity of VTCA resources.

Vtca Resource of The Gateway

Exceeds Level-2 Threshold(7514)
Alarm Code 7514
Cause MG VTCA resource beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the VTCA resource of the gateway exceeds level-2 threshold
alarm
Handling method The gateway VTCA resourse exceeds the second level threshold.
1. Use traffic control to ensure the VTCA resource useage for the
important subscribers.
2. Add new VTCA resource hardware, to ensure enough availabil-
ity of VTCA resources.

Vtca Resource of The Gateway

Exceeds Level-3 Threshold(7515)
Alarm Code 7515
Cause MG VTCA resource beyond threshold 3

Confidential and Proprietary Information of ZTE CORPORATION 39

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the VTCA resource of the gateway exceeds level-3 threshold
alarm
Handling method The gateway VTCA resourse exceeds the third level threshold.
1. Use traffic control to ensure the VTCA resource useage for the
important subscribers.
2. Add new VTCA resource hardware, to ensure enough availabil-
ity of VTCA resources.

Vtca Resource of The Gateway

Exceeds Level-4 Threshold(7516)
Alarm Code 7516
Cause MG VTCA resource beyond threshold 4
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the VTCA resource of the gateway exceeds level-4 threshold
alarm
Handling method The gateway VTCA resourse exceeds the fourth level threshold.
1. Use traffic control to ensure the VTCA resource useage for the
important subscribers.
2. Add new VTCA resource hardware, to ensure enough availabil-
ity of VTCA resources.

Vtca Resource of The Gateway

Exceeds Level-5 Threshold(7517)
Alarm Code 7517
Cause MG VTCA resource beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the VTCA resource of the gateway exceeds level-5 threshold
alarm
Handling method The gateway VTCA resourse exceeds the fifth level threshold.

40 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

1. Use traffic control to ensure the VTCA resource useage for the
important subscribers.
2. Add new VTCA resource hardware, to ensure enough availabil-
ity of VTCA resources.

Vtca Resource of The Gateway

Exceeds Level-6 Threshold(7518)
Alarm Code 7518
Cause MG VTCA resource beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the VTCA resource of the gateway exceeds level-6 threshold
alarm
Handling method The gateway VTCA resourse exceeds the sixth level threshold.
1. Use traffic control to ensure the VTCA resource useage for the
important subscribers.
2. Add new VTCA resource hardware, to ensure enough availabil-
ity of VTCA resources.

Tln Resource of The Gateway

Exceeds Level-1 Threshold(7519)
Alarm Code 7519
Cause MG TLN resource beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the TLN resource of the gateway exceeds level-1 threshold
alarm
Handling method The gateway TLN(trunk line network) resource exceeds the first
level threshold.
1. Use traffic control to reduce the use of unneccessary gateway
TLN resources.
2. Add new hardware to provide more gateway TLN resources.

Confidential and Proprietary Information of ZTE CORPORATION 41

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Tln Resource of The Gateway

Exceeds Level-2 Threshold(7520)
Alarm Code 7520
Cause MG TLN resource beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the TLN resource of the gateway exceeds level-2 threshold
alarm
Handling method The gateway TLN(trunk line network) resource exceeds the second
level threshold.
1. Use traffic control to reduce the use of unneccessary gateway
TLN resources.
2. Add new hardware to provide more gateway TLN resources.

Tln Resource of The Gateway

Exceeds Level-3 Threshold(7521)
Alarm Code 7521
Cause MG TLN resource beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the TLN resource of the gateway exceeds level-3 threshold
alarm
Handling method The gateway TLN(trunk line network) resource exceeds the third
level threshold.
1. Use traffic control to reduce the use of unneccessary gateway
TLN resources.
2. Add new hardware to provide more gateway TLN resources.

Tln Resource of The Gateway

Exceeds Level-4 Threshold(7522)
Alarm Code 7522
Cause MG TLN resource beyond threshold 4

42 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the TLN resource of the gateway exceeds level-4 threshold
alarm
Handling method The gateway TLN(trunk line network) resource exceeds the fourth
level threshold.
1. Use traffic control to reduce the use of unneccessary gateway
TLN resources.
2. Add new hardware to provide more gateway TLN resources.

Tln Resource of The Gateway

Exceeds Level-5 Threshold(7523)
Alarm Code 7523
Cause MG TLN resource beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the TLN resource of the gateway exceeds level-5 threshold
alarm
Handling method The gateway TLN(trunk line network) resource exceeds the fifth
level threshold.
1. Use traffic control to reduce the use of unneccessary gateway
TLN resources.
2. Add new hardware to provide more gateway TLN resources.

Tln Resource of The Gateway

Exceeds Level-6 Threshold(7524)
Alarm Code 7524
Cause MG TLN resource beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the TLN resource of the gateway exceeds level-6 threshold
alarm

Confidential and Proprietary Information of ZTE CORPORATION 43

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Handling method The gateway TLN(trunk line network) resource exceeds the sixth
level threshold.
1. Use traffic control to reduce the use of unneccessary gateway
TLN resources.
2. Add new hardware to provide more gateway TLN resources.

CPU Utilization of Gateway MP Board

Exceeds Level-1 Threshold(7525)
Alarm Code 7525
Cause MG MP CPU usage beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway MP board exceeds level-1 threshold
alarm
Handling method The gateway CPU utilization of MP card exceeds the first level
threshold.
1. Use traffic control to reduce CPU utilization of MP card.
2. Replace the MP card with a higher prcoessing speed.

CPU Utilization of Gateway MP Board

Exceeds Level-2 Threshold(7526)
Alarm Code 7526
Cause MG MP CPU usage beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway MP board exceeds level-2 threshold
alarm
Handling method The gateway CPU utilization of MP card exceeds the second level
threshold.
1. Use traffic control to reduce CPU utilization of MP card.
2. Replace the MP card with a higher prcoessing speed.

44 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

CPU Utilization of Gateway MP Board

Exceeds Level-3 Threshold(7527)
Alarm Code 7527
Cause MG MP CPU usage beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway MP board exceeds level-3 threshold
alarm
Handling method The gateway CPU utilization of MP card exceeds the third level
threshold.
1. Use traffic control to reduce CPU utilization of MP card.
2. Replace the MP card with a higher prcoessing speed.

CPU Utilization of Gateway MP Board

Exceeds Level-4 Threshold(7528)
Alarm Code 7528
Cause MG MP CPU usage beyond threshold 4
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway MP board exceeds level-4 threshold
alarm
Handling method The gateway CPU utilization of MP card exceeds the fourth level
threshold.
1. Use traffic control to reduce CPU utilization of MP card.
2. Replace the MP card with a higher prcoessing speed.

CPU Utilization of Gateway MP Board

Exceeds Level-5 Threshold(7529)
Alarm Code 7529
Cause MG MP CPU usage beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification

Confidential and Proprietary Information of ZTE CORPORATION 45

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Report Background Server

Object
Aftermath of the CPU utilization of gateway MP board exceeds level-5 threshold
alarm
Handling method The gateway CPU utilization of MP card exceeds the fifth level
threshold.
1. Use traffic control to reduce CPU utilization of MP card.
2. Replace the MP card with a higher prcoessing speed.

CPU Utilization of Gateway MP Board

Exceeds Level-6 Threshold(7530)
Alarm Code 7530
Cause MG MP CPU usage beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway MP board exceeds level-6 threshold
alarm
Handling method The gateway CPU utilization of MP card exceeds the sixth level
threshold.
1. Use traffic control to reduce CPU utilization of MP card.
2. Replace the MP card with a higher prcoessing speed.

CPU Utilization of Gateway PP Board

Exceeds Level-1 Threshold(7531)
Alarm Code 7531
Cause MG PP CPU usage beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway PP board exceeds level-1 threshold
alarm
Handling method The gateway CPU utilization of PP card exceeds the first level
threshold.
1. Use traffic control to reduce CPU utilization of PP card.
2. Add new PP card hardware or replace the PP card with a higher
prcoessing speed.

46 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

CPU Utilization of Gateway PP Board

Exceeds Level-2 Threshold(7532)
Alarm Code 7532
Cause MG PP CPU usage beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway PP board exceeds level-2 threshold
alarm
Handling method The gateway CPU utilization of PP card exceeds the second level
threshold.
1. Use traffic control to reduce CPU utilization of PP card.
2. Add new PP card hardware or replace the PP card with a higher
prcoessing speed.

CPU Utilization of Gateway PP Board

Exceeds Level-3 Threshold(7533)
Alarm Code 7533
Cause MG PP CPU usage beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway PP board exceeds level-3 threshold
alarm
Handling method The gateway CPU utilization of PP card exceeds the third level
threshold.
1. Use traffic control to reduce CPU utilization of PP card.
2. Add new PP card hardware or replace the PP card with a higher
prcoessing speed.

CPU Utilization of Gateway PP Board

Exceeds Level-4 Threshold(7534)
Alarm Code 7534
Cause MG PP CPU usage beyond threshold 4

Confidential and Proprietary Information of ZTE CORPORATION 47

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway PP board exceeds level-4 threshold
alarm
Handling method The gateway CPU utilization of PP card exceeds the fourth level
threshold.
1. Use traffic control to reduce CPU utilization of PP card.
2. Add new PP card hardware or replace the PP card with a higher
prcoessing speed.

CPU Utilization of Gateway PP Board

Exceeds Level-5 Threshold(7535)
Alarm Code 7535
Cause MG PP CPU usage beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway PP board exceeds level-5 threshold
alarm
Handling method The gateway CPU utilization of PP card exceeds the fifth level
threshold.
1. Use traffic control to reduce CPU utilization of PP card.
2. Add new PP card hardware or replace the PP card with a higher
prcoessing speed.

CPU Utilization of Gateway PP Board

Exceeds Level-6 Threshold(7536)
Alarm Code 7536
Cause MG PP CPU usage beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the CPU utilization of gateway PP board exceeds level-6 threshold
alarm

48 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Handling method The gateway CPU utilization of PP card exceeds the sixth level
threshold.
1. Use traffic control to reduce CPU utilization of PP card.
2. Add new PP card hardware or replace the PP card with a higher
prcoessing speed.

Traffic of Gateway IPI Network

Interface Exceeds Level-1
Threshold(7537)
Alarm Code 7537
Cause MG IPI flux beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Traffic of gateway IPI network interface exceeds level-1 threshold
alarm
Handling method The gateway NIC flux of IPI card exceeds the first level threshold.
1. Use traffic control to reduce NIC flux of IPI card.
2. Replace the IPI card with a greater bandwidth.

Traffic of Gateway IPI Network

Interface Exceeds Level-2
Threshold(7538)
Alarm Code 7538
Cause MG IPI flux beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Traffic of gateway IPI network interface exceeds level-2 threshold
alarm
Handling method The gateway NIC flux of IPI card exceeds the second level thresh-
old.
1. Use traffic control to reduce NIC flux of IPI card.
2. Replace the IPI card with a greater bandwidth.

Confidential and Proprietary Information of ZTE CORPORATION 49

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Traffic of Gateway IPI Network

Interface Exceeds Level-3
Threshold(7539)
Alarm Code 7539
Cause MG IPI flux beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Traffic of gateway IPI network interface exceeds level-3 threshold
alarm
Handling method The gateway NIC flux of IPI card exceeds the third level threshold.
1. Use traffic control to reduce NIC flux of IPI card.
2. Replace the IPI card with a greater bandwidth.

Traffic of Gateway IPI Network

Interface Exceeds Level-4
Threshold(7540)
Alarm Code 7540
Cause MG IPI flux beyond threshold 4
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Traffic of gateway IPI network interface exceeds level-4 threshold
alarm
Handling method The gateway NIC flux of IPI card exceeds the fourth level thresh-
old.
1. Use traffic control to reduce NIC flux of IPI card.
2. Replace the IPI card with a greater bandwidth.

Traffic of Gateway IPI Network

Interface Exceeds Level-5
Threshold(7541)
Alarm Code 7541

50 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Cause MG IPI flux beyond threshold 5

System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Traffic of gateway IPI network interface exceeds level-5 threshold
alarm
Handling method The gateway NIC flux of IPI card exceeds the fifth level threshold.
1. Use traffic control to reduce NIC flux of IPI card.
2. Replace the IPI card with a greater bandwidth.

Traffic of Gateway IPI Network

Interface Exceeds Level-6
Threshold(7542)
Alarm Code 7542
Cause MG IPI flux beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Traffic of gateway IPI network interface exceeds level-6 threshold
alarm
Handling method The gateway NIC flux of IPI card exceeds the sixth level threshold.
1. Use traffic control to reduce NIC flux of IPI card.
2. Replace the IPI card with a greater bandwidth.

Packet Loss Ratio of Gateway IPI

Network Interface Exceeds Level-1
Threshold(7543)
Alarm Code 7543
Cause MG IPI loss beyond threshold 1
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Packet loss ratio of gateway IPI network interface exceeds level-1
alarm threshold

Confidential and Proprietary Information of ZTE CORPORATION 51

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Handling method The gateway NIC package loss ratio of IPI card exceeds the first
level threshold.
1. Contact with the gateway engineers to seek the reason of pack-
age loss.
2. Check if the traffic is too high,use traffic control to reduce the
traffic.

Packet Loss Ratio of Gateway IPI

Network Interface Exceeds Level-2
Threshold(7544)
Alarm Code 7544
Cause MG IPI loss beyond threshold 2
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Packet loss ratio of gateway IPI network interface exceeds level-2
alarm threshold
Handling method The gateway NIC package loss ratio of IPI card exceeds the second
level threshold.
1. Contact with the gateway engineers to seek the reason of pack-
age loss.
2. Check if the traffic is too high,use traffic control to reduce the
traffic.

Packet Loss Ratio of Gateway IPI

Network Interface Exceeds Level-3
Threshold(7545)
Alarm Code 7545
Cause MG IPI loss beyond threshold 3
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Packet loss ratio of gateway IPI network interface exceeds level-3
alarm threshold
Handling method The gateway NIC package loss ratio of IPI card exceeds the third
level threshold.
1. Contact with the gateway engineers to seek the reason of pack-
age loss.

52 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

2. Check if the traffic is too high,use traffic control to reduce the

traffic.

Packet Loss Ratio of Gateway IPI

Network Interface Exceeds Level-4
Threshold(7546)
Alarm Code 7546
Cause MG IPI loss beyond threshold 4
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Packet loss ratio of gateway IPI network interface exceeds level-4
alarm threshold
Handling method The gateway NIC package loss ratio of IPI card exceeds the fourth
level threshold.
1. Contact with the gateway engineers to seek the reason of pack-
age loss.
2. Check if the traffic is too high,use traffic control to reduce the
traffic.

Packet Loss Ratio of Gateway IPI

Network Interface Exceeds Level-5
Threshold(7547)
Alarm Code 7547
Cause MG IPI loss beyond threshold 5
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Packet loss ratio of gateway IPI network interface exceeds level-5
alarm threshold
Handling method The gateway NIC package loss ratio of IPI card exceeds the fifth
level threshold.
1. Contact with the gateway engineers to seek the reason of pack-
age loss.
2. Check if the traffic is too high,use traffic control to reduce the
traffic.

Confidential and Proprietary Information of ZTE CORPORATION 53

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Packet Loss Ratio of Gateway IPI

Network Interface Exceeds Level-6
Threshold(7548)
Alarm Code 7548
Cause MG IPI loss beyond threshold 6
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Packet loss ratio of gateway IPI network interface exceeds level-6
alarm threshold
Handling method The gateway NIC package loss ratio of IPI card exceeds the sixth
level threshold.
1. Contact with the gateway engineers to seek the reason of pack-
age loss.
2. Check if the traffic is too high,use traffic control to reduce the
traffic.

Synchronization-To-Desynchronizat
ion Conversion Failure(7549)
Alarm Code 7549
Cause � The table record is 0;
� The table record is wrong.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Synchronization-to-desynchronization conversion failure
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

Obtaining The Logic Board Number of

Synchronization Record Failed(7550)
Alarm Code 7550

54 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Cause The logic board is offline or the foreground synchronizing other

board is wrong, resulting in the alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Obtaining the logic board number of synchronization record failed
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

MMLReturns Data Area Index

Error(7551)
Alarm Code 7551
Cause The establishment of the data area Index is wrong, resulting in the
alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the MML returns data area Index error
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

This Record Does Not Need to Be

Synchronized Because The Board Is
Offline(7552)
Alarm Code 7552
Cause When synchronizing the data to a certain board, the board is of-
fline.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object

Confidential and Proprietary Information of ZTE CORPORATION 55

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Aftermath of the This record does not need to be synchronized because the board
alarm is offline
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

Handle of The Synchronous Module

Database Becomes Invalid(7553)
Alarm Code 7553
Cause The handle creation of the database is wrong or the handle does
not exist.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Handle of the synchronous module database becomes invalid
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

MMLError Message Is Received by

Synchronous Module(7554)
Alarm Code 7554
Cause Execution of the MML is wrong, resulting in the alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the MML error message is received by synchronous module
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

56 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Foreground MMLModule Times

Out(7555)
Alarm Code 7555
Cause The foreground MML module times out, resulting in the alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Foreground MML module times out
alarm
Handling method Please obtain all files from the specified directory
:$PROJECT_DIR/log and contact the related ZTE technical
experts.

FTP Operation Failure(7556)

Alarm Code 7556
Cause The FTP process is closed or the port is occupied.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the FTP operation failure
alarm
Handling method Run the netstat –an command to check whether the FTP process is
in service.Check the network connection and the FTP configuration
as mentioned in the installation guide.

Unauthorized User Tttempts to Log

in to The System(8448)
Alarm Code 8448
Cause If the number of input errors of the user name or password reaches
three, the system will report the alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object

Confidential and Proprietary Information of ZTE CORPORATION 57

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Aftermath of the Unauthorized user tttempts to log in to the system

alarm
Handling method Check the IP address of the unauthorized login terminal. Record
it and notify the related department and individual to avoid the
unauthorization of the IP address.

Log Alarm([Alarm Code])

Alarm Code 8704
Cause When the write exception of the operation or maintenance log hap-
pens, the alarm is generated.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Log alarm
alarm
Handling method 1. Check whether the log database state is normal.
2. Check whether the log database capacity is oversize.

Log Database Connection

Alarm(8705)
Alarm Code 8705
Cause When the connection state of the background log database
changes, an alarm is generated.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Log database connection alarm
alarm
Handling method 1. Check if the user name and password are changed.
2. If the user name and password have no problem, login the
background database system to reboot the database SSCFG.
3. Check if the oracle database moniter application is normal
4. Check the network service name.
5. In case of server reboot failure,please contact with the ZTE
technical experts.

58 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Usage of Trunk Group Crosses

Upper Threshold(8971)
Alarm Code 8971
Cause Usage of trunk group exceeding upper threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Usage of trunk group crosses upper threshold
alarm
Handling method Seizure ratio of trunk group is high. Adjust trunk, route or add
trunk group to decrease its seizure ratio.

Usage of Trunk Group Crosses

Lower Threshold(8972)
Alarm Code 8972
Cause Usage of trunk group below lower threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Usage of trunk group crosses lower threshold
alarm
Handling method Seizure ratio of trunk group is too low.
1. No handling for normal case.
2. Apply the trunk group circuit to share the load if "seizure ratio
of trunk group is high".

Average Seizure Time of Trunk Group

Crosses Upper Threshold(8973)
Alarm Code 8973
Cause Average of seize time of trunk group exceeding high threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification

Confidential and Proprietary Information of ZTE CORPORATION 59

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Report Background Server

Object
Aftermath of the Average seizure time of trunk group crosses upper threshold
alarm
Handling method Average time occupancy of trunk group is too long, adjust trunk,
route or add trunk group to decrease this average time occupancy.

Average Seizure Time of Trunk Group

Crosses Lower Threshold(8974)
Alarm Code 8974
Cause Average of seize time of trunk group below low threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Average seizure time of trunk group crosses lower threshold
alarm
Handling method Average time occupancy of trunk group is too short.
1. No handling for normal case.
2. Apply the trunk group resource to share the load if "average
time occupancy is too long".

Average Answer Time of Trunk Group

Crosses Upper Threshold(8975)
Alarm Code 8975
Cause Average of answer time of trunk group exceeding high threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Average answer time of trunk group crosses upper threshold
alarm
Handling method Average answer time of the trunk group is too long.
1. Check whether it is caused by big network delay by Ping com-
mand.
2. Adjust trunk, route or add trunk group to decrease this average
answer times.
3. If no fault is found out,notify the peer side and check whether
peer device has some faults.

60 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Average Answer Time of Trunk Group

Crosses Lower Threshold(8976)
Alarm Code 8976
Cause Average of answer time of trunk group below low threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Average answer time of trunk group crosses lower threshold
alarm
Handling method Average answer time of the trunk group is too short.
1. Check whether related configuration is reasonable and adjust
unreasonable configuration.
2. Apply this trunk group resource to share the load if "average
anwser time of trunk group is too long".

Answer/Seizure Ratio of Trunk Group

Crosses Lower Threshold(8977)
Alarm Code 8977
Cause Answer rate of seize of trunk group below low threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Answer/seizure ratio of trunk group crosses lower threshold
alarm
Handling method Answer seizure ratio of the trunk group is too low.
1. Check whether the threshold value is set properly. It’s possible
to lower the threshold of answer time or increase the threshold
of accupancy times to lower this threshold when registering this
task.
2. Consider load sharing when there is trunk group resource in-
sufficiency.
3. No need to handle.

Confidential and Proprietary Information of ZTE CORPORATION 61

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Answer/Call Attempt Ratio of

Trunk Group Crosses Lower
Threshold(8978)
Alarm Code 8978
Cause Answer rate of attempt call of trunk group below low threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Answer/call attempt ratio of trunk group crosses lower threshold
alarm
Handling method Answer seizure ratio of the trunk group is too low.
1. Check whether the threshold value is set properly,broaden the
threshold configured in traffic statistics. It’s possible to in-
crease the threshold of answer time or lower the threshold of
accupancy times to lower this threshold when registering this
task.
2. Consider to add trunk group resource.

Call Attempts of One Circuit of

Trunk Group Crosses Upper
Threshold(8979)
Alarm Code 8979
Cause Attempt call number of one circuit exceeding high threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Call attempts of one circuit of trunk group crosses upper threshold
alarm
Handling method Single-circuit call attempt of the trunk group is too high. It’s pos-
sible to configure more allocatable circuit number to decrease the
call attempt times of single circuit which results in average call at-
tempt of each circuit and enhance the call completion rate.

62 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Seizure Time of One Circuit of

Trunk Group Crosses Upper
Threshold(8980)
Alarm Code 8980
Cause Seize number of one circuit exceeding high threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Seizure time of one circuit of trunk group crosses upper threshold
alarm
Handling method Single-circuit seizure ratio of the trunk group is too high. It’s pos-
sible to configure more allocatable circuit number to decrease the
occupancy of single circuit which results in average call attempt of
each circuit and enhance the call completion rate.

Voice Quality of The Gateway

Exceeds The Threshold(8981)
Alarm Code 8981
Cause Quality of voice over threshold
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Voice quality of the gateway exceeds the threshold
alarm
Handling method 1. Check if the network is normal.
2. Check if the configuration of the traffic control is reasonable.
3. Check the configuration of the Voice quality level.
4. Check the MG configurations of parameters relating to Voice
quality.

Length of Call Info Message Is

Wrong(9013)
Alarm Code 9013
Cause Length of call info message is wrong

Confidential and Proprietary Information of ZTE CORPORATION 63

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Length of call info message is wrong
alarm
Handling method Contact experts for help

Circuit Board State Change

Notification(9217)
Alarm Code 9217
Cause Usually, the circuit board has the following state: power-on, of-
fline, online, active, standby, and faulty. As long as the board
changes from one state to another, an alarm will be reported.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Circuit board state change notification
alarm
Handling method 1. No need to handle if the status of the board changes to the fol-
lowing sequence:“power-on, offline, online, active, standby”.
2. If the status of the board is “faulty” , handle it according to the
prescribed phenomena.

Unreasonable Board/Shelf Number

Received by The Alarm Module(9218)
Alarm Code 9218
Cause The board/shelf number received by the alarm module is unrea-
sonable, resulting in the alarm.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Unreasonable board/shelf number received by the alarm module
alarm
Handling method Please contact the related ZTE technical experts.

64 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Recover SPC Board Based on The

Configuration in Alarm-Manager
Options(9219)
Alarm Code 9219
Cause Recover SPC board based on the configuration in Alarm-Manager
options
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Recover SPC board based on the configuration in ALARM-MANAGER
alarm options
Handling method Not need to handle.

Reset SPC Board Based on The

Configuration in Alarm-Manager
Options(9220)

Alarm Code 9220

Cause Reset SPC board based on the configuration in Alarm-Manager op-
tions
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Reset SPC board based on the configuration in ALARM-MANAGER
alarm options
Handling method Not need to handle.

Notification Database Record

Overflow(9456)

Alarm Code 9456

Cause There are too many notifications recorded in the database. As a
result, the database space is insufficient.

Confidential and Proprietary Information of ZTE CORPORATION 65

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Notification database record overflow
alarm
Handling method Delete the outdated record to release the database space in the
following two ways:
1. At the EMS/GUI interface, delete the earliest 1000 notifications
each time to release the database.
2. If all the notifications can be deleted, log in to sqlplus to run
the truncate table am_notilog command to clear the database.

History Alarm Database Record

Overflow(9457)
Alarm Code 9457
Cause There are too many history alarms recorded in the database. As
a result, the database space is insufficient.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the History alarm database record overflow
alarm
Handling method Delete the outdated record to release the database space in the
following two ways:
1. At the EMS/GUI interface, delete the earliest 1000 history
alarms each time to release the database.
2. If all the history alarms can be deleted, log in to sqlplus to run
the truncate table am_notilog command to clear the database.

Server Reboot Notification(9458)

Alarm Code 9458
Cause The monitoring program reboots the system or it is manually re-
booted.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Server reboot notification
alarm

66 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Handling method 1. Not need to handle if the server is manually rebooted .

2. If the server is rebooted by the monitor program, Please obtain
all files from the specified directory :$PROJECT_DIR/log and
contact the related ZTE technical experts.

Clearing All The Signaling Tracing

Tasks Due to Overhigh CPU
Utilization(9459)
Alarm Code 9459
Cause Because the CPU utilization of SC is overhigh, the system auto-
matically clear all the signaling tracing tasks.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Clearing all the signaling tracing tasks due to overhigh CPU utiliza-
alarm tion
Handling method Normally no need to handle, but if CPU utilization ratio is high for
a long time, handle it according to the related alarm.

SC Startup Succeeds(9470)
Alarm Code 9470
Cause The SC board is successfully started.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the SC startup succeeds
alarm
Handling method Not need to handle.

Disaster Recovery Tcp Link

Re-Building(12846)

Alarm Code 12846

Cause Isaster recovery TCP link re-building

Confidential and Proprietary Information of ZTE CORPORATION 67

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Disaster recovery TCP link re-building
alarm
Handling method 1. Check the link between SS.
2. Check the link status of 6755 port on background machine and
the related remote port configuration.
3. Contact with the related ZTE technical experts .

HLR Inserting User Data Is

Invalid(12847)
Alarm Code 12847
Cause HLR inserting user data is invalid
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the HLR inserting user data is invalid
alarm
Handling method No need to provide because of no usage.

Configured User Data Space Is

Insufficient(12848)
Alarm Code 12848
Cause Configured user data space is insufficient
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Configured user data space is insufficient
alarm
Handling method No need to provide because of no usage.

68 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Map Version Supported by SHLR Is

Earlier Than That of SS(12856)
Alarm Code 12856
Cause MAP version supported by the SHLR is earlier than that supported
by the SS.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the MAP version supported by SHLR Is earlier than that of SS
alarm
Handling method This alarm does not affect the interaction between the SS and
SHLR, does not affect call connection and services. This alarm
is only designed to avoid repeated negotiation and prompt the
maintainers to modify the MAP version configuration on the SS to
make the versions keep consistent with each other. No handling
is mandatory. Or turn to the technical gurus.

Capacity Overflow After Mapping

Disaster Recovery Node(12857)
Alarm Code 12857
Cause Mapping table error
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report Background Server
Object
Aftermath of the Capacity overflow after mapping disaster recovery node
alarm
Handling method Please contact the related ZTE technical experts.

Uni-User Meter Is Reset(13200)

Alarm Code 13200
Cause Single user met table reset
System Style of Charging server
Alarm
Alarm Style notification

Confidential and Proprietary Information of ZTE CORPORATION 69

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Report Charging server

Object
Aftermath of the Uni-user meter is reset
alarm
Handling method Uni-user meter is reset because the value reaches the max. Not
need to handle.

Billing Server Windows Login

Notification(13338)
Alarm Code 13338
Cause When there is the Windows login on the billing server, the notifi-
cation is generated.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server Windows login notification
alarm
Handling method Windows login notification. No need to handle.

Billing Server System User Login

Notification(13339)
Alarm Code 13339
Cause When there is a subscriber login to the billing server, the notifica-
tion is generated.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server system user login notification
alarm
Handling method Check if the login is performed by the authorized subscriber. Usu-
ally no need to handle.

70 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Billing Server Starting Service

Notification(13340)
Alarm Code 13340
Cause This notification is generated when a new service is enabled by the
billing server.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server starting service notification
alarm
Handling method Check if reasonable new service is started. Usually no need to
handle.

Billing Server Windows Port Filtering

Notification(13341)
Alarm Code 13341
Cause This is a notification used when the billing server checking the
Windows port.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server Windows port filtering notification
alarm
Handling method Normal port check of the billing server.No need to handle.

Billing Server System Log

Notification(13342)
Alarm Code 13342
Cause Notification about the system log of the billing server
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object

Confidential and Proprietary Information of ZTE CORPORATION 71

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Aftermath of the Billing server system log notification

alarm
Handling method The billing server normally generates log . No need to handle.

Billing Server Background Login User

Notification(13343)
Alarm Code 13343
Cause The notification appears because there is the subscriber logging in
to the billing server background.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server background login user notification
alarm
Handling method Check if the background login is performed by the authorized sub-
scriber. Usually no need to handle.

Billing Server Network Traffic

Alarm(13344)
Alarm Code 13344
Cause The alarm is triggered by the network monitoring of the billing
server because the network traffic of billing server exceeds the
system default value.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server network traffic alarm
alarm
Handling method 1. Check if the network traffic source of the billing server is a nor-
mal bill upload or the data transmission with the billing center.
No need to handle if this is a normal system operation .
2. In case of an abnormal system operation, check if the invalid
operation is performed by the unauthorized user or else wise.

72 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Billing Server Network Filtering

Alarm(13345)
Alarm Code 13345
Cause The billing server performs the network filtering, and then the net-
work monitor of the billing server triggers the alarm.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server network filtering alarm
alarm
Handling method Check if an abnormal network connection exits. Usually no need
to handle.

Billing Server Exceptional Alarm

Notification(13348)
Alarm Code 13348
Cause This notification is the result of inconsistency of the definition of bill
transfer interface with the alarm code definition of billing server.
System Style of Charging server
Alarm
Alarm Style notification
Alarm Report Charging server
Object
Aftermath of the Billing server exceptional alarm notification
alarm
Handling method Please contact with ZTE experts to make sure if the definitions
of bill transfer interface and the alarm code of billing server are
consistent.

There Are Same Name Files on The

Billing Server(13353)
Alarm Code 13353
Cause On the billing server, copy files under the JFCENTER directory to
under the jftransfer directory. If there are same name files in the
jftransfer directory, the alarm is reported.
System Style of Charging server
Alarm

Confidential and Proprietary Information of ZTE CORPORATION 73

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Style notification

Alarm Report Charging server
Object
Aftermath of the There are same name files on the billing server
alarm
Handling method Log into the billing server, and modify the names of files under the
JFCENTER directory those having same names with files under the
jftransfer directory.

Task Message Processing

Exception(16385)
Alarm Code 16385
Cause When the exception happens in the process of processing the task
message, the board will automatically reset the record logs. View
the logs according to the processing mode.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Task message processing exception
alarm
Handling method Return the board-related log information under the /diskc/ver-
sion/logfile directory on the spot. Contact the technical gurus for
analysis.

Active/Standby Boards
Switchover(16647)
Alarm Code 16647
Cause The running of active board is faulty or active/standby switchover
is performed manually.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Active/standby boards switchover
alarm
Handling method Observe the changeover process, to check if the board runs nor-
mally after the switchover; whether the whole system runs nor-
mally; whether the ongoing call service is interrupted. Usually, no
handling is needed. Contact the technical gurus to find out why
the boards perform switchover.

74 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Board Startup Notification(16648)

Alarm Code 16648
Cause The board is powered on.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Board startup notification
alarm
Handling method Observe the power-on process of the board to check whether it
runs normally. Usually, no handling is needed.

Board Holder Status Notification(16

649)
Alarm Code 16649
Cause Board clap is loose or tighten
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Board holder status notification
alarm
Handling method None

System Clock Is Being Changed on

Purpose(16708)

Alarm Code 16708

Cause Run the MML command 1216 to set the foreground SC clock. At
the end, this notification is presented.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC
Object
Aftermath of the System clock is being changed on purpose
alarm

Confidential and Proprietary Information of ZTE CORPORATION 75

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Handling method Run the MML command 1216 to set the foreground SC clock,
and then view the notification. Running the MML command 1265
can view the changed clock. Usually, no man-made handling is
needed. For more details, refer to Chapter 4 System Control
in the ZXSS10 SS1b SoftSwitch Control Equipment Command
Manual, Operation Support.

Board Reset Notification(16709)

Alarm Code 16709
Cause Card reset notification
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Board reset notification
alarm
Handling method Board reset notification. Not need to handle.

Traffic of The Equipment Exceeds

The System Configuration(16710)

Alarm Code 16710

Cause The traffic is too heavy and exceeds the corresponding processing
capability of the SPC board.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Traffic of the equipment exceeds the system configuration
alarm
Handling method Check whether the equipment related to the IP address abnormally
works and then leads to the consecutive sending of packets. Check
the related equipment or contact the technical gurus for analysis.

Address Clash(16780)
Alarm Code 16780
Cause The IP or MAC address clash leads to the alarm.

76 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Address clash
alarm
Handling method Properly plan the network and modify the IP address that clashes.

Ping Gateway of Nic Does Not

Work(16799)
Alarm Code 16799
Cause The NIC Ping gateway is unreachable.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Ping gateway of NIC does not work
alarm
Handling method In the first place, check whether the configuration is correct. Then,
check the network connection and Ping the configured gateway. If
necessary, delete the old configuration and configure again. Speed
the MAC table aging and then Ping the gateway again to check the
connection.

H248 Inter-Process Communication

Recovery(20491)
Alarm Code 20491
Cause After receiving the message sent by another process, the
process that reports the alarm should judge whether there is the
PH248_TTM_MGCLINKDOWN exception existed. If yes, report the
alarm to resume.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the H248 inter-process communication recovery
alarm
Handling method This is alarm recovery notification. No handling is needed.

Confidential and Proprietary Information of ZTE CORPORATION 77

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

H248 Inter-Process Communication

Failure(20492)
Alarm Code 20492
Cause When the transaction processing process of the H248 module pro-
cesses the request transaction of the terminal,if the frequency of
the Pending timer timeouts exceeds the maximum Pending time-
outs,and the timeout duration is longer than the maximum Pending
duration,it indicates that the communication between the transac-
tion processing process (TTM) and the call control process (CA) of
the H248 module is abnormal, or the processing of the call control
process (CA) or the process itself is abnormal.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the H248 inter-process communication failure
alarm
Handling method As for the H248 inter-process communication fault, check whether
the node of the related great-capacity node that handles the SG
has checked the H248 process. If not, check it and reboot the
corresponding SPC board on a proper time. Contact the technical
gurus for handling.

Ph248 Transaction Re-Transfer

Times Out And No Answer Is
Received From The Gateway(20495)
Alarm Code 20495
Cause The network does not work or the NIC distribution error happens.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the PH248 transaction re-transfer times out and no answer is received
alarm from the gateway
Handling method 1. Confirm whether the gateway is faulty. Run the Ping packet
command to check whether the network has the packet loss
happened. If no packet loss happens, catch the packets with
the packet catching tools to find out which link has problems.
2. If the fault cannot be handled, contact the technical gurus.

78 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Power-on Registration Message of

The Gateway Is Received(20501)
Alarm Code 20501
Cause SS received register message from gateway
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Power-on registration message of the gateway is received
alarm
Handling method Power-on registration message of the gateway is received. MML
may be used to check the status of this gateway . Not need to
handle .

SS Block The Trunk Circuit Because

Mg Return 431 Error Code(20515)
Alarm Code 20515
Cause SS block the trunk circuit because MG Return 431 error code
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS block the trunk circuit because MG Return 431 error code
alarm
Handling method SS blocks the trunk circuit because MG returns error 431.Please
contact with gateway maintainance engineers to handle.

Ph248 Transaction Request Over

Time,Iad No Reply.(20518)
Alarm Code 20518
Cause PH248 transaction request over time,IAD no reply.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object

Confidential and Proprietary Information of ZTE CORPORATION 79

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Aftermath of the PH248 transaction request over time,IAD no reply.

alarm
Handling method 1. Check the network.
2. Check the number of times and the timer of retransmission .
3. Check the IAD terminal.

Ph248 Received Srvchg From Iad

Belonged Other SS(20519)
Alarm Code 20519
Cause PH248 received srvchg from IAD belonged other ss
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the PH248 received srvchg from IAD belonged other ss
alarm
Handling method MML may be used to view the status of this IAD node. Not need
to handle.

Mrs Disaster Recovery

Registration(20741)
Alarm Code 20741
Cause DRSS received register message of MRS
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the MRS disaster recovery registration
alarm
Handling method MML may be used to view the status of this MRS node. Not need
to handle.

UDP Socket Creation Error(20993)

Alarm Code 20993
Cause The system SOCKET is used up or the lower lay support is excep-
tional.

80 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the UDP socket creation error
alarm
Handling method 1. Select Protocol Configuration > SCTP Configuration >
SCTP Link Configuration to check the faulty board. For
more details, refer to the Trunk Configuration section in the
ZXSS10 SS1b SoftSwitch Control Equipment Data Configura-
tion Manual, Trunk.
2. Run the MML command 1211 to reboot the board. For more
details, refer to Chapter 4 System Control in the ZXSS10 SS1b
SoftSwitch Control Equipment Command Manual, Operation
Support.
3. If the error cannot be removed, contact the technical gurus for
further handling.

UDP Socket Binding Error(20994)

Alarm Code 20994
Cause The lower layer OS support is exceptional.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the UDP socket binding error
alarm
Handling method 1. Select Protocol Configuration > SCTP Configuration >
SCTP Link Configuration to check the faulty board. For
more details, refer to the Trunk Configuration section in the
ZXSS10 SS1b SoftSwitch Control Equipment Data Configura-
tion Manual, Trunk.
2. Run the MML command 1211 to reboot the board. For more
details, refer to Chapter 4 System Control in the ZXSS10 SS1b
SoftSwitch Control Equipment Command Manual, Operation
Support.
3. If the error cannot be removed, contact the technical gurus for
further handling.

UDP Socket Is Normal(20995)

Alarm Code 20995
Cause Display the normal alarm code of the system.
System Style of Foreground NE Device Alarm
Alarm

Confidential and Proprietary Information of ZTE CORPORATION 81

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Style notification

Alarm Report SC,SPC
Object
Aftermath of the UDP socket is normal
alarm
Handling method This is a normal notification. No handling is needed.

IP Socket Creation Error(20996)

Alarm Code 20996
Cause The system SOCKET is used up or the lower lay support is excep-
tional.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the IP socket creation error
alarm
Handling method 1. Select Protocol Configuration > SCTP Configuration >
SCTP Link Configuration to check the faulty board. For
more details, refer to the Trunk Configuration section in the
ZXSS10 SS1b SoftSwitch Control Equipment Data Configura-
tion Manual, Trunk.
2. Run the MML command 1211 to reboot the board. For more
details, refer to Chapter 4 System Control in the ZXSS10 SS1b
SoftSwitch Control Equipment Command Manual, Operation
Support.
3. If the error cannot be removed, contact the technical gurus for
further handling.

IP Socket Binding Error(20997)

Alarm Code 20997
Cause The lower layer OS support is exceptional.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the IP socket binding error
alarm
Handling method 1. Select Protocol Configuration > SCTP Configuration >
SCTP Link Configuration to check the faulty board. For
more details, refer to the Trunk Configuration section in the
ZXSS10 SS1b SoftSwitch Control Equipment Data Configura-
tion Manual, Trunk.

82 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

2. Run the MML command 1211 to reboot the board. For more
details, refer to Chapter 4 System Control in the ZXSS10 SS1b
SoftSwitch Control Equipment Command Manual, Operation
Support.
3. If the error cannot be removed, contact the technical gurus for
further handling.

IP Socket Is Normal(20998)
Alarm Code 20998
Cause Display the normal alarm code of the system.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the IP socket is normal
alarm
Handling method This is a normal notification. No handling is needed.

CIC Number Does Not Exist(21249)

Alarm Code 21249
Cause � Under the circumstance that the non-SCCP message is re-
ceived, reading the TID information from the database through
the CIC circuit number failed. As a result, an alarm is reported
to show that the CIC trunk circuit number does not exist.
� Run the MML command 5327 and set the flag bit to 1. Also, as
a result, an alarm is reported to show that the CIC trunk circuit
number does not exist.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the CIC number does not exist
alarm
Handling method Select Service Manage > Trunk Configuration > Trunk Cir-
cuit Configuration to check whether the trunk group circuit is
configured or properly configured. For more details, refer to the
Trunk Configuration section in the ZXSS10 SS1b SoftSwitch Con-
trol Equipment Data Configuration Manual, Trunk.

Confidential and Proprietary Information of ZTE CORPORATION 83

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Office Direction Number Does Not

Exist(21250)
Alarm Code 21250
Cause When receiving the DATA message, reading the office direction
information from the database through the signaling point code in
the DATA message failed. As a result, an alarm is reported to show
that the office direction number does not exist.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Office direction number does not exist
alarm
Handling method Double-click the office direction (CO) icon, and a dialog is dis-
played. Check whether the signaling point code set by the office
direction has problems.

Message Discarding(21251)
Alarm Code 21251
Cause When creating the M3UA message, the buffer used for sending the
message is insufficient.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Message discarding
alarm
Handling method Run the MML command 5316: link number to reboot the corre-
sponding link.

Connection Errors Reach The

Threshold(21259)
Alarm Code 21259
Cause Control and count the packet errors created in the process of pro-
tocol interaction. When the consecutive errors is not less than 255,
or the errors total is not less than 65535, an alarm is reported to
show that the consecutive errors reach the threshold.

84 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Connection errors reach the threshold
alarm
Handling method The protocol packet interaction errors reach the threshold. Run
the MML command 5316: link number to reboot the corresponding
link.

Deletion Operation Is Executed in

Database(21281)
Alarm Code 21281
Cause When the SS receiving M3UA_LINK_DELETE, M3UA_SG_DELETE,
and M3UA_OFFICE_DELETE, the alarm that the database perform-
ing the deletion operation is generated.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Deletion operation is executed in Database
alarm
Handling method The database performs the deletion operation, prompting that a
deletion operation is performed on the table by the database. No
handling is needed.

Invoking Data Interface Failure At

SIP Module Startup(21515)
Alarm Code 21515
Cause Get sip config data is failed
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Invoking data interface failure at SIP module startup
alarm
Handling method Check SIP protocol data configuration refered by the alarm infor-
mation.

Confidential and Proprietary Information of ZTE CORPORATION 85

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

SIP Register Dispatch Fail(21516)

Alarm Code 21516
Cause SIP register dispatch fail
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SIP register dispatch fail
alarm
Handling method Contact experts for help

SIP Register Adduser Fail(21517)

Alarm Code 21517
Cause SIP register adduser fail
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SIP register adduser fail
alarm
Handling method Contact experts for help

SIP Register Deluser Fail(21518)

Alarm Code 21518
Cause SIP register deluser fail
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SIP register deluser fail
alarm
Handling method Contact experts for help

86 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Illegal SDP Alarm(21519)

Alarm Code 21519
Cause Include illegal SDP in message
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Illegal SDP Alarm
alarm
Handling method Check if the SDP syntax in the SIP messages is right.

SS7: Waiting for Block-Acknowledg

ment Times Out(21840)
Alarm Code 21840
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7: Waiting for block-acknowledgment times out
alarm
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

SS7: Waiting for Unblock-Acknowled

gment Times Out(21841)
Alarm Code 21841
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object

Confidential and Proprietary Information of ZTE CORPORATION 87

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Aftermath of the SS7: Waiting for unblock-acknowledgment times out

alarm
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

SS7: Signaling Block Due to Waiting

for Reset-Acknowledgment Times
Out(21842)
Alarm Code 21842
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7: Signaling block due to waiting for reset-acknowledgment
alarm times out
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

SS7: SC Data Area Allocation

Failure(21843)
Alarm Code 21843
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7: SC data area allocation failure
alarm
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

88 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

SS7: Waiting for Gra Times

Out(21844)
Alarm Code 21844
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7: Waiting for GRA times out
alarm
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

SS7 : Waiting for Cgba Times

Out(21845)
Alarm Code 21845
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7 : Waiting for CGBA times out
alarm
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

SS7:Waiting for Cgua Times

Out(21846)
Alarm Code 21846
Cause � Signaling link failure;
� Peer-end circuit configuration error.
System Style of Foreground NE Device Alarm
Alarm

Confidential and Proprietary Information of ZTE CORPORATION 89

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Alarm Style notification

Alarm Report SC,SPC
Object
Aftermath of the SS7:Waiting for CGUA times out
alarm
Handling method Check whether the signaling link works well. If yes, check whether
the peer-end circuit configuration is correct.

SS7: Cg Data Area Allocation

Failure(21847)
Alarm Code 21847
Cause The number of data areas allocated to the PSS7UP CG is insuffi-
cient.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7: CG data area allocation failure
alarm
Handling method Increase the number of data areas allocated to the PSS7UP CG,
and configure it based on the processing board where the TG is
located. Details are as follows:At the GUI, find out the gateway
stack of the TG to check the processing board numbers in the stack
and board configuration. Find out the processing board in the SS
shelf configuration and the gateway stack of the TG in the data
area capacity configuration. Expand the value of maximum SS7
CG data area.

SS7:Call Data Area Allocation

Failure(21848)
Alarm Code 21848
Cause The number of data areas allocated to the PSS7UP call is insuffi-
cient.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7:Call data area allocation failure
alarm
Handling method Increase the number of data areas allocated to the PSS7UP call,
and configure it based on the processing board where the TG is

90 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

located. Details are as follows:At the GUI, find out the gateway
stack of the TG to check the processing board numbers in the stack
and board configuration. Find out the processing board in the SS
shelf configuration and the gateway stack of the TG in the data
area capacity configuration. Expand values of the maximum TG
call data area and the maximum SS7 call data area.

SS7up Unexpected Message(21849)

Alarm Code 21849
Cause Network delay;The peer-end device sends the wrong messages.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7UP unexpected message
alarm
Handling method 1. Check whether the network works well, and whether there is
transmission delay.
2. Check whether the configuration of the peer-end device is cor-
rect.
3. Contact the technical gurus to handle it.

SS7: Reachable Indication of The

Signaling Point of The Data Is
Received(21850)
Alarm Code 21850
Cause The data indicates that the signaling point can receive the message
from the SS.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SS7: Reachable indication of the signaling point of the data is
alarm received
Handling method This is a prompt. No handling is needed.

Confidential and Proprietary Information of ZTE CORPORATION 91

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Unreachable Indication of The

Signaling Point of The Data Is
Received(21853)
Alarm Code 21853
Cause The network connection between the SG and switch is abnormal.Or
the link between the SG and switch does not work due to the fault
of data configuration of the SG and switch.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Unreachable indication of the signaling point of the data is received
alarm
Handling method 1. Run the ping packet command to check whether the hardware
and network connection between the SG and the switch is nor-
mal.
2. View the data configuration of SG and switch to check whether
the switch signaling point code is consistent with that in the
SS.
3. Check the signaling tracing (tracing M3UA).

A Certain Circuit Operation in The

Trunk Group Times Out(21854)
Alarm Code 21854
Cause � Data configuration error;
� Signaling link failure.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the A certain circuit operation in the trunk group times out
alarm
Handling method 1. Check whether there is the circuit state exception happened in
the group. Check the dynamic route table of the corresponding
office direction is null.
2. Check the SG state. Check whether the signaling link is faulty.

92 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Subsystem Congestion(22274)
Alarm Code 22274
Cause The local end does not receive the SSA message from peer sub-
system, or receives the SSC message from peer subsystem.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subsystem congestion
alarm
Handling method Check whether the subsystem numbers of both sides are consis-
tent or whether subsystem No. exists on peer side. Access the
following path to check:Protocol Configuration > SS7 Config-
uration > SS7 GT Conversion Relationship

Subsystem Failure(22275)
Alarm Code 22275
Cause When receiving the connectionless-oriented data, querying the re-
lated local subsystem status from the database encounters return
failure due to subsystem configuration error.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subsystem failure
alarm
Handling method Check whether the subsystem is busy. Check the data configura-
tion of the subsystem. Access the following path to check:Proto-
col Configuration > SS7 Configuration > SS7 GT Conversion
Relationship

Route Hop(22280)
Alarm Code 22280
Cause The Signaling Connection Control Part (SCCP) transfers data in the
connectionless service over the Unit Data (UDT) message. The
Unit Data Service (UDTS) message is used to indicates that the
UDT cannot reach the destination, and then it is found that the
counter hops abnormally when sending segmented UDT message
or UDTS message.

Confidential and Proprietary Information of ZTE CORPORATION 93

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

System Style of Foreground NE Device Alarm

Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Route hop
alarm
Handling method No spot handling is needed. Contact the technical gurus.

Unknown Route(22281)
Alarm Code 22281
Cause When querying the state of the signaling point, the DPC+SSN ad-
dressing mode has no subsystem number, resulting in the routing
failure.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Unknown route
alarm
Handling method 1. Check the configuration by accessing the following path:
Protocol Configuration > SS7 Configuration > SS7 GT
Conversion Relationship. At the interface of the DPC+SSN
mode, add the item of “With Subsystem.”
2. If the alarm continues, check the data interface. Contact the
technical gurus.

Reassembling Timeout(22282)
Alarm Code 22282
Cause When reassembling the SCLC segment message, the data re-
sources space is insufficient or the timer times out.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Reassembling timeout
alarm
Handling method 1. Run the MML command 5304 to check the network state.
2. For the memory resources, In the ZTE Unified Management
System window, first select SS node and then select Opera-
tion > Diagnose Management > Instant Test > Perfor-
mance View > View CPU and Memory.

94 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

3. If there is any exception, reboot the SPC board.

Reassembling Sequence
Error(22283)
Alarm Code 22283
Cause The fault probably lies in the network.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Reassembling sequence error
alarm
Handling method Run the Ping packet to check the network. Check whether the
interface cannot be properly connected or whether the network
equipment is faulty.

No Space for Reassembling(22284)

Alarm Code 22284
Cause The number of segment messages waiting for reassembling con-
currently has reached the threshold.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the No space for reassembling
alarm
Handling method 1. In the SC or SPC processing board, adjust the capacity of the
upper protocol (TCAP, INAP, and so on) to relief the load of the
SCCP module.
2. Select Global Configuration > SoftSwitch Data Configu-
ration > Shelf Configuration and right-click the correspond-
ing SPC board. Select Data Area Capacity Configuration to
modify the data area capacity configuration. For more details,
refer to the Basic Data Configuration section in the ZXSS10
SS1b SoftSwitch Control Equipment Data Configuration Man-
ual, Global Configuration.

Riar Timeout(22285)
Alarm Code 22285

Confidential and Proprietary Information of ZTE CORPORATION 95

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Cause T(iar) expiry

System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the RIAR timeout
alarm
Handling method View the attribute configuration.

Connection Reset(22286)
Alarm Code 22286
Cause SCCP becomes abnormal.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Connection reset
alarm
Handling method Reset the SPC board in which the office direction is located. Usu-
ally, contact the technical gurus for fault handling.

Message Oversize(22287)
Alarm Code 22287
Cause The message sent from the upper layer TCAP to the SCCP is over-
size.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Message oversize
alarm
Handling method Perform the signaling tracing to the TCAP module. Usually, contact
the technical gurus for fault handling.

96 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Connection-Oriented Resource Is
Not Released Completely(22288)
Alarm Code 22288
Cause Error occurs in the resource release program.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Connection-oriented resource is not released completely
alarm
Handling method Reboot the SPC board. If the fault continues, contact the technical
gurus for fault handling.

Section Division Unsupported(22289)

Alarm Code 22289
Cause Segment error: not supported
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Section division unsupported
alarm
Handling method Please contact the related ZTE technical experts.

Section Division Failure(22290)

Alarm Code 22290
Cause Segment error: segment failed
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Section division failure
alarm
Handling method Please contact the related ZTE technical experts.

Confidential and Proprietary Information of ZTE CORPORATION 97

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Reassembling Failure(22291)
Alarm Code 22291
Cause When reassembling the SCLC segment message, the data re-
sources space is insufficient or the timer times out.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Reassembling failure
alarm
Handling method Check why the data resources are occupied and the working state
of the timer. In the ZTE Unified Management System window,
first select SS node and then select Operation > Diagnose Man-
agement > Instant Test > Performance View > View CPU
and Memory.

SCCP Startup on Busy(22293)

Alarm Code 22293
Cause SCCP start unavailing: maintain busy
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SCCP startup on busy
alarm
Handling method Please contact the related ZTE technical experts.

SCCP Startup Congestion(22294)

Alarm Code 22294
Cause SCCP start unavailing: congest
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SCCP startup congestion
alarm
Handling method Please contact the related ZTE technical experts.

98 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

SCCP Stop([Alarm Code])

Alarm Code 22295
Cause SCCP stop unavailing: all reasons
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the SCCP stop
alarm
Handling method Please contact the related ZTE technical experts.

System Error Supported(22296)

Alarm Code 22296
Cause Support system error
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the System error supported
alarm
Handling method The support system is faulty.

Service Syntax Error(22299)

Alarm Code 22299
Cause This error accidentally occurs because the message length exceeds
the specified threshold.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Service syntax error
alarm
Handling method View the signaling tracing and check whether it is an accidental
error. If not, replace the version.

Confidential and Proprietary Information of ZTE CORPORATION 99

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

M3UA Syntax Error(22300)

Alarm Code 22300
Cause This is possible or occasional error. The message length exceeds
the pre-defined value.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the M3UA syntax error
alarm
Handling method View the signaling tracing to check whether it is inevitable. If yes,
replace the version.

Message Decode Error(22301)

Alarm Code 22301
Cause Message Decode error
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Message decode error
alarm
Handling method The message length exceeds the preset value, or the message
contains unknown fields.

Subsystem Prohibition
Started(22302)
Alarm Code 22302
Cause Start subsystem prohibited
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subsystem prohibition started
alarm
Handling method Please contact the related ZTE technical experts.

100 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Subsystem Prohibited
Finished(22303)
Alarm Code 22303
Cause Stop subsystem prohibited
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subsystem prohibited finished
alarm
Handling method Please contact the related ZTE technical experts.

Prohibition Message of The

Subsystem Is Received(22304)
Alarm Code 22304
Cause � The subsystem is faulty;
� The subsystem is cancelled;
� The subsystem is congested.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Prohibition message of the subsystem is received
alarm
Handling method This is a notification. Usually, no handling is needed.

Subsystem Congestion(22305)
Alarm Code 22305
Cause Subsystem congestion
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subsystem congestion
alarm

Confidential and Proprietary Information of ZTE CORPORATION 101

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Handling method Please contact the related ZTE technical experts.

Subsystem Rejection(22306)
Alarm Code 22306
Cause The subsystem sends the service interruption request message is
rejected.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Subsystem rejection
alarm
Handling method Check the state of the subsystem. Run the MML command: 4104:
OFFICEID (office direction ID), SSN1 (start subsystem number),
and SSN2 (end subsystem number) to view whether the state of
the subsystem is normal. If not, contact the technical gurus for
fault handling.

Grant Message Is Received(22307)

Alarm Code 22307
Cause The subsystem service interruption is granted.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Grant message is received
alarm
Handling method Applied to the subsystem management process SCMG, this is a
notification. Usually, no handling is needed.

Permission Message of The

Subsystem Is Received(22308)
Alarm Code 22308
Cause This message is sent after the other subsystem is restored.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification

102 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Alarm Report SC,SPC

Object
Aftermath of the Permission message of the subsystem is received
alarm
Handling method Applied to the subsystem management process SCMG, this is a
notification. Usually, no handling is needed.

Utilization of Connecting Data

Resources Exceeds 80%(22309)
Alarm Code 22309
Cause Too many XUDTS messages exist at the same time. As a result, the
SCOC connecting data resources utilization of the SCCP exceeds
80%. There are too many coexistent XUDTS messages, resulting
in the SCOC connecting data resources utilization of the SCCP ex-
ceeds 80%.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of connecting data resources exceeds 80%
alarm
Handling method Contact the technical gurus for fault handling.

Utilization of Connecting Data

Resources Exceeds 96%(22310)
Alarm Code 22310
Cause Too many XUDTS messages exist at the same time. As a result, the
SCOC connecting data resources utilization of the SCCP exceeds
96%.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of connecting data resources exceeds 96%
alarm
Handling method Contact the technical gurus for fault handling.

Confidential and Proprietary Information of ZTE CORPORATION 103

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Utilization of XUDTS Data Resources

Exceeds 80%(22311)
Alarm Code 22311
Cause The coexistent XUDTS messages are excessive.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of XUDTS data resources exceeds 80%
alarm
Handling method 1. Applied to the SCLC XUDTS message, check the related mem-
ory utilization and find out the process that occupies too much
memory. Then properly allocate the resources and adjust ser-
vice allocation. After the handling, check whether the XUDTS
data resources utilization is reduced and no alarm will happen.
2. For the memory resources, In the ZTE Unified Management
System window, first select SS node and then select Opera-
tion > Diagnose Management > Instant Test > Perfor-
mance View > View CPU and Memory.

Utilization of XUDTS Data Resources

Exceeds 96%(22312)
Alarm Code 22312
Cause The coexistent XUDTS messages are excessive.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of XUDTS data resources exceeds 96%
alarm
Handling method 1. Applied to the SCLC XUDTS message, check the related mem-
ory utilization and find out the process that occupies too much
memory. Then properly allocate the resources and adjust ser-
vice allocation. After the handling, check whether the XUDTS
data resources utilization is reduced and no alarm will happen.
2. For the memory resources, In the ZTE Unified Management
System window, first select SS node and then select Opera-
tion > Diagnose Management > Instant Test > Perfor-
mance View > View CPU and Memory.

104 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Utilization of XUDT Data Resources

Exceeds 96%(22313)
Alarm Code 22313
Cause The coexistent XUDT messages are excessive.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of XUDT data resources exceeds 96%
alarm
Handling method 1. Applied to the SCLC XUDT message, check the related mem-
ory utilization and find out the process that occupies too much
memory. Then properly allocate the resources and adjust ser-
vice allocation. After the handling, check whether the XUDTS
data resources utilization is reduced and no alarm will happen.
2. For the memory resources, In the ZTE Unified Management
System window, first select SS node and then select Opera-
tion > Diagnose Management > Instant Test > Perfor-
mance View > View CPU and Memory.

Utilization of XUDT Data Resources

Exceeds 80%(22314)
Alarm Code 22314
Cause The coexistent XUDT messages are excessive.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of XUDT data resources exceeds 80%
alarm
Handling method 1. Applied to the SCLC XUDT message, check the related mem-
ory utilization and find out the process that occupies too much
memory. Then properly allocate the resources and adjust ser-
vice allocation. After the handling, check whether the XUDTS
data resources utilization is reduced and no alarm will happen.
2. For the memory resources, In the ZTE Unified Management
System window, first select SS node and then select Opera-
tion > Diagnose Management > Instant Test > Perfor-
mance View > View CPU and Memory.

Confidential and Proprietary Information of ZTE CORPORATION 105

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Utilization of Connection Resources

Exceeds 96%(22315)
Alarm Code 22315
Cause Over 245 SCCP users send requests.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of connection resources exceeds 96%
alarm
Handling method Available connection resources are very limited and the transmis-
sion of SCCP user requests must be reduced at once.

Utilization of Connection Resources

Exceeds 80%(22316)
Alarm Code 22316
Cause Over 204 SCCP users send requests.
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Utilization of connection resources exceeds 80%
alarm
Handling method Available connection resources are very limited. It is recom-
mended to reduce the transmission of SCCP user requests.

Registering to GK Failed(22790)
Alarm Code 22790
Cause Register to GK failure. Please check the consistency of register
config information
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Registering to GK failed
alarm

106 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Handling method Contact experts for help

Registering to GK Succeeded(22791)
Alarm Code 22791
Cause Register to GK success
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Registering to GK succeeded
alarm
Handling method Contact experts for help

Unregistered User(22792)
Alarm Code 22792
Cause Unregistered user, User need to register first
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Unregistered user
alarm
Handling method Contact experts for help

Broadband Resources Are

Exhausted(22793)
Alarm Code 22793
Cause Current bandwidth resources overrun. Please increase the config
data of bandwidth resources
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Broadband resources are exhausted
alarm

Confidential and Proprietary Information of ZTE CORPORATION 107

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Handling method Contact experts for help

Call Channel Resources Are

Exhausted(22794)
Alarm Code 22794
Cause Current call channel resources overrun. Please increase the config
data of call channel resources
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Call channel resources are exhausted
alarm
Handling method Contact experts for help

Device Resources Are Exhausted in

Local Zone(22795)
Alarm Code 22795
Cause Current device resources overrun in local zone. Please increase
the config data of device resources in local zone
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Device resources are exhausted in local zone
alarm
Handling method Contact experts for help

Device Resources Are Exhausted in

Adjacent Zone(22796)
Alarm Code 22796
Cause Current device resources overrun in neighbor zone. Please in-
crease the config data of device resources in neighbor zone
System Style of Foreground NE Device Alarm
Alarm

108 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Alarm Style notification

Alarm Report SC,SPC
Object
Aftermath of the Device resources are exhausted in adjacent zone
alarm
Handling method Contact experts for help

Access Table Resources Are

Exhausted(22797)
Alarm Code 22797
Cause Current access table resources overrun in neighbor zone, increase
the config data of access table resources in neighbor zone
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Access table resources are exhausted
alarm
Handling method Contact experts for help

Service Resources Are Exhausted in

Local Zone(22798)
Alarm Code 22798
Cause Service resources are exhausted in local zone. Please increase the
config of service resources in local zone
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Service resources are exhausted in local zone
alarm
Handling method Contact experts for help

Confidential and Proprietary Information of ZTE CORPORATION 109

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

Service Resources Are Exhausted in

Adjacent Zone(22799)
Alarm Code 22799
Cause Service resources are exhausted in neighbor zone. Please increase
the config of service resources in neighbor zone
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Service resources are exhausted in adjacent zone
alarm
Handling method Contact experts for help

Failed to Add Dynamic Configuration

Data(22800)
Alarm Code 22800
Cause Failed to add dynamic configuration data. Please check the validity
of config data
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Failed to add dynamic configuration data
alarm
Handling method Contact experts for help

Failed to Delete Dynamic

Configuration Data(22801)
Alarm Code 22801
Cause Failed to erase dynamic configuration data. Please check the va-
lidity of config data
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object

110 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Notification Information and Relevant Handling

Aftermath of the Failed to delete dynamic configuration data

alarm
Handling method Contact experts for help

Failed to Modify Dynamic

Configuration Data(22802)
Alarm Code 22802
Cause Failed to modify dynamic configuration data. Please check the va-
lidity of configure data
System Style of Foreground NE Device Alarm
Alarm
Alarm Style notification
Alarm Report SC,SPC
Object
Aftermath of the Failed to modify dynamic configuration data
alarm
Handling method Contact experts for help

Confidential and Proprietary Information of ZTE CORPORATION 111

ZXSS10 SS1b Alarm And Notification Handling Manual---Notification

This page is intentionally blank.

112 Confidential and Proprietary Information of ZTE CORPORATION

Tables

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

Table 2 Safety Signs And Their Meanings ............................... 4

Confidential and Proprietary Information of ZTE CORPORATION 113