Sjzl20092872-NetNumen M31 (RAN) (V3[1].10.420) Fault Management Operation Guide

NetNumen M31(RAN)Mobile Network Element Management SystemFault Management Operation Guide

Version 3.10.420

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter 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.1 July 20, 2009 Review and Test Comments Modification

R1.0 June 26, 2009 First Edition

Serial Number: sjzl20092872

Contents

Preface............................................................... i

Overview of Fault Management .........................1Overview....................................................................... 1

Introduction................................................................... 2

Fault Classification ...................................................... 2

Alarm Severity ........................................................... 3

Alarm Rule ................................................................ 3

Alarm Display ............................................................ 3

Opening Fault Management Interface ................................ 4

Closing Fault Management Interface.................................. 4

Fault Management Interface............................................. 5

User Customization......................................................... 8

Setting Alarm Sound................................................... 8

Setting Alarm Color ...................................................10

Setting Alarm Forward Template ..................................11

Regrading Alarm Severity ...............................................12

Realtime Fault Monitor ....................................15Overview......................................................................15

Monitoring Realtime Alarm..............................................15

Monitoring Realtime Notification ......................................17

Operations Based on Query Result ..................19Overview......................................................................19

Synchronizing Alarm ......................................................19

Acknowledging Alarm.....................................................21

Unacknowledging Alarm .................................................22

Clearing Alarm ..............................................................23

Forwarding Alarm ..........................................................24

Creating Rule ................................................................25

Querying Related Rules ..................................................27

Viewing Notification Details .............................................29

Viewing Alarm Details ....................................................31

Monitoring Specified Alarm .............................................33

Assigning Alarm ............................................................35

Locating Alarm on Topology View.....................................35

Locating Alarm on Rack View ..........................................36

Querying Alarm/Notification Statistics...............................36

Exporting Alarm/Notification ...........................................36

Printing Alarm/Notification ..............................................37

Fault Data Query .............................................41Overview......................................................................41

Querying Current Alarm .................................................41

Querying History Alarm ..................................................44

Querying Notification .....................................................47

Combined Query ...........................................................50

Displaying Current Alarm................................................51

Important Site Alarm Statistics........................................54

Setting VIP Site.........................................................54

Getting Alarm Statistics of Important Site .....................56

Fault Handling Suggestion...............................59Overview......................................................................59

Creating Alarm Maintenance Suggestion ...........................59

Importing Alarm Maintenance Suggestion .........................60

Exporting Alarm Maintenance Suggestion..........................62

Modifying Alarm Maintenance Suggestion..........................62

Deleting Alarm Maintenance Suggestion ...........................63

Fault Management Rule Setting.......................65Overview......................................................................65

Creating Management Rule .............................................65

Modifying Management Rule............................................66

Enabling Management Rule .............................................67

Disabling Management Rule ............................................68

Deleting Management Rule .............................................68

Refreshing Management Rule ..........................................69

Setting Alarm Merging Rule.............................................69

Setting Alarm Persisting Rule ..........................................70

Setting Alarm Counting Rule ...........................................70

Setting Alarm Global Filtering Rule...................................71

Setting Alarm Discarding Rule .........................................72

Setting Alarm Delaying Rule............................................72

Setting Alarm Restraining Rule ........................................73

Setting Alarm Masking Rule ............................................73

Setting Alarm User Filtering Rule .....................................74

Setting Alarm Forwarding Rule ........................................74

Setting Alarm Clearing Rule ............................................75

Setting Alarm Acknowledging Rule ...................................76

Setting Notification Global Filtering Rule ...........................76

Setting Notification Discarding Rule..................................77

Alarm Box Setting ...........................................79Overview......................................................................79

Creating Alarm Box Rule.................................................79

Modifying Alarm Box Rule ...............................................83

Deleting Alarm Box Rule .................................................83

Refreshing Alarm Box Rule..............................................84

Enabling Alarm Box Rule.................................................84

Disabling Alarm Box Rule................................................85

Figures ............................................................87

Tables .............................................................89

Glossary ..........................................................91

Preface

Purpose This manual introduces the operations of fault management of Net-Numen M31(RAN) Mobile Network Element Management System.

IntendedAudience

This document is intended for engineers and technicians who per-form operations on NetNumen M31(RAN) (Fault Management).

Prerequisite Skilland Knowledge

Wireless telecommunications technology

Local operating procedures and functions

What Is in ThisManual

This manual contains the following chapters:

TABLE 1 CHAPTER SUMMARY

Chapter Summary

Chapter 1, Overview ofFault Management

Introduces fault management, alarmclassification, fault management interfaceand exiting fault management interface.

Chapter 2, Realtime FaultMonitor

Describes realtime fault monitor andrealtime notification monitor.

Chapter 3, OperationsBased on Query Result

Describes operations based on fault dataquery result.

Chapter 4, Fault DataQuery

Describes fault data query methods.

Chapter 5, Fault HandlingSuggestion

Describes operations related to faulthandling suggestion,

Chapter 6, FaultManagement Rule Setting

Describes operations related to faultmanagement rule setting.

Chapter 7, Alarm BoxSetting

Describes alarm box setting methods.

Confidential and Proprietary Information of ZTE CORPORATION i

NetNumen M31(RAN) Fault Management Operation Guide

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Overview of FaultManagement

Table of ContentsOverview........................................................................... 1Introduction....................................................................... 2Opening Fault Management Interface .................................... 4Closing Fault Management Interface...................................... 4Fault Management Interface................................................. 5User Customization............................................................. 8Regrading Alarm Severity ...................................................12

OverviewAs an important component of ZTE NMS, fault management col-lects information and manages faults that occur during equipmentoperation. Via NMS fault management, the user can get networkoperation status, as well as locate/troubleshoot faults in a timelyway.

Major contents to be covered include:

Introduction

Opening Fault Management Interface

Closing Fault Management Interface

Fault Management Interface

User Customization

Regrading Alarm Severity

Confidential and Proprietary Information of ZTE CORPORATION 1


Introduction

Fault Classification

Faults can be classified by different standards. The following threeclassification standards are introduced: fault nature, fault time,and fault object.

1. Fault Nature

Alarm

The fault that persists during system operation and affectssystem reliability and normal services is referred to as analarm.

Due to its possible impact on normal system operation,alarm requires timely troubleshooting in which alarm causeis identified, and the fault is located and handled.

Notification

Notification refers to the fault or event that occurs dur-ing system operation and cannot be automatically restored.Examples include board reset, fake power-off, etc.

Notification is mostly caused by sudden environmentchange or other accidental factors. No special handling isnecessary. Only the notification that occurs persistentlyrequires troubleshooting.

2. Fault Time

Current Alarm

Current alarm is an active alarm that has occurred but hasnot been restored yet.

History Alarm

History alarm is an alarm that has been restored. The usermay try to improve system reliability and stability based onanalysis and summary of history alarm information.

3. Fault Object

Communication Alarm

It refers to communication-related alarm that occurs duringsystem operation, such as abnormal link status, inaccessi-ble signaling point, unavailable signaling link, link interrup-tion between foreground NE and background NMS, etc.

Environment Alarm

