NetAct Monitor Theory With Exercise

1 © 2008 Nokia Siemens Networks. All rights reserved. NetAct Monitor: Overview of Applications and Functionality / GSt / 10/2008

NetAct MonitorOverview of Applications

and Functionality

NSN NetAct OSS5.1OS8212-51A


Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia training material, are the exclusive property of Nokia. Nokia owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments.

Nokia has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia training material. Individuals can use the Nokia training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia.

The Nokia training material cannot be used outside of an agreed Nokia training session for development of groups without the prior written agreement of Nokia.


Objectives

List the suite of Nokia NetAct Fault Management (FM) tools Explain the advantages and disadvantages of the Nokia NetAct

online and offline FM applications Reconfigure the different FM applications Use the different FM tools to efficiently perform a variety of tasks

applicable to their own job roles


Content

NetAct Monitor Functionality NetAct Monitor Basic Software NetAct Monitor Application Software Overview of Global Monitor Common Iub Integration


Contents of OSS5.1 Release

NetAct OSS5.1 release covers the following products of NetAct Regional Cluster

CM3

HWManager

SQM

Administrator

Trace Monitor

ReportingSuites

GlobalMonitor

GlobalReporter

NetAct Global Cluster Other Products

Optimizer (MV)

Planner

Traffica

MQA

SQM

ReportingSuites

NetAct Regional Cluster

Optimizer

OSS5.1 scope

Audit Trail

NetAct OSW

Standalone SQM

Reporter


• Identify Fault• Locate Fault• Impact on Service?• Classify / Prioritize Fault• Corrective Course of Action• Follow up

Object changescolor in Top leveluser interface

Use the Object to select Criteria. Also can use object by drag and drop to application

Alarm appears in themonitor. Double clickto see more information and acknowledge

or

More informationin manual page

Usage of variousNetAct MonitorTools to Handlethe process

Focus of NetAct Monitor Tools


NetAct Monitor Software

Application Software (ASW):

Tools for real-time network monitoring - Modifiable Alarm Manual

Tools for alarm reduction - Maintenance Mode - Alarm Correlation - FM Rule Editor

Tools for troubleshooting the network - Alarm History Handling

Tools for automating network monitoring processes - Alarm Trigger - Alarm Forwarding to E-Mail

Application Software (ASW):

Tools for real-time network monitoring - Modifiable Alarm Manual

Tools for alarm reduction - Maintenance Mode - Alarm Correlation - FM Rule Editor

Tools for troubleshooting the network - Alarm History Handling

Tools for automating network monitoring processes - Alarm Trigger - Alarm Forwarding to E-Mail

Basic Software (BSW):

Tools for collecting and storing alarms - Alarm Data Collection - Alarm Event Data Storing

Tools for real-time network monitoring - Top-level User Interface - Alarm Monitor - Pre-defined Alarm Manual

Basic Software (BSW):

Tools for collecting and storing alarms - Alarm Data Collection - Alarm Event Data Storing

Tools for real-time network monitoring - Top-level User Interface - Alarm Monitor - Pre-defined Alarm Manual


Alarm Monitoring Flow

From Network

Connects to Network Element Directly


Use of Monitoring Tools to Identify Status of Object

** Major Alarm** Major Alarm

Use of mode and Colours in Help can identify Administrative, Alarm or Object State mode.

User can gain a quick overview of the alarm statuses of the network elements, and of the problems in the services provided to the

subscribers. The colours of the symbols for the NEs change in real-time according to the active alarm situation.

Alarms are divided into four different classes according to the severity of the alarm. Each class is presented by using a specific colour in the NE symbol.

When a new alarm arrives, the symbol of the network element in question blinks in the view. This is know as an Unacknowledged Alarm

*** Critical Alarm** Major Alarm

* Minor Alarm


Alarm MonitorPresents the active alarm situation

sorted by alarm severity and time stamps

The user can:• Acknowledge and cancel alarms• Define the monitoring criteria for

network elements, maintenance region, alarm number and object class

• Open several monitors simultaneously

• Print selected alarms from the list• Define updating period of alarms

Full integration with:• Nokia Trouble Ticket system• Modifiable Alarm Manual• Explanation dialog (information on

correlated alarms)


