02 OS82122EN80GLA00 Fault Management

Nokia Solutions and Networks

1 (210)

NetAct 8

Fault Management

Legal notice


1 (210)

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Solutions and Networks training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training material. Individuals can use the Nokia Solutions and Networks 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 Solutions and Networks. The Nokia Solutions and Networks training material cannot be used outside of an agreed Nokia Solutions and Networks training session for development of groups without the prior written agreement of Nokia Solutions and Networks.

Indemnity

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document.

Nokia Solutions and Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT

This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The NSN logo is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Export Control Marks:

AL: N and ECCN=5E991 or AL: N and ECCN=N (as in TCM course core data)

This course is subject to the European Export Control Restrictions.

Copyright 2014 Nokia Solutions and Networks. All rights reserved.

.

Content


2 (210)

Content

1 Fault Management Basic Concepts 4

1.1 Fault Management Overview 5

1.2 Strategies for Effective Network Monitoring 7

1.3 Fault Management Events 9

1.4 Alarm Flow Supervision 11

1.5 Defining the Components of Network Topology 12

2 Common Operations in the NetAct Monitor Desktop 17

2.1 Fault Management System in NetAct 8 18

2.2 Using the Monitor Desktop 20

3 Basic Fault Management Operations: Monitoring the Network 35

3.1 Fault Management Workflow 36

3.2 Alarm Monitoring Tools 38

3.3 Alarm Monitoring using Alarm Lists 40

3.4 Alarm Monitoring using Network Views 52

3.5 Finding Managed Objects 73

4 Basic Fault Management Operations: Alarm Statistics Reporting 97

4.1 Alarm Reports Dashboard 98

4.2 Alarm Reports Dashboard Configuration 99

4.3 Search Alarms 101

4.4 Search Result 103

4.5 Scheduling Task List 105

4.6 Schedule Task Report 105

5 Advanced Fault Management Operations: Alarm Filtering and Reduction of the Alarm Flow 107

5.1 Filtering the Alarm and Warning Lists 108

5.2 Alarm Flow Reduction in NetAct 116

5.3 Configuring Alarm Reduction in NetAct 119

5.4 Reducing alarms caused by network maintenance with Maintenance Mode 120

5.5 Rule Explorer and Rule Editor 125

6 Advanced Topology Management 149

6.1 Managing Network Views 150

6.2 Managing Working Sets 163

6.3 Creating, deleting and Modifying Managed Objects 170

7 Revising the Alarm Management Functionality 181

7.1 Fault Management Pipe Status 182

7.2 Manual upload of Alarms 184

7.3 Deleting Alarms of an Object 186

8 Exercises 189

Exercise 1 191

Content


3 (210)

Exercise 2 192

Exercise 3 194

Exercise 4 197

Exercise 5 199

Exercise 6 201

Exercise 7 203

9 Solution 205

Solution 1 207

Fault Management Basic Concepts


4 (210)

1 Fault Management Basic Concepts



5 (210)

1.1 Fault Management Overview

Fault management is one of the main functions in network management. The purpose of fault management is to detect, isolate and correct malfunctions in a network.

The basic requirement for keeping telecommunication services up and running, is a good understanding of the network situation. Network elements contain monitoring and diagnostic tools for detecting various types of fault situations. In a typical situation a network element recognizes malfunction and sends an alarm to NetAct.

A single fault in the network can cause a number of various alarms in several network elements. The reliability of the alarm database and efficient network troubleshooting practices form a base for successful network management. Established alarm analysis practices are a part of the troubleshooting process. Faults that affect the quality of service and, therefore, are visible to the subscriber have to be recognized and corrected as soon as possible. NetAct offers network management tools for reliable alarm collection and monitoring. It provides a set of tools for pre-processing, storing, and displaying alarm and event information from the network in real time.

In global network and service monitoring the focus of monitoring is the whole network that includes several sub-networks, various technologies, and geographical regions. This global monitoring process includes alarm collection from the managed sub-networks and their management systems through southbound multivendor integration (MVI) interfaces and through the NetAct 6 Cluster. Northbound interfaces are available to support the data forwarding to third-party network management systems.