It refers to environment-related alarm that occurs dur-ing system operation, such as rack temperature alarm,equipment room temperature alarm, voltage alarm, envi-ronment humidity alarm, door access control alarm, smogalarm, infrared alarm, lightning alarm, etc.

Equipment Alarm

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview of Fault Management

It refers to equipment-related alarm that occurs during sys-tem operation, such as fan alarm, optical module faulty,CPU overload, input clock abnormal, etc.

Processing Alarm

It refers to the alarm that occurs during system processingprocess, such as ATM cell processing alarm, SDH signalloss, startup file nonexistent, etc.

QoS Alarm

It refers to the alarm that directly affects service opera-tion quality, such as CS domain QoS alarm-RNC call lossrate, PS domain QoS alarm-RNC call loss rate, cell RRCaccess success rate, CS RAB assignment success rate, PSRAB assignment success rate, cell soft/hard handover suc-cess rate, RNC soft/hard handover success rate, inter-sys-tem handover success rate (CS domain), inter-system han-dover success rate (PS domain), CPU utilization, peak CPUutilization, etc.

Alarm Severity

There are four alarm levels by default, which are indicated in de-scending order of severity as:

Critical

Major

Minor

Warning

Alarm severity can be user-defined if necessary.

Alarm Rule

The NMS provides a rich variety of alarm management rules. Viasetting alarm rule, the user may define the alarm type and alarmseverity to be reported, whether automatic processing is needed,and automatic processing mode.

Users are recommended to customize alarm management rulesafter having a good knowledge of the NMS and based on firsthandexperience of alarm handling.

Alarm Display

The fault information generated by the NMS is displayed in thefollowing ways.

1. Topology View



On topology view, the user may view alarm severity and thenumber of alarms on a realtime basis via alarm color and sta-tistical information.

2. Alarm Box

As an important component of communication equipment,alarm box (ALB) indicates equipment fault status in a timely,correct and visual way, thus facilitating fault location andtroubleshooting. There are two types of alarm boxes: softalarm box and hard alarm box.

Soft alarm box is a tool software attached to NMS software.It is used on client side display alarm severity and the num-ber of alarms in graphic form and on a realtime basis.

Located in equipment room, hard alarm box is connectedto NMS equipment via IP protocol. With NMS software,the user may define alarm box display rule and alarm boxcontrol information, and send qualified foreground fault in-formation to the alarm box as fault indication output.

3. Fault Management Interface

After starting NMS, click View > Fault Management on themenu bar to open Fault Management interface. The usermay view alarm details on the interface.

Opening Fault ManagementInterface

Prerequisites NMS system has started up.

Steps 1. Click View > Fault Management on the menu bar to openFault Management interface.

END OF STEPS

Closing Fault ManagementInterface


Fault Management interface is open.

Context To close fault management interface.

Steps 1. Click of tab to close Fault Manage-ment interface.

END OF STEPS



Fault Management InterfaceFault Management interface is shown in Figure 1.

FIGURE 1 FAULT MANAGEMENT INTERFACE

1. Main menu2. Tool bar3. Resource/Management View

4. Fault information view5. Message area6. Status bar

Main Menu Main menu description is shown in Table 2.

TABLE 2 MAIN MENU DESCRIPTION

Menu Item Function

System Setting system function property

View Listing submenu items that can beused to open interfaces of varioussystem modules

Query Querying current/history alarms,or notifications;

Viewing alarm monitor

Synchronizing alarms

Setting Setting alarm management rules,alarm box, NE filter rule, etc.

Help Providing system help information

Tool Bar Description of icons on the tool bar is shown in Table 3.



TABLE 3 TOOL BAR ICON DESCRIPTION OF FAULT MANAGEMENT

Icon Indication Description

Lock Screen Lock screen

Logout Log out the currentaccount

View Current Alarms Query current alarminformation basedon user-specifiedcondition

View History Alarms Query history alarminformation basedon user-specifiedcondition

View Notifications Query notificationinformation basedon user-specifiedcondition

Help Provide Helpinformation

Resource/Man-agement View

The structure of Resource View and Management View aresimilar to that of Windows directory tree. Resource View treeis shown in Figure 2. Management View tree is shown in Figure3.

FIGURE 2 RESOURCE VIEW TREE



FIGURE 3 MANAGEMENT VIEW TREE

NEs are organized in the form of tree under Resource View. Thenodes under the tree indicate the functional units in NE. Adjacentnodes under the tree are in parallel or hierarchical relationship.Resource View truthfully demonstrates the physical relationshipbetween the functional units of managed NE.

Fault management functions are organized in the form of treeunder Management View. The nodes under the tree indicatethe functional objects of fault management. Management Viewclearly displays all functions of fault management. The user mayview and set alarms/notifications via Management View.

Click the following two bars to switch between Resource Viewand Management View.

Fault InformationView

Fault information view is the main interface of fault managementat client side. It displays various fault information based on thegiven operation.

Status Bar Status bar displays user and server information of the current loginaccount.



User Customization

Setting Alarm Sound



Context The user may customize alarm sounds for different alarm severitylevels at client side, which enables the user to identify the alarmseverity by sound.

The alarm sound file formats supported by the system include aif,au, mid, and wav.

Caution:

The sound parameter will take effect soon after configuration. Ifthe configured file path is incorrect, the system will play the defaultsound file.

Steps 1. On Fault Management interface, click Setting > Preferenceson the menu bar. Preferences interface appears, as shown inFigure 4.



FIGURE 4 ALARM SOUND SETUP

2. On Alarm Sound Setup tab, configure the sound modes andsound files for four alarm severity levels. The user may trialplay the sound file online.

Note:

The default Sound Mode is Silence. If the user wants to initi-ate sound monitor, select Continuous Sound or Short Beepsfrom the Sound Mode combo box. Click the Select buttonto choose sound file. The default file path of sound files is\ums-clnt\platform\pal\uep-pal-fm.par\res\sound.

3. Click OK to save the settings.

END OF STEPS



Setting Alarm Color



Context The user may customize alarm color for different alarm severitylevels at client side, which enables the user to identify alarm sever-ity by color.

Steps 1. On Fault Management interface, click Setting > Preferenceson the menu bar. Preferences interface appears.

2. On Alarm Color Setup tab, configure the color for four alarmseverity levels, as shown in Figure 5.

FIGURE 5 ALARM COLOR SETUP




END OF STEPS

Setting Alarm Forward Template



Context The user may customize the forwarding information format of mes-sage/email, which enables the user to send the alarms to the des-ignated mailbox/handset via email/short message.

Steps 1. On Fault Management interface, click Setting > Preferenceson the menu bar. Preferences interface appears.

2. On Forward Template Setup tab, configure message/emailforwarding format and the forwarded information format, asshown in Figure 6.

FIGURE 6 FORWARD TEMPLATE SETUP




END OF STEPS

Regrading Alarm SeverityPrerequisites NMS system has started up.


Context Each alarm code has a default alarm severity level. The user mayalso modify the alarm severity level if necessary. Alarm severityrules can be queried and modified on Severity Regrading Set-ting interface.

Steps 1. On Fault Management interface, click Setting > Severity Re-grading Setting on the menu bar. Severity Regrading Set-ting interface appears, as shown in Figure 7. Tool bar icondescription is shown in Table 4.

