You are on page 1of 19

2011 Tieto Corporation

Fault
Management

in OMS

Agenda

Fault Management in OMS


FM diagram
OMSFM related components
Keyword alarm
FM logs, pronto hints.

Questions

2011 Tieto Corporation

2011-05-11

Fault Management in OMS


Split across two functional domains:
FM server team responsible for:
Managing/supervising alarm flow (mainly between controller & OMS
and internally between OMS & Flexi Alarm System)
Managing alarms configurations: parameters, blockings, preventions,
operating instructions and much more
Exporting alarm parameters and manuals from RISE
DR: adrian.swiatkowski@tieto.com

GUI domain:
Responsible for FM GUI, WebUI
(but of course problem there might be a result of server error).
DR: piotr.kiriakou@tieto.com
3

2011 Tieto Corporation

2011-02-03

How we are working


Mainly with simulators (BTSSim, NetActStub)
As a result some problems will likely appear during the
integration with real NE

2011 Tieto Corporation

2011-02-03

Alarm
Announcement that is given to the management
system about failure abnormal functioning of the
system or about a failure, or an indication of the
degradiation of the service level or reliability.

2011 Tieto Corporation

2011-02-03

NetAct

Apllication Launcher

Alarm Monitor

WEBUI
Topology Tree View

Fault Management GUI

NWI3

EMI

OMS
FlexiPlatform

SS_OMSFM

NWI3Adapter
FMAdapter

FMUIGate

FS AlarmSystem

AlarmDB

SZCZECIN
(EXT-WRANOMS)
BTSOM

NE

2011 Tieto Corporation

2011-05-11

Alarm origin
Raised on NE
Raised on flexi on NE (mcRNC, ADA3)
Raised by OMS components
Raised by Flexi on OMS
Raised by NetAct

2011 Tieto Corporation

2011-02-03

FMAdapter
System

FMAdapter
Communication
with NE (alarm
events, upload)
Alarms validation
Converting
alarms and
storing them to
database via Flexi
interfaces
Alarm
synchronization

<<include>>
Connect

Start Switchover Timer Procedure

<<include>>

Delete

Clear active alarms for deleted NE

Start Alarm Upload from FM GUI


NE

<<include>>

Alarm Upload

MessageSendingThread

<<extend>>

Read AckNack

<<extend>>
Receive Message

<<extend>> Read Alarm Observation

Read AlarmStatusReply

2011 Tieto Corporation

2011-05-11

CMaus

FMUIGate

FMUIGate
Bidirection
communication with FM
GUI (WebUI)
Communication with NE
(rtOperations) regarding
alarms related operations
Retrieving data from Flexi
Passing on-demand
upload request to
FMAdapter

Info events

Get all alarms (refresh)

Network element
Alarm printing

Alarm upload

Alarm Outputs

FM GUI

Change alarm parameters

Alarm manual

Indication prevention

Get alarm history

Alarm blocking

Operating instructions

External alarms

2011 Tieto Corporation

2011-02-03

FM GUI

10

2011 Tieto Corporation

2011-02-03

FM part in WebUI
Limited FM functionality
RNCOMS, IHSPA OMS:
Getting active alarms for child
controller objects
Displaying highest severity
Femto OMS:
Getting logs
Its possible that in the future more
operations will be available via
WebUI

11

2011 Tieto Corporation

2011-02-03

AlarmSystem
Under flexi maintenance:
YFSPFMSW_HKI
Contact person: yury.kulikov@nsn.com

Caches alarm requests, processing them from queue


Alarm management tasks
Communicates directly with alarm database

12

2011 Tieto Corporation

2011-02-03

AlarmDB
Under flexi maintenance:
YFSPFMSW_HKI
Contact person: yury.kulikov@nsn.com

Stores alarms & related parameters


Exporting alarm database, as a root:
/opt/MySQL/bin/mysqldump --user=fsalarmadmin --password=`fsgetcred db_alarm fsalarmadmin`
--socket=/var/mnt/local/MySQL_DB_Alarm/mysql.sock asdb > /home/Nemuadmin/alarmDB.sql

13

2011 Tieto Corporation

2011-02-03

NWI3Adapter
Under flexi maintenance:
YFSPFSW_CELTIS
Contact person: naga.vadakoppula@nsn.com

Handles communication to NetAct (especially alarm upload case)

Some moid conversions (especially NE-OMS -> N3MD-OMS conversion)

Collecting NWI3 logs:


Enable NWI3 trace logging
znwi3logging e
Disable NWI3 trace logging
znwi3logging d
Logs are available in /tmp/trace.log
This logging is quite heavy, should be turned off if not needed
14

2011 Tieto Corporation

2011-02-03

Keyword alarm
Not all problems with alarm in the title are connected with
Fault Management domain itself
Alarms are raised / cancelled by most domains
Example: if in general alarm flow is working but some
particular alarm e.g. regarding some process failure is
appearing then probably this is the case for the domain
which is responsible for this process, not for Fault
Management domain

15

2011 Tieto Corporation

2011-05-11

screenshots, video

screenshots, video

Logs

NetAct

Apllication Launcher

Alarm Monitor

WEBUI
Topology Tree View

Fault Management GUI

alarm export
NetAct eaccolmx log
NWI 3Adapter trace

NWI3

alarms export from GUI ,


debug window output

EMI

OMS
FlexiPlatform

SS_OMSFM

NWI3Adapter
FMAdapter

currentdelivery

FMUIGate

FS AlarmSystem

syslog
alarms / master-alarms
F MAdapter_trace.txt*
fmuigateSrv_trace.txt*
zstatus -d -c
(zcollectlogs collects these
logs and much more)

AlarmDB
fmadapter or fmuigate coredumps

database dump

BTSOM

.pcap, O MSBTSO MSrv_trace.txt*

NE

16

2011 Tieto Corporation

2011-02-03

Few roubleshooting hints


It is crucial to know situation at every step on whole alarm
chain (not only where the behavior is abnormal):
e.g. when there is problem with coming alarms to NetAct it is a valuable
information whether these alarms appeared correctly in FM GUI.

It is important to preserve logs consistency. All logs should


be from the same test execution, mixing them will cause a lot
of confusion and dramatically increase investigation time.
It is important to collect all requested logs. Omitting even one
step out of ten may result in a logs being not useful at all.

17

2011 Tieto Corporation

2011-02-03

Questions?

18

2011 Tieto Corporation

2011-02-03

2011 Tieto Corporation

Thank you

Adrian Swiatkowski
Senior Software Engineer,
Tieto,
adrian.swiatkowski@tieto.com