SJ-20130524154927-006-NetNumen U31 R18 (V12.12.43) Fault Management Operation Guide

NetNumen U31 R18Unified Element Management System

Fault Management Operation Guide

Version: V12.12.43

ZTE CORPORATIONNo. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 2013 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

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

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

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

Revision History

Revision No. Revision Date Revision Reason

R1.0 2013-06-20 First edition

Serial Number: SJ-20130524154927-006

Publishing Date: 2013-06-20 (R1.0)

SJ-20130524154927-006|2013-06-20 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Overview.................................................................................... 1-1

1.1 Fault Management System ................................................................................. 1-1

1.2 Functions........................................................................................................... 1-3

1.3 Fault Indication................................................................................................... 1-4

1.3.1 Alarm ...................................................................................................... 1-4

1.3.2 Notification............................................................................................... 1-5

1.4 Alarm Classification............................................................................................ 1-5

1.4.1 Active Alarm and History Alarm ................................................................. 1-5

1.4.2 Alarm Classification by Fault Severity ........................................................ 1-6

1.4.3 Alarm Classification by Fault Type ............................................................. 1-6

1.4.4 Alarm Classification by Resource Type ...................................................... 1-7

1.5 General Alarm Handling Flow.............................................................................. 1-7

1.6 Fault Management Window................................................................................. 1-8

1.6.1 Fault Management Menus ........................................................................ 1-8

1.6.2 Fault Management Buttons on the Main Toolbar ........................................ 1-9

1.6.3 Navigation Pane..................................................................................... 1-10

1.6.4 Alarm Information Pane .......................................................................... 1-10

1.7 Prerequisites.................................................................................................... 1-10

Chapter 2 Alarm and Notification Monitoring .......................................... 2-1

2.1 Alarm Monitoring Policies.................................................................................... 2-1

2.2 Alarm Monitoring Methods .................................................................................. 2-2

2.2.1 Configuring Short Message Monitoring Parameters .................................... 2-3

2.2.2 Configuring E-Mail Monitoring Parameters ................................................2-11

2.3 Monitoring Alarms in Real Time......................................................................... 2-14

2.4 Monitoring Notifications in Real Time ................................................................. 2-15

2.5 Monitoring Alarms by NE .................................................................................. 2-16

2.6 Monitoring Active Alarms by NE Type ................................................................ 2-18

2.7 Viewing Alarms on the Alarm Box...................................................................... 2-20

Chapter 3 Alarm and Notification Query .................................................. 3-1

3.1 Overview ........................................................................................................... 3-1

3.2 Querying Active Alarms by Customized Conditions............................................... 3-2

3.3 Querying History Alarms by Customized Conditions ............................................3-11

I


3.4 Querying Notifications by Customized Conditions............................................... 3-15

3.5 Managing Query Conditions.............................................................................. 3-17

3.5.1 Customizing Query Conditions ................................................................ 3-17

3.5.2 Exporting Query Conditions to an XML File .............................................. 3-19

3.5.3 Importing Query Conditions From an XML File ......................................... 3-20

3.5.4 Copying and Pasting Query Conditions.................................................... 3-20

Chapter 4 Alarm Statistics......................................................................... 4-1

4.1 Overview ........................................................................................................... 4-1

4.2 Setting the Default Conditions for History Alarm Statistics ..................................... 4-2

4.3 Viewing the Statistic Data of History Alarms by a Predefined Template .................. 4-5

4.4 Customizing the Basic Statistics of History Alarms................................................ 4-6

4.5 Customizing the Busy-Time Statistics of History Alarms ...................................... 4-10

4.6 Customizing Important Alarm Code Statistics of History Alarms........................... 4-14

4.7 Creating a Template for Customized Statistics of History Alarms ......................... 4-17

4.8 Creating a Timing Statistic Task......................................................................... 4-19

4.9 Creating a Timing Export Task........................................................................... 4-22

4.10 Viewing Statistics on the Alarm Panel .............................................................. 4-26

4.11 Viewing the Statistics of Active Alarms in Important Sites .................................. 4-27

Chapter 5 Alarm and Notification Management....................................... 5-1

5.1 Overview ........................................................................................................... 5-1

5.2 Acknowledging an Active Alarm .......................................................................... 5-2

5.3 Un-acknowledging of an Active Alarm.................................................................. 5-2

5.4 Clearing an Active Alarm .................................................................................... 5-3

5.5 Clearing a Root Alarm and its Correlated Alarms.................................................. 5-4

5.6 Adding a Comment to an Active Alarm................................................................. 5-5

5.7 Forwarding an Active Alarm via a Short Message or E-Mail................................... 5-5

5.8 Viewing the Details of an Alarm........................................................................... 5-8

5.9 Viewing and Supplementing the Handling Suggestions of an Alarm ..................... 5-10

5.10 Viewing History Alarms Related to an Active Alarm............................................5-11

5.11 Displaying the Alarm Reporting Time by Time Zone .......................................... 5-12

5.12 Creating a Rule for an Active Alarm ................................................................. 5-13

5.13 Viewing Related Rules of an Alarm.................................................................. 5-15

5.14 Locating the Source NE of an Active Alarm in the Topology Management

Window.......................................................................................................... 5-16

5.15 Viewing Active and History Alarms via Rack Diagram ....................................... 5-17

5.16 Printing Alarms............................................................................................... 5-19

5.17 Exporting Alarms to a File ............................................................................... 5-21

II


5.18 Displaying a Root Alarm and its Correlated Alarms ........................................... 5-22

5.19 Synchronizing Active Alarms ........................................................................... 5-23

5.20 Recollecting History Alarms............................................................................. 5-24

Chapter 6 Alarm Rule Management .......................................................... 6-1

6.1 Alarm Rules ....................................................................................................... 6-1

6.2 Alarm Rule Management Operations ................................................................... 6-6

6.3 Creating an Alarm Rule ...................................................................................... 6-7

6.3.1 Creating an Alarm Acknowledging Rule ..................................................... 6-9

6.3.2 Creating an Alarm Clearing Rule ............................................................. 6-14

6.3.3 Creating an Alarm Filtering Rule.............................................................. 6-16

6.3.4 Creating an Alarm Delaying Rule............................................................. 6-19

6.3.5 Creating an Alarm Merging Rule.............................................................. 6-22

6.3.6 Creating an Alarm Persisting Rule ........................................................... 6-25

6.3.7 Creating an Alarm Counting Rule ............................................................ 6-27

6.3.8 Creating an Alarm Forwarding Rule ......................................................... 6-30

6.3.9 Creating an Alarm Masking Rule ............................................................. 6-33

6.3.10 Creating an Alarm Triggering Script Rule ............................................... 6-34

6.3.11 Creating a Notification Filtering Rule by NE Type .................................... 6-38

6.3.12 Creating a Repeated Notification Filtering Rule....................................... 6-40

6.3.13 Creating an Alarm Restraining Rule by NE............................................. 6-42

6.3.14 Creating an Alarm Restraining Rule by NE Type..................................... 6-45

Chapter 7 Alarm Severity Management.................................................... 7-1

7.1 Overview ........................................................................................................... 7-1

7.2 Resetting the Severity Level of an Alarm.............................................................. 7-2

7.3 Creating a Severity Regrading Rule for Specific Managed NEs ............................. 7-3

Chapter 8 Alarm Parameter Settings........................................................ 8-1

8.1 Setting an Alarm Box.......................................................................................... 8-1

8.2 Modifying Handling Suggestions for an Alarm ...................................................... 8-4

8.3 Customizing an Alarm Code................................................................................ 8-6

8.4 Modifying the Cause Description of an Alarm ....................................................... 8-9