TABLE 4 TOOL BAR ICON DESCRIPTION OF SEVERITY REGRADINGSETTING


Import Importing severityregrading settings

Export Exporting severityregrading settings

Save Saving severitymodification

Refresh Refreshing theregrade setting ofalarm severity

Reset Restoring alarmseverity to defaultsetting

Find Looking for theseverity informationof alarm code by keywords



FIGURE 7 SEVERITY REGRADING SETTING INTERFACE

2. Select System Type and the alarm codes subject to the se-lected system type are displayed in the list. Select an alarmitem whose severity information is to be modified. Click thecombo box on New Severity column to display the pull-downlist, as shown in Figure 8.

FIGURE 8 SEVERITY REGRADING PULL-DOWN LIST

3. Regrade alarm severity by selecting a new severity level. Afterregrading, appears on Modify Status column, as shownin Figure 9.



FIGURE 9 REGRADE SEVERITY LEVEL

4. Click on the tool bar to synchronize the modification betweenclient and server database.

Tip:

If Original is selected in New Severity pull-down list, thealarm severity level can be restored to system default setting.

END OF STEPS


C h a p t e r 2

Realtime Fault Monitor

Table of ContentsOverview..........................................................................15Monitoring Realtime Alarm..................................................15Monitoring Realtime Notification ..........................................17

OverviewNetNumen M31 NMS provides powerful fault view and monitorfunctions. Via monitoring and querying alarm/notification infor-mation, the user may monitor equipment faults, locate faults onrack view and get fault handling suggestion information.

Monitoring Realtime AlarmPrerequisites NMS system has started up.


Context The user may monitor realtime alarms on NMS interface, which en-ables the viewing of network operation status and troubleshootingin a timely way. Realtime alarm monitor truthfully reflects the sta-tus of the alarms that require handling.

Realtime Alarm Monitor view is composed of two panes: Real-time Current Alarms and Realtime History Alarms. RealtimeCurrent Alarms is responsible for realtime monitoring of currentalarms, and Realtime History Alarms is responsible for realtimemonitoring of history alarms.

Realtime History Alarms enables the getting and tracing of faultrecovery status. It truthful reflects the fault handling and recoverystatus since the starting time of the monitoring.



Caution:

When the user opens Fault Management interface, RealtimeAlarm Monitor view will appear by default.

Realtime History Alarms pane displays the realtime informationof history alarms that come into existence after monitor startingtime. Therefore, Realtime History Alarms pane is blank whenstarting Realtime AlarmMonitor. As time goes on, history alarminformation is generated. Contents on Realtime History Alarmspane will be refreshed realtime to trace the latest history alarmdata.

Steps 1. On Fault Management interface, click Query > RealtimeAlarm Monitor on the menu bar. Realtime Alarm Monitorinterface appears, as shown in Figure 10.

FIGURE 10 REALTIME ALARM MONITOR INTERFACE

Interface Description

TABLE 5 TOOL BAR ICON DESCRIPTION OF REALTIME ALARM MONITOR


Customize DisplayColumns

Customizing thecolumns to bedisplayed in alarmlist

Export Exporting all alarmdata on RealtimeAlarm Monitorinterface into a file

Print Printing the alarmdata on RealtimeAlarm Monitorinterface

Alarm Sound Setup Setting alarm sound


Chapter 2 Realtime Fault Monitor


Full Screen Displaying alarmlists in full screen

Lock Scroll Locking the selectedalarm. After lockingthe selected item,even if alarm listchanges, the itemkeeps selected bythe system.

END OF STEPS

Monitoring RealtimeNotification



Context The user may monitor realtime notifications on NMS interface,which enables the viewing of network operation status in a timelyway. Realtime notification monitor truthfully reflects the status ofthe problems that occur during equipment operation and requirehandling. The notifications that occur before the opening of Real-time Notification Monitor interface are not displayed.

Caution:

Realtime Notification Monitor interface displays the realtimeinformation of notifications that occur after monitor starting time.Therefore, Realtime Notification Monitor interface is blankwhen starting Realtime Notification Monitor. As time goeson, notification information is generated. Contents on RealtimeNotification Monitor interface will be refreshed realtime to tracethe latest notification data.

Steps 1. On Fault Management interface, click Query > Realtime No-tification Monitor on the menu bar. Realtime NotificationMonitor interface appears, as shown in Figure 11.



FIGURE 11 REALTIME NOTIFICATION MONITOR INTERFACE


TABLE 6 TOOL BAR ICON DESCRIPTION OF REALTIME NOTIFICATIONMONITOR

Icon Indication Notification


Customizing thecolumns to bedisplayed innotification list

Export Exporting allnotification dataon RealtimeNotificationMonitor interfaceinto a file

Print Printing notificationinformation

Remove All Data Removing all dataon notificationlist. The removednotifications canbe queried vianotification query.

Lock Scroll Locking the selectednotification. Afterlocking the selecteditem, even ifnotification listchanges, the itemkeeps selected bythe system.

END OF STEPS


C h a p t e r 3

Operations Based onQuery Result

Table of ContentsOverview..........................................................................19Synchronizing Alarm ..........................................................19Acknowledging Alarm.........................................................21Unacknowledging Alarm .....................................................22Clearing Alarm ..................................................................23Forwarding Alarm ..............................................................24Creating Rule....................................................................25Querying Related Rules ......................................................27Viewing Notification Details.................................................29Viewing Alarm Details ........................................................31Monitoring Specified Alarm .................................................33Assigning Alarm ................................................................35Locating Alarm on Topology View.........................................35Locating Alarm on Rack View ..............................................36Querying Alarm/Notification Statistics ..................................36Exporting Alarm/Notification ...............................................36Printing Alarm/Notification ..................................................37

OverviewThis chapter focuses on related operations based on alarm/notifi-cation query result. These operations help the user handle equip-ment faults in a timely way.

Synchronizing AlarmPrerequisites NMS client and server have started up.


Context When the link between NMS server and NE is interrupted, the latestalarm information generated by NE will fail to be reported to NMSserver.

In order to ensure integrity and consistency of alarm data, theuser may synchronize alarm data of the designated NE.



Steps 1. On the topology tree of Resource View, right-click the NEwhose alarm data are to be synchronized. Select Alarm syn-chronization in the shortcut menu. Or click Query > AlarmSynchronization on the main menu. Alarm Synchroniza-tion interface appears, as shown in Figure 12.

FIGURE 12 ALARM SYNCHRONIZATION INTERFACE

2. Configure system type and location of the NE to be synchro-nized.

i. Click Select and select NE type. The NEs of the selectedtype are listed in the Location list box (left).

ii. Select the desire NE(s) in the left list box. Click tochoose the selected NE(s), which will appear in the rightlist box.

3. Click OK to complete alarm synchronization. A message boxappears, prompting sending success of synchronization com-mand, as shown in Figure 13.


Chapter 3 Operations Based on Query Result

FIGURE 13 SYNCHRONIZATION COMMAND SENT SUCCESSFULLY

END OF STEPS

Acknowledging AlarmPrerequisites NMS client and server have started up.


