Ce Tmo18261 9353 Wms Ua07 Utran Fault Management

TMO18261 9353 WMS UAO7 UTRAN Fault Management - Page 1All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

9353 WMSTMO18261 9353 WMS UAO7 UTRAN Fault Management

STUDENT GUIDE

TMO18261 Issue D0 SG DEN I1.0

All rights reserved Alcatel-Lucent 2010 Passing on and copying of this document, use and communication of its contents

not permitted without written authorization from Alcatel-Lucent



TMO18261 9353 WMS UAO7 UTRAN Fault Management9353 WMS2

Empty page

Switch to notes view!

This page is left blank intentionally




Terms of Use and Legal Notices

Switch to notes view!1. Safety WarningBoth lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment alone.

The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.

2. Trade MarksAlcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.

All other trademarks, service marks and logos (Marks) are the property of their respective holders, including Alcatel-Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change without notice.

3. CopyrightThis document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.

Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited.

User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express written consent of Alcatel-Lucent.

All rights reserved Alcatel-Lucent 2010

4. DisclaimerIn no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-Lucent has been advised of the possibility of such damages.

Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor a recommendation.

This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely accurate.

Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and its operation, or contact your nearest Alcatel-Lucent representative for more information.

The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-Lucent disclaims any warranties in connection with the products as used and described in the courses or the related documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade practice.

Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature

5. Governing LawThe products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to,the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and LegalNotices shall remain in full force and effect.




Blank Page






Course Outline

About This CourseCourse outlineTechnical supportCourse objectives

1. Topic/Section is Positioned HereXxxXxxXxx

2. Topic/Section is Positioned Here






Section 1. Alarm defintion and Open NSP

Module 1. Alarm definition and Open NSP TMO18261 D0 SG DEN I1.0

Section 2. Modify alarm display

Module 1. modify alarm display TMO18261 D0 SG DEN I1.0

Section 3. Define UTRAN NE and OAM link

Module 1. Define UTRAN NE and OAM link TMO18261 D0 SG DEN I1.0

Section 4. Analyse alarm

Module 1. Analyse alarm TMO18261 D0 SG DEN I1.0

Section 5. Alarm Correction Process

Module 1. Alarm Correction Process TMO18261 D0 SG DEN I1.0

Section 6. Options

Module 1. Options TMO18261 D0 SG DEN I1.0




Course Outline [cont.]






Course Objectives


Welcome to TMO18261 9353 WMS UAO7 UTRAN Fault Management

Upon completion of this course, you should be able to:

Illustrate the Fault Management Architecture Identify the Fault Detection Mechanisms Illustrate the Alarm Processing Flow Describe the Fault Management Use the Alarm On-Line Help Filter Alarms Employ the Access Network Specific Maintenance Tools




Course Objectives [cont.]






About this Student Guide

Switch to notes view!Conventions used in this guide

Where you can get further information

If you want further information you can refer to the following:

Technical Practices for the specific product Technical support page on the Alcatel website: http://www.alcatel-lucent.com

Note Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.