Alarm History Handling

Analysis of faults using default or user-defined queries about alarm history

The user can make a query using• NE or maintenance region

selection• Alarm severity and type• Alarm number and object class• Time periods• Alarm or Ack state

The user can also• Acknowledge and cancel

alarms• Access the Database Statistics

dialog• Open the Modifiable Alarm

Manual application or start an MML session


Modifiable Alarm Manual

• The user can open the Alarm Manual page which is related to the investigated alarm.• The Alarm Manual page provides detailed information on the alarm, for example, explaining the possible reasons for the alarm as well as giving instruction on how to correct the fault.• Users can add their own comments and instructions for alarms, or own pages.

• The Alarm Manual window can be opened in several ways: from Alarm History Handling, Alarm Monitor, and FM Rule Editor applications.


Alarm Database Upload

To ensure a consistent alarm information in NetAct, the NetAct alarm database is uploaded from the network elements alarm databases.

This can be achieved by selecting the Object and Selecting Alarm database Upload


Alarm reduction

Many faults are important but temporary in nature (e.g. under severe weather conditions) - these can be correlated to produce more meaningful alarmsNokia's alarm reduction strategy• The user needs to be informed only of relevant alarms

to locate and diagnose a fault in the most timely manner

• Alarm reduction takes place where it is most sensible, either on network element level or in the NetAct. The NetAct is the place, if there is a need for a network level view in alarm reduction (e.g. from a topological point of view)

• The target: 1 alarm / 1 faultNokia NetAct can help operators to manage alarm flow information with Alarm Filtering and Reclassification and Alarm CorrelationWith the Alarm Statistics in PC application inNokia NetAct the user can estimate the efficiencyof alarm reduction and the need for that

networkregion 1

networkregion 2

Alarm Reduction

• Correlation• Re-

classification• Filtering


Alarm Filtering and ReclassificationThe user can control alarm flow from network to database or alarm handling application by rule sets• Filtering: alarms are filtered from the alarm handling applications or totally omitted from the database• Alarm Reclassification: alarm classes can be changed• Auto-ack: generates an automatic acknowledgement for the alarms covered in the rule• Ack with cancel: generates an automatic acknowledgement for the cancelled alarms• Informing delay: if the alarm is cancelled within the specified informing delay time, it will not be shown in the alarm monitoring applications


Maintenance Mode• User can block unnecessary alarms from a network element (NE) and reduce the number of alarms shown in the monitoring applications.• By default, in maintenance mode, no alarms from the NE are received (configurable). • When returning to the normal mode, the NMS database is synchronised with the NE.• Maintenance mode can be activated for one NE or a NE and its subnetwork.• A workstation alarm is sent for each NE in maintenance mode, which enables separate monitoring of NEs in maintenance mode. • Maintenance Mode is activated and deactivated from Top-level User Interface• NEs in maintenance mode are shown in blue


Report Set for FM

•Most frequent alarms in the network

•Most alarming network elements

•Alarm distribution for a selected network element

•Number of network elements that produced the selected alarm

•Number of occurrences for a selected alarm


Alarm Trigger• Makes it possible to automatically start UNIX

processes on the basis of defined alarms

• Triggering is controlled by rules specified in a configuration file. The rules include:

• Alarm events which trigger the process

• The process to be triggered

• Usage examples:• Automatic recovery (automatic NE resets

triggered by the certain alarms)

