40147180 04 Alarm Monitoring

7/28/2019 40147180 04 Alarm Monitoring

1/21

1 NOKIA CT6042en version 1/ 08.07.2002 / PMa

Alarm Monitoring


2/21


Objectives

After completing this module, the participant should be able to:

Explain how to identify alarm situations within the network and howto outline the procedures used to handle new active alarms. Inaddition, explain how to interpret alarm information in order toclassify the alarm severity.

Explain how to analyse alarm information in order to identify the

affected element and also outline the techniques and commandsused to conclude the possible effect on the network service.

Based upon the knowledge gained about the affected element andusing alarm history information with basic system commands, outlinehow it is possible to conclude the possible reason for the alarm and

identify procedures to handle alarms. Explain a follow-up procedure used to determine that an alarm

situation is closed and that the fault has not re-occurred. In addition,outline any reporting procedures that maybe necessary (based uponthe operator's model or the remedy trouble ticketing system).


3/21


Detecting faults in the network can beseen from different points of view

Alarm flowTraffic & Signalling

MSCHLR

NetAct

RNC

MGW

BS

CustomerComplaints

AlarmsTestResultReports

Data fromother systems


4/21


monitoring

External system

E.g. TransmissionIP network

Global Network MonitorCentralised alarm database

Allocate work toregional office

Field engineersRegional people

Downtownsouth

Maintenance regions

DowntownNorth

SMSCSCPSMS

NetActRegionalNetworkMonitor

Nomansville

Filter


5/215 NOKIA CT6042en version 1/ 08.07.2002 / PMa

Life cycle of an alarm in the NetAct

Active

alarm

Activealarm

Cancelledalarm

Cancelledalarm

Cancelledalarm

Normal situation

Alarm triggers

Acknowledged

Problem is fixed

Alarm is cancelled

by network element

Alarm is cancelled

by network element

Alarm activates again

in network element

Acknowledged



Alarm States and Data Inconsistencies

Active Alarm

In Network Element

Active Alarm in NMS or NetAct

(Unacknowledged)

Cancel Alarm in NMS

(Not acknowledged)

Cancel events are NOT sent to the Network Element from the NMS

Active Alarm

In Network Element

Alarm Cancelled

in Network Element

Cancel event to NMS or NetAct

Alarm Cancelled

Acknowledged

Fault resolved

Most alarms automatically cancel at the network element

NMS

NetAct

DX200

IPA2800 DCN

Resolve the Fault

Alarm event to NMS or NetAct

Acknowledge Alarm in NMS

(Unacknowledged)



Handling alarmingsituations in the network

Unable tosolve intime limit

Network cancels alarm once fault is fixed

CanNOC fix the

fault?

Take correctiveaction

Locatethe fault

Identifythe fault

Alarm

Situation

escalated

/ assigned

no

yes

Fault fixed

Assess theeffect on service

Classify

the fault

Follow up and close the fault



Using the NetAct tools to monitor thenetwork

Location of fault? Impact on service? Classification of fault? Corrective course of action?

Object changes

colour in top level

user interface

Drop the object into

the alarm history to

see condition and

acknowledge

Alarm appears in the

monitor. Double-click

to see more information

and acknowledge

or

More information

in manual page


9/21


Broken link between the BTS/WBTSand BSC/RNC (as seen from the NetAct)

When the connection between a BTS and BSCis broken, the BSC generates alarmsindicating a broken PCM connection.

When a sector is unable to carry any

traffic or signalling, then alarm 7767is always generated.

Use the alarm manual togain more reasons for thecause of the alarm.

The most critical alarms


10/21


Using Traffica to monitor the network

Alarmwindow

MSCTraffica

Alarm appears in the monitor.Double click to see alarmdescription and cancel the alarm.

Wh li k i l t l l


11/21


When a link is lost, several alarms aregenerated from different elements

Al l ifi ti i th N ki


12/21


Alarm classification in the Nokianetwork

Type of alarm Colour in NetAct Severity of alarm

*** Red Critical: There is a fault that will effectthe service.

** Orange Major: There is a potential situationthat

may result in a fault that will

effect the service.

* Yellow Minor: There is either a smallproblem in

the network, or an indication ofan

abnormalsituation.

Warning None The network will generate a messagewhenever something happens.

Cl if i f lt l ti b d


13/21


Classifying fault location based onelement and location

Shopping Area

Rural Area

RNC

OSS


14/21


Identifying the effect on service

Site

Site

Site

Packet Data ServicesVoice Services

BSC / RNC

SGSN / 3G-SGS

Site

BTS

WBTSSiteBTS WBTS


15/21


The state of radio network objectsand effect on service

2G: MSC / SGSN

3G: 3G-MSC / 3G-SGSN

BSC

RNC WBTS

BTS

CNCN RANRAN BSBS

MMLZEEI

NEMUObject

Browser


16/21


The state of signalling linksand effect on service

2G: MSC

3G: 3G-MSC

BSC

RNC WBTS

BTS

CNCN RANRAN BSBS

ZNEL

ZNEL


17/21


The state of PCN signallingand effect on service

2G: SGSN

3G: 3G- SGSN

BSC

RNC WBTS

BTS

CNCN RANRAN BSBS

MMLZFWO

WebBrowser

2G: SGSN

3G: 3G- SGSN

BSC

RNC WBTS

BTS

CNCN RANRAN BSBSCNCN RANRAN BSBS

MMLZFWO

WebBrowser

MMLZFWO

WebBrowserVoyager


18/21


The state of PCN signallingbetween SGSN and HLR

2G- SGSN/MSC

3G- SGSN

BSC

RNC WBTS

BTS

CNCN RANRAN BSBSHLRHLR

MMLZNET

WebBrowser

2G- SGSN/MSC

3G- SGSN

BSC

RNC WBTS

BTS

CNCN RANRAN BSBSHLRHLR

MMLZNET

WebBrowser


19/21


Example of fault prioritisation

Severity of problem Impact on service Responsetime scale

High priority Major loss of service ASAP

Medium priority Service-affecting problem 1

hour

Low priority Non-service affecting problemWorkinghours


20/21


Scope of problem

Does it effect different parts of the system, other than theelement in question? (e.g. BTS transmission problems)

Depth of problem

The technical ability needed to fix the problem

(that is, a system expert is needed)

Time needed

Does the monitoring personnel have the time to find and fix

the problem?

Scope of authority

Is the monitoring personnel allowed to make any changes orfixes

Determining a course of action

E l ti


21/21


Escalationprocess

Create logor ticket

Is thesituationcritical

Alarmescalated

Contactengineer

2nd line orspecialist

Create logor ticket

Recoveryprocedures

Contact on-call engineer

Is itnormalhours

yesno

yes

no

Fault located

and effect on

service identified

Documents

40147180 04 Alarm Monitoring