netnumen u31 r18 unified element management system fault management operation guide

NetNumen™ U31 R18Unified Element Management System

Fault Management Operation Guide

Version: 12.10.040

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 © 2011 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 2011-09–22 First Edition

Serial Number: SJ-20110823134613-007

Publishing Date: 2011-09-22(R1.0)

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

Chapter 1 Overview of Fault Management ............................................... 1-11.1 Introduction to the Fault Management System...................................................... 1-1

1.2 Fault Management Functions .............................................................................. 1-3

1.3 Fault Indication................................................................................................... 1-3

1.3.1 Alarm ...................................................................................................... 1-3

1.3.2 Notification............................................................................................... 1-4

1.4 Alarm Classification............................................................................................ 1-4

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

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

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

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

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

1.6 Introduction to the Fault Management Window..................................................... 1-7

1.6.1 Fault Management Window....................................................................... 1-7

1.6.2 Menus for Fault Management.................................................................... 1-7

1.6.3 Toolbar Buttons Related to Fault Management ........................................... 1-8

1.6.4 Navigation Pane....................................................................................... 1-9

1.6.5 Alarm Information Pane ............................................................................ 1-9

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

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

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

2.2.1 Alarm Monitoring via Network Element Management System ...................... 2-2

2.2.2 Alarm Monitoring via Alarm Box ................................................................ 2-2

2.2.3 Alarm Monitoring via Short Message and E-mail......................................... 2-3

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

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

2.5 Monitoring Active Alarms by Network Element.................................................... 2-12

2.6 Monitoring Active Alarms by Network Element Type ........................................... 2-14

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

Chapter 3 Alarm and Notification Query .................................................. 3-13.1 Overview of Alarm and Notification Query ............................................................ 3-1

I

3.2 Querying Active Alarms ...................................................................................... 3-2

3.2.1 Querying All Active Alarms........................................................................ 3-2

3.2.2 Querying Unacknowledged Active Alarms.................................................. 3-2

3.2.3 Querying the Active Alarms of a Network Element ...................................... 3-3

3.3 Querying History Alarms ..................................................................................... 3-3

3.3.1 Querying All History Alarms Within One Day .............................................. 3-3

3.3.2 Querying All History Alarms Within Three Days .......................................... 3-4

3.3.3 Querying the History Alarms of a Network Element..................................... 3-4

3.4 Querying Notifications......................................................................................... 3-5

3.4.1 Querying Notifications Within One Day ...................................................... 3-5

3.4.2 Querying Notifications Within Three Days .................................................. 3-5

3.4.3 Querying Current Notifications of a Network Element.................................. 3-6

3.5 Customized Query.............................................................................................. 3-6

3.5.1 Querying Active Alarms by Customized Conditions..................................... 3-6

3.5.2 Querying History Alarms by Customized Conditions ................................. 3-14

3.5.3 Querying Notifications by Customized Conditions..................................... 3-18

3.6 Managing Query Conditions.............................................................................. 3-20

3.6.1 Modifying Customized Query Conditions.................................................. 3-20

3.6.2 Exporting Query Conditions to an XML File .............................................. 3-21

3.6.3 Importing Query Conditions From an XML File ......................................... 3-21

3.6.4 Copying and Pasting Query Conditions.................................................... 3-22

Chapter 4 Alarm Statistics......................................................................... 4-14.1 Overview of Alarm Statistics................................................................................ 4-1

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

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

4.4 Customized Statistics of History Alarms ............................................................... 4-7

4.4.1 Customizing the Basic Statistics of History Alarms...................................... 4-7

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

4.4.3 Creating a Template for Customized Statistics of History Alarms ............... 4-13

4.5 Viewing the Statistics of Active Alarms in Important Sites.................................... 4-15

4.6 Viewing Statistics on the Alarm Panel ................................................................ 4-17

4.7 Timing Statistic Task Management .................................................................... 4-17

4.7.1 Opening the Timing Statistic Task Management Tab ................................. 4-18

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

4.8 Timing Report Task Management ...................................................................... 4-21

4.8.1 Opening the Timing Export Task Management Tab ................................... 4-22

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

II

Chapter 5 Alarm and Notification Management....................................... 5-15.1 Overview of Alarm and Notification Management.................................................. 5-1

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

5.3 Cancelling the Acknowledgement of an Active Alarm............................................ 5-2

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

5.5 Adding a Comment to an Active Alarm................................................................. 5-4

5.6 Forwarding an Active Alarm via E-mail and Short Message................................... 5-5

5.7 Creating a Rule for an Active Alarm..................................................................... 5-8

5.8 Locating the Source Network Element of an Active Alarm on the TopologyGraph ............................................................................................................ 5-10

5.9 Viewing Active and History Alarms of a Board via Rack Diagram..........................5-11

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

5.11 Showing the Alarm Raising Time by Time Zone ................................................ 5-13

5.12 Viewing the Details of an Alarm ....................................................................... 5-13

5.13 Viewing and Supplementing the Handling Suggestions of an Alarm ................... 5-16

5.14 Viewing Related Rules of an Alarm.................................................................. 5-17

5.15 Exporting Alarms to a File ............................................................................... 5-18

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

5.17 Synchronizing Alarms ..................................................................................... 5-21

Chapter 6 Alarm Rule Management .......................................................... 6-16.1 Explanation of Alarm Rules ................................................................................. 6-1

6.2 Introduction to Alarm Rule Management .............................................................. 6-6

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

6.3.1 Alarm Acknowledging Rule ....................................................................... 6-8

6.3.2 Alarm Clearing Rule ................................................................................6-11

6.3.3 Alarm Filtering Rule................................................................................ 6-12

6.3.4 Alarm Delaying Rule............................................................................... 6-13

6.3.5 Alarm Merging Rule................................................................................ 6-15

6.3.6 Alarm Persisting Rule ............................................................................. 6-16

6.3.7 Alarm Counting Rule .............................................................................. 6-18

6.3.8 Alarm Forwarding Rule ........................................................................... 6-20

6.3.9 Alarm Masking Rule ............................................................................... 6-22

6.3.10 Alarm Triggering Script Rule.................................................................. 6-23

6.3.11 Alarm Restraining Rule by Network Element .......................................... 6-26

6.3.12 Alarm Restraining Rule by Network Element Type .................................. 6-27

6.3.13 Notification Filtering Rule ...................................................................... 6-30

Chapter 7 Handling Suggestion Management ......................................... 7-1

III

7.1 Introduction to Handling Suggestion Management ................................................ 7-1

7.2 Exporting Handling Suggestions to a File ............................................................. 7-2

7.3 Importing Handling Suggestions From a File ........................................................ 7-3

7.4 Searching for Handing Suggestions..................................................................... 7-3

7.5 Supplementing Handling Suggestions for an Alarm .............................................. 7-4

Chapter 8 Alarm Severity Management.................................................... 8-18.1 Introduction to Alarm Severity Management ......................................................... 8-1

8.2 Resetting the Severity Level of an Alarm.............................................................. 8-3

8.3 Creating a Severity Regrading Rule for Specific Managed Elements...................... 8-4

Chapter 9 Alarm Box Management ........................................................... 9-19.1 Alarm Box Introduction ....................................................................................... 9-1

9.2 Adding an Alarm Box.......................................................................................... 9-1

9.3 Modifying the Settings of an Alarm Box................................................................ 9-4

9.4 Enabling an Alarm Box ....................................................................................... 9-5

9.5 Disabling an Alarm Box ...................................................................................... 9-5

9.6 Deleting an Alarm Box ........................................................................................ 9-6

9.7 Refreshing the Settings of Alarm Boxes ............................................................... 9-6

Chapter 10 Preference Settings .............................................................. 10-110.1 Customizing an Alarm Code............................................................................ 10-1

10.2 Modifying the Cause Description of an Alarm ................................................... 10-3

10.3 Setting the Alarm Forward Template ................................................................ 10-5

10.4 Merging Intermittent Alarms ............................................................................ 10-6

10.5 Setting an Alarm Prompting Rule..................................................................... 10-7

10.6 Customizing Alarm Sounds and Colors ...........................................................10-10

10.7 Creating an Alarm-Suppressing Plan Task ......................................................10-12

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

Tables .............................................................................................................V

Glossary .......................................................................................................VII

IV

About This ManualThe NetNumenTM U31 R18 Unified Element Management System (NetNumen U31 orEMS) is a special network element management system that manages network elementsin radio access systems. By using NetNumen U31, users can configure and maintainindividual network elements, and manage radio access networks in a unified manner.NetNumen U31 provides the following management functions:

l Configuration managementl Fault managementl Performance managementl Topology managementl Security management

As an object-oriented system designed on the JAVA 2 platform Enterprise Edition (J2EE),NetNumen U31 provides unified standard interfaces to external devices.

Purpose

This operation guide provides instructions on fault management operations in theNetNumen U31 system.

Intended Audience

l Maintenance engineersl Debugging engineers

What Is in This Manual

Chapter Summary

Chapter 1, Overview of Fault

Management

Provides a general overview of the fault management system

of NetNumen U31, including fault management functions, fault

indication modes, alarm classification, alarm handling flow, and an

introduction to the fault management view.

Chapter 2, Alarm and

Notification Monitoring

Describes the alarm monitoring policies and methods, and provides

the instructions for monitoring alarms and notifications in different

ways.


Notification Query

Provides different methods for querying active alarms, history

alarms, and notifications.

Chapter 4, Alarm Statistics Describes the alarm statistics functions, gives the definitions

of timing statistic task and timing report task, and provides the

instructions for viewing, exporting, and saving the statistical results

of history alarms.

I

Chapter Summary


Notification Management

Describes the management operations that can be done on active

alarms, history alarms and notifications, such as acknowledge,

unacknowledge, clear, forward, export, and print active alarms.

Chapter 6, Alarm Rule

Management

Explains various alarm rules supported by NetNumen U31, and

provides the instructions for how to create each kind of alarm rule.

Chapter 7, Handling

Suggestion Management

Describes how to search for handling suggestions of a specific

alarm, how to export all handling suggestions to a file, and how to

supplement user-defined handling suggestions to an alarm.

Chapter 8, Alarm Severity

Management

Describes how to reset the severity levels of alarms.

Chapter 9, Alarm Box

Management

Provides a brief introduction to alarm box, and describes how to add

the information of an alarm box for sending concerned alarms to it.

Chapter 10, Preference

Settings

Provides instructions on setting the preference related to fault

management, for example, alarm sound, alarm color and alarm

forward template.

Reference List

l NetNumen U31 Unified Element Management System MML Terminal OperationGuide

l NetNumen U31 Unified Element Management System Configuration ApplicationOperation Guide

l NetNumen U31 Unified Element Management System Performance ManagementOperation Guide

l NetNumen U31 Unified Element Management System Security ManagementOperation Guide

l NetNumen U31 Unified Element Management System Topology ManagementOperation Guide

II

Chapter 1Overview of FaultManagementTable of Contents

Introduction to the Fault Management System............................................................1-1Fault Management Functions .....................................................................................1-3Fault Indication...........................................................................................................1-3Alarm Classification....................................................................................................1-4General Alarm Handling Flow.....................................................................................1-6Introduction to the Fault Management Window...........................................................1-7Implicit Prerequisites ................................................................................................1-10

1.1 Introduction to the Fault Management SystemThe fault management system, as a component of the Network Element ManagementSystem (EMS), is a system maintenance tool for the centralized monitoring of NetworkElements (NEs). It collects fault information from all kinds of elements in the managednetwork in near-real time, such as boards, links, databases, and servers, and thendisplays the collected fault information in the format of alarm or notification. The faultmanagement system helps the system administrator to quickly locate and removefailures in the managed network, and provides telecom operators, network managementdepartments and equipment vendors with correct, timely and necessary alarm data toensure the stable running of networks.

System Composition

The NetNumen U31 server, client and alarm box(es) 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 corporate witheach other to implement all kinds of fault management functions. Figure 1-1 illustratesthe relationships among them.

1-1

SJ-20110823134613-007|2011-09-22(R1.0) ZTE Proprietary and Confidential

NetNumen™ U31 R18 Fault Management Operation Guide

Figure 1-1 Composition of the Fault Management System

The functions of each component in the fault management system are described asfollows.

l Server

On the NetNumen U31 server (also called EMS server), operation and maintenanceprograms are running for the centralised management of network elements, thatis, equipment in the managed network. The EMS server is the core of the networkelement management system. Fault management is an important function setprovided by the EMS.

In addition, the EMS server configured with a Short Message Service (SMS) modulecan send alarm information to specific personnel via short message.

l Client

The NetNumen U31 client (also called EMS client) provides a Graphic User Interface(GUI) through which the system administrator can control the whole network elementmanagement system.

l Alarm Box

An alarm box is a tool used to indicate 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 TCP/IP. After receiving alarms,the alarm box displays them on an LCD screen, illuminates its alarm indicator lights,and produces alarm sounds.

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

l E-mail Server

The NetNumen U31 system can send alarm information to specific personnel viaE-mail when an E-mail server has been configured for the system.

1-2


Chapter 1 Overview of Fault Management

Note:

Before using the alarm information forwarding functions, you need to configure the alarmbox, SMS module, and E-mail server in the NetNumen Configuration Center. For detailedconfiguration instructions, refer to the later sections “Alarm Monitoring via Short Messageand E-mail” in Chapter 2 and “Adding an Alarm Box” in Chapter 9.

1.2 Fault Management FunctionsThe fault management system of NetNumen U31 provides a collection of faultmanagement functions for monitoring and processing alarms and notifications caused byfailures in the managed network. It supports the real-time monitoring of alarms, the queryof alarms by filtering conditions, and the display of alarms in multiple modes, for example,indicating alarms in sounds, colors, and on the screen of an alarm box.

Using the fault management system of NetNumen U31, you can

l acknowledge alarms,l cancel the acknowledgement of alarms,l filter alarms by customized conditions to determine the display of specific alarms on

the client GUI or an alarm box,l clear alarms from the active alarm list,l notify alarms to related personnel via Email or short message,l summarize the processing experience and save it as a suggestion to the alarm

handling suggestion library after successfully handling an alarm.

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

1.3.1 AlarmA fault is indicated in the form of alarm when it persists and affects the reliability andservices in the system. The alarm only disappears after the fault is removed. Immediatetroubleshooting is required when such faults occur because of their adverse impact on thesystem.

Alarms can be regarded as specific types of notifications indicating detected failuresor abnormal conditions in a network. In the NetNumen U31 system, each alarm has aunique alarm code, that is, a sequence number used to identify the alarm. In addition,the NetNumen U31 system also provides a series of standard alarm codes based oninternational standards. A standard alarm code generally indicates faults of the sametype. For example, alarm codes 198099803 (Link Broken Between OMM and NE) and

1-3