8.5 Setting the Alarm Forward Template ...................................................................8-11

8.6 Merging Intermittent Alarms .............................................................................. 8-13

8.7 Setting an Alarm Prompting Rule....................................................................... 8-14

8.8 Creating an Alarm-Suppressing Plan Task ......................................................... 8-17

Figures............................................................................................................. I

Tables ...........................................................................................................VII

III


Glossary ........................................................................................................IX

IV


About This ManualPurpose

This manual provides instructions for fault management operations in the NetNumenTM

U31 R18 Unified Element Management System (NetNumen U31).

Intended Audience

This manual is intended for:

l Maintenance engineersl Debugging engineers

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

1, Overview Provides an overview of the fault management system of NetNumen

U31.

2, Alarm and Notification

Monitoring

Describes the alarm monitoring policies and methods, and provides

instructions for monitoring alarms and notifications using different

methods.

3, Alarm Query Provides different methods for querying active alarms, history

alarms, and customized alarms.

4, Alarm Statistics Describes the alarm statistics functions and provides instructions

for viewing, exporting, and saving the statistical results of history

alarms.

5, Alarm and Notification

Management

Describes the management operations that can be performed for

active alarms and history alarms.

6, Alarm Rule Management Explains the alarm rules supported by NetNumen U31 and describes

how to create each alarm rule.

7, Alarm Severity Management Describes how to manage severity levels of alarms, such as reset

the security level of an alarm, and create a severity regrading rule.

8, Alarm Parameter Settings Describes how to set the alarm parameters related to alarm

box, handling suggestions, alarm code, cause description, alarm

forwarding template, merging intermittent alarms, alarm alerting

rule, , alarm sounds and colors, and custom code setting, probable

cause, forwarding template, intermittent alarm suppressing plan

task.

I


Related Documentation

The following documentation is related to this manual:

NetNumen U31 Unified Element Management System Security Management OperationGuide

Conventions

This manual uses the following typographical conventions:

Typeface Meaning

Italics Variables in commands. It may also refer to other related manuals and

documents.

Bold Menus, menu options, function names, input fields, option button names,

check boxes, drop-down lists, dialog box names, window names,

parameters, and commands.

Constant width Text that you type, program codes, filenames, directory names, and function

names.

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 certain topic.

II


Chapter 1OverviewTable of Contents

Fault Management System.........................................................................................1-1Functions ...................................................................................................................1-3Fault Indication...........................................................................................................1-4Alarm Classification....................................................................................................1-5General Alarm Handling Flow.....................................................................................1-7Fault Management Window........................................................................................1-8Prerequisites ............................................................................................................1-10

1.1 Fault Management SystemThe fault management system, as a component of the NetNumenTM U31 R18 UnifiedElement Management System (EMS), is a system maintenance tool for the centralizedmonitoring of Network Elements (NEs). It collects fault information of boards, links,databases, servers and others from all NEs in the managed network in near real time,and then displays the collected fault information in the format of alarm or notification. Thefault management system helps users quickly locate and resolve faults in the managednetwork.

System Composition

The NetNumen U31 server, clients, and alarm boxes are involved in the fault managementsystem. In addition, a mail server can be deployed to support the transfer of faultinformation via E-mail. All components in the fault management system cooperate toimplement fault management functions. Figure 1-1 illustrates the relationships among thecomponents.

1-1


NetNumen U31 R18 Fault Management Operation Guide

Figure 1-1 Composition of the Fault Management System

The following describes the functions of each component in the fault management system:

l NetNumen U31 server

The NetNumen U31 server (also called EMS server) manages the NEs in themanaged network in a unified manner. The EMS server is the core of the EMS. Faultmanagement is one of the most important functions provided by the EMS.

The EMS server configured with a Short Message Service (SMS) module can sendalarm information to specified personnel via a short message.

l NetNumen U31 client

A NetNumen U31 client (also called EMS client) provides a Graphic User Interface(GUI) to control the entire EMS.

l Alarm box

An alarm box is a tool used to convey alarm information fast and intuitively. It canbe connected to the EMS server through a broadband network. The NetNumen U31system transfers alarm information to the alarm box by using Transmission ControlProtocol/Internet Protocol (TCP/IP). After receiving alarms, the alarm box displaysthem on a Liquid Crystal Display (LCD) screen and activates visual and audiblealarms.

The alarm box can also use its built-in SMS module to forward the received alarminformation to specified personnel via a short message.

1-2


Chapter 1 Overview

Note:

Either of the following SMS modules can be used for alarm information forwarding:

SMS module connected to the serial port of the NetNumen U31 server

Built-in SMS module in the alarm box

l E-mail server

The NetNumen U31 system can send alarm information to specified personnel viaE-mail if an E-mail server is configured in the system.

1.2 FunctionsThe fault management system of the NetNumen U31 provides a range of functions formonitoring and processing alarms and notifications caused by failures in the managednetwork. You can monitor alarms in real time and query alarms by using filteringconditions. In addition, the system can display alarms in multiple modes, for example,indicating alarms in different sounds, colors, and on the screen of an alarm box.

In the NetNumen U31 system, the following fault management functions are supported:

l Acknowledging alarms.

After an alarm is acknowledged, the status of the alarm changes from"Unacknowledged" to "Acknowledged", indicating that a maintenance personnelacknowledges and starts handling this alarm. The system records the time, useraccount, and description related to this acknowledge operation in the alarm database.

l Unacknowledging alarms.

If the maintenance personnel fails to solve an alarm after acknowledging the alarm,the unacknowledge operation can be performed to change the status of an alarm from"Acknowledged" to "Unacknowledged".

l Suppressing alarms.

The system can suppress specific alarms based on predefined conditions. Thesuppressed alarms are not displayed on the client GUI or the alarm box.

l Forwarding alarms.

Alarms in the system can be forwarded to related persons via E-mail or short message.

l Merging alarms.

An alarmmerging rule can be created for merging multiple alarms caused by the samefault. After the alarm merging, only the first received alarm is displayed on the clientGUI.

l Delaying alarms.

1-3



An alarm delaying rule can be created for delaying the processing of transient alarms.When the network managed by the NetNumen U31 system is being tested or unstable,a large number of alarms are reported to the NetNumen U31 system but they arecleared later in a short time. Such transient alarms are not caused by serious failures.The alarm delaying function can limit the report of transient alarms. Only alarmspersisting for a period longer than the preset delay time are reported to the systemand displayed on the client GUI.

l Counting alarms.

The system can count frequently occurring alarms during a time period. When thealarm frequency exceeds the preset threshold, the system can generate a new alarmbased on the statistical result to prompt the maintenance personnel. The descriptionand severity level of the new alarm can be specified by users.

l Counting alarm duration.

If the duration of an active or unacknowledged alarm exceeds a preset threshold,the system can upgrade the severity level of this alarm or generate a new alarm inaccordance with the preset conditions.

l Filtering alarms.

The system can filter received alarms in accordance preset filter conditions.

l Clearing alarms.

If the fault causing an active alarm is solved, the alarm is automatically cleared. Thesystem generates an alarm clearing message and stores the alarm in the history alarmdatabase. You can query history alarms to view the alarms that have been cleared.

In addition, an alarm clearing rule can be created to filter and clear specific alarmswhen these alarms are received from managed NEs. These alarms are stored in thehistory alarm database directly.

l Restraining alarms.

The system can restrain the display of alarms that are correlated with a specificalarm (root alarm). If the root alarm occurs and is displayed on the client, the alarmscorrelated to this alarm are not displayed on the client. If the root alarm does notexist in the system, its correlated alarms (if occurred) are displayed on the client.