Technical Reference (1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.

WarningAlerts you to instances where non-compliance could result in equipment damage or personal injury.




About this Student Guide [cont.]






Self-assessment of Objectives

At the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training


Instructional objectives Yes (or globally

yes)

No (or globally

no) Comments

1 To be able to XXX

2

Contract number :

Course title :

Client (Company, Center) :

Language : Dates from : to :

Number of trainees : Location :

Surname, First name :

Did you meet the following objectives ?Tick the corresponding box

Please, return this sheet to the trainer at the end of the training




Self-assessment of Objectives [cont.]


Instructional objectives Yes (or Globally

yes)

No (or globally

no) Comments

Thank you for your answers to this questionnaire

Other comments

Section 1 Module 1 Page 1

All Rights Reserved Alcatel-Lucent 2010TMO18261 D0 SG DEN I1.0 Issue 1

Do not delete this graphic elements in here:


Module 1Alarm definition and Open NSP

TMO18261 D0 SG DEN I1.0 Issue 1

Section 1Alarm defintion and Open NSP






9353 WMS TMO18261 9353 WMS UAO7 UTRAN Fault ManagementAlarm defintion and Open NSP Alarm definition and Open NSP1 1 2

Blank Page


First editionLast name, first nameYYYY-MM-DD01

RemarksAuthorDateEdition

Document History





Module Objectives

Upon completion of this module, you should be able to:

Describe List Explain Identify ...





Module Objectives [cont.]






Table of Contents

Switch to notes view! Page

1 Name of Level 1 71.1 Name of Level 2 8

1.1.1 Name of Level 3 91.1.1.1 Name of Level 4 10

No Level 11Text Boxes 13Symbols (mentioned in Front-Matter Part of Course) 14Tables 15Numbered Lists 16Unnumbered List 17Presentation of Animation Settings on Slide Master 18Animation Sequence Complete 19Text and Graphic 20Annotations 21Oversized Screen Snapshots 22(1) Detail 1 23(2) Detail 2 24Notes Page only (Standard Notes Text Field Extended) 25Notes Page only (Active X Word Text Field) 26Main Colors 27Splash Pictures (Samples) 28How to Do It 29Discover 30Answer the Questions 31Exercise 32Summary 33Self-Assessment on the Objectives 34Abbreviations and Acronyms 35Glossary 37References 39End of Module 40





Table of Contents [cont.]







1 Definition of an alarm






1.1 Definition of an alarm

Lets imagine that you are a journalist and you need to retrieve all information about a specific accident from the newspaper database :

Ref 322234: Old car against a train: impact and consequences In France, several years ago, an old car stopped on a rail cross and cannot restart.The driver went outside his car.A train came and hurt this car.The train left the railways.The train hurt a bridge and fell in the river under this bridge.The train carried some chemical elements.These ones went into the ground and then polluted the water for several months for several towns.

How can you characterize this accident ?






1.2 How an alarm is defined in the system

On which type of equipment: Old car, TrainLocation: South of France

When?Time raised: several years ago

How?Type of accident: train hurt carProbable Cause: old car cannot restartConsequence: train destroy old car and bridgeIs there a main problem: from the car.Are they other problem in consequence:

Yes,pollution, bridgeIs there a correlation between the different parts?Yes, different level of severity

Can we split the accident from a source problem withseveral consequences? Yes

Do the rescuer manage completely the accident?yes they acknowledges all details

Can we add some comment, in addition? Yes hazardIs there any trouble ticket send to the emergency doctor ?YesCan we define a reference of this accident? 322234With a title? Old car against a train: impact and

consequences

Active/Acknowledged

Note

Alarm Code

Ne name

Ne Id

Correlation Group Id

Component

Type

Correlation Alarm Type

Probable cause

Severity

Additional text

Time raised

Trouble Ticketing

In NSP ?





Whats an Alarm ?

BTS

Notification

RNC

State / Status Change

MainServer internal decision

Alarm !

Each Manageable entity in the RNC/BTS has in general something like 3 states (administrative state, operational state & usage state) and 6 status (alarm status, upgrade status, )

When one of this states or status change the NE might send SCN (state or status change notification) to the Main server.

The main server using it own internal decision mechanism decide to transform this notification (or thesenotifications) into an alarm (or several alarms). The Mais server decides also about the severity of this alarm(Critical, Major or minor)

AdministratorTypewritten TextITFB

AdministratorTypewritten TextITR

AdministratorTypewritten Text





Alarm life cycle

Administrative state

Operational state

Usage state

unlocked

enabled

active

locked

disabled

idle

Goodstate

Badstate

SET

Clear

When the object state change from good state into bad state, an alarm (or notification) with SET flag israised. In the opposite, when the object goes back to the good state the flag CLR is raised in the notification or the alarm.

The states depend on the object, for example some object support two administrative states only(locked/unlocked) some others can have a third state (shutting down). The same thing for the usage state for example: it can be idle, active or busy.

AdministratorHighlight







2 How to open the NSP






2.1 Modify the hosts file on your PC

On your PC client Under C:\WINNT\system32\drivers\etc directory

Modify the hosts file like this:

IP Addressof the Main Server

Short name of the Main Server

Full name of the Main Server

The Network Services Platform (NSP) is a network management platform that enables you to manage your network from within a single user interface. A basic NSP installation provides standardized fault information about many different types of network elements. One of its key strengths is that additional Preside products, such as Historical Fault Browser, can be integrated into and launched directly from within the NSP interface. Therefore, each NSP installation can be customized to suit your needs.

To install NSP on your PC you need to declare the WMS server\ on your PC, to do that you need to add a line to your hosts file located on:C:\WINNT\system32\drivers\etc the first directory could be WINNT or windows depending on your OS The line should contain the IP address of the WMS server, the hostname and the DNS as mentioned above








2.2 Install the Java version







2.3 Launch NSP







2.4 Main Window

In the main Window, a menu bar provides standardized functional grouping of menus and dialogs based on TMN recommendations. This consistent user environment increases efficiency, driving down operational and training costs.The Resource Browser provides a layered, map-based representation of the network.The Navigator provides an hierarchical view of the network organized in a Windows ExplorerTM style tree, based on NE groups (see "Creating Network Element Groups"). The Navigator also provides a summary count of alarms at each level in the network hierarchy.The Network Banner provides an "always-on" summary of active alarms in the network.This main window also provides Layout administration tools (Layout Editor and Network Definition toolbar), System Administration tools (Application Management, Access Control, Netscape Directory Service (NDS) configuration, and Custom Commands) and a Status bar, Management and System Management Indicators.









2.5 Display alarm with the Alarm Manager

A new field is added to the alarm message: the alarm code.The alarm code identifies uniquely an alarm type within all domains, OAM, RNC, BTS, POC.In order to harmonize the display and simplify the reporting, this field shall have anhomogeneous format across the nodes:__ This new field is displayed in a new column in the alarm browser and the HFB. This field can be used in HFB for statistical reporting.








2.6 Principles

The alarm code shall identify uniquely an alarm type within all domains, OAM, RNC, BTS, MSS. This new field shall be displayed in a new column in the alarm browser and the HFB. This field can be used in HFB for statistical reporting.

A new field is added to the alarm message: the alarm code.The alarm code identifies uniquely an alarm type within all domains, OAM, RNC, BTS, POC.In order to harmonize the display and simplify the reporting, this field shall have anhomogeneous format across the nodes:__ This new field is displayed in a new column in the alarm browser and the HFB. This field can be used in HFB for statistical reporting.





Answer the Questions

Read this notification and answer the questions:

2010/04/08-19:16:35,000-00:00;2010/04/08-19:16:35,000-00:00;ALAR;(RNC.userLabel,RNC1);(RNC.userLabel,RNC1)(RNCEquipment,0)(INode.neId,RNC1_IN);INode;(RNC.userLabel,RNC1);NE;72939;CommunicationAlarm;lossOfSignal;70060003;Major;(PPSubEqt,EM RNC1_IN NMIS$ TELNET $ SESSION 1);'TCP connection from 10.10.10.6 failed. userid = debug role = dataStreams = ala ~deb ~log ~scn ~rts rem oteTcpPort = 62866 screenWidth = 79 loginTime = 2010-04-08 18:54:02.921 idleTime = 22' componentId: EM RNC1_IN NMIS $ TELNET $ SESSION 1 operationalState: enabled administrativeState: unlocked usageStatus: usageActive standbyStatus: standbyEmpty unknownStatus: FALSE ;

What happened exactly?

Do you thing that the Main server generated a alarm due to this notification?









Module Summary

You are now able to:

Define an alarm

Show how to have access to the GUI which allow to display alarm





Discussion or Question





Self-assessment on the Objectives

Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module

The form can be found in the first partof this course documentation





Abbreviations and Acronyms

Switch to notes view!# #1 Full Writing of Term #1 #2 Full Writing of Term #2 A A1 Full Writing of Term A1 A2 Full Writing of Term A2 B B1 Full Writing of Term B1 B2 Full Writing of Term B2 C C1 Full Writing of Term C1 C2 Full Writing of Term C2 D D1 Full Writing of Term D1 D2 Full Writing of Term D2 E E1 Full Writing of Term E1 E2 Full Writing of Term E2 F F1 Full Writing of Term F1 F2 Full Writing of Term F2 G G1 Full Writing of Term G1 G2 Full Writing of Term G2 H H1 Full Writing of Term H1 H2 Full Writing of Term H2 I I1 Full Writing of Term I1 I2 Full Writing of Term I2 J J1 Full Writing of Term J1 J2 Full Writing of Term J2 K K1 Full Writing of Term K1 K2 Full Writing of Term K2 L L1 Full Writing of Term L1 L2 Full Writing of Term L2 M M1 Full Writing of Term M1 M2 Full Writing of Term M2 N N1 Full Writing of Term N1 N2 Full Writing of Term N2

O O1 Full Writing of Term O1 O2 Full Writing of Term O2 P P1 Full Writing of Term P1 P2 Full Writing of Term P2 Q Q1 Full Writing of Term Q1 Q2 Full Writing of Term Q2 R R1 Full Writing of Term R1 R2 Full Writing of Term R2 S S1 Full Writing of Term S1 S2 Full Writing of Term S2 T T1 Full Writing of Term T1 T2 Full Writing of Term T2 U U1 Full Writing of Term U1 U2 Full Writing of Term U2 V V1 Full Writing of Term V1 V2 Full Writing of Term V2 W W1 Full Writing of Term W1 W2 Full Writing of Term W2 X X1 Full Writing of Term X1 X2 Full Writing of Term X2 Y Y1 Full Writing of Term Y1 Y2 Full Writing of Term Y2 Z Z1 Full Writing of Term Z1 Z2 Full Writing of Term Z2





Abbreviations and Acronyms [cont.]






Glossary

Switch to notes view!# #1 Explanation of Term #1 #2 Explanation of Term #2 A A1 Explanation of Term A1 A2 Explanation of Term A2 B B1 Explanation of Term B1 B2 Explanation of Term B2 C C1 Explanation of Term C1 C2 Explanation of Term C2 D D1 Explanation of Term D1 D2 Explanation of Term D2 E E1 Explanation of Term E1 E2 Explanation of Term E2 F F1 Explanation of Term F1 F2 Explanation of Term F2 G G1 Explanation of Term G1 G2 Explanation of Term G2 H H1 Explanation of Term H1 H2 Explanation of Term H2 I I1 Explanation of Term I1 I2 Explanation of Term I2 J J1 Explanation of Term J1 J2 Explanation of Term J2 K K1 Explanation of Term K1 K2 Explanation of Term K2 L L1 Explanation of Term L1 L2 Explanation of Term L2 M M1 Explanation of Term M1 M2 Explanation of Term M2





Glossary [cont.]

Switch to notes view!N N1 Explanation of Term N1 N2 Explanation of Term N2 O O1 Explanation of Term O1 O2 Explanation of Term O2 P P1 Explanation of Term P1 P2 Explanation of Term P2 Q Q1 Explanation of Term Q1 Q2 Explanation of Term Q2 R R1 Explanation of Term R1 R2 Explanation of Term R2 S S1 Explanation of Term S1 S2 Explanation of Term S2 T T1 Explanation of Term T1 T2 Explanation of Term T2 U U1 Explanation of Term U1 U2 Explanation of Term U2 V V1 Explanation of Term V1 V2 Explanation of Term V2 W W1 Explanation of Term W1 W2 Explanation of Term W2 X X1 Explanation of Term X1 X2 Explanation of Term X2 Y Y1 Explanation of Term Y1 Y2 Explanation of Term Y2 Z Z1 Explanation of Term Z1 Z2 Explanation of Term Z2





References





End of ModuleAlarm definition and Open NSP



Do not delete this graphic elements in here:


Module 1modify alarm display

TMO18261 D0 SG DEN I1.0 Issue 1

Section 2Modify alarm display






9353 WMS TMO18261 9353 WMS UAO7 UTRAN Fault ManagementModify alarm display modify alarm display2 1 2

Blank Page


First editionLast name, first nameYYYY-MM-DD01

RemarksAuthorDateEdition

Document History





Module Objectives

Upon completion of this module, you should be able to:

Describe List Explain Identify ...





Module Objectives [cont.]






Table of Contents

Switch to notes view! Page

1 Name of Level 1 71.1 Name of Level 2 8

1.1.1 Name of Level 3 91.1.1.1 Name of Level 4 10

No Level 11Text Boxes 13Symbols (mentioned in Front-Matter Part of Course) 14Tables 15Numbered Lists 16Unnumbered List 17Presentation of Animation Settings on Slide Master 18Animation Sequence Complete 19Text and Graphic 20Annotations 21Oversized Screen Snapshots 22(1) Detail 1 23(2) Detail 2 24Notes Page only (Standard Notes Text Field Extended) 25Notes Page only (Active X Word Text Field) 26Main Colors 27Splash Pictures (Samples) 28How to Do It 29Discover 30Answer the Questions 31Exercise 32Summary 33Self-Assessment on the Objectives 34Abbreviations and Acronyms 35Glossary 37References 39End of Module 40





Table of Contents [cont.]







3 Modify the alarm stream on the NSP





Events


3.1 Fault Detection Mechanisms

Hardwarefault

NSP GUI

PC Client

Notifications

StateChange Warning

Softwareanomaly

Alarms

RNS 1RNC BTS BTS BTS

.

Interventionrequired

Main Server

Faultdetection

(supervision)

The Alarmstream can be

modified

Everything that happens during the lifecycle of the NEs is called event. Event reports are sent by all pieces of equipment to the OAM platform in order to constantly inform the system about the state of the whole network.

The fault management function manages the unsolicited messages coming from the NEs. These messages are as follows:

software anomaly: software anomaly messages inform users of anomalies detected in applications associated with UTRAN processing chains.

hardware fault: hardware fault messages inform users of equipment failures and malfunctions. Warning: warning messages inform users of operating changes, such as short-lived faults and

inconsistencies detected on managed objects.

State changes usually generate notifications which are stored in the log file for investigation purposes, later on. However, some state changes may lead to alarms when specific events require intervention of the OAM staff members.

For instance, the state change to Disabled Dependency is sufficient to generate an alarm. Besides, some logical objects (FDDCell, ControlPort, neighbouringRnc, ) may also generate OsiState alarms.

Starting from V3.1, the state changes are treated as functional faults (loss of service) and processed as beginning or end of alarms (QoS).

The OAM link state generates a critical alarm when the link is lost, and only a warning if the link is locked.





Alarm Panel


3.2 Alarm Stream Management (On/Off)

OriginalAlarm Stream(from the NEs) Alarm Stream

Management

ON ActiveRule Set GUI

Alarm Banner Display

Overview

You can manage the alarm stream sent from the server to reduce the number of alarms displayed in the GUI clients, or perform other actions on alarms; for example, delay alarms, or change alarm severity.

Rules

To implement alarm stream management, you define alarm rules. A rule or multiple rules can then be applied to the managed alarm stream.

Once you apply a rule and enable alarm stream management, you can reduce, delay, or modify the severity of incoming alarms in the current Alarm Manager window, and any subsequent Alarm Manager windows that you launch.

Benefits

This mechanism has been developed to limit the number of alarms that are displayed in the GUI clients. Reducing the number of alarms displayed helps to focus alarm monitoring tasks and improves the

performance of the GUI clients.






3.3 Alarm Stream Rule Set Access

The Advanced Filters window allows you to apply a configurable alarm filter. Applying a filter reduces the number of alarms displayed in the Alarm List.

If you want to use an advanced filter, you must apply the filter each time you log in and each time you open a new layout. You can use an advanced filter in combination with the filtering options available in the Alarm List options panel.

Alarms can be filtered by criteria such as NE Name, alarm severity, alarm type (as per ITU recommendations), alarm name, time of occurrence (local time zones are supported).

The Advanced Filter Settings panel allows you to define advanced filter attributes and to Apply advanced filters

Define advanced filter attributes: the Advanced Filter Settings panel contains three tabs that display the properties for a filter (Alarm specific, NE specific, problem specific). If a filter is currently selected in the Retrieve Saved Filters panel, the properties for that filter are displayed.

Apply advanced filters: When you apply an advanced filter to the alarm display for the current layout, the filter name displays in the Advance Filtering text field.

With the support of the negative criteria in the Alarm Manager Advanced Filtering, the operator is able to filter alarm information using negation criteria, for instance NE name "does not contain" instead of only "contain".






3.4 Alarm Stream Rule Set

The Advanced Filters window allows you to apply a configurable alarm filter. Applying a filter reduces the number of alarms displayed in the Alarm List.

If you want to use an advanced filter, you must apply the filter each time you log in and each time you open a new layout. You can use an advanced filter in combination with the filtering options available in the Alarm List options panel.

Alarms can be filtered by criteria such as NE Name, alarm severity, alarm type (as per ITU recommendations), alarm name, time of occurrence (local time zones are supported).

The Advanced Filter Settings panel allows you to define advanced filter attributes and to Apply advanced filters

Define advanced filter attributes: the Advanced Filter Settings panel contains three tabs that display the properties for a filter (Alarm specific, NE specific, problem specific). If a filter is currently selected in the Retrieve Saved Filters panel, the properties for that filter are displayed.

Apply advanced filters: When you apply an advanced filter to the alarm display for the current layout, the filter name displays in the Advance Filtering text field.

With the support of the negative criteria in the Alarm Manager Advanced Filtering, the operator is able to filter alarm information using negation criteria, for instance NE name "does not contain" instead of only "contain".






3.4 Alarm Stream Management [cont.] Inhibit

Rule Definition

Action Type

GUI

Alarm Stream

Alarm Stream modified

Other Alarms

ON TIME

INHIBIT

Action on Alarms

The parameters of the Rule Definition window must be specified first. To take this mechanism into account, the Alarm Stream Management window must be turn ON.

These parameters describe the type of action that can be undertaken in front of the alarms raised at NSP level: Inhibit: removes the alarms from the managed stream. If multiple actions are defined, only the

inhibit action will be applied. Delay: postpones the display of alarms that match the rule criteria for a specified period of time. Modify severity: replaces the default value with a value selected in the Action area. A drop-down box

gives the list of possible severity values. Manage as toggling: creates a specific alarm. For instance, you specify rule conditions to create a

toggling alarm when 5 alarms matching the criteria are raised (and cleared) for the same NE within 30 minutes.

Manage as threshold: creates a specific alarm so that one single alarm is displayed instead of multiple alarms. This new alarm prevents a flood of alarms from being displayed in the Alarm Manager.

Launch application: defines a rule to launch an application once the condition has been met. A drop-down box gives the details of the parameters to be filled.

Acknowledge, Send email & Send SMS are described further in this chapter.






3.4 Alarm Stream Management [cont.] delay

Rule Definition

Action Type

GUI

Alarm Stream


Other Alarms

ON TIME

WITH A DELAY

Action on Alarms














3.4 Alarm Stream Management [cont.] Modify Severity

Rule Definition

Action Type

GUI

Alarm Stream


Other Alarms

ON TIME

Severity modified

Action on Alarms














3.4 Alarm Stream Management [cont.] Automatic Acknowledged Alarms

Rule Definition

Action Type

GUI

Alarm Stream


Other Alarms

ON TIME

AlarmsAuto-

acknowledged

The Alarm Stream Management allows the user to create a new rule, remove or update existing rules, and specify whether a rule is applied to the received alarms, that is, set the rule as activated or inactivated.

From the alarm stream rule set menu, the user can configure the Acknowledge action.

This feature allows the operator to automatically acknowledge some alarms based on the alarm type.

This feature dramatically helps the operator supervise his network by auto-acknowledging some alarms according to their type.

This way, the operator can reduce the volume of alarms to handle and treat as some of them will have been automatically acknowledged.

The operator gains in terms of operational savings.






3.4 Alarm Stream Management [cont.] Manage as Toggling

Rule Definition

Action Type

GUI

Alarm Stream

Alarm managed as Toggling

Other Alarms

ON TIME

Action on Alarms














3.4 Alarm Stream Management [cont.] Manage as Thresthold

Rule Definition

Action Type

GUI

Alarm Stream

Alarm managed as threshold

Other Alarms

ON TIME

Action on Alarms













From: [email protected]: wednesday 13 october 2005 15:29To: [email protected]; [email protected]: Alarm:Rule Name = alarm send mail demoRule Name = alarm send mail demoNode Name = UTRAN-002Node Id = EM UTRAN-002Node Address = 47.153.176.119Managed Object Class = 1003Managed Object Instance = (, 1030 = NW UTRAN, 1028 = EM UTRAN-002) Notification Id = 104203246 Event Time = 20041013210159ZSpecific Problem = 123 Equipment Type =Unknown Status = falseProbable Cause = alarmIndicationSignalAdditional Text = This machine is crashed.Severity = CriticalAlarmed Component = ()Vendor Specific Info = (, alarmSupportAging = true,alarmSupportManualClear = true, faultCode = 7654, helpVolume=, NE_TYPE = 214)


3.4 Alarm Stream Management [cont.] Send an email

Rule Definition

Action Type

GUI

Alarm Stream

Send an email

Alarm stream

ON TIME

Action on Alarms














3.4 Alarm Stream Management [cont.] send a SMS

Rule Definition

Action Type

GUI

Alarm Stream

Alarm stream

ON TIME

Send a SMS

Action on Alarms













4 View the alarms with the Alarm Manager





4 View the alarm with the alarm manager

4.1 Show alarm from Resource Browser (Network Level)

NSP provides a graphical indication of which alarms are acknowledged via the alarm balloon icon displayed at the left-hand side of each alarm in the alarm list.

Alarms that are not acknowledged have a solid color alarm balloon, in the appropriate color for the alarm severity, and icons for acknowledged alarms are displayed without the balloon.

Some NEs can generate alarms without generating alarm clear notifications. In such cases, the user can manually clear these alarms using the same mechanism described above for alarm acknowledgement.

Manually clearing an alarm removes the immediate alarm notification associated with the selected network element. This option is only available for those alarms that require manual alarm clears, preventing users from clearing other valid, active alarms.

The system administrator uses the Access Control tool to assign permission to manually clear an alarm.

Details about a specific alarm can be displayed by selecting the alarm in the Alarm Manager. These details are displayed directly below the alarm list. Details include NE name, Alarm ID, Alarm Type, Unit, Probable Cause, Equipment Type, Common Language Facility Identifier (CLFI), Reason, as well as acknowledgement information.






4.2 Show alarm from Network Element (Pop-up menus)

POC (pp7k)

BTS

RNC

NSP provides a graphical indication of which alarms are acknowledged via the alarm balloon icon displayed at the left-hand side of each alarm in the alarm list.

Alarms that are not acknowledged have a solid color alarm balloon, in the appropriate color for the alarm severity, and icons for acknowledged alarms are displayed without the balloon.

Some NEs can generate alarms without generating alarm clear notifications. In such cases, the user can manually clear these alarms using the same mechanism described above for alarm acknowledgement.

Manually clearing an alarm removes the immediate alarm notification associated with the selected network element. This option is only available for those alarms that require manual alarm clears, preventing users from clearing other valid, active alarms.

The system administrator uses the Access Control tool to assign permission to manually clear an alarm.

Details about a specific alarm can be displayed by selecting the alarm in the Alarm Manager. These details are displayed directly below the alarm list. Details include NE name, Alarm ID, Alarm Type, Unit, Probable Cause, Equipment Type, Common Language Facility Identifier (CLFI), Reason, as well as acknowledgement information.






4.3 Show alarm from Navigator

The Navigator can be defined as a list-based display of NE groups, in a network tree hierarchy.

It also gives the corresponding alarm summary information. All these parts of information are associated with one specific user-created layout.

The Navigator allows the user to access his network at 3 levels, from top to bottom: Layout, Group, NEs.

NE Store

The NE Store is a system group for the NEs that have not yet been placed in a group.Find

The Find utility is a search utility for managed network resources. It is particularly useful for editing layouts, because you use Find to add network elements to groups.

In the NSP window, select Find in the File menu to start the Find utility.






4.4 Show alarm from Equipment Monitor




NE Store









4.5 Show alarm from boards




NE Store








WarningCritical

MajorMinor


4.6 Show summarize of alarms from Network Banner

Alarms encountered

Last action performed

Total Number of NEs in the Layout/Total Number of NEs in the Network

Active Critical Alarms reported by SMC

Alarm Stream Management (On / off)

Leads to Alarm Manager window

Loss of communication

The Network Banner is the highest-level alert window. The status bar (lowest part of NSP window) and the network banner provide the same information to the OA&M staff members.

The Network Banner sends visual signals to alert the user whenever potential problems occur in the system. These aids include a summarization of alarm count and an alarm count for each of the different alarm severities:

Critical, Major, Minor, Warning.

This summary allows users to track network and sub-network status changes.

Note

The Network Banner remains displayed when the Network Services Platform window is minimized. Use it when you need to minimize NSP window and do other work while keeping an eye on the alarm states.






4.7 Alarm Manager Overview

Pushbutton Alarm Details Additional text Note

Users can investigate alarms and decide to:

Reduce the number of alarms displayed in the alarm manager

Acknowledge or unacknowledge individual or multiple alarms

Manually clear individual or multiple alarms when appropriate

Users can investigate alarms and decide to:

Reduce the number of alarms displayed in the alarm manager

Acknowledge or unacknowledge individual or multiple alarms

Manually clear individual or multiple alarms when appropriate

Basically, the Alarm Manager is the main decision assistant enabling the support engineer to decide how to react in front of the various situations.

All parts of the UMTS network share a common Fault Management System. All alarms are stored in a single database and reported to the user thanks to NSP.

The NSP GUI identifies a Network Element in an alarm state by adding a balloon to the NE icon, as well as changing the icons color. The operator has the ability to:

remove alarms from the Preside system remove reporting of symptomatic alarms from the Preside system delay reporting of alarms control reporting of Toggling alarm conditions in the network The operator can open the Alarm Manager window to display a more detailed view of the faults that

are reported. More precisely, the operator can open up to 5 Alarm Manager simultaneous windows during his NSP session.

The Alarm Manager brings up a listing of all the alarms that are associated with the Network Elements. In the following pages, we are going to deeply discuss the facilities of the Alarm Manager tool.






4.8 Sorting Alarms

Selecting the appropriatecolumn heading

Display Criteria

Select a column as the key for sorting the Alarm List by clicking on a column heading. Double-clicking the appropriate column heading displays the alarm list of alarms according to the selected criteria. Type & Severity are the usual ways to organize the list of alarms.

Selecting Type will show the alarms in the following order: Communications

environmental

Equipment

processing

quality of service

Selecting Severity as the criterion will show the alarms in the following order: Critical

Major

Minor

Unknown

Warning

Once selected, the current criterion is associated with a triangle signal. Choosing a new order doesnt reduce the number of alarms displayed in the list.






4.9 Sorting Alarms [cont.]

Selecting the sort keys

As we have seen earlier, the Alarm Manager brings up a listing of all the alarms that are associated with the Network Elements.

In addition to the display criteria, the alarm manager allows sorting alarm records. With this feature, the users can define three sort keys among the available columns in the alarm manager list:

Primary sort key

Secondary sort key

Tertiary sort key

To specify the sort keys, the user opens the Sort Alarm List option from the Action menu and selects the keys as well as the direction ascending / descending.

Right click any of the sort key column to deactivate this feature.In the slide above, the selected sort keys are:

1) Type,

