ZXUR 9000 UMTS

Radio Network Controller

Fault Management Description

Version: V4.15.10.20

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: 800@zte.com.cn

LEGAL INFORMATION
Copyright 2016 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

2016-04-30

First edition

Serial Number: SJ-20160328171815-006

Publishing Date: 20160430 (R1.0)

SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Architecture of the Fault Management System...................... 1-1
Chapter 2 Basic Concepts ......................................................................... 2-1
Chapter 3 NE Fault Management .............................................................. 3-1
Chapter 4 EMS Fault Management............................................................ 4-1
4.1 Alarm/Notification Display ................................................................................... 4-2
4.1.1 Alarm Monitoring ...................................................................................... 4-2
4.1.2 Notification Monitoring .............................................................................. 4-2
4.1.3 Active Alarm Query .................................................................................. 4-2
4.1.4 Historical Alarm Query.............................................................................. 4-2
4.1.5 Notification Query..................................................................................... 4-2
4.1.6 Alarm Panel ............................................................................................. 4-3
4.2 Alarm Statistics .................................................................................................. 4-3
4.2.1 Alarm Monitoring by NE ............................................................................ 4-3
4.2.2 Alarm Monitoring by NE Type.................................................................... 4-3
4.2.3 Basic Statistics of Historical Alarms ........................................................... 4-3
4.2.4 Busy-Hour Statistics of Historical Alarms ................................................... 4-4
4.2.5 Statistics of Alarms on VIP/B/C Sites ......................................................... 4-4
4.3 Alarm Task Management .................................................................................... 4-4
4.3.1 Timing Statistic Task Management ............................................................ 4-4
4.3.2 Timing Export Task Management............................................................... 4-4
4.4 Alarm Rule Management .................................................................................... 4-5
4.4.1 Alarm Clearing Rule ................................................................................. 4-5
4.4.2 Alarm Acknowledging Rule ....................................................................... 4-5
4.4.3 Alarm Filtering Rule .................................................................................. 4-5
4.4.4 Alarm Forwarding Rule ............................................................................. 4-5
4.4.5 Alarm Delaying Rule................................................................................. 4-6
4.4.6 Alarm Merging Rule.................................................................................. 4-6
4.4.7 Alarm Counting Rule ................................................................................ 4-6
4.4.8 Alarm Timing Rule.................................................................................... 4-6
4.4.9 Alarm Suppression Rule ........................................................................... 4-7
4.4.10 Alarm Masking Rule ............................................................................... 4-7
4.4.11 Notification Filtering Rule ........................................................................ 4-7
I
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

4.4.12 Alarm Triggering Script Rule.................................................................... 4-7

4.4.13 Intermittent Alarm Setting........................................................................ 4-7
4.5 Alarm Reminding................................................................................................ 4-8
4.5.1 Alarm Box Setting .................................................................................... 4-8
4.5.2 Alarm Forwarding Template Setting ........................................................... 4-8
4.5.3 Alarm Prompting Setting ........................................................................... 4-8
4.5.4 Alarm Sound and Color Setting ................................................................. 4-8
4.6 Alarm Regarding ................................................................................................ 4-9
4.6.1 Severity Regarding Setting ....................................................................... 4-9
4.6.2 Handling Suggestion Setting ..................................................................... 4-9
4.6.3 User-Defined Alarm Code Setting.............................................................. 4-9
4.7 Alarm Synchronization........................................................................................ 4-9
4.8 Alarm Testing ................................................................................................... 4-10

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

II
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

About This Manual

Purpose
This manual describes the fault management and principles of the ZXUR 9000 UMTS
and the EMS, including the architecture of the fault management system, NE fault
management, and EMS fault management.

Intended Audience
This manual is intended for:
l
l

Maintenance engineers
Network supervision engineers

What Is in This Manual

This manual contains the following chapters.
Chapter 1, Architecture of the Fault Manage-

Describes the architecture of the fault management

ment System

system of the ZXUR 9000 UMTS.

Chapter 2, Basic Concepts

Describes the alarm type and severity of the ZXUR

9000 UMTS.

Chapter 3, NE Fault Management

Describes the NE fault management of the ZXUR 9000

UMTS.

