SJ-20141104150738-014-NetNumen U31 R18 (V12.13.51) Alarm Handling Reference PDF

NetNumen U31 R18
Unified Element Management System

Alarm Handling Reference
Version: V12.13.51
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-11-06 First edition
Serial Number: SJ-20141104150738-014
Publishing Date: 2014-11-06 (R1.0)
SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Alarm Information............................................................................................... 1-1
1.2 Alarm Cause ...................................................................................................... 1-2
1.3 Impact ............................................................................................................... 1-2
1.4 Action ................................................................................................................ 1-2
Chapter 2 Communications Alarms ......................................................... 2-1

2.1 198099803 Link Broken Between OMM and NE ................................................... 2-1
2.2 198099804 Link Broken Between Server and Alarm Box ...................................... 2-2
Chapter 3 QoS Alarm ................................................................................ 3-1

3.1 1513 Performance Index Threshold Crossing....................................................... 3-1
Chapter 4 Equipment Alarm ...................................................................... 4-1

4.1 15010001 Performance Data Delayed ................................................................. 4-1
4.2 15010003 Performance Data Properly Delayed .................................................... 4-2
Chapter 5 OMC Alarms .............................................................................. 5-1

5.1 198099806 Server Hard Disk Fault...................................................................... 5-2
5.2 198099807 Master-to-Slave Database Synchronization Failed .............................. 5-2
5.3 198099808 Link Broken Between Master and Slave Boards.................................. 5-4
5.4 15010002 NAF Performance Data File Delayed ................................................... 5-5
5.5 198099809 Back Card of SBCX Board Offline ...................................................... 5-6
5.6 198099810 Slave SBCX Board Offline ................................................................. 5-6
5.7 1000 User Account Locked ................................................................................. 5-7
5.8 1001 Database Overload .................................................................................... 5-8
5.9 1002 CPU Overload of Application Server............................................................ 5-9
5.10 1003 RAM Overload of Application Server ....................................................... 5-10
5.11 1004 Hard Disk Overload of Application Server .................................................5-11
5.12 1006 File Cleanup Failed ................................................................................ 5-12
5.13 1008 Database Space Threshold Crossing ...................................................... 5-13
5.14 1009 Synchronization Failure of Server Time ................................................... 5-14
5.15 1010 Broken Link Between Server and Alarm Box ............................................ 5-15
5.16 1011 Running Failure of the Whole Database Backup Task ............................... 5-17
5.17 1012 License Has Expired .............................................................................. 5-18
5.18 1013 License Will Expire................................................................................. 5-19

5.19 1014 Broken Link Between Server and NE....................................................... 5-19
5.20 1015 Broken Link Between Server and NE Agent ............................................. 5-20
5.21 1016 Alarm Frequency Threshold Crossing...................................................... 5-21
5.22 1017 Alarm Duration Threshold Crossing ......................................................... 5-22
5.23 1018 Duration Threshold Crossing of Unacknowledged Alarm........................... 5-22
5.24 1019 TRAP Messages Discarded .................................................................... 5-23
5.25 1020 The Number of Log Records Exceeds the Threshold ................................ 5-24
5.26 1021 Running Failure of the Basic Database Backup Task ................................ 5-25
5.27 1022 New Alarm Raised Based on the Alarm Merging Rule .............................. 5-25
5.28 1023 Scheduled Alarm Suppressing Task ........................................................ 5-26
5.29 1024 Broken Link Between Upper-Level EMS and Lower-Level EMS ................ 5-27
5.30 1026 The Number of Alarm Records Exceeds the Threshold............................. 5-27
5.31 1027 The capacity of the PM database has exceeded the threshold .................. 5-28
5.32 1028 Alarm Forwarding Failure........................................................................ 5-29
5.33 1029 Abnormal Alarm Reporting...................................................................... 5-30
5.34 1030 Dual-Server Software Failure .................................................................. 5-31
5.35 1031 Broken Link between the EMS and NMS ................................................. 5-31
5.36 1032 Link Broken Between NMS and License Center ....................................... 5-32
5.37 1034 License Consumption Threshold Crossing ............................................... 5-33
5.38 1037 RAID1 Degradation ................................................................................ 5-34
5.39 1038 Hard Disk S.M.A.R.T Error...................................................................... 5-35
5.40 1039 NE Agent Stops Exceptionally................................................................. 5-35
5.41 1040 EMS Agent Stops Exceptionally .............................................................. 5-36
5.42 1041 Broken FTP Connection to NE Agent ...................................................... 5-38
5.43 1042 Broken FTP Connection to EMS Agent ................................................... 5-39
5.44 1036 Process Exception ................................................................................. 5-39
5.45 1050 Wrong Login Password Entered .............................................................. 5-40
5.46 1053 The Main Process of the EMS System Is Switched to Another
Computer....................................................................................................... 5-41
5.47 1054 Service Model Upgrade Failed ................................................................ 5-41
Glossary .......................................................................................................... I
II

About This Manual
Purpose
This manual provides a reference for alarms related to the network element management
system. For alarms related to a specific Network Element (NE), refer to the corresponding
manual of the NE.
Intended Audience
This manual is intended for:
l Maintenance engineers
l Debugging engineers
What Is in This Manual

This manual contains the following chapters:
Chapter 1, Overview Describes the concepts related to alarm reference

information, including alarm attributes, causes, system
impact, and handling suggestions.
Chapter 2, Communication Alarms Provides a reference for communication alarms related to

the NetNumen U31 system.
Chapter 3, QoS Alarm Provides a reference for the Quality of Service (QoS) alarms
related to the NetNumen U31 system.
Chapter 4, Equipment Alarm Provides a reference for the equipment alarms related to the
NetNumen U31 system.
Chapter 5, OMC Alarms Provides a reference for the Operation and Maintenance
Center (OMC) alarms related to the NetNumen U31 system.
Related Documentation
The following documentation is related to this manual:
NetNumen U31 R18 Unified Element Management System Fault Management Operation
Guide
NetNumen U31 R18 Unified Element Management System Maintenance Management
Operation Guide
Conventions
This manual uses the following conventions.
Typeface Meaning
Italics Variables in commands. It may also refer to other related manuals and documents.

Typeface Meaning
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
Constant Text that you type, program codes, filenames, directory names, and function names.
width
Note: provides additional information about a certain topic.
II

Chapter 1
Overview
The NetNumen U31 system defines each alarm with an alarm code.
This manual only describes the alarms related to the NetNumen U31 system. For alarms
related to specific equipment, refer to the user manuals of the equipment.
This manual describes four aspects of alarms, including alarm information, probable
cause, impact on system, and handling method.
Table of Contents
Alarm Information .......................................................................................................1-1
Alarm Cause ..............................................................................................................1-2
Impact ........................................................................................................................1-2
Action.........................................................................................................................1-2
1.1 Alarm Information

Alarm information includes alarm code, severity, and alarm type.
Alarm Code
Each alarm has a code consisting of a code number and a code name.
l The code number is a unique number containing a maximum of 32 bits.
l The code name briefly describes fault cause and symptom.
Severity
By severity, alarms can be classified into the following four levels.
l Critical Alarm
A critical alarm indicates a fault that causes the system failing to operate or provide
service, and needs to be handled immediately.
l Major Alarm
A major alarm indicates a fault that seriously impacts system operation or reduces the
service capacity, and needs to be handled quickly.
l Minor Alarm
A minor alarm indicates a fault that slightly impacts system operation or reduces the
service capacity, and needs to be handled in time.
l Warning
1-1

NetNumen U31 R18 Alarm Handling Reference
A warning indicates a fault that has a potential impact on the system operation or
service capacity, and needs to be handled on time.
In the NetNumen U31 system, a few alarms are not defined with a severity level. Users
can specify their severity levels.
Alarm Type
l Communications alarm
l Processing error alarm
l Quality of service alarm
l Equipment alarm
l Environmental alarm
l OMC Alarm
l Integrity violation
l Operational violation
l Physical violation
l Security violation
l Time domain violation
1.2 Alarm Cause

The alarm cause of an alarm is the cause that facilitates users to perform fault analysis
and troubleshooting.
1.3 Impact
The impact of an alarm is the impact that an alarm brings on the system and services.
1.4 Action
Action is the method for handing an alarm. If the alarm cannot be handled after following
the method provided in this manual, contact your local ZTE office.
1-2

Chapter 2
Communications Alarms
Table of Contents
198099803 Link Broken Between OMM and NE.........................................................2-1
198099804 Link Broken Between Server and Alarm Box............................................2-2
2.1 198099803 Link Broken Between OMM and NE