2) NE Name,

3) Severity.






4.10 Alarm Information Load View

Tiny NEs

From the OAM 5.0, the Resource Browser provides two kinds of views: the existing topology view and a new grid layout view called info load. The Grid layout View offers a convenient way to display large numbers of NEs such as in typical wireless edge networks. This option includes the following capabilities:

In a Grid View only NEs and groups are displayed. They are automatically displayed in a grid pattern (i.e. uniform rows and columns of objects), with all NEs displayed in front of all groups. The links between NEs are not displayed.

The Grid Size of a Grid View can be set. Changing the Grid Size enables the user to control the number of objects that are visible in a single window. When a smaller Grid Size is selected, the information displayed for each NE or group (alarm balloons, labels, icons, etc.) is reduced to enable more objects to be visible in the window.

Information in a Grid View can be sorted and filtered according to certain options such as sorting both NEs and groups by name, filtering so that only the ones with new alarms are displayed, etc..

As shown in the slide above, the new Grid Layout view includes 4 icon sizes. The information load shows the percentage of criteria selected to be associated with the NEs.






4.11 Info Load View [cont.]

Grid view: sort alarm from left to right according to severity etc. possibility to filter alarms

On the left: not sorted not filtered, max size; on the right, sorted by severity, filtered on new alarms, min size 25%