Chapter 4, EMS Fault Management

Describes the EMS fault management of the ZXUR

9000 UMTS.

Related Documentation
The following documentation is related to this manual: ZXUR 9000 UMTS Base Station
Controller Alarm and Notification Handling Reference

Conventions
This manual uses the following conventions.
Danger: indicates an imminently hazardous situation. Failure to comply can
result in death or serious injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result
in serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result
in moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.

I
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

This page intentionally left blank.

II
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 1

Architecture of the Fault

Management System
The fault management system can be divided into three layers from bottom to top as
follows:
1. NE operation and management layer: During equipment operation, the alarm
monitoring module on the equipment monitors alarms. If an alarm is raised, the
module reports it to the OMM.
2. Unified element management layer: The OMM converts the alarm messages to a
unified format, and reports them to the EMS.
3. Network management layer: The EMS coverts alarm messages to the required format
in accordance with the northbound-interface specification, and reports them to the
NMS.
Figure 1-1 describes the architecture of the entire system.
Figure 1-1 System Architecture

1-1
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

This page intentionally left blank.

1-2
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 2

Basic Concepts
The ZXUR 9000 UMTS defines the probable causes and handling suggestions for each
alarm. Based on the specifications in 3GPP TS 32.111, alarm triggering conditions, and
impact on the system, with reference of X.721, X.733, X.736, and M3100, equipment
alarms are classified into the following five types:
l

Communication Alarm
Alarms caused by information delivery error, for example, signal loss, frame loss,
frame error, local-end transmission error, remote-end transmission error, call
establishment error, signal fading, transmission subsystem error, communication
protocol error, LAN error, and error on interfaces of data transmission devices.

Processing Alarm
Alarms caused by software or processing error, for example, storage capacity
shortage, version inconsistency, data corruption, over CPU period limit, software
program error, abnormal software program termination, file error, out of memory,
unavailable resource, and configuration error.

QoS Alarm
Alarms caused by QoS decrease, for example, timeout, bandwidth decrease, over
retransmission limit, abnormal relay rate, over threshold, performance decrease,
congestion, and almost the maximum resource usage.

Equipment Alarm
Alarms caused by equipment hardware, for example, power supply, clock, processor,
multiplexer, receiver, transmitter, transmission device, input device, output device,
and adapter.

Environment Alarm
Alarms caused by the environment in which the equipment is operating, for example,
temperature, humidity, heating, ventilation, cooling, fire, water logging, poison,
leakage, pressure, shock, and access control.

ZTE classifies the ZXUR 9000 UMTS alarms into four levels by alarm severity:
l
l
l

Critical: If a critical alarm occurs, the system cannot operate properly or provide
services, and you need to remove the fault immediately.
Major: A major alarm affects the system greatly, the service provision capability
decreases a lot, and you need to remove the fault as soon as possible.
Minor: If a minor alarm occurs, the system can still operate and provide services, but
you should remove the fault in time to avoid an alarm of a higher level.
2-1

SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

Warning: A warning alarm raises potential risks on reliable system operation and
service provision capability. You should remove the fault in time to avoid an alarm
of a higher level.

2-2
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 3

NE Fault Management
Figure 3-1 shows the NE fault management architecture. The alarm flow is as follows:
1. The upper-layer service alarm module sends alarms to the local alarm agent.
2. The local alarm agent sends the alarms to the platform alarm agent.
3. The bottom-layer platform alarm agent gathers the alarms to the platform alarm
manager.
4. The bottom-layer platform alarm manager sends the alarms to the alarm management
module of the OMP.
5. The alarm common module sends the alarms to the OMM.
Figure 3-1 NE Fault Management

3-1
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

This page intentionally left blank.

3-2
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 4

EMS Fault Management

Figure 4-1 shows the EMS fault management architecture. Upon receiving the alarms
reported by the OMM, the EMS handles the alarms in accordance with the rules that you
have created, stores the alarms, and displays the alarms on the client. On the EMS, you
can query, acknowledge, and unacknowledge alarms.
Figure 4-1 EMS Fault Management