Alarm Information
l Code Number: 198099803
l Code Name: Link Broken Between OMM and NE
l Severity: Critical
l Alarm Type: Communication alarm
Alarm Cause
The link between an NE and the OMM server is broken.
Impact
The OMM fails to obtain performance and alarm data from the NE.
Action
1. Locate the NE on the client GUI, and check whether the IP address is correctly
configured, which must be the same as the actual IP address of the NE.
l Yes -> 3.
l No -> 2.
2. Correct the IP address, wait for three minutes, and then check whether the alarm is
cleared.
l Yes -> End.
l No -> 3.
3. Log in to the OMM server, ping the IP address of the NE, and check whether the
communication between the OMM server and the NE is normal.
l Yes -> 5.
l No -> 4.
4. Contact the NE and network maintenance engineers, and ask them to troubleshoot
the fault. After the troubleshooting, check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
2-1

5. Contact the next level of maintenance support.
2.2 198099804 Link Broken Between Server and Alarm

Box
Alarm Information
l Code Name: Link Broken Between Server and Alarm Box
Alarm Causes
The probable causes are as follows:
l The network connection between the EMS server and the alarm box is abnormal.
l The alarm box IP address configured on the EMS server is different from the actual
IP address of the alarm box.
l The EMS server IP address configured in the alarm box is different from the actual IP
address of the server.
l The port number configured in the alarm box is different from that configured on the
EMS server.
Impact
The EMS server fails to send alarm information to the alarm box.
Action
1. In the Fault Management window on the client GUI, open the dialog box containing
the configuration information of the alarm box, and check whether the IP address of
the alarm box is correctly configured.
l Yes -> 3.
l No -> 2.
2. Correct the IP address of the alarm box in the EMS, wait for three minutes, and then
check whether the alarm is cleared.
l Yes -> End.
l No -> 3.
3. On the EMS server, ping the IP address of the alarm box, and check whether the
communication between the server and the alarm box is normal.
l Yes -> 4.
l No -> 7.
4. Check whether the menu screen of the alarm box is properly displayed.
l Yes -> 5.
l No -> 8.
2-2

Chapter 2 Communications Alarms
5. Press the left arrow key on the alarm box to display the version information, and use
an appropriate method to display the server IP address configured in the alarm box
depending on the displayed version:
l If the version is V3 or a previous version, select the appropriate menu on the
screen to display the server IP address.
l If the version is V5, open the terminal window on the EMS server, execute the
command telnet ip address of the alarm box 601 to access the alarm box, enter
the password alarmpro, and then execute the command tcpcfgshow to display the
server IP address.
Check whether the server IP address is correctly set.
l Yes -> 7.
l No -> 6.
6. Correct the server IP address on the alarm box, wait for three minutes, and check
whether the alarm is cleared.
l Yes -> End.
l No -> 7.
7. Verify that the network cable is intact and securely connected to the network port (lan1)
of the alarm box, and check whether the alarm is cleared.
l Yes -> End.
l No -> 9.
8. Restart or replace the alarm box, and check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
2-3

This page intentionally left blank.
2-4

Chapter 3
QoS Alarm
Table of Contents
1513 Performance Index Threshold Crossing .............................................................3-1
3.1 1513 Performance Index Threshold Crossing

NetNumen U31 supports the customization of threshold crossing alarms based on different
Key Performance Indexes (KPIs) for Performance Management (PM). You can predefine
the severity of a threshold-crossing alarm for an index and modify the default handling
method for the alarm.
The following describes the performance index threshold crossing alarm with the default
code number for example.
Alarm Information
l Code Number: 1513
l Code Name: PM threshold cross-border
l Severity: No original level, depending on the threshold and hysteresis of an alarm
level specified by the performance threshold task
l Alarm Type: OMC alarm
Alarm Cause
The value of the counter or KPI exceeds the threshold specified by the performance
threshold task.
Impact
The network management system reports This alarm, which can be viewed on the Alarm
Monitoring tab. Analyze in accordance with the specific service indicated by the monitored
KPI.
Action
1. On the Alarm Monitoring tab, check whether any handling suggestions are provided.
l Yes -> 2.
l No -> 3.
2. Follow the handling suggestions, and then check whether the alarm is cleared.
l Yes -> End.
l No -> 3.
3-1

3. In the Performance -> Threshold Task Management window, check the settings of the
performance threshold task in accordance with the alarm information (Index Name,
Index Value, Task ID), including alarm severity, threshold and oscillation values. Check
whether the settings are consistent with the planning.
l Yes -> 5.
l No -> 4.
4. In the Performance window, modify the threshold and oscillation values of the task.
After a collection period, check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
5. Check the expression of the counter or index in accordance with the alarm information,
and determine whether the service is abnormal in accordance with the current counter
value.
l Yes -> 6.
l No -> 7.
6. Check and analyze the service operation in accordance with the traffic model. After
the service fault is resolved, check whether the alarm is cleared.
l Yes -> End.
l No -> 7.
3-2

Chapter 4
Equipment Alarm
Table of Contents
15010001 Performance Data Delayed........................................................................4-1
15010003 Performance Data Properly Delayed..........................................................4-2
4.1 15010001 Performance Data Delayed

Alarm Information
l Code Name: Performance data delayed
l Severity: Warning
l Alarm Type: Equipment alarm
Alarm Cause
l The link between the EMS and an OMM is broken.
l The link between the EMS server and the database is broken.
l A measurement task is changed.
l The database table spaces used for storing performance data are full.
Impact
The NetNumen U31 system fails to store the collected performance data to the database.
Therefore, the system will report failure after the performance data collected during the
delay period is queried or a performance report involving related data is requested.
Action
1. In the Fault Management window, check whether any "198099803 Link Broken
Between OMM and NE" alarm exists in the active alarm list.
l Yes -> 2.
l No -> 3.
2. Handle the 198099803 alarm in accordance with the corresponding handling
suggestion, and then check whether the “Performance Data Delayed” alarm is
cleared.
l Yes -> End.
l No -> 3.
4-1

3. Query historical alarms raised during the period when the "Performance Data Delayed"
alarm occurs, and check whether any 198099803 alarm exists.
l Yes -> 4.
l No -> 5.
4. In the Performance Management window on the client GUI, query the performance
data integrity, select the corresponding time period in the query results, and initiate a
data re-collection. After the data re-collection is completed, check whether the alarm
is cleared.
l Yes -> End.
l No -> 5.
5. Check whether the granularity time in the alarm details is earlier than the time when
the corresponding measurement task is modified.
l Yes -> Ignore the alarm.
l No -> 6.
6. If the database server and the EMS server are deployed on different hosts, ping
the IP address of the database server on the EMS server, and check whether the
communication between the EMS server and the database server is normal.
l Yes -> 7.
l No -> 8.
7. In the System Monitor window on the client GUI, select the database server node,
and open the dialog box displaying the database resources. Check whether the free
space percentage of each table space related to performance data (meaning each
table space whose name contains "PM") is smaller than five percent.
l Yes -> 9.
l No -> 10.
8. Verify that the network cable between the database server and the EMS server is intact
and securely connected. Check whether the alarm is cleared.
l Yes -> End.
l No -> 10.
9. Contact the next level of database maintenance to enlarge the table spaces. Check
l Yes -> End.
l No -> 10.
4.2 15010003 Performance Data Properly Delayed

Alarm Information
l Code Name: Performance data properly delayed
l Severity: Warning
l Alarm Type: Equipment alarm
4-2

Chapter 4 Equipment Alarm
Alarm Cause
l The link between the OMM and the NE is broken.
l The NE is in commissioning state.
l The NE is in RAT commissioning state.
Impact
The NetNumen U31 system fails to store the collected performance data to the database.
Therefore, the system will report failure after the performance data collected during the
delay period is queried or a performance report involving related data is requested.
Action
1. In the Fault Management window, check whether any "198099803 Link Broken
Between OMM and NE" alarm exists in the active alarm list.
l Yes -> 2.
l No -> 3.
suggestion, and then check whether the “Performance Data Properly Delayed” alarm
is cleared.
l Yes -> End.
l No -> 3.
3. Query historical alarms raised during the period when the "Performance Properly Data
Delayed" alarm occurs, and check whether any 198099803 alarm exists.
l Yes -> 4.
l No -> 5.
4. In the Performance Management window on the client GUI, query the performance
data integrity, select the corresponding time period in the query results, and initiate a
data re-collection. After the data re-collection is completed, check whether the alarm
is cleared.
l Yes -> End.
l No -> 5.
5. In the Topology Management window on the client GUI, check whether the faulty NE
is in commissioning state or in RAT commissioning state.
l Yes -> End.
l No -> 6.
4-3