NetAct Monitor offers tools for collecting and storing real-time information from the network to detect and analyze faults in network elements and for monitoring the quality of service provided by the network.



6 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 2014 Nokia Solutions and Networks. All rights reserved.

Fault ManagementOverview

The purpose of the network monitoring is to detect, to isolate and correct

malfunctions in the network.

Fault Management consists of all the tasks oriented to prevent critical faults

in the network and to identify the problems that directly affect the quality of

the service, criteria by which subscribers judge the quality of the network.

GSMGSM

WCDMAWCDMA

I-HSPAI-HSPA

LTELTE

HLR

MSC

hiE

SGSNLIG

GGSN

Flexi NG

NW Monitoring

Fig. 1



7 (210)

1.2 Strategies for Effective Network Monitoring

The primary aim of effective network monitoring is to prevent critical faults in the network and to identify the problems that directly affect the quality of the service, that is, the criteria by which subscribers judge the quality of the network.

Network monitoring can be a reactive process where a high number of alarms arrive during a day, causing a lot of manual routine work in alarm handling. The operator can, however, develop a network monitoring process so that it becomes a planned, controlled process where monitoring personnel can focus their attention on the essential problems in the network. There are different ways to make network monitoring more effective.

1.2.1 Using Views hierarchies

A view is a logical representation of the object hierarchy that includes parent and child objects. A main view visualizes the parent objects of the network and the subview contains the child objects that are controlled by the same parent object. Subviews can be created to monitor, for instance, prioritized geographical areas, workstation networks, or transmission networks. For easy navigation in the view hierarchy, there can be links between the views, for example, from the main view to the workstation network view or to the transmission network view. Proper planning of the network main view and subviews makes it possible to trace an alarm to the correct source of the problem.

1.2.2 Alarm Flow Reduction

Alarm situations can be anticipated and operators can make plans to reduce the alarm flow. The reduced alarm flow makes it easier to spot the real source of problems and to start working on solutions as quickly as possible. The flow of alarms can be reduced by means of alarm filtering, alarm reclassification, and alarm correlation.

1.2.3 Alarm Trigger

The Alarm Trigger feature can be used for automating certain external and internal processes that support the daily routines of alarm handling. The default processes that can be triggered automatically vary. The operators can define the trigger rules.

1.2.4 Maintenance Mode

The Maintenance Mode can be used to block alarms that arrive from sites under maintenance. Alarms that arrive from objects in maintenance mode are not shown in the alarm handling applications. This mode can be activated for a managed object or for a managed object and its subordinate network .



8 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Fault ManagementStrategies for Effective Network Monitoring

Reduces the amount of manual work required in the

network monitoring

Network Views Graphical representation of the network elements

hierarchy and their alarm status organized accordingly to

network configuration.

Main view to visualize parent objects

Subviews to visualize child objects.

Alarm Flow Reduction Reduced alarm flow presents to the user only the

relevant events.

Alarm TriggeringAutomatically starts up defined external and internal

processes on the occurrence of specific configured

events..

Easier fault localization and visualization

Improved network QoS: faults affecting the service are investigated more quickly.

No information overloadSkilled personnel concentrated in problem solving

rather than in alarm handling

Less operational costs

Fig. 2



9 (210)

1.3 Fault Management Events

1.3.1 Alarms

An alarm is a message that notifies the management system of an abnormal condition in the managed system. The message carries information on the origins, time, and possible reasons for the abnormal condition. In NetAct this information is broken down into different fields. The fields are put together to construct the alarms which are shown in the alarm handling applications.

All alarms have an alarm number that identifies the possible reason for the alarm.

Alarms are placed into a class that indicates their severity.

1.3.2 Alarm Acknowledgement

If an alarm is raised an operator has to acknowledge the error condition to indicate that appropriate corrective action will be taken.

1.3.3 Alarm Cancel

Alarm Cancel is a message that clears an alarm when the fault situation is over. In managing a telecommunications network it is very important to clearly indicate the end of an alarm situation. If alarms are not cancelled is not possible to have an accurate and up-to-date view of the network situation.