4 sizes: max size, 75%, 50%, 25%

Sort - NEs and groups are sorted from left to right and top to bottom. Sort by Name: NE and group name in alphabetical order and by Severity: alarm severity are possible. Filter on - You can limit the display to NEs display can be limited by filtering on All alarms, New alarms, Acknowledged alarms or No alarms Auto-refresh - When the grid view is sorted by alarm severity or a filter is applied, the display will update dynamically when the Auto-refresh box is checked






4.12 Info Load View [cont.]

Sortingthe NEs

Filtering the NEs

Sorting by Severity:

1- Critical 2 Lille B-182 2 Lille B-1272- Major 1 Lille B-152 Etc3-Minor 1 Lille B-070 Etc4-Warning 1 Lille B-078 Etc

Sorting by Severity:

1- Critical 2 Lille B-182 2 Lille B-1272- Major 1 Lille B-152 Etc3-Minor 1 Lille B-070 Etc4-Warning 1 Lille B-078 Etc

Info.Load

Sorting capabilities: The position of the NEs in the Grid Layout View can be adjusted to reflect the sorting of NEs based on two criteria:

The Default order is the order defined by the user when the layout was last saved. This is the only stable NE positioning reference in the Layout. It enables the user to find a given NE in a given position in the grid when needed. If "Default order" is selected the position of the NEs does NOT change when the Alarm State and Status of the NEs changes if the Auto-refresh option is selected or if the Refresh command is used.