This page intentionally left blank.
4-4

Chapter 5
OMC Alarms
Table of Contents
198099806 Server Hard Disk Fault.............................................................................5-2
198099807 Master-to-Slave Database Synchronization Failed ...................................5-2
198099808 Link Broken Between Master and Slave Boards.......................................5-4
15010002 NAF Performance Data File Delayed .........................................................5-5
198099809 Back Card of SBCX Board Offline ............................................................5-6
198099810 Slave SBCX Board Offline .......................................................................5-6
1000 User Account Locked ........................................................................................5-7
1001 Database Overload............................................................................................5-8
1002 CPU Overload of Application Server ..................................................................5-9
1003 RAM Overload of Application Server................................................................5-10
1004 Hard Disk Overload of Application Server ........................................................5-11
1006 File Cleanup Failed..........................................................................................5-12
1008 Database Space Threshold Crossing...............................................................5-13
1009 Synchronization Failure of Server Time ...........................................................5-14
1010 Broken Link Between Server and Alarm Box ...................................................5-15
1011 Running Failure of the Whole Database Backup Task ......................................5-17
1012 License Has Expired........................................................................................5-18
1013 License Will Expire ..........................................................................................5-19
1014 Broken Link Between Server and NE...............................................................5-19
1015 Broken Link Between Server and NE Agent.....................................................5-20
1016 Alarm Frequency Threshold Crossing..............................................................5-21
1017 Alarm Duration Threshold Crossing .................................................................5-22
1018 Duration Threshold Crossing of Unacknowledged Alarm .................................5-22
1019 TRAP Messages Discarded.............................................................................5-23
1020 The Number of Log Records Exceeds the Threshold.......................................5-24
1021 Running Failure of the Basic Database Backup Task .......................................5-25
1022 New Alarm Raised Based on the Alarm Merging Rule .....................................5-25
1023 Scheduled Alarm Suppressing Task ................................................................5-26
1024 Broken Link Between Upper-Level EMS and Lower-Level EMS.......................5-27
1026 The Number of Alarm Records Exceeds the Threshold....................................5-27
1027 The capacity of the PM database has exceeded the threshold.........................5-28
1028 Alarm Forwarding Failure ................................................................................5-29
1029 Abnormal Alarm Reporting...............................................................................5-30
1030 Dual-Server Software Failure...........................................................................5-31
1031 Broken Link between the EMS and NMS .........................................................5-31
1032 Link Broken Between NMS and License Center...............................................5-32
1034 License Consumption Threshold Crossing.......................................................5-33
5-1

1037 RAID1 Degradation .........................................................................................5-34

1038 Hard Disk S.M.A.R.T Error...............................................................................5-35
1039 NE Agent Stops Exceptionally .........................................................................5-35
1040 EMS Agent Stops Exceptionally.......................................................................5-36
1041 Broken FTP Connection to NE Agent...............................................................5-38
1042 Broken FTP Connection to EMS Agent ...........................................................5-39
1036 Process Exception...........................................................................................5-39
1050 Wrong Login Password Entered ......................................................................5-40
1053 The Main Process of the EMS System Is Switched to Another Computer ........5-41
1054 Service Model Upgrade Failed.........................................................................5-41
5.1 198099806 Server Hard Disk Fault

Alarm Information
l Code Name: Hard disk fault on server
Alarm Cause
A hard disk of an SBCX board is faulty.
Impact
If another hard disk is available in the system, the alarm has no impact on the system. If
all the other available hard disks are faulty, the OMM cannot operate properly.
Action
Contact the equipment maintenance personnel to replace the faulty hard disk.
5.2 198099807 Master-to-Slave Database

Synchronization Failed
Alarm Information
l Code Name: Master to slave database sync failure
l Severity: Major
Alarm Cause
l The standby board is not present.
5-2

Chapter 5 OMC Alarms
l The link between the active and standby boards is broken.

l The database fails to operate properly.
Impact
l The active/standby switchover may fail due to broken link between active and standby
boards.
l If the alarm is caused by link communication or database problems, the active/standby
switchover may succeed, but the data on the active and standby board may be
inconsistent after the switchover.
Action
1. In the operating system of the standby board, run the script */ums-svr/bin/conso
lemml/status-linux.sh, and check whether the BACKUP, CONSOLE, and FTP
processes are running properly.
l Yes -> 2.
l No -> 10.
2. Execute the ifconfig command to obtain the IP address settings of the active and
standby boards, and then perform the following operations:
l Ping the internal IP address of the standby board on the active board.
l Ping the internal IP address of the active board on the standby board
l Ping the external IP address of the active board on the standby board.
Check whether the communication between the active and standby boards is normal.
l Yes -> 5.
l No -> 3.
3. Check whether the physical connection between the active and standby boards is
loose.
l Yes -> 4.
l No -> 5.
4. Reconnect the connectors to secure the physical connection, and check whether the
alarm is cleared.
l Yes -> End.
l No -> 5.
5. Execute the sqlplus system/password@instance name command to log in to the
database of the standby board as the system user. Check whether the login is
successful.
l Yes -> 6.
l No -> 9.
6. Execute the command select df.tablespace_name "tableSpaceName",totalspace "Tota
lSpace M",freespace "Not Used Space M",round((1-freespace/totalspace)*100,2) "Used
Ratio%" from (select tablespace_name,round(sum(bytes)/1024/1024) totalspace from db
a_data_files group by tablespace_name) df, (select tablespace_name,round(sum(bytes)/1
024/1024) freespace from dba_free_space group by tablespace_name) fs where df.tables
5-3

pace_name=fs.tablespace_name;, and check whether the used ratio of the table space
is close to 100 percent.
l Yes -> 7.
l No -> 8.
7. Contact the next level of database maintenance to enlarge the table space. Check
l Yes -> End.
l No -> 8.
8. Open the terminal window in the operating system of the standby board, execute the
netstat command to display the list of database ports, and check whether the database
port exists.
l Yes -> 10.
l No -> 9.
9. Contact the next level of database maintenance.
5.3 198099808 Link Broken Between Master and Slave

Boards
Alarm Information
l Code Name: Link broken between master and slave
l Severity: Major
Alarm Cause
l The standby board is not present.
l The link between the active and standby boards is broken.
Impact
l The active/standby switchover may fail.
l The data is inconsistent between the active board and the standby board. If the
active/standby switchover succeeds, the data in the EMS is in disorder after the
switchover.
Action
1. In the operating system of the standby board, run the script */ums-svr/bin/conso
lemml/status-linux.sh, and check whether the BACKUP, CONSOLE, and FTP
processes are running properly.
l Yes -> 2.
l No -> 5.
5-4

2. Execute the ifconfig command to obtain the IP address settings of the active and
standby boards, and then perform the following operations:
l Ping the internal IP address of the standby board on the active board.
l Ping the internal IP address of the active board on the standby board
l Ping the external IP address of the active board on the standby board.
Check whether the communication between the active and standby boards is normal.
l Yes -> 5.
l No -> 3.
3. Check whether the physical connection between the active and standby boards is
loose.
l Yes -> 4.
l No -> 5.
4. Reconnect the connectors to secure the physical connection, and check whether the
alarm is cleared.
l Yes -> End.
l No -> 3.
5.4 15010002 NAF Performance Data File Delayed

Alarm Information
l Code Name: Naf Performance Data File Delayed
l Severity: Warning
Alarm Cause
The EMS delays storing the collected performance data into the database during a period.
Impact
The EMS cannot generate the NAF performance data file, and therefore fails to send the
performance data to the NMS that is connected to the EMS over northbound interfaces.
Action
1. In the Fault Management window on the client GUI, check whether any "15010001
Performance Data Delayed" alarm exists in the active alarm list.
l Yes -> 2.
l No -> 3.
suggestion, and then check whether this alarm is cleared.
l Yes -> End.
l No -> 3.
5-5

5.5 198099809 Back Card of SBCX Board Offline