• Forwarding low-volume alarm data to the external systems (automatic trouble ticket creation, generating notifications to customer's own systems or system management platforms e.g. IT/Operations)

• Reduces the amount of manual work required in the network monitoring routines

NMS Alarm Pipe

ALARMTRIGGER

AutomaticRecovery

AutomaticTesting

Config.file


Alarm CorrelationThe user can create correlation rules so that only informative alarms are shown in the Alarm Monitor application

Compression: an alarm is shown only once, even if there have been several occurrences of the alarm active at the same time

Suppression: lower priority alarms are not shown when there is an active alarm of higher priority

Count: a new alarm is generated whenever a predefined number of defined alarms have been received within a certain time

+

+


Alarm Forwarding to E-mail

• Quality of network services to subscribers must always be at a high level even if the assigned personnel may not be present at all times• With this feature it is possible to forward alarm information using e-mail• This feature can be used in communication between network monitoring centers and maintenance people • Criteria set defines the alarms which will cause messages to be forwarded• E-mail messages are sent via an electronic mail system (SMTP)


ASCII Alarm Forwarding

• The NetAct-NMC ASCII Alarm Forwarding interface is a solution for sending alarm information from the Nokia NetAct to an NMC in ASCII format using TCP/IP and UNIX services. • The interface is intended to be used with a third-party NMC.• The alarms are routed from the NetAct alarm pipe to the ASCII Alarm Forwarding application, optionally via buffering.• The ASCII Alarm Forwarding application writes the data through the socket connection to the NMC.• The NMC alarm application is responsible for receiving and handling the alarms as required.

NetworkElements

NetAct

Buffer (optional)

ASCII Alarm Forwarding

NMC

NMC alarm application

NMS alarm pipe

TCP/IP address + port


3GPP FM Forwarding

• fault management interface • based on 3GPP TS32.111-x (R4) and relevant references, Corba Solution Set• alarm upload for alarm synchronisation• continuous alarm notifications (newAlarm, AckStateChanged, ClearedAlarm, AlarmList-Rebuild)• alarm acknowledge from external system• configurable filter for notifications set by external system at subscription time• information either based on generic 3GPP object model (RAN and Core area supported in initial version) or on Nokia proprietary object model (Alarms from all NEs supported by NetAct and all NetAct internal alarms transferred)

Itf-NAlarm IRPNotification IRPCorba Solution Set

IRP Manager

NetworkElements

ExternalAlarmTool

Nokia NetAct

Nokia NetAct Monitor

alarm upload

alarm notifications

acknowledgealarms


Global Monitor Regional Monitor

NetworkElements

GlobalMonitor

RegionalMonitor

Same Monitoring Tools on Global and on Regional

Level

Global Monitor, Regional Monitor

and NE´s are hierarchically

linked together… and much more:• Drag & Drop between Global

Monitor and Regional Monitor

• Direct Access to Element Manager

• Automatic Alarm Synchronisation

• Automatic View Updates• Connection Supervision• Same Look and Feel


Common IuB Integration

RNC

NetActRC/OTS

NBxxx

FlexiBTS

RN

C &

Fle

xiB

TS

alar

ms

& s

tatis

tics

NBxxx alarms & statistics

• NetAct consolidates the FM data from NB/RSxxx, RNCs and FlexiBTSs

– NBxxx alarms are collected by Radio Commander and forwarded to NetAct

– NetAct Monitor applications provide a network wide view to the alarms

– RC/OTS and NBxxx LTE can be used as complementary tools, e.g. in troubleshooting

New in OSS5.1 CD1


EXERCISE – Alarm Monitor

1. What is the main idea of the Alarm Monitor?

2. Study the main window of the Alarm Monitor. What do you see?

3. Study the Alarm menu and the buttons (both are correlated). If subpoints are greyed out, select one ore more alarms in the main view.

4. Study the Configuration menu and change some settings.

5. Open the Monitoring Criteria pane by using the correct button.

6. Change some settings inside the Monitoring Criteria and review different output results in the main view.

Use the Notes Page for your results.


OPTIONAL EXERCISE – TLUI and Maintenance Mode 1. Check if the TLUI is working in the alarms mode? Select

the alarms mode if necessary.

2. What is the difference of a blinking object and a blinking shadow of an object?

3. What is the purpose of the feature Maintenance Mode?

4. Set a BCF/WBTS named by the trainer to Maintenance Mode. In which colour are the objects shown afterwards?• Activate for MO• Activate for MO and Subnetwork

5. Deactivate Maintenance Mode for your objects. Check the change of colours.



OPTIONAL EXERCISE – Other NetAct Monitor Tools 1. Open and study the Alarm History

2. Open and study the Modifiable Alarm Manual

3. Perform an Alarm Database Upload

4. Open and study FM Reports (if you do not find them on the NetAct Start Page open them from the TLUI)


NetAct Monitor Theory With Exercise

Documents

Transcript of NetAct Monitor Theory With Exercise