1.3.4 Warnings

NetAct also supports warnings that provide information on transient error situations. Unlike alarms, warnings do not have start and end times and are not cancelled.

1.3.5 Alarm Upload

To ensure consistency of alarm information between the different databases, you can upload alarms from the network elements to the NetAct Cluster.



10 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Fault ManagementFM Events

Fault Management Events

Alarms

Cancel: Automatic cancel - Manual cancel

Acknowledgement Unacknowledgement Change event Alarm upload (synchronization)

Alarm class (or Perceived Severity)

The alarm class represents the severity of the alarm.

The following alarm classes are used in NetAct:

critical (***)

major (**)

minor (*)

warning

Alarm Class Required Actions

Critical (***) This type of alarm is likely to cause disturbances in traffic. You must take action within one hour

Major (**) You must take action within working hours

Minor (*) You do not have to take action unless the alarm occurs repeatedly

Warning (W) You do not have to take any action

Alarm number

Each alarm has an alarm number for identification purposes. The alarm number can have a value between 1

and 99999.

Fig. 3



11 (210)

1.4 Alarm Flow Supervision

Alarm Flow Supervision feature ensures that alarms from network elements are not lost or delayed on their way to NetAct. The supervision involves heartbeat alarms, which are sent by a network element if no other alarms have been sent for 15 minutes (by default).

The heartbeat alarms are not stored in the NetAct database, nor are they relayed to NetAct alarm handling applications. If no heartbeat alarms are raised during the specified period, an alarm is generated and shown in the Active Alarms List.

1.4.1 Alarm Types

The event type provides more information on the problem that caused the alarm. The following event types are used in NetAct.

Alarm Type Explanation

Communication An alarm that is associated with the procedures and/or processes which are required to convey information from one point to another (for example, loss of frame or call establishment error)

Environmental An alarm that is associated with a condition relating to an enclosure in which the equipment resides (for example, door open or electricity failure)

Equipment An alarm that is related to an equipment fault (for example, power problem, receiver failure or I/O device error)

Event processing An alarm type that is associated with a software or data processing fault (for example, storage capacity problem, version mismatch, corrupt data, file error or out of memory)

Quality of Service An alarm that is associated with certain degradation in the quality of service (for example, response time too long, resource limits near, or congestion)



12 (210)

1.5 Defining the Components of Network Topology

1.5.1 Topology

The topology of a network is the representation of the actual physical elements of the network, where they are located, and how they are related to each other. To get an accurate representation of the network it is important to keep the topology as consistent with the actual physical network as possible.

1.5.2 Managed object

A managed object represents a physical or a logical network element, or a piece of equipment that belongs to the network. This element must be connected to NetAct, so that NetAct can be used to manage it by gathering information, such as information on alarms, from it. In some cases information can be downloaded from NetAct to the managed object.

1.5.3 Managed object class

All managed objects of the same type are grouped together to form a class. This enables NetAct to represent the elements in the network in a logical way. In NetAct software each class is represented by its own symbol. These symbols can be used in the NetAct Monitor to make graphical views of the network.

1.5.4 Managed object instance

In the same way that a managed object class represents a type of network element, a managed object instance represents one unique element. For example, workstation is an object class, while a workstation physically located in the monitoring room is an instance of the workstation class.

Each managed object class can have several instances, depending on the configuration of the network. In the NetAct documentation, managed object instance is often referred to as managed object or object.

1.5.5 Parent and child objects

Managed objects are often hierarchical with certain objects controlling and containing others. This hierarchy is shown in the NetAct object model as well. A parent object controls or contains a child object.



13 (210)

1.5.6 Site object

A site is a place where one or more of the elements of the network are located. One site can contain more than one managed object. If there are multiple elements on one site, the site object represents the element which is highest in the hierarchy on that site. For example, a site may contain an OMC as well as one of its workstations.

1.5.7 Distinguished Name