Alarm Information
l Code Name: Back Card of SBCX Board Offline
l Severity: Major
Alarm Cause
l The rear card of an SBCX board is not present.
l The rear card is not securely installed.
l The rear card is faulty.
Impact
The corresponding SBCX board fails to communicate with the other boards.
Action
1. Check whether the rear card of the SBXC board is present.
l Yes -> 3.
l No -> 2.
2. Remove and reinstall the rear card, and check whether the alarm is cleared.
l Yes -> End.
l No -> 3.
3. Replace the rear card, and check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
5.6 198099810 Slave SBCX Board Offline

Alarm Information
l Code Name: Slave SBCX Board Offline
l Severity: Major
5-6

Alarm Cause
l The standby SBCX board is not present.
l The software of the standby SBCX board runs improperly.
l The hardware of the standby SBCX board is faulty.
Impact
The switchover between the active and standby SBCX boards fails.
Action
1. Check whether the standby SBCX board is present.
l Yes -> 2.
l No -> 3.
2. Ask the equipment maintenance personnel to check whether the operating system on
the standby SBCX board stops response, a power failure occurs on the standby SBCX
board, or the log service is abnormally terminated.
l Yes -> 3.
l No -> 4.
3. Ask the equipment maintenance personnel to restart the standby SBCX board, and
then check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
4. Ask the equipment maintenance personnel to replace the standby SBCX board, and
l Yes -> End.
l No -> 5.
5.7 1000 User Account Locked

Alarm Information
l Code Number: 1000
l Code Name: User locked
l Severity: Warning
Alarm Cause
The probable causes of this alarm are as follows:
l Someone deliberately guesses the login password.
l The user is locked because the number of successive wrong passwords exceeds the
threshold.
5-7

Impact
The user cannot log in to the network management system, and the account is locked.
Action
Use the following methods to handle this alarm:
1. Log in to the EMS system as the super user. Query the user's logs about system login,
and check whether someone deliberately guessed the login password, and analyze
whether there is a threat to the network management system safety.
l Yes -> 2.
l No -> 3.
2. Harden the system, for example, by changing the user password to a more
complicated one or restricting the MAC addresses by using which the users accessed
the system. Go to Step 5.
3. Check whether the locked user has forgotten the login password.
l Yes -> 4.
l No -> 5.
4. Reset the user password.
5. Unlock the user.
5.8 1001 Database Overload

Alarm Information
l Code Number: 1001
l Code Name: Hard disk usage of database server overload
l Severity: Major
Alarm Cause
l During the use of the network management system, new data is imported into the
database continuously, and thus the space allocated to the database becomes
insufficient. In this case, the database automatically expands. The disk space used
by the database exceeds the threshold after several times of expansion.
l The threshold is too small.
Impact
If the database occupies a large disk space, and there is no free disk space, data will fail
to be imported and the network management server will be faulty.
Action
1. On the EMS client, select Maintenance > System Monitoring. The System
Monitoring window is displayed.
5-8

2. In the System Monitoring window, select a database node, and click Configure. A
dialog box is displayed. Check whether the value of Usage Threshold in the Total
Database Usage Monitoring area is too small. (Normally, Scale 1: <60 G; Scale 2:
<65 G; Scale 3: <95 G; Scale 4: <160 G; Scale 5: <170 G; Scale 6: <175 G.)
l Yes -> 3.
l No -> 4.
3. Modify the value of Usage Threshold, and check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
4. Select Maintenance > System Backup and Restore. The System Backup and
Restore window is displayed. Back up the logs, alarms and performance data, and
then delete them. Check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
5.9 1002 CPU Overload of Application Server

Alarm Information
l Code Number: 1002
l Code Name: CPU usage of application server overload
l Severity: User-defined
Alarm Cause
l The user-specified threshold is too small.
l Too many application programs irrelative to network management are running on the
server.
l The network management processes are faulty.
Impact
The server performance becomes poor, and the client responds slowly to user operations
or even worst, the client cannot operate properly.
Action
2. In the System Monitoring window, select an application server, and click Configure.
Check whether the values of the CPU thresholds and the Usage Alarm Threshold
parameters are too small. (By default, Threshold (Critical) is 90%, Threshold (Major)
is 85%, Threshold (Minor) is 80%, Threshold (Warning) is 70%, and Usage Alarm
Threshold is 3.)
5-9

l Yes -> 3.
l No -> 4.
3. Modify the CPU thresholds and the value of Usage Alarm Threshold. Check whether
the alarm is cleared.
l Yes -> End.
l No -> 4.
4. Log in to the server as the admin user, and check whether many application programs
irrelative to network management are running.
l Yes -> 5.
l No -> 6.
5. Manually stop the application programs that are not used in accordance with the actual
conditions, and check whether the alarm is cleared.
l Yes -> End.
l No -> 6.
5.10 1003 RAM Overload of Application Server

Alarm Information
l Code Number: 1003
l Code Name: Ram usage of application server overload
Alarm Cause
l The user-specified RAM thresholds and the value of Usage Alarm Threshold are too
small.
l Too many application programs irrelative to network management are running on the
server.
l The network management processes are faulty.
l The server memory is small.
Impact
The server performance becomes poor, and the client responds slowly to user operations,
or even worst situation is that the network management processes may become faulty and
exit.
Action
Check whether the values of the RAM thresholds and the Usage Alarm Threshold
5-10

parameter are too small. (By default, Threshold (Critical) is 90%, Threshold (Major)
is 85%, Threshold (Minor) is 80%, Threshold (Warning) is 70%, and Usage Alarm
Threshold is 2.)
l Yes -> 3.
l No -> 4.
3. Modify the memory thresholds and the value of Usage Alarm Threshold. Check
l Yes -> End.
l No -> 4.
4. Log in to the server as the admin user, and check whether many application programs
irrelative to network management are running.
l Yes -> 5.
l No -> 6.
5. Manually stop the application programs that are not used in accordance with the actual
conditions, and check whether the alarm is cleared.
l Yes -> End.
l No -> 6.
6. Expand the server memory. Contact the next level of maintenance support.
5.11 1004 Hard Disk Overload of Application Server

Alarm Information
l Code Number: 1004
l Code Name: Application server disk-overload
Alarm Cause
l The user-specified threshold percentage or absolute value of used space is too small.
l The free disk space of the server is small or there is no free space.
Impact
When the free disk space of the server is small or there is no free space, the network
management processes cannot generate new files and cannot save data into files, and
thus the network management system operates improperly and network management
functions cannot be used normally.
Action
Use the following methods to handle this alarm:
5-11

Check whether the values of the hard disk thresholds are too small. (By default,
Threshold (Critical) is 90%, Threshold (Major) is 85%, Threshold (Minor) is 80%, and
Threshold (Warning) is 70%.)
l Yes -> 3.
l No -> 4.
3. Modify the HD monitoring thresholds, and check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
4. Select Maintenance > Task Management > Show Timing Task. The Task
Management window is displayed.
5. On the Task Management window, manually execute the task in the File Clean-up
node. Check whether the alarm is cleared.
l Yes -> End.
l No -> 6.
6. Expand the disk space of the application server. Contact the next level of maintenance
support.
5.12 1006 File Cleanup Failed

Alarm Information
l Code Number: 1006
l Code Name: File cleanup failed
l Severity: Major
Alarm Cause
A process of the server occupies the file handle for a long time, so one or more files fail to
be cleaned, and the remaining files in the directory cannot meet the user-specified space
or (and) time threshold.
Impact
If the directory monitoring task fails for several times successively, files may accumulate
in the directory and cannot be cleaned, which causes a waste of disk space and high
disk usage. When the situation becomes worst, the disk space is full, and the network
management processes cannot generate new files and save data into files. As a result,
the network management system operates improperly.
Action
1. Search for the name of the directory monitoring task that is executed unsuccessfully
in accordance with the alarm information.
5-12

2. Select Maintenance > Task Management > Show Timing Task. The Task
Management window is displayed.
3. In the Task Management window, manually execute the directory monitoring task in
the File Clean-up node that failed to be executed. Check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
5.13 1008 Database Space Threshold Crossing

Alarm Information
l Code No.: 1008
l Code Name: Database space usage too large
Alarm Cause
l The percentage or absolute value of used database space exceeds the user-specified
threshold during the server operation.
l The user-specified threshold percentage or absolute value is too small.
Impact
If the percentage or absolute value of used database space is too large, or there is no free
space, data cannot be imported into the database, and thus the network management
system runs improperly.
Action
Use the following method to this alarm:
1. On the client, select Maintenance > System Monitoring. The System Monitoring
window is displayed.
2. In the System Monitoring window, select a database server, and click Configure.
Check whether the threshold values in the Table Space Usage Monitoring list are too
small. (By default, Threshold (Critical) is 90%, Threshold (Major) is 85%, Threshold
(Minor) is 80%, and Threshold (Warning) is 70%.)
l Yes -> 3.
l No -> 4.
3. Modify the value of Usage Threshold, and check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
4. Select Maintenance > System Backup and Restore. The System Backup and
Restore window is displayed. Back up the logs, alarms and performance data, and
then delete them. Check whether the alarm is cleared.
5-13