Table of Contents
Alarm/Notification Display...........................................................................................4-2
Alarm Statistics ..........................................................................................................4-3
Alarm Task Management............................................................................................4-4
Alarm Rule Management............................................................................................4-5
Alarm Reminding........................................................................................................4-8
Alarm Regarding ........................................................................................................4-9
Alarm Synchronization ...............................................................................................4-9
Alarm Testing ...........................................................................................................4-10

4-1
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

4.1 Alarm/Notification Display

4.1.1 Alarm Monitoring
The Alarm Monitoring tab is used for real-time alarm monitoring. On this tab, alarms
generated by the managed devices and background alarms can be monitored in a
timely manner. You can monitor the active system alarms, know the system operation
situation, and solve problems as soon as possible if faults occur. Active alarms indicate
the unprocessed alarms in a timely manner. After the alarms are cleared, they are not
displayed in the real-time alarm monitoring list but are transferred to the historical alarms.

4.1.2 Notification Monitoring

The Notification Monitoring tab is used for real-time notification monitoring. On this tab,
notifications generated by the managed devices and background alarms can be monitored
in a timely manner.

4.1.3 Active Alarm Query

The Query Active Alarms dialog box is used for you to monitor active alarms in a
timely manner. In this dialog box, active alarms generated by the managed devices and
background alarms can be monitored in a timely manner. This dialog box supports the
same function as that in the sub-window of the Alarm Monitoring tab. You can query for
the active alarms that arose in the last hour, all the active alarms, visible active alarms,
and unacknowledged active alarms.
In the query result, the alarms can be filtered by alarm severity and acknowledge status.
In the Topology Management window, you can query for the active alarms of an NE by
clicking the NE on the NE Tree. The queried alarms are displayed in the alarm tables
under the main window.
This function supports alarm monitoring for the current user only. After the user logs out
of the system, the monitoring alarms are not saved.

4.1.4 Historical Alarm Query

The Query History Alarms dialog box is used for you to monitor historical alarms in a
timely manner. In this dialog box, historical alarms generated by the managed devices
and historical background alarms can be monitored.
In this dialog box, you can query for the cleared alarms in the last day and in the last three
days.

4.1.5 Notification Query

The Query Notifications dialog box is used for you to monitor the notifications generated
by the devices.
4-2
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 EMS Fault Management

In this dialog box, you can query for notifications in the last day and in the last three days.

4.1.6 Alarm Panel

The alarm panel performs statistics on active alarms by alarm severity and
acknowledgement status. Meanwhile, flashed alarm icons provide warning information
for you.

4.2 Alarm Statistics

4.2.1 Alarm Monitoring by NE
The Alarm Monitoring by NE dialog box is used for monitoring the alarms of the managed
NEs. The alarms are displayed in a table for easy query.
The following information is displayed in this dialog box:
l
l

Alarm information consists of the following fields: NE, critical, major, minor, warning,
and total.
Number of alarms and number of unackowledged alarms, for example, "5/6" is
displayed in the critical column of an alarm record, which means that there are six
critical alarms and five of them are unacknowledged.

4.2.2 Alarm Monitoring by NE Type

The Alarm Monitoring by NE Type dialog box is similar to the Alarm Monitoring by
NE dialog box. However, the alarms of the managed NEs are collected by NE type, and
you can check the alarms of specific NE types only. When the number of active alarms
exceeds a threshold, the alarm monitoring table cannot play an expected role. Therefore,
only the number of alarms of NE types is displayed in this dialog box.
The following information is displayed in this view:
1. Alarm information of NE types consists of the following fields: NE type, critical, major,
minor, warning, and total.
2. Number of alarms and number of unackowledged alarms, for example, "5/6" is
displayed in the critical column of an alarm record, which means that there are six
critical alarms and five of them are unacknowledged.

4.2.3 Basic Statistics of Historical Alarms

In the History Alarm Basic Statistics dialog box, historical alarms are collected based
on alarm frequency or average period.
l
l

You can set statistic conditions and collect the satisfied alarms only.
Basic statistics support the following objects: NE, NE type, alarm code, alarm type,
alarm severity, alarm clear time. The clear time may be week, time, or date.
4-3

SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

l
l