1.3 Fault IndicationThe fault management system indicates a fault or event occurring in the network in theform of an alarm or a notification.

1.3.1 AlarmA fault is indicated in the form of alarm when it persists and affects the reliability andservices of the system. An alarm will be cleared only after the fault is resolved. Immediatetroubleshooting is required when alarms occur.

1-4


Chapter 1 Overview

Alarms can be regarded as specific types of notifications indicating detected failures orabnormal conditions in a network.

In the NetNumen U31 system, each alarm has a unique Alarm Code, which is a sequencenumber used to identify the alarm. For example, the alarm code 1001 indicates that thehard disk of the database is overload.

In addition, the NetNumen U31 system also provides a series of Standard AlarmCodes in accordance with international standards (ITU-T M.3100, ITU-T X.721, ITU-TX.733, and ITU-T X.736). A standard alarm code indicates alarms of the same type.For example, alarm codes 198099803 (Link Broken Between OMM and NE) and15010001 (Performance Data Delayed) correspond to the same standard alarm code 566(Connection Establishment Error).

1.3.2 NotificationA notification indicates a non-repeatable or instantaneous fault or event in the system, forexample, board reset and signaling overload. Such a fault or event is normally caused bya sudden environment change or other accidental factors, for example, a restart or fakepower failure of a board. No special handling is required because the fault or event causinga notification can be automatically handled by the system. However, a frequently-reportednotification requires troubleshooting.

1.4 Alarm ClassificationAlarms are classified by different standards in the NetNumen U31 system. The followingsections describe the classification of alarms by four standards: active status, fault type,fault severity, and resource type.

1.4.1 Active Alarm and History AlarmAlarms are classified into active alarms and history alarms depending on the status of thefaults.

l Active alarm

An active alarm indicates a fault that has not been cleared yet.

l History alarm

A history alarm indicates a fault that has already been cleared.

An alarm is displayed as an active alarm on the client GUI when it is reported due to theoccurrence of a fault. If the fault is resolved, this alarm will be cleared from the active alarmlist and turn into a history alarm.

1-5



Note:

An active alarm can be forcibly cleared even if the fault causing this alarm is not resolved.After being cleared, this active alarm will turn into a history alarm.

1.4.2 Alarm Classification by Fault SeverityAlarms are divided into the following four classes depending on the severity of the faultscausing them:

l Critical alarm

A critical alarm indicates a fault that causes failures of system operations or servicecapabilities. Immediate troubleshooting is required when a critical alarm is reported.

l Major alarm

A major alarm indicates a fault that seriously impacts proper system operations orreduces service capabilities. Clearing the fault to restore the system as soon aspossible is required when a major alarm occurs.

l Minor alarm

A minor alarm indicates a fault that slightly influences proper system operations orreduces service capabilities. Proper measures should be taken to clear the fault in atimely manner and prevent the occurrence of more severe alarms when a major alarmoccurs.

l Warning

A warning indicates a fault that has a potential or gradual impact on proper systemoperations or service capabilities. Warning messages need to be analyzed and propermeasures should be taken to clear the fault in a timely manner and avoid more severealarms.

1.4.3 Alarm Classification by Fault TypeAlarms in the NetNumen U31 system are classified into the following types depending onthe type of faults causing them.

l Communication Alarml Processing Error Alarml Quality of Service (QoS) Alarml Equipment Alarml Environmental Alarml Operation & Maintenance Center (OMC) Alarml Integrity Violation Alarml Operational Violation Alarml Physical Violation Alarm

1-6


Chapter 1 Overview

l Security Violation Alarml Time Domain Violation Alarm

1.4.4 Alarm Classification by Resource TypeAlarms can also be classified by the type of resources raising them. The resource typessupported by the NetNumen U31 system depend on the application packages that areselected during the installation of the server and client software.

The following describes the alarm classification in a NetNumen U31 system supportingGlobal System for Mobile Communication (GSM) and Wideband Code Division MultipleAccess (WCDMA) products.

l Alarms reported by the EMS server

OMC alarms

Performance threshold alarms

Public alarms of wireless products

l Alarms reported by GSM products

Hardware platform alarms

GSM alarms

Software Defined Radio (SDR) alarms

l Alarms reported by WCDMA products

Hardware platform alarms

WCDMA Radio Network Controller (RNC) alarms

WCDMA Node B alarms

SDR alarms

1.5 General Alarm Handling FlowImmediate troubleshooting is required when alarms are displayed on the client GUI of anEMS because alarms indicate failures having adverse impacts on the network.

When an alarm occurs, record the failure symptoms, and then handle the alarm inaccordance with the following instructions:

1. View the detailed information of the alarm.2. Analyze the alarm information to locate the cause of the alarm and possible impacts

on the system.3. Take appropriate actions to clear the alarm.4. Verify the alarm handling result.

If the faults fail to be cleared, contact the local ZTE office for support.

1-7



1.6 Fault Management WindowFigure 1-2 shows an example of the fault management window, on which theActive AlarmMonitoring tab is displayed in the alarm information pane.

Figure 1-2 Fault Management Window

1. Menu bar2. Toolbar

3. Navigation pane4. Alarm information pane

5. Message bar

1.6.1 Fault Management MenusTwo menus on the client window menu bar provide commands for fault managementoperations: Fault and Statistics.

For a description of the menu commands, refer to Table 1-1.

Table 1-1 Fault Management Menus

Menu Command Function

Active Alarm Monitoring Monitors alarms.

Notification Monitoring Monitors notifications.

Active Alarm Monitoring by

NE

Monitors alarms by NE.

Active Alarm Monitoring by

NE Type

Monitors alarms by NE type.

Query Active Alarms Queries active alarms.

Query History Alarms Queries history alarms.

Query Notifications Queries notifications.

1-8


Chapter 1 Overview

Menu Command Function

History Alarm Basic Statistics Displays the basic statistics of history alarms.

History Alarm Busy-time

Statistics

Displays the statistics of history alarms during busy hours.

Timing Statistic Task

Management

Manages scheduled statistical tasks.

Timing Export Task

Management

Manages scheduled export tasks.

Suppress Plan Task

Management

Manages scheduled alarm suppressing tasks.

Setting Contains the commands for setting alarm management rules, handling

suggestion, alarm severity, alarm box, alarm code description, alarm

causes, forward template, intermittent alarm, alarm prompt, and alarm

sound and color.

Alarm Panel Enables or disables alarm indicators on the alarm panel.

Synchronize Active Alarms Synchronizes active alarms from all NEs.

Synchronize History Alarms Synchronizes history alarms from all NEs.

VIP Site Alarm Statistics Obtains the statistics of active alarms in VIP sites.

Class B Site Alarm Statistics Obtains the statistics of active alarms in class-B sites.

Class C Site Alarm Statistics Obtains the statistics of active alarms in class-C sites.

1.6.2 Fault Management Buttons on the Main ToolbarThe main toolbar in the client window provides some shortcut buttons related to faultmanagement functions.

For a description of the toolbar buttons, refer to Table 1-2.

Table 1-2 Fault Management Buttons on the Main Toolbar

Button Function

Monitors active alarms.

Queries active alarms.

Queries history alarms.

Queries notifications.

Displays the basic statistics of history alarms.

1-9



Button Function

Displays the statistics of history alarms during busy hours.

1.6.3 Navigation PaneThe navigation pane organizes shortcut links in the form of a hierarchical tree for quickfault management.

There are three tabs on the top of the navigation pane: Management, NE Tree, andStatistic.

l Management

On the Management tab, most fault management functions are organized in a tree.The nodes under the tree root correspond to different functions. You can performalarm query operations and some settings via the management tree.