l Yes -> End.

l No -> 5.
5. Manually expand the table or database space. Contact the next level of maintenance
support.
5.14 1009 Synchronization Failure of Server Time

Alarm Information
l Code Number: 1009
l Code Name: Server clock synchronization failure
l Severity: Warning
Alarm Causes
The probable causes of the time synchronization failure are as follows:
l Time difference between the clock client and the clock source server exceeds the
preset threshold.
l The clock source server configured on the clock client is wrong.
l The clock source server is not started up.
l Network connection fails.
Impact
The current time on the OMM server (clock client) is not synchronized with that on the
clock source server.
Action
Use the following method to handle this alarm:
1. On the clock client, run the ping command to connect to the IP address of the clock
server. Check whether the IP address of the clock server can be pinged successfully.
l Yes -> 4.
l No -> 2.
2. Handle the network connection problem between the clock client and the clock source
server. Check whether the IP address of the clock sever can be pinged successfully.
l Yes -> 3.
l No -> 7.
3. Check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
4. Contact the clock source provider to check whether the clock source service is started.
l Yes -> 6.
l No -> 5.
5-14

5. Ask the clock source provider to start the clock source service, and then check whether
l Yes -> End.
l No -> 6.
6. On the clock client, manually modify the system time to be the same with the time on
the clock source server. Check whether the alarm is cleared.
l Yes -> End.
l No -> 7.
5.15 1010 Broken Link Between Server and Alarm Box

Alarm Information
l Code Number: 1010
l Code Name: The link between the server and the alarm box is broken
Alarm Cause
The probable causes of the broken link between the NetNumen U31 server and the alarm
box are as follows:
l The link between the alarm box and EMS server is faulty.
l The alarm box IP configured on the EMS server is not consistent with that of the alarm
box.
l The alarm box port configured on the EMS server is not consistent with that of the
alarm box.
Impact
No alarm box can be used to prompt the network management maintenance personnel to
handle the faults.
Action
1. On the client, select Fault -> Setting -> Alarm Box Setting. The Alarm Box Setting tab
is displayed. Double click the record corresponding to the alarm box ID. The Alarm
Box dialog box is displayed. View the specified IP address of the alarm box, and then
run the ping alarm box IP command on the server to check whether the IP address
can be pinged.
l Yes -> 8.
l No -> 2.
2. Check whether the power cable of the alarm box is plugged properly.
l Yes -> 4.
5-15

l No -> 3.
3. Plug the power cable and start the alarm box. Check whether the alarm box screen
displays information properly.
l Yes -> 6.
l No -> 5.
4. Restart the alarm box, and then check whether the alarm box screen displays
information properly.
l Yes -> 6.
l No -> 5.
5. Replace the alarm box with a new one. Plug the power cable and start the new alarm
box. Check whether the alarm box screen displays information properly.
l Yes -> 6.
l No -> 5.
6. Check the network connection between the alarm box and the server. Check whether
the position of the network interface Lan1 of the alarm box is correct, and whether the
network cable is plugged properly.
l Yes -> 8.
l No -> 7.
7. Find the correct Lan1 position, and set it again. Replace the network cable, and check
l Yes -> End.
l No -> 8.
8. On the alarm box screen, select Alarm Box IP Setting from the menu, and check
whether the IP address of the alarm box is consistent with that configured on the EMS
server.
l Yes -> 10.
l No -> 9.
9. On the EMS client, open the alarm box rule, and set the IP to be consistent with that
of the alarm box. Check whether the alarm is cleared.
l Yes -> End.
l No -> 10.
10. On the alarm box, press the left navigation key to view the version number. Check
whether the version number is earlier than V3.
l Yes -> 11.
l No -> 13.
11. On the alarm box screen, select Server IP Setting from the menu, and check whether
the IP address of the server is consistent with that configured on the EMS server.
l Yes -> 14.
l No -> 12.
12. Change the server IP configured on the alarm box to the EMS server IP. Check whether
l Yes -> End.
l No -> 14.
5-16

13. Enter the telnet alarm box IP 601 in the operating system command window to access
the alarm box. Enter the password alarmpro and the tcpCfgShow command to check
whether the configured server IP is consistent with the EMS server IP.
l Yes -> 14.
l No -> 15.
14. On the alarm box screen, select Alarm Box Port Setting from the menu, and check
whether the configured port number is consistent with that configured in the alarm box
rule on the EMS server.
l Yes -> 17.
l No -> 16.
15. Set the server IP on the alarm box to the EMS server IP. Check whether the alarm is
cleared.
l Yes -> End.
l No -> 14.
Configuration method:
Enter the telnet alarm box IP 601 command to access the alarm box. Enter the
password alarmpro and the cfgTcpComm serial number server IP port group ID
command.
16. Change the port number of the alarm box to that configured in the alarm box rule on
the EMS server. Check whether the alarm is cleared.
l Yes -> End.
l No -> 17.
5.16 1011 Running Failure of the Whole Database

Backup Task
Alarm Information
l Code Number: 1011
l Code Name: Failed to execute the whole DB structure backup task
l Severity: Major
Alarm Cause
l The system fails to query the database, retrieve definitions of basic tables, or acquire
information about table space or database files.
l The system fails to upload files through FTP.
l The disk space of the network management server is insufficient.
l The system fails to carry out database commands.
5-17

Impact
When a critical error occurs on the database of the EMS system, the database structure
cannot be recovered rapidly.
Action
Contact the next level of maintenance support.
5.17 1012 License Has Expired

Alarm Information
l Code Number: 1012
l Code Name: License is expired
l Severity: Major
Alarm Cause
The temporary license has expired.
Impact
Contents applied in the temporary license may become ineffective. After the applied
contents become effective, authorized contents applied during the validity period will be
withdrawn gradually. Withdrawal is made in the following two modes:
l Under a strict situation, the authorized contents are withdrawn immediately and are
not allowed to be used again.
l Under a non-strict situation, the authorized contents are withdrawn gradually.
Action
1. Get the sequence number of the temporary license from the alarm information, provide
it to the commercial personnel, and inform them of license expiration. The commercial
personnel determine whether to reapply for a temporary license.
l Yes -> 2.
l No -> 3.
2. Re-apply for a new temporary license, and import it into the license center through a
client.
3. Clear the alarm manually and check whether alarms are still reported.
l Yes -> 4.
l No -> End.
5-18

5.18 1013 License Will Expire

Alarm Information
l Code Number: 1013
l Code Name: License is about to expire
l Severity: Major
Probable Cause
The license of the NetNumen U31 system will expire in a short time.
Impact on System
You cannot use the NetNumen U31 system after the license expires.
Handling Method
Contact the system administrator for a new license.
5.19 1014 Broken Link Between Server and NE

Alarm Information
l Code Number: 1014
l Code Name: The link between the server and the NE is broken
Alarm Causes
The probable causes of the broken link between the NetNumen U31 server and an NE are
as follows:
l The link between an NE and the EMS server is broken.
l The NE is faulty, no response returned.
Impact
If the communication link is broken, the NE cannot be managed through the EMS server.
Another possible cause is that the NE is faulty.
Action
1. Check whether the connection between the EMS server and NE is normal. Find the
NE IP address in the configuration management window in accordance with the NE
5-19

name in the alarm information, and then ping the NE IP address on the EMS server.
Check whether the IP address can be pinged.
l Yes -> 2.
l No -> 4.
2. The connection between the EMS server and the NE is normal. The SNMP may have
a communication fault. Check whether the SNMP parameters of the NE are correct in
the configuration management window.
l Yes -> 5.
l No -> 3.
3. Enter the correct SNMP parameters in the configuration management window, and
wait for a polling task period. Check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
4. Restore the connection between the NE and EMS server, and wait for a polling task
period. Check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
5.20 1015 Broken Link Between Server and NE Agent