The By severity is the order where NEs are laid out based on the Alarm Status and State of the NE (listing the worst cases first). If "By severity" is selected the position of the NEs changes when the Alarm State and Status of the NEs changes if the Auto-refresh option is selected or if the "Refresh" command is used.

Filtering capabilities: The display of the NEs can be adjusted to show only those alarmed or acknowledged, etc.. The display option includes the option to filter on the following items:

All Alarms: Only alarmed NEs will be displayed acknowledged or not. New alarms: Only NEs will unacknowledged alarms will be displayed Acknowledged alarms: Only NE with ack. alarms will be displayed No alarms: Only NEs without alarms ack. or not will be displayed

With these enhancements, the customers have the ability to have the entire network view in one window.






4.13 Radio Network Subsystem View

RNCs

RNS#4

This feature provides an additional optional view of UMTS Access Network Elements in the Resource Browser. The RNS View shows the relationship between one specific RNC and its related Node-B NEs. It aligns with the designs of other W-NMS browser views, which include the ability to scroll, filter, sort, and launch other applications.

The screenshot above shows an example, where RNCs are displayed at the top of the window whereas their related Node-B NEs are grouped below. This example shows a relatively large network view, with NEs sorted by severity of alarms.

Additional information about a selected NE is shown in an In Focus: description located at the bottom.