Context Newly generated alarms are required to be handled and acknowl-edged. For the alarm that have been handled and acknowledged,the user may configure its acknowledgement status as unac-knowledged, in order to differentiate it from acknowledgedalarms.

When acknowledging an alarm, the operator is required to inputacknowledgement information. Meanwhile, the system records ac-knowledgement time and operator.

Steps 1. Open any alarm list. This topic takes Realtime Alarm Mon-itor interface as an example. Right-click an alarm item thathas not been acknowledged. The shortcut menu appears, asshown in Figure 14.

FIGURE 14 SELECT AN ALARM ITEM

2. Click Acknowledge in the shortcut menu. AcknowledgeAlarm interface appears, as shown in Figure 15.



FIGURE 15 ACKNOWLEDGE ALARM INTERFACE

3. After inputting acknowledgement information in Acknowl-edge Alarm interface, click OK to complete acknowledge-ment. The system records acknowledgement time, operator,and other related information.

END OF STEPS

Unacknowledging AlarmPrerequisites NMS client and server have started up.


Context If the user finds previous acknowledgment operation improper oracknowledgement information incorrect, the alarm that has beenacknowledged can be restored to unacknowledged status.

Steps 1. Open any alarm list. This topic takes Realtime Alarm Mon-itor interface as an example. Right-click an alarm item thathas been acknowledged. The shortcut menu appears.

2. Click Unacknowledged from the shortcut menu. Unac-knowledged Alarm interface appears, as shown in Figure16.



FIGURE 16 UNACKNOWLEDGED ALARM INTERFACE

3. After inputting unacknowledgement information in Un-acknowledged Alarm interface, click OK to completeunacknowledgement.

END OF STEPS

Clearing AlarmPrerequisites NMS client and server have started up.


Context After completing alarm handling, the user may clear the alarmdata from network equipment and the NMS. The alarm that hasbeen cleared is saved as history alarm.

Caution:

Alarm clearing clears alarm information from NMS database, notfrom NE. Therefore, if the user performs alarm synchronization,the alarm information of the NE will be reported and displayed incurrent alarm list again.

Steps 1. Open any alarm list. This topic takes Realtime Alarm Mon-itor interface as an example. Right-click an alarm item. Theshortcut menu appears.

2. Click Clear from the shortcut menu. Confirm interface ap-pears, as shown in Figure 17.



FIGURE 17 CONFIRM ALARM CLEARING

3. Click OK to clear the alarm.

END OF STEPS

Forwarding AlarmPrerequisites NMS client and server have started up.


Context When viewing current alarms, the user may select and send im-portant alarm information to designated handler via email/shortmessage, to improve alarm handling efficiency.

Both manual and automatic forwarding of alarm information aresupported by setting alarm forwarding rules.

Click Setting > Preferences on the main menu to open Pref-erences interface. The user may configure forward template onForward Template Setup tab. For details, please refer to Set-ting Alarm Forward Template in Chapter 1.

Caution:

Before forwarding information via email, please ensure that thesystem has been properly connected to SMTP server and thatSMTP server operation is normal. Before forwarding informationvia SMS, please ensure that the system has been properly con-nected to SMS module and that SMS module operation is normal.

Forwarding history alarm, notification and events are not sup-ported.


2. Click Forward in the shortcut menu. Forwarding Setup in-terface appears, as shown in Figure 18.



FIGURE 18 FORWARDING SETUP INTERFACE

3. Input user information on Forwarding Setup interface. Or

click to open Select a User interface. Performselection from the available forward email address(es) and for-ward phone number(s), as shown in Figure 19.

FIGURE 19 SELECT A USER

4. Click OK to forward the alarm to the designated handler.

END OF STEPS

Creating RulePrerequisites NMS client and server have started up.




Context Via creating rule, the user may create alarm rule based on thealarm data in the alarm list. The rules that can be created in-clude Alarm Discarding Rule, Alarm Global Filtering Rule, AlarmUser Filtering Rule, Alarm Forwarding Rule, Alarm Acknowledg-ing Rule, Alarm Clearing Rule, Alarm Delaying Rule, AlarmRestraining Rule, Alarm Merging Rule, Alarm Counting Rule,Alarm Persisting Rule, etc. Upon rule creation, rule parameterswill be initiated based on attribute value of the selected alarm.


2. Click Create Rule in the shortcut menu. Create Rule inter-face appears, as shown in Figure 20.

FIGURE 20 CREATE RULE INTERFACE

3. Select the alarm rule to be created. This topic takes AlarmDiscarding Rule as an example. Click OK to open the cor-responding rule creation (Alarm Discarding Rule) interface.Currently, rule parameters have been initiated by the systembased on attribute value of the selected alarm, as shown in Fig-ure 21. (For initial creation of alarm rules, please refer to theNM operation manual of corresponding equipment/product).



FIGURE 21 ALARM DISCARDING RULE (EXAMPLE)

4. Input user data and click OK to complete rule creation.

END OF STEPS

Querying Related RulesPrerequisites NMS client and server have started up.


Context Via querying related rules, the user can query the rules that mightaffect the selected alarm, which means that the alarm is within theregulation range of the rule. It is possible but not certain for therelated rules to affect the alarm.


2. Click Related Rules in the shortcut menu. Potential Affect-ing Rules interface appears, as shown in Figure 22.



FIGURE 22 POTENTIAL AFFECTING RULES INTERFACE


TABLE 7 TOOL BAR ICON DESCRIPTION OF POTENTIAL AFFECTING RULES


Modify Modifying rule

Enable Enabling rule

Disable Disabling rule

Delete Deleting rule

If there exists no rule related to this alarm, a message box willappear, prompting that no such rule exists, as shown in Figure23.

FIGURE 23 NO RELATED RULES

3. Click OK to complete the operation.

END OF STEPS



Viewing Notification DetailsPrerequisites NMS client and server have started up.


Context To view details of a notification.

Steps 1. Open any notification list. This topic takes Realtime Notifi-cation Monitor interface as an example. Right-click a notifi-cation item. The shortcut menu appears.

2. Click Details from the shortcut menu. Details interface ap-pears, as shown in Figure 24.

FIGURE 24 NOTIFICATION DETAILS


TABLE 8 TOOL BAR ICON DESCRIPTION OF NOTIFICATION DETAILS

Icon Description

Displaying details of theprevious notification item

Displaying details of the nextnotification item

Closing the Details interface

Parameter Description



TABLE 9 PARAMETER DESCRIPTION OF NOTIFICATION DETAILS

Item Description

Location It indicates where thenotification is generated.Location information includesNE, site, rack No, shelf No,board No., etc.

Site Name (OFFICE) The name of the specificNE/site where the notification isgenerated.

Alarm Object ID Notification object identifier.

Alarm Object Name Notification object name.

Board Type Type of the board where thenotification is generated.

Happen Time Time when the notificationhappens.

System Type Location of the system wherethe notification is generated.(For example, managedequipment)

Original ID Notification ID provided byforeground NE.

ID Notification ID provided bybackground NMS.

Device Name Name of the NE device wherethe notification is generated.

Notification Code Description Description of the notification inOMM.

Probable Cause Probable cause for thenotification.

Details Detailed description of thenotification.

NE Type Type of the NE where thenotification is generated.

Other Information Additional information on thenotification.