Alarm Information
l Code Number: 1015
l Code Name: The link between the server and the NE agent is broken
Alarm Causes
l The OMM system is not started up.
l A network fault occurs.
Impact
The EMS system cannot communicate with the OMM system.
Action
1. On the EMS server, ping the IP address of the opposite OMM server. Check whether
it can be pinged successfully.
l Yes -> 3.
l No -> 2.
2. Handle the network fault between the EMS and the OMM, wait for one minute, and
5-20

l Yes -> End.

l No -> 5.
3. Contact maintenance personnel of the lower-level OMM system to check whether the
OMM is started up.
l Yes -> 5.
l No -> 4.
4. Tell maintenance personnel of the lower-level OMM system to restart the OMM, wait
for one minute, and then check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
5.21 1016 Alarm Frequency Threshold Crossing

Alarm Information
l Code Number: 1016
l Code Name: Frequency of warning overload
l Severity: Determined by the severity level of the alarm triggering the alarm
Alarm Cause
The alarm that is generated in accordance with the alarm counting rule is used to prompt
users that alarms generated within the specified period has reached the set reporting
frequency.
Impact
The network management system reports an alarm of this code, which can be viewed on
the Alarm Monitoring tab.
Action
1. In the current alarm table, double click or right click the alarm and select Detail. Check
the Remark parameter to find the original alarm that is not acknowledged after the
specified time. Check whether it is necessary to continue observing the number of
alarms generated by the NE where the original alarm occurs.
l Yes -> End.
l No -> 2.
2. The alarm is cleared automatically when the alarm counting rule is suspended.
5-21

5.22 1017 Alarm Duration Threshold Crossing

Alarm Information
l Code Number: 1017
l Code Name: The time in which the designated alarm remains active has expired
l Severity: Depending on the severity of the original alarm that triggers this alarm
Alarm Cause
The alarm that is generated in accordance with the alarm time rule is used to prompt users
that an alarm is not cleared within the specified time.
Impact
Action
1. In the current alarm table, double click or right click an alarm of this code and select
Detail. Check the Remark parameter to find the original alarm that is not acknowledged
after the specified time. Handle the original alarm in accordance with the handling
suggestions and then clear it. After the original alarm is cleared, check whether this
alarm is automatically cleared.
l Yes > End.
l No > 2.
5.23 1018 Duration Threshold Crossing of

Unacknowledged Alarm
Alarm Information
l Code Number: 1018
l Code Name: The time in which the designated alarm remains unacknowledged has
expired
l Severity: Depending on the severity of the original alarm that triggers this alarm
Alarm Cause
The alarm that is generated in accordance with the alarm time rule is used to prompt users
that an alarm is not acknowledged within the specified time.
5-22

Impact
Action
1. In the current alarm table, double click or right click an alarm of this code and select
Detail. Check the Remark parameter to find the original alarm that is not acknowledged
after the specified time. Handle the original alarm in accordance with the handling
suggestions and then clear it. After the original alarm is cleared, check whether this
alarm is automatically cleared.
l Yes > End.
l No > 2.
5.24 1019 TRAP Messages Discarded

Alarm Information
l Code Number: 1019
l Code Name: Trap receiving speed too fast, some trap messages discarded
l Severity: Major
Alarm Cause
l A fault occurs on the lower-level NE, so it reports a large number of TRAP messages
to the EMS server within a short period.
l The EMS is slow in processing TRAP messages, so TRAP messages are
accumulated on the EMS.
l The size of TRAP message processing queues is not set reasonably on the EMS.
Impact
Some TRAP messages reported by the NE are discarded, so alarms for these TRAP
messages cannot be displayed properly.
Action
1. In the Fault Management window, check whether a large number of alarms are
reported.
l Yes -> 2.
l No -> 3.
5-23

2. Find out the NE that reports these alarms, handle the fault with this NE, and manually
clear the alarm. Check whether alarms are still reported.
l Yes -> 3.
l No -> End.
3. The alarm may be caused because TRAP messages are accumulated on the EMS
due to slow processing of TRAP messages on the EMS, or the size of TRAP message
processing queues is not set reasonably on the EMS. In this case, Contact the next
level of maintenance support.
5.25 1020 The Number of Log Records Exceeds the

Threshold
Alarm Information
l Code Number: 1020
l Code Name: Log records exceeded the threshold
l Severity: Major
Alarm Cause
The log records saved in the database exceeds the current threshold setting.
Impact
l If the free space of the database is sufficient, it does not have great impact.
l If the database space is fully occupied, the new log records cannot be saved into the
database anymore.
Action
1. According to the threshold in the detailed alarm information, check whether the
capacity threshold in the log data backup and deletion task is set properly. (Reference
values: the four threshold levels are 95%, 90%, 85%, and 80% respectively.)
l Yes -> 3.
l No -> 2.
2. Readjust the capacity threshold value in the task.
3. Manually execute the log data backup and deletion task. Or, wait for the system to
automatically run the log data backup and deletion task the next day. Check whether
l Yes -> End.
l No -> 4.
5-24

5.26 1021 Running Failure of the Basic Database

Backup Task
Alarm Information
l Code Number: 1021
l Code Name: Fail to execute the basic database backup task
l Severity: Major
Alarm Cause
l The system fails to query the database, retrieve definitions of basic tables, or acquire
information about table space or database files.
l The system fails to upload files through FTP.
l The disk space on the OMC server is insufficient.
l The system fails to carry out database commands.
Impact
When a critical error occurs on the database of the EMS system, basic data in the system
cannot be recovered rapidly.
Action
5.27 1022 New Alarm Raised Based on the Alarm

Merging Rule
Alarm Information
l Code Number: 1022
l Code Name: Relative alarms arise a new alarm
l Severity: Depending on the severity of the merged alarm
Alarm Cause
The alarm merging rule combines multiple alarms generated by the same fault and displays
only one alarm of this code as a root alarm in the fault management window. Alarms that
meet the rule are hidden as the root correlated alarms.-
Impact
This alarm represents the alarms that meet the merging rule, so those alarms are invisible.
5-25

Action
1. Click the + sign before this alarm to open the Root-Correlated Alarm Tree dialog box.
Handle the correlated alarms in accordance with the handling suggestions. Check
whether this alarm is cleared after all its correlated alarms are cleared.
l Yes -> End.
l No -> 2.
5.28 1023 Scheduled Alarm Suppressing Task

Alarm Information
l Code Number: 1023
l Code Name: Suppress plan task
l Severity: Determined by the suppressed severity level
Alarm Cause
An alarm satisfying task conditions is reported during the validity period of the task.
Impact
Because the alarm suppresses the alarms that satisfy the task conditions, the current
alarms satisfying task conditions are invisible.
Action
1. According to the task name in the Remark parameter in the alarm details, check
whether the device where this task is set is in an engineering cutover or switchover
phase.
l Yes -> 2.
l No -> 3.
2. Wait until the engineering cutover or switchover is ended.
3. Delete the suppression planning task, and check whether the alarm is cleared
automatically.
l Yes -> End.
l No -> 4.
5-26

5.29 1024 Broken Link Between Upper-Level EMS and

Lower-Level EMS
Alarm Information
l Code Number: 1024
l Code Name: The link between the server and the EMS agent is broken.
Alarm Cause
l The EMS agent server is not started up.
l A network fault occurs.
Impact
The EMS system cannot communicate with the EMS agent.
Action
1. On the EMS server, ping the IP address of the opposite EMS agent server. Check
whether it can be pinged successfully.
l Yes -> 3.
l No -> 2.
2. Handle the network fault between the EMS and the EMS agent, wait for one minute,
and then check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
3. Contact maintenance personnel of the EMS agent server to check whether the EMS
agent server is started up.
l Yes -> 5.
l No -> 4.
4. Tell maintenance personnel of the EMS agent server to restart it, wait for one minute,
l Yes -> End.
l No -> 5.
5.30 1026 The Number of Alarm Records Exceeds the

Threshold
Alarm Information
l Code Number: 1026
5-27

l Code Name: The alarm records have exceeded the threshold

l Severity: Major
Alarm Cause
Too many historical alarms or notification records are saved in the database, exceeding
the threshold.
Impact
The alarm does not have great impact if database space is sufficient. However, data cannot
be saved into the database any more if the database space is fully occupied.
Action
1. According to the threshold in the detailed alarm information, check whether the
capacity threshold in the historical data backup and deletion task is set properly.
(Reference values: the four threshold levels are 95%, 90%, 85%, and 80%
respectively.)
Yes -> 3.
No -> 2.
2. Readjust the capacity threshold value in the task.
3. Manually execute the historical data backup and deletion task. Or, wait for the system
to automatically run the log data backup and deletion task the next day. Check whether
l Yes -> End.
l No -> 4.
5.31 1027 The capacity of the PM database has