POCs are not seen in this particular RNS view.Note:

This feature does not position Node-B NE according to an assigned numerical identifier. For example,Node-B NEs related to a particular RNC are not assigned a position number 0 through 200. Instead, they are positioned by the users selected sort option.






4.14 Alarm due to Board Insertion & Extraction

Board extraction in cabinet 0, shelf 0,

Boards inserted in (or extracted from) the BTS automatically generate a warning message. This new alarm is attached to BTS object in the Equipment Monitor window.

However, the plug & play mechanism is preserved: afterwards, the Equipment Monitor window still reflects the physical board layout (30s refresh period).

Multi Service Switches provide the ability to add extended information to the alarm comment text on a per port basis. This feature allows operators to provision text of their choosing to be appended to the comment field of alarms for specific MSS interface ports.

These additional comments appear in the Alarm browser and the Historical Fault Browser.

This feature allows for instance to indicate the name of the remote node connected to the faulty interface, hence facilitating troubleshooting.






4.15 Alarm Annotations

The operator has the ability to annotate alarm type (fault code) from the alarm browser by right clicking on an alarm. An editor is provided to add the annotations.

From the NSP alarm window, the user first selects the concerned alarm type by right clicking on an alarm record. Next, he presses the Edit (left part) button and writes down his annotation.