15010001 (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,for example, board reset and signaling overload. Such fault or event is generally causedby sudden environment change or other accidental factors, for example, a restart ora fake power failure of a board. No special handling is required because the fault orevent causing the notification can be automatically removed by the system. However, afrequently-reported notification needs your troubleshooting.

1.4 Alarm ClassificationAlarms are classified by different standards in the NetNumen U31 system. The followingsections describe the classification of alarms based on four standards: active status, faulttype, 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 offaults causing them.

l Active Alarm

An active alarm indicates the occurrence of a fault that has not been removed yet.

l History Alarm

A history alarm indicates the occurrence of a fault that has already been removed.

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 removed, this alarm turns into a history alarm, beingcleared from the active alarm list.

Note:

You can also forcibly clear an active alarm even the failure causing this alarm has not beenremoved. After being cleared, this active alarm turns into a history alarm.

1.4.2 Alarm Classification by Fault SeverityAlarms are divided into the following four classes depending on the severity of faultscausing these alarms.

l Critical Alarm

1-4



A critical alarm indicates a fault that causes the failure of system operation or serviceoffering. Immediate troubleshooting is required when a critical alarm is reported.

l Major Alarm

A major alarm indicates a fault that seriously impacts the proper running of the systemor reduces the capability of service offering. Removing corresponding fault to restorethe system as soon as possible is required when a major alarm occurs.

l Minor Alarm

Aminor alarm indicates a fault that slightly influences the proper running of the systemor reduces the capability of service offering. You are required to take measures toremove corresponding fault in time and prevent the occurrence of severer alarmswhen a major alarm occurs.

l Warning

A warning indicates a fault that has a potential or gradual impact on the proper runningof the system or the service offering capability. You are required to diagnose thewarning message and then take proper measures timely to remove correspondingfault and thus avoid severer alarms.

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 these alarms.

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 Alarml 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 these alarms. The resourcetypes supported by the NetNumen U31 system depend on the application packages thatare selected while you install the server and client software.

The following introduces the alarm classification in a NetNumen U31 system supportingGSM and WCDMA products.

l Alarms Raised by EMS Server

à Operation & Maintenance Center (OMC) alarms

1-5



à Performance threshold crossing alarms

à Public alarms of wireless products

l Alarms Raised by GSM Product

à Hardware platform alarms

à GSM alarms

à SDR alarms

à SDR-II public alarms

à GSM SDR-II alarms

l Alarms Raised by WCDMA Product

à Hardware platform alarms

à WCDMA RNC alarms

à WCDMA Node B alarms

à SDR alarms

à SDR-II public alarms

à WCDMA SDR-II alarms

1.5 General Alarm Handling FlowImmediate troubleshooting is required when alarms are displayed on the client GraphicUser Interface (GUI) of a network Element Management System (EMS) because alarmsindicate failures having adverse impacts on the network.

The following recommends a general handling flow for alarms on different severity levels.

l When a critical or major alarm is raised, contact the local office of ZTE and handle thealarm under the guidance of ZTE engineers.

l When a minor alarm or warning is raised, record the failure symptoms, and thenhandle the alarm according to the following instructions.1. View the detailed information of the alarm, including the alarm code, severity level,

description, and related components of the alarm.2. Analyze the alarm information to find the cause of the alarm and possible impact

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

If you fails to remove the failure, please contact the local office of ZTE for support.

1-6



1.6 Introduction to the Fault Management Window

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

Figure 1-2 Fault Management Window

1. Main menu2. Toolbar

3. Navigation pane4. Alarm information pane

1.6.2 Menus for Fault ManagementTwo menus on the menu bar of the client window provides commands for faultmanagement operations: Fault and Statistics. You can click appropriate commands onthe menus to use the corresponding fault management functions, as described in Table1-1.

Table 1-1 Menus for Fault Management

Command Function

Active Alarm Monitoring Monitors alarms.

Notification Monitoring Monitors notifications.

Active Alarm Monitoring by

NE

Monitors alarms by network element.

1-7



Command Function

Active Alarm Monitoring by

NE Type

Monitors alarms by network element type.

Query Active Alarms Queries active alarms.

Query History Alarms Queries history alarms.

Query Notifications Queries notifications.

History Alarm Basic Statistics Gets the basic statistic of history alarms.

History Alarm Busy-time

Statistics

Gets the statistic of history alarms in busy hours.

Timing Statistic Task

Management

Manages timing statistic tasks.

Timing Export Task

Management

Manages timing export tasks.

Suppress Plan Task

Management

Manages scheduled alarm suppressing tasks.

Setting This submenu 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 the flashing of alarm indication on the alarm

panel.

Synchronize Active Alarms Synchronizes active alarms from all network elements.

Synchronize History Alarms Synchronizes history alarms from all network elements.

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.3 Toolbar Buttons Related to Fault ManagementThe main toolbar in the client window provides some shortcut buttons related to faultmanagement functions. You can click them to open the corresponding management tabsquickly. Table 1-2 describes the functions of these buttons.

Table 1-2 Buttons Related to Fault Management on the Main Toolbar

Button Function

Monitors active alarms.

1-8



Button Function

Queries active alarms.

Queries history alarms.

Queries notifications.

Initiates the basic statistics of history alarms.

Initiates the statistics of history alarms in busy hours.

1.6.4 Navigation PaneThe navigation pane, being the base of fault management functions, organizes shortcutlinks in tree format for quick fault management, which are different from the topologicaltrees in topology management or other modules.

On the top of the navigation pane in the fault management view are three tabs:Management, NE Tree, and Statistic.

l Management

On the Management tab, a management tree organizes most fault managementfunctions in the form of tree. The nodes under the tree root indicate the correspondingfunctions. You can perform alarm query operations and some settings convenientlyvia the management tree.

l NE Tree

On the NE Tree tab, an NE tree organizes managed elements in the form of tree. Thenodes under the tree root indicate different functional units of the managed elements.Adjacent nodes under the tree are in parallel or hierarchical relationship. The NEtree demonstrates the real physical relationships among the functional units of eachmanaged element.

l Statistic

On the Statistic tab, a statistic tree organizes all available statistic methods in theform of tree. You can perform different statistical functions quickly by double-clickingthe corresponding nodes on the tree.

1.6.5 Alarm Information PaneThe alarm information pane is the major part of the fault management window. Thepane varies with the actual fault management functions, showing the alarm or notificationinformation you want to view.

1-9



1.7 Implicit PrerequisitesFor all operations subsequent to this section, the following prerequisites may be presumedto have been met.

l The NetNumen U31 client has been started and successfully connected to the server.l The NetNumen U31 server, the Operation and Maintenance Modules (OMMs) of

managed Network Elements (NEs), and the managed NEs are synchronous in time.l You have fault management permissions.l The Fault Management window is open on the client Graphic User Interface (GUI).

1-10


Chapter 2Alarm and NotificationMonitoringTable of Contents

Alarm Monitoring Policies ...........................................................................................2-1Alarm Monitoring Methods..........................................................................................2-2Monitoring Alarms in Real Time................................................................................2-10Monitoring Notifications in Real Time........................................................................2-11Monitoring Active Alarms by Network Element..........................................................2-12Monitoring Active Alarms by Network Element Type .................................................2-14Viewing Alarms on the Alarm Box.............................................................................2-16

2.1 Alarm Monitoring PoliciesAlarmmonitoring is an important function of the fault management system. When a fault orabnormal condition is detected, alarm information is generated and reported by the devicein failure. The fault management system receives the alarm information, and then forwardsit to an alarm box, or sends it to related personnel via short message or E-mail. In thisway, maintenance personnel can get the fault information in time and do troubleshootingimmediately.

Principle of Alarm Monitoring

The following gives a severity-based principle of alarm monitoring for timely alarmnotification and immediate troubleshooting.

l Forward critical and major alarms to an alarm box and related personnel via shortmessage to obtain immediate handling because such alarms may severely influenceservices.

l Display minor alarms and warnings on the Graphic User Interface (GUI) of NetNumenU31, or send them to related personnel via short message or E-mail.

Alarm Monitoring Policies

The following explains four commonly-used alarm monitoring policies. You can adopt oneor multiple policies at the same time to ensure in-time troubleshooting of faults.

l Severity-Based Priority Policy

When this policy is adopted, the system forwards alarms in turns according to theseverity levels of alarms. If multiple alarms of different severity levels are raised at

2-1



the same time, the system sends the alarms with the higher severity first, and thenthose with the lower severity to an alarm box or related personnel.

l First-Time Policy

This policy aims minimizing the adverse impact of faults on services. When thispolicy is adopted, the system immediately sends the alarms received from managedelements to an alarm box and related personnel via short message upon receivingthe alarm from a managed element.

l Multi-Receiver Policy

When the multi-receiver policy is adopted, the system sends the alarm informationto multiple receivers. This policy ensures that alarms can be handled immediatelyas long as one of the multiple receivers successfully receive the alarm information intime. It reduces the possibility that alarms are not handled in time.

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 down even one alarm forwarding way takes no effect.

2.2 Alarm Monitoring MethodsYou can use one of the following three methods to monitor alarms in a network accordingto the actual situation.

l Monitoring alarms via network element management systeml Monitoring alarms via alarm boxl Monitoring alarms via short message and E-mail

2.2.1 Alarm Monitoring via Network Element Management SystemThe NetNumen U31 system, that is, the network Element Management System (EMS),receives alarm information reported by managed network elements and detects alarmsraised in the system itself. It displays all detected alarms on the client GUI. The EMS canbe used to monitor the running status of a network. Therefore, you can conveniently queryand view all the alarms generated in the whole system on the GUI of the NetNumen U31system.

An advantage of this alarm monitoring method is that you can also view topologyinformation, configuration data, and performance data on the client GUI. By analysing thealarm information together with the other information, you can more easily locate the faultin the network.

2.2.2 Alarm Monitoring via Alarm BoxAn alarm box is a tool used to indicate alarm information fast and intuitively. It can beconnected to the NetNumen U31 system through a broadband network. The system

2-2


Chapter 2 Alarm and Notification Monitoring

transfers alarm information by TCP/IP to the alarm box. After receiving alarms, the alarmbox displays them on an LCD screen, illuminates its alarm indicator lights, and producesalarm sounds.

l The alarm box provides the details of received alarms on its LCD screen. You canscroll the details by pressing the scroll key.

l The alarm box supports both voice prompts and beep sounds for alarm indication.

In addition, the alarm box can forward the collected alarm notifications and alarm clearingnotifications to related personnel via short message by its built-in SMS module.

2.2.3 Alarm Monitoring via Short Message and E-mail

Function Description

The NetNumen U31 system can forward alarm information to related personnel viashort message and E-mail, such as maintenance engineers in local ZTE office, andmaintenance personnel of the telecom operator. The maintenance personnel receivesalarm notifications by cell phone or E-mail to know the running status of the network eventhey are not on field.

l An active alarm can be forwarded to specific personnel via short message or E-mail.For the detailed instructions, refer to the later section “Forwarding an Active Alarm viaE-mail and Short Message” in Chapter 5.

l An alarm forwarding rule can be created for automatic forwarding of active alarmsmeeting the specified conditions via short message or E-mail. For the detailedinstructions, refer to the later sections “Creating an Alarm Rule” and “AlarmForwarding Rule” in Chapter 6.

Prerequisite Configuration

To ensure the successful forwarding of alarm information via short message or E-mail,necessary parameters must be properly set in the NetNumen configuration center. You cancomplete this configuration during the installation of the NetNumen U31 server software,or start the NetNumen configuration center and complete the configuration separately.

The following describes how to start the NetNumen configuration center and setparameters for alarm forwarding functions on the NetNumen U31 server.

1. Log in to the AIX system on the NetNumen U31 server as omc user, change the currentdirectory to NetNumen Installation Directory/ems/uif/, and then run therunPlugCenter.sh file as follows:

$ runPlugCenter.sh

The NetNumen Configuration Center window opens, as shown in Figure 2-1. TheCommon Configuration node is selected by default in the left pane.

2-3



Figure 2-1 NetNumen Configuration Center

2. On the Server tab in the right pane, expand the Global Configuration node and thenthe Forward node, as shown in Figure 2-2.

Figure 2-2 Expanding the Forward Node

3. To configure the E-mail forwarding function, expand theMail Forward node, and thenclick each child node under Mail Forward to set all necessary parameters, as shownin Figure 2-3.

2-4



Figure 2-3 Expanding the Mail Forward Node

The following table describes the parameters that shall be set for E-mail forwardingfunction.

Parameter Description

Mail server IP Specifies the IP address of the E-mail server used for alarm

information transfer.

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

E-mail server. If Yes is selected, user name and password need tobe set.

Mail server username Specifies the user name used for login to the E-mail server when

authentication is required.

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

Mail server’s FromAddress Specifies the E-mail address from which the E-mail containing

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

4. To configure the short message forwarding function, click the Forward type node, andselect a forward type from the Value of config drop-down box, as shown in Figure 2-4.

2-5



Figure 2-4 Selecting the Forward Type Node

Note:l The default forward type is 4, that is, alarm short messages are sent to related

personnel via an alarm box connected to the NetNumen U31 system.l The forward type 5 (PRIVATE) is not supported now. The purpose of this forward

type is to send alarm short messages to related personnel via a private transferinterface. For example, the NetNumen U31 system forwards short messages toan Environment Monitor Board (EMB), which sent these short messages via aprivate interface that is customized on the requirements of an operator.

The following describes how to set the parameters when different types are selected.

l If 1 (MODEM) is selected, short messages containing alarm information will betransferred to related personnel via GSM MODEM. You need to expand theGSM Moden Forward node as shown in Figure 2-5, and then set necessaryparameters.

2-6



Figure 2-5 Expanding the GSM Moden Forward Node

The following table describes the parameters that shall be set for sending shortmessages via GSM MODEM.


Country code Specifies the country code of receivers, for example, “86”.

GSM Moden equipment

serials

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

The default value is COM1. The value format varies with different

operating systems.

à In the case of Windows operating system, type COM1 if the

SMS module is connected to serial port 1; type COM2 if the

SMS module is connected to serial port 2.

à In the case of Linux operating system, type /dev/ttyS0

if the SMS module is connected to serial port 1; type

/dev/ttyS1 if the SMS module is connected to serial port

2.

à In the case of UNIX operating system, type /dev/cua/a

if the SMS module is connected to serial port 1; type

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

2.

GSM part times Specifies the maximum number of segments to which a short

message can be divided when it contains too many characters.

The default value is 3.

2-7




GSM receiver number Specifies the cell phone numbers of receivers to whom short

messages can be sent. Use a comma to separate multiple cell

phone numbers.

The cell phone numbers set here are valid only when no cell

phone number of receivers is set in the NetNumen U31 system.

l If 2 (SMPP) is selected, short messages containing alarm information will betransferred to related personnel by Short Message Peer to Peer Protocol (SMPP).You need to expand the SMPP Forward node as shown in Figure 2-6, and thenset necessary parameters after getting the configuration information from yourservice provider.

Figure 2-6 Expanding the SMPP Forward Node

l If 3 (CMPP) is selected, short messages containing alarm information will betransferred to related personnel by ChinaMobile Point to Point (CMPP) protocol.You need to expand the CMPP Forward node as shown in Figure 2-7, and thenset necessary parameters after getting the configuration information from yourservice provider.

2-8



Figure 2-7 Expanding the CMPP Forward Node

l If 4 (Alarm box) is selected, short messages containing alarm information will betransferred to related personnel by an alarm box. You need to expand the AlarmBox Forward node as shown in Figure 2-8, and then set the IP address of thealarm box to be used.

Figure 2-8 Expanding the Alarm Box Forward Node

When this forward type is selected, it is unnecessary to set the country code,the allowable short message segments, and the cell phone number of receiversbecause:

à The country code of the alarm box will be used.

2-9



à The system automatically divides a short message into multiple segmentswhen the number of characters in the message exceeds the allowable one.

à The cell phone numbers of receivers are set in the NetNumen U31 system.

For detailed instruction of setting the above parameters, refer to the later sections“Forwarding an Active Alarm via E-mail and Short Message” in Chapter 5, and“Creating an Alarm Rule” and “Alarm Forwarding Rule” in Chapter 6.

5. Click Save All and then Close in the NetNumen Configuration Center window.6. Restart the NetNumen U31 server software to make the configuration effective.

2.3 Monitoring Alarms in Real TimeContext

By monitoring active and historical alarms in real time, you can get the latest alarminformation of the network elements managed by NetNumen U31.

Steps

To view the active alarms and historical alarms in real time, do one of the following in theclient window:

l On the menu bar, select Fault > Active Alarm Monitoring.l On the toolbar, click .l On the Management tab in the navigation pane, double-click the Active Alarm

Monitoring node.

– End of Steps –

Result

The Active Alarm Monitoring tab opens in the left pane of the client window, as shown inFigure 2-9. The upper part of the tab shows the current alarms, while the lower part showsthe historical alarms.

2-10



Figure 2-9 Active Alarm Monitoring Tab

1. Active alarms 2. Historical alarms

2.4 Monitoring Notifications in Real TimeContextBy monitoring notifications, you can get the information of the latest events occurring inthe network and determine whether it is necessary to process these events for networkstability.

StepsTo view real-time notifications in the client window, do the following:

l On the menu bar of the client window, select Fault > Notification Monitoring.


ResultThe Notification Monitoring tab opens in the right pane of the client window, as shownin Figure 2-10.

2-11



Figure 2-10 Notification Monitoring Tab

2.5 Monitoring Active Alarms by Network ElementContext

The system can count the active alarms of all severity levels for each Network Element(NE) in themanaged network. In addition to view the statistical information of active alarms,including unacknowledged alarms and all alarms, you can monitor the active alarms of aspecific NE.

The following example shows how to monitor the active alarms of a specific NE in the clientwindow.

Steps

1. Open the Active Alarm Monitoring by NE tab as shown in Figure 2-11 by performingone of the following two operations.l On the menu bar of the client window, select Fault > Active Alarm Monitoring

by NE.l Double-click the Active Alarm Monitoring by NE node on the Management tab

in the navigation pane.

2-12



Figure 2-11 The Tab of Alarm Monitor by NE

2. On the Alarm Monitor by NE tab, expand the NE tree, locate the NE whose activealarms you want to view, and then perform an operation below to view the details.l If you want to monitor all active alarms of the NE, double-click the corresponding

cell on the total column.l If you want to monitor the active alarms of a specific severity, double-click the

corresponding cell on the column of a severity, for example, Minor.


Result

A new tab opens to show all active alarms of this NE (Figure 2-12), or the active alarms ofa specific severity (Figure 2-13).

2-13



Figure 2-12 Monitoring Active Alarms of an NE

Figure 2-13 Monitoring Active Minor Alarms of an NE

2.6 Monitoring Active Alarms by Network Element TypeContext

The system can count the active alarms of all severity levels in the managed network byNetwork Element (NE) type. In addition to view the statistical information of active alarmsby NE type, you can monitor the active alarms raised by all NEs of the same type.

2-14



The following example shows how to monitor the active alarms raised by all NEs of thesame type.

Steps

1. Open the Active Alarm Monitoring by NE Type tab as shown in Figure 2-14 byperforming one of the following two operations.l On the menu bar of the client window, select Fault > Active Alarm Monitoring

by NE Type.l Double-click the Active Alarm Monitoring by NE Type node on the

Management tab in the navigation pane.

Figure 2-14 The Tab of Alarm Monitor by NE Type

2. On the Alarm Monitor by NE Type tab, expand the resource type tree to find theNE type whose active alarms you want to view, and then do an appropriate actionaccording to the actual need as follows:l If you want to monitor all active alarms of the NE type, double-click the

corresponding cell on the total column.l If you want to monitor the active alarms of a specific severity, double-click the

corresponding cell on the column of a severity, for example, Minor.


Result

A new tab opens to show all active alarms raised by all NEs of this NE type (Figure 2-15),or the active alarms of a specific severity (Figure 2-16).

2-15



Figure 2-15 Monitoring Active Alarms of an NE Type

Figure 2-16 Monitoring Active Minor Alarms of an NE Type

2.7 Viewing Alarms on the Alarm BoxPrerequisites

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

Context

When an alarm box is used, you can directly view the information of some concernedalarms on the alarm box. Upon receiving alarms, the alarm box produces alarm soundsand turns on the corresponding indicator lights, prompting the occurrence of alarms.

2-16



The following describes how to view alarm information on the LCD screen of an alarm box.

Steps

1. On the initialization screen of the alarm box, press FUN.

2. On the main screen, press to activate the function menu.

3. Press the up or down arrow to select the Alarm Querying menu, and then press Ok.


Result

The information of the latest alarm is displayed on the screen. You can use the up or downarrow to browse the information of other received alarms.

2-17



This page intentionally left blank.

2-18


Chapter 3Alarm and Notification QueryTable of Contents

Overview of Alarm and Notification Query ..................................................................3-1Querying Active Alarms..............................................................................................3-2Querying History Alarms.............................................................................................3-3Querying Notifications ................................................................................................3-5Customized Query......................................................................................................3-6Managing Query Conditions .....................................................................................3-20

3.1 Overview of Alarm and Notification QueryThe NetNumen U31 system supports the query of active alarms, history alarms, andnotifications in different ways.

TheManagement tab in the navigation pane of the fault management view provides someshortcut links for quick query of alarms and notifications under the Alarm Query node,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

On the NE Tree tab in the navigation pane of the fault management view, you can queryactive alarms, history alarms, or notifications of a specific NE by choosing 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

In addition, you can customize query conditions to query specific active alarms, historyalarms, or notifications as needed, and save the customized query conditions as atemplate, which can be used for later alarm or notification query with the same queryconditions.

3-1



3.2 Querying Active Alarms

3.2.1 Querying All Active Alarms

Context

The following describes how to query all active alarms in the NetNumen U31 system.

Steps

On the Management tab in the navigation pane, do one of the following:

l Double-click the All Active Alarms node on the Management Tree.l Right-click the All Active Alarms node on the Management Tree, and then click

Execute.


Result

An All Active Alarms tab appears in the client window, listing all active alarms in thesystem.

3.2.2 Querying Unacknowledged Active Alarms

Context

The following describes how to query all unacknowledged active alarms in the NetNumenU31 system.

Steps


l Double-click the Unacknowledged Active Alarms node on the Management Tree.l Right-click theUnacknowledged Active Alarms node on theManagement Tree, and

then click Execute.


Result

An Unacknowledged Active Alarms tab appears in the client window, listing allunacknowledged active alarms in the system.

3-2


Chapter 3 Alarm and Notification Query

3.2.3 Querying the Active Alarms of a Network Element

Context

On the NE Tree tab in the navigation pane of the fault management view, you can doan appropriate action to query the active alarms of a specific Network Element (NE) asfollows.

Steps

1. Expand the NE tree, and find the NE whose active alarms you want to query.

2. Right-click the NE, and then choose an appropriate command on the shortcut menuto query the active alarms you want.

For example, clickActive AlarmsWithin One Hour to view the active alarms reportedby the NE within the latest one hour.


Result

A new tab appears in the client window, listing the active alarms of the NE.

3.3 Querying History Alarms

3.3.1 Querying All History Alarms Within One Day

Context

The following describes how to query all history alarms within the latest 24 hours in theNetNumen U31 system.

Steps


l Double-click the History Alarms Within One Day node on the Management Tree.l Right-click the History Alarms Within One Day node on theManagement Tree, and

then click Execute.


Result

A History Alarms Within One Day tab appears in the client window, listing all historyalarms within the latest 24 hours.

3-3



3.3.2 Querying All History Alarms Within Three Days

Context

The following describes how to query the history alarms within the latest 72 hours in theNetNumen U31 system.

Steps


l Double-click the History AlarmsWithin Three Days node on theManagement Tree.l Right-click the History Alarms Within Three Days node on the Management Tree,

and then click Execute.


Result

A History Alarms Within Three Days tab appears in the client window, listing all historyalarms within the latest 72 hours.

3.3.3 Querying the History Alarms of a Network Element

Context

On the NE Tree tab in the navigation pane of the fault management view, you can do anappropriate action to query history alarms of a specific Network Element (NE) as follows.

Steps

1. Expand the NE tree, and find the NE whose history alarms you want to query.

2. Right-click the NE, and then select an appropriate command on the shortcut menu toview the history alarms you want.

For example, click History Alarms Within One Day to view the history alarms of theNE within the latest 24 hours.


Result

A new tab appears in the client window, listing the history alarms of the NE.

3-4



3.4 Querying Notifications

3.4.1 Querying Notifications Within One Day

Context

The following describes how to query all notifications within the latest 24 hours in theNetNumen U31 system.

Steps


l Double-click the Notifications Within One Day node on the Management Tree.l Right-click the Notifications Within One Day node on the Management Tree, and

then click Execute.


Result

A Notifications Within One Day tab appears in the client window, listing all notificationswithin the latest 24 hours.

3.4.2 Querying Notifications Within Three Days

Context

The following describes how to query all notifications within the latest 72 hours in theNetNumen U31 system.

Steps


l Double-click the Notifications Within Three Days node on the Management Tree.l Right-click the NotificationsWithin Three Days node on theManagement Tree, and

then click Execute.


Result

ANotificationsWithin Three Days tab appears in the client window, listing all notificationswithin the latest 72 hours.

3-5



3.4.3 Querying Current Notifications of a Network Element

Context

To query the current notifications of a specific Network Element (NE), do the following onthe NE Tree tab in the navigation pane of the fault management view.

Steps

1. Expand the NE tree, and find the NE whose notifications you want to query.

2. Right-click the NE, and then click Current Notifications.


Result

A new tab appears in the client window, listing the current notifications of the NE.

3.5 Customized Query

3.5.1 Querying Active Alarms by Customized Conditions

Context

In addition to querying active alarms by conditions predefined by the system, you cancustomize query conditions according to the actual need to get the active alarms youwant, including NE type, alarm location, alarm code, standard alarm code, occurrencetime, acknowledgement time or unacknowledgement time, alarm type, alarm severity level,acknowledgement status, IP address of an NE, the name of user who acknowledges orunacknowledges the alarm, additional information, comment, alarm ID, and alarm visibility.Some query conditions are optional, that is, the system considers that all items are selectedif you do not select any item. For example, if you do not specify the alarm type(s), thesystem considers that you want to query the alarms of all types.

The following example shows how to customize query conditions for querying specificactive alarms.

Steps

1. In the fault management view of the client window, perform one of the following actionsto open the Query Active Alarms dialog box.l On the menu bar, select Fault > Query Active Alarms.l On the toolbar, click .l On the Management tab, right-click Active Alarms, and then click New Active

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

click New Active Alarm Query.

3-6



2. On the Location tab as shown in Figure 3-1, select NE type(s) from the NE Typedrop-down box as needed, select the element(s) whose active alarms you want toquery on the NE tree, and use the arrow buttons to add the selected elements to theright list box, as shown in Figure 3-1.

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

Note:

An alarm raised by an element may be reported to the EMS by another element. Forexample, a board in a device raises an alarm. But this alarm is reported by the deviceto the EMS. To query such an alarm, you can select the device or the board whenselecting the element on the NE tree.

The following table describes the functions of arrow buttons on the Location tab.

Button Description Remarks

Used to add one or multiple selected nodes. A single selected node is

marked with a file icon ( ).

Used to add the selected node(s) and all their

child nodes.

A selected node with all its child

nodes is marked with a folder

icon ( ).

3-7



Button Description Remarks

Used to remove one or multiple added nodes. -

Used to remove all added nodes. -

Used to execute filter: displaying NEs

matching the keywords you enter.

-

3. If you want to query active alarms with specific alarm codes, click the Alarm Code tab,expand the Resource Type tree to find the alarm code(s) you want, click the alarmcode(s), and then click to add the selected alarm code(s) to the right list box, asshown in Figure 3-2.

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

Tip:l To quickly find the alarm codes you want, you can enter a keyword in the Enter

filter text box, and then click .l To select all alarm codes at a time, click .l The Exclude Mode can be selected for adding those alarm codes that are not

selected on the resource type tree.

3-8



4. If you want to query active alarms of specific standard alarm codes, click the ProbableCause tab in the Query Active Alarms dialog box, select the standard alarm codeson the Probable Cause tree, and then click , as shown in Figure 3-3.

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

Note:

The NetNumen U31 system summarizes the probable causes of all alarms basedon international specifications and organizes them as standard alarm codes on theProbable 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. For example,the alarm codes 198099803 and 1501001 correspond to the same standard alarmcode 566 (Connection establishment error).

Caution!

Be sure that appropriate alarm codes and standard alarm codes having mappingrelations are selected on the Alarm Code and Probable Cause tabs. Or else, thesystem will fail to query alarms you want.

3-9



5. If you want to query active alarms raised, acknowledged, or unacknowledged duringa specific period, click the Time tab in the Query Active Alarms dialog box, select atime zone, and then set the period(s) under Raised Time, and/or (Un)ACK Time, asshown in 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 the NEsreporting the alarms and the time zone support is enabled in the NetNumen U31system, you can determine which time zone is based before setting the time period foralarm query.

l NE Wall-Time: When the NE time zone is selected, you can set a time periodbased on the time zone of the NEs for querying the alarms raised in this period.

l Client Time Zone (GMT+08:00) When the client time zone is selected, you canset a time period based on the time zone of the client for querying alarms raised,acknowledged or unacknowledged in this period.

6. Click the Others tab in the Query Active Alarms dialog box, as shown in Figure 3-5.Next, perform appropriate operations as needed.

3-10



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

l If you want to query active alarms of specific type(s), select the alarm type(s)under Alarm Type.

l If you want to query active alarms of specific severity level(s), select the severitylevel(s) under Perceived Severity.

l If you want to query active alarms according to their acknowledgement status,select Acknowledged and/or Unacknowledged under ACK State.

l If you want to query active alarms of an NE whose IP address you have known,type the IP address under NE IP.

l if you want to query active alarms, click the Advanced button, and then setparameters in the pop-up Advanced dialog box as shown in Figure 3-6 accordingto the following conditions:

à User ID: the name of the user who do the acknowledge or unacknowledgeaction.

à Remark: a string in the additional information of active alarms.

à Comment: a string in the comments of active alarms.

à Alarm ID: the alarm ID.

Visible/Invisible: the visibility of active alarms.

3-11



Figure 3-6 Advanced Dialog Box for Active Alarm Query

7. Click OK.


Result

A Query Active Alarms tab appears in the client window, listing the query result of activealarms, as shown in Figure 3-7.

3-12



Figure 3-7 Query Result of Active Alarms

Follow-Up Action

To save the customized query conditions as a query template, click on the toolbar ofthe Query Active Alarms tab, and then type a name for the query template in the pop-upNew Query dialog box.

To reset conditions for querying the active alarms, click on the toolbar.

To monitor the historical alarms in the query result of active alarms, click . If any ofthe active alarms is cleared either automatically or manually, the corresponding alarm isdisplayed in the History Alarms pane, as shown in

3-13



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

Note:

When you attempt to close the Query Active Alarms tab after viewing the active alarmsyou want, aConfirm dialog box will open, asking whether you want to save the customizedquery conditions. You can click Yes, and type a name for the query template in the pop-upQuery Active Alarms dialog box to save the query conditions.

After the customized query conditions are saved as a query template, you can right-clickit under the Custom Query node and then click Execute to initiate a query based on thesame query conditions.

3.5.2 Querying History Alarms by Customized Conditions

Context

In addition to querying history alarms by conditions predefined by the system, you cancustomize query conditions according to the actual need to get the history alarms youwant. Some query conditions are optional, that is, the system considers that all items areselected if you do not select any item. For example, if you do not specify the alarm type(s),the system considers that you want to query the alarms of all types.

The following example shows how to customize query conditions for querying specifichistory alarms.

3-14



Note:

The setting of some conditions for querying history alarms is similar to that for queryingactive alarms. This section does not repeat the explanation of the same conditions. Seethe previous section “Querying Active Alarms by customized Conditions” for the detailedexplanation of them.

Steps

1. In the fault management view of the client window, do one of the following to open theQuery History Alarms dialog box, as shown in Figure 3-9.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.

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

2. On the Location tab of the Query History Alarms dialog box, select NE type(s) fromthe NE Type drop-down box as needed, select the element(s) whose history alarmsyou want to query on the NE tree, and use the arrow buttons to add the selectedelements to the right list box.

3-15



Note:

An alarm raised by an element may be reported to the EMS by another element. Forexample, a board in a device raises an alarm. But this alarm is reported by the deviceto the EMS.

Suppose you select an NE on this tab. Then the system will query history alarmsreported by this NE (The Match By Additional NE check box is not selected). If youselect theMatch By Additional NE check box at the same time, the system will queryhistory alarms raised by this NE.

3. Set parameters on the Alarm Code tab, Probable Cause tab, Time tab, and theOthers tab according to description in the previous section “Querying Active Alarmsby Customized Conditions”.

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.

4. On the Others tabclick the Advanced button. The Advanced dialog box appears, asshown in Figure 3-10.

Figure 3-10 The Advanced Dialog Box

Set the query conditions as needed. The conditions include:

l Clear Type

3-16



l (Un)Ack User ID: specifies the user who (un)acknowledged alarms.l Clear User ID: specifies the user who performed alarm-clearing operations.l Remark: additional information.l Comment: alarm comment.l Alarm IDl Query maximum count: restricts the maximum number of query records.

5. To display other alarm clearing types, click the More button in the Advanced dialogbox. The Extended Clear Type dialog box appears, as shown in Figure 3-11. Selectthe options as needed, and click OK.

Figure 3-11 The Extended Clear Type Dialog Box

6. In the Advanced dialog box, click OK.

7. In the Query History Alarms dialog box, click OK. The alarm information panedisplays the history alarms according to the conditions you set, as shown in .

3-17



Figure 3-12 Query Result of Historical Alarms


Follow-Up Action

You can also save the customized query conditions as a query template for later use. Forthe detailed instructions, see the follow-up actions in the previous section “3.5.1 QueryingActive Alarms by customized Conditions”.

3.5.3 Querying Notifications by Customized Conditions

Context

In addition to querying notifications by conditions predefined by the system, you cancustomize query conditions according to the actual need to get the notifications you want.

The following example shows how to customize query conditions for querying specificnotifications.

Steps

1. On the menu bar of the client window, click Fault > Query Notifications.

The Query Notifications dialog box opens, as shown in Figure 3-13.

3-18



Figure 3-13 The Query Notifications Dialog Box

2. On the Location tab, select the NE type from the NE type drop-down list box, clickthe NE(s) to be queried in the NE list box, and then click to add the NE(s).

3. Click the Notification Code tab, select the notification codes in the left list box andthen click .

4. Click the Others taband then set the time range and/or additional information as thequery conditions.

5. Click OK.


Result

The alarm information pane show the query result.

Follow-Up Action

You can also save the customized query conditions as a query template for later use. Forthe detailed instructions, see the follow-up actions in the section “Querying Active Alarmsby Customized Conditions”.

3-19



3.6 Managing Query Conditions

3.6.1 Modifying Customized Query Conditions

Prerequisites

You have saved the customized query conditions as a query template.

Context

After some customized query conditions are saved as a query template under the CustomQuery node on the Management tab in the navigation pane of the client window, you canmodify the conditions when necessary.

Note:

For the detailed instructions on how to set specific query conditions, see the previoussections “Querying Active Alarms by Customized Conditions”, “Querying History Alarmsby Customized Conditions”, or “Querying Notifications by Customized Conditions”.

Steps

1. On the Management tab in the navigation pane, right-click the query template whosequery conditions you want to modify, and then click Edit.

Tip:

You can also execute the query template first, and then click on the toolbar of thequery result tab.

2. In the pop-up dialog box, modify the query conditions, and then click OK.

The system queries required alarms or notifications according to the new queryconditions and refreshes the query result in the client window.

3. Do one of the following to save the modification of query conditions.l Right-click the query template under the Management tab again, and then click

Save.l Click on the toolbar of the query result tab.


3-20



3.6.2 Exporting Query Conditions to an XML File

Context

Both the default query conditions preset by the NetNumen U31 system and queryconditions customised by users can be exported to an XML file.

The following procedure describes how to export the preset query conditions (HistoryAlarms Within One Day) to an XML file as an example.

Steps

1. On theManagement tab in the navigation pane, right-click theHistory AlarmsWithinOne Day node, and then click Export Condition.

2. In the pop-up Save dialog box, type or select a directory where you want to save theexported query conditions from the Save in drop-down box, change the file name inthe File name box as needed, and then click the Save button.


Result

An XML file containing the exported query conditions appears under the specified directory.

3.6.3 Importing Query Conditions From an XML File

Prerequisites

Before you begin this procedure, make sure that the format of query conditions defined inthe XML file you want to import meets the requirement of the NetNumen U31 system.

Note:

To know the required format of query conditions in an XML file, you can open an XML filecontaining query conditions that are exported from the NetNumen U31 system. For how toexport query conditions, see the previous section “Exporting Query Conditions to an XMLFile”.

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 following procedure describes how to import a predefined XML file for creating a querytemplate.

3-21



Steps

1. On the Management tab in the navigation pane, right-click the My Query node underCustom Query, and then click Import Condition.

2. In the pop-up Open dialog box, select the directory where the XML file is saved fromthe Look in drop-down box, select the XML file you want to import, and then click theOpen button.

An Import Query dialog box opens, prompting you to type a name for the importedquery template.

3. In the Import Query dialog box, type a name in the Query Name box, and then clickOK.


Result

A query template appears under the Custom Query node on the Management tab in thenavigation pane.

3.6.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 following procedure describes how to copy the query conditions of the queryUnacknowledged Active Alarms as an example.

Steps

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

2. Right-click the My Query node under Custom Query, and then click Paste.


Result

The same query template (Unacknowledged Active Alarms) appears under the CustomQuery node on the Management tab. You can rename this query template, and modifythe query conditions in this template to create a new query template based on the existingquery conditions.

3-22


Chapter 4Alarm StatisticsTable of Contents

Overview of Alarm Statistics .......................................................................................4-1Setting the Default Conditions for History Alarm Statistics ..........................................4-2Getting the Statistic Data of History Alarms by a Predefined Template........................4-5Customized Statistics of History Alarms .....................................................................4-7Viewing the Statistics of Active Alarms in Important Sites .........................................4-15Viewing Statistics on the Alarm Panel.......................................................................4-17Timing Statistic Task Management ...........................................................................4-17Timing Report Task Management .............................................................................4-21

4.1 Overview of Alarm StatisticsThe NetNumen U31 system supports the statistics of alarms. The statistical result canbe displayed in the format of table, bar chart, and pie chart on the client GUI. The alarmstatistics functions provided by NetNumen U31 can be classified into the following groups:

l History alarm statistics based on predefined counting rulesl History alarm statistics based on customized counting rulesl Timing task management related to alarm statisticsl Statistics of active alarms in important sites

History Alarm Statistics Based on Predefined Counting Rules

You can view the statistical results of alarm frequency and duration based on differentpredefined counting rules, including:

l Alarm frequency statistics by network elementl Alarm frequency statistics by network element typel Alarm frequency statistics by alarm codel Alarm frequency statistics by timel Alarm frequency and duration statistics by groupl Alarm frequency and duration statistics by alarm-acknowledging user

4-1



Note:

The system counts all history alarms raised during the latest five days by default whenno special statistic conditions are specified. If you want to get the statistical result ofspecific history alarms, you can set appropriate conditions in advance before doingactions to view the statistical result. For the detailed instruction for how to set the defaultstatistical conditions, see the later section “Setting the Default Conditions for HistoryAlarm Statistics”.

History Alarm Statistics Based on Customized Counting Rules

In addition to the predefined counting rules, you can customize specific counting rules toget the statistical information of history alarms you want to know, including:

l Basic statistics of the frequency and average duration of history alarmsl Busy-time statistics of the frequency and average duration of history alarms

The customized counting rules can be saved as templates for convenient viewing ofstatistical results later.

Timing Task Management Related to Alarm Statistics

The system also specifies two kinds of tasks to periodically output and save specificstatistical results and specific alarms in files. They are:

l Timing statistic taskl Timing report task

You can create, view, modify, activate, suspend, and delete these tasks.

Statistics of Active Alarms in Important Sites

The system supports the classification of important sites into VIP sites, Class-B sites andClass-C sites with their importance descending. You can view the statistical information ofactive alarms in these sites separately.

4.2 Setting the Default Conditions for History AlarmStatistics

Context

If you want to get the statistical result of specific history alarms, you can set appropriateconditions in advance to specify the history alarms you want to count. After you setting theconditions, the system will first query the required history alarms and then counting thesealarms by predefined rules to provide the statistical results you want.

4-2


Chapter 4 Alarm Statistics

The following procedure describes how to set the default statistic conditions for countingspecific history alarms.

Steps

1. In the navigation pane of the fault management view, double-click Default StatisticSetting on the Statistic tab to open the Default Statistic Setting dialog box.

2. On the Location tab of the Default Statistic Setting dialog box, select a networkelement type from the NE Type drop-down box, click the NE(s) whose history alarmsyou want to count on the NE tree, and then click appropriate arrow buttons to selectthem, as shown in Figure 4-1.

Figure 4-1 Default Statistic Setting Dialog Box (Location Tab)

3. If you want to count history alarms with specific alarm codes, click the Alarm Codetab in the Default Statistic Setting dialog box, and then select the alarm codes youwant, as shown in Figure 4-2.

4-3



Figure 4-2 Default Statistic Setting Dialog Box (Alarm Code Tab)

4. Click the Others tab in the Default Statistic Setting dialog box, and then doappropriate actions according to the actual need as follows:l To count history alarms raised during a specific period, set the period under

Raised Time.l To count history alarms of specific alarm types, select the corresponding types

under Alarm Type.l To count history alarms of specific severity levels, select the corresponding

severity levels under Original Severity.l To count history alarms acknowledged or unacknowledged by a specific user, type

the user name in the (Un)ACK User ID box.

Figure 4-3 shows an example of theOthers tab in the Default Statistic Setting dialogbox.

4-4



Figure 4-3 Default Statistic Setting Dialog Box (Others Tab)

5. Click OK.


4.3 Getting the Statistic Data of History Alarms by aPredefined Template

Prerequisites

If you want to get the statistic data of specific history alarms, make sure that you have setappropriate conditions as described in the previous section “Setting the Default Conditionsfor History Alarm Statistics”.

Context

On the Statistic tab in the navigation pane of the fault management view, the systemprovides some shortcut links for quick history alarm statistics based on predefinedstatistical templates.

l By NE: The system counts the frequency of history alarms in each NE, and lists theNEswith Top 5, Top 10, Top 20, or Top 100 alarm frequency in addition to the frequencysum.

l By NE Type: The system counts the frequency of history alarms in all NEs of each NEtype, and lists the NE types with Top 5, Top 10, Top 20, or Top 100 alarm frequencyin addition to the frequency sum.

4-5



l By Alarm Code: The system counts the frequency of history alarms by alarm code,and lists the alarm codes with Top 5, Top 10, Top 20, or Top 100 alarm frequency inaddition to the frequency sum.

l By Time: The system counts the frequency of history alarms by their generation time,for example, each day in a week, each day in a month, or each hour in a day. Thestatistical result arranges the statistical frequency in descending order.

l By Group: The system counts the frequency or duration of history alarms in each NEby alarm severity.

l By Ack User: The system counts the frequency or duration of history alarms by userswho acknowledged these alarms.

The following example shows how to get the alarm codes that the frequencies of historyalarms corresponding to these alarm codes rank Top 10 in the fault management view.

Steps

On the Statistic tab in the navigation pane of the fault management view, do one of thefollowing:

l Double-click the Top10 node under By Alarm Code.l Right-click the Top10 node under By Alarm Code, and then click Execute.


Result

A new tab appears to show the Top 10 alarm codes and the corresponding alarm frequency,as shown in Figure 4-4.

Figure 4-4 Alarm Frequency Statistics By Alarm Code_Top 10

4-6



4.4 Customized Statistics of History Alarms

4.4.1 Customizing the Basic Statistics of History Alarms

Context

The basic statistic of history alarms includes the statistics of alarm frequency and alarmduration. You can customize a statistical template and conditions according to thestatistical information you want to know.

Note:

A predefined and saved template with appropriate counting rule and conditions for basicstatistics of history alarms can also be used directly for customized statistics of historyalarms.

The following is an example of how to get and view the statistical result of specific historyalarms by setting a statistical template.

Steps

1. In the client window, do one of the following:l Select Fault > History Alarm Basic Statistics on the menu bar.l Select Statistics > History Alarm Statistics > History Alarm Basic Statistics

on the menu bar.l Click on the toolbar.

The Alarm Basic Statistic dialog box opens, as shown in Figure 4-5.

4-7



Figure 4-5 The Alarm Basic Statistic Dialog Box (Basic Tab)

2. On the Basic tab, set a statistical template as follows:

a. UnderStatistic Type, select the type of data you want to count: Alarm Frequencyor Average Period (average alarm duration).

b. Under Statistic Row, select the object(s) which will be displayed as the rows inthe statistical result table. Two statistic objects can be selected. For example,Alarm Type and Alarm Code are selected.

c. Under Statistic Column, select Severity if you want to count the history alarms ofdifferent severity levels and the severity has not been selected as a statistic objectunder Statistic Row.

d. Under View Setting, select Maximum rows allowed and then type a number ifyou want to limit the number of rows displayed in the statistical result.

After setting the statistical template, you can preview the format of the statistical resultunder Preview. Figure 4-6 shows an example of a statistical result preview.

Figure 4-6 Preview of Statistical Result

4-8



3. Click the Condition tab in the Alarm Basic Statistic Template dialog box, and thenset parameters on the three tabs: Location, Alarm Code, Others, as shown in Figure4-7.

Figure 4-7 Alarm Basic Statistic Template dialog box (Condition Tab)

Note:

For the detailed instructions on setting the parameters (query conditions), see thesection “Setting the Default Conditions for History Alarm Statistics” in this chapter.

After setting the template for basic statistics of historical alarms, you can click Saveto save the template. The template will appear under Customized Statistics on theStatistic tab in the navigation pane.

4. Click OK.


Result

A History Alarm Basic Statistics tab appears in the client window, showing the statisticalresult in a table, as shown in Figure 4-8.

4-9



Figure 4-8 Basic Statistical Result of History Alarms

Follow-Up Action

On the upper part of the History Alarm Basic Statistics tab showing the statistical resultis a toolbar. You can use the buttons on the toolbar to manage the statistical result, asdescribed in Table 4-1.

Table 4-1 Toolbar Buttons for Managing the Statistical Result

Button Operation

Start a new statistics after resetting the current statistical template and

conditions.

Export the statistical result to a CSV, XML, TXT, HTM, PDF, or XLS file.

Print the statistical result.

Refresh the statistical result.

Show the statistical result in the format of bar chart.

Show the statistical result in the format of pie chart.

4.4.2 Customizing the Busy-Time Statistics of History Alarms

Context

Busy time, or busy hour, refers to a 60-minute period during which the total traffic load inthe network is heavy in a day. The system offers a special function for counting historyalarms in busy hours because alarms raised in such hours generally need more concern.

In the NetNumen U31 system, you can specify the busy hours in a day, and then setstatistical conditions for counting the frequency and average duration of history alarms inbusy time.

4-10



Note:

A predefined and saved template with appropriate counting rule and conditions forbusy–time statistics of history alarms can also be used for customized statistics of historyalarms in busy hours.

The following is an example of how to get and view the statistical result of history alarmsin busy hours by setting a counting rule.

Steps

1. In the client window, do one of the following:l Choose Fault > History Alarm Busy-time Statistics on the menu bar.l Choose Statistics > History Alarm Statistics > History Alarm Busy-time

Statistics on the menu bar.l Click on the toolbar.

The History Alarm Busy-time Statistic dialog box opens, as shown in Figure 4-9.

Figure 4-9 History Alarm Busy-time Statistic Dialog Box (Basic Tab)

2. On the Basic tab, set a counting rule as follows:

a. UnderStatistic Type, select the type of data you want to count: Alarm Frequencyor Average Period (average alarm duration).

4-11



b. Under Effective Time, select the busy hour(s).

All hours, being highlighted, are selected by default. You can click the hours thatare not busy hours to cancel the selection.

c. Under View Setting, select Maximum rows allowed and then type a number ifyou want to limit the number of rows displayed in the statistical result.

3. Click the Condition tab to open it. Next, set parameters on the three tabs: Location,Alarm Code, and Others.

Note:

For the detailed instructions of setting the statistical conditions, refer to the section“Setting the Default Conditions for History Alarm Statistics” in this chapter.

After setting the template for busy-time statistics of historical alarms, you can clickSave to save the template. The template will appear under Customized Statisticson the Statistic tab in the navigation pane.

4. Click OK.


Result

AHistory AlarmBusy-time Statistics tab appears in the alarm information pane, showingthe statistical result of busy-hour history alarms in table format, as shown in Figure 4-10.

Figure 4-10 Statistical Result of History Alarms in Busy Hours

4-12



Follow-Up Action

On the upper part of the History Alarm Busy-time Statistics tab showing the statisticalresult is a toolbar. You can use the buttons on the toolbar to manage the statistical result.For the detailed description of the toolbar buttons, see the previous section “Customizingthe Basic Statistics of History Alarms” in this chapter.

4.4.3 Creating a Template for Customized Statistics of HistoryAlarms

Context

A template can be created to specify the counting rule and statistical conditions in advance.This template can be used conveniently for the statistics of concerned history alarms atany time you want without setting statistical conditions repeatedly. Two kinds of statisticstemplates are supported:

l History alarm basic statistics templatel History alarm busy-time statistics template

Three methods can be used to create a statistics template. The following proceduredescribes these three methods with an example of how to create a history alarm basicstatistics template.

Steps

l Method 1:

a. On the Statistic tab in the navigation pane of the fault management view,right-click the Customized Statistics node, and then click New History AlarmBasic Statistic Template.

The New History Alarm Basic Statistic Template dialog box appears, as shownin Figure 4-11.

Figure 4-11 New History Alarm Basic Statistic Template Dialog Box

b. Type a name for the new template in the Template Name box, and then click OK.

c. In the pop-up Alarm Basic Statistic dialog box, set a counting rule and statisticalconditions on the Basic and Condition tabs.

4-13



Note:

For detailed instructions on setting a counting rule and statistical conditions forbasic statistic of history alarms, see the previous section “Customizing the BasicStatistics of History Alarms” in this chapter.

d. Click OK.

l Method 2:

The prerequisite of this method is that you have customized the basic statistics ofhistory alarms as described in the section “Customizing the Basic Statistics of HistoryAlarms”, and the statistical result is displayed on a History Alarm Basic Statisticstab.

a. On the History Alarm Basic Statistics tab, click on the toolbar.

b. In the pop-up Alarm Basic Statistic Template dialog box, modify the existingcounting rule and/or statistical conditions if the existing ones do not meet yourrequirements.

c. Click the Save button. In the pop-up Save As dialog box, type a template name,and then click OK.

l Method 3:

The prerequisite of this method is that the XML file containing the template informationis available on your client.

a. On the Statistic tab in the navigation pane of the fault management view,right-click the Customized Statistics node, and then click Import StatisticTemplate.

b. In the pop-up Open dialog box, select the directory where the XML file is locatedfrom the Look in drop-down box, select the XML file, and then click the Openbutton.

c. In the pop-up Save As dialog box, type a new name if you want to use anothertemplate name, and then click OK.


ResultA new template appears under the Customized Statistics node on the Statistic tab inthe navigation pane.

Follow-Up ActionYou can manage an existing statistics template by right-clicking it on the Statistic tab andthen selecting an appropriate menu item, as described in Table 4-2.

4-14



Table 4-2 Shortcut Menu Items for Managing Statistics Template

Shortcut Menu Item Operation

Execute Run the statistics template to get the statistical result.

Edit Modify the counting rule and/or statistical conditions specified in the

statistics template.

Delete Delete the statistics template.

Rename Rename the statistics template.

Save Save the modification of the statistics template. This button is only

activated after the statistics template has been edited.

Save As Save the statistics template as another template with a different name.

Export Statistic Template Export the statistics template to an XML file.

4.5 Viewing the Statistics of Active Alarms in ImportantSites

Prerequisites

The important sites that you concern most have been set as VIP sites, Class-B sites orClass-C sites according to the priorities.

Note:

If you want to focus on some important sites, you can set them as VIP sites, Class-B sitesor Class-C sites and count alarms occurring in these sites separately.

To set a site as VIP site, Class-B site or Class-C site, you can do one of the following:

l Select Configuration > MML Terminal on the menu bar, select the site on the NEtree and then enter appropriate commands on the MML terminal to set the priority ofthe site.

l Select Configuration > Wireless Config Application > VIP NodeB Priority Queryand Set on the menu bar, and then set the priority of the sites you concern.

For the detailed instruction on how to set a site as VIP site, Class-B site, or Class-C site,see NetNumen U31 R58 Unified Element Management System MML Terminal OperationGuide or NetNumen U31 R58 Unified Element Management System ConfigurationApplication Operation Guide.

4-15



Context

The system supports the statistics of active alarms in VIP sites, Class-B sites, and Class-Csites by hour. You can view the statistical results of active alarms raised during:

l the latest hourl the hour before the latest hourl the hour before the latest two hoursl the hour before the latest three hoursl the hour before the latest four hoursl the hour before the latest five hours

The following procedure describes how to view the statistics of active alarms in importantsites.

Steps

1. Select the statistics of sites at a specific priority level.l To view the statistics of active alarms in VIP sites, select Fault > VIP Site Alarm

Statistics on the menu bar of the client window.l To view the statistics of active alarms in Class-B sites, select Fault > Class B Site

Alarm Statistics on the menu bar of the client window.l To view the statistics of active alarms in Class-C sites, select Fault > Class C

Site Alarm Statistics on the menu bar of the client window.

2. A tab appears in the client window, showing the statistical results of active alarms.Figure 4-12 shows an example of the VIP Site Alarm Statistics tab, on which thestatistical results of active alarms during six periods are displayed in table format.

Figure 4-12 VIP Site Alarm Statistics

On the VIP Site Alarm Statistics tab, the numbers of alarms at different levels arerefreshing in real time.

4-16



3. (Optional) To export the alarm statistics of each NE to a specified XLS document, click, and the Save dialog box appears. Set the file name and path, and click Save in

the dialog box.

4. To view the detailed active alarms of a VIP site during a specific period, double-clicka row in the corresponding table. A tab will appear, listing the active alarms raised inthe VIP site during the period.


4.6 Viewing Statistics on the Alarm PanelContextThe alarm panel displays the statistics of alarms at different security levels by theiracknowledgement status.

Steps1. On the main menu, select Fault > Alarm Panel. TheAlarm Panel dialog box appears,

as shown in Figure 4-13.

Figure 4-13 Alarm Panel

The Alarm Panel shows the statistics of acknowledged and unacknowledged alarmsat different security levels.

By default, the alarm level icons are flashing. To stop their flashing status, click theStop Flash button. To start flashing again, click the Flash button.


4.7 Timing Statistic Task ManagementA timing statistic task specifies a schedule for running a statistical template (predefinedor customized) periodically and outputting the statistical results as files (CSV, XML, XLS,or TXT files) to a specified directory on the NetNumen U31 server. You can use a timingstatistic task to count concerned history alarms periodically and open the result files savedon the server to view and analyze the statistical results.

4-17



A timing statistic task can be run by day, by week, by month, or by a customized cycle.

l By day: The task runs at 5:00 A.M. every day.l By week: The task runs at 5:00 A.M. every Monday.l By month: The task runs at 5:00 A.M. on the first day every month.l Customized cycle: The task runs at the specified time every day, week, or month.

4.7.1 Opening the Timing Statistic Task Management Tab

Context

Before creating a timing statistic task or managing existing timing statistic tasks, you needto open the Timing Statistic Task Management tab in the client window.

Steps

To open the Timing Statistic Task Management tab, do one of the following:

l On the menu bar, select Fault > Timing Statistic Task Managementl On the menu bar, select Statistics > History Alarm Statistics > Timing Statistic

Task Management .


Result

The Timing Statistic Task Management tab appears in the client window, as shown inFigure 4-14. The upper part of the Timing Statistic TaskManagement tab lists all statistictasks. The lower part lists the running result of the selected timing statistic task.

Figure 4-14 Timing Statistic Task Management Tab

4-18



4.7.2 Creating a Timing Statistic Task

Context

You can create a timing statistic task to collect the statistical information of concernedhistory alarms periodically and save them in file format on the NetNumen U31 server.

The following example shows how to create a timing statistic task.

Steps

1. On the Timing Statistic Task Management tab, click on the toolbar above the AllStatistic Tasks list.

The Statistic Task dialog box opens, as shown in Figure 4-15.

Figure 4-15 Statistic Task Dialog Box

2. In the Task Name box, type a name for the task to be created.

3. From the Template Name drop-down box, select a statistical template you want touse.

4-19



Tip:

You can click View to view the details of the selected template.

4. In the Begin Time and End Time combo boxes, set the begin time and end time forthe new task as needed.

5. From the Task Status drop-down box, select an initial status for the new task: Activate(Active) or Suspend (Suspended).

6. Select a file type (CSV, XML, XLS, or TXT) for the output of statistical results.

When XLS is selected, you can select Format Template and click Select FormatTemplate to select a template for formatting the statistical results in the generatedfiles.

Note:

For the description of Excel templates, refer to NetNumen U31 R58 Unified ElementManagement System Performance Management Operation Guide.

7. Under Task execution plan, select a running cycle for the new task: By day, Byweek, By month, or Custom.

If Custom is selected, set the specific task plan in the activated Custom ExecutionTime area, as shown in Figure 4-16.

Figure 4-16 Custom Execution Time Area

8. To set the forwarding parameters, click the Forward Settings button, and the ForwardSettings dialog box. You can set parameters to forward the task execution result toan E-mail address or to an IP address via FTP.

9. Click OK.


4-20



Result

The created timing statistic task appears in the list of All Statistic Tasks. The system willexecute the timing statistic task according to the scheduled time. And after the executionof a timing statistic task, you can view its result in the list of Statistic Task Execute Resultafter clicking the task in the list of All Statistic Tasks.

Follow-Up Action

For the created timing statistic task, you can use different buttons on the toolbar abovethe All Statistic Tasks list to perform the corresponding operations as needed. Table 4-3describes the functions of these toolbar buttons.

Table 4-3 Toolbar Buttons for Managing Timing Statistic Tasks

Button Function

Modifies the timing statistic task.

Deletes the timing statistic task when it is suspensive.

Activates the timing statistic task when it is suspensive.

Suspends the timing statistic task when it is active.

Refreshes the list of timing statistic tasks.

The system automatically stores the statistical result files on the server. You can also savethese files to a specified directory on your client by selecting the files in the Statistic TaskExecute Result list and then clicking on the toolbar.

4.8 Timing Report Task ManagementA timing report task specifies a schedule for outputting and saving specific active alarms orhistory alarms as CSV files under a specified directory on the NetNumen U31 server. Youcan use a timing report task to periodically collect the active or history alarms you concern.

A timing report task can be run by day, by week, by month, or by a customized cycle.

l By day: The task runs at 5:00 A.M. every day.l By week: The task runs at 5:00 A.M. every Monday.l By month: The task runs at 5:00 A.M. on the first day every month.l Customized cycle: The task runs at the specified time every day, week, or month.

4-21



4.8.1 Opening the Timing Export Task Management Tab

Context

Before creating a timing Export task or managing existing timing Export tasks, you needto open the Timing Export Task Management tab in the client window.

Steps

To open the Timing Export Task Management tab, do the following:

l On the menu bar, select Fault > Timing Export Task Management .


Result

The Timing Export Task Management tab appears in the client window, as shown inFigure 4-17. On the upper part of the Timing Export Task Management tab is the list ofall timing export tasks, while on the lower part is the list of running result of the selectedtiming export task.

Figure 4-17 Timing Export Task Management Tab

4.8.2 Creating a Timing Export Task

Context

You can create a timing Export task to periodically collect the concerned active or historyalarms and save them as CSV files on the NetNumen U31 server for analysis.

The following example shows how to create a timing export task.

4-22



Steps

1. On the Timing Export Task Management tab, click on the toolbar above the AllTiming Report Alarm Tasks pane.

The Timing Export Alarm Task dialog box opens, as shown in Figure 4-18.

Figure 4-18 Timing Export Alarm Task Dialog Box (Basic Tab)

2. In the Task Name box, type a name for the timing Export task to be created.

3. Select the type of alarms you want to collect: Active Alarms or History Alarms.

4. In the Begin Time and End Time combo boxes, set the begin time and end time forthe new task as needed.

5. From the Task Status drop-down box, select an initial status for the new task: Activeor Suspend.

6. Under Task execution plan, select a running cycle for the new task: By day, Byweek, By month, or Custom.

If Custom is selected, set the specific task plan in the activated Custom ExecutionTime area, as shown in Figure 4-19.

4-23



Figure 4-19 Custom Execution Time Area

Note:

The NetNumen U31 system can support a limited number of tasks at the same time.Outnumbered tasks are waiting in a queue for execution. Therefore, setting the customexecution time is recommended to arrange different tasks in a way that avoid taskqueueing.

7. To set the forwarding parameters, click the Forward Settings button, and the ForwardSettings dialog box. You can set parameters to forward the task execution result toan E-mail address or to an IP address via FTP.

8. Click the Condition tab, and then set the query conditions on the Location, AlarmCode, Probable Cause, Time, and Others sub-tabs, as shown in Figure 4-20.

4-24



Figure 4-20 Timing Export Alarm Task Dialog Box (Condition Tab)

Note:

For detailed instruction of how to set specific query conditions, see the previous section“Querying Active Alarms by Customized Conditions” or “Querying History Alarms byCustomized Conditions” in Chapter 3 Alarm and Notification Query.

9. Click OK.


Result

The created timing Export task appears in the list of All Timing Export Alarm Tasks. Thesystem will execute the timing export task according to the scheduled time. And after thetiming export task has been executed, you can view its result in the list of Timing ExportTask Execute Result after clicking the task in the list of All Timing Export Alarm Tasks.

Follow-Up Action

For the created timing Export task, you can use an appropriate button on the toolbar ofthe All Timing Export Alarm Tasks list to modify, activate, suspend, or delete the task asneeded.

4-25



The system automatically stores the alarm Export files on the server. You can also savethese files to a specified directory on your client by selecting the files in the Timing ExportTask Execute Result list and then clicking on the toolbar.

4-26


Chapter 5Alarm and NotificationManagementTable of Contents

Overview of Alarm and Notification Management .......................................................5-1Acknowledging an Active Alarm .................................................................................5-2Cancelling the Acknowledgement of an Active Alarm .................................................5-2Clearing an Active Alarm ............................................................................................5-3Adding a Comment to an Active Alarm .......................................................................5-4Forwarding an Active Alarm via E-mail and Short Message........................................5-5Creating a Rule for an Active Alarm............................................................................5-8Locating the Source Network Element of an Active Alarm on the Topology Graph ....5-10Viewing Active and History Alarms of a Board via Rack Diagram..............................5-11Viewing History Alarms Related to an Active Alarm ..................................................5-12Showing the Alarm Raising Time by Time Zone........................................................5-13Viewing the Details of an Alarm................................................................................5-13Viewing and Supplementing the Handling Suggestions of an Alarm .........................5-16Viewing Related Rules of an Alarm ..........................................................................5-17Exporting Alarms to a File ........................................................................................5-18Printing Alarms.........................................................................................................5-19Synchronizing Alarms...............................................................................................5-21

5.1 Overview of Alarm and Notification ManagementIn the NetNumen U31 system, you can manage active alarms, history alarms, andnotifications displayed in the client window after you perform a monitoring or query action.

Note:

For the instructions of monitoring and querying alarms and notifications, see Chapter2 Alarm and Notification Monitoring and Chapter 3 Alarm and Notification Query in thismanual.

The allowable management operations are different for active alarms, history alarms, andnotifications. Right-click an active alarm, history alarm, or notification, and you can findthe permitted operations on the shortcut menu.

5-1



In addition to the operations supported by the shortcut menu, you can export and printalarms and notifications by clicking and on the toolbar.

5.2 Acknowledging an Active AlarmPrerequisitesYou are monitoring active alarms in the system or have successfully queried some activealarms.

ContextWhen a new alarm is received from a managed element, it is displayed as“Unacknowledged” in the alarm list. You can change the acknowledgement status of thisalarm into “Acknowledged”, indicating that you have known the occurrence of this alarm.

Steps1. In the alarm list displayed on the client window, right-click the unacknowledged alarm

you want to acknowledge, and then click Acknowledge.

Tip:

To acknowledgemultiple alarms at the same time, use the CTRL or SHIFT key to selectmultiple alarms, and then right-click any selected alarm, and select Acknowledgefrom the shortcut menu.

2. In the pop-up Alarm acknowledge dialog box, type a comment when necessary, andthen click OK.


ResultThe acknowledgement status of the alarm changes from Unacknowledged toAcknowledged. The system records the information related to the acknowledgementaction, including the action time, the user doing this action, and the input comment.

5.3 Cancelling the Acknowledgement of an ActiveAlarm

PrerequisitesYou are monitoring active alarms in the system or have successfully queried some activealarms.

5-2


Chapter 5 Alarm and Notification Management

Context

You can cancel the acknowledgement of an active alarm to change its status from“Acknowledged” to “Unacknowledged” if you do not want to handle it immediately.

Steps

1. In the alarm list displayed on the client window, right-click the acknowledged alarmyou want to unacknowledge, and then click Unacknowledge.

Tip:

To cancel the acknowledgement of multiple alarms at the same time, use the CTRLor SHIFT key to select the alarms, and then right-click any selected alarm, and selectUnacknowledge from the shortcut menu.

2. In the pop-up Alarm unacknowledge dialog box, type a comment when necessary,and then click OK.


Result

The acknowledgement status of the alarm changes from Acknowledged toUnacknowledged. The system records the information related to the cancellation action,including the action time, the user doing this action, and the input comment.

5.4 Clearing an Active AlarmPrerequisites

You are monitoring active alarms in the system or have successfully queried some activealarms.

Context

An active alarm is automatically cleared from the active alarm list and then moved to thehistory alarm list after the failure causing this alarm is removed. The active alarm can alsobe forcibly cleared from the active alarm list even the failure causing it still exists.

5-3



Note:

If an active alarm meets the conditions specified in a predefined clearance rule, the systemwill automatically clear this alarm and put it into the history alarm list upon receiving it fromthe managed element. For a description of alarm clearance rule, see Chapter 6 AlarmRule Management.

Steps

1. In the alarm list displayed on the client window, right-click the active alarm you wantto clear, and then click Clear.

Tip:

To clear multiple alarms at the same time, select the alarms first, and then right-clickany selected alarm, and select Clear from the shortcut menu.

2. In the pop-up Confirm dialog box, click OK.


Result

The cleared alarm disappears from the active alarm list, turning into a history alarm. Thesystem records the information related to the clearance action, including the action timeand the user doing this action.

5.5 Adding a Comment to an Active AlarmPrerequisites

You are monitoring active alarms in the system or have successfully queried some activealarms.

Context

If you want to add some information to an active alarm, for example, an explanation orspecial note, you can add a comment to this alarm.

Steps

1. In the alarm list displayed on the client window, right-click the active alarm that youwant to add information to, and then click Comment.

5-4



Tip:

To add the same comment to multiple alarms at the same time, select the alarms first,and then right-click any selected alarm, and select Comment from the shortcut menu.

2. In the pop-up Comment dialog box, type the information, and then click OK.


Result

The system records the information related to the comment action, including the actiontime, the user performing this action, and the comment.

5.6 Forwarding an Active Alarm via E-mail and ShortMessage

Prerequisites

To ensure the successful forwarding of an active alarm, make sure that:

l The communication between the NetNumen U31 server and the Short MessageService (SMS) center is normal if you want to forward the active alarm via shortmessage.

l The communication between the NetNumen U31 server and the mail server is normalif you want to forward the active alarm via Email.

l You have obtained the phone numbers and/or E-mail addresses of the persons whomthe active alarm needs be forwarded to.

Context

You can forward an active alarm via short message and E-mail to notify related personnelof this alarm so as to ensure the in-time handling of the alarm.

Steps

1. In the alarm list displayed on the client window, right-click the active alarm you wantto forward, and then click Forward.

The Forwarding Setup dialog box opens, as shown in Figure 5-1.

5-5



Figure 5-1 Forwarding Setup Dialog Box

2. Type E-mail address(es) in the Email box, and phone number(s) in the Phone box.

Note:

Be sure to separate two adjacent E-mail addresses and phone numbers by a commawhen typing multiple E-mail addresses and phone numbers.

If the E-mail and phone number information of the persons have been set in the system,you can do the following to set the E-mail addresses and phone numbers:

a. Click the Address button to open the Select Users dialog box.

b. In the Available users list box, select the user(s) you want, and then click theEmail and/or Phone button to add them to the Selected users list box, as shownin Figure 5-2.

5-6



Figure 5-2 Select Users Dialog Box

c. Click OK.

Note:

For how to set the information of a user, including E-mail address and phone number,see NetNumen U31 R18 Unified Element Management System Security ManagementOperation Guide.

3. On the Forward by Email and Forward by SMS tabs, edit the subject and contentsof the Email and short message as needed.

Note:

The default subject and contents of E-mail and short message is determined by apredefined forward template. You can modify the forward template to change thedefault subject and contents you want to forward by choosing Fault > Setting >Forward Template Setting on the menu bar of the client window.

For detailed instructions of setting the forward template, see the later section “Settingthe Alarm Forward Template” in Chapter 10 Preference Settings.

4. Click OK.


5-7



Result

The system sends an E-mail and a short message containing the alarm information to thespecified person(s).

5.7 Creating a Rule for an Active AlarmContext

You can create an alarm management rule based on the information of an existing activealarm. The attributes of this alarmwill be inherited in the created rule, including the location,alarm code, and other attributes (for example, alarm type, severity level, and the IP addressof the NE).

The system supports the creation of the following alarm management rules:

l Alarm Acknowledging Rulel Alarm Clearing Rulel Alarm Filtering Rulel Alarm Delaying Rulel Alarm Merging Rulel Alarm Counting Rulel Alarm Forwarding Rulel Alarm Triggering Script Rule

The following procedure describes a general procedure for how to create an alarmacknowledging rule based on an existing active alarm as an example.

Note:

For the explanations of different alarm rules and the detailed instructions for setting specificrules, see Chapter 6 Alarm Rule Management.

Steps

1. In the active alarm list, right-click the active alarm you want, and then click CreateRules > Alarm Acknowledging Rule.

The Alarm Acknowledging Rule dialog box opens, as shown in Figure 5-3.

5-8



Figure 5-3 Alarm Acknowledging Rule dialog box (Basic Tab)

2. On the Basic tab, set the basic information for the new rule to be created as follows:

a. In the Name box, type a name for the new rule.

b. In the Description box, type additional information for the new rule as needed.

c. Select an initial status for the new rule: Activate or Suspend.

d. Select when the system shall do the acknowledgement action:l While Reporting: acknowledge an alarm meeting the specified conditions

when the system receives it from the managed element.l While Restoring: acknowledge an alarm meeting the specified conditions

when the alarm is cleared due to the removal of the failure causing it.

3. Click the Condition tab, as shown in Figure 5-4. The location, alarm code, and otherconditions are already set according to the information of the selected active alarm.You can modify the conditions on the corresponding sub-tabs as needed.

5-9



Figure 5-4 Alarm Acknowledging Rule dialog box (Condition Tab)

4. Click OK.


Result

A new alarm acknowledging rule is created. The system will automatically acknowledgeactive alarms according to the conditions set in the rule.

5.8 Locating the Source Network Element of an ActiveAlarm on the Topology Graph

Context

You can locate the source Network Element (NE) of an active alarm on the topology graphas follows.

Steps

l In the active alarm list, right-click the active alarm, and then click Locating Alarm toNE.


5-10



Result

The client window switches to the topology management window, where the source NE ofthe active alarm is highlighted with a white frame on the topology graph. Click this NE iconon the topology graph, and then you can view all active alarms raised by this NE on thelower part of the topology management window.

Note:

For more information about the topology management view, refer to NetNumen U31 R18Unified Element Management System Topology Management Operation Guide.

5.9 Viewing Active and History Alarms of a Board viaRack Diagram

Context

If an active alarm is reported by a board of a network element, you can open the rackdiagram of the NE via this alarm. Then you can view the active alarms or history alarmsof specific boards on the rack.

Steps

1. In the active alarm list, right-click the active alarm, and then clickOpen Rack Diagram.

A Rack Diagram dialog box opens, presenting the board layout on the rack of thenetwork element raising this active alarm, as shown in Figure 5-5.

5-11



Figure 5-5 Rack Diagram

If some alarm(s) are raised in a board, the little block on the upper part of the boardblinks in a certain colour to indicate the occurrence of alarm(s). The colour of the blockindicates the highest severity of alarms occurring in the board.

2. Move the cursor on a board with alarms. The information of the board, as well asthe statistical information of alarms in this board is displayed in a call-out, includingthe rack No., shelf No., slot No., board type, and the counts of acknowledged andnon-acknowledged alarms at different severity levels.

3. Right-click a board with a blinking block, and then click Show Active Alarm or ShowHistory Alarm to view all active or history alarms of the board in the pop-up dialogbox.


5.10 Viewing History Alarms Related to an Active AlarmContext

You can check the related history alarms of an active alarm, analyze and handle the activealarm according to the information of these history alarms.

5-12



Steps

l In the active alarm list, right-click the active alarm you want, and then click RelatedHistory Alarm.


ResultA Related History Alarm tab appears in the client window to list all related history alarmsof the selected active alarm. If the selected active alarm has no related history alarm, aConfirm box appears, prompting that no matching record is found.

5.11 Showing the Alarm Raising Time by Time ZoneContextIf the NetNumen U31 client you are using is located in a different time zone from that ofthe managed NEs, the occurrence time of reported alarms varies with the selected timezone. The reported alarms can be displayed on the client GUI based on the time zone ofthe client or the NEs.

Steps

l In the alarm list, right-click any alarm, point to Time Show Style and then click NETime Zone or Client Time Zone.l If NE Time Zone is selected, the occurrence time of alarms displayed in the list

is based on the time zone of the NEs reporting these alarms.l If Client Time Zone is selected, the occurrence time of alarms displayed in the

list is based on the time zone of the client.


5.12 Viewing the Details of an AlarmContextViewing the details of an active alarm helps you to locate and handle the failure causingthis alarm. In addition to active alarms, you can view the details of history alarms andnotifications in the same way. The following only describes how to view the details of anactive alarm for example.

Steps1. In the active alarm list, find the active alarm you want to view, and then perform one

of the following operations:l Double-click the active alarm.l Right-click the active alarm, and then click Detail.

5-13



A dialog box opens, showing the details of the active alarm on the Detail tab. Thedetails of an active alarm is shown in Figure 5-6. The details of an historical alarm isshown in .

Figure 5-6 Details of an Active Alarm

5-14



Figure 5-7 Details of a Historical Alarm

The Detail tab lists the detailed information of the alarm, including acknowledgementstate, perceived severity, NE, location in the NE, standard alarm code, alarm code,occurrence time, NE type, alarm type, probable cause, product type, additionalinformation, clearance time, alarm ID, service information, and the other informationrelated to actions on the alarm that is recorded by the system.

Note:l The fields NE and Location specifies the location of the element reporting this

alarm; while the fields Additional NE and Additional Location specifies thelocation of the element raising this alarm.

l The ADMC Alarm field in the details indicates whether the equipment canautomatically report an alarm clearing message. If the field value is “Yes”, theequipment does not report an alarm clearing message when an fault disappears.In this case, you have to manually clear the alarm information.

2. To view the predefined handling suggestions and/or add user-defined suggestions tothe alarm, click the Handling Suggestions tab.

3. After viewing the alarm details, click Close.


5-15



Follow-Up Action

In the dialog box showing the details of an active alarm, you can do the operationsdescribed in Table 5-1 by using the corresponding buttons.

Table 5-1 Operations in the dialog box Showing the Alarm Details

Button Operation

Click this button to show the details of the previous alarm.

Click this button to show the details of the next alarm.

Click this button to acknowledge the unacknowledged alarm.

Click this button to cancel the acknowledgement of the acknowledged

alarm.

To add a comment on the alarm:

1. Click this button to open a Comment dialog box.2. Type your comment in the text box and click OK.

To forcibly clear the active alarm, click this button and click OK in the

pop-up Confirm dialog box.

To forward the alarm to related personnel:

1. Click this button to open the Forwarding Setup dialog box.

2. Select the forwarding mode (Email or/and Phone) and type theE-mail address or/and phone number of the person.

3. Click OK.

To export the details of the alarm to an XML, TXT, HTM, PDF, XLS,

or CSV file:

1. Click this button to open a Save dialog box.2. In the Save dialog box, select a directory where you want to save the

file, type a name for the file, and then click the Save button.

Click this button to copy the details of the alarm to a clipboard.

5.13 Viewing and Supplementing the HandlingSuggestions of an Alarm

Context

The system provides some handling suggestions for each alarm. You can try to handle thefailure causing the alarm according to the suggestion, and supplement other informationor suggestions to the alarm according to your handling experience, for example, additionalprobable causes, analysis, and repair actions.

5-16



Steps

1. In the alarm list, right-click the alarm you want to view, and then click HandlingSuggestions.

A dialog box opens, showing the default handling suggestions of the alarm, as shownin Figure 5-8.

Figure 5-8 Handling Suggestions of an Alarm

2. View the probable causes of the alarm and suggested handling measures.

If you want to add more analysis and suggestion to the alarm, type the texts in theUser-defined Suggestions box, and then click the Save button.

3. Click Close.


Follow-Up Action

For the usage of the other buttons in the dialog box, refer to the pervious section “Viewingthe Details of an Alarm”.

5.14 Viewing Related Rules of an AlarmContext

By checking the related rules of an alarm, you can know what rules are applied on thealarm. When the alarm meets the conditions specified by a rule, the system takes thecorresponding action on the alarm. For example, if an alarm acknowledgement rule relatedto the alarm specifies that the alarm should be automatically acknowledged when the

5-17



corresponding fault condition is cleared, the acknowledgement status of the alarm turnsinto “Acknowledged” when the fault causing this alarm is removed.

Steps

l In the alarm list, right-click the alarm you want to view, and then click Related Rules.


Result

l If some alarm rule(s) is effective on this alarm, a Related Rules dialog box opens,listing the rule(s) affecting this alarm, as shown in Figure 5-9.

Figure 5-9 Related Rules dialog box

In the Related Rules dialog box, you can double-click the corresponding row to viewthe detailed specification of the alarm rule. In addition, you can modify, delete, enableor disable a related rule by clicking appropriate buttons on the toolbar.

l If no alarm rule is effective on this alarm, aConfirm box opens, prompting the absenceof related rule.

5.15 Exporting Alarms to a FileContext

You can export all current alarms, history alarms or notifications displayed on the faultmanagement view, or the alarm/notification information in some columns to an XML, TXT,XLS, PDF, HTM, or CSV file. If you want to export specific alarms or notifications, querythem by setting conditions to list them on the fault management view first. For how to queryalarms and notifications, see Chapter 3 Alarm and Notification Query.

The following procedure describes how to export history alarms within the latest 24 hoursto a file for example.

5-18



Steps

1. On the Management tab in the navigation pane, double-click History Alarms WithinOne Day. TheHistory AlarmsWithin One Day tab appears on the fault managementview, listing all history alarms within the latest 24 hours.

2. On the toolbar of the History Alarms Within One Day tab, click .

3. In the pop-up Save dialog box, type or select a directory where you want to save thefile from the Save in drop-down box, select a file type form the Files of type drop-downbox, type a name for the file in the File name box, and then click Save.

4. In the pop-up Confirm box, click OK.


5.16 Printing AlarmsPrerequisites

The connection between the NetNumen U31 server and the printer you want to use isnormal.

Context

You can print active alarms, history alarms or notifications displayed on the faultmanagement view of the client window. If you want to print specific alarms or notifications,query them by setting conditions to list them on the fault management view first. For howto query alarms and notifications, see Chapter 3 Alarm and Notification Query.

The following procedure describes how to print history alarms within the latest 24 hoursfor example.

Steps

1. On the Management tab in the navigation pane, double-click History Alarms WithinOne Day. TheHistory AlarmsWithin One Day tab appears on the fault managementview, listing all history alarms within the latest 24 hours.

2. On the toolbar of the History Alarms Within One Day tab, click

The Print Setup dialog box opens, as shown in Figure 5-10.

5-19



Figure 5-10 Print Setup dialog box (General Tab)

3. On the General tab, select the printer to be used from the Name drop-down box, setthe print range and the number of copies you want.

4. Click the Page Setup tab, and then set the paper size, orientation, and the margins,as shown in Figure 5-11.

Figure 5-11 Print Setup dialog box (Page Setup Tab)

5. Click the Advance tab, and then select the print style in the list box as shown in Figure5-12.

5-20



Figure 5-12 Print Setup dialog box (Advanced Tab)

Three print styles are optional: Recommend Setup, Typical Setup, and SimpleSetup. The displayed items vary with the selected print style. For example, whenRecommend Setup is selected, the printer name, footer, date, and grid will be printedon the alarm report and the column name will be printed out on every page. You canalso select or clear some items to be displayed on the alarm report as needed.

6. After completing the print setup, click Print.

Tip:

Before printing out the alarms, you can preview the alarm report by clicking PreviewAll.


5.17 Synchronizing AlarmsPrerequisites

The communication between the NetNumen U31 server and the Network Elements (NEs)whose alarms you want to synchronize is normal.

Context

In actual network environment, the alarms of an NE displayed on the EMS client maybe different from the alarms actually raised in the NE when a transmission failure occursbetween the NE and the EMS or the NE does not report the latest alarms in time. By

5-21



synchronizing alarms, you can keep the consistency of alarm information between themanaged NEs and the EMS for timely analysis and handling of faults based on correctinformation.

The following are two alarm synchronization cases.

l Case 1: synchronizing alarms from a specific NE.l Case 2: synchronizing alarms from one or more specified NEs.

Steps

l Method 1:

a. On the NE Tree tab in the navigation pane of the fault management view, expandthe NE tree and find the NE whose alarms you want to synchronize.

b. Right-click the NE, and then click Synchronize Active Alarms.

c. In the pop-up Confirm box, which prompts the successful sending ofsynchronization command, click OK.

l Method 2:

a. On the menu bar of the client window, select Fault > Synchronize Active Alarmsor Fault > Synchronize History Alarms as needed.

b. In the pop-up dialog box, select the NE(s) whose alarms you want to synchronize,and click OK.

If you want to synchronize history alarms, set the period during which the historyalarms were raised in addition to selecting NEs.

c. In the pop-up Confirm box, which prompts the successful sending ofsynchronization command, click OK.


Result

After the system completes the synchronization, a message prompting successfulsynchronization appears on the status bar of the client window.

5-22


Chapter 6Alarm Rule ManagementTable of ContentsExplanation of Alarm Rules ........................................................................................6-1Introduction to Alarm Rule Management.....................................................................6-6Creating an Alarm Rule ..............................................................................................6-7

6.1 Explanation of Alarm RulesIn the NetNumen U31 system, you can define different alarm rules for managing alarms ornotifications reported by managed Network Elements (NEs), for example, acknowledging,clearing, filtering, or merging specific alarms when these alarmsmeet the preset conditionsin a rule.

Alarm Rule TypesNetNumen U31 supports the creation and management of various alarm rules. Thefollowing gives the definitions of some common alarm rules.

Note:

The available alarm rules vary with the product types and actual version of NetNumen U31you are using.

l Alarm Acknowledging Rule

An Alarm Acknowledging Rule specifies the conditions for the automaticacknowledgement of alarms. According to the Alarm Acknowledging Rule, thesystem will automatically acknowledge the alarms that meet the specified conditionsonce they are received or cleared.

l Alarm Clearing Rule

An Alarm Clearing Rule specifies the conditions for the automatic clearance of alarms.According to the Alarm Clearing Rule, the system will automatically clear the alarmsthat meet the specified conditions upon receiving them.

l Alarm Filtering Rule

An Alarm Filtering Rule specifies the conditions for the automatic filtering of alarms.According to the Alarm Filtering Rule, the system will automatically filter the alarmsthat meet the specified conditions.

6-1



Two filtering modes are optional for an Alarm Filtering Rule: “Display” and “Save”.When “Display” is selected, the filtered alarms are not displayed on the client GraphicUser Interface (GUI). When “Save” is selected, the filtered alarms are not displayedon the client GUI or stored in the database.

l Alarm Delaying Rule

An Alarm Delaying Rule specifies the conditions for delaying the processing oftransient alarms. According to the Alarm Delaying Rule, the system will directly storethe received alarm meeting the specified conditions as a history alarm when thisalarm is cleared during the preset delay time.

When a network being debugged or an unstable network is managed by theNetNumen U31 system, lots of alarms are reported to the system but they are clearedlater in a short time. Generally, such transient alarms are not caused by seriousfailures. However, a large amount of transient alarms displayed in the real-timemonitoring window may bury serious alarms that require immediate handling. In thiscase, an Alarm Delaying Rule can be used to limit the report of transient alarms.Only the alarms persisting for a period longer than the preset delay time are reportedto the system and displayed on the client GUI.

l Alarm Merging Rule

An alarm merging rule specifies the conditions for merging multiple alarms causedby the same failure. According to the alarm merging rule, the system will merge thealarms meeting the specified conditions, and only display the first received alarm onthe client GUI, which represents the other merged alarms caused by the same failure.

l Alarm Persisting Rule

An Alarm Persisting Rule specifies the conditions for processing some persistingactive or unacknowledged alarms. According to the Alarm Persisting Rule, the systemwill upgrade the alarm severity or raise a new alarm for an active or unacknowledgedalarm meeting the specified conditions when its persisting time exceeds the presetlimit.

l Alarm Counting Rule

An Alarm Counting Rule specifies the conditions for processing some alarms thatfrequently occur. According to the Alarm Counting Rule, the system will raise a newalarm for the alarm meeting the specified conditions when the frequency of this alarmduring a period exceeds the preset threshold.

l Alarm Forwarding Rule

An alarm forwarding rule specifies the conditions for the automatic forwarding ofalarms. According to the alarm forwarding rule, the system will automatically forwardthe alarms meeting the conditions to the specified personnel via E-mail or shortmessage when these alarms are received or have not been cleared during a specificperiod.

l Alarm Masking Rule

6-2


Chapter 6 Alarm Rule Management

An Alarm Masking Rule specifies the masking conditions for preventing the report ofsome alarms. The system issues the Alarm Masking Rule to the corresponding NEagents, who will not report the alarms meeting the specified conditions to the systemafter receiving this rule.

Note:

The Alarm Masking Rule is different from the Alarm Filtering Rule in “Save” modealthough the intuitive result of these two rules is that the alarms meeting the specifiedconditions are not displayed on the client GUI or stored in the database of theNetNumen U31 system.

à The Alarm Masking Rule is issued to the related NE agent or the related NEmanaged by an NE agent. For the successful issue of the Alarm Masking Rule,the NE agent must be started, and the link between the NetNumen U31 serverand the NE agent must be normal. The NE agent discards the specified alarmsaccording to the rule. Therefore, the discarded alarms does not occupy anynetwork bandwidth between the NE agent and the NetNumen U31 server.

à The Alarm Filtering Rule in “Save” mode is not issued to the related NE agent.The NetNumen U31 server discards the specified alarms upon receiving them.Although the discarded alarms are not displayed on the client GUI, they consumesome network bandwidth when being transferred from the NE agent to theNetNumen U31 server.

l Alarm Restraining Rule

An Alarm Restraining Rule specifies the conditions for restraining the display of somealarms. An alarm may correlate with another alarm. For example, the occurrence ofalarm B results in the occurrence of alarm A. In this case, you can create an AlarmRestraining Rule to restrain the display of alarm A, that is, only alarm B is displayedon the client GUI. The alarm restraining another alarm is called root alarm; while thealarm restrained by another alarm is called consequential alarm.

The following two kinds of Alarm Restraining Rules can be created depending on thecorrelation of alarms.

à AlarmRestraining Rule by NE: This rule can be specified for the restraint of alarmsbetween different NEs.

à Alarm Restraining Rule by NE Type: This rule can be specified for the restraintof alarms between correlated NEs of the same type, or alarms in differentcomponents (such as racks, and boards) in the same NE.

6-3



Note:

In an Alarm Restraining Rule, only one root alarm can be specified; while multipleconsequential alarms can be specified. That is, the occurrence of a root alarmrestrains the display of multiple consequential alarms.

l Alarm Triggering Script Rule

An Alarm Triggering Script Rule specifies the conditions for triggering a presetMan-Machine Language (MML) script that specifies the actions that should beperformed when the condition is met. According to the Alarm Triggering Script Rule,the system will run the preset MML script when the specified conditions are met. Thetriggering conditions may be:

à The persisting time of a specific alarm exceeds the preset threshold.

à The persisting time of multiple specified alarms exceeds the preset threshold.

l Notification Filtering Rule

A Notification Filtering Rule specifies the conditions for the automatic filtering ofnotifications. According to the Notification Filtering Rule, the system will automaticallydiscard the notifications that meet the specified conditions, which will not be displayedon the client GUI or stored in the database.

Attributes of Alarm RulesEach kind of alarm rule has three attributes, which determines its valid range, storage inthe database, and transfer via northbound interface.

l Valid Range

The valid range of an alarm rule is determined by two dimensions: effective scope(global or user) and effective period (forward or backward).

à Global Validity: An alarm rule with global validity is valid on all alarms andnotifications that meets the specified conditions, regardless of the maker of thisrule. All alarms displayed by the system have been processed according to thisrule.

à User Validity: An alarm rule with user validity is only valid for the maker of thisrule. For example, a user specifies an Alarm Filtering Rule. Then the system onlyfilters received alarms according to this rule for this user and displays requiredalarms on the client of this user. Other users are not affected by the rule.

à Backward Validity: An alarm rule with backward validity is valid for all alarms,including the alarms reported before the creation of this rule and those reportedafter the creation.

à Forward Validity: An alarm rule with forward validity is only valid for alarmsreported after the creation of this rule.

6-4



l Storage in Database

This attribute specifies whether the system stores the alarms meeting the conditionsof the rule into the database.

l Transfer via Northbound Interface

This attribute specifies whether the system transfers the alarmsmeeting the conditionsof the rule to an upper-lever Network Management System (NMS) via northboundinterface.

Table 6-1 lists the attributes of the previously-described alarm rules.

Table 6-1 Attributes of Alarm Rules

Alarm Rule Valid Range Storage inDatabase

Transfer viaNorthboundInterface

Alarm Acknowledg-

ing Rule

l Global validity

l Forward validity

Yes Yes

Alarm Clearing Rule l Global validity

l Forward validity

Yes Yes

Display l Global validity or user validity

l Backward validity

Yes YesAlarm

Filtering

Rule Save l Global validity or user validity

l Forward validity

No No

Alarm Delaying Rule l Global validity

l Forward validity

Yes Yes

Alarm Merging Rule l Global validity

l Forward validity

Yes Yes

Alarm Persisting

Rule

l Global validity

l Forward validity

Yes Yes

Alarm Counting Rule l Global validity

l Forward validity

Yes Yes

Alarm Forwarding

Rule

l Global validity

l Forward validity

Yes Yes

Alarm Masking Rule l Global validity

l Forward validity

No No

Alarm Restraining

Rule

l Global validity

l Forward validity

Yes Yes

Alarm Triggering

Script Rule

l Global validity

l Forward validity

Yes Yes

Notification Filtering

Rule

l Global validity

l Forward validity

No No

6-5



6.2 Introduction to Alarm Rule ManagementBefore any alarm rule management operation, you need to open the Rule Setting tab (asshown in Figure 6-1) in the client window by one of the following ways:

l On the menu bar, select Fault > Setting > Rule Setting.l On the Management tab in the navigation pane, double-click the Rule Setting node.

Figure 6-1 Rule Setting Tab

The NetNumen U31 system supports the following operations for managing different typesof alarm rules. You can use appropriate toolbar buttons or shortcut menus to do theseactions, as described in Table 6-2.

Table 6-2 Alarm Rule Management Operations

Operation Toolbar Button Shortcut Menu Description

Create an alarm rule - Create an alarm rule of a certain type.

Modify an alarm rule Modify Modify the settings of an existing

alarm rule.

Enable an alarm rule Enable Enable an alarm rule to make this rule

effective

Disable an alarm rule Disable Disable an alarm rule.

Delete an alarm rule Delete Delete an unnecessary alarm rule.

Refresh alarm rules - Refresh the information of all alarm

rules by synchronizing the latest

alarm rule information from the

NetNumen U31 server.

View related rules - Relative rule View the other rules related to an

alarm rule.

6-6



For the alarm rule creating and modifying operations, the NetNumen U31 system willrecord the information of the user who performs the operations and the operation time.This record can be queried subsequently for tracing the relevant operations.

6.3 Creating an Alarm RuleContext

The procedures for creating different types of alarm rules are similar except the setting ofsome special parameters. The following only gives a general procedure of how to createan alarm rule. For the detailed instructions for how to set special parameters for a specificrule, see the later section corresponding to the type of the alarm rule you want to create.

Steps

1. In the client window, perform one of the following operations to open the Rule Settingtab.l On the menu bar, select Fault > Setting > Rule Setting.l On the Management tab in the navigation pane, double-click the Rule Setting

node.

The Rule Setting tab appears, as shown in Figure 6-2.

Figure 6-2 The Rule Setting Tab

2. On the toolbar of the Rule Setting tab, click .

The New dialog box appears, as shown in Figure 6-3.

6-7



Figure 6-3 Selecting an Alarm Rule Type

3. In the New dialog box, select an alarm rule type, and then click OK.

Depending on the selected alarm rule type, the corresponding dialog box opens.

Note:

For the description about special parameters for a specific rule, refer to the latersections corresponding to each rule type.

4. After setting the conditions for the new rule, click OK.


ResultThe created alarm rule appears in the rule list on the Rule Setting tab.

6.3.1 Alarm Acknowledging RuleIn the Alarm Acknowledging Rule dialog box, set the parameters for the rule as follows:

1. On the Basic tab as shown in Figure 6-4, set the basic parameters for the rule.

6-8



a. Type a name and additional information in the Name box and the Description boxfor the rule to be created.

b. Select an initial status for the new rule: Activate or Suspend.

c. Select when the system shall take the acknowledgement action: While Reporting(when alarms are reported) orWhile Restoring (when alarms are cleared).

Figure 6-4 Alarm Acknowledging Rule Dialog Box (Basic Tab)

2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that need to be acknowledged by the system.

Note:l If you select All NEs and All Codes on the Location tab and Alarm Code tab

respectively, a Confirm dialog box appears after you click OK, asking you toconfirm the selection.

l If you do not set special conditions on the Others tab, the system considers allthe options are selected by default.

a. On the Location sub-tab as shown in Figure 6-5, select the NEs whose alarmsneed automatic acknowledgement.

6-9



Figure 6-5 Alarm Acknowledging Rule Dialog Box (Condition Tab-Location)

b. On the Alarm Code sub-tab as shown in Figure 6-6, select the alarm codes foracknowledging the corresponding alarms.

Figure 6-6 Alarm Acknowledging Rule Dialog Box (Condition Tab-Alarm Code)

6-10



c. On the Others sub-tab as shown in Figure 6-7, set a period for acknowledgingalarms raised during this period, select alarm type(s) for acknowledging alarms ofcertain types, select severity level(s) for acknowledging alarms at certain severitylevels, set an IP address for acknowledging alarms of a specific NE, and/or typea keyword for acknowledging alarms by the content of alarm remark.

Figure 6-7 Alarm Acknowledging Rule Dialog Box (Condition Tab-Others)

After the alarm acknowledging rule is successfully created and activated, the system willautomatically acknowledge the alarms that meet the specified conditions when they arereceived or cleared.

6.3.2 Alarm Clearing RuleIn the Alarm Clearing Rule dialog box, set the parameters for the rule as follows:

1. On the Basic tab, set the basic parameters for the rule.



2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that need to be cleared by the system.

6-11



Note:

The instructions on setting the parameters on the Condition tab for the alarmclearance rule are similar to those for an alarm acknowledging rule. Refer to theprevious section “Alarm Acknowledging Rule” for the detailed instructions.

After the alarm clearing rule is successfully created and enabled, the system will forciblyclear the alarms that meet the specified conditions upon receiving them and store thesealarms as historical alarms.

6.3.3 Alarm Filtering RuleIn the Alarm Filtering Rule dialog box, set the parameters for the Alarm Filtering Rule asfollows:




c. Select a filter type: Display, or Save.

If Display is selected, you can set the validity range of the new rule:l Valid for all usersl Valid only for current user’s departmentl Valid only for admin

6-12



Figure 6-8 Alarm Filtering Rule Dialog Box (Basic Tab)

2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that need to be filtered by the system.

Note:

The instructions for setting the parameters on the Condition tab for the Alarm FilteringRule are similar to those for an alarm acknowledging rule. See the previous section“Alarm Acknowledging Rule” for the detailed instructions.

After the Alarm Filtering Rule is successfully created and enabled, the system will filter thealarms that meet the specified conditions, which will not be displayed on the client GUI.

6.3.4 Alarm Delaying RuleIn the Alarm Delaying Rule dialog box, set the parameters for the Alarm Delaying Ruleas follows:




6-13



c. Type a number or click the upper arrow of the Delay time spin box to set the delaytime.

Note:

The default delay time is 10 seconds. That means only the alarms that have notbeen cleared in 10 seconds will be reported and displayed on the client GUI. Therange of delay time is from 10 to 1800 seconds.

Figure 6-9 Alarm Delaying Rule Dialog Box (Basic Tab)

2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that shall be processed after the delay time.

Note:

The instructions for setting the parameters on theCondition tab for the AlarmDelayingRule are similar to those for an alarm acknowledging rule. See the previous section“Alarm Acknowledging Rule” for the detailed instructions.

6-14



6.3.5 Alarm Merging RuleIn the Alarm Merging Rule dialog box, set the parameters for the alarm merging rule asfollows:




2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that need to be merged by the system.

Note:

The instructions for setting the parameters on the Condition tab for the alarm mergingrule are similar to those for an alarm acknowledging rule. See the previous section“Alarm Acknowledging Rule” for the detailed instructions.

You must specify the NEs and alarm codes on the Location tab and Alarm Code tabrespectively.

3. On the Action tab as shown in Figure 6-10, specify the alarm that will be displayed onthe client GUI to represent the other merged alarms. The options are:l Display one of the merged alarmsl Raise a new alarm

Note:

The merging action cannot be modified later once the alarm merging rule issuccessfully created.

If you want the system to raise a new alarm to represent the merged alarms, set aseverity level for the new alarm, and type additional information of the new alarm inthe New Alarm Remark box.

6-15



Figure 6-10 Alarm Merging Rule Dialog Box (Action Tab)

After the alarm merging rule is successfully created and activated, the system will mergethe alarms that meet the specified conditions. Only one of the merged alarms or anewly-raised alarm is displayed on the client GUI, representing all the other mergedalarms. If one of the merged alarm is displayed on the client GUI but this alarm is cleared,the system will select and display another alarm to represent the other merged alarms.You can click the plus sign before the displayed alarm to view all the merged alarms.

The merged alarms not displayed on the client GUI are regarded as invisible alarms inthe system. When querying active alarms, you can select Invisible to show the mergedalarms in the query result. For detailed instructions, see the previous section “QueryingActive Alarms by Customized Conditions”.

6.3.6 Alarm Persisting RuleIn the Alarm Persisting Rule dialog box, set the parameters for the Alarm Persisting Ruleas follows:




2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that shall follow the rule.

6-16



Note:

The instructions for setting the parameters on the Condition tab for the AlarmPersisting Rule are similar to those for an alarm acknowledging rule. Refer to theprevious section “Alarm Acknowledging Rule” for the detailed instructions.


3. On the Action tab as shown in Figure 6-11, do the following:

a. Type a number in the Alarm Persisting Duration spin box, and select a unit fromthe drop-down box after it to set the duration threshold.

The following table provides the range of the persisting duration.

Duration Range Unit

[10, 86400] Second

[1, 1440] Minute

[1, 24] Hour

b. Select a persisting state: Unacknowledged State or Active state, for countingthe duration of persisting unacknowledged alarms or active alarms.

c. Select the action that the system shall do when the duration of the alarm meetingthe specified conditions exceeds the threshold: Severity level raise or Createnew alarm.

If Raise the Severity Level is selected, select the severity level(s) that the alarmsshall be upgraded to.

If Create a New Alarm is selected, select a severity level for the new alarm to beraised, and type the information for the new alarm.

6-17



Figure 6-11 Alarm Persisting Rule Dialog Box (Action Tab)

After the Alarm Persisting Rule is successfully created and activated, the system countsthe persisting time of the unacknowledged alarms or active alarms that meet the specifiedconditions. Once the persisting time exceeds the threshold, the system will upgrade theseverity level of such alarms or raise a new alarm to indicate that these alarms persistedin the unacknowledged or active state for a long time.

The system will clear the newly-raised alarm upon the state change of the persisting alarm,for example, the active alarm becomes a history alarm, or the unacknowledged alarm isacknowledged.

6.3.7 Alarm Counting RuleIn the Alarm Counting Rule dialog box, set the parameters for the Alarm Counting Ruleas follows:




2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that need to be counted by the system.

6-18



Note:

The instructions for setting the parameters on theCondition tab for the AlarmCountingRule are similar to those for an alarm acknowledging rule. See the previous section“Alarm Acknowledging Rule” for the detailed instructions.


3. On the Action tab, set the counting period, frequency threshold, and the severity levelof the new alarm to be raised, and type a remark for the new alarm as needed, asshown in Figure 6-12.

For example, use the default settings: the counting period is 20 seconds, the frequencythreshold is 10, and the severity level of the alarm to be raised is critical.

Figure 6-12 Alarm Counting Rule dialog box (Action Tab)

After the Alarm Counting Rule is successfully created and activated, the system startscounting the times of occurrence upon receiving the first alarm that meets the specifiedconditions. Once the frequency of this alarm during a counting period is found thresholdcrossing, the system raises a new alarm, which indicates the detailed alarm information,such as the severity level, the original alarm and the current frequency.

If the alarm is reported again before the counting period ends, the system updates thefrequency information of the newly-raised alarm instead of raising another new alarm.

6-19



Upon the ending of the counting period, the system clears the raised alarm and startsthe counting of alarms in the new period.

6.3.8 Alarm Forwarding RuleIn the Alarm Forwarding Rule dialog box, set the parameters for the alarm forwardingrule as follows:




c. If you want to forward specific alarms when they are cleared, select SupportForwarding Alarm on Clearing.

d. If you want to forward the statistical information of specific alarms, select SupportForwarding Alarm Statistics.

Figure 6-13 Alarm Forwarding Rule Dialog Box (Basic Tab)

2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms you want to forward.

6-20



Note:

The instructions for setting the parameters on the Condition tab for the alarmforwarding rule are similar to those for an alarm acknowledging rule. See the previoussection “Alarm Acknowledging Rule” for the detailed instructions.

3. On the Action tab as shown in Figure 6-14, do the following:

a. Under User Information, type E-mail address(es) in the Email box, and phonenumber(s) in the Phone box.

If the E-mail and phone number information of the person have been set in thesystem, you can click the Address button to select the E-mail address and phonenumber in the pop-up dialog box. For the detailed instructions of selecting E-mailaddresses, see the previous section “Forwarding an Active Alarm via E-mail andShort Message”.

b. Under Forward Type, select a forward type: Immediately forward or Forwardwhen time is over.

For example, if you want to forward the alarms meeting the forwarding conditionsafter 30 minutes every hour, select Forward when time is over, type 20 in thespin box after the option button, and select Every.

c. If you want to forward the alarms on special day(s), select Forward on specialday, select By week or By month, and then select the day(s) under Day setting.

d. If you want to forward the alarms on special hour(s) in a day, select Forward atspecial hour(s), and then select the day(s) under Time setting.

6-21



Figure 6-14 Alarm Forwarding Rule Dialog Box (Action Tab)

After the alarm forwarding rule is successfully created and activated, the system willsuccessfully forward the information of the alarms meeting the forwarding conditions to thespecified person via E-mail and/or short message on the condition that you have properlyconfigured the mail server and/or SMS module as specified in the previous section “AlarmMonitoring via Short Message and E-mail” in Chapter 2 Alarm and Notification Monitoring.

6.3.9 Alarm Masking RuleIn the Alarm Masking Rule dialog box, set the parameters for the Alarm Masking Rule asfollows:




2. On the Condition tab, set the parameters on three sub-tabs (Location, Alarm Code,and Others) to specify the alarms that you want to mask.

6-22



Note:l The instructions for setting the parameters on the Condition tab for the Alarm

Masking Rule are similar to those for an alarm acknowledging rule. See theprevious section “Alarm Acknowledging Rule” for detailed instructions.

l On the Location sub-tab, only started NE agents and NEs managed by them areoptional.

l You must specify NEs on the Location tab.

After the Alarm Masking Rule is successfully created and activated, the corresponding NEagent or NE will discard the alarms meeting the specified conditions. As a result, thesealarms will not be reported to the NetNumen U31 system.

6.3.10 Alarm Triggering Script RuleIn the Alarm Triggering Script Rule dialog box, set the parameters for the alarm triggerscript rule as follows:

1. On the Basic tab as shown in Figure 6-15, do the following:



c. AfterDuration, type a number in the spin box and select a unit from the drop-downbox to set a duration threshold.

The range of the duration threshold is from 10 seconds to 3650 days.

d. Click the Choose button. In the pop-up Open dialog box, find and select the MMLscript, and then click OK.

e. Select a rule type to determine when the MML script shall be run.

If Single alarm exists in duration time is selected, proceed to Step 2.

If Multiple alarms exist at the same time is selected, proceed to Step 3.

6-23



Figure 6-15 Alarm Trigger Script Rule Dialog Box (Basic Tab)

2. For the rule type Single alarm exists in duration time, set the parameters on twosub-tabs (Location and Alarm Code) of the Condition tab (as shown in Figure 6-16)to specify the alarm(s) that can trigger the running of the MML script. And the settingof the alarm trigger script rule is completed.

Figure 6-16 Alarm Trigger Script Rule Dialog Box (Condition Tab-Single Alarm Type)

6-24



Note:

The instructions for setting the parameters on the Location and Alarm Code sub-tabfor the alarm trigger script rule are similar to those for an alarm acknowledging rule.See the previous section “Alarm Acknowledging Rule” for the detailed instructions.


3. For the rule type Multiple alarms exist at the same time, repeat the following stepsto add the alarms that you want to use for triggering the MML script on the Conditiontab as shown in Figure 6-17.

a. Click the Add button.

b. In the pop-up Alarm Trigger Script Rule Condition dialog box, select the NEsand alarm codes on the Location and Alarm Code tabs to specify the alarm.

c. Click OK.

Figure 6-17 Alarm Trigger Script Rule Dialog Box (Condition Tab-Multiple AlarmsType)

After the alarm trigger script rule is successfully created and enabled, the system will runthe specified script file when the persisting time of a specified alarm or multiple alarmsexceeds the duration threshold.

6-25



Note:

If the selected MML script is modified after the creation of the alarm trigger script rule, youneed to modify this rule by re-selecting this MML script to make the script modificationeffective.

6.3.11 Alarm Restraining Rule by Network ElementIn the Alarm Restraining Rule by NE dialog box, set the parameters for the alarm restrainrule as follows:




2. On the Root Alarm tab as shown in Figure 6-18, select an NE and an alarm code ontwo sub-tabs (Location and Alarm Code) to specify the root alarm.

Figure 6-18 Alarm Restraining Rule by NE Dialog Box (Root Alarm Tab)

6-26



Note:

Only one NE and one alarm code can be selected for specifying the root alarm; whilemultiple NEs and alarm codes can be selected for specifying consequential alarms.

3. On theConsequential Alarm tab, select the NE(s) and alarm code(s) on two sub-tabs(Location and Alarm Code) to specify the consequential alarm(s).

Note:

An alarm cannot be defined as a root alarm or a consequential alarm at the same time.If an alarm is selected as a root alarm in an alarm restrain rule, it cannot be selectedas a consequential alarm in another alarm restrain rule.

After the Alarm Restraining Rule by NE is successfully created and activated, the specifiedconsequential alarms will not be displayed when the specified root alarm is raised oralready exists in the system.

6.3.12 Alarm Restraining Rule by Network Element TypeIn the Alarm Restraining Rule by NE Type dialog box, set the parameters for the alarmrestrain rule as follows:




2. On the Condition tab, do the following:

a. On the NE Type sub-tab, select an NE type, as shown in Figure 6-19.

6-27



Figure 6-19 Alarm Restraining Rule by NE Type Dialog Box (Condition Tab-NEType)

You can only select one NE type on the NE Type tab.

b. On the Root Alarm Code sub-tab, select a root alarm code, as shown in Figure6-20.

6-28



Figure 6-20 Alarm Restraining Rule by NE Type Dialog Box (Condition Tab-RootAlarm Code)

You can only select one root alarm code on the Root Alarm Code tab.

c. On the Consequential Alarm Code sub-tab, select one or multiple consequentialalarm code(s), as shown in Figure 6-21.

6-29



Figure 6-21 Alarm Restraining Rule by NE Type Dialog Box (ConditionTab-Consequential Alarm Code)

After the Alarm Restraining Rule by NE Type is successfully created and activated, thespecified consequential alarm(s) will not be displayed when the specified root alarm israised or already exists in the system.

6.3.13 Notification Filtering RuleIn the Notification Filtering Rule dialog box, set the parameters for the NotificationFiltering Rule as follows:




2. On the Condition tab, set the parameters on three sub-tabs (Location, NotificationCode, and Others) to specify the notifications to be filtered by the system.

Note:

The instructions for setting the parameters on the Condition tab for the NotificationFiltering Rule are similar to those for an alarm acknowledging rule. See the previoussection “Alarm Acknowledging Rule” for the detailed instructions.

6-30



After the Notification Filtering Rule is successfully created and enabled, the systemautomatically filters the notifications meeting the specified conditions upon receiving them.The filtered notifications are not displayed on the client GUI or stored in the database ofthe system.

6-31




6-32


Chapter 7Handling SuggestionManagementTable of Contents

Introduction to Handling Suggestion Management......................................................7-1Exporting Handling Suggestions to a File ...................................................................7-2Importing Handling Suggestions From a File ..............................................................7-3Searching for Handing Suggestions ...........................................................................7-3Supplementing Handling Suggestions for an Alarm ....................................................7-4

7.1 Introduction to Handling Suggestion ManagementNetNumen U31 provides handling suggestions for each alarm and notification forreference. After maintaining the network and the network element management systemfor a long time, maintenance personnel can summarize alarm processing experiencesand supplement the contents of handling suggestions in the system.

Before managing existing handling suggestions in the NetNumen U31 system, you needto open the Handling Measure Setting tab in the client window by one of the followingways:

l On the menu bar, select Fault > Setting > Handling Suggestion Setting.l On the Management tab in the navigation pane, double-click the Handling

Suggestion Setting node.

Select an alarm code on the Resource Type tree. You can view the reason code, reasondescription, default handling suggestions, and user-defined handling suggestions of thisalarm on the Handling Suggestion Setting tab, as shown in Figure 7-1.

7-1



Figure 7-1 Handling Suggestion Setting Tab

On the Handling Suggestion Setting tab, you can:

l Export existing handling suggestions to an XML, TXT, HTM, PDF, XLS, or CSV filel Import user-defined handling suggestions from an XLS or CSV filel Search for the handling suggestions of an alarm or notificationl Supplement handling suggestions of an alarm or notification.

7.2 Exporting Handling Suggestions to a FileContext

The existing handling suggestions in the NetNumen U31 system can be exported andsaved as an XML, TXT, HTM, PDF, XLS, or CSV file on your local client.

The following procedure describes how to export all handling suggestions to a file.

Steps

1. On the Handling Suggestion Setting tab, click the Export button.

2. In the pop-up Save dialog box, type or select a directory where you want to save thefile from the Save in drop-down box, select a file type from the Files of type drop-downbox, type a name for the file in the File name box, and then click Save.


7-2


Chapter 7 Handling Suggestion Management

ResultThe file containing the handling suggestions of all alarms appears under the specifieddirectory.

7.3 Importing Handling Suggestions From a FilePrerequisitesThe XLS or CSV file containing the user-defined handling suggestions is available on yourclient.

ContextYou can modify existing user-defined handling suggestions in the system by importing anXLS or CSV file.

Steps1. On the Handling Suggestion Setting tab, click the Import button.

A Confirm dialog box opens, prompting you that only user-defined handlingsuggestions can be changed according to the contents in the file to be imported.

2. Click OK in the Confirm dialog box.

3. In the pop-up Open dialog box, select the directory where you save the file to beimported from the Look in drop-down box, select the file, and then click the Openbutton.


ResultThe user-defined handling suggestions in the system change according to the importedinformation.

7.4 Searching for Handing SuggestionsContextIf you know some information of the alarm whose handling suggestions you want to view,you can use a keyword for quickly finding this alarm and its handling suggestions.

The following gives an example for how to search for the handling suggestions of an alarmrelated to E1/T1 link.

Steps1. On the Handling Suggestion Setting tab, type a keyword (E1/T1) in the Enter filter

text box, and then click .

7-3



The Resource Type tree is expanded, listing all alarm codes containing the keyword“E1/T1”, as shown in Figure 7-2.

Figure 7-2 Resource Type Tree

2. After finding the alarm you want, click it on theResource Type tree to view its handlingsuggestions.


7.5 Supplementing Handling Suggestions for an AlarmContext

You can add more handling suggestions according to your experience in alarm handling.The supplemented handling suggestions are saved as user-defined handling suggestionsfor reference.

The following procedure describes how to add user-defined handling suggestions for analarm.

Steps

1. On the Handling Suggestion Setting tab, click the alarm that you want to addhandling suggestions to on the Resource Type tree.

2. Under User-defined Suggestions, type your handling suggestions, and then click theSave button.


7-4


Chapter 8Alarm Severity ManagementTable of Contents

Introduction to Alarm Severity Management ...............................................................8-1Resetting the Severity Level of an Alarm ....................................................................8-3Creating a Severity Regrading Rule for Specific Managed Elements ..........................8-4

8.1 Introduction to Alarm Severity ManagementAlarms can be classified into the following four types according to the severity of the failurescausing them.

l Critical alarml Major alarml Minor alarml Warning

NetNumen U31 assigns a default severity level to each alarm, which can be modified asneeded. The modification impacts all alarms corresponding to the alarm code reported byall NEs. You can also create a severity regrading rule to specify the severity of the alarmsreported by specific NEs.

Before any operation on alarm severity, do one of the following to open the SeverityRegrading Setting tab in the client window:

l On the menu bar, select Fault > Setting > Severity Regrading Setting.l On theManagement tab in the navigation pane, double-click the Severity Regrading

Setting node.

Figure 8-1 shows an example of the Severity Regrading Setting tab, on which OMCAlarm is selected from the Code Group drop-down box on the toolbar.

8-1



Figure 8-1 Severity Regrading Setting Tab

The toolbar on the upper part of the Severity Regrading Setting tab offers some shortcutbuttons for managing alarm severity, as described in Table 8-1.

Table 8-1 Description of Toolbar Buttons on the Severity Regrading Setting Tab

Button Function

Export all the alarm severity settings to an XML, TXT, HTM, PDF, XLS,

or CSV file.

Import customized severity settings from an XLS or CSV file.

Create a severity regrading rule to specify the severity level of alarms

reported by specific NEs based on an alarm code.

Modify an existing severity regrading rule.

Delete an existing severity regrading rule.

Save the modification of alarm severity.

Restore the default severity settings.

Refresh the alarm severity list.

Search for a specific severity regrading rule.

8-2


Chapter 8 Alarm Severity Management

8.2 Resetting the Severity Level of an AlarmContext

Caution!

Although NetNumen U31 supports the modification of alarm severity level, be cautiouswhen you attempt to modify the severity level of an alarm because the default severitylevel is generally an appropriate one.

The following procedure describes an example of how to reset the severity level of analarm.

Steps

1. On the Severity Regrading Setting tab, select the group of the alarm you want toregrade from the Code Group drop-down box on the toolbar to show all alarms of theselected group.

2. On the row of the alarm to be regraded, click the drop-down box in the CustomSeverity column, and then select a new severity level you want. A sign appears inthe corresponding cell on the Modify Flag column.

3. Click on the toolbar to save the modification of the alarm severity level.

After the successful saving, the sign in the corresponding cell on the Modify Flagcolumn disappears.


Result

The severity level of the alarm changes correspondingly.

Note:

The severity level of the alarms received by the system before the regrading keepsunchanged, that is, the severity level before regrading. The new severity level only takeseffect on the alarms received by the system after the resetting.

In addition, the severity regrading is only valid in the NetNumen U31 system, which doesnot impact the alarms in NEs and their Operation & Maintenance Modules (OMMs).

8-3



8.3 Creating a Severity Regrading Rule for SpecificManaged Elements

Context

If you only want the customized severity level to be effective on the alarms reported byspecific NEs, you can create a severity regrading rule on the basis of the correspondingalarm code.

The following example describes how to create a severity regrading rule.

Steps

1. On the Severity Regrading Setting tab, select the group of the alarm you want fromthe Code Group drop-down box on the toolbar to show all alarms of the selectedgroup.

2. Click the row of the alarm code that you want to base for creating a severity regradingrule, and then click on the toolbar.

3. In the pop-upRegrade Severity dialog box, select the network elements and clickOK.

A plus sign appears before the selected alarm code. Click the plus sign to show thecreated severity regrading rule, as shown in Figure 8-2.

Figure 8-2 Created Severity Regrading Rule

4. On the row of the severity regrading rule, click the drop-down box in the CustomSeverity column, and then select a new severity level you want.

5. Click on the toolbar to save the modification of the alarm severity level.


8-4


Chapter 8 Alarm Severity Management

Result

The severity level of the alarms (corresponding to the selected alarm code) reported bythe specified NEs follows the created severity regrading rule; while the severity level of thealarms reported by the other NEs is the default level defined by the system.

8-5




8-6


Chapter 9Alarm Box ManagementTable of Contents

Alarm Box Introduction ...............................................................................................9-1Adding an Alarm Box..................................................................................................9-1Modifying the Settings of an Alarm Box ......................................................................9-4Enabling an Alarm Box...............................................................................................9-5Disabling an Alarm Box ..............................................................................................9-5Deleting an Alarm Box................................................................................................9-6Refreshing the Settings of Alarm Boxes .....................................................................9-6

9.1 Alarm Box IntroductionAn alarm box can be used to collect alarm information and alarm clearing notifications froma network Element Management System (EMS), displays the received alarms on an LCDscreen, illuminates its alarm indicator lights, and produces alarm sounds. In addition, thealarm box can forward the collected alarm notifications and alarm clearing notifications torelated personnel via short message by its built-in SMS module.

Before using an alarm box, you are required to set the alarm box in the NetNumen U31system. According to the settings, NetNumen U31 establishes a connection to the alarmbox, over which alarm information is transferred to the alarm box. When setting the alarmbox, you can set conditions for forwarding specific alarms to the alarm box.

NetNumen U31 supports the following operations related to alarm box:

l Add an alarm boxl Modify the settings of an alarm boxl Enable an alarm boxl Disable an alarm boxl Refresh the settings of alarm boxes

9.2 Adding an Alarm BoxPrerequisites

The physical link between the NetNumen U31 system and the alarm box to be added isnormal.

9-1



ContextYou can add the information of an alarm box and configure the alarm box in the NetNumenU31 system. When the network connection between the NetNumen U31 system and thealarm box is normal, the system will transfer the information of required alarms to the alarmbox.

The following procedure describes how to add the information of an alarm box in theNetNumen U31 system.

Steps1. In the client window, do one of the following to open the Alarm Box Setting tab.

l On the menu bar, select Fault > Setting > Alarm Box Setting.l On the Management tab in the navigation pane, double-click the Alarm Box

Setting node.

2. On the toolbar of the Alarm Box Setting tab, click .

The Alarm Box dialog box opens, as shown in Figure 9-1

9-2


Chapter 9 Alarm Box Management

Figure 9-1 Alarm Box Dialog Box

Table 9-1 describes the related parameters.

Table 9-1 Alarm Box Parameters


Name Alarm box name.

Description Description of the alarm box.

9-3




Initial State Initial state of the alarm box.

l Activate: When rule-meeting alarms are raised, the system will

send the alarms to the alarm box.

l Suspend: When rule-meeting alarms are raised, the system will

not send the alarms to the alarm box.

IP IP address of the alarm box.

Server Port The port number of the NetNumen U31 server used to connect to the

alarm box. The value cannot be modified.

Detect button Click the button to detect whether the alarm box can be connected.

Display Alarm Severity Specify the severities of alarms to be displayed on the LCD screen of

the alarm box.

Alarm Severity Specify the severities of alarms which will trigger the alarm sound.

Alarms send to alarm

box

Select the severities of alarms to be sent to the alarm box.

Advanced button The Advanced button is available after you set the alarms to be sent to

the alarm box.

3. To set advanced conditions that restrict the alarm sending, click the Advanced button.The Alarm Box Rule dialog box appears. Select the NEs, alarm codes, raised time,and/or alarm types on the Location, Alarm Code, and Others tabs to specify thealarms that you want to send to the alarm box. Click OK.

4. In the Alarm Box dialog box, click OK.


Result

The added alarm box appears on the Alarm Box Setting tab. The NetNumen U31 systemestablishes a connection to the added alarm box. The alarms meeting the conditions willbe sent by the NetNumen U31 system to the alarm box.

9.3 Modifying the Settings of an Alarm BoxContext

You can modify the settings of an existing alarm box (except the name of the alarm box)in the NetNumen U31 system as follows.

Steps

1. On the Alarm Box Setting tab, find the alarm box you want to modify, and then doone of the following to open the Alarm Box dialog box.

9-4



l Right-click the alarm box, and then click Modify.l Click the alarm box, and then click on the toolbar.

2. In the Alarm Box dialog box, modify the settings of the alarm box as needed.

3. Click OK to save the modification.


9.4 Enabling an Alarm BoxPrerequisitesThe status of the alarm box to be enabled is “Disable”.

ContextThe system only transfers the required alarms to an alarm box when this alarm box isenabled in the NetNumen U31 system. The following describes how to enable a disabledalarm box.

Steps1. On the Alarm Box Setting tab, find the alarm box you want to enable, and then do

one of the following:l Right-click the alarm box, and then click Enable.l Click the alarm box, and then click on the toolbar.



ResultThe status of the alarm box changes from Disable to Enable. The system will transferreceived alarms to the alarm box according to the settings.

9.5 Disabling an Alarm BoxPrerequisitesThe status of the alarm box you want to disable is “Enable”.

ContextIf you do not want to transfer required alarms to an alarm box, you can disable it as follows.

Steps1. On the Alarm Box Setting tab, find the alarm box you want to disable, and then do

one of the following:

9-5



l Right-click the alarm box, and then click Disable.l Click the alarm box, and then click on the toolbar.



Result

The status of the alarm box changes fromEnable toDisable. The system does not transferthe alarms meeting the specified conditions to the disabled alarm box.

9.6 Deleting an Alarm BoxContext

If an alarm box will not be used any longer, you can delete it from the NetNumen U31system as follows.

Steps

1. On the Alarm Box Setting tab, find the alarm box you want to delete, and then doone of the following:l Right-click the alarm box, and then click Delete.l Click the alarm box, and then click on the toolbar.



Result

The deleted alarm box disappears from the Alarm Box Setting tab.

9.7 Refreshing the Settings of Alarm BoxesContext

The NetNumen U31 server saves the modifications on alarm boxes done by different userslogging in to the system via different clients. You can refresh the alarm box list to get thelatest settings of all alarm boxes in the system.

Steps

l On the Alarm Box Setting tab, click on the toolbar.


9-6



Result

The system synchronizes the latest settings of all alarm boxes from the NetNumen U31server and refreshes the information of alarm boxes on the Alarm Box Setting tab.

9-7




9-8


Chapter 10Preference SettingsTable of Contents

Customizing an Alarm Code.....................................................................................10-1Modifying the Cause Description of an Alarm ...........................................................10-3Setting the Alarm Forward Template.........................................................................10-5Merging Intermittent Alarms......................................................................................10-6Setting an Alarm Prompting Rule..............................................................................10-7Customizing Alarm Sounds and Colors ..................................................................10-10Creating an Alarm-Suppressing Plan Task..............................................................10-12

10.1 Customizing an Alarm CodeContext

In addition to predefined alarm codes, the NetNumen U31 system also supports thecustomization of some alarm codes, such as performance threshold crossing alarms andproduct-specific public alarms. You can specify the name and severity level for suchalarms according to the actual situation of the managed network.

Note:

The available alarm codes that can be customized vary with the version of the NetNumenU31 system.

The following procedure describes an example of how to customize a performancethreshold crossing alarm.

Steps

1. In the client window, do one of the following to open the Alarm Code DescriptionSetting tab, as shown in Figure 10-1.l On the menu bar, select Fault > Setting > Alarm Code Description Setting.l On the Management tab in the navigation pane, double-click the Alarm Code

Description Setting node.

10-1



Figure 10-1 Alarm Code Description Setting Tab

2. Find the alarm code you want to customize, and then do one of the following:l Double-click the alarm code.l Click the alarm code, and then click on the toolbar of the tab.

The Alarm Code Description Setting dialog box opens, as shown in Figure 10-2.

Figure 10-2 Alarm Code Description Setting dialog box

3. Under Modified Name, type a new name for the alarm code.

10-2


Chapter 10 Preference Settings

Note:

You cannot set the severity of a performance threshold alarm in this dialog box becausethe actual severity of this alarm vary with the value of the corresponding performanceindex. For example, if the system detects that the value of the performance indexlocates in the threshold range for critical severity level, it will raise a threshold crossingalarm as a critical alarm.

For an alarm whose severity can be set, a Modified Severity drop-down box isavailable under Severity in the Alarm Code Description Setting dialog box.

4. Click OK.


Result

If an alarm of the customized alarm code occurs, it will be displayed on the client GUI withthe specified name and severity level.

Follow-Up Action

On the Alarm Code Description Setting tab, you can also do the following operations byclicking the corresponding buttons on the toolbar:

l Export the alarm codes that can be customized to an XML, TXT, HTM, PDF, XLS, orCSV file.

l Import the modification of customized alarm codes from an XLS or CSV file.l Refresh the alarm codes displayed in your client window to get the latest information

of these alarm codes from the server.

10.2 Modifying the Cause Description of an AlarmContext

The NetNumen U31 system provides probable causes for each alarm code for yourreference. You can modify the description of probable causes when necessary.

The following procedure describes an example of how to modify the description of probablecauses of an alarm.

Steps

1. In the client window, do one of the following to open theReason Setting tab, as shownin Figure 10-3.l On the menu bar, select Fault > Setting > Reason Setting.

10-3



l On theManagement tab in the navigation pane, double-click theReason Settingnode.

Figure 10-3 The Reason Setting Tab

2. Find the alarm code whose causes you want to modify, and then do one of thefollowing:l Double-click the alarm code.l Click the alarm code, and then click on the toolbar of the tab.

The Reason Setting dialog box opens, as shown in Figure 10-4.

10-4



Figure 10-4 Reason Setting dialog box

3. In the Modified Name area, type new probable causes for the alarm code.

4. Click OK.


10.3 Setting the Alarm Forward TemplateContext

When you use the alarm forwarding function, the system forwards the information ofrequired alarms via E-mail or short message based on the forward template. The systemprovides a default forward template that determines the content and format of alarminformation in an E-mail or short message. You can customize the forward templateaccording to the actual requirements.

Steps

1. On the menu bar of the client window, select Fault > Setting > Forward TemplateSetting to open the Forward Template Setting dialog box, as shown in Figure 10-5.

10-5



Figure 10-5 Forward Template Setting dialog box

2. Under SMS template, Mail subject, and Mail contents, edit the fields and formatsfor short message, E-mail subject, and E-mail content.

Note:

After modifying the fields in a box. you can click the corresponding Verify button tocheck the validity of the fields.

3. Click OK to save the modification.


10.4 Merging Intermittent AlarmsContext

When the managed network is instable, the system may receive multiple alarms of thesame alarm code from a network element in a short time. These alarms are regardedas intermittent alarms. You can set a rule for merging such alarms into one alarm. When

10-6



multiple alarmsmeet the specification of the rule, the system only displays the first receivedone on the client with a plus sign before it.

The following procedure describes how to set the condition for merging intermittent alarms.

Steps1. On the menu bar of the client window, select Fault > Setting > Intermittent Alarm

Setting.

The Intermittence Alarm Setting dialog box opens, as shown in Figure 10-6.

Figure 10-6 Intermittence Alarm Setting dialog box

2. To enable the intermittent alarm merging function, select the Enable intermittentalarm processing check box.

3. Modify the time and the number of alarms to specify the merging condition.

The default merging condition is that five alarms of the same alarm code are reportedby the same network element in one minute.

4. Click OK.


Follow-Up ActionThe system will merge intermittent alarms according to the setting.

10.5 Setting an Alarm Prompting RuleContextIn the NetNumen U31 system, you can set a prompting rule for concerned alarms. Aprompt dialog box opens or alerting sounds are produced when these alarms are received.

10-7



The following procedure describes how to set an alarm prompting rule for specific alarms.

Steps

1. In the client window, select Fault > Setting > Alarm Prompting Setting on the menubar to open the Alarm Prompting Setting tab.

2. On the Alarm Prompting Setting tab, click on the toolbar.

The Alarm Prompting Setting dialog box opens, as shown in Figure 10-7.

Figure 10-7 Alarm Prompting Setting Dialog Box

3. On the Basic tab, set the alarm prompting rule as follows:

a. Type a name and the additional information you want to add in the Name andDescription boxes.

b. Select an initial status for the rule: Activate or Suspend.

c. Select a prompting mode: Notify by dialog or Notify by sound.

If Notify by sound is selected, you can change the alerting sound by clicking theChoose button and selecting another sound file. Type a number in the Times ofrepetition spin box to set the repeat times of the sound.

4. On the Condition tab, set the conditions on four sub-tabs (Location, Alarm Code,Probable Cause, and Others) to specify the alarms that need to be prompted whenthey are reported.

10-8



5. Click OK.


Result

The created alarm prompting rule appears on theAlarmPrompting Setting tab. And if thealarm prompting rule is enabled, the system will prompt the occurrence of alarms meetingthe specified conditions in sound or a pop-up dialog box, as shown in Figure 10-8.

Figure 10-8 Alarm Prompting

Follow-Up Action

On the Alarm Prompting Setting tab, you can also manage existing alarm promptingrules by using the shortcut buttons on the toolbar, as described in Table 10-1.

Table 10-1 Description of Toolbar Buttons on the Alarm Prompting Setting Tab

Button Function

Modify an existing alarm prompting rule.

Delete an suspensive alarm prompting rule.

Activate an alarm prompting rule.

Suspend an alarm prompting rule.

Refresh the information of alarm prompting rules.

Open the alarm prompting dialog box again. If multiple alarm prompting rules

have been made, the open dialog box shows all the alarms meeting the

conditions of all these rules.

10-9



10.6 Customizing Alarm Sounds and ColorsPrerequisites

The sound file(s) to be used are available.

Context

Different sounds and colors are used to indicate alarms at different severity levels. Youcan customize the sounds and colors according to your own preference.

Steps

1. In the client window, do one of the following to open the Alarm Sound and ColorSetting dialog box.l Choose Fault > Setting > Alarm Sound and Color Setting on the menu bar.l Choose System > Customize > Alarm Sound Color Setting on the menu bar.

2. On the Sound Setting tab as shown in Figure 10-9, select the sounds for differentalarm severity levels.

Figure 10-9 Alarm Sound and Color Setting dialog box (Sound Setting Tab)

For example,

10-10



a. To select the sound for critical alarms, click the Choose button corresponding toCritical. In the pop-up Open dialog box, find and select the sound file, and thenclick the Open button.

b. To listen the sound file selected for critical alarms, click the correspondingAudition button.

c. To mute the sound of critical alarms, select the corresponding Mute check box.

d. To determine when the system generates alarm sounds, select a sound model.

If Sound According to the Highest Severity Unacknowledged Alarm isselected, the system will produce alarm sounds according to the highest severityof existing unacknowledged alarms.

If Receiving Alarm Message is selected, the system will produce alarm soundsupon receiving new alarms. You can also select Sound When Restoring, andthen click the Setting button to set the sound files for the system to produce alarmsounds when alarms are cleared.

e. To restore the default settings of alarm sounds (that is, use the default sound files),click Restore to default.

f. To mute all alarm sounds, select the All Mute check box.

3. On the Color Setting tab, set the colors for different alarms, as shown in Figure 10-10.

Figure 10-10 Alarm Sound and Color Setting dialog box (Color Setting Tab)

10-11



For example, to set the color for critical alarms, do one of the following:

l Click the Critical drop-down box, and select a new color by clicking thecorresponding color box.

l Or, click the Critical drop-down box, and clickOther Colors. In the pop-up ColorSetup dialog box, select or set a new color and click OK.

4. Click OK to complete the customization of alarm sounds and colors.


10.7 Creating an Alarm-Suppressing Plan TaskContext

A suppressing plan task suppresses the alarms raised during engineering cut-over,changeover, and so on. During task execution, when the first condition-meeting alarm isreported, the system generates a new alarm as the primary alarm. The reported alarmbecomes a secondary alarm. The alarms reported later are all treated as the secondaryalarms of that primary alarm.

Steps

1. On the main menu of the NetNumen U31 system, select Fault > Suppres Plan TaskManagement to open the Suppress Plan Task Management tab, as shown in Figure10-11.

Figure 10-11 Suppress Plan Task Management Tab

2. On the toolbar, click to open the Suppress Plan Task dialog box, as shown inFigure 10-12.

10-12



Figure 10-12 Suppress Plan Task Dialog Box

Set parameters in the Suppress Plan Task dialog box. Table 10-2 describes therelated parameters.

Table 10-2 Parameters for Creating a Suppress Plan Task


Task Name Indicates the name of the task.

Task Type Indicates the task type. The options are:

l Change: task for network changeover

l Cut: task for network cut-over

l Others: task for other cases

Task Status Indicates the initial status of the task after

creation. The options are: Activate and

Suspend

Task Period Indicates the task execution period:

l Effective Temporarily: specifies a duration

for a task that runs once.

l Effective Everyday: specifies a duration

for a task that runs every day.

Detail Indicates the remarks for the task.

3. Click the NE tab, as shown in Figure 10-13. Select an NE type, and specify the NEson the tab.

10-13



Figure 10-13 The NE Tab

4. Click OK to finish.


Result

The system will suppress the alarms that meet the specified conditions.

10-14


FiguresFigure 1-1 Composition of the Fault Management System ........................................ 1-2

Figure 1-2 Fault Management Window ..................................................................... 1-7

Figure 2-1 NetNumen Configuration Center .............................................................. 2-4

Figure 2-2 Expanding the Forward Node................................................................... 2-4

Figure 2-3 Expanding the Mail Forward Node ........................................................... 2-5

Figure 2-4 Selecting the Forward Type Node ............................................................ 2-6

Figure 2-5 Expanding the GSM Moden Forward Node.............................................. 2-7

Figure 2-6 Expanding the SMPP Forward Node........................................................ 2-8

Figure 2-7 Expanding the CMPP Forward Node ....................................................... 2-9

Figure 2-8 Expanding the Alarm Box Forward Node ................................................. 2-9

Figure 2-9 Active Alarm Monitoring Tab .................................................................. 2-11

Figure 2-10 Notification Monitoring Tab................................................................... 2-12

Figure 2-11 The Tab of Alarm Monitor by NE........................................................... 2-13

Figure 2-12 Monitoring Active Alarms of an NE....................................................... 2-14

Figure 2-13 Monitoring Active Minor Alarms of an NE ............................................. 2-14

Figure 2-14 The Tab of Alarm Monitor by NE Type.................................................. 2-15

Figure 2-15 Monitoring Active Alarms of an NE Type .............................................. 2-16

Figure 2-16 Monitoring Active Minor Alarms of an NE Type..................................... 2-16

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

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

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

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

Figure 3-5 Query Active Alarms Dialog Bbox (Others Tab) ...................................... 3-11

Figure 3-6 Advanced Dialog Box for Active Alarm Query ........................................ 3-12

Figure 3-7 Query Result of Active Alarms ............................................................... 3-13

Figure 3-8 Query Result of Active Alarms (with the History Alarms Pane) ............... 3-14

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

Figure 3-10 The Advanced Dialog Box.................................................................... 3-16

Figure 3-11 The Extended Clear Type Dialog Box................................................... 3-17

Figure 3-12 Query Result of Historical Alarms......................................................... 3-18

Figure 3-13 The Query Notifications Dialog Box...................................................... 3-19

Figure 4-1 Default Statistic Setting Dialog Box (Location Tab)................................... 4-3

I


Figure 4-2 Default Statistic Setting Dialog Box (Alarm Code Tab).............................. 4-4

Figure 4-3 Default Statistic Setting Dialog Box (Others Tab)...................................... 4-5

Figure 4-4 Alarm Frequency Statistics By Alarm Code_Top 10 ................................. 4-6

Figure 4-5 The Alarm Basic Statistic Dialog Box (Basic Tab)..................................... 4-8

Figure 4-6 Preview of Statistical Result ..................................................................... 4-8

Figure 4-7 Alarm Basic Statistic Template dialog box (Condition Tab) ....................... 4-9

Figure 4-8 Basic Statistical Result of History Alarms ............................................... 4-10

Figure 4-9 History Alarm Busy-time Statistic Dialog Box (Basic Tab) ....................... 4-11

Figure 4-10 Statistical Result of History Alarms in Busy Hours................................ 4-12

Figure 4-11 New History Alarm Basic Statistic Template Dialog Box........................ 4-13

Figure 4-12 VIP Site Alarm Statistics ...................................................................... 4-16

Figure 4-13 Alarm Panel ......................................................................................... 4-17

Figure 4-14 Timing Statistic Task Management Tab ................................................ 4-18

Figure 4-15 Statistic Task Dialog Box...................................................................... 4-19

Figure 4-16 Custom Execution Time Area............................................................... 4-20

Figure 4-17 Timing Export Task Management Tab .................................................. 4-22

Figure 4-18 Timing Export Alarm Task Dialog Box (Basic Tab) ................................ 4-23

Figure 4-19 Custom Execution Time Area............................................................... 4-24

Figure 4-20 Timing Export Alarm Task Dialog Box (Condition Tab).......................... 4-25

Figure 5-1 Forwarding Setup Dialog Box................................................................... 5-6

Figure 5-2 Select Users Dialog Box .......................................................................... 5-7

Figure 5-3 Alarm Acknowledging Rule dialog box (Basic Tab)................................... 5-9

Figure 5-4 Alarm Acknowledging Rule dialog box (Condition Tab)........................... 5-10

Figure 5-5 Rack Diagram........................................................................................ 5-12

Figure 5-6 Details of an Active Alarm ...................................................................... 5-14

Figure 5-7 Details of a Historical Alarm ................................................................... 5-15

Figure 5-8 Handling Suggestions of an Alarm ......................................................... 5-17

Figure 5-9 Related Rules dialog box ....................................................................... 5-18

Figure 5-10 Print Setup dialog box (General Tab) ................................................... 5-20

Figure 5-11 Print Setup dialog box (Page Setup Tab) .............................................. 5-20

Figure 5-12 Print Setup dialog box (Advanced Tab) ................................................ 5-21

Figure 6-1 Rule Setting Tab ...................................................................................... 6-6

Figure 6-2 The Rule Setting Tab ............................................................................... 6-7

Figure 6-3 Selecting an Alarm Rule Type .................................................................. 6-8

Figure 6-4 Alarm Acknowledging Rule Dialog Box (Basic Tab).................................. 6-9

II

Figures

Figure 6-5 Alarm Acknowledging Rule Dialog Box (Condition Tab-Location) ........... 6-10

Figure 6-6 Alarm Acknowledging Rule Dialog Box (Condition Tab-AlarmCode) ................................................................................................... 6-10

Figure 6-7 Alarm Acknowledging Rule Dialog Box (Condition Tab-Others) .............. 6-11

Figure 6-8 Alarm Filtering Rule Dialog Box (Basic Tab) ........................................... 6-13

Figure 6-9 Alarm Delaying Rule Dialog Box (Basic Tab).......................................... 6-14

Figure 6-10 Alarm Merging Rule Dialog Box (Action Tab)........................................ 6-16

Figure 6-11 Alarm Persisting Rule Dialog Box (Action Tab) ..................................... 6-18

Figure 6-12 Alarm Counting Rule dialog box (Action Tab) ....................................... 6-19

Figure 6-13 Alarm Forwarding Rule Dialog Box (Basic Tab) .................................... 6-20

Figure 6-14 Alarm Forwarding Rule Dialog Box (Action Tab)................................... 6-22

Figure 6-15 Alarm Trigger Script Rule Dialog Box (Basic Tab)................................. 6-24

Figure 6-16 Alarm Trigger Script Rule Dialog Box (Condition Tab-Single AlarmType) .................................................................................................... 6-24

Figure 6-17 Alarm Trigger Script Rule Dialog Box (Condition Tab-Multiple AlarmsType) .................................................................................................... 6-25

Figure 6-18 Alarm Restraining Rule by NE Dialog Box (Root Alarm Tab) ................ 6-26

Figure 6-19 Alarm Restraining Rule by NE Type Dialog Box (Condition Tab-NEType) .................................................................................................... 6-28

Figure 6-20 Alarm Restraining Rule by NE Type Dialog Box (Condition Tab-RootAlarm Code) ......................................................................................... 6-29

Figure 6-21 Alarm Restraining Rule by NE Type Dialog Box (ConditionTab-Consequential Alarm Code) ........................................................... 6-30

Figure 7-1 Handling Suggestion Setting Tab ............................................................. 7-2

Figure 7-2 Resource Type Tree ................................................................................ 7-4

Figure 8-1 Severity Regrading Setting Tab................................................................ 8-2

Figure 8-2 Created Severity Regrading Rule............................................................. 8-4

Figure 9-1 Alarm Box Dialog Box .............................................................................. 9-3

Figure 10-1 Alarm Code Description Setting Tab..................................................... 10-2

Figure 10-2 Alarm Code Description Setting dialog box .......................................... 10-2

Figure 10-3 The Reason Setting Tab....................................................................... 10-4

Figure 10-4 Reason Setting dialog box ................................................................... 10-5

Figure 10-5 Forward Template Setting dialog box ................................................... 10-6

Figure 10-6 Intermittence Alarm Setting dialog box ................................................. 10-7

Figure 10-7 Alarm Prompting Setting Dialog Box .................................................... 10-8

Figure 10-8 Alarm Prompting .................................................................................. 10-9

Figure 10-9 Alarm Sound and Color Setting dialog box (Sound Setting Tab) ........... 10-10

III


Figure 10-10 Alarm Sound and Color Setting dialog box (Color Setting Tab)........... 10-11

Figure 10-11 Suppress Plan Task Management Tab ............................................. 10-12

Figure 10-12 Suppress Plan Task Dialog Box ....................................................... 10-13

Figure 10-13 The NE Tab...................................................................................... 10-14

IV

TablesTable 1-1 Menus for Fault Management .................................................................... 1-7

Table 1-2 Buttons Related to Fault Management on the Main Toolbar ....................... 1-8

Table 4-1 Toolbar Buttons for Managing the Statistical Result ................................. 4-10

Table 4-2 Shortcut Menu Items for Managing Statistics Template............................ 4-15

Table 4-3 Toolbar Buttons for Managing Timing Statistic Tasks ............................... 4-21

Table 5-1 Operations in the dialog box Showing the Alarm Details .......................... 5-16

Table 6-1 Attributes of Alarm Rules........................................................................... 6-5

Table 6-2 Alarm Rule Management Operations......................................................... 6-6

Table 8-1 Description of Toolbar Buttons on the Severity Regrading SettingTab........................................................................................................... 8-2

Table 9-1 Alarm Box Parameters .............................................................................. 9-3

Table 10-1 Description of Toolbar Buttons on the Alarm Prompting SettingTab......................................................................................................... 10-9

Table 10-2 Parameters for Creating a Suppress Plan Task ................................... 10-13

V

Tables


GlossaryCMPP- ChinaMobile Point to Point

EMB- Environment Monitor Board

EMS- Network Element Management System

GSM- Global System for Mobile Communication

GUI- Graphical User Interface

IP- Internet Protocol

J2EE- JAVA 2 platform Enterprise Edition

LCD- Liquid Crystal Display

MML- Man Machine Language

NE- Network Element

NMS- Network Management System

OMC- Operation & Maintenance Center

OMM- Operation & Maintenance Module

QoS- Quality of Service

RNC- Radio Network Controller

SDR- Software Defined Radio

SMPP- Short Message Peer to Peer Protocol

VII


SMS- Short Message Service

TCP- Transfer Control Protocol

WCDMA- Wideband Code Division Multiple Access

XML- eXtensible Markup Language

VIII

netnumen u31 r18 unified element management system fault management operation guide

Documents

alarm classification

overview of fault management

fault management system

fault management functions

zte corporationno

fault severity

fault type

fault indication