Distinguished Name (DN) is an effective identifier of a particular managed object instance. It contains the relative Distinguished Name of the object instance in question, plus the relative Distinguished Names of all its parent objects. These are shown as a path of elements arranged in a hierarchical order and separated by a slash (/). For example:

ClassName-InstanceValue/ClassName-InstanceValue/ClassName-InstanceValue

which corresponds to:

PLMN-PLMN/OMC-2/WS-4

ClassName is an abbreviation for a managed object class name and consists of numbers or capital letters. The maximum length of InstanceValue is ten characters and the value must contain printable characters. These are often numbers, but they do not necessarily have to be.

DistinguishedName must contain at least two ClassName-InstanceValue levels. Interfaces can set their own limitations for the length of the Distinguished Name.

The following figure shows how the DistinguishedName is formed in the NetAct Object Model.

1.5.8 Global Identifier (GID)

The Global Identifier is a number which uniquely identifies a MO in the Topology. The same MO always has the same GID in any NetAct system.

1.5.9 Internal ID

The internal ID is a number which uniquely identifies a MO within one NetAct system (within a regional or the global system). The same MO usually has not the same internal ID in different NetAct systems.

1.5.10 Object State

The Object State specifies whether the MO exists in the actual configuration ("operational" or "created from network" state) or not ("non-operational" state).



14 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Fault Management Basic ConceptsNetwork Topology, Managed Objects and Distinguished Names

Managed Object (MO)

Parent Object

MO Distinguished name:PLMN-PLMN/NTHLRFE-1/ACP-1/ACTADAPTER-1

MO Global ID:

501667000000006793

Fig. 4



15 (210)

1.5.11 Working Sets

Managed object refers to an abstract representation of a network resource, which can be either a physical or logical entity, in a network managed by NetAct.

Working set refers to a set of managed objects to which recurring management tasks are applied. Working sets facilitate network management, for example, when certain configuration changes are applied to a set of network elements recurrently. For example, network operators often want to configure a set of base stations with the same radio network parameters. In this case, the use of working sets can facilitate configuration management significantly.

1.5.12 Maintenance Regions

A maintenance region is a logical managed object in NetAct Object Model. It is a collection of managed objects that are grouped together, normally to represent some geographical part of the network.

NetAct Monitor applications allow to define maintenance regions that should be monitored. Dividing the network view into two or more maintenance regions facilitates online monitoring because that way the number of alarms that different groups responsible for network operation need to analyze is reduced.

Using maintenance regions

The system administrator can create separate Maintenance regions within the network.

Dividing the network view into two or more maintenance regions makes online monitoring easier as it reduces the number of alarms that personnel in operation need to analyze. For example, it may be useful to have separate maintenance regions for different geographical areas, for prioritized areas, or for certain types of alarms.

The users can set up monitoring criteria that narrow the focus of monitoring so that they can concentrate only on the network areas or alarm numbers needed.



16 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Components of the Network TopologyManaged Objects, Maintenance Regions and Working Sets

Maintenance RegionGroup of network elements and their subordinate

managed objects, which are managed by a certain

part of an organization. A maintenance region

represents a maintenance domain.

Maintenance Region I

Managed ObjectRefers to an abstract representation of

a network resource, either a physical or

logical entity in a network.

Network Assurance scope I

Working SetsGroup of managed objects to which

recurring management tasks are

applied. Users create their own

working sets.

Maintenance Region II

Fig. 5

Common Operations in the NetAct Monitor Desktop


17 (210)

2 Common Operations in the NetAct Monitor Desktop



18 (210)

2.1 Fault Management System in NetAct 8

The fault management monitoring tools in NetAct Monitor are used to manage alarms from various network elements and types, to perform root cause analysis, to troubleshoot faults that cause disruptions in network services, and to improve the quality of the network services for subscribers.

The NetAct Monitor fault management system consists of an FM event collection engine, FM event correlation engine, FM adaptation fragments, mediation interfaces, and fault management monitoring tools.

Event Collection Engine collects and preprocesses the alarm events. Depending on selected filtering attributes, the alarm events are loaded into the alarm database and monitoring tools at defined intervals. Separate forwarding filters control the alarm forwarding to northbound mediations.