You can define a template for basic statistics of historical alarms, and perform
execution, modification, deletion, save, export operations on the template.
You can set the maximum rows of the statistical result, for example, only the first 50
rows are displayed.

4.2.4 Busy-Hour Statistics of Historical Alarms

Busy hours refer to some times when the service is busy in a day. Therefore, alarms
occurred in these busy hours may greatly impact services.
With busy-hour statistics, you can collect the historical alarms during busy hours only.
Similar to basic statistics, you can set the alarm frequency and average period.
You can set statistic conditions and collect the satisfied alarms only.
You can set the maximum rows of the statistical result, for example, only the first 50 rows
are displayed.
You can define a template for basic statistics of historical alarms, and perform execution,
modification, deletion, save, export operations on the template.

4.2.5 Statistics of Alarms on VIP/B/C Sites

The number of alarms in each severity and the number of all active alarms of each VIP/B/C
site in periods can be counted in this view, for example, active alarms in the last one hour,
two to three hours, three to four hours, four to five hours, and earlier than five hours.
Both the number of alarms and alarm details are displayed. The statistical result can be
dynamically refreshed per two minutes or less.

4.3 Alarm Task Management

4.3.1 Timing Statistic Task Management
You can specify a task to execute a statistic template and export the result to a designated
directory.
To set a timing statistic task, you can select any statistic template or define a statistic
template.

4.3.2 Timing Export Task Management

Active or historical alarms can be filtered by specified conditions in a specified time and
be exported to files. You can add, delete, modify, and query for a timing export task.
A timing export task supports the following execution plans:
l
l
l

By day: The task is executed by default at 5:00 every day.

By week: The task is executed by default at 5:00 every Monday.
By month: The task is executed by default at 5:00 of the first day in every month.
4-4

SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 EMS Fault Management

l
l

By period: The task is executed by default every one hour.

Self-defined: You set the execution time.

The exported files support four formats: CSV, XML, XLS, and TXT.

4.4 Alarm Rule Management

In the Rule Setting view, you can set rules for different types of alarms and notifications.
The rules include: alarm clearing rule, alarm acknowledging rule, alarm filtering rule,
alarm forwarding rule, alarm delay rule, alarm merging rule, alarm counting rule, alarm
suppression rule, alarm masking rule, and notification filtering rule. Rules can simplify
user operations and improve the user efficiency of checking, analyzing, and handling
alarms generated by NEs and background alarms. You can set the rules as required.

4.4.1 Alarm Clearing Rule

The alarm clearing rule is a rule to automatically clear alarms in accordance with the set
conditions. When alarms are raised, if the clearing conditions are satisfied, the clearing
rule clears these alarms.

4.4.2 Alarm Acknowledging Rule

The alarm acknowledging rule is a rule to automatically acknowledge alarms in accordance
with the set conditions. When alarms are raised, if the acknowledging conditions are
satisfied, the acknowledging rule acknowledges these alarms.

4.4.3 Alarm Filtering Rule

The alarm filtering rule is a rule to automatically filter alarms in accordance with the set
conditions. When alarms are raised, if the filtering conditions are satisfied, the filtering rule
filters these alarms. Two filtering methods: display filtering and suppression filtering. The
alarms handled by display filtering are not displayed on the GUI. The alarms handled by
suppression filtering are neither displayed on the GUI nor saved in the database.

4.4.4 Alarm Forwarding Rule

When the satisfied alarms are raised or the alarms are not cleared for a time, the system
sends an E-mail or SMS to specified staff. Similar to other rules, you need to set a rule
name, description, and alarm forwarding conditions. The forwarding conditions include
alarm location, alarm code, and others (for example, raised time, alarm type, and severity).
In addition, you need to set the E-mail address or phone number, forward type, and forward
days or hours.

4-5
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

4.4.5 Alarm Delaying Rule

When the network is being tested or the network quality is not stable, some alarms are
reported, cleared quickly, but reported again in a short time. Such flashing alarms are not
critical alarms in most cases, but lots of them in the real-time alarm monitoring window
may make critical alarms obscure.
An alarm is not reported if it is cleared in a specified time. The alarm is reported only
when it is not cleared in a specified time. The number of alarms in the real-time monitoring
window is reduced.
The rules are only valid for those alarms reported after the rules are set.