l NE Tree

On the NE Tree tab, managed elements are organized in a tree. The nodes underthe tree root corresponds to different functional units of the managed NEs. Adjacentnodes under the tree are in parallel or hierarchical relationships. The NE treedemonstrates the physical relationships among the functional units of each managedNE.

l Statistic

On the Statistic tab, all available statistical methods are organized in a tree. You canperform different statistical functions by double-clicking the corresponding nodes inthe tree.

1.6.4 Alarm Information PaneThe alarm information pane is the major part of the fault management window. The panevaries with different fault management functions, displaying the information about therequired alarms or notifications.

1.7 PrerequisitesFor all operations subsequent to this section, the following prerequisites are presumed tohave been met.

l The NetNumen U31 client has been started and successfully connected to the server.l The NetNumen U31 server, the OMMs of managed NEs, and the managed NEs are

synchronous in terms of time.l Fault management permissions have been acquired.l The Fault Management window is open on the client GUI.

1-10


Chapter 2Alarm and NotificationMonitoringTable of Contents

Alarm Monitoring Policies ...........................................................................................2-1Alarm Monitoring Methods..........................................................................................2-2Monitoring Alarms in Real Time................................................................................2-14Monitoring Notifications in Real Time........................................................................2-15Monitoring Alarms by NE..........................................................................................2-16Monitoring Active Alarms by NE Type.......................................................................2-18Viewing Alarms on the Alarm Box.............................................................................2-20

2.1 Alarm Monitoring PoliciesWhen a fault or abnormal condition is detected, an alarm is generated and reported bythe device that failed. The fault management system receives the alarm information, andthen forwards it to the alarm box, or sends it to relevant personnel via a short message orE-mail.

Alarm Monitoring Principles

The following describes the severity-based alarm monitoring principles for timely alarmnotification and immediate troubleshooting.

l Critical and major alarms must be forwarded to the alarm box and relevant personnelvia a short message and handled immediately.

l Minor alarms and warnings can be displayed on the Graphic User Interface (GUI) ofNetNumen U31, or sent to relevant personnel via a short message or E-mail.

Alarm Monitoring Policies

The following describes the four commonly-used alarm monitoring policies. One or morepolicies can be used at the same time.

l Severity-based priority policy

When this policy is used, the system forwards alarms in turn and in accordance withthe severity levels of alarms. If multiple alarms of different severity levels are reportedat the same time, the system will send the alarms with the highest severity first, andthen those with lower severities to the alarm box or relevant personnel.

l First-time policy

2-1



This policy is intended to minimize the adverse impact of faults on services. Whenthis policy is used, the system immediately sends the alarms received from managedelements to the alarm box, and relevant personnel via a short message.

l Multi-receiver policy

When this policy is used, the system sends the alarm information to multiple receivers.This policy ensures that alarms can be handled immediately as long as one of thereceivers successfully receives the alarm information.

l Multi-way policy

Multiple ways, such as alarm sound, short message, and E-mail, can be used at thesame time to notify the occurrence of alarms. This policy ensures that immediatetroubleshooting can be performed even if one alarm forwarding way does not apply.

2.2 Alarm Monitoring MethodsThree methods are available for monitoring alarms in a network:

l Alarm monitoring via EMS

The EMS receives alarm information reported by managed NEs, detects alarmsreported in the system, and displays all detected alarms on the client GUI. It can beused to monitor the operating status of a network. You can conveniently query andview all the alarms generated in the entire system.

An advantage of this alarm monitoring method is that other information, such astopology information, configuration data, and performance data, can also be viewedon the client GUI. With the analysis of the alarm information and other relatedinformation, faults in the network can be more easily located. In addition, you canforward important alarms to maintenance personnel through short messages orE-mails on the client GUI.

l Alarm monitoring via alarm box

The alarm box is a tool used to convey alarm information fast and intuitively. It can beconnected to the NetNumen U31 system through a broadband network. The systemtransfers alarm information to the alarm box through TCP/IP. After receiving alarms,the alarm box displays them on the LCD screen and activates visual and audiblealarms.

The alarm box displays the details of received alarms on its LCD screen. Youcan read the details by pressing the scroll key.

The alarm box provides voice prompts and beep sounds as alarm indications.

In addition, the alarm box can notify relevant personnel of alarms and alarm clearinginformation via short messages through its built-in SMS module.

l Alarm monitoring via short message or E-mail

2-2


Chapter 2 Alarm and Notification Monitoring

The NetNumen U31 system can forward the alarm information to relevant personnelvia a short message or E-mail. This function enables them to know the operatingstatus of the network even if they are not on site.

An active alarm can be forwarded to specified personnel via a short message orE-mail.

An alarm forwarding rule can be created for automatically forwarding activealarms that meet specified conditions via a short message or E-mail.

Before forwarding alarms via a short message or E-mail, you must configure therequired parameters in Configuration Center. For how to configure short messagemonitoring parameters and E-mail monitoring parameters, refer to "2.2.1 ConfiguringShort Message Monitoring Parameters" and "2.2.2 Configuring E-Mail MonitoringParameters".

2.2.1 Configuring Short Message Monitoring ParametersThis procedure describes how to configure short message monitoring parameters in theconfiguration center of the NetNumen U31 system before using short messages to forwardalarms.

The short message monitoring parameters can be configured during the process ofinstalling the NetNumen U31 server software. After the NetNumen U31 server software isinstalled, you can start the configuration center and configure the parameters after exitingthe server software. To validate the parameter configuration, the NetNumen U31 servermust be restarted after the configuration is completed.

Caution!

Do not exit the NetNumen U31 server software unless absolutely necessary. Exiting theNetNumen U31 server software results in an interruption of network management services.

Prerequisite

l The NetNumen U31 server and the SMS module are connected properly.l The information of the mobile phone number to be forwarded is acquired.l The user account (for example, "omc") that is used for installing the NetNumen U31

server software is acquired.

Steps

1. Log in to the NetNumen U31 server as the "omc" user, and execute the followingcommands to change the current directory to ums-server in the installation path($HOME) of the server software and exit the server software:

cd $HOME/ums-server

2-3



./shutdown-console.sh

2. Execute the following commands to change the current directory to uif in theinstallation path of the server software and start the configuration center:

cd $HOME/uif

./runPlugCenter.sh

The NetNumen Unified Management System Configuration Center window isdisplayed.

3. In the left navigation tree, select Common Configuration > Common Property,expand the Forward node on the Server tab in the right pane, and select the Forwardtype node. The default type 4 (forwarding alarm short messages via alarm box) isdisplayed in the Value of config drop-down list, see Figure 2-1.

Figure 2-1 Forward Type Node

For a description of the available short message forwarding types, refer to Table 2-1.

Table 2-1 Short Message Forwarding Types

Short Message Forwarding

Type

Description Value of

Config

Forwarding short messages

via a GSM modem

Alarm short messages are forwarded to

relevant personnel via the SMS module

connected to the NetNumen U31 server.

1

2-4



Short Message Forwarding

Type

Description Value of

Config


via SMPP

Alarm short messages are sent to the short

message center through Short Message Peer

to Peer Protocol (SMPP). The short message

center then forwards the short messages to

relevant personnel.

2


via CMPP


message center through ChinaMobile Point

to Point (CMPP). The short message center

then forwards the short messages to relevant

personnel.

3


via an alarm box

Alarm short messages are forwarded to

relevant personnel via the SMS module built

in the alarm box.

4 (default)


via a private transferring

interface

The NetNumen U31 system sends alarm short

messages to a specified Enterprise Message