Event Correlation Engine is used to consolidate the volume of alarms produced in the network. The number of alarm events in a network can be higher than the number of actual faults. The Event Correlation Engine combines the alarms that are associated with one another. Instead of displaying each alarm separately, it displays the root cause to the end user. Users can implement operator-specific correlation rules to best suit their needs.

Fault Management Monitoring tools

NetAct System provides fault management functionalities with versatile monitoring tools integrated on top of the Monitor Common Desktop. The available views and editing permissions for different rules depend of pre-defined user rights.



19 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Fault Management and Topology Management in NetAct

Event Collection

Event Processing

Event Post-processing

Event forwarding NetAct Monitor offers tools for collecting and

storing real-time information from the network

to detect and analyze faults in NEs as well

as monitoring the quality of service provided

by the network.

Fig. 6



20 (210)

2.2 Using the Monitor Desktop

2.2.1 Monitor Applications

Most of the NetAct Monitor Applications can be accessed from the Tools menu in NetAct Monitor graphical user interface. Some of the tools (for example, Properties) can be launched context-sensitively from a pop-up menu in another tool.

Authorization in the Monitoring Desktop applications

Several Monitoring Desktop applications require an authorization process. This process is used to determine, if you have permissions to access the data, functionality, or service.

When you log in to the application, the login credentials are validated. If your login credentials are valid, you will be provided access to the application. The permissions to perform certain operations are based on the specific roles assigned to you.

Authorization is given by the system administrator

Wizards

NetAct Monitor provides wizards that support the creation of different items, for example objects or rules. The following wizards are available in the File menu:

New Rule

New Alarm Filter

New View

New View Folder

New Object

New Group

New Role

These wizards can also be accessed via other tools. For example, the New Rule wizard can be started from Rule Explorer and the New Object wizard from Object Explorer.



21 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct Monitor Common DesktopApplications

Permission Management

Administration Tools

Managed Objects

Managed Objects

Monitoring Desktop

Monitoring

Operation Tool

Operations

Administration ToolsTo administrate the user permissions to objects and

operations in Monitor

Operation ToolTo keep track of current or past operations in

Monitor

Managed Objects ToolsTo visualize and manage the network topology data

Monitoring ToolsTo visualize and manage the network alarms

Optional Tools

Trouble ticket tools The trouble ticketing and workflow management system is integrated to NetAct

Monitor via the OSS/J interface. The trouble tickets or

work orders can be attached to alarms, and they are

shown in the Monitor Desktop to enable managing the

fault and handling work orders.

Base Tools

Fig. 7



22 (210)

2.2.2 Common Desktop Functionality

Common desktop functionality refers to the generic functionality of the Desktop, shared by all the individual tools and the main application window. It includes general principles of how operations (such as copy and paste or sorting) work throughout the user interface.

The NetAct Monitor tools are integrated in the Desktop Framework. On the Desktop the user can flexibly change the view that is used for the monitoring. Changing from one tool to another, and finding the relevant content are made easy for the user by context-sensitive navigation, drag-and-drop support and use of the menu entry. Each user can also set up the tools to match the requirements of their actual task and to store that setup.

The Desktop Framework provides the following tool-independent services to support the daily workflow:

forward and backward navigation in sub-windows for fast workflow navigation

object menu offering comprehensive context related services from other integrated tools and applications

drag and drop support

quick search for data filtering

field information and tool tip when hovering over graphical user interface components

automated information update for object properties and alarm help in case the instance selections changes within a tool

easy and flexible window management

The tool utilization principles are the same across all tools, which means that when the user has learnt to use one tool, he or she can successfully use all the other tools in Desktop Framework.



23 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct Monitor Common DesktopWorkspace

Managed Objects tools

Properties Tools working area

Tabs displaying the

opened tools

Fig. 8



24 (210)

2.2.3 Managing the Workspace

In the context of the Desktop, workspace refers to how the application is displayed in the application window.