exceeded the threshold
Alarm Information
l Code Number: 1027
l Code Name: The capacity of the PM database has exceeded the threshold
l Severity: Undefined
Alarm Cause
l The performance database usage thresholds are too low or the database size is too
small.
l The usage of the performance database has exceeded a threshold.
5-28

Impact
l If the unused space on the disk allocated for the performance database (or table
space) is sufficient, there is no serious impact.
l If the disk space is used up, performance data cannot be imported to the database.
Action
1. Check the performance database usage thresholds in the performance data backup
and deletion task. Check whether the thresholds are reasonable (usually, the default
proportions are 95% for critical severity level, 90% for major severity level, 85% for
minor severity level, and 80% for warning severity level).
l Yes -> 3.
l No -> 2.
2. Modify the thresholds, and check whether the alarm is cleared.
l Yes -> End.
l No -> 3.
3. On the client, select Maintenance > Backup & Restore to manually clear
performance data in the network management system. After clearing performance
data, check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
4. If the performance database capacity or disk space on the server needs to be
expanded, contact the next level of maintenance support.
5.32 1028 Alarm Forwarding Failure

Alarm Information
l Code Number: 1028
l Code Name: Alarm Forwarding Failure
l Severity: Major
Alarm Cause
An alarm SM or email fails to be sent.
Impact
Forwarding fails.
Action
If an SM fails to be sent, perform the following steps:
1. Log in to the EMS client, and check whether the telephone number set in the alarm
forwarding rule or on the manual forwarding page is correct.
5-29

l Yes -> 3.
l No -> 2.
2. Modify the telephone number, and check whether the alarm is cleared.
l Yes -> End.
l No -> 3.
3. Check whether the SM forwarding configuration in the configuration center is correct.
l Yes -> 5.
l No -> 4.
4. Modify the telephone number in the configuration center, and check whether the alarm
is cleared.
l Yes -> End.
l No -> 5.
If an email fails to be sent, perform the following steps:
1. Log in to the EMS client, and check whether the email address set in the alarm
forwarding rule or on the manual forwarding page is correct.
l Yes -> 3.
l No -> 2.
2. Modify the email address, and check whether the alarm is cleared.
l Yes -> End.
l No -> 3.
3. Check whether the email forwarding configuration in the configuration center is correct.
l Yes -> 5.
l No -> 4.
4. Modify the email address in the configuration center, and check whether the alarm is
cleared.
l Yes -> End.
l No -> 5.
5.33 1029 Abnormal Alarm Reporting

Alarm Information
l Alarm Code: 1029
l Alarm Name: Abnormal alarm reporting
l Severity: Warning
Alarm Cause
l The primary key where an alarm is reported is blank or over long.
l The NE type where an alarm is reported is blank or does not exist in the OMC.
l The NE where an alarm is reported is blank or does not exist in the OMC.
5-30

l The reported alarm source does not exist in the OMC.
Impact
Abnormal alarms are discarded, and the operator cannot know the related NE faults.
Action
5.34 1030 Dual-Server Software Failure

Alarm Information
l Alarm Code: 1030
l Alarm Name: Dual-server software failure
l Alarm type: OMC alarm
Alarm Cause
Dual-server software is faulty.
Impact
None
Action
5.35 1031 Broken Link between the EMS and NMS

Alarm Information
l Code Number: 1031
l Code Name: NMS disconnection
Alarm Cause
The causes of the broken link between the EMS and the NMS are as follows:
l Network connection between the EMS and the NMS fails.

l The NMS process quits abnormally.
5-31

Impact
The EMS fails to report various messages to the NMS, such as alarms and performance
data.
Action
1. On the EMS server, run the ping command to test whether the IP address of the NMS
can be pinged successfully.
l Yes -> 3.
l No -> 2.
2. Handle the network fault between the EMS and the NMS, check whether this alarm is
cleared.
l Yes -> End.
l No -> 3.
3. Contact maintenance personnel of the NMS to check whether the NMS process quits
abnormally.
l Yes -> 4.
l No -> 7.
4. Check whether the NMS no longer needs to receive any CORBA message from the
EMS.
l Yes -> 5.
l No -> 7.
5. Contact maintenance personnel. On the EMS, delete invalid subscription of CORBA
objects related to the NMS. Clear the alarm manually and check whether alarms are
still reported.
l Yes -> 7.
l No -> End.
6. Contact maintenance personnel of the NMS to start up or restore the NMS. Check
l Yes -> End.
l No -> 7.
5.36 1032 Link Broken Between NMS and License

Center
Alarm Information
l Code Number: 1032
l Code Name: Link breakage between the network management system and the
license center
l Severity: Major
5-32

Alarm Cause
l The license center is shut down.
l Network connection between the network management system and the license center
fails.
Impact
License authorization operations cannot be carried out on the OMM properly.
Action
1. Restart the license server, wait for 15 minutes, and check whether the alarm is cleared.
Yes -> End.
No -> 2.
2. Restart the network management system, wait for 15 minutes, and check whether the
alarm is cleared.
Yes -> End.
No -> 3.
5.37 1034 License Consumption Threshold Crossing

Alarm Information
l Code Number: 1034
l Code Name: License consumption exceeds the alarm threshold.
l Severity: Major
Alarm Cause
The configured value of a numeric-type authorization item has exceeded the authorized
value.
Impact
l Under a non-strict situation, corresponding functions of the authorization item is not
affected. However, the reapplied value cannot exceed the configured value.
l Under a strict situation, the corresponding function of the authorized item cannot
operate properly.
Action
1. The alarm information includes the function item name (or function item ID), authorized
value, and the configured value. Report the alarm information and alarm threshold
5-33

to the commercial personnel, and inform them of the cross-threshold situation. The
commercial personnel decide whether to reapply for a formal license.
l Yes -> 2.
l No -> 3.
2. Make sure that the authorized value of the reapplied formal license satisfies actual
requirements of configuration values, and import the license into the license center.
Check whether the license can be imported successfully.
l Yes -> 5.
l No -> 6.
3. According to service needs, decide whether to reapply for a temporary license.
l Yes -> 4.
l No -> End.
4. Increase the authorized value in the new temporary license. Make sure that the
new authorized value of the reapplied formal license satisfies actual requirements of
configuration values, and import the license into the license center. Check whether
the license can be imported successfully.
l Yes -> 5.
l No -> 6.
5. Clear the alarm manually and check whether alarms are still reported the next day.
l Yes -> 6.
l No -> End.
5.38 1037 RAID1 Degradation

Alarm Information
l Code Number: 1037
l Code Name: RAID1 degradation detected
Alarm Cause
The probable causes of the Redundant Array of Independent Disks (RAID) degradation
are as follows:
l No hard disk exists.

l A hard disk is faulty.
Impact
The faulty hard disk must be replaced with a normal disk for data backup when only one
normal hard disk is available in the RAID1 even no system data loss occurs.
5-34

Action
5.39 1038 Hard Disk S.M.A.R.T Error

Alarm Information
l Code Number: 1038
l Code Name: Hard disk S.M.A.R.T error detected
Alarm Cause
The system detects the S.M.A.R.T fault in a disk.
Impact
The disk with the S.M.A.R.T fault cannot be used and data on the disk will be lost.
Action
5.40 1039 NE Agent Stops Exceptionally

Alarm Information
l Code Number: 1039
l Code Name: The NE agent stops exceptionally
Alarm Cause
l The link between the EMS and the OMM is disconnected.
l Language environments on the upper-level system and the lower-level system are
inconsistent.
l The lower-level OMM is connected into another EMS.
Impact
Communication between the EMS and the OMM fails.
5-35

Action
1. Get the NE agent name from the alarm details, and then query out the EMB port in
the attribute of the corresponding NE agent in the EMS topology window. On the EMS
sever, run the telnet command to connect to the EMB port of the lower-level OMM.
Check whether the EMB port can be connected to successfully.
l Yes -> 3.
l No -> 2.
2. Handle the network fault between the EMS and the OMM, wait for one minute, and
l Yes -> End.
l No -> 3.
OMM is started up.
l Yes -> 5.
l No -> 4.
4. Tell maintenance personnel of the lower-level OMM system to restart the OMM, wait
for one minute, and then check whether the alarm is cleared.
l Yes -> End.
l No -> 5.
5. Check whether languages on the EMS and the OMM are consistent.
l Yes -> 7.
l No -> 6.
6. Adjust language settings on the EMS and the OMM to be the same. Restart the OMM
and the EMS, wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> 7.
OMM is connected to another EMS.
l Yes -> 8.
l No -> 9.
8. Tell maintenance personnel of the lower-level OMM to disconnect it from the other
EMS and connect it to this EMS system. Wait for one minute and check whether the
alarm is cleared.
l Yes -> End.
l No -> 9.
5.41 1040 EMS Agent Stops Exceptionally