Bus (EMB), which then forwards the alarm

short messages.

This type is developed in accordance with user

requirements, and is not provided for the time

being.

5


via SGIP


message center through Short Message

Gateway Interface Protocol (SGIP). The

short message center then forwards the short

messages to relevant personnel.

6


via SMGP


message center through Short Message

Gateway Protocol (SMGP). The short message

center then forwards the short messages to

relevant personnel.

7

4. Select a short message forwarding type from the Value of config list in accordancewith the actual condition, and then set the required parameters.l If it is required to forward short messages via an alarm box, select 4 from theValue

of config list, select Forward > Alarm Box Forward > IP address of alarm boxfor forwarding SMS, and enter the IP address of the alarm box in the Value ofconfig text box, see Figure 2-2.

2-5



Figure 2-2 IP Address of Alarm Box for Forwarding SMS Node

Note:

In this forwarding type, if a short message exceeds the maximum length, thesystem automatically divides it into multiple short messages.

l If it is required to forward short messages via a GSM modem, select 1 from theValue of config list, and expand Forward > GSM Modem Forward, see Figure2-3.

2-6



Figure 2-3 GSM Modem Forward Node

Set the parameters under the GSM Modem Forward node. For a description ofthe parameters, refer to Table 2-2.

Table 2-2 GSM Modem Forwarding Function Parameters

Parameter Description

GSM Modem equipment

serials

Sets the serial port to which the SMS module is connected.

In theWindows operating system, enter COM1 if the SMS

module is connected to serial port 1; enter COM2 if the

SMS module is connected to serial port 2.

In the Linux operating system, enter /dev/ttyS0 if the

SMS module is connected to serial port 1; enter /dev/

ttyS1 if the SMS module is connected to serial port 2.

In the Solaris operating system, enter /dev/cua/a if

the SMS module is connected to serial port 1; enter /

dev/cua/b if the SMS module is connected to serial

port 2.

The default value is COM1.

GSM part times Sets the maximum number of segments into which a

short message can be divided when it contains too many

characters. The default value is 3.

GSM receiver number Sets cellphone numbers of the receivers to whom short

messages can be sent. User can set multiple cellphone

numbers, which are separated by commas.

If no receiver cellphone number is set in the NetNumen U31

system, the parameter setting becomes valid.

2-7



l If it is required to forward short messages through SMPP, select 2 from the Valueof config list, and expand Forward > SMPP Forward, see Figure 2-4.

Figure 2-4 SMPP Forward Node

Set the parameters in accordance with the information provided by the operator,including the IP address and port number of the SMPP gateway, user name andpassword for accessing the short message center, source Type of Number (TON),destination TON, source Number Plan Indicator (NPI), destination NPI, sourcenumber for sending short messages, encoding mode of short messages, and thesystem type used for setting up connection to the short message center.

l If it is required to forward short messages through CMPP, select 3 from the Valueof config list, and expand Forward > CMPP Forward, see Figure 2-5.

2-8



Figure 2-5 CMPP Forward Node

Set the parameters in accordance with the information provided by the operator,including the IP address and port number of the CMPP gateway, ICP, SP identity,service identity, subscriber type and phone number for accounting, messagesource, charge type, charge code, and encoding mode.

l If it is required to forward short messages through SGIP, select 6 from the Valueof config list, and expand Forward > SGIP Forward, see Figure 2-6.

Figure 2-6 SGIP Forward Node

2-9



Set the parameters in accordance with the information provided by the operator,such as the IP address and port number of the SGIP gateway, user name andpassword for accessing the short message center, SP identity, server type, linkidentity, login type, phone number for accounting, and the enterprise code.

l If it is required to forward short messages through SMGP, select 7 from the Valueof config list, and expand Forward > SMGP Forward, see Figure 2-7.

Figure 2-7 SMGP Forward Node

Set the parameters in accordance with the information provided by the operator,such as the IP address and port number of the SMGP gateway, user name andpassword for accessing the short message center, SP identity, server type, chargetype, charge per short message, monthly fee, encoding mode of short messages,phone number for accounting, product identity, and the link identity.

5. On the Server tab in the right pane, select Forward > Country code, and set thereceiver's country code in the Value of config text box (for example, 86), see Figure2-8.

2-10



Figure 2-8 Country Code Node

6. Click Save. A message confirming the configurations is displayed.

7. Click OK, and then click Close in the NetNumen Unified Management System Configuration Center window.

8. Execute the following commands to change the current directory to ums-server inthe installation path ($HOME) of the server software and start the NetNumen U31 serversoftware:

cd $HOME/ums-server

nohup ./console.sh &

End of Steps

2.2.2 Configuring E-Mail Monitoring ParametersThis procedure describes how to configure E-mail monitoring parameters in theconfiguration center of the NetNumen U31 system before using E-mails to forward alarms.

The E-mail monitoring parameters can be configured during the process of installing theNetNumen U31 server software. After the NetNumen U31 server software is installed, youcan start the configuration center and configure the parameters after exiting the serversoftware. To validate the parameter configuration, the NetNumen U31 server must berestarted after the configuration is completed.

2-11



Caution!

Do not exit the NetNumen U31 server software unless absolutely necessary. Exiting theNetNumen U31 server software results in an interruption of network management services.

Prerequisite

l The NetNumen U31 server and the mail server are connected properly.l The information of the E-mail box address to be forwarded is acquired.l The user account (for example, "omc") that is used for installing the NetNumen U31

server software is acquired.

Steps

1. Log in to the NetNumen U31 server as the "omc" user, and execute the followingcommands to change the current directory to ums-server in the installation path($HOME) of the server software and exit the server software:

cd $HOME/ums-server

./shutdown-console.sh

2. Execute the following commands to change the current directory to uif in theinstallation path of the server software and start the configuration center:

cd $HOME/uif

./runPlugCenter.sh

The NetNumen Unified Management System Configuration Center window isdisplayed.

3. In the left navigation tree, select Common Configuration > Common Property, andexpand the Forward node and then the Mail Forward node on the Server tab in theright pane, see Figure 2-9.

2-12



Figure 2-9 Mail Forward Node

4. Set the required parameters under the Mail Forward node.

For a description of the parameters, refer to Table 2-3.

Table 2-3 E-Mail Forwarding Parameter Descriptions

Parameter Description

Mail server IP Sets the IP address of the E-mail server used for forwarding

alarm information.

Mail server port Sets the port number of the E-mail server.

Default: 25.

Mail server need auth Sets whether authentication is needed for logging in to the

E-mail server. The value range is Yes and No. If Yes is

selected, the user name and password are required.

Mail server username Sets the user name used for logging in to the E-mail server

when authentication is required.

Mail server password Sets the login password when authentication is required.

Mail server's FromAddress Sets the E-mail address from which the E-mail containing

alarm information is sent, for example, [email protected].

Mail encoding Selects an E-mail encoding mode from the Value of config

list.

Mail text format Selects an E-mail content format from the Value of config list.

5. Click Save. A message confirming the configurations is displayed.

2-13



6. Click OK, and then click Close in the NetNumen Unified Management System Configuration Center window.

7. Execute the following commands to change the current directory to ums-server inthe installation path ($HOME) of the server software and start the NetNumen U31 serversoftware:

cd $HOME/ums-server

nohup ./console.sh &

End of Steps

2.3 Monitoring Alarms in Real TimeThis procedure describes how to monitor alarms in real time.

Context

By monitoring active and history alarms in real time, you can obtain the latest alarminformation of the NEs managed by NetNumen U31.

Steps