The default configuration of the workspace contains four areas: Explorer area, Properties area, Editor area and Output area. Desktop tools open in windows that are displayed in these areas; the default location of a tool window depends on the settings for the tool and the workspace.

Tools that you open in the same area are displayed on tabs.

Which tools (tool windows) are available depends on how the desktop has been previously configured.

The workspace is customizable and you can save your customized settings.

2.2.4 Managing tool windows

In the Desktop workspace, tools display their data in tool windows. You can move the tool windows around in the workspace in the Explorer, Properties, Editor and Output areas and dock them in place where you like. The windows can also be stacked on top each other in the Explorer, Properties, Editor and Output areas so that a row of tabs is visible.

You can display some of the tools in several windows at once, and changes made in one window are instantly reflected in all open windows for that tool.

Moving a tool window

Click the window header and drag it to the desired position.

A preview box shows where the window will reside.

Drop the window.

Maximizing a window and restoring window size

Double-click the window header.

The window is maximized or restored to its original size.

Browsing through tool windows

If there are several windows open in an area, they are stacked and displayed as tabs.

To browse through stacked windows, click on the tabs along the top edge of the tool window. If more windows are stacked in the same area than can be displayed (in other words, if all the tabs do not fit in the window and some are hidden), you can use the right and left arrows to the right of the row of tabs to display the hidden tabs.

You can also click the downward-pointing arrow to display a list of all available tabs and then click the name of the tab you want.



25 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct Monitor Common Desktop

Managing the Workspace

2. Dropping the window.

Rearrange the desktop tools

visualization by:

1. Clicking the window header and

dragging it to the desired position

Fig. 9



26 (210)

2.2.5 Editing data and saving the changes

When you edit the properties, locations or other aspects of Desktop entities, the changes have to be saved. You have several options available for saving your changes: using the Save and Save All menu items or buttons and saving your changes when exiting the Desktop.

Menu items, buttons and keyboard shortcuts

To perform a standard Save operation on the active tool, you can use the Save menu item, the Save toolbar button or the related keyboard shortcut. This Save operation saves the changes made in the active tool only.

The Save All functionality accessed using the Save All menu item, Save All toolbar button or the related keyboard shortcut saves data changes made in all currently open tools, not just the active one.

WARNING

When you click the menu item or toolbar button, the workspace configuration is not saved.

The Save dialog on exit

When you close the main window without explicitly saving your changes, a Save dialog opens, allowing you to select which changes to save.

To save changes to some items only, select an item or items in the dialog (hold down the Ctrl key to select multiple items) and click Save. When the save operation is complete, click Discard All to exit without saving any other changes.

Save saves the changes made to selected items.

Save All saves all changes.

Discard All saves no changes.



27 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct Monitor Common DesktopManaging the Workspace: Saving Changes

Save the current

configuration of your

workspace in the

Window menu

System will request for saving when exiting

Monitor Application if changes are not yet saved

Fig. 10



28 (210)

2.2.6 Using the clipboard

The Desktop supports copying and pasting data within the application. Some tools even support pasting operations to other applications, such as a text or spreadsheet editor.

To place an item on the clipboard, select the item in the tool window and then, on the Edit menu, click Copy or Cut.

To insert the contents of the clipboard, place the cursor or activate the tool where you want the data to be inserted and then, on the Edit menu, click Paste.

2.2.7 Using the Properties tool

To open the Properties tool, click Tools -> Properties. Some tools also offer the option of viewing the properties of an object by right-clicking and selecting Properties on the pop-up menu.

Sorting in the Properties tool window

Right-click anywhere in the Properties tool window. A pop-up menu opens.

Sort by category sorts the properties to different categories depending on the set of properties that can be shown.

Sort by name sorts the properties by the name of the property.

Showing the description area of the Properties tool

To display additional information about the selected property, right-click anywhere in the Properties tool window and click Show description area.



29 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


NetAct Monitor Common DesktopManaging the Workspace: Using the Clipboard and Properties tools

Fig. 11



30 (210)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

02 OS82122EN80GLA00 Fault Management

Documents

Transcript of 02 OS82122EN80GLA00 Fault Management