Importance It indicates the importanceof the notification, which fallsinto two levels: Important andordinary.

Notification Counter Used for notificationcompression.

END OF STEPS



Viewing Alarm DetailsPrerequisites NMS client and server have started up.


Context To view details of an alarm.


2. Click Details in the shortcut menu. Details interface appears,as shown in Figure 25.

FIGURE 25 ALARM DETAILS


TABLE 10 TOOL BAR ICON DESCRIPTION OF ALARM DETAILS

Icon Description

Displaying details of theprevious alarm item

Displaying details of the nextalarm item

Acknowledging the alarm

Unacknowledging the alarm thathas been acknowledged



Icon Description

Clearing the alarm

Forwarding the alarm to thehandler

Commenting on the alarm

Closing the Details interface


TABLE 11 PARAMETER DESCRIPTION OF ALARM DETAILS


Severity It indicates alarm severity,which falls into four levels:Critical, Major, Minor, andWarning.

Location It indicates where the alarm isgenerated. Location informationincludes NE, site, rack No, shelfNo, board No., etc.

Site Name (OFFICE) The name of the specific NE/sitewhere the alarm is generated.

Alarm Object ID Alarm object identifier.

Alarm Object Name Alarm object name.

Board Type Type of the board where thealarm is generated.

Original Alarm Describe Description of the alarm in OMM.

Happen Time Time when the alarm happens.

Alarm Code Each alarm corresponds to analarm code.

Original Probable Cause Description of the alarm causein OMM.

Alarm Type Alarm type, such asenvironment alarm, equipmentalarm, etc.

System Type Location of the system wherethe alarm is generated. (Forexample, managed equipment)

Original ID Alarm ID provided by foregroundNE.




ID Alarm ID provided bybackground NMS.

Device Name Name of the NE device wherethe alarm is generated.

Probable Cause Probable cause for the alarm.

Details Detailed description of thealarm.

Acknowledgement Status Alarm acknowledgement status,showing if the user knows theoccurrence of the alarm.

(Un)acknowledged Operator The person who performs alarm(un)acknowledgement.

(Un)acknowledged System System indication of alarm(un)acknowledgement status.

(Un)acknowledged Information The information inputted when(un)acknowledging the alarm.

(Un)acknowledged Time Alarm (un)acknowledged time.

Comment Information Comments on the alarm.

Last Update Time Alarm modification time.

Dispatch Status It indicates whether the alarmhas been assigned to anyhandler.

NE Type Type of the NE where the alarmis generated.

Other Information Additional information on thealarm.

Counter Used for alarm compression.

END OF STEPS

Monitoring Specified AlarmPrerequisites NMS client and server have started up.


Context To monitor the specified current alarm on an interface.

Steps 1. Open Realtime Alarm Monitor interface. Right-click analarm. The shortcut menu appears.



2. Select Specified Alarms Monitoring in the shortcut menu.Specified Alarms Monitoring interface appears, as shown inFigure 26.

FIGURE 26 SPECIFIED ALARMS MONITORING INTERFACE


TABLE 12 TOOL BAR ICON DESCRIPTION OF SPECIFIED ALARMSMONITORING



Customizing thecolumns displayed inthe alarm list

Export Exporting the alarmdata on SpecifiedAlarms Monitoringinterface to a file

Print Printing the alarmdata on SpecifiedAlarms Monitoringinterface

Lock Scroll Locking the selectedalarm. After lockingthe selected item,even if alarm listchanges, the itemkeeps selected bythe system.

END OF STEPS



Assigning AlarmPrerequisites NMS client and server have started up.


Context The NMS supports the assignment of an alarm to related handlerin the form of short message or email, which makes timely trou-bleshooting possible.


2. Select Alarm Assign in the shortcut menu. Alarm AssignConfiguration interface appears, as shown in Figure 27.

FIGURE 27 ALARM ASSIGN CONFIGURATION

3. After configuring forward email address, forward phone num-ber and deadline, click OK. The system will execute alarm as-signment.

END OF STEPS

Locating Alarm on TopologyView

Prerequisites NMS client and server have started up.


Context To open topology view, where the alarm-reporting NE is selected.




2. Select Go to Topo Map in the shortcut menu. Topology viewappears, and the NE where the alarm is generated is selectedby the system.

END OF STEPS

Locating Alarm on RackView



Context To open rack view and locate the board where the alarm is gener-ated.

Steps 1. Open Realtime Alarm Monitor interface. Right-click analarm and the shortcut menu appears.

2. Select Display Rack in the shortcut menu. Rack view is openand the board where the alarm is generated is selected.

END OF STEPS

Querying Alarm/NotificationStatistics



Context To query current/history alarm and notification information in thedatabase.

Steps To get alarm/notification-related statistics, please refer tothe O&M center operation manual of the corresponding prod-uct/equipment.

END OF STEPS

Exporting Alarm/NotificationPrerequisites NMS system have started up.


There exists alarm/notification information in the system.



Context To export all the data on the opening interface to a file. File formatcan be TXT/EXCEL/PDF/HTML/CSV.

Steps 1. Open any alarm/notification list. This topic takes Realtime

Alarm Monitor interface as an example. Click on the toolbar. Save interface appears, as shown in Figure 28.

FIGURE 28 EXPORT ALARM/NOTIFICATION

2. Select destination folder and input file name. Click Save tosave the file to the designated folder.

END OF STEPS

Printing Alarm/NotificationPrerequisites NMS client and server have started up.


There exists alarm/notification information in the system.

The printer to be used functions properly and the connectionbetween printer and NMS server is normal.

Context To print all the data on the opening interface. The user may setprint range, the number of copies, paper, layout, style, etc.

Steps 1. Open any alarm/notification list. This topic takes Realtime

Alarm Monitor interface as an example. Click on the toolbar. Print Setup interface appears, as shown in Figure 29.



FIGURE 29 PRINT SETUP INTERFACE

2. After configuration print parameters, click Print to print data,or click Preview All to preview data, as shown in Figure 30.



FIGURE 30 PRINT PREVIEW INTERFACE

END OF STEPS


C h a p t e r 4

Fault Data Query

Table of ContentsOverview..........................................................................41Querying Current Alarm .....................................................41Querying History Alarm ......................................................44Querying Notification .........................................................47Combined Query ...............................................................50Displaying Current Alarm....................................................51Important Site Alarm Statistics............................................54

OverviewThis chapter introduces the query function of fault management,including current/history alarm query, notification query, and com-bined query.

Querying Current AlarmPrerequisites NMS client and server have started up.


Context The user may query the desired current alarms by specifying suchconditions as location, happen time, alarm type, system type,probable cause, etc.

Steps 1. Click Query > View Current Alarms on the main menu offault management to open Current Alarm Query Conditionsinterface, as shown in Figure 31.



FIGURE 31 CURRENT ALARM QUERY CONDITIONS INTERFACE

2. Click on the tool bar. Query Current Alarm interface ap-pears, as shown in Figure 32.

FIGURE 32 QUERY CURRENT ALARM INTERFACE

3. Specify query conditions and clickOK. Query result is displayedon View Current Alarms interface in the form of table list.


Chapter 4 Fault Data Query


TABLE 13 TOOL BAR ICON DESCRIPTION OF CURRENT ALARM QUERY