1. To view the active alarms and history alarms in real time, perform one of the followingoperations in the client window:l On the menu bar, select Fault > Alarm Monitoring.l On the toolbar, click .l On the Management tab in the navigation pane, double-click Alarm Monitoring

under the Alarm Monitoringnode.

TheAlarmMonitoring tab is displayed in the left pane of the client window, see Figure2-10. The upper part of the tab displays the active alarms. The lower part displays thehistory alarms.

2-14



Figure 2-10 Alarm Monitoring Tab

1. Active alarms 2. History alarms

End of Steps

2.4 Monitoring Notifications in Real Time

Context

By monitoring notifications, you can obtain the information of the latest events occurring inthe network and determine whether it is necessary to process these events.

The following procedure describes how to view real-time notifications in the client window.

Steps

1. On the menu bar of the client window, select Fault > Notification Monitoring. TheNotification Monitoring tab page is displayed in the right pane of the client window,see Figure 2-11.

2-15



Figure 2-11 Notification Monitoring Tab

2. (Optional) Perform the required operations, such as export displayed columns, exportall columns, print, clear table, view full screen, stop refreshing, customize displayedcolumns, view details, and view handling suggestions.

End of Steps

2.5 Monitoring Alarms by NEThis procedure describes how to monitor the active alarms of a specific NE in the clientwindow.

Context

The system can count the active alarms of all severity levels for each NE in the managednetwork. In addition to viewing the statistical information of active alarms, you can monitorthe active alarms of a specific NE.

Steps

1. Perform either of the following operations:l On the menu bar of the client window, select Fault > Alarm Monitoring by NE.l On the Management tab in the navigation pane, double-click Alarm Monitoring

by NE under the Realtime Monitoring node.

The Alarm Monitoring by NE tab is displayed, see Figure 2-12

2-16



Figure 2-12 Alarm Monitor by NE Tab

Note:

The button is used to save the alarm information to a specified directory in thelocal computer or the server.

2. Expand the NE tree, locate the NE whose active alarms are to be viewed, and thenview the details.l To monitor all active alarms of the NE, right-click the corresponding cell and select

Detail from the shortcut menu. Alternatively, double-click the corresponding cellon the Total column.

l To monitor the active alarms of a specific severity, double-click the correspondingcell on the column of a severity, for example, Major.

A new tab is displayed, listing all active alarms of this NE (see Figure 2-13), or theactive alarms of a specific severity (see Figure 2-14).

2-17



Figure 2-13 Tab for Monitoring Active Alarms of an NE

Figure 2-14 Tab for Monitoring Active Major Alarms of an NE

End of Steps

2.6 Monitoring Active Alarms by NE TypeContext

The system can count the active alarms of all severity levels in the managed network byNE type. In addition to viewing the statistical information of active alarms by NE type, youcan monitor the active alarms reported by all NEs of the same type.

The following procedure describes how to monitor the active alarms reported by all NEsof the same type.

Steps

1. Perform either of the following operations:l On the menu bar of the client window, select Fault > Alarm Monitoring by NE

Type.

2-18



l On the Management tab in the navigation pane, double-click the AlarmMonitoring by NE Type under the Realtime Monitoring node.

The Alarm Monitoring by NE Type tab is displayed, see Figure 2-15

Figure 2-15 Alarm Monitoring by NE Type Tab

2. Expand the resource type tree, locate the type of the NEs whose active alarms are tobe viewed, and then view the details.l To monitor all active alarms of the NE type, right-click the corresponding

cell and select Detail from the shortcut menu. Alternatively, double-click thecorresponding cell on the Total column.

l To monitor the active alarms of a specific severity, double-click the correspondingcell on the column of a severity, for example, Major.

A new tab is displayed, listing all active alarms reported by all NEs of this NE type (seeFigure 2-16), or the active alarms of a specific severity (see Figure 2-17).

2-19



Figure 2-16 Tab for Monitoring Active Alarms of an NE Type

Figure 2-17 Tab for Monitoring Active Major Alarms of an NE Type

End of Steps

2.7 Viewing Alarms on the Alarm BoxThis procedure describes how to view alarm information on the LCD screen of an alarmbox.

2-20



Context

When an alarm box is used, you can directly view the information of alarms on the alarmbox. Upon receiving alarms, the alarm box produces alarm sounds and turns on thecorresponding indicators.

Prerequisite

l The connection between the alarm box and the NetNumen U31 system is normal.l The user has the authority of viewing alarms on the alarm box.

Steps

1. Verify that the alarm box activates any visual or audible alarm.

2. Press the M button on the alarm box. The function menu is displayed.

3. Press the up or down arrow to select the Alarm Querying menu, and then select OK.The information of the latest alarm is displayed on the screen.

4. Use the up or down arrow to view the information of other received alarms.

End of Steps

2-21



This page intentionally left blank.

2-22


Chapter 3Alarm and Notification QueryTable of Contents

Overview....................................................................................................................3-1Querying Active Alarms by Customized Conditions ....................................................3-2Querying History Alarms by Customized Conditions .................................................3-11Querying Notifications by Customized Conditions.....................................................3-15Managing Query Conditions .....................................................................................3-17

3.1 OverviewThe NetNumen U31 system supports the query of active alarms, history alarms, andnotifications in different ways.

Note:

The alarm and notification query functions are also available in the TopologyManagement window in addition to the Fault Management window. Users can right-clickan NE agent on the NE Tree tab in the left navigation pane, point to Fault Managementon the shortcut menu, and then select an appropriate command as required, for example,Active Alarms or History Alarms Within One Day. The subsequent query proceduresare performed in the Fault Management window.

Querying Alarms and Notifications by Default Conditions

The Management tab in the navigation pane of the Fault Management window providessome shortcut links for quick query of alarms and notifications under the Alarm Querynode, including:

l All Active Alarmsl Unacknowledged Active Alarmsl History Alarms Within One Dayl History Alarms Within Three Daysl Notifications Within One Dayl Notifications Within Three Days

For example, either of the following operations can be performed for querying all activealarms:

3-1



l Selecting Management Tree > Alarm Query > Active Alarms and double-clickingthe All Active Alarms node.

l Selecting Management Tree > Alarm Query > Active Alarms. Right-click the AllActive Alarms node, and then clicking Execute.

Querying Alarms and Notifications of a Specific NE

On the NE Tree tab in the navigation pane of the fault management window, you can queryactive alarms, history alarms, or notifications of a specific NE by selecting an appropriateitem on the shortcut menu. These menu items are:

l Active Alarmsl Unacknowledged Active Alarmsl Active Alarms Within One Hourl Active Alarms Within One Dayl History Alarms Within One Dayl History Alarms Within Three Daysl All The History Alarmsl Current Notifications

Querying Alarms and Notifications by Customized Conditions

You can customize query conditions to query specific active alarms, history alarms, ornotifications as needed, and save the customized query conditions as a template, whichcan be used for future alarm or notification queries with the same query conditions.

3.2 Querying Active Alarms by Customized Conditions

Context

In addition to querying active alarms by conditions predefined by the system, you cancustomize query conditions to obtain the specified active alarms as required. All queryconditions are optional. If no item is selected, the system considers that all items areselected. For example, if no specific alarm type is selected, the system will query thealarms of all types.

This procedure describes how to query specific active alarms by customized conditions.

3-2


Chapter 3 Alarm and Notification Query

Steps

Note:

An alarm reported by an NEmay be reported to the EMS by another NE. For example,a board in a device reports an alarm, but this alarm is reported by the device to theEMS. To query such an alarm, you can select the device or the board when selectingthe NE in the NE tree.

1. In the Fault Management window, perform one of the following operations:l On the menu bar, select Fault > Query Active Alarms.l On the toolbar, click .l On the Management tab, select Management Tree > Alarm Query. Right-click