4.4.6 Alarm Merging Rule

In some cases, a device may report multiple alarms indicating the same fault. Alarm
merging rules can merge the satisfied alarms into one, and only the first alarm is displayed
on the GUI.
The rules are only valid for those alarms reported after the rules are set.

4.4.7 Alarm Counting Rule

The system samples the frequency of reported alarms, and check whether the number of
times that an alarm is reported in a specified period before the sampling point is greater
than a threshold. If yes, a counting alarm is raised. For a new counting alarm, you can
specify detailed information and severity.
After an alarm counting rule is set, the system starts sampling the alarm report frequency
after the first satisfied alarm is raised. If the number of times that the alarm is raised
exceeds the threshold, the system automatically generates a counting alarm. The counting
alarm uses the severity and detailed information defined by you. In one period, only one
counting alarm can be raised. In the next period, the previous counting alarm is cleared
first, and a new counting alarm is raised. The counting alarm information is updated in one
period only. When a period expires, the counting alarm is cleared no matter whether the
conditions are satisfied or not. In the next period, whether a counting alarm is raised or
not is based on the conditions.
The rules are only valid for those alarms reported after the rules are set.

4.4.8 Alarm Timing Rule

The system times the duration of satisfied alarms in accordance with conditions. If the
time is longer than a threshold, specified operations are performed. The severity level is
increased or a new alarm is raised.
After an alarm timing rule is set, the system times the specified alarm state when a satisfied
alarm is raised. If the duration of the alarm state is longer than the specified time, the
predefined operations are performed.
4-6
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 EMS Fault Management

The rules are only valid for those alarms reported after the rules are set.

4.4.9 Alarm Suppression Rule

The alarm that satisfies the specified conditions suppresses other alarms.
The
suppressing alarm is called primary alarm, and the suppressed alarm is called secondary
alarm. As long as a primary alarm is raised, secondary alarms are not reported no matter
whether they are raised before or after the primary alarm. Alarm suppression rule by
NE can suppress the alarms of different NEs. Alarm suppression rule by NE type can
suppress the alarms of NEs in the same NE type and the NEs are correlated (for example,
some NEs are child NEs of others).

4.4.10 Alarm Masking Rule

The satisfied alarms are masked. To reduce alarms being reported and save bandwidth,
alarm masking rules are sent to the source where alarms are raised. The reported alarms
can be masked by NE, alarm code, and severity. The result of alarm masking is the same
as that of alarm suppression. However, the NE agent discards alarms when alarm masking
rules are used, but the EMS discards alarms when alarm suppression rules are used.
Masked alarms do not occupy bandwidth, but suppressed alarms do. Alarm masking rules
must be supported by devices. Only the NE agent and NEs managed by the NE agent
support alarm masking rules.

4.4.11 Notification Filtering Rule

The notification filtering rule is a rule to automatically filter notifications in accordance with
the set conditions. When notifications are reported, if the filtering conditions are satisfied,
the filtering rule filters these notifications. The filtered notifications are neither displayed
on the GUI nor saved in the database.

4.4.12 Alarm Triggering Script Rule

The system times the alarm duration when the conditions are satisfied. If the duration is
longer than a threshold, a specified MML script is executed.
After an alarm triggering script is set, the system times the alarm duration when the
conditions are satisfied. If the alarm duration is longer than the threshold, the system
executes the specified MML script.

4.4.13 Intermittent Alarm Setting

Multiple alarms with the same NE and alarm code are merged into one alarm so that you
can easily check the alarm.
In the Intermittent Alarm Setting dialog box, you can set the following:
l
l

Activating or suspending the intermittent alarm rule.

Setting the conditions for intermittent alarms.
4-7

SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

4.5 Alarm Reminding

4.5.1 Alarm Box Setting
On the Alarm Box Setting tab, you can set an alarm box. With the alarm box, alarms can
be presented by more methods such as sounds and lights. You can set alarms in different
severities and locations into an alarm box. The alarm box indicates that alarms are raised
when the conditions are satisfied.

4.5.2 Alarm Forwarding Template Setting