Icon Description

Quick Search

Execute

New

Modify

Delete

Refresh

Key Parameter Description

TABLE 14 KEY PARAMETER DESCRIPTION OF CURRENT ALARM QUERY

Parameter Description Value Range

System Type Location of the system wherethe alarm is generated

The systems available to theuser.

Original ID Original ID of the alarm

Location It indicates where the alarmis generated.

Location information includessubnet, managed NE, rackNo, shelf No, board No., CPUNo., etc.

It depends on the selectedsystem type.

Alarm Code Alarm description

The description displayed bythe system is related to theselected system type.

Available descriptioninformation in the list

Severity Alarm severity level Critical/Major/Minor/Warning

Alarm Type Altogether there are six alarmtypes: Processing alarm,QoS alarm, Environmentalarm, Equipment alarm,Communication alarm, andOMS alarm.

Processing Alarm/QoSAlarm/EnvironmentAlarm/EquipmentAlarm/CommunicationAlarm/OMS Alarm

Probable Cause The probable cause displayedby the system is related tothe selected system type.

Available descriptioninformation in probablecause list




Happen Time Time when the alarmhappens.

Alarm occurrence time can bespecified as query condition.

Acknowledgement Status Alarm acknowledgementstatus set by the operator

Used as one query condition

Acknowledged/Unacknowl-edged

(Un)acknowledged Operator The operator who performsalarm (un)acknowledgement


Not available

(Un)acknowledged Time Alarm (un)acknowledged time


Begin Time, End Time,and Time Segment can bespecified as query condition.

NE Type Type of the NE where thealarm is generated


Not available

Details User-Defined alarm details Not available

Other Information User-Defined additionalinformation

Not available

Visibility Visibility of the alarm in alarmlist

Visible Data/Invisible Data

END OF STEPS

Querying History AlarmPrerequisites NMS client and server have started up.


Context The user may query the desired history alarms by specifying suchconditions as location, happen time, alarm type, system type,probable cause, etc.

Steps 1. Click Query > View History Alarms on the main menu offault management to open History Alarm Query Conditionsinterface, as shown in Figure 33.



FIGURE 33 HISTORY ALARM QUERY CONDITIONS INTERFACE

2. Click on the tool bar. Query History Alarm interface ap-pears, as shown in Figure 34.

FIGURE 34 QUERY HISTORY ALARM INTERFACE

3. Specify query conditions and clickOK. Query result is displayedon View History Alarms interface in the form of table list.




TABLE 15 TOOL BAR ICON DESCRIPTION OF CURRENT ALARM QUERY

Icon Description

Quick Search

Execute

New

Modify

Delete

Refresh


TABLE 16 KEY PARAMETER DESCRIPTION OF CURRENT ALARM QUERY


System Type Location of the system wherethe alarm is generated

The systems available to theuser

Original ID Original ID of the alarm

Location It indicates where the alarmis generated.

Location information includessubnet, managed NE, rackNo, shelf No, board No., CPUNo., etc.


Alarm Code Alarm description



Severity Alarm severity level Critical/Major/Minor/Warning

Alarm Type Altogether there are six alarmtypes: Processing alarm,QoS alarm, Environmentalarm, Equipment alarm,Communication alarm, andOMS alarm.

Processing Alarm/QoSAlarm/EnvironmentAlarm/EquipmentAlarm/CommunicationAlarm/OMS Alarm






Happen Time Time when the alarm happens Alarm occurrence time can bespecified as query condition.

Acknowledgement Status Alarm acknowledgementstatus set by the operator


Acknowledged/Unacknowl-edged

(Un)acknowledged Operator The operator who performsalarm (un)acknowledgement


Not available

(Un)acknowledged Time Alarm (un)acknowledged time



Restore Type Alarm restoration type


Normal/Cleared byUser/Restoration upon NERestart/Restoration uponSynchronization/Restorationupon Alarm Pool Fill-up/Restoration uponUMS Restart/AutoCleared/Restoration uponNE Delete/ADMC Alarm AutoCleared

Clear Operator The operator who clear thealarm


Not available

Restore Time The time when the alarm isrestored



NE Type Type of the NE where thealarm is generated


Not available

Details User-Defined alarm details Not available

Other Information User-Defined additionalinformation

Not available

Visibility Visibility of the alarm in alarmlist


END OF STEPS

Querying NotificationPrerequisites NMS client and server have started up.




Context The user may query the desired notification by specifying suchconditions as location, happen time, system type, probable cause,etc.

Steps 1. Click Query > View Notifications on the main menu of FaultManagement to open Notification Query Conditions inter-face, as shown in Figure 35.

FIGURE 35 NOTIFICATION QUERY CONDITIONS INTERFACE

2. Click on the tool bar. Query Notification interface ap-pears, as shown in Figure 36.



FIGURE 36 QUERY NOTIFICATION INTERFACE

3. Specify query conditions and clickOK. Query result is displayedon View Notifications interface in the form of table list.


TABLE 17 TOOL BAR ICON DESCRIPTION OF NOTIFICATION QUERY

Icon Description

Quick Search

Execute

New

Modify

Delete

Refresh




TABLE 18 KEY PARAMETER DESCRIPTION OF NOTIFICATION QUERY


System Type Location of the system wherethe notification is generated

The systems available to theuser

Original ID Original ID of the notification

Location It indicates where thenotification is generated.

Location information includesRNC NE, rack No, shelf No,board No., CPU No., etc.


Notification Code Description Notification code description





Happen Time Time when the notificationhappens

Notification occurrence timecan be specified as querycondition.

NE Type Type of the NE where thenotification is generated


Not available

Details User-Defined notificationdetails

Not available

Visibility Visibility of the notification innotification list


END OF STEPS

Combined QueryPrerequisites NMS client and server have started up.


Alarm/notification query conditions have been created.

Context Combined query is performed on Current Alarm Query Con-ditions/History Alarm Query Conditions/Notification QueryConditions interface. The user may perform combined query bymultiple query conditions that have been created. The alarms/no-tifications that meet the multiple query conditions will be displayedin query result.



Steps 1. Open Current Alarm Query Conditions/History AlarmQuery Conditions/Notification Query Conditions inter-face. Select multiple query conditions, as shown in Figure 37.Click on the tool bar.

FIGURE 37 SELECT QUERY CONDITIONS

2. The system carries out the query according to the selectedquery conditions and displays the query result in the form oftable list, as shown in Figure 38.

FIGURE 38 COMBINED QUERY RESULT

END OF STEPS

Displaying Current AlarmPrerequisites NMS client and server have started up.


Context The NMS may display current alarms by time.



Show All Current Alarms

Show Current Alarms in One Hour

Show Current Alarms in One Day

Steps Open NMS Fault Management interface.Show All Current Alarms

i. On Resource View tree of fault management, right-clickthe NE whose alarms are to be queried. Click Show cur-rent alarms > Show all current alarms in the shortcutmenu.

ii. Show all current alarms interface appears. Query resultis displayed in the form of table list, as shown in Figure 39.

FIGURE 39 SHOW ALL CURRENT ALARMS

Show Current Alarms in One Hour