Active Alarms, and then click New Active Alarm Query.l On the Management tab, select Management Tree > Alarm Query > Custom

Query. Right-click My Query and then click New Active Alarm Query.

The Query Active Alarms dialog box is displayed with five tabs. By default, theLocation tab is displayed, see Figure 3-1.

Figure 3-1 Query Active Alarms Dialog Box (Location Tab)

2. On the Location tab, perform the following operations:

3-3



Note:

The details of an alarm records the locations of both the NE reporting this alarm andthe NE influenced by this alarm. The query result contains this alarm when the locationof either NE is selected on the Location tab as a query condition.

a. Select NE type(s) from the NE Type drop-down list.

b. Select the product from the Product drop-down list.

c. Select the element(s) whose active alarms are to be queried in the NE tree.

d. Use the arrow buttons to add the selected elements to the right list box.

For a description of the functions of the arrow buttons on the Location tab, refer toTable 3-1.

Table 3-1 Arrow Button Function Descriptions

Button Description Remarks

Adds one or multiple selected

nodes.

A single selected node is marked

with a file icon ( ).

Adds the selected node(s) and all

their child nodes.

A selected node with all its child

nodes is marked with a folder icon

( ).

Removes one or multiple added

nodes.

-

Removes all added nodes. -

Executes the filter function by

displaying NEs matching the

keywords.

-

3. To query active alarms with specific alarm codes, perform the following operations:

a. Click the Alarm Code tab. The Alarm Code tab is displayed, see Figure 3-2.

3-4



Figure 3-2 Query Active Alarms Dialog Box (Alarm Code Tab)

Note:l The system supports query by keyword. You can enter a keyword in the Enter

filter text box, and then click to quickly locate the required alarm codes.l The icon is used to select all alarm codes at a time.l The Exclude Mode can be selected for adding those alarm codes that are

not selected in the resource type tree.

b. Expand the Resource Type tree to locate the required alarm code(s).

c. Click the alarm code(s), and then click to add the selected alarm code(s) to theright list box

4. To query active alarms of specific standard alarm codes, perform the followingoperations:

a. Click the Probable Cause tab. The Probable Cause tab is displayed, see Figure3-3.

3-5



Figure 3-3 Query Active Alarms Dialog Box (Probable Cause Tab)

Note:

The NetNumen U31 system summarizes the probable causes of all alarms inaccordance with international specifications (such as ITU-T M.3100, ITU-T X.721,ITU-T X.733, and ITU-T X.736) and organizes them as standard alarm codes onthe Probable Cause tab.

The system specifies an alarm code and a standard alarm code for each alarm.Multiple alarm codes may correspond to the same standard alarm code. Forexample, the alarm codes 198099803 and 1501001 correspond to the samestandard alarm code 566 (Connection establishment error).

Alarms related to Code Division Multiple Access (CDMA) NEs have not standardalarm code, so they cannot be queried by standard alarm code.

The required alarms cannot be found until appropriate alarm codes and standardalarm codes having mapping relationships are selected on the Alarm Code andProbable Cause tabs.

b. Select the standard alarm codes in the Probable Cause tree, and then click .

3-6



5. To query active alarms reported, acknowledged, or unacknowledged during a specificperiod, perform the following operations:

a. Click the Time tab. The Time tab is displayed, see Figure 3-4.

Figure 3-4 Query Active Alarms Dialog Box (Time Tab)

Note:

If the NetNumen U31 client is located in a different time zone from that of theNEs reporting the alarms and the time zone support function is enabled in theNetNumen U31 system, the reference time zone can be determined before thesetting of time period for alarm query.

l NE Wall-Time: This option indicates that the specified time period for alarmquery is in accordance with the time zone of the NEs.

l Client Time Zone (GMT+08:00): This option indicates that the specified timeperiod for alarm query is in accordance with the time zone of the client.

b. Select a time zone, and then set the period(s) under Raised Time, and/or(Un)ACK Time.

6. Click the Others tab. The Others tab is displayed, see Figure 3-5.

3-7



Figure 3-5 Query Active Alarms Dialog Box (Others Tab)

7. Perform appropriate operations as needed as follows:l To query active alarms of specific type(s), select the alarm type(s) under Alarm

Type.l To query active alarms of specific severity level(s), select the severity level(s)

under Perceived Severity.l To query active alarms in accordance with their acknowledgement status, select

Acknowledged and/or Unacknowledged under ACK State.l To query active alarms of an NE whose IP address is known, enter the IP address

under NE IP.l To query active alarms, click the Advanced button, and then set parameters in

the displayed Advanced dialog box shown in Figure 3-6 in accordance with thefollowing conditions:

On the Advanced tab, enter keywords for the (Un)ACK User ID, comment,and/or alarm ID, and select the visibility, correlation, and/or testing status.

Correlated alarms are invisible by default. When correlated alarms arequeried, invisible alarms will also be queried.

On the Additional Information tab, enter the site ID (office), alarm objecttype, alarm object ID, or board type.

3-8



Figure 3-6 Advanced Dialog Box for Active Alarm Query

8. Click OK. The Query Active Alarms tab is displayed in the client window, listing thequery results of active alarms, see Figure 3-7.

Figure 3-7 Query Results of Active Alarms

For a description of the buttons and drop-down list boxes on the toolbar, refer to Table3-2.

3-9



Table 3-2 Buttons and Drop-Down List Boxes on the Toolbar of the Alarm QueryResult Tab

Button Description

Two buttons are available after the down arrow is clicked:

: Exports all columns in the query results

into a file.

: Exports all visible columns in the query

results into a file.

Prints the alarm query results.

Resets conditions for querying the active alarms.

Saves the customized query conditions as a query template.

After clicking this button, you need to enter a name for the query

template in the displayed New Query dialog box.

Pins or scrolls the table.

Customizes the displayed columns.

Monitors history alarms in the query results of active alarms.

If any of the active alarms is cleared automatically or manually,

the corresponding alarm is displayed in the History Alarms pane

displayed on the lower part of the Query Active Alarms tab, see

Figure 3-8.

Synchronizes active alarms.

After click this button, you need set the related parameters in the

displayed Synchronize Active Alarms dialog box.

Severity Filters the alarm query results by severity level (critical, major, minor,

and/or warning).

ACK State Filters the alarm query results by acknowledgement state

(acknowledged and/or unacknowledged).

3-10



Visibility Filters the alarm query results by visibility (visible and/or invisible).

Figure 3-8 Query Results of Active Alarms (with the History Alarms Pane)

Note:

When closing the Query Active Alarms tab, you will be asked whether to savethe customized query conditions. If you click Yes, a name is required for the querytemplate in the displayed Query Active Alarms dialog box.

After the customized query conditions are saved as a query template, you canright-click it under the My Query node and then click Execute to initiate a query inaccordance with the same query conditions.

End of Steps

3.3 Querying History Alarms by Customized ConditionsThis procedure describes how to customize query conditions for querying specific historyalarms.

Context

In addition to querying history alarms by conditions predefined by the system, you cancustomize query conditions to obtain the specified history alarms as required. All query

3-11



conditions are optional. If no item is selected, the system considers that all items areselected. For example, if no specific alarm type is selected, the system queries historyalarms of all types.

Note:

The setting of some conditions for querying history alarms is similar to that for queryingactive alarms. This procedure does not repeat the explanation of the same conditions. Forthe details explanation, refer to "3.2 Querying Active Alarms by Customized Conditions".

Steps

Note:

An alarm reported by an NEmay be reported to the EMS by another NE. For example,a board in a device reports an alarm, but this alarm is reported by the device to theEMS.

