Nokia - Alarm Monitoring

1 NOKIA CT6042en version 1/ 08.07.
2002 / PMa
Alarm Monitoring Alarm Monitoring
2 NOKIA CT6042en version 1/ 08.07.2002 / PMa
Objectives
After completing this module, the participant should be able to:
Explain how to identify alarm situations within the network and how
to outline the procedures used to handle new active alarms. In
addition, explain how to interpret alarm information in order to
classify the alarm severity.
Explain how to analyse alarm information in order to identify the
affected element and also outline the techniques and commands
used to conclude the possible effect on the network service.
Based upon the knowledge gained about the affected element and
using alarm history information with basic system commands, outline
how 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 upon
the operator's model or the remedy trouble ticketing system).
Detecting faults in the network can be
seen from different points of view
Alarm flow
Traffic & Signalling
MSC
HLR
NetAct
RNC
MGW
BS
Customer
Complaints
Alarms
Test
Result
Reports
Data from
other systems
Organisation of a network used in
monitoring
External system
E.g. Transmission
IP network
Global Network Monitor
Centralised alarm database
Allocate work to
regional office
Field engineers
Regional people
Downtown
south
Maintenance regions
Downtown
North
SMSC
SCP
SMS
NetAct
Regional
Network
Monitor
Nomansville
Filter
Life cycle of an alarm in the NetAct
Active
alarm
Active
alarm
Cancelled
alarm
Cancelled
alarm
Cancelled
alarm
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 DCN
Resolve the Fault
Alarm event to NMS or NetAct
Acknowledge Alarm in NMS
(Unacknowledged)
Handling alarming
situations in the network
Unable to
solve in
time limit
Network cancels alarm once fault is fixed
Can
NOC fix the
fault?
Take corrective
action
Locate
the fault
Identify
the fault
Alarm
Situation
escalated
/ assigned
no
yes
Fault fixed
Assess the
effect on service
Classify
the fault
Follow up and close the fault
Using the NetAct tools to monitor the
network
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
Broken link between the BTS/WBTS
and BSC/RNC (as seen from the NetAct)

W en t e connection et een a T an C
is roken, t e C enerates alar s
in icatin a roken PCM connection.
W en a sector is na le to carr an
traffic or si nallin , t en alar 7767
is al a s enerate .
Use t e alar an al to
ain ore reasons for t e
ca se of t e alar .
T e ost critical alar s

Using Traffica to monitor the network

larm
win ow

Traffica
Alar a ears in t e onitor.
o le click to see alar
escri tion an cancel t e alar .

When a link is lost, several alarms are
generated from different elements
BSC/RNC
CN
HLR
BTS/ BTS
Alarms
Alarm classification in the Nokia
network
Type of alarm Colour in NetAct Type of alarm Colour in NetAct Severity of alarm Severity of alarm
*** Red Critical: There is a fault that will effect
the service.
** Orange Major: There is a potential situation
that
may result in a fault that will
effect the service.
* Yellow Minor: There is either a small
problem in
the network, or an indication of
an
abnormal situation.
Warning None The network will generate a message
whenever something happens.
Classifying fault location based on
element and location

siness Area
o in Area
ral Area
NC
O

Identifying the effect on service

Site
Site
Site
Packet ata ervices
Voice ervices
C / NC
M C / 3G M C
G N / 3G- G N
Site
T
W T
Site
T W T

The state of radio network objects
and effect on service
2G: M C / G N
3G: 3G-M C / 3G- G N
C
NC
W T
T
CN
CN
AN
AN
MM
Z I
N MU
O ect
ro ser
The state of signalling links
2 : MSC
3G: 3G-MSC
BSC
RNC
BTS
BTS
CN
CN
RAN
RAN
BS
BS
NEL
NEL
The state of PCN signalling
2G: SGSN
3G: 3G-SGSN
BSC
RNC
BTS
BTS
CN
CN
RAN
RAN
BS
BS
MML
F O
eb
Browser
2G: SGSN
3G: 3G-SGSN
BSC
RNC
BTS
BTS
CN
CN
RAN
RAN
BS
BS
CN
CN
RAN
RAN
BS
BS
MML
F O
eb
Browser
MML
F O
eb
Browser
oyager
The state of PCN signalling
between SGSN and HLR
2G-SGSN/
MSC
3G-SGSN
BSC
RNC
BTS
BTS
CN
CN
RAN
RAN
BS
BS
HLR
HLR
MML
NET
eb
Browser
2G-SGSN/
MSC
3G-SGSN
BSC
RNC
BTS
BTS
CN
CN
RAN
RAN
BS
BS
HLR
HLR
MML
NET
eb
Browser
Example of fault prioritisation
Severity of problem Severity of problem Impact on service Impact on service Response Response
time scale time scale
High priority Major loss of service ASAP
Medium priority Service-affecting problem 1
hour
Low priority Non-service affecting problem
orking
hours
Scope of problem
Does it effect different parts of the system, other than the
element 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 or
fixes
Determining a course of action
Escalation
process
Create log
or ticket
Is the
situation
critical
Alarm
escalated
Contact
engineer
2nd line or
specialist
Create log
or ticket
Recovery
procedures
Contact on-
call engineer
Is it
normal
hours
yes no
yes
no
Fault located
and effect on
service identified

Nokia - Alarm Monitoring

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nokia - Alarm Monitoring

Uploaded by

Copyright:

Available Formats

1 NOKIA CT6042en version 1/ 08.07.

You might also like