i. On Resource View tree of fault management, right-clickthe NE whose alarms are to be queried. Click Show cur-rent alarms > Show current alarms in one hour in theshortcut menu.

ii. Show current alarms in one hour interface appears.Query result is displayed in the form of table list, as shownin Figure 40.



FIGURE 40 SHOW CURRENT ALARMS IN ONE HOUR

Show Current Alarms in One Day

i. On Resource View tree of fault management, right-clickthe NE whose alarms are to be queried. Click Show cur-rent alarms > Show current alarms in one day in theshortcut menu.

ii. Show current alarms in one day interface appears.Query result is displayed in the form of table list, as shownin Figure 41.

FIGURE 41 SHOW CURRENT ALARMS IN ONE DAY

END OF STEPS



Important Site AlarmStatisticsNetNumen M31 supports the creation of important site alarm sta-tistics via MML command and VIP site query. The user may performalarm query and realtime monitor of important sites on fault man-agement interface. Three types of Important sites, in descendingorder of importance, are VIP site, B Class site, and C Class site.Three command parameters are Subnet ID, NE ID, and priority.Priority 5 refers to VIP site. NE ID is the ID of Node B. Once a siteis set as important site, the user may get statistics of site alarmsof all severity levels in six time segments. The six time segmentsare:

In one hour

In one to two hour

In two to three hour

In three to four hour

In four to five hour

Before five hour

Currently, only TD-SCDMA and Node B support VIP site.

Setting VIP Site



Steps 1. Click View > MML Terminal to open MML Terminal inter-face.

2. Select the desired NE on the left topology tree or execute SETAMO: NE agent name; command by clicking Execute button,as shown in Figure 42. Set the name of the NE agent that NodeB NE belongs to.



FIGURE 42 SET NE AGENT NAME

3. Execute SET NETYPE: 0x800; command by clicking Executebutton.

FIGURE 43 SET NE TYPE

4. Execute SET NEPRIO: SubNet ID, NE ID. priority; com-mand by clicking Execute button.



FIGURE 44 SET NE PRIORITY

END OF STEPS

Example On NE agent of RNC1, set the Node B (ID=20) under the Subnet(ID=1) as VIP site. On MML Terminal interface, execute the fol-lowing three MML commands.

Tip:

If application for mutex right is required, input the following com-mand:

APPLYMUTEX:MOI= TSUBNETWORKID=9,TP72MEID=33333;

SET AMO: RNC1;

Tip:

The command above is equivalent to NE selection on NE agent treelocated in the upper left pane. The command of SET AMO is notnecessary on OMM.

SET NETYPE: 0x800;

SET NEPRIO: 1, 20, 5;

Getting Alarm Statistics of ImportantSite





Steps 1. Click Query > Important Site Alarm Stat on the main menuof fault management. Three submenu items appear, as shownin Figure 45.

FIGURE 45 IMPORTANT SITE ALARM STATISTICS

2. Click VIP Site Alarm Stat/B Class Site Alarm Stat/C ClassSite Alarm Stat. Corresponding alarm statistics are shown inthe form of table list.

END OF STEPS


C h a p t e r 5

Fault HandlingSuggestion

Table of ContentsOverview..........................................................................59Creating Alarm Maintenance Suggestion ...............................59Importing Alarm Maintenance Suggestion .............................60Exporting Alarm Maintenance Suggestion..............................62Modifying Alarm Maintenance Suggestion..............................62Deleting Alarm Maintenance Suggestion ...............................63

OverviewThis chapter covers the operations on fault handling suggestion.

Creating Alarm MaintenanceSuggestion



Context To create an the maintenance suggestion for an alarm whose sys-tem type is specified.

Steps 1. Click Setting > Maintenance Suggestion Setting on themain menu of fault management to open Maintenance Sug-gestion Setting interface.

2. Select system type in the pull-down list (This example selects

Managed Equipments as system type). Click on the toolbar. Maintenance Suggestion interface appears, as shownin Figure 46.



FIGURE 46 CREATE ALARM MAINTENANCE SUGGESTION

3. Select Alarm Code and Probable Cause. Input CustomizedSuggestions. Click OK to complete the creation.

Note:

Alarm Code and Probable Cause of an alarm are system-defined. The corresponding alarmmaintenance suggestion canbe customized.

END OF STEPS

Importing AlarmMaintenance Suggestion



The alarm maintenance suggestion to be imported exists.

Context The NMS supports the import of alarm maintenance suggestionfile in the format of xls or csv. The operation imports the alarmmaintenance suggestion defined in the file into the NMS.

Steps 1. Click Setting > Maintenance Suggestion Setting on themain menu to open Maintenance Suggestion Setting inter-face.

2. Click on the tool bar. A message box appears promptingthe operator to confirm import of suggestion data, as shown inFigure 47.


Chapter 5 Fault Handling Suggestion

FIGURE 47 CONFIRM DATA IMPORT

3. Click OK and file import interface appears, as shown in Figure48.

FIGURE 48 SELECT IMPORT FILE

4. Select the file to be imported and click Open. The designatedfile will be imported.

Caution:

If the system type of the currently displayed alarms is incon-sistent with that of the imported alarms, the latter should bechecked to see whether the imported data are correct. The im-ported data may include alarm information of different systemtypes.

END OF STEPS



Exporting AlarmMaintenance Suggestion



There exists alarm maintenance suggestion in the system.

Context The NMS supports the export of alarm maintenance suggestioninto a file in the format of txt, xls, csv, pdf, or html.


2. Click on the tool bar. A message box appears, promptingthe operator to confirm export of suggestion data, as shown inFigure 49.

FIGURE 49 DATA EXPORT SETTING

3. Select format of the exported file. Input file name and specifyfile path. Click Save to export alarm maintenance suggestionsto the designated location and file.

END OF STEPS

Modifying AlarmMaintenance Suggestion




Chapter 5 Fault Handling Suggestion

The alarm maintenance suggestion to be modified exists in thesystem.

Context To modify the existing alarm maintenance suggestion. Only theuser-defined/customized suggestion is modifiable.


2. Select an alarm in the alarm list and click on the tool bar. Orright-click an alarm in the alarm list and selectModify from theshortcut menu. Maintenance Suggestion interface appears

3. Modify alarm maintenance suggestion. Then click OK to savethe modification.

END OF STEPS

Deleting Alarm MaintenanceSuggestion



The alarm maintenance suggestion to be deleted exists in thesystem.

Context To delete the needless alarm maintenance suggestion.

Steps 1. On Maintenance Suggestion Setting interface, select analarm item whose maintenance suggestion is to be deleted.

2. Click on the tool bar. Or right-click the alarm item andclick Delete in the shortcut menu. A message box appearsasking the operator to confirm deletion. Click OK to delete themaintenance suggestion.

END OF STEPS


C h a p t e r 6

Fault Management RuleSetting