If a user selects an NE on the Location tab page, the systemwill query history alarmsreported by this NE (The Match By Additional NE check box is not selected). If theuser selects the Match By Additional NE check box at the same time, the system willquery history alarms reported by this NE.

1. In the fault management window of the client window, perform one of the followingoperations:l On the menu bar, select Fault > Query History Alarms.l On the toolbar, click .l On theManagement tab, right-click History Alarms, and then click New History

Alarm Query.l On the Management tab, right-click My Query under Custom Query, and then

click New History Alarm Query.

The Query History Alarms dialog box is displayed with five tabs. By default, theLocation tab is displayed, see Figure 3-9.

3-12



Figure 3-9 Query History Alarms Dialog Box (Location Tab)

2. On the Location tab, perform the following operations:

a. Select NE type(s) from the NE Type drop-down list as needed.

b. Select the product from the Product drop-down list.

c. Select the NE(s) whose history alarms are to be queried in the NE tree.

d. Use the arrow buttons to add the selected NE(s) to the right list box.

Note:

In the Duration area of the Time tab, you can set the specific alarm-raising durationaccurate to the unit of day, hour, minute, or second.

3. Set parameters on the Alarm Code, Probable Cause, Time, and Others tabs .

4. Click the Others tab. The Others tab is displayed.

5. Click the Advanced button. The Advanced dialog box is displayed, see Figure 3-10.

3-13



Figure 3-10 Advanced Dialog Box

6. Set the query conditions as needed.l On the Advanced tab, set the clear type, (Un)ACK user ID, clear user ID, remark,

comment, alarm ID, correlation, and/or testing status.

Correlated alarms are invisible by default. When correlated alarms are queried,invisible alarms will also be queried.

l On the Additional Information tab, set the site ID (Office), alarm object type,alarm object ID, or board type.

7. (Optional) To display other alarm clearing types, click theMore button. In the displayedExtended Clear Type dialog box, select the options as needed, and click OK, seeFigure 3-11.

3-14



Figure 3-11 Extended Clear Type Dialog Box

8. In the Advanced dialog box, click OK.

9. In the Query History Alarms dialog box, click OK. The alarm information panedisplays the history alarms meeting the specified conditions, see Figure 3-12.

Figure 3-12 Query Results of History Alarms

End of Steps

3.4 Querying Notifications by Customized ConditionsThis procedure describes how to customize query conditions for querying specificnotifications.

3-15



Context

In addition to querying notifications by conditions predefined by the system, you cancustomize query conditions to obtain the specified notifications as required. All queryconditions are optional. If no item is selected, the system considers that all items areselected. For example, if the occurrence time is not specified, the system queries allnotifications that occurred.

Steps

1. In the Fault Management window, perform one of the following operations:l On the menu bar, select Query Notifications.l On the Management tab, select Management Tree > Alarm Query. Right-click

Notifications, and then click New Notification Query.l On the Management tab, select Management Tree > Alarm Query > Custom

Query. Right-click My Query and then click New Notificatoin Query.

The Query Notifications dialog box is displayed with three tabs. By default, theLocation tab is displayed, see Figure 3-13.

Figure 3-13 Query Notifications Dialog Box

2. On the Location tab, select the NE type and Product, click the NE(s) to be queriedin the NE list box, and then click to add the NE(s).

3. Click the Notification Code tab. The Notification Code tab is displayed.

3-16



4. Select the notification codes in the left list box, and then click .

5. Click the Others tab. The Others tab is displayed.

6. Set the time range and/or additional information as the query conditions.

On the Others tab, you can click Advanced, and set advanced conditions in theAdvanced dialog box, such as office ID, alarm object type, alarm object ID, and boardtype.

7. Click OK. The alarm information pane displays the queried notifications, see Figure3-14.

Figure 3-14 Notification Query Results

You can also save the customized query conditions as a query template for futureuse. For details, see the follow-up actions in the section "Querying Active Alarms byCustomized Conditions".

End of Steps

3.5 Managing Query Conditions

3.5.1 Customizing Query ConditionsIn the fault management window, you can customize conditions (such as location, time,cause, description, and system type) for querying specific alarms or notifications and savethe query conditions as a query template for repeated use. The created query can bemodified, deleted, renamed, copied, and saved as another query.

The customized queries are classified into two categories in accordance with their visibility:

l My Query: Queries under this node are visible only to the current user.

3-17



l Department's Query: Queries under this node are visible to users in the samedepartment as the current user.

Creating a new query of active alarms, history alarms, or notifications involves similarprocedures. You can create a new query under the My Query node or the Department'sQuery node. This procedure describes how to create a new query for active alarms underMy Query.

Steps

1. In the Fault Management window, select Management Tree > Alarm Query >Custom Query on the Management tab, right-click My Query, and then click NewActive Alarm Query. The Query Active Alarms dialog box is displayed, see Figure3-15.

Figure 3-15 Query Active Alarms Dialog Box

2. Set query conditions on the Location, Alarm Code, Probable Cause, Time, andOthers tab.

3. Click OK. The query results are displayed in the alarm information pane, see Figure3-16.

3-18



Figure 3-16 Query Results of Active Alarms

4. Click on the toolbar. The New Query dialog box is displayed.

5. Enter a name for the query, and then click OK. The new query is displayed under theMy Query node on the Management tab.

End of Steps

3.5.2 Exporting Query Conditions to an XML FileThis procedure describes how to export the predefined query conditions (History AlarmsWithin One Day) to an XML file.

Context

The default query conditions predefined by the NetNumen U31 system and customized byyou can be exported to an XML file.

Steps

1. On theManagement tab in the navigation pane, right-click theHistory AlarmsWithinOne Day node, and then click Export Condition. The Save dialog box is displayed.

2. Enter or select a directory for saving the exported query conditions from the Save indrop-down list, change the file name in the File name box as needed, and then clickSave. An XML file containing the exported query conditions is displayed under thespecified directory.

End of Steps

3-19



3.5.3 Importing Query Conditions From an XML FileThis procedure describes how to import an XML file under theMy Query node for creatinga query template.

Context

You can specify query conditions in an XML file in the format supported by the NetNumenU31 system, and then import the predefined query conditions to the NetNumenU31 systemas a new customized query template.

The procedures for importing query conditions under the My Query node and theDepartment's Query node are the same.

Prerequisite

The format of query conditions defined in the XML file to be importedmeets the requirementof the NetNumen U31 system.

Note:

To view the required format of query conditions in an XML file, you can open an existingXML file that contains the query conditions exported from the NetNumen U31 system.

Steps

1. On the Management tab in the navigation pane, right-click the My Query node underCustom Query, and then click Import Condition. The Open dialog box is displayed.

2. Select the directory of the XML file from the Look in drop-down list, select the XMLfile to be imported, and then click Open. The Import Query dialog box is displayed,asking for a name for the imported query template.

3. Enter a name in theQuery Name box, and then clickOK. A query template is displayedunder the My Query node on the Management tab in the navigation pane.

End of Steps

3.5.4 Copying and Pasting Query Conditions

Context

By copying and pasting existing query conditions, default query conditions, or customizedquery conditions, you can create a new query template conveniently.

The procedures for copying a query template under the My Query node and theDepartment's Query node are the same. This procedure describes how to copy and

3-20



paste the query conditions of the query Unacknowledged Active Alarms under the MyQuery node.

Steps

1. On the Management tab in the navigation pane, right-click the UnacknowledgedActive Alarms node, and then click Copy.

Documents

SJ-20130524154927-006-NetNumen U31 R18 (V12.12.43) Fault Management Operation Guide