Rights

The latest user editing the annotation has the ability to edit the entire annotation. Only authorized users have the rights to edit the annotation. The rights are controlled by the access control framework.

Users can edit / modify the Annotation for the alarms which are saved on the Main server and purged accordingly to the platform administration rules.

The user name, the date and time as well as the hostname and IP @ of the location are recorded in the annotation.

Display

If there is only one Fault-code and Help Volume per alarm type, then the Alarm Annotation window will be displayed.

If there are multi Help Volumes for the selected alarm, an Option Panel will popup to select one specific Help. Next, the Alarm Annotation window will be displayed.






4.16 User Preferences

Sort key:column name and

order

Column sizes Sorting order(chronology)

This facility allows the operator to save his own user preferences related to the alarm manager display.

Starting from OAM 5.0, customers have the capability to save their own user preferences such as column order, size, and sorting settings.

The size and position of the window are also recorded.

By keeping the alarm manager user preferences, operators save considerable time since they dont have to set up their preferences each time they log in.

This way, they can immediately start to supervise the network in terms of fault management, based on the alarm manager tool in concordance with their most optimized display preferences.






4.17 Raw Details

Some alarms include text fields that are too large for the Alarm Manager window.

The Alarm Record Viewer shown above allows you to view the raw alarm fields.

Open the Alarm Record Viewer from the Alarm Manager window (Action menu) by selecting View Raw Details.

