Ch.03 Fault Management

8/16/2019 Ch.03 Fault Management

1/23

Fault Management

1


2/23

Proprietary and Confidential

Alarm Workflow Perspective

New alarms All new alarms thatare reported from the

managed network

«Ack’ed» alarms All active alarms that have been

acknowledged by an operator

Cleared alarms All alarms that have

been cleared

Cleared & «ack’ed» All alarms that an operator has

acknowledged as cleared

2


3/23


“Time Slider” histogram For Alarms

The Time slider shows a histogram of the n!mber of alarms occ!rring alongthe time a"is

#t is possible to e"pand this time interval$ or to %oom in for a f!rther detailedhistogram

3


4/23


Fa!lt &anagement ' (asis

Alarm Severity are represented by colors

Alarms can be seen from the Tree view$ &ap view or from )ogical view

To see details$ right click on the item$ “Fault” and then “Current alarms” *

To see previo!s alarms from the data base$ right click on the item$ “Fault” and then “Historical alarms” *

&ap view )ogical tree view +eographical tree view

4


5/23


Fa!lt &anagement Tasks

Alarm ac,!isition in the form of notification reception from -.s

/isplay network alarm stat!s in many different ways

Coloring of graphical ob0ects in the network views

/isplay new 1!n'acked2 alarms and old 1acked2 alarmsindependently*

Propagation of the highest severity level !pwards in thenetwork display hierarchy*

/isplay alarm s!mmary co!nt /isplay c!rrent alarms

Alarms acking$ !nacking and commenting

A!dible notifications !pon severity level increase*

/isplay historical alarms3 specify advanced filters4,!eries*

C!stomi%e alarms for selected -. types 1alarm te"t$ severity

and blocking2 for a selection of -.s thro!gh alarm templates*

5


6/23


Alarms Severities 4 Colors

-o alarms or warnings havebeen reported from the

network element*

-ormal Condition

+ray

Priority 5 in the list ofseverities

6


7/23Proprietary and Confidential


A notice from the -.$ whichis not connected to any

error sit!ation$ e*g* a

confirmation*

#nformation

White

Priority 6 in the list ofseverities

Example: “User logged in”

7


8/23Proprietary and Confidential


The network manager cannot determine the severity of an alarm*

#ndeterminate Condition

Pink

Priority 7 in the list of severities

When no contact has been made with the network element$ -et&aster cannot

determine the correct stat!s of the alarms on the -.$ as alarms are c!rrently no

longer being received*

Possible ca!ses8- Comm!nication Ports- &anagements cables4connections- S94Control !nit- )ink down$ etc*

."ample alarm8 )ost Contact


9/23



#ndicates the detection of a

potential or impending fa!lt

that will affect the service$

before any significant effectshave been felt* Action sho!ld be

taken to f!rther diagnose and

correct the problem in order to

prevent it from becoming a more

serio!s fa!lt that will affect the

service*

Warning Condition

:ellow

Priority ; in the list of

severities

!


10/23



#ndicates the e"istence of acondition not affecting the

service$ b!t that re,!ires

corrective action in order to

prevent a more serio!s

fa!lt*

&inor Alarm

(rown

Priority < in the list of

severities

1"


11/23



#ndicates that a conditionaffecting the service has

occ!rred and !rgent

corrective

action is re,!ired*

&a0or Alarm

=range

Priority > in the list of

severities

11


12/23



The most severe alarm* #tsignifies that a condition

affecting the service has

occ!rred and immediate

corrective action is

re,!ired*

Critical Alarm

?ed

Priority @ in the list of

severities

12


13/23



#ndicates that no contacthas been made with the

network element* The

comm!nication settings

sho!ld be checked in order

to obtain contact with the

element*

)oss of Connectivity

(l!e

Priority in the list of

severities

13


14/23


Alarm states

Active8 When a clearable alarm is raised for the -.*

Acked 8 When a clearable alarm is being followed !p* #tBs possible toadd a comment to the alarm*

New 8 A clearable alarm which is c!rrently active and has not beenacked is called a new alarm*

Cleared 8 When the fa!lt condition disappears from the -. thealarm becomes cleared and the -. sends a clear signal to-et&aster* The alarm then go to Distorical Alarm list in thedatabase*

14


15/23


Alarm states* Eiew e"amples

15


16/23


Alarm states* Eiew e"amples

16


17/23


Alarm stat!s

Alarm State Severity '/irectly in +9#

Alarm S!mmary

Alarm Co!nt

/etailed Alarm )ist

Distorical Alarms

17


18/23


Alarm information on topological ob0ects

1


19/23


Alarm indication in map view

< &a0or alarms

G less severe alarmscoming !p*

1!


20/23


Alarm indication in map view

< &a0or alarms acknowledged

#ndicated by o!tline colo!r

< &a0or alarms

acknowledged

minor alarm not acknowledged

G other less severe alarms

2"


21/23


?eport +enerator

+9#

Eiewer P/F File$

&s=ffice

doc!ment

21


22/23


-etwork Time Synchroni%ation

.nablingsynchroni%ation from

system preferences

• Selecting -.s to be

synchroni%ed

22


23/23

#$ank %u

Ch.03 Fault Management

Documents

Transcript of Ch.03 Fault Management