In the Alarm Forwarding Template Setting dialog box, you can set the information
template in which the system sends alarms to maintenance staff through an E-mail or an
SMS. You can define the template as required.
The Alarm Forwarding Template Setting dialog box is described as follows:
l

Three areas:

SMS template: sets the SMS template for alarm transmission.

Mail subject: sets the mail subject template for alarm transmission.

Mail content: sets the mail content template for alarm transmission.

Two buttons in each area:

Verify: verifies that the template conforms to the specification and format.

Default: restores the settings to the default values.

4.5.3 Alarm Prompting Setting

To facilitate system management, each maintenance staff is allowed to customize his or
her critical alarms. When these alarms are raised or the alarm status is changed, the
system prompts specially for them.

4.5.4 Alarm Sound and Color Setting

The alarm sound and color setting dialog box is used to define the sounds or colors by
alarm severity and color.
l

Alarm sound setting:

Alarm sound setting: sets different sound files for alarm severities as required.

Sound mode: sets the sound mode (short sound or continuous sound) and
whether to make a sound when a new alarm is raised or an alarm is cleared.

Restore to the default: sets the alarm sound to the default value (mute state).

Alarm color setting

4-8
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 EMS Fault Management

Sets different colors for the five alarm severities: critical, major, minor, warning,
and cleared.

Sets the alarm severity colors to the default values.

4.6 Alarm Regarding

4.6.1 Severity Regarding Setting
On the Severity Regarding Setting tab, you can define alarm severities. For different
service requirements and operation environment, different alarm severities are defined so
that you can focus in some special alarms. In addition, alarm severities can be defined by
NE, element, or NE type.

4.6.2 Handling Suggestion Setting

The Handling Suggestion Setting tab provides alarm causes, diagnosis methods, and
handling suggestions. You can modify these contents based on experience and service
requirements to make alarms friendly and improve the analysis efficiency.
You can modify, import, and export handling suggestions.

4.6.3 User-Defined Alarm Code Setting

On this tab, you can set the name of an alarm code, and define the severity of the alarm
code. In most cases, dry-contact alarms are set on this tab.

4.7 Alarm Synchronization

Alarm synchronization can ensure that the alarms displayed on the upper-level and
lower-level network management systems are the same. Due to complicated network
architecture, transmission problems, and delay, the alarms displayed on different network
management systems may be different. To ensure that the alarms are correctly displayed
on all the network management systems in a timely manner for maintenance personnel,
alarms must be synchronized.
You can synchronize alarms in either of the following ways:
l
l

Right-click an NE and select Synchronize Active Alarms from the shortcut menu.
The alarms of this NE are synchronized.
Select Fault > Synchronize Active Alarms. The Synchronize Active Alarms dialog
box is displayed. Select NEs from the left NE tree, and add them to the list in the right
pane. Click OK. The alarms are synchronized.

Except manual synchronization, the system starts alarm synchronization to the lower-level
OMM after the communication link between them is restored. Scheduled synchronization
is also supported. The scheduled synchronization period can be set. By default, the period
is six hours.
4-9
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

ZXUR 9000 UMTS Fault Management Description

4.8 Alarm Testing

When devices are in engineering installation, commissioning, or cut-over state, the alarm
testing function is used to avoid lots of alarms reported to the EMS. The EMS supports
four alarm handling strategies:
l
l
l
l

The EMS neither receives testing alarms nor reports alarms to the northbound
interface.
The EMS receives testing alarms but does not store them, and does not report alarms
to the northbound interface. The active testing alarms can be queried.
The EMS receives testing alarms, stores them, and reports them to the northbound
interface. The active and historical testing alarms can be queried.
The EMS receives testing alarms and stores them, but does not report alarms to the
northbound interface. The active and historical testing alarms can be queried.

By default, the first strategy is used, which means that testing alarms are discarded.
Strategies can be selected for different scenarios.

4-10
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential

Glossary
CPU
- Central Processing Unit
EMS
- Element Management System
GUI
- Graphical User Interface
MML
- Man Machine Language
NMS
- Network Management System
OMM
- Operation & Maintenance Module
OMP
- Operation & Maintenance Processor
SMS
- Short Message Service

I
SJ-20160328171815-006|20160430 (R1.0)

ZTE Proprietary and Confidential