The Alarm Record Viewer displays all the alarm fields in a scrollable text field. The Alarm Record Viewer window contains an Edit menu with a Copy command.





5 Reduce the alarms displayed in the Alarm Manager





5 Reduce the alarms display in the alarm manager

5.1 Criteria for filtering (by Severity & Acknowledgment)

In alarm filtering criteria and In Alarm stream rule set, the advance filter GUI and ruledefinition GUI should provide the Alarm Code filter in the Problem Specific tab with the following conditions: Contains, does not contains, equals, not equal to.

Previous OAM05 alarm code values are not maintained. After OAM upgrade all active alarms raised before upgrade are shown with the legacy

alarm code (OAM05 alarm code) until they are cleared, all new alarms raised after upgrade are shown with the new OAM06 alarm code value.

The help on-line for alarms (Selected Item Help on contextual menu), is not available for these remaining OAM05 alarms.






5.2 Criteria for filtering (Advanced Filter)










5.3 New criteria for filtering

You can filter By

Alarm code









6 Acknowledge the alarms





6 acknowledge the Alarm codes display

6.1 Acknowledge the alarms









7 Clear the alarms





7 Clear the alarms

7.1 Clear the alarms









How to Do it



All R

Documents

Ce Tmo18261 9353 Wms Ua07 Utran Fault Management