Alarm Information
l Code Number: 1040
l Code Name: The EMS agent stops exceptionally
5-36

Alarm Cause
l The link between the EMS and the EMS agent is disconnected.
l Languages on the EMS and the EMS agent are inconsistent.
l The EMS agent is connected into another EMS.
Impact
Communication between the EMS and the EMS agent fails.
Action
1. Get the EMS agent name from the alarm details, and then query out the EMB port in
the attribute of the corresponding EMS agent in the EMS topology window. On the
EMS sever, run the telnet command to connect to the EMB port of the EMS agent.
Check whether the EMB port can be connected to successfully.
l Yes -> 3.
l No -> 2.
2. Handle the network fault between the EMS and the EMS agent, wait for one minute,
l Yes -> End.
l No -> 3.
3. Contact maintenance personnel of the EMS agent server to check whether the EMS
agent server is started up.
l Yes -> 5.
l No -> 4.
4. Tell maintenance personnel of the EMS agent server to restart it, wait for one minute,
l Yes -> End.
l No -> 5.
5. Check whether languages on the EMS and the EMS agent are consistent.
l Yes -> 7.
l No -> 6.
6. Adjust language settings on the EMS and the EMS agent to be the same. Restart the
EMS agent server, wait for one minute, and check whether the alarm is cleared.
l Yes -> End.
l No -> 7.
7. Contact maintenance personnel of the EMS agent to check whether the EMS agent is
connected to another EMS.
l Yes -> 8.
l No -> 9.
8. Tell maintenance personnel of the EMS agent to disconnect it from the other EMS and
connect it to this EMS system. Wait for one minute and check whether the alarm is
cleared.
l Yes -> End.
5-37

l No -> 9.
5.42 1041 Broken FTP Connection to NE Agent

Alarm Information
l Code Number: 1041
l Code Name: The FTP connection with the NE agent is broken
Alarm Cause
The EMS fails to detect the FTP port of the NE agent.
Impact
The EMS fails to perform FTP-related operations.
Action
1. Perform the following steps to check whether the EMS server can connect to the FTP
port on the lower-level OMM properly:
a. In the Alarm Management window, query the name of the NE agent in the alarm
details.
b. In the EMS topology sub-view window, query the corresponding FTP port of the
NE agent.
c. On the EMS server, run the telnet command to connect to the FTP port of the
OMM.
l Yes -> 2.
l No -> 3.
2. Clear the alarm manually and check whether alarms are still reported
l Yes -> 4.
l No -> End.
3. After enabling the FTP service process in the control center on the OMM server, check
l Yes -> End.
l No -> 4.
5-38

5.43 1042 Broken FTP Connection to EMS Agent

Alarm Information
l Code Number: 1042
l Code Name: The FTP connection with the EMS agent is broken
Alarm Cause
The FTP service on the EMS agent is not started up properly.
Impact
FTP-related operations on the EMS cannot be carried out successfully. Service operations
on each module may fail.
Action
1. Perform the following steps to check whether the EMS server can connect to the FTP
port on the EMS agent properly:
a. In the Alarm Management window, query the name of the EMS agent in the alarm
details.
b. In the EMS topology sub-view window, query the corresponding FTP port of the
EMS agent.
c. On the EMS server, run the telnet command to connect to the FTP port of the EMS
agent.
l Yes -> 2.
l No -> 3.
2. Clear the alarm manually and check whether alarms are still reported.
l Yes -> 4.
l No -> End.
3. After enabling the FTP service process in the control center on the EMS agent server,
check whether the alarm is cleared.
l Yes -> End.
l No -> 4.
5.44 1036 Process Exception

Alarm Information
l Code Number: 1036
l Code Name: Process exception alarm
5-39

l Severity: Major
Alarm Cause
l The server process memory is overflowed.
l Threads in the server process exceed the lifetime.
l The operating speed of the server process is slow for a long period.
l The server process quits accidentally.
Impact
OMM functions provided by this process cannot operate properly.
Action
1. In the alarm details, view the name of the abnormal process. Restart this process in
the control center on the OMM server, and check whether the alarm is cleared.
l Yes -> End.
l No -> 2.
5.45 1050 Wrong Login Password Entered

Alarm Information
l Code Number: 1050
l Code Name: Wrong login password
l Severity: Warning
Alarm Cause
The login password entered by the user is wrong.
Impact
The user cannot log in to the network management system.
Action
1. Check whether the user forgets the login password.
l Yes -> 2.
l No -> 3.
2. Reset the user password and notify the user.
3. Clear the alarm manually.
5-40

5.46 1053 The Main Process of the EMS System Is

Switched to Another Computer
Alarm Information
l Code Number: 1053
l Code Name: The main process of the EMS system is switched to another computer
Alarm Cause
l The OMM server is down due to a hardware fault.
l The OMM server stops operating due to an error with its operating system.
l A network error occurs to the OMM server.
l The OMM application process or database stops operating due to an error.
l A switchover operation is carried out manually.
Impact
OMM services fail during the switchover process.
Action
1. Check whether a switchover operation is carried out manually.
l Yes -> 2.
l No -> 4.
2. Check whether OMM services are normal.
l Yes -> 3.
l No -> 4.
3. Manually clear the alarm.
5.47 1054 Service Model Upgrade Failed

Alarm Information
l Code Number: 1054
l Code Name: Service model upgrade failed
l Severity: Major
Alarm Cause
l The service model of OMM type triggered by AMF fails to be upgraded dynamically.
5-41

l The hierarchical service model of OMM type triggered by HMF fails to be upgraded
dynamically.
Impact
The network management functions related to the service model may not be used normally.
Action
5-42

Glossary
EMS
- Element Management System
GUI
- Graphical User Interface
KPI
- Key Performance Indicator
NAF
- Northbound Adapter Function
NE
- Network Element
NMS
- Network Management System
OMC
- Operation & Maintenance Center
OMM
- Operation & Maintenance Module
PM
- Performance Management
QoS
- Quality of Service
RAID
- Redundant Array of Independent Disks
RAT
- Radio Access Technology
SBCX
- X86 Single Board Computer

SJ-20141104150738-014-NetNumen U31 R18 (V12.13.51) Alarm Handling Reference PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20141104150738-014-NetNumen U31 R18 (V12.13.51) Alarm Handling Reference PDF

Uploaded by

Copyright:

Available Formats

NetNumen U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2014-11-06 First edition

Serial Number: SJ-20141104150738-014

Publishing Date: 2014-11-06 (R1.0)

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

Chapter 2 Communications Alarms ......................................................... 2-1

Chapter 3 QoS Alarm ................................................................................ 3-1

Chapter 4 Equipment Alarm ...................................................................... 4-1

Chapter 5 OMC Alarms .............................................................................. 5-1

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Overview Describes the concepts related to alarm reference

Chapter 2, Communication Alarms Provides a reference for communication alarms related to

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

Note: provides additional information about a certain topic.

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

1.1 Alarm Information

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

1.2 Alarm Cause

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

2.1 198099803 Link Broken Between OMM and NE

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5. Contact the next level of maintenance support.

2.2 198099804 Link Broken Between Server and Alarm

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

3.1 1513 Performance Index Threshold Crossing

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

4.1 15010001 Performance Data Delayed

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

4.2 15010003 Performance Data Properly Delayed

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

1037 RAID1 Degradation .........................................................................................5-34

5.1 198099806 Server Hard Disk Fault

5.2 198099807 Master-to-Slave Database

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

l The link between the active and standby boards is broken.

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5.3 198099808 Link Broken Between Master and Slave

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5.4 15010002 NAF Performance Data File Delayed

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

3. Contact the next level of maintenance support.

5.5 198099809 Back Card of SBCX Board Offline

5.6 198099810 Slave SBCX Board Offline

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5.7 1000 User Account Locked

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5.8 1001 Database Overload

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5.9 1002 CPU Overload of Application Server

SJ-20141104150738-014|2014-11-06 (R1.0) ZTE Proprietary and Confidential

5.10 1003 RAM Overload of Application Server