ONW430330 iManager M2000

www.huawei.com

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Fault Management


Referencesz M2000 Product Documentation

--Operation and Maintenance

--M2000 Operator Guide

--Fault Management


Objectivesz Upon completion of this course, you will be able to:

Master the concept related to Fault Management

Master how to perform the Fault management


Contents1. Basic concept

2. Alarm Browsing

3. Alarm Preprocessing

4. Alarm postprocessing


Basic Knowledge of Fault Management

z Event

The notices that generated when the system is running normally and should be prompt to users.

z Fault

The departure from system normal running, which may cause low performance .

z Alarm

The notices generated when the system detected faults. According to the auto-detect ability, alarms are group as two types:ADAC Alarm and ADMC Alarm.


Basic Knowledge of Fault Managementz Alarm log: The fault system collects all the alarms and

saves each alarm as one log record;

z Event log: The fault system collects all the events and

saves each event as one log record;

z Alarm list: The alarms need to be focused and dealt;

alarms in the list are counted by alarm types and alarm

source; users monitor the whole network mainly by Alarm

list;

z Alarm merge: Alarms of the same type and generated on

the same NE are shown as one record in the Alarm list.



z Alarm Management

Alarm management involves alarm display and statistics, audio

and visual alarm notification, alarm acknowledgement and

synchronization..

z Alarm Severities

The alarms can be define to critical, major, minor and warning

severities according to the severity of the alarm. You can adopt

corresponding processing strategy for different alarm severities

and redefine the alarm severities.



z Alarm Status

Alarm status refer to the alarm acknowledgement and

clearance status. You can adopt corresponding processing

measures for alarms of different status.



z Alarm Reporting Procedure

Start

Reporting alarms

End

Masking alarmsSaving alarms

information

Analyzing alarms

correlation

Redefining alarms Notifying the userof alarms


Fault Interface



2. Alarm Browsing

3. Alarm Preprocessing



Browsing the Alarm List z Choose Monitor > Browse Alarm List from the main menu,

or click on the toolbar.


Querying the Alarm Logsz Choose Monitor > Query Alarm Logs from the main menu,



Querying the Event Logsz Choose Monitor > Query Alarm Logs from the main menu,



Querying the Suppressed Alarm Logsz Choose Monitor > Query Suppressed Alarm Logs


Sorting the Query Results


Setting an NE Object Group


Setting an Alarm/Event Name Group

z choose Monitor > Alarm Setting > Alarm/Event Name Group

Management


Setting an Alarm/Event Name Group z choose Monitor > Alarm Setting > Alarm/Event Name Group

Management


Managing the Alarm/Event Template


Alarm Statistics


Alarm Statistics Result


Setting Columns in Alarm Interfacez Modify the alarm information and show some necessary

columns as required.



2. Alarm Browsing

3. Alarm and Events Preprocessing



Contents3. Alarm and Events Preprocessing

3.1 Alarm shieding

3.2 Alarm redefining

3.3 Alarm correlation

3.4 Setting Events as ADMC alarms

3.5 Alarm auto acknowledgement

3.6 User defined NE alarm


Setting Alarm Shield

NEM2000

Discard

Alarm Shield


Setting Alarm Mask Rule


Shielding an NE Alarmz Shield the alarms that you are not required.



3.1 Alarm shieding







Setting Alarm Redefine



3.1 Alarm shieding







Alarm Correlationz Aim

To reduce the redundant alarms.

z Correlative alarms

Correlative alarms are alarms that have correlations between

one another. One is the root alarm that raises other alarms.

A fault may result in multiple alarms, the non-root alarms do

not help in the fault location or analysis.


Alarm Correlationz Intermittent Alarms

If the interval between two clearance times of an alarm is less than set period of the cleared alarm, the alarm is an intermittent alarm.

z Repeat Events If the reporting times of an event is more than the set times in the set

period, the event is a repeat event.

z Simple/Advanced Correlation the correlation of the intermittent alarms or repeat events is

considered as simple correlation alarms.

the correlation of the other alarms is considered as advanced correlation alarms.


z Understand the alarm interval T

Fault alarm

Event alarm

Alarm Correlation

T0 tT T

Generate Recover

T

0 tT T T


Principles of Correlationz Two conditions

Alarm interval T Unit: second