Table of ContentsOverview..........................................................................65Creating Management Rule .................................................65Modifying Management Rule ...............................................66Enabling Management Rule .................................................67Disabling Management Rule ................................................68Deleting Management Rule .................................................68Refreshing Management Rule ..............................................69Setting Alarm Merging Rule.................................................69Setting Alarm Persisting Rule ..............................................70Setting Alarm Counting Rule ...............................................70Setting Alarm Global Filtering Rule.......................................71Setting Alarm Discarding Rule .............................................72Setting Alarm Delaying Rule................................................72Setting Alarm Restraining Rule ............................................73Setting Alarm Masking Rule ................................................73Setting Alarm User Filtering Rule .........................................74Setting Alarm Forwarding Rule ............................................74Setting Alarm Clearing Rule ................................................75Setting Alarm Acknowledging Rule .......................................76Setting Notification Global Filtering Rule ...............................76Setting Notification Discarding Rule......................................77

OverviewThis chapter introduces operations and configurations on faultmanagement rules.

Creating Management RulePrerequisites NMS client and server have started up.


Context To create a new fault management rule.



Steps 1. Click Setting > Management Rule Setting on the mainmenu of fault management. Management Rule Settinginterface appears.

2. Select rule type in the pull-down list. Alarm Acknowledging

Rule is selected in this example. Click on the tool bar.Alarm Acknowledging Rule interface appears, as shown inFigure 50.

FIGURE 50 ALARM ACKNOWLEDGING RULE INTERFACE

3. After setting rule conditions, click OK to complete creation ofalarm acknowledging rule.

END OF STEPS

Modifying Management RulePrerequisites NMS client and server have started up.


The management rule to be modified exists in the system.

Context The user may modify fault management rule. Modifiable itemsinclude rule description, selection condition, etc.



Chapter 6 Fault Management Rule Setting

2. Select rule type in the pull-down list. Alarm AcknowledgingRule is selected in this example. Select the rule to be mod-

ified on the rule type list. Click on the tool bar. AlarmAcknowledging Rule interface appears.

3. Modify the description information and selection condition ofalarm acknowledging rule. Then click OK to complete the mod-ification.

END OF STEPS

Enabling Management RulePrerequisites NMS client and server have started up.


The management rule to be enabled is in disabled status.

Context To enable a rule that is in disable status.

Note:

The default rule status is enable once upon rule creation. Onlythe fault management rule in enable status is effective.


2. Select rule type in the pull-down list. Alarm AcknowledgingRule is selected in this example. Select the rule to be enabledon the rule type list. Click on the tool bar. Confirm interfaceappears, as shown in Figure 51.

FIGURE 51 CONFIRM RULE STATUS CHANGE (ENABLE)

3. Click OK to complete enablement of the rule.

END OF STEPS



Disabling Management RulePrerequisites NMS client and server have started up.


The management rule to be disabled is in enabled status.

Context To disable a rule that is in enable status.


2. Select rule type in the pull-down list. Alarm AcknowledgingRule is selected in this example. Select the rule to be disabledon the rule type list. Click on the tool bar. Confirm interfaceappears, as shown in Figure 52.

FIGURE 52 CONFIRM RULE STATUS CHANGE (DISABLE)

3. Click OK to complete disablement of the rule.

END OF STEPS

Deleting Management RulePrerequisites NMS client and server have started up.


The management rule to be deleted exists in the system.

Context To delete a fault management rule. The rule no longer takes effectafter deletion.


2. Select rule type in the pull-down list. Alarm AcknowledgingRule is selected in this example. Select the rule to be deleted

on the rule type list. Click on the tool bar. Confirm inter-face appears, as shown in Figure 53.



FIGURE 53 CONFIRM RULE DELETION

3. Click OK to confirm rule deletion.

END OF STEPS

Refreshing ManagementRule



Context In the case of simultaneous login of multiple clients into a server,if a management rule is configured by one client, the other clientsmight not see new configuration of the rule immediately due tonetwork factor. In this case, the other clients should re-obtain therule from the server to view the latest status of the rule.


2. Select rule type in the pull-down list. Alarm AcknowledgingRule is selected in this example. Select the rule to be re-

freshed on the rule type list. Click on the tool bar to per-form rule refreshment.

END OF STEPS

Setting Alarm Merging RulePrerequisites NMS client and server have started up.


Context The purpose of alarm merging rule is to reduce the items of thesame alarms displayed and to highlight important alarm.

The alarms merged by the rule are those belonging to the samefault type and occurring repeatedly. After creation of alarm merg-ing rule, qualified alarms will merge into one alarm displayed at



client end. The alarm will not disappear until the recovery of themerged alarms.

The rule is only applicable to the alarms that occur after rule es-tablishment.

Steps Please refer to the following sections in this chapter:

Creating Management Rule

Modifying Management Rule

Enabling Management Rule

Disabling Management Rule

Deleting Management Rule

Refreshing Management Rule

END OF STEPS

Setting Alarm PersistingRule



Context The purpose of alarm persisting rule is to alert the user to trou-bleshoot important faults that persist for a long time. When thealarm persisting time reaches a certain value within a certain pe-riod as specified in the rule, alarm persisting alarm will be gen-erated.








Refreshing Management Rule

END OF STEPS

Setting Alarm Counting RulePrerequisites NMS client and server have started up.




Context The purpose of alarm counting rule is to highlight the occurrencefrequency of important faults. When the alarm occurrence timesreaches a certain value within a certain period as specified in therule, alarm counting alarm will be generated.








END OF STEPS

Setting Alarm GlobalFiltering Rule



Context The purpose of alarm global filtering rule is to decide whether analarm will be sent from server to client. The rule is applicable toall login clients. When one alarm is filtered by the rule, all clientswill not be able to see the alarm.

The rule is applicable to all alarms, regardless of alarm occurrencetime.







END OF STEPS



Setting Alarm DiscardingRule



Context The purpose of alarm discarding rule is to decide whether an alarmshould be handled or discarded when the server gets the alarm.If an alarm meets the rule condition, the alarm will be discardedby the fault management module, which means that the alarmwill neither be let into database/alarm pool, nor be sent to theclient(s).








END OF STEPS

Setting Alarm Delaying RulePrerequisites NMS client and server have started up.


Context It is not necessary for the alarm that can be restored within thespecified delay time to be displayed at client end. If the alarm failsto be restored within the delay time as specified by the rule, thealarm will be declared at client end.

The alarm that can be restored within the specified delay time issaved in history alarm database.










END OF STEPS

Setting Alarm RestrainingRule



Context The purpose of alarm restraining rule is to restrain the alarms re-ported from foreground NE to background NMS. The alarm thatmeets the rule condition is kept at NMS server end and will not besent to client end.

The occurrence of some primary alarm will incur the emergenceof a series of incidental secondary alarms. Since the restorationof primary alarm results in the restoration of secondary alarms,the user should focus on the handling of primary alarm. Alarm re-straining rule highlights primary alarm and reduces network trafficby restraining secondary alarms.

The user should define primary alarm and secondary alarm re-spectively during creation of alarm restraining rule. When primaryalarm occurs, the NE will only report primary alarm instead of sec-ondary alarm. After restoration of primary alarm, whether sec-ondary alarm should be reported is up to configuration.








END OF STEPS

Setting Alarm Masking RulePrerequisites NMS client and server have started up.


Context The alarms th

Sjzl20092872-NetNumen M31 (RAN) (V3[1].10.420) Fault Management Operation Guide

Documents

Transcript of Sjzl20092872-NetNumen M31 (RAN) (V3[1].10.420) Fault Management Operation Guide