If the alarm interval is less than or equivalent to T, the first alarm will enter the fault alarm current table or event alarm table. And the subsequent alarms whose alarm intervals are less than or equivalent to T will be saved to mask table or abandoned directly according to the correlation rules.

High frequency alarm threshold N Unit: times

If the system receives certain alarms (alarm intervals T and number of alarms N ) of the NE continuously, the system will generate high frequency alarms whose Equipment Serial Number is 0 and alarm level is higher. For fault alarms, if the subsequent alarm interval of the alarms are more than T, the high frequency alarm will clear.


Principles of Correlationz Examples

The correlation configuration of the MSCe is as follows: The fault alarm whose alarm level is Major is E1/T1 Loss of Signal

(ID=1101)

The interval of the alarm is 10s.

The times of high frequency alarm is 10.

The alarms meeting the correlation are saved to the mask table.

t

1 2 3 4 5 6 7 8 9 10 11

0T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12

12

t1 t2

T13

13


Principles of Correlationz Examples

Suppose T1 to T12 10 s, the M2000 will generate a E1/T1 Loss of Signal alarm for MSCe at t1. The alarm level is Critical and the alarm will clear at t2.

The first alarm is saved to fault alarm current table and the 2-12 alarms are saved to alarm mask table.



3.1 Alarm shieding







Setting Events as ADMC Alarms



3.1 Alarm shieding







Setting an Alarm Auto Acknowledgement Rule



3.1 Alarm shieding







Defining an User-Defined Alarm


Binding a User-Defined Alarmz To define the corresponding relations between the user-

defined alarms and the signal input ports. When a signal

received through a port meets the alarm triggering

conditions, the NE reports an alarm to the M2000, and the

alarm is bound with a customized name and ID.


Binding a User-Defined Alarm



2. Alarm Browsing

3. Alarm and Events Preprocessing



Manually Synchronize Alarm


Locating Alarmsz Use the function to locate the NE that raises the alarm by

the alarm record.


Client Timez Client Time is supported in the new version, which means

the client can get the time zone and DST settings from client OS and transform the alarm time into client time.


Alarm Acknowledgement


Manually Clearing Alarmz Manually clear the alarms that cannot be recovered

automatically or that are confirmed to be cleared.


Setting Alarm Experience


Setting Alarm Remote Notificationz Email

Transmitted through smtp Server.

z SMS Transmitted through wireless Modem. The wireless modem

can be connected to the M2000 Server or the 2000 Client.

Transmitted through short message center.

Alarm messages

EmailEmailSMSSMS


Setting Alarm Remote Notification


Alarm lifecycle


Summaryz This course mainly discuss about the fault management. In

this course, we need to master some basic concept related

to FM, and master how to perform the FM.

Thank youwww.huawei.com

Fault ManagementReferencesObjectivesContentsBasic Knowledge of Fault ManagementBasic Knowledge of Fault ManagementBasic Knowledge of Fault ManagementBasic Knowledge of Fault ManagementBasic Knowledge of Fault ManagementFault InterfaceContentsBrowsing the Alarm List Querying the Alarm LogsQuerying the Event LogsQuerying the Suppressed Alarm LogsSorting the Query ResultsSetting an NE Object GroupSetting an Alarm/Event Name Group Setting an Alarm/Event Name Group Managing the Alarm/Event TemplateAlarm StatisticsAlarm Statistics ResultSetting Columns in Alarm InterfaceContentsContentsSetting Alarm ShieldSetting Alarm Mask RuleShielding an NE AlarmContentsSetting Alarm RedefineContentsAlarm CorrelationAlarm CorrelationAlarm CorrelationPrinciples of CorrelationPrinciples of CorrelationPrinciples of CorrelationContentsSetting Events as ADMC AlarmsContentsSetting an Alarm Auto Acknowledgement RuleContentsDefining an User-Defined AlarmBinding a User-Defined AlarmBinding a User-Defined AlarmContentsManually Synchronize Alarm Locating AlarmsClient TimeAlarm AcknowledgementManually Clearing AlarmSetting Alarm ExperienceSetting Alarm Remote NotificationSetting Alarm Remote NotificationSetting Alarm Remote NotificationAlarm lifecycleSummary

Documents

ONW430330 iManager M2000