NetAct Training Manual

Nokia
Networks
Network Operations and

Maintenance Tasks with
NetAct (NetAct 16.5)
Student Guide
OS8212-16A-NRM

2 Network Operations and Maintenance Tasks with NetAct (NetAct 16.5)
This page is left blank for your notes.
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
......................................................................................................................................
© Nokia Solutions and Networks. All rights reserved.
......................................................................................................................................
......................................................................................................................................

Legal Notice 3
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 NETRORKS 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.
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.
Copyright © Nokia Solutions and Networks 2013. All rights reserved.
About Nokia
Nokia invests in technologies important in a world where billions of devices are connected. We are
focused on three businesses: network infrastructure software, hardware and services, which we offer
through Networks; location intelligence, which we provide through HERE; and advanced technology
development and licensing, which we pursue through Technologies. Each of these businesses is a
leader in its respective field.
Through Networks, Nokia is the world’s specialist in mobile broadband. From the first ever call on
GSM, to the first call on LTE, we operate at the forefront of each generation of mobile technology. Our
global experts invent the new capabilities our customers need in their networks. We provide the world’s
most efficient mobile networks, the intelligence to maximize the value of those networks, and the
services to make it all work seamlessly.
http://www.nsn.com
http://www.company.nokia.com

Safety statements in Student Handouts
Presents information to identify and warn of a situation where improper

precautions will result in death or serious (irreversible) personal injury.
Presents information to identify and warn of a situation where improper

precautions could result in death or serious (irreversible) personal injury.
Presents information to warn of a potentially hazardous situation where

improper precautions could result in minor or moderate (reversible) personal
injury. This alert is also used to identify a situation where equipment damage
could occur and help you avoid damaging your equipment.
Presents information to identify and warn of a potentially hazardous situation

to help avoid the possibility of property damage.

Contents 5
Contents
Network Operations and Maintenance Tasks with NetAct (NetAct 16.5)
Getting started with NetAct ...................................................................................13
Module Objectives ................................................................................................ 13
Nokia Operations and Support System ................................................................ 13
What is NetAct?..................................................................................................13
Nokia Cloud Application Manager...................................................................... 14
Cloud Network Director ..................................................................................... 15
NetAct Managed Network Model........................................................................16
Knowledge Check: NetAct functionality..............................................................18
Knowledge Check: NetAct Managed Network Model.........................................19
NetAct Architecture and virtualization....................................................................20
Three tiered Architecture.................................................................................... 20
Virtualization....................................................................................................... 21
NetAct Deployments...........................................................................................23
NetAct Interfaces ............................................................................................... 25
Knowledge Check: Virtualization........................................................................ 26
Knowledge Check: NetAct Deployments............................................................27
Accessing NetAct...................................................................................................28
NetAct Start Page...............................................................................................28
Lab exercise: Connecting to NetAct .................................................................. 30
Lab exercise: NetAct Start Page........................................................................ 31
NetAct Application Categories .............................................................................. 32
Start page Applications Categories.................................................................... 32
Reporting category............................................................................................. 33
Configuration category....................................................................................... 36
NetAct Configurator............................................................................................ 38
Working Set Manager.........................................................................................39
Configuration Management – Flexible CM Search.............................................42
Monitor category.................................................................................................43
User Assistance Category.................................................................................. 46
Administration category...................................................................................... 47
Security category................................................................................................49
Optimization category.........................................................................................50
Lab exercise: Application Categories................................................................. 51
Managed Objects...................................................................................................52
Components of Network Topology..................................................................... 52
NetAct User Assistance ........................................................................................ 55
Operating Documentation...................................................................................55
Nokia Online Service ......................................................................................... 58

Online Documentation........................................................................................ 59
Object Information Browser................................................................................ 61
Lab exercise: NetAct User Assistance (1/2)....................................................... 64
Lab exercise: NetAct User Assistance (2/2)....................................................... 66
Lab exercise: Object Information Browser..........................................................68
Summary: Getting started with NetAct ..................................................................69
Basic Fault Management with NetAct................................................................... 71
Module Objectives ................................................................................................ 71
Fault Management Basic Concepts ......................................................................71
Strategies for effective network monitoring........................................................ 71
Fault Management events.................................................................................. 73
Alarm Flow supervision...................................................................................... 74
Defining components of Network Topology........................................................ 75
Maintenance Region...........................................................................................78
Knowledge Check: Fault Management Concepts ............................................. 79
Common Operations in NetAct Monitor Desktop ..................................................80
Fault Management System in NetAct................................................................. 80
Monitor Applications........................................................................................... 82
Common Desktop Functionality..........................................................................83
Using default keyboard shortcuts....................................................................... 87
Audible Alarms................................................................................................... 89
Lab exercise: NetAct Monitor Desktop............................................................... 92
Monitoring Network ...............................................................................................94
Fault Management workflow ..............................................................................94
Alarm Monitoring tools........................................................................................95
Alarm Monitoring using Alarm Lists.................................................................... 97
Alarm Details...................................................................................................... 99
Alarm History.................................................................................................... 100
Warning List......................................................................................................101
Reconfiguring Alarm and Warning Lists display............................................... 102
Immediate access to Alarm and Object Tasks from Alarm Lists...................... 103
Alarm Monitoring using Network Views ........................................................... 104
Loading Views in Network View....................................................................... 105
Network Views Monitor Modes......................................................................... 107
Network Objects and Topology......................................................................... 110
Alarm and Subview States................................................................................117
SingleRAN Site View........................................................................................ 119
Site View...........................................................................................................121
Finding Managed Objects.................................................................................123
Object Explorer.................................................................................................124

Contents 7
Displaying Managed Objects Attributes............................................................126

Alarm Operations in an Object......................................................................... 128
Searching for managed objects........................................................................131
Managed Objects List.......................................................................................133
Switching the view mode and selecting columns attributes..............................134
Filtering managed object classes..................................................................... 135
Object Search...................................................................................................137
Viewing objects associated with a Maintenance Region or Site.......................139
Navigating to other tools...................................................................................140
Customize user interface .................................................................................141
Lab exercise: Object Explorer Tool ..................................................................142
Lab exercise: Object Search ........................................................................... 145
Lab exercise: Configuration Database Modification......................................... 148
Lab exercise: Network Views........................................................................... 150
Lab exercise: Alarm Lists and Warning Lists....................................................152
Alarm Statistics Reporting .................................................................................. 154
Alarm Reports Dashboard................................................................................ 154
Alarm Reports Dashboard Configuration..........................................................155
Search Alarms.................................................................................................. 157
Search Result................................................................................................... 160
Scheduling Task List.........................................................................................162
Lab exercise: Alarm Report Dashboard........................................................... 163
Summary: Basic Fault Management ...................................................................165
Advanced Fault Management with NetAct..........................................................167
Module Objectives .............................................................................................. 167
Alarm Filtering and Reduction of Alarm Flow...................................................... 167
Alarm flow reduction in NetAct......................................................................... 167
Maintenance Mode .......................................................................................... 169
Alarm filtering ...................................................................................................171
Create Rules with Rule Editor.......................................................................... 175
Alarm Correlation..............................................................................................180
Grouping types................................................................................................. 181
Creating Rules..................................................................................................184
Compression Rule............................................................................................ 185
Count Rule........................................................................................................187
Toggle Rule.......................................................................................................189
Threshold Rule................................................................................................. 191
Informing Delay Rule........................................................................................ 192
Reclassification Rule........................................................................................ 193
Suppression Rule............................................................................................. 194

Filtering Rule.................................................................................................... 195

Trigger Rule...................................................................................................... 197
Alarm definitions............................................................................................... 198
Lab exercise: Rule Explorer and Rule Editor....................................................206
Lab exercise: Alarm Filters............................................................................... 208
Lab exercise: Alarm Rules................................................................................210
Topology Management.........................................................................................211
Managing Network Views................................................................................. 211
Network Views Monitor Modes......................................................................... 212
Creating and Editing Network Views................................................................ 214
Adding a link between two objects................................................................... 216
Linking and unlinking a sub-view......................................................................217
Saving a view................................................................................................... 220
Creating Children Objects’ Subviews............................................................... 221
Automatic View Generation.............................................................................. 222
Working Set Manager.......................................................................................223
Creating managed objects................................................................................226
Associating a Managed Object to Maintenance Region...................................228
Associating a Managed Object to Site..............................................................229
Editing object attributes in the Properties tool.................................................. 231
Object Deletion................................................................................................. 233
Deleting managed objects in the operational state...........................................234
Handling of Alarm Processing............................................................................. 236
Fault Management Pipe Status........................................................................ 236
Alarm database upload........................................................................................237
Manual upload of Alarms..................................................................................237
Alarm Deletion for a MO...................................................................................... 239
Deleting Alarms of an Object............................................................................239
Lab exercise: Enable FM Pipe..........................................................................240
Summary: Advanced Fault Management with NetAct......................................... 241
Basic Performance Management with NetAct....................................................243
Performance Management Principles .................................................................243
Performance Management process................................................................. 243
Purpose of Performance Management.............................................................247
Reporting Needs...............................................................................................248
Counters, Measurements and Observations.................................................... 254
Logical Counters and KPIs............................................................................... 256
Key Performance Indicators and Reports.........................................................257
Knowledge Check: Performance Management Concepts................................258

Contents 9
NetAct Performance Manager tools.....................................................................259
Performance Management system ..................................................................259
Performance Manager tools............................................................................. 260
Performance Manager start page.....................................................................262
Lab exercise: Performance Manager tools.......................................................264
Knowledge Check: Performance Manager applications...................................265
Create, customize and generate performance management reports and
dashboards.......................................................................................................... 266
Creating reports................................................................................................266
Saving and generating reports......................................................................... 270
Real-time PM display with dashboards............................................................ 272
Rehoming support for 2G and 3G.................................................................... 273
Lab exercise: Create report for active user equipment with category 5 for
MRBTS............................................................................................................. 274
Creating Dashboards........................................................................................276
Viewing and customizing reports......................................................................278
Report Navigator.............................................................................................. 280
Report Suite Publisher......................................................................................281
Lab exercise: Report Creator........................................................................... 282
Summary: Basic Performance Management with NetAct....................................283
Advanced Performance Management................................................................. 285
Create, modify and publish KPIs ........................................................................ 285
KPI Creator introduction................................................................................... 285
Creating KPIs................................................................................................... 287
Example KPI creation....................................................................................... 292
KPI Publisher....................................................................................................294
Lab exercise: Creating, modifying and publishing KPI .................................... 295
Manage preferences and schedule reporting...................................................... 296
Preferences...................................................................................................... 296
Report Scheduler .............................................................................................297
Lab exercise: Scheduling a report.................................................................... 298
Set threshold values for alarms........................................................................... 299
Thresholder and Profiler .................................................................................. 299
Lab exercise: Object selection..........................................................................300
Lab exercise: Time Selection........................................................................... 301
Lab exercise: Alarm Settings............................................................................302
Lab exercise: Threshold information and notification....................................... 303
Create and activate measurement plans............................................................. 304
Administration of Measurements...................................................................... 304
Creating plan.................................................................................................... 305

Activating plan.................................................................................................. 308

Lab exercise: Creating new measurement plan for LTE cell load ................... 310
Summary: Advanced Performance Management................................................ 311
Configuration Management..................................................................................313
Configuration Management in NetAct .................................................................313
Overview...........................................................................................................313
Configuration Management Process................................................................ 314
Configurator Basic Concepts............................................................................315
Managed Objects............................................................................................. 316
Working sets.....................................................................................................317
Configuration Types..........................................................................................318
Configuration Rules and Checks...................................................................... 322
NetAct Configurator Applications.........................................................................323
Configurator Architecture..................................................................................323
CM Editor..........................................................................................................324
CM Analyzer..................................................................................................... 325
CM Rule Editor................................................................................................. 326
Selecting a template type................................................................................. 327
Filling in the templates parameters...................................................................328
CM Operations Manager.................................................................................. 329
CM Reference.................................................................................................. 330
Flexible CM Search.......................................................................................... 331
CM History........................................................................................................332
Hardware Management functionality................................................................ 333
Command Line Operations in Configurator...................................................... 335
Intelligent feature activation .............................................................................336
Configurator Basic User Tasks............................................................................ 337
General Workflow............................................................................................. 337
Sychronize Network Data................................................................................. 338
Locking NE configuration data for exclusive usage..........................................341
Hardware Configuration Upload / Export..........................................................342
Viewing Actual Configuration............................................................................344
CM Editor: View Filter.......................................................................................347
Managing Working Sets................................................................................... 349
Selecting Working Set to be used as filter........................................................351
Adding managed objects to working set(s).......................................................353
Creating working set from CM Query............................................................... 355
Modifying Parameters via Working Set............................................................ 356
Deleting Objects from the NetAct CM Database ............................................. 361

Contents 11
Exporting Configuration.................................................................................... 366

Export / Import data with CM Editor..................................................................368
CM Express Data Exchange............................................................................ 369
Exporting relationship plan using CM Editor - Table Editor.............................. 370
Importing relationship plan using CM Editor.....................................................373
Displaying plans............................................................................................... 374
Mass parameter changes and plan creation.................................................... 375
Changing Mass Parameter...............................................................................376
Creating Plan....................................................................................................379
Early plan validation in network controllers...................................................... 381
More granular provisioning permissions...........................................................382
Checking Plans.................................................................................................383
Provisioning Plans............................................................................................ 386
Procedure: Provisioning plans..........................................................................388
Comparing plans to actual configuration.......................................................... 390
Executing Commands in Network Elements using Command Manager.......... 392
Searching Managed Objects with Flexible CM Search.................................... 393
Operations with CM History..............................................................................395
Generating report on parameter changes........................................................ 396
Viewing historical configuration snapshots of NEs........................................... 399
Command Line Operations: Massive Provisioning via CLI...............................401
Lab exercise: HW Inventory Management....................................................... 404
Lab exercise: CM tools..................................................................................... 405
Optimizer............................................................................................................. 408
Optimizer Overview.......................................................................................... 408
Optimizer main user interface...........................................................................410
Summary: Configuration Management................................................................ 413
License management in NetAct...........................................................................415
NetAct licensing concepts....................................................................................415
NetAct Licensing...............................................................................................415
NetAct software asset protection......................................................................... 418
NetAct hard lock............................................................................................... 418
License Manager to check licenses ....................................................................422
License Management Overview ...................................................................... 422
Licensing Concepts: Pool License....................................................................425
Licensing Concepts: License Sets....................................................................426
License States.................................................................................................. 427
License Management Tasks............................................................................. 429
License Import.................................................................................................. 430

Viewing Licenses..............................................................................................432
Uploading Licenses.......................................................................................... 435
Exporting Licenses........................................................................................... 436
Distributing Licenses........................................................................................ 437
Feature Templates............................................................................................440
Network Element Audit against Feature Template........................................... 442
License Pool Substitution................................................................................. 443
Licenses Reports..............................................................................................444
Viewing Recent Operations.............................................................................. 446
Software Asset Monitoring...................................................................................447
Introduction to Software Asset Monitoring........................................................447
Software Asset Monitoring Notifications........................................................... 450
Software Asset Monitoring Reports.................................................................. 451
LTE and SRAN Licenses..................................................................................... 454
LTE and SRAN License Management..............................................................454
Summary: License management in NetAct......................................................... 457
Software Management.......................................................................................... 459
Software Management.........................................................................................459
Software Management in NetAct......................................................................459
Software Manager............................................................................................ 461
Software Manager Operations..........................................................................463
Software Manager Graphical User Interface.................................................... 464
Network Software Status.................................................................................. 465
Viewing details of a Managed Object............................................................... 467
Uploading software configuration information from NE to NetAct.................... 469
Network Operations- Tasks.............................................................................. 472
Software Archive.............................................................................................. 474
Attaching / Viewing Software Package Documentation....................................476
Viewing Compatible Managed Objects.............................................................479
Changing status of software package in Software Archive.............................. 481
Network Element Backup.................................................................................... 483
Network Elements Remote Backup from NetAct..............................................483
Network Elements Backup Archive.................................................................. 484
Summary: Software Management....................................................................... 486

Getting started with NetAct 13
Getting started with NetAct

Module Objectives
• Explain the role of the NetAct in the mobile network.
• Describe the NetAct architecture and the virtualization concept.
• Access the NetAct start page.
• Describe the main functionalities of NetAct.
• Describe the components of the managed object.
• Use NetAct Documentation.
Nokia Operations and Support System

What is NetAct?
NetAct is the Network Element manager in the Nokia and OSS portfolio.
Performance Manager, Advanced Monitor and Advanced Configurator are using the
same platform as NetAct and have some applications in common.
The following figure illustrates the Nokia and OSS portfolio.
Figure 1: Nokia and OSS portfolio

Nokia Cloud Application Manager

The following figure illustrates the key features of Nokia Cloud Application Manager.
Figure 2: Nokia Cloud Application Manager Overview

Cloud Network Director

The following figure illustrates the Cloud Network Director:
Figure 3: Nokia Cloud Network Director

NetAct Managed Network Model

The role of NetAct in managing a network can be classified into two categories:
• NetAct operation system
• NetAct Global Level (umbrella) products
A cluster is a networked grouping of one or more servers and disk drives that are
designed to support each other if a failure occurs in one server or network
component. A cluster consists of several co-operating nodes that are interconnected
in a redundant way to distribute information and resources.
A NetAct cluster is a hierarchical, highly available, and secured computing system
that consists of multiple internal components, such as servers, a shared storage
system, LAN switches, and routers. It contains the necessary security control, such
as encryption capability in data communication, firewall protection, and a hardened
system platform.
Regional Cluster
A Regional Cluster manages a specific region and provides a view to a particular
network area or technology. The network elements of a certain sub-network are
connected to and managed by a Regional Cluster, which contains the network
management system for that region.
NetAct can contain several Regional Clusters, which can be connected to the
NetAct Products that work in a Global level.
Each Regional Cluster runs a database that stores the data arriving from the
network elements in the managed region. In the Regional Cluster you do not have
access to the data that arrives from network elements belonging to another Regional
Cluster. You can have an overview of all the managed objects in the network only in
the Global level.
Global Level Products

The Global Level Products are umbrella solutions that provide an entire view of the
network in areas of Fault Management, Performance Management and
Configuration Management.
The global level products are intended for centralized, network-wide management
tasks. They are not connected directly to the network elements but communicate
with one or more Regional Clusters. Because these platforms are connected to all
the Regional Clusters, you can have a view of all the network elements.
Multiple NetAct instances and other Network Management Systems or other
vendors, for example MVI, can be connected to a single NetAct Global Product
instance.
There are three NetAct Global level Products:
• NetAct Advanced Monitor
• NetAct Advanced Configurator
• Nokia Performance Manager
The following figure illustrates the NetAct Managed Network Model.

Figure 4: NetAct Managed Network Model

Knowledge Check: NetAct functionality

This section test the students on differentiation of the functions of NetAct Products
for Regional Clusters and Global Level.
1. What is the main functionality of NetAct?
Notes
1. __________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________

Knowledge Check: NetAct Managed Network Model

This section test the students on differentiation of the functions of NetAct Products
for Regional Clusters and Global Level.
1. What is the relationship between NetAct (regional level) and the NetAct
Advanced Monitor, Advanced Configurator and Nokia Performance Manager
Systems?
Notes
1. __________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________

NetAct Architecture and virtualization

Three tiered Architecture
The hardware platform of NetAct consists of three main parts, namely servers,
storage devices and network equipment, such as switches and routers.
NetAct’s software architecture is three-tiered: the tiers are
Presentation tier Presentation tier hosts client applications. The client
applications access Business logic tier and reside
typically on a user workstation, for example, a laptop or a
desktop computer. The recommended workstation is an
office PC with either Windows or Linux operating system.
Business logic tier Business logic tier hosts the business logic and data

access specific for NetAct.
Data tier Data tier hosts NetAct data storages, that is, the database

and directory servers.
Business logic and Data tiers are separated from Presentation tier by firewalls and
reside inside the secure domain.
Both Business logic tier and Data tier utilize virtual machines running on one or
more host servers dedicated to NetAct.
The following figure illustrates the NetAct architecture.
Figure 5: NetAct Architecture

Virtualization
With NetAct, we are stepping into a virtualized environment. In a virtualized
infrastructure (VI), software is set up in such a way that it can operate independently
from the underlying hardware. The physical resources of multiple machines are
shared across the whole infrastructure, and they act as a resource pool. In a VI, the
physical hardware resources are divided into smaller units, virtual machines (VMs)
that have their own allocated virtual CPU and memory.
The virtualization layer (HW virtualization capability) is provided by the VMware
hypervisor. Servers simply add I/O, CPU and RAM computing resources to the HW
pool and virtualization provides a logical view of data, computing power, storage
capacity and other server resources.
There are no longer dedicated hardware roles. Instead, NetAct applications,
mediations, and services running on a number of VMs are powered by a hardware
resource pool. Each VM is dimensioned and optimized for the service or services
running in it. In this way, the same NetAct functions can be provided but with better
high availability and scalability options.
The following figure illustrates the virtual environment of NetAct architecture.
Figure 6: NetAct Architecture - Virtual environment
Benefits of virtualization in NetAct

Virtualization in NetAct brings the following benefits:
• Reduced CAPEX and OPEX by consolidation, for example, improved HW
utilization, and the possibility to co-locate Nokia products.
• Near zero downtime upgrade: Upgrade can be performed by cloning the system
within the virtualized infrastructure. Upgrades are performed on the clone side
and then after upgrade testing, the clone system becomes the live system.
• Zero downtime hardware maintenance and capacity can be added without
business impact.
• Efficient high availability and disaster avoidance solutions by using shared
redundancy resources.
• All HW resources are in efficient use: No more fixed amount of physical servers
or standby nodes as virtual machines are distributed by load. In addition,
decoupling NetAct and 3rd party HW/SW makes HW planning more flexible.
• Increased elasticity, in other words, scalability in a virtual environment.
• Less licenses are needed.
The following figure illustrates the benefits of virtualization.

Figure 7: Benefits of virtualization
Scalability in virtualized infrastructure

Scalability is an important feature of the virtual NetAct environment since there are
software components that can be located on more than one VM, and conversely,
one VM can contain more than one software component.
If the load increases beyond a virtual machine’s ability to handle the load, then the
software component and/or virtual machine must be scaled to cope with the
increased demand. However, not all software components scale in a similar way:
• Some software components are designed to scale horizontally, which means
that additional virtual machines need to be provisioned in order to enable the
software component to distribute its load. Horizontal scalability is enabled by
placing software components behind load balancers.
• Other software components scale better vertically, which means that additional
resources (CPU and memory) need to be allocated to the virtual machine where
the software component is hosted.

NetAct Deployments
NetAct is delivered on three standard configurations: Small, Mainstream, and Large
using HP blade servers.
Table 1: NetAct Deployments: EMC solution

NetAct Server Model No. of Storage System
Configuration Blades
Small – 23 HP BL460c Gen9 1p12c 4 VNX Small:
VMs 96GB VNX5200: 3x100GB
Optional extra 1x Intel E5-2680v3 twelve SSD SSF + 9x600GB
– 15 VMs core processors 96 GB SAS SFF + 13x1TB
memory NL_SAS SFF
Diskless 3PAR7200: 8x480GB
2x10GbE LAN; fc controller SSD + 8x900GB SAS
SFF
(16G)
VNX Backup:
VNX5200: 5x600GB
SAS SFF + N x
(8x1TB NL-SAS SFF)
Mainstream – HP BL460c Gen9 2p8c 6 VNX Medium:

29 VMs 128GB VNX5200: 5x100GB
Optional extra 2x Intel E5-2680v3 eight core SSD SSF +
– 22 VMs processors 128GB memory 13x600GB SAS SFF
Diskless + 21x1TB NL_SAS
SFF
2x10GbE LAN; fc controller
VNX Backup:
(16G)
VNX5200: 5x600GB
SAS SFF + N x
(8x1TB NL-SAS SFF)
Large – 35 HP BL460c Gen9 2p12c 6 VNX Large:

VMs 256GB
VNX5200: 5x200GB
Optional extra 2x Intel E5-2680v3 twelve SSD SSF +
– 26 VMs core processors 256GB 17x600GB SAS SFF
memory + 27x1TB NL_SAS
Diskless SFF
2x10GbE LAN; fc controller VNX Backup:

(16G) VNX5200: 5x600GB
SAS SFF + N x
(8x1TB NL-SAS SFF)

Table 2: NetAct Deployments: HP solution

NetAct Server Model No. of Storage System
Configuration Blades
Small – 23 HP BL460c Gen9 1p12c 4 HP Small:
VMs 96GB 3PAR7200: 8x480GB
Optional extra 1x Intel E5-2680v3 twelve SSD + 8x900GB SAS
– 15 VMs core processors 96 GB SFF
memory HP Backup:
Diskless
P2040 G4: 6x2TB
2x10GbE LAN; fc controller MDL LFF
(16G)
Mainstream – HP BL460c Gen9 2p8c 6 HP Medium:

29 VMs 128GB 3PAR7200: 8x480GB
Optional extra 2x Intel E5-2680v3 eight core SSD + 16x900GB
– 22 VMs processors 128GB memory SAS SFF
Diskless HP Backup:
2x10GbE LAN; fc controller P2040 G4: 6x2TB
(16G) MDL LFF
Large – 35 HP BL460c Gen9 2p12c 6 HP Large:

VMs 256GB 3PAR7200:
Optional extra 2x Intel E5-2680v3 twelve 12x480GB SSD +
– 26 VMs core processors 256GB 24x900GB SAS SFF
memory HP Backup:
Diskless P2040 G4: 6x2TB
2x10GbE LAN; fc controller MDL LFF
(16G)
NetAct also supports EMC VNX5400 extra large configuration due to capacity and
performance requirement which is required for NetAct Datacenter and scalability
solutions. For example, for co-locating with other products such as Network360 and
SON with NetAct storage platform.

NetAct Interfaces
In NetAct, interface-related issues are very important, since dependencies are
controlled via interfaces, and controlled dependencies are a key enabler of
modularity - an important property of the NetAct architecture.
NetAct can be integrated into external systems via Northbound interfaces. External
systems are employed for similar monitoring, reporting and network planning tasks
as NetAct, but at a higher abstraction level. These higher-level systems can be
either Nokia or third-party management systems.
Lower-level systems or network elements can be integrated into NetAct via
Southbound interfaces. Again, these lower-level systems can be either Nokia or
third-party element management systems.
Mediations are responsible for the interworking or conversion between the protocols
or data formats used in the lower-level or higher-level systems and the protocols or
data formats used in the NetAct system.
Protocols used in the lower-level or higher-level systems are, for instance, SNMP,
SOAP or HTTP, and data formats are, for instance, ASCII or XML.
Figure 8: NetAct Interfaces - Northbound and Southbound
Refer to the NetAct documentation to check what are the supported functions
for each Network Elements and information on the Northbound interfaces.

Knowledge Check: Virtualization

This section test the students on the description of NetAct virtualization.
1. List two benefits of virtualization.
Notes
1. __________________________________________________
____________________________________________________
____________________________________________________
____________________________________________________
____________________________________________________

Knowledge Check: NetAct Deployments

This section test the students on the differentiation of the three NetAct hardware
deployments and explaination on how system scalability is implemented.
1. List the three configuration types of NetAct. How is the system size scaled
taking into account the virtualization?
Notes
1. __________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________

Accessing NetAct
NetAct Start Page
NetAct Start Page is a centralized launch pad for starting NetAct user interface
applications. You can start all the NetAct applications that have been configured and
for which you have permission to launch from NetAct Start.
NetAct uses Single Sign-On (SSO) for accessing applications through NetAct Start.
To be able to access applications through NetAct Start, a user must have a valid
user name and password. The user also must be granted the permissions for
accessing the needed applications. Depending on the permissions granted for the
user, a list of published applications is visible to the user.
From the right-hand dropdown menu the user can select between two different
views.
Folder view shows the different fragments as folders. The applications are grouped
into the following functional areas:
• Administration: Applications for administering adaptations.
• Configuration: NetAct CM applications, License Manager and Software
Manager.
• Optimization: Applications for network Optimization.
• Monitoring: NetAct Monitor.
• Reporting: NetAct Reporter.
• Security: Certificate, User Management and NE User Management applications.
• User Assistance: Operating documentation library.
Clicking the Online Help icon opens the Online Help Browser. By selecting Show all
applications from the dropdown menu the user can see all the applications in one
view and access them by mouse click.
All the Java applications are installed on the application server cluster when NetAct
is deployed. When a Java Rich Client is accessed for the first time, it is downloaded
by the Java Service Wrapper (JWS) to user workstation and launched for the user.
The next time it is accessed, the application is started from the local JWS cache.
JWS checks the version of the application every time it is launched on the user
workstation, and if necessary, updates the application from the application server.
The following figure illustrates the accessing NetAct.

Figure 9: Accessing NetAct
New applications visualization modes

The following figure illustrates the start page view modes.
Figure 10: Start Page View modes

Lab exercise: Connecting to NetAct

Context
This section test the students for setting up the connection to NetAct system and
functions of the NetAct Start Page.
Figure 11: Lab exercise: Connecting to NetAct
Procedure
1 Login to lab.
2 Open session to NetAct system as omc user.
Result of this step

Describe the access to NetAct.
Did you need to install NetAct SW in your local machine to access the system?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: NetAct Start Page

Context
This section test the students on setting up connection to NetAct system and
functions of the NetAct Start Page.
Figure 12: Lab exercise: NetAct Start Page
Procedure
1 Login to NetAct and navigate to Start Page.
Result of this step

Describe the purpose of the NetAct Start Page.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 Change the visualization mode of NetAct Start Page from Show All Application

to Show Applications by folder.
Result of this step

What is the difference between the two visualization modes?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

NetAct Application Categories

Start page Applications Categories
Each application that a user can launch from NetAct is grouped into the following
categories according to what kind of tasks it is used for:
Table 3: NetAct Applications Categories

Categories Description
Administration Applications used for the administration of Mediations and
Adaptations in NetAct. Provides as well access to Element
Managers.
Deployment For AddOns Management. AddOns are enterprise applications
that can be deployed to the NetAct server.
Configuration Set of applications used to manage the network configuration.
Optimization Set of applications used to optimize the network configuration.
Monitoring This is the group for fault management applications to monitor
and troubleshoot the managed network.
Reporting Use these applications to start measurements and generate
reports on the performance of the managed network.
Security Applications for User Account Management, Network Elements
User Management and Certification Authority (Certificates
generation).
User Assistance Applications to access User Documentation and Information
Adaptation Browser.
Some applications are optional and require a license, otherwise they are not visible
in NetAct GUI. The applications are grouped into functionality areas.
The following figure illustrates the NetAct application categories.
Figure 13: NetAct Application Categories

Reporting category
The Performance Manager in the Reporting category is described as follows:
Performance Manager
Performance Manager is a centralized, multi-vendor, multi-technology data reporting
solution, providing easy and accurate information on network wide performance,
usage and quality statistics.
The new easy-to-use GUI allows advanced reporting, threshold supervision, profiling
and trending on long term raw and aggregated data. By using Performance
Manager tools the NetAct users are able to:
• Create and edit reports, for private or public usage
• Create and edit KPIs, for private or public usage
• Browse for existing KPIs and reports
• Customize dashboards with tables and multiple chart types
• Schedule reports and distribute them through email in CSV or XLS format
• Customize the web portal look and feel and setup your preferences
Performance Manager is multi vendor-capable and collects data from the entire
network that consists of network elements from Nokia and from other vendors.
Performance Manager includes also several ready-made report packages.
The following figure illustrates the Reporting category.
Figure 14: NetAct Applications Categories - Reporting
Administration of Measurements
Administration of Measurements (AoM) application enables the PM Administrator
user to manage (enable/disable) measurements on network elements to allow data
collection from network elements to NetAct.
This application can be used to view, create, modify and delete measurement plans
and templates.
Measurement plans can be used to start and stop the measurements on the network
elements. AoM also helps to upload measurement plans from the network elements
to NetAct.
This tool contains the following tabs:

• Network Overview: It enables the user to view the activation status of
measurements in the network.
• Plans: It enables the user to create, modify, delete, activate and deactivate
plans.
• Templates: It enables the user to create, modify and delete a template. It also
allows the user to create a plan based on an existing template.
• Upload Overview: It enables the user to view a summary of all the upload
operations carried out during a specific time period for specific NE types.
Thresholder and Profiler

Thresholder and Profiler are NetAct applications that are integrated with NetAct
Performance Manager: they allow setting and managing thresholds or profiles,
respectively, for the counters or KPIs calculated in Performance Manager.
Profiler capitalizes on the observation that the measured values of a KPI often follow
a pattern. Profiler tracks this pattern and provides a reliable approximation of the
typical value of the KPI based on a week's data.
Nevertheless, the user can define a threshold and a profile for the same KPI
independently from each other: if a user enable thresholding and profiling but the
threshold is not a profiled threshold, Profiler still maintains the profile for the KPI.
This way a user can monitor the KPI actively (with the threshold and by receiving
violation notifications) and at the same time user can also gather longer-term
information on the KPI (with the profile).
Software Asset Monitoring

Software Asset Monitoring application collects and processes the configuration and
measurement data based on customer specific settings. It generates a report on the
feature usage and forwards the formatted monitoring data to the customer and
Nokia Customer Team through an encrypted e-mail. The encrypted e-mail can be
read and validated by Customer and Nokia Customer Team only. The report on the
feature usage is used to generate an invoice. One software monitoring report
comprises information related to one NetAct cluster.
For LTE and Flexi Direct, software monitoring is the only way of usage
control as License Keys are not implemented for these technologies.
Software Asset Monitoring enables speed and efficiency with fast software
activations through bypassing the pre-activation procurement process, and applying
alternative pricing models where invoicing is based on network configuration or on
used functionality. This results in OPEX savings and in an increased flexibility.
The following figure illustrates the functions of Performance Management.

Figure 15: Performance Management Functions

Configuration category
This following section describes the NetAct Configurator.
NetAct Configurator
NetAct Configurator is a component in the scalable NetAct framework for operating
mobile networks. Configurator gives access to real-time network configuration data
and provides tools to manage network configuration. The basic functionality of
NetAct Configurator is to define and manage parameter data in the network.
Network architecture can be functionally grouped into the access network and the
core network. The access network handles all radio-related functionality while the
core network is responsible for routing calls and data connections to external
networks. With Configurator, the access network and core network are managed in
a centralized way.
The main functionalities of Configurator are:
• Storing the network parameters in the database
• Data exchange with external tools
• Setting, modifying, viewing, and comparing network configuration data
• Mass modifications on the network: integrating sites, extending and optimizing
the network
• Small scale tuning of the network configuration
Software Manager, License Manager

Software Manager and License Manager are centralized NetAct applications for the
network management of Software (NetAct and NEs Software) and Licenses (NetAct
and NE's licenses).
Self-Organizing Networks Scheduler

Self-Organizing Networks (SON) Scheduler allows user to view and configure
operations related to Wideband Code Division Multiple Access (WCDMA) Flexi
BTS(s) as well as auto connection and auto configuration features both in the
network and planned configuration. SON Scheduler functionality manages the four
following features in Long-Term Evolution (LTE) networks:
• Peripheral Component Interconnect (PCI) Conflict Resolution
• Mobility Robustness
• Synchronization of Inter-Radio Access Technologies (RAT) Neighbors
• Optimization of Intra LTE Neighbor Relations
It provides advanced filtering options to improve displaying required information as
well as an array of scheduling options.
Plan Editor
Plan Editor allows the user to edit radio network plans offline, making it possible to
modify all network parameters locally on a PC. Changes to the network topology or
either single parameter changes or mass operations on large groups of parameters
can be planned in a format that can be used by network planning and management
systems.

Plan Editor Graphical User Interface (GUI) displays managed objects in a
hierarchical order and provides a drag-and-drop functionality to ease the planning
work.
Plan Editor includes a reporting functionality, Parameter Dictionary, for online
reference and help on parameter value ranges, and the possibility to store several
default parameter sets.
Figure 16: NetAct Applications Categories - Configuration

NetAct Configurator
This section describes the NetAct configurator.
Maintaining up-to-date picture of the network

Working with the latest data is a precondition for exploiting the full potential of any
network. Configurator not only retrieves configuration data from network elements
whenever desired. It also saves this information to allow operators create an archive
of configuration stages to give them vital insight and thus enables them to optimize
their network. Built-in Northbound interface capability allows for the export of data
towards third-party post-processing applications.
Configuring the network

Configurator provides offline planning capabilities to prevent any mistakes to be
made on a running network. Current and planned configurations can be compared
to identify the best solution. Plausibility checks prevent errors from the start. An
Import functionality is available which enables to process network plans which have
been prepared outside of Configurator in an operator’s planning environment.
In the configure phase all three Configurator components work hand-in-hand:
• CM Editor is used for displaying configuration data and for comfortable editing of
data when creating a network plan.
• CM Analyzer is used for use case specific running of consistency checks.
• CM Operations Manager comes into the game when externally created network
plans are imported into the Configurator application for further processing. With
the Command Manager, CM Operations Manager allows the direct execution of
commands and command files (on-demand or scheduled) to network elements.
Once a new configuration has been defined automatic delta command generation
takes care of spelling out all necessary changes in the relevant network element
specific data formats. Controlled deployment of all administration is provided by the
provisioning capability.
The automation of all download tasks ensures network consistency and minimizes
operational efforts, allowing a complete transparency of all planning and with
minimized margin for error. All provisioning steps are controlled by the CM
Operations Manager.
Figure 17: Configurator Functionality

Working Set Manager

NetAct allows to create groups of network elements and operate on them, so to
ease their management. The grouping can be based for example on area, feature
enabled, alarming status or parameters. The operator can also create an own list or
use additional criterias for the grouping.
A group of network elements is refered to as working set. The maximum number of
managed objects in each working set is 100 000. The creation of such working sets
helps in minimizing the time needed to fix faults in these sites.
Working sets are categorized into:
• Static working sets, where the list of managed objects is invariable.
• Dynamic working sets. These are based on a constant criteria, but the managed
objects can be added or removed based on network changes.
Once the working sets are defined, it is possible to execute operations in all the key
NetAct applications.
The following figure illustrates the Working Set Manager:
Figure 19: Working Set Manager
Working Set Manager – Show all view

Working Set Manager is the tool where you can create, view, search, export and
delete working sets.
The application user interface gives quick access to all the working set already
existing and enables to easily create new ones.
The initial view of Working Set Manager shows the list of all existing groups. You
can search for a specific one using the search box, or organize the list by name,
type, creation and modification dates. From this view you can delete or export the
selected groups.
There are 3 main types of working sets:
• Distinguished Name (DN) List, which consists of a static list of managed object
DNs.
• Area, Configuration Management (CM) Query, Fault Management (FM) Query,
CM Advanced Query and Combined compose the second type. These working
sets have dynamically changing content based on the selected criteria.

• Legacy is a working set that was not migrated to the new data representation, or
its migration script was not executed correctly. This working set cannot be
edited.
The following figure shows the view of Show all in Working Set Manager tool:
Figure 20: Working Set Manager – Show all view
Working Set Manager – Create new working set

A new working set is created based on DN List, FM Query, CM query, CM Advanced
Query, Area or Combination criteria. The correct form can be selected from the tabs
at the top of the user interface.
In the example, it is shown a FM Query working set formed by network objects
having over two unacknowledged critical alarms.
The following figure displays creating the new working set:
Figure 21: Working Set Manager – Create new working set
Working Set Manager – Create a new combined working set

• Union creates a new working set containing all Managed Objects (MO) both
sets.

• Intersections creats a new working set containing only common objects.
• Difference creates a new working set composed by MOs contained in the first
set, but not in the second one.
The following figure displays creating the new combined working set:
Figure 22: Working Set Manager – Create a new combined working set

Configuration Management – Flexible CM Search

A search engine is available in NetAct system. This tool is called Flexible CM
Search. It is a web application in NetAct Configurator that allows searching for radio
and core network elements.
From the landing page it is possible to type key words and in few moments the
results are provided. The search can be based on different criteria, for example the
name of NE, identification number or location. It’s possible to use also only partial
information.
The following figure shows the configuration management with flexible CM search:
Figure 23: Configuration Management – Flexible CM Search
This application enables to:
• View details of the element. This will provide the list of parameters with
corresponding value.
• Show active alarms for the NE selected.
• Upload a new configuration.
• Open the object in CM Editor, a NetAct tool for configuration management.
• Reset cells right from the search page.
The results can be used by other NetAct applications, for troubleshooting purposes,
configuration and fault management operations.
The following figure shows the Configuration Management – Flexible CM Search:
Figure 24: Configuration Management – Flexible CM Search results

Monitor category
The Monitoring is described as follows:
NetAct Monitor
NetAct Monitor provides a new desktop and a new toolset for monitoring tasks. The
fault management monitoring tools in NetAct Monitor can be 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.
NetAct Monitor provides:
• List and view based alarm monitoring
• Object management tools
• Rule management for automated alarm handling and correlation
• Alarm filtering
• Alarm forwarding to e-mail
• Trouble Ticket management tools
• OSS/J Trouble Ticket Northbound interface
• 3GPP CORBA Fault Management Northbound interface
• Application launch for all NetAct tools, including NetAct OSS5 level applications
NetAct Monitor toolset accelerates the monitoring workflow by providing centralized
monitoring tools on a single screen for different networks.
Alarm filtering and correlation rules help to automate the regular fault management
actions and reduce the alarm flow to NetAct Monitor alarm tools and upper level
systems integrated through 3GPP CORBA Fault Management Northbound interface.
OSS/J Trouble Ticket interface together with trouble ticket tools enhances the
trouble ticket handling within monitoring tools.
NetAct Monitor supports user specific customization on tool views and tool set-ups
and its permission management supports user group specific tool and operation
permissions.
With this integrated toolset NetAct Monitor provides excellent support for daily
monitoring tasks in operations helping operator to gain OPEX savings when tools
are in full use.
Figure 25: NetAct Applications Categories - Monitoring
The following figure illustrates the Alarm Report Dashboard.

Figure 26: Monitoring Category: Alarm Reports Dashboard
The following figure illustrates the troubleshooting with monitor tools.
Figure 27: Troubleshooting with Monitor Tools
Trace Viewer
Tracing is a concept name for an optional NetAct functionality, which is performed by
the TraceViewer application, and allows the tracing of mobile equipment and
subscribers in mobile networks.
TraceViewer enables global tracing, which means that a user can trace an
International Mobile Equipment Identity (IMEI) number or International Mobile
Subscriber Identity (IMSI) number throughout the network. Additionally, the
TraceViewer application provides a mechanism for administering, collecting and
viewing information related to a specific subscriber or mobile equipment.
TraceViewer can activate traces in several network elements, including Nokia RNC,
FlexiNS. In addition, TraceViewer receives events from Nokia BSC and MGW
network elements.
Trace data is collected from the network elements and is sent to TraceViewer, where
it can be viewed in the form of reports.
TraceViewer can be also used to support network planning and optimization. After
changing the network parameters, users can easily verify that all sites are working
as planned, by using TraceViewer’s graphical and textual presentations. This tool is
also used for real-time troubleshooting to follow the functionality of the network and
possible problems with a call.

Operators can use tracing to troubleshoot problems with mobile equipment or
subscriber’s connections and to follow up customer complaints. Tracing can be also
used to monitor the network and to check the results of the network optimization.

User Assistance Category

The following section describes the user assistance category.
Operating Documentation
NetAct operating documentation contains the user assistance needed for the daily
network management operations. The documentation is available on NetAct user
workstations in a browsable format. The NetAct application Online Helps are
available in the same NetAct Operating Documentation set, and they can be
launched via context-sensitive launch from the NetAct applications.
Object Information Browser

Object Information Browser (OIB) is an application used for browsing of alarm,
measurement, counter, and both radio and core network parameter descriptions, as
well as object class information and changes between network element releases.
OIB user interface provides following functions for utilizing the adaptation reference
information:
• Search
• View
• Browse
• Compare
• Export to spreadsheet or XML
• Print
• View release changes
• Select GUI columns for browsing and export
The following figure illustrates the user assistance.
Figure 28: NetAct Applications Categories – User Assistance

Administration category
The section describes the administration category.
Adaptation Manager
An adaptation is a set of fragments such as Configuration Management (CM),
Performance Management (PM), Fault Management (FM), and other fragments.
These fragments contain data that enables NetAct to communicate with any
Network Element (NE). Several releases of an adaptation can be deployed to
NetAct to support multiple versions of network elements.
Adaptation Manager allows to manage adaptations. A user with adequate roles and
permissions can perform the following actions with Adaptation Manager:
• Deploying adaptations, Un-deploying adaptations, Redeploying adaptations
• Viewing adaptations
Dynamic Adaptation
Dynamic Adaptation GUI is a web application, which provides an interface to view
and trigger the Dynamic Adaption process. It allows as well monitoring the dynamic
adaptation status. The network elements integrated via Dynamic Adaptation are
those managed by @vantage agent, generic agent or ne3s agent.
When Dynamic Adaptation is triggered for a network element from the Web UI, the
request is dispatched to Dynamic Adaptation Mediation. After that, mediation starts
to upload metadata for the network element. These metadata contents are
processed, and then adaptations are generated dynamically. Adaptations for
@vantage agent or generic agents are generated dynamically based on the fault
management, performance management, and configuration management metadata
present on the network element. Adaptations for ne3s agent are generated
dynamically based on the fault management and performance management
metadata present on the network element. The generated adaptations are then
deployed into NetAct System dynamically. Once the Adaptation process is
completed, Dynamic Adaptation GUI is updated with the status of the adaptation.
NE Integration Wizard
Network element integration wizard application is used by system administrator to
automatically integrate a network element to NetAct.
SNMP FM Mediator
SNMP FM Mediator application allows system administrator to activate, deactivate,
and configure parameters of agent supervision, trap reliability, and alarm upload
functions for all network elements. Parameters as such as timeout, retries, number
of messages to be handled and so on can be configured with this tool.
With SNMP FM Mediator, you can:
• Configure global parameters for agent supervision
• Configure global parameters for trap reliability
• Configure parameters for agent supervision by network elements
• Configure global parameters for alarm synchronization

SNMP PM Mediator
SNMP PM Mediator allows system administrator to activate, deactivate, and
configure parameters of PM mediation (for example, timeout, retries and number
messages handled in parallel mode).
Using SNMP PM Mediator, administrator user can:
• Configure global parameters
• Configure parameters for PM Polling by network element
• Configure polling for existing network elements
SNMP PM Mediator application allows administrator to configure performance
management measurement data polling for the SNMP based network elements and
stores the performance indicators in the system. The performance indicators are
configured in the performance management adaptation and the mapping between
SNMP variables and performance indicators is defined by the SNMP PM fragment
of the adaptation. The network elements having SNMP PM fragments deployed on
NetAct can be polled by the SNMP PM mediation. If performance management
adaptation exists, then the data is used by performance management and stored in
performance management database.
Map Administrator
Map Administrator is an administration tool designed for managing the Geographic
Information System (GIS). GIS combines data with location. The main usages for
such a system are data retrieval and visualization based on the location, for
example, showing computed network coverage or dominance on a map.
The following figure illustrates the NetAct Applications Categories - Administration.
Figure 29: NetAct Applications Categories - Administration

Security category
The following section describes the User Management.
User Management
User management is a web based management system for monitoring, managing
and administering users and groups. The user management application manages
user profile information, groups and password policies and ensures the security of a
user.
User management is integrated with Permission Management (PEM) of the different
NetAct tools for the corresponding authorizations to be assigned to users. The
authentication of a user is based on user profile information stored in the system
specific authentication repository.
The following operations are managed by user management:
• Creating, deleting and updating user and login profile
• Creating, deleting and updating a group
• Importing and Exporting users and permissions
• Resetting user passwords
• Configuring password policy
Certification Authority
Certification Authority is the tool used to download the security server CA certificates
used by the tier1 to communicate con NetAct applications (launch NetAct desktop).
Network Element Access Control

Web application used to administer Network Element credentials for the users that
NetAct uses to access Network Elements.
The following figure illustrates the NetAct Applications Categories - Security.
Figure 30: NetAct Applications Categories - Security

Optimization category
The optimization process usually takes place when the monitored performance
drops below the set targets, when a periodical tuning task is to be started or when
there is need to optimize the behavior of new network elements in the network. The
existing network configuration and performance needs to be taken into account
when adding the new elements. Measurements are used for analyzing the network
and service performance development against set targets. A detailed analysis is
performed to find the reasons behind decreased performance and to select the
appropriate corrective actions. In this phase, the relations between performance
indicators and element parameters are analyzed. After the analysis phase, the
configuration parameter settings are optimized and the set quality criteria are
checked. When the corrections are verified and implemented into the network, the
quality monitoring cycle starts from the beginning.
The following applications and tools are used in network optimization with NetAct:
Optimizer NetAct Optimizer is designed for automated,
measurement based optimization of operational GSM,
WCDMA and LTE networks. It provides the functionality
for viewing, analyzing and optimizing the actual network
performance and capacity.
Map Administrator Map Administrator is an administration tool designed for

managing the GIS. Map Administrator is located in the
Administration folder on the NetAct Start Page.
Antenna Data Editor Antenna Data Editor is an Optimizer functionality used for

importing site and antenna relations to the cells and base
stations of the actual network. The tool is run by the
administrator user whenever new sites and antennas and
relations to the cells in the network need to be updated.
Antenna Data Editor supports data import from any
external system producing a CSV (Comma Separated
Values) data input file that complies with the import format
definition.
Configurator The following Configurator applications are used in the
optimization process: CM Analyzer, for running
consistency checks, CM Operations Manager, for
downloading and activating plans and for running
workflow-based optimization operations, CM Editor, for
editing plans and templates, SON Scheduler, for running
scheduled workflow-based optimization operations.
Performance Manager Optimizer uses mobile measurement reports collected by

Performance Manager in interference matrix creation.
The following figure illustrates the NetAct Applications Categories - Optimization.
Figure 31: NetAct Applications Categories - Optimization

Lab exercise: Application Categories

Context
Explain the purpose of NetAct categories groups.
Figure 32: Lab exercise: Application Categories
Procedure
1 Login to NetAct.
2 Navigate to Start Page.
Result of this step

List the NetAct Start Page Categories.
Explain the purpose of each category?
Explain the main functionalities of the following applications. Indicate to which
category they belong to:
• NetAct Monitor
• Performance Manager
• CM Operations Manager
• Online Documentation
• Trace Viewer
• Optimizer
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Managed Objects
Components of Network Topology
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.
Managed Object
A Managed Object (MO) 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.
Every Managed Object belongs to a specific Managed Object Class (MOC) which
defines its characteristics, such as its parameters, operations, notifications and
behavior.
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.
It defines the characteristics of the MO, such as its parameters, operations,
notifications and behavior.
Object Instance
The Object Instance and the associated Managed Object Class of the MO uniquely
identify the MO within its Parent Object.
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.
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.
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

Global Identifier
The Global Identifier (GID) is a number which uniquely identifies a MO in the
Topology. The same MO always has the same GID in any NetAct system.
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.
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).
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.
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.
Figure 33: Managed Objects, Maintenance Regions and Working Sets
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.
You 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.
NetAct users can create own working set. But Maintenance Regions are
created by Administrators.

NetAct User Assistance

Operating Documentation
NetAct operating documentation contains the user assistance needed for the daily
network management operations. The documentation is available on NetAct user
workstations in a browsable format.
The NetAct application Online Helps are available in the same NetAct Operating
Documentation set, and they can be launched via context-sensitive launch from the
NetAct applications.
Browsing the content

1. From Contents frame expand the category by clicking the plus icon or double-
clicking the category name.
2. Click the document name.
The content appears in main frame.
Additional information:
• On the top of Contents frame click Collapse all button to collapse all opened
topics.
• On the top of Contents frame click Link with Contents button to link viewed
content in main frame with related topic in Contents frame.
• On the top of Contents frame click Maximize button to maximize the Contents
frame. Click Restore button to restore the view.
• On the top of main frame click Maximize button to maximize the main frame.
Click Restore button to restore the view.
Searching in the publication

1. Above the Contents frame fill in the Search field with the searched expression.
2. Click Search scope if you want to choose which categories and documents
need to be searched through.
3. Click GO button to run the searching.
The results are displayed in Search results frame.
4. Click on chapter name.
The content appears in the main frame.
You can return to browsing the content by clicking Contents button at the bottom of
Search results frame.
The following figure illustrates the operating documentation.

Figure 34: Operating Documentation
Operating Documentation: Browsing documentation

The following figure illustrates the browsing documentation in operating
documentation.
Figure 35: Browsing Documentation in Operating Documentation
Searching currently browsed content

When browsing the content (publication category) you can quickly run the search.
1. On the top of Contents frame click the Search selected topic and all subtopics
button.
The Search selected topic and all subtopics dialog appears.
2. Type the searched expression.
3. Click OK button to run the searching.
The results are displayed in Search results frame.
4. Click on document or chapter name.
The content appears in main frame.
You can return to browsing the content by clicking Contents button at the bottom of
Search results frame.

Navigating
• On the top of main frame click the Go Back button to return to previously
viewed page.
• On the top of main frame click the Go Forward button to go forward in the
history of viewed pages.
• On the top of main frame click the Home button to go to the top of the
publication.
Adding viewed page to favorites

This instruction is available only for Internet Explorer browser.
• On the top of main frame click the Bookmark Document button.
The Add a Favorite dialog appears.
• Type the name of the bookmark and select its location in favorites folder of your
browser.
• Click Add button.
Results page options

The following figure illustrates the results page options in operating documentation.
Figure 36: Results page options in Operating Documentation

Nokia Online Service

The Nokia Online Service (NOLS) provides easy and secure access to solution and
product documentation, downloadable software, project management tools, online
entry and tracking of Help Desk cases, online ordering, e-learning and collaboration
tools.
The following screenshot displays the NOLS.
Figure 37: NOLS: Nokia Online Services
Product Information Center

The following figure illustrates the features of Product Information Center.
Figure 39: Product Information Center

Online Documentation
The following section describes the online documentation.
Online Documentation: Infocenter and Operating Documentation Library

NetAct operating documentation is available in Infocenter as browsable HTML-
library.
The browser window is divided to two parts: on the left side is the table of contents
which can be used for fast access to any operating document, or part of a
document. On the right side the document itself is visible.
The topics can be opened and searched using:
• The table of contents
• Search functions
The NetAct operating documentation set contains the documents needed for getting
familiar with NetAct and the daily operations. The topics covered include:
• Overviews to NetAct functionality
• Release change documentation
• Operating concepts to network management and NetAct system administration
• Network element integration instructions
• System technical references
• Troubleshooting principles
• Open interface specification
The following screenshot displays the online help.
Figure 40: Online Help
Rich Media in Operating Documentation

HTML-format documentation is accompanied by rich media (Flash) presentations
and sortable tables.
The following screenshot displays the rich media in operating documentation.

Figure 41: Rich Media in Operating Documentation

Object Information Browser

Object Information Browser is a customer documentation browser designed
specifically for browsing of Adaptation metadata information on object classes, and
performance management, configuration management data, and fault management
metadata.
The content in Object Information Browser covers the descriptions of PM
measurements and counters, CM parameters, alarm descriptions, and object
classes for the Adaptations deployed in NetAct.
Information on alarming, measured and configurable (CM) objects is available via
managed object class metadata in Adaptation Information Browser.
Adaptation Information Browser is a Web UI application which is accessed from the
NetAct Start Page. The basic functionality in Adaptation Information Browser
includes:
• Searching by data type (PM, CM, FM, Object Class) and by release, based on
the free text.
• Viewing the description of an individual counter, measurement, parameter, alarm
manual, or object class based on search results, for example, viewing the
description of an individual measurement.
• Browsing counters, measurements, parameters, alarm manuals and object
classes by release or by user-defined criteria and drilling down to details.
• Comparing selected adaptation descriptions, for example, comparing the
descriptions of two measurements, counters, or parameters.
• Exporting to Excel and XML, based on search results.
• Printing of search results.
The following screenshot displays the Object Information Browser.
Figure 42: Object Information Browser OIB
Search functionalities
To search for and browse measurements information:
1. In the main window, click Measurements.
2. Click the drop-down list of Adaptation to choose a specific adaptation. The
corresponding data are displayed in the result panel. If you do not want to
designate a specific adaptation, you can choose all, and use Look for below
directly.

3. Click the drop-down list of Release to choose a version. The corresponding data
are displayed in the result pane below. Again, if you do not want to designate a
specific version, you can choose all.
If you do not choose a specific adaptation in Adaptation, you can not
choose a specific version in Release.
4. Enter the keywords in the search box of Look for, and click Search.
Keywords can be any part of the attributes of the data. To narrow
down the search scope, enter two or more keywords separated by
white-spaces.
The search rules are listed below:
The search supports fuzzy match.
If there is no precisely matched result according to the keyword, items with
similar keywords are displayed. If there is even no similar result, no record is
displayed.
The order of the search results is determined by the priority of the attributes.
For example, you enter two keywords for attributes, one for ID and the other for
Description. As the priority of ID is higher than that of Description, the searched
items for ID are listed above the items for Description.
5. To show more detailed information about the measurements, follow the steps
below:
Click Column settings at right-top of the result panel to choose the information
needed in the drop-down list, and then click Apply.
You can also choose Default to reset the settings as default value.
Click the attribute with hyperlink in ID, and then the details are displayed in a
pop-up dialog box.
Click the attribute with hyperlink in Managed objects, and the detailed
information of the selected item is displayed in the same window.
Click the arrow icon next to the attribute name to view the whole description of
the attribute.
6. To define how many items to show per page, click the drop-down list of items
per page at the right-bottom of the result panel.
7. To export the measurements of the page, follow the steps below:
• Navigate to the page you want to use for exporting.
• Click Export to export the measurements of the current page in a specific
format.
• Choose the format you want in the pop-up box, and then click Export in it.
By default, the exporting is in xml format.
• Save or open the exported data file.
The following screenshot displays the Object Information Browser search.

Figure 43: Object Information Browser Search
The following screenshot displays the managed object browsing in OIB.
Figure 44: Managed Object Browsing in OIB

Lab exercise: NetAct User Assistance (1/2)

Context
1. List the different documentation references in NetAct.
2. Use the Online documentation for searching main NetAct topics.
3. Use the Online Help for searching for specific NetAct Operative procedures.
Figure 45: Lab exercise: NetAct User Assistance (1/2)
Procedure
1 Login to NetAct.
Result of this step

List the applications available in NetAct to provide documentation and
information about NetAct and the supported Network Elements.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 Go to User Assistance Category.
a) Open the Operating Documentation.
Result of this step

List the some of the Main Contents items.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

3 Search for the NetAct Monitor Application and save the corresponding page for
the Overview of this application.
Result of this step

List the steps to do this task.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: NetAct User Assistance (2/2)

Context
Use the Online documentation Rich Media to view videos on concepts and tasks
execution in NetAct.
Figure 46: Lab exercise: NetAct User Assistance (2/2)
Prerequisites
You need to be logged into NetAct and at start page.
Procedure
1 Open the NetAct Monitor application.
a) Go to the menu Help ► Contents and find the corresponding help for using
Network Views.
Result of this step

________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

2 Open the Operating Documentation.
Result of this step

Find a Rich media item to get an overview of the Configuration Management
Operations in NetAct.
Describe the format and content of such overview.
What can be advantages of the Rich Media information compared with the
standard html Online Help?
When would you use of Rich Media and when you use the standard
documentation?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: Object Information Browser

Context
Use the Object Information Browser application to browse, visualize and export
detailed data of the supported network elements in NetAct.
Figure 47: Lab exercise: Object Information Browser
Prerequisites
You need to be logged in to NetAct and at start page.
Procedure
1 Open the Object Information Browser application.
Result of this step

List the types of information about network elements that you can find using this.
Explain how you can find information for certain type and version of network
element.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 Browse the Measurements for the RNC network element and export the
results.
Result of this step

What are the options for exporting the Measurements List.
How can you find the counters that belong of those Measurements using OIB.
Using OIB, find out how many alarms can be received in NetAct Monitor for the
LTE Base Stations.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Summary: Getting started with NetAct

Module Summary
This module covered the following learning objectives:
• Explain the role of the NetAct in the mobile network.
• Describe the NetAct architecture and virtualization concept.
• Access the NetAct start page.
• Describe the main functionalities of NetAct.
• Describe the components of the managed object
• Use NetAct Documentation.


Basic Fault Management with NetAct 71
Basic Fault Management with NetAct

Module Objectives
• Explain how to use Fault Management and Topology based tools.
• Use the Common Desktop within Monitor to arrange a customized user
interface.
• Use the Network Monitor Tools to find problems within the Network and
begin to find a solution to fix them.
• Create reports on the most frequent alarms and the most alarmed network
elements in the network or in a part of it.
Fault Management Basic Concepts

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.
The following figures illustrates the strategies for an effective network monitoring:
Figure 48: Strategies for an effective network monitoring
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.

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.
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.
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
processed by NetAct. This mode can be activated for a managed object or for a
managed object and its subordinate network.

Fault Management events

The following figure illustrates the Fault Management events.
Figure 49: Fault Management events
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.
Alarm Acknowledgement
If an alarm is raised an operator has to acknowledge the error condition to indicate
that appropriate corrective action will be taken.
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 canceled is not possible to have an
accurate and up-to-date view of the network situation.
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 canceled.
Alarm Upload
To ensure consistency of alarm information between the different databases, you
can upload alarms from the network elements to the NetAct Cluster.

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.
Alarm Types
The event type provides more information on the problem that caused the alarm.
The following event types are used in NetAct.
Table 4: Fault Management Alarm Types

Alarm Type Explanation
An alarm that is associated with the procedures and/or
processes which are required to convey information from one
Communication
point to another (for example, loss of frame or call
establishment error)
An alarm that is associated with a condition relating to an
Environmental enclosure in which the equipment resides (for example, door
open or electricity failure)
An alarm that is related to an equipment fault (for example,
Equipment
power problem, receiver failure or I/O device error)
An alarm type that is associated with a software or data
Event processing processing fault (for example, storage capacity problem,
version mismatch, corrupt data, file error or out of memory)
An alarm that is associated with certain degradation in the
Quality of Service quality of service (for example, response time too long,
resource limits near, or congestion)

Defining components of Network Topology

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.
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.
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.
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.
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.
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.
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 DistinguishedName is formed in the NetAct Object Model.
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.
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.
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).
Figure 50: Network Topology, Managed Objects and Distinguished Names
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.
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.
Figure 51: Managed Objects, Maintenance Regions and Working Sets
A managed object can be only in one maintenance region but in many
working sets. Maintenance regions are created by administrators and each
user can create its own working set.

Maintenance Region
Figure 52: Maintenance Region
The features of Maintenance Region (MR) are as follows:
• NetAct has overload protection, whereby drag and drop of MRs having > 10K
objects will not be allowed to avoid DB overload.
• MR View tool is introduced to provide operators a top-down view of MRs.
• Alarm states are aggregated at MR level, operator can drill down to affected
NEs from this top-down view.
The benefits are as follows:
• Easy monitoring of alarm states at MR level- provides maximum alarm severity
and alarm counts/statistics.
• Support all actions on objects associated to the MR.

Knowledge Check: Fault Management Concepts

Find the right answer under the following statement.

Common Operations in NetAct Monitor Desktop

Fault Management System in NetAct
This figure illustrates the Fault Management and topology management in NetAct.
Figure 53: Fault Management and Topology Management in NetAct
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 :
• FM event collection engine
• FM event correlation engine
• FM adaptation fragments
• Mediation interfaces
• FM monitoring tools
Event Collection Engine

It collects and pre-processes 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

It 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.

Monitor Applications
The figure illustrates the NetAct Monitor applications.
Figure 54: NetAct 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.

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.
Figure 55: NetAct Monitor Common Desktop Workspace

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
• 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.
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.
Figure 56: Managing the Workspace
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.
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.
Figure 57: Saving changes in Workspace
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.
When you click the menu item or toolbar button, the workspace configuration
is not saved.
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.
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.
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.
Figure 58: Using the Clipboard and Properties Tool
Sorting in the Properties tool window

1. Right-click anywhere in the Properties tool window. A pop-up menu opens.
2. Sort by category sorts the properties to different categories depending on the
set of properties that can be shown.
3. 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,
1. Right-click anywhere in the Properties tool window
2. Click Show description area.

Using default keyboard shortcuts

Table 5: Using Windows navigation shortcuts 1/2
Keys Command Action
File Menu
Ctrl + P Print Prints the current selection
Ctrl + S Save Saves the changes on the selection
Edit Menu
Ctrl + F Find Finds the required element
Ctrl + X Cut Cuts the element you want to remove
or move to a new location
Ctrl + C Copy Copies the element to a new location
Ctrl + V Paste Pastes the cut or copied element to a
new location
Ctrl + A Select All Selects the entire content of a window
Tools Menu
Ctrl + 1 Properties Opens the Properties Tool
Table 6: Using Windows navigation shortcuts 2/2

Keys Action
Home In Table views, goes to the first field on the current row. In tree
view, goes to the first node.
End In Table views, goes to the last field on the current row. In tree
view, goes to the last node.
Ctrl + Tab Toggles through windows that are collected in a set of tab in the
order that they were last used. To toggle through the tabs, hold
down the Ctrl key and press Tab as many times as required to
reach the tab you want to activate.
Shift + Maximizes the current window or restores a maximized window to
Escape its previous size
Ctrl + W Closes the current tab in the current window. If the window has no
tabs, the whole window is closed
Alt + Right Displays the next tab in the current window
Arrow
Alt + Left Displays the previous tab in the current window
Arrow
Customizing keyboard shortcuts

The figure illustrates customizing keyboard shortcuts.

Figure 59: Customizing keyboard shortcuts
Adding or changing keyboard shortcuts

These instructions are for adding or changing keyboard shortcuts for actions that are
located in the menus of the main window.
1. In the main window, select Tools ► Options.
2. In the bar on the left, click Keymap.
3. Select the action that you are creating a shortcut for.
The actions are grouped according to categories. Some of the categories do not
correspond to the names of the menus in the desktop.
4. Click Add.
In the Add Shortcut dialog, press the keys you want to use for the selected
action.
As you press the key combination, the correct syntax for that combination
automatically appears in the Shortcut text field.
For example, If you press the key, the word Backspace appears. If you
simultaneously hold down the key, the key, and the key, Alt+Ctrl+J appears. The
dialog lets you specify only a keyboard shortcut that is not being used by another
action.
Removing keyboard shortcuts

These instructions are for removing keyboard shortcuts for actions that are located
in the menus of the main window.
Resetting your workspace settings also removes customization from
keyboard shortcuts.
1. In the main window, select Tools ► Options.
2. In the bar on the left, click Keymap.
3. Select the action that is associated with the shortcut you want to remove.
Note that there can be more than one shortcut attached to an action. Select the
correct shortcut to be removed. The first shortcut is selected by default.
4. Click Remove.

Audible Alarms
The figure illustrates the managing Audible Alarms.
Figure 60: Managing Audible Alarms
The Monitor user can configure different alarm sounds for the incoming alarms in the
Alarm List. User can also configure the duration for which the Alarm Sound should
be played.
When two or more alarms are raised, the Alarm Sound is played for all the alarms
that match the criteria in the sound rules configured.
The sound stops when the Alarm Sound is acknowledged.
The following Alarm Sound parameters are available for configuration:
• Type of Sound: Beep, Midi Note and Alarm Tone.
Midi Note and Alarm Tone is supported only in Windows
environment.
• Severity: Critical, Major, Minor
• Alarm Number: Alarm number
• Beep delay: 0-500 ms
• Sound Polling Interval: 10 to 60 seconds

• The Alarm Sound criteria is applicable only to the users who configure
alarm sound settings.
• When the alarm matches both the severity and alarm number criteria,
the sound defined for the alarm number criteria takes precedence.
• The Alarm Sound is not played for alarms if they are not displayed in the
Alarm List due to filtering.
• If the Alarm Sound column is added to the Alarm List, sound icon is
displayed only for the new alarms appearing in the alarm list as part of
polling. Sound icon is not displayed for the alarms that already exists in
the Alarm List even though they match a sound rule.
• Filter Drag and Drop, managed object Drag and Drop, reopening alarm
list or clicking on Show correlated alarms or Hide correlated alarms
button refreshes the Alarm List and removes the sound icon and the
alarm sound.
• When an alarm is canceled, the alarm sound for that alarm stops.
• The Alarm Sound is played only once even if there are multiple alarms
with the same alarm attribute (severity or alarm number) for which the
sound is playing.
Example
When the Alarm Sound is configured for critical, major, and minor alarms, the
following scenarios are applicable:
1. When one critical, one major and one minor alarm is raised (after you configured
the Alarm Sound criteria) and only Alarm Sound for the critical alarm is
acknowledged.
Result: The Alarm List plays only configured sound for both major and minor
alarms.
2. A new critical alarm is raised.
Result: The Alarm List plays sound for the critical alarm. It also continues to
play sound for both major and minor alarms.
3. Alarm Sound for the major alarm is acknowledged.
Result: The Alarm List continues to play the configured critical and minor Alarm
Sound.
For the new changes or settings to be effective, close and reopen all the
Alarm List instances.
Adding Alarm Sound Rule

To add a new Sound Rule, follow the steps mentioned:
1. Log in to NetAct Start Page.
2. To open NetAct Monitor, click Monitoring ► Monitor.
3. Open Options, click Tools ► Options.
4. In the left pane, click Audible Alarm.
5. In the Audible Alarm pane, click Add Sound Rule.

Add Sound Rule dialog opens.

6. From the Alarm Criteria list, select either Severity or Alarm Number.
7. Based on the selected criteria:
a. Select the alarm severity from the Value list.
b. Enter the alarm number in the Value field.
Alarm Number range is from 0 to 2147483647.
8. You can enter multiple alarm numbers separated by comma(,).
For example, 9255, 9633, and so on.
9. Select the type of sound from the Type list.
For example, Beep.
10. To check the Alarm Sound, click Play.
11. Click OK.
12. To set the sound interval, enter the value in Sound Polling Interval field.
13. To save, click OK.
Result: Alarm Sound Rule is defined.
If Alarm Sound Rule is added, Alarm Sound column in Alarm List displays
the speaker icon only if the incoming alarms matches the Alarm Sound Rule.

Lab exercise: NetAct Monitor Desktop

Context
This section tests the students on the following skills:
• Identify the parts of the Monitor desktop.
• Identify the Tools groups.
• Describe the purpose of each Tool group.
• Rearrange the tools in the desktop.
The following figure illustrates the monitor desktop.
Figure 61: NetAct Monitor Desktop

Procedure
1 Identify the different parts of the Graphical User Interface: Menu Tools, Explorer
window (accordingly to selected tool: for example managed object tab ) and
Working Area (Monitoring Desktop).
Result of this step

Which applications groups can you find under the Tools menu?
What is the purpose of each group?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 Open the following tools (if not previously opened): Object Explorer, Alarm
Monitor, Alarm History, Details.
Information
The tools will open in a predefined position into the desktop.
a) Rearrange the position of the tools in the desktop and save the changes in
the workspace.
Result of this step

Describe the procedure.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Monitoring Network
Fault Management workflow
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.
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.
There are a number of common fault management workflows. Fault management
usually begins with routine monitoring and the discovery of a fault or faults in the
system which triggers an alarm or a series of alarms. The workflow example
illustrates a typical monitoring workflow and combines services from different NetAct
Managed Object and Monitoring tools like the Alarm List, Network View, Trouble
Ticket List, Object Explorer, and Trouble Ticket Details.
Alarms are displayed in the Alarm List tool. User can select an alarm from Alarm List
to display the existing trouble tickets for the managed object or the site. The Find
function in the Trouble Ticket List tool provides this output directly from the selected
alarm. To display further object attributes, the user can navigate to the object
properties in Object Explorer. From there they can navigate to views that include the
object and investigate the connectivity or status of the object and environment. After
collecting all the required information, the user can create a new ticket, if needed, or
attach the alarm information to an existing ticket in one single step.
Figure 62: Fault Management workflow

Alarm Monitoring tools

Alarm monitoring is executed by verifying the alarm status of the managed objects,
identifying, prioritizing and processing the new incidents and executing the related
actions in order to solve the faults.
In NetAct, Alarm Monitoring tasks can be executed from two applications. Using the
network views, incoming and existing alarms can be visualized directly on the
symbols of the affected network elements in a summarized way. Using Alarm List,
the active alarms are presented as a table in which each row represents one alarm
received by NetAct and the complete group of alarms provides an instant overview
of alarm status.
With the network views or alarm list, the active alarms are shown instantly as they
appear in the network. The context menu functionalities available in the two
applications (right click pop-up menu in each managed object or alarm) work as a
platform for investigating problems further, providing the operator with the ability to
react immediately.
In the following sections the alarm monitoring via alarm list will be explained in
detail.
Alarm List Monitoring tools

There is a group of applications in NetAct that provide the support for the Alarm
Monitoring using alarm lists:
• Alarm List
• Alarm History
• Warning List
• Alarm Details
• Alarm Filter Explorer
• Rule Explorer
• Rule Analyzer
• FM Pipe Statistics
The access to these applications is provided from the menu Tools ► Monitoring
Desktop or directly from different context menus in other applications.
Managed Objects tools

The Managed Objects (MO) tools allow creation, modification, and management of
network topology data. Managed Objects utilizes the concept of metadata that
defines the types network element objects in the network and their relations. The
MO tools can be used to model managed objects and network topology.
The object data is available in the monitoring tools to support the monitoring process
with the relevant information upon the objects. The desktop includes a set of
integrated tools to administrate and configure the monitored objects.

Figure 63: Alarm Monitoring Tools and Managed Objects Tools

Alarm Monitoring using Alarm Lists

The Alarm List tool gives the user an overview of all alarms that are currently active.
The Alarm List is presented as a table and each row of the table shows one alarm
received by Event Collection Engine.
Alarms are data objects that receive service actions from other tools. By right
clicking an alarm it will be displayed all the actions that are currently possible and
offered by all the tools available. With Alarm List the user can:
• Acknowledge, unacknowledge or clear an alarm
• Create, delete, attach, or query related trouble tickets
• Launch context related external application or element manager
• Navigate to related object information in explorer or views
• Display problem instructions in Alarm Details
• Consolidate using filter or quick filter
• Select the attributes to be displayed and configure row appearance.
• Sort by several attributes
• Manage the maintenance mode of the object
• Request alarm synchronization
It is important that all relevant information for the ongoing task is shown. For this
purpose, the user can adjust the appearance of the table according to his / her
needs.
For a quick search inside the table, the Quick filter feature helps to select any cell of
the table and show only the rows whose column content matches the selected cell.
The Quick search option filters the loaded alarm data for a selected attribute using
symbols like <, >, and <>.
Alarm List can be filtered on a working set by drag and drop of working sets (either
dynamic or static) on Alarm List. Operators like to create working sets with the top
level objects alone and still be able to filter the alarm list such as parent and child
objects alarms are shown. It is possible to configure in Tools ► Options setting
whether drag and drop to Alarm List should also include child objects. The user can
select this option to either include or exclude child objects for filtering the Alarm List.
This is a one-time settings per operator user. This feature does not affect the way
the working sets itself is displayed (by opening the working set) or in correlation
rules, where only the objects which are explicitly part of the working set are
displayed. If there are lot of child objects (greater than 10000) present for the top
level objects of the working sets, the alarm filtering operation may take a long time.
This also causes a heavy load on the database.
Alarm List interacts with other tools. For example, to view the alarms sent by the
selected object, the user can drag a managed object to an open instance of Alarm
List or select a managed object in any other tool and select Find in Alarm List from
the pop-up menu.
From Alarm List, there is also access to actions and services from other tools . For
example, the user can select an alarming object and Find in Network View to open a
list of views containing this alarming or controlling object. To open an existing trouble
ticket, the user can drag the alarm to the Trouble Ticket Details tool.

Figure 64: Monitoring the network using Alarm Lists
Special columns in Alarm List

There are three columns in the Alarm Lists that allows a better visualization of alarm
handling and alarm behavior:
• Instance counter column
• Consecutive Number
• Alarm Insertion Time
Figure 65: Special columns in Alarm List

Alarm Details
The Alarm Details tool helps the user to troubleshoot alarms. It provides a deeper
insight into the details of the alarm that cannot be shown as effective in the table
view of Alarm List.
Because the name of an alarm is often not meaningful enough to fully explain its
origin, the Alarm Details tool explains the sense of each alarm in detail. Additional
parameters like Supplementary Info and Diagnostic Info are detailed, and unclear
value chains are translated to clear text.
For inexperienced personnel, an instructions section explains for each alarm what to
do next with this alarm in order to troubleshoot it.
For correlated alarms, Alarm Details shows the source alarms to the user. The
instructions section can be extended with the user own findings to reflect local
working procedures.
Alarm Details automatically displays the details of every alarm selected in Alarm
List. When Alarm Details is launched within the context of a given alarm, the scope
of the tool remains fixed. It is possible to launch a number of instances of the tool.
With Alarm Details the user can:
• Compare, match and expand alarm fields
• Add or edit user information
• Acknowledge, Un-acknowledge and Cancel alarms
• Drag and drop managed objects
• Delete alarms of an object and its subnetwork
• Upload alarms
• Check active alarms of faulty objects
Figure 66: Alarm Details

Alarm History
The Alarm History tool is used to examine the historical alarm data of one or more
managed objects.
Unlike the Alarm List tool that only shows current (not canceled) alarms, Alarm
History shows all the alarms contained in the FM database that match the given filter
criteria.
The Alarm History tool displays all the alarms including warnings and canceled
alarms contained in the Fault Management (FM) database.
With Alarm History, the user can perform the following tasks:
• Acknowledge, unacknowledge and cancel the alarms
• View Alarm properties
• Perform a quick search for the required alarm
• Filter an Alarm
• Customize the tool
• Apply a quick filter
• Add note for an alarm
In Alarm List, Alarm History and Alarm Details, the user needs authorization rights to
acknowledge, unacknowledge, and cancel an alarm.
Figure 68: Alarm History

101
Warning List
The warnings provide information on temporary error situations or alarms that
indicate potential problems and unusual situations. Unlike problem alarms, warnings
do not have start and end times and are not canceled.
The Warning List tool is used to examine the warnings of one or more managed
objects. The cancel, acknowledge and unacknowledge operations are not available
when the object menu of an object is selected.
The features and the appearance of the Warning List tool correspond to those
described in the Alarm List section.
With Warning List tool, the user can perform the following tasks:
• View properties of a warning
• Perform quick search for a required warning
• Filter an alarm
• Customize the tool
• Apply quick filter
• Add notes for alarm
Figure 69: Warning List

Reconfiguring Alarm and Warning Lists display

The figure illustrates the reconfiguring alarms and warning list display.
Figure 70: Reconfiguring Alarms and Warning List display
Displaying, hiding and reordering columns for Table views

To select which columns to display, click the button just above the scroll bar or right-
click on the header row to open the Select Visible Columns dialog. The Available
Columns list on the left shows hidden columns and the Selected Columns list on the
right shows the columns that are displayed. To display a column, click to select it in
the Available Columns list and then click the arrow button pointing to the right. To
hide a column, click to select it in the Selected Columns list and then click the arrow
button pointing to the left.
To change the order in which columns are displayed, click the column name in the
Available Columns list of the Select Visible Columns dialog and then use the up
and down arrows to the right of the list to adjust the relative position of the column.
In the Table itself, you can also click the column header and drag the column into a
new location.
Sorting data in Tables

To sort data in Tables, click the column header you want to use as sort criterion. The
current sorting criterion is indicated by a small arrow in the column header. The
direction of the arrow in the column header indicates the sort order – up for
ascending and down for descending.
To sort data by using many columns as criteria, hold down the key and click the
column headers in the order that you want sorting to be applied. Your first click is the
primary sort criterion, your second click the secondary and so on.

103
Immediate access to Alarm and Object Tasks from Alarm Lists

Users can launch applications through context-sensitive menus for a selected alarm.
These menus are visible in all the Alarm Lists tools (Alarm List, Alarm History and
Warning List) and provide access to alarm processing tasks, managed objects tasks
and alarm processing for the affected object and managed object tasks and alarm
processing for the controlling object of the affected MO.
Figure 71: Alarm List and Alarm Tasks
Context-sensitive launch
Right-click an alarm and select the desired application either from the shortcut
menu, or from the corresponding submenu (for example, the submenu for Element
Management).
• Fast access to many functions
• Menu adapts to the context
• Menu for alarms, working sets, network elements and so on.

Alarm Monitoring using Network Views

Managed Objects in NetAct can be monitored by using Network Views in the
Network View Tool. The following sections explain how the managed objects are
visualized and the views and the meaning of colors and ornaments in the
corresponding symbols representing the objects.
Hierarchical and scalable views over the entire managed network are visualized in
the Network View tool. The graphical views can be adjusted to the different
monitoring needs from network-wide monitoring to object-level and technology-
specific monitoring. In the upper-level views, users can quickly see the general
situation of the managed network. Moving to a subview shows the alarming objects.
Monitoring Desktop provides a range of monitoring tools that can be accessed from
Network View.
A common concept in network management is to have views to the managed
network that is typically arranged according to the object hierarchy, connectivity, or
other information levels. These views can model either logical or geographical
aspects of the underlying network.
View Explorer visualizes the view hierarchy that has been implemented. It shows the
views in folders that can be used to structure views for a better overview. The View
Explorer tool provides a search facility that can be used to find views for different
aspects, for example for contained managed objects.
You can select a view for manipulation or display the different attributes of the
chosen view in the Properties window. You can also create new folders for new
views or move views from one folder to another.
Network View Tool

The Network View tool provides hierarchical and scalable views over the entire
managed network. The graphical views allow drilling down from a network-wide
overview to the lowest modeled elements. In the upper level views, users can
quickly visualize the general topology of the managed network. The detailed
relationships between objects are shown when moving to a sub-view.
A view contains the following types of view objects:
• A Symbol represents, for example, a managed object, a service, or a grouping
object.
• A Link represents a physical or logical connection between two symbols. Links
do not have any relation to the managed object database.
• Background graphics cover, for example, rectangles, polygons, lines, and text
labels.
Sub-views can be attached to all kinds of view objects. The label of the view object
is displayed similar to a hyperlink.

105
Loading Views in Network View

Context
The following figure illustrates the View Explorer.
Figure 72: View Explorer
The following figure illustrates the View Explorer and Network View.
Figure 73: View Explorer and Network View

You can open a view by selecting it in the View Explorer tool, right-clicking it and
selecting Open in the pop-up menu. The Network View tool starts with a new
instance. The view is loaded into the tool, and the objects contained in the view are
displayed with their states. You can also open views by dragging them from Network

View Explorer to the open Network View tool.
Procedure
1 On the Desktop menu bar, select Tools ► Managed Objects ► View
Explorer.
2 Browse to the view you want to open.
Information
Views are loaded in any one of the following sub-step:
a) Drag the view with the mouse and drop it on the Network View tool.
Information
For this you must have an instance of Network View open.
b) Drag and drop a view onto the currently opened Network View tool.
c) Right-click a view and select Open from the shortcut menu.
d) Double-click a view.
3 You can select several views at once and open them from the shortcut menu.
Information
If a view is already opened in the Desktop, it is brought to the front and not
opened a second time. The Network View opens on the right side of the screen.
Use the Back and Forward buttons on the toolbar to switch between
the views in the same panel.

107
Network Views Monitor Modes

You can view the Network View tool in two modes:
Monitoring mode
Views are constructed from the view objects and represent the monitored network.
In this mode, you can monitor complete state information of the monitored objects.
The tool displays two states:
• Topology state
• Alarm state
In this mode, you can also search for managed objects. Drag and drop managed
object from Object Explorer to network view to view all the network views in which
the object exist. If the managed object does not exist in any view, a message is
displayed.
Edit mode
In the Edit mode, you can modify the views. In this mode the state information is
suppressed.
Edit mode is restricted to some users, requires additional authorization.
When another user modifies the views in the database, a message to reload the
view is displayed and the views are automatically updated.
The tools in the lower toolbar are available only in the Edit mode. In the
toolbar, you can select one tool at a time. By default, deselecting a tool
activates the Select tool and the Move and Resize tool.
Some tools are active only for a single operation and get de-activated
automatically, while others are permanent and hence you must activate a
different tool (usually the Select tool and the Move and Resize tool to switch
it off).
Switching between Monitor and Edit mode

Open the shortcut menu of the tool by right clicking anywhere and selecting Switch
to Edit Mode or Switch to Monitor Mode, depending on the current operation
mode.
When changing a view and switch to Monitor mode, the users are still prompted to
save changes when closing the view.

Figure 74: Network View Window: Switching from Edit to Monitor Mode
Navigating in the view hierarchy

Objects and links in views can be associated with sub-views. This is indicated by
blue labels and a small sub-view indicator shows the aggregated alarm state of the
sub-view.
The labels of view objects with an associated sub-view are blue when they
appear for the first time. However, the labels are pink when the sub-view has
been previously loaded.
You can navigate in view hierarchy in three ways:
1. To open its sub-view, click the label or sub-view indicator of an object. The sub-
view indicator provides a tool tip with the name of the associated view.
2. Use the backward navigation button to return to the previous view. Similarly, use
the forward navigation button to load the sub-view again.
3. Open the shortcut menu of the object having a sub-view and select Open and
view view name.

109
Figure 75: View Tool: Navigating in the View Hierarchy

Network Objects and Topology

Objects are represented by icons in the view. The color and the different virtual
decorations of the icon represent the state of the object. The Network View tool
supports the following states visualized by graphics or color code:
• Alarming State
• Administrative State
• Operational State
• Maintenance Mode
• Trouble Ticket existing
• Note existing
• Subview existing /subview state
Transmission objects can be visualized by different indicators for the transmission
type. Complex transmission networks can be modeled and visualized by network
views supporting efficient management.
Context related actions on objects can be initiated by selecting the objects and then
right-clicking on them. Depending on the tools available for the user, these actions
can include showing all alarms for the object, finding the object in the object
hierarchy, or opening an element manager session to the object.
The colors of the symbols for the network elements change in real time according to
the active alarm situation, that is, the incoming new alarm changes the color of the
symbol indicating the network element and a number can be displayed for amount of
alarms with highest severity. When the fault situation is cleared, the color changes
back to normal.
Alarms are divided into four different severity class, each class is represented by a
specific color on the network element symbol:
• *** Critical (red)
• ** Major (orange)
• * Minor (yellow)
• W Warning (blue)
Figure 76: Network Objects in the Network View

111
Topology view objects
Figure 77: Topology network view
The managed objects are displayed as symbols or links. It is possible to group
objects and use them as anchors for sub-views.
Grouped objects are not managed objects; they only represent, for example,
an office or a transmission equipment in the view.
Symbols
A managed object symbol provides the following information:
• The object class is represented by the symbol itself. If the object has no name,
the relative distinguished name is used. The relative distinguished name has the
form <object class>- <object instance>.
• The object instance is shown on top of the symbol.
Grouped objects are only available as symbols. Grouping symbols are typically

used as anchors of sub-views. They are basically visualized like managed objects,
but with the following differences:
• The symbol is white.
• A symbol has no object instance, so only the name is shown below the symbol.
Links
Links can either be symbolic links, or be associated with a managed object. A link
that is associated with a managed object provides the following information:
• The object class is represented by the symbol in the middle of the link.
• The name of the object is shown below the symbol. If the object has no name,
the relative distinguished name is used. The relative distinguished name has the
form <object class>- <object instance>.
• The object instance is shown on top of the symbol.

Symbolic links can have a label and a type. The icon representing the link type and
the label are both placed at the center of the link. The following link types are
supported:
• Cable
• Leased line
• Microwave
Object states
The object state represents different phases in the life cycle of a managed object. It
shows if the managed object is operational and can be monitored. The object states
are updated automatically and no manual interaction is required.
Table 7: Object states

Object Details Visualization
state
Non- The object is fully constructed in the The default managed
operational database, and represents either a non- object symbol is used.
network object or a managed network Alarms are not shown.
resource that is currently in the disabled
state. The resource is totally inoperable
and unable to provide service to the
user(s). The object exists in the Topology
database, but has no actual value
parameters.
Created The object has been partially The default managed
from constructed from an action initiated by a object symbol is used. The
Network network element. For example, an exclamation mark shows
incoming alarm, performance that maintenance work is
measurement or an upload operation required. Alarms are not
from the network element covering only shown.
a small subset of the object's attributes.
This state indicates that not all attributes
may have been set and that the object
instance may be violating semantic
constraint checks. Typically this is a
temporary state, which will move to
Operational as soon as a complete
synchronization of the object with its
upload agent has been performed.
Operational This state is a fully-constructed object in The default managed
the database, which represents a object symbol is used.
managed network resource that is Alarms are shown.
currently in enabled state according to
CCITT recommendation X.731
Information Technology OSI: The
resource is partially or fully operable.

113
Administrative state
The administrative state indicates whether the object can carry traffic or not. It is
automatically updated in the view. The administrative states of the object are visible
only when the object has AdministrativeStateType attribute defined in the core
adaptation. The following states are supported:
Table 8: Administrative state
Object Details Visualization
state
Locked The resource is administratively Identified by a small pad
prohibited from performing services for lock at the upper left corner
its users. of the managed object
symbol.
Shutting Use of the resource is administratively Identified by a small arrow

Down permitted to existing instances of use at the upper left corner of
only. While the system remains in the managed object symbol.
shutting down state, the manager may at
any time cause the managed object to
revert to the unlocked state.
Unlocked The resource is administratively Not visualized

permitted to perform services for its
users. This is independent of its inherent
operability.
No state Network View tool has no information on Not visualized

available the state of the object.
Operational states
The operational state describes whether or not the object is physically installed and
working, and is able to provide service. The following table describes the operational
states of a managed objects and their visualization.

Table 9: Operational states

Operational Details Visualization
state
Enabled The resource is fully operational and The default managed
available for use object symbol is used
Disabled The resource is unable to provide Identified by a red cross

service to its clients and there is some mark at the upper left
correction required corner of the managed
object symbol.
Maintenance Mode
If your system includes the optional Maintenance mode feature, objects can also be
in the following states:

115
Table 10: Maintenance state

Object state Details Visualization
Maintenance The object from which the Identified by a small indicator in the
Mode Root maintenance mode has been upper right corner of the managed
activated and can be object symbol. When a managed
deactivated object is operational and set to
maintenance, the managed object
symbol is displayed in purple color
Maintenance The object which has been put Identified by a small indicator in the

Mode Child into the maintenance mode as upper right corner of the managed
a part of the subnetwork of object symbol.
Maintenance Mode Root.
Maintenance The object is not under No visualization

Mode Off maintenance
Tool tip and Notes indicator
Figure 78: Tool Tips and Notes
Tool tip
For every managed object in the Network View tool, the Tool tip displays the name
of the object and the following states:
• Additional State Info:
The Tool tip displays this information only if the managed object supports
Resource State.
• Operational State:

Resource State.
• Communication State:
Communication State.
Notes indicator
When the Notes Indicator is switched ON for a managed object, clicking the Notes
Indicator icon displays the latest note added for that managed object in a balloon.
• Notes Indicator ON
The Notes Indicator icon in the middle left corner of the managed object indicates
that the Notes Indicator is switched ON from the Notes tool for the managed object.
When you click on the Notes Indicator icon, the latest note added for the managed
object is displayed in a balloon.
• Notes Indicator OFF
The user cannot view the Notes Indicator icon. This indicates that no note is
available for the managed object.

117
Alarm and Subview States

The alarm states of the managed object can be monitored in the network views.
Alarm state
In each network element the worst-case alarm situation is shown, that is, the
severity of the worst active alarm is displayed. Alarm states are updated
automatically, no manual interaction is required. In the Maintenance mode the
alarms for network elements under maintenance are suppressed.
The table below contains the alarm severity used by Fault Management.
Table 11: Alarm state

Severity Details Visualization
Critical One or more critical (***) Red
alarms active in the object.
Major One or more major (**) Orange
Minor One or more minor (*) Yellow
Unknown Undefined alarm severity. Gray
Indeterminate The system cannot None
determine the current
alarm state.
No Alarms Active The object has no active Not visualized
alarms.
A small sub-view indicator shows the aggregated alarm state of all network
elements in the sub-view (sub-view state). The sub-view state includes alarms from
the whole sub-view hierarchy, that is, from all levels of sub-views.
This allows the construction of a view hierarchy that aggregates the alarm state of
many network elements.
The sub-view indicator uses the same alarm colors as the alarm state, the only
difference being that a sub-view indicator does not blink, but uses bright or dark
colors to visualize new and acknowledged states.
Sub-view states are displayed in a small information icon at the bottom right corner
of the view object. The sub-view state is visualized by changing the color of the sub-
view indicator.
Alarm modes
There are two modes for visualizing the alarm state. These two modes are
applicable only for network elements or any object (including logical devices) which
have their object state as Operational. Network elements which have their object
state as Non-operational or Created from Network will not have any visualization of
the alarm state. The different alarm severity are mapped to certain colors in both
modes. In the Options dialog, the alarm mode can be configured.
The modes differ in visualizing, acknowledged and new alarms:
• Blinking Mode

The network element or any object (including logical devices) in Operational
state blinks in the alarm color when the alarm is new. It stops blinking when all
alarms are acknowledged.
The blinking mode has the advantage of using less space.
Blinking is visible only if the color of the network element and alarm
color is different.
• Balloon Mode
The network element in Operational state displays an alarm balloon showing the
number of alarms of the most critical severity. The severity of the most critical
acknowledged alarm is shown as alarm border around the network element.
The balloon mode has the advantage of providing more detailed information on
the alarm state. It requires less concentration, since the human eye can
distinguish different shapes more easily than different (flashing) colors.
To switch between the two alarm modes, use the monitor desktop Tools ►
Options ► Network View.
Figure 79: Alarm Visualization Modes

119
SingleRAN Site View

Single Radio Access Network (SingleRAN) Site view lists the multi-radio sites
(MRSITE and SRANSITE) and the related objects with a corresponding summary
view of alarm states in a tree-table format.
Single RAN view enables you to view alarm summary at MRSITE or SRANSITE
level. You can also visualize the RF sharing BTSs and the corresponding alarm
summary by expanding the MRSITE or SRANSITE.
The complete hierarchy of BTSs can be viewed by further expanding the MRSITE or
SRANSITE view.
In this view, you can perform:
• Element manager launch
• State management functions
• Open filtered Alarm List, Alarm History, Warning List
• Analyze faults in a RF shared BTSs
The following object parameters are displayed in the site view:
• Objects
The objects parameter consists of MRSITE and SRANSITE objects. MRSITE
objects, BTSs associated to that MRSITE and the containment hierarchy of
BTSs in the tree format. For objects under MRSITE, name of the object is
shown. If the object name is not available, then the relative distinguished name
is shown.
SRANSITE is a logical object which has a one-to-one mapping with
SBTS and is a special case where it does not have a name of its
own. Objects under SRANSITE follow the usual naming convention
(that is, if the object name is not available, then the relative
distinguished name is shown). The Objects parameter in SingleRAN
Site view has the following naming convention:
RDN<Space>[Name]. The MRSITE is displayed as: MRSITE-
mrsiteId [mrsiteName] where mrsiteId is the instance ID of the
MRSITE and mrsiteName is the presentation name of the MRSITE.
The SRANSITE is displayed as: SRANSITE-sbtsId [sbtsName]
where sbtsId is the instance ID of the SBTS mapped to the
SRANSITE and sbtsName is the presentation name of the SBTS.
• Distinguished Name
The fully qualified distinguished name of an object.
• Max Alarm Severity
The highest severity level of any active alarm of the object.
• Critical Alarm Count
The total number of active critical alarms present for the object.
• Major Alarm Count
The total number of active major alarms present for the object.
• Minor Alarm Count
The total number of active minor alarms present for the object.
• Unacknowledged Alarm Count

The total number of active unacknowledged alarms present for the object.
• Operational State
The operational state of the managed object.
• Administrative State
The administrative state of the object after object creation or modification.
• For objects associated to MRSITE, Max Alarm Severity displays the
highest severity of all alarms against the selected object and its children
and the same will be displayed at the MRSITE level.
• In Object Explorer tool, the Find In ► SingleRAN Site View option is
enabled only for objects associated to MRSITE or SBTS.
Figure 80: SingleRAN Site View

121
Site View
Site view lists the sites and the associated objects with a corresponding summary
view of alarm states in a tree-table format. You can expand a site or an object to
view its children and corresponding alarm states. Site view displays the alarm states
of all the associated managed objects and their children for each site in a hierarchy.
The following object parameters are displayed in the site view:
• Objects
• Max Alarm Severity
• Critical Alarm Count
• Major Alarm Count
• Minor Alarm Count
• Unacknowledged Alarm Count
• For objects associated to a site, Max Alarm Severity displays the highest
severity of all alarms against the selected object.
• For a site, Max Alarm Severity displays the highest severity of all alarms
against all the objects of the selected site.
The figure illustrates the site view.
Figure 81: Site View
Finding alarms and objects

• Right-click a site and select Find in to list the alarms related to the site with
Associated Objects and Associated Objects and its SubNetwork. This task can
be performed to find alarms in Alarm List, Alarm History and Warning List.
• Right-click an object and select Find in to list the alarms related to the object.
This task can be performed to find alarms in Alarm List, Alarm History and
Warning List.
• Right-click an object and select Find in to list the object in Object Explorer. This
task can be performed to find objects in Object Explorer and Network View.

Filtering Site View

You can filter the Site View on sites by specifying the filter criteria. In the filter, enter
the site name or relative distinguished name of the site. For example, if the fully
qualified distinguished name of the site is SITEC-1/SITE-1 then the relative
distinguished name is SITE-1.
You can enhance the filter criteria using * and ? wildcard characters.
Refreshing data
Click the icon to view the updated list of managed objects, their children and the
alarm count details associated with a site. If a filter is applied to the site view, the
filtered result is updated upon refreshing.

123
Finding Managed Objects

The Object Explorer tool allows browsing through and configuring the network
topology. It is an integral part of the most workflows involving network topology. The
tool displays network topology in a tree defined by the Object Explorer.
Besides the tree hierarchy, the browser can display the main attributes of the
corresponding objects. The result is a mixture of tree and table display that users
can freely arrange: the content of the table columns to be displayed can be selected
from available attributes, the sequence of the columns can be changed with drag-
and-drop, and the sequence of rows inside one hierarchy level can be sorted. This
feature allows to have all the required information in one view.

Object Explorer
Object Explorer displays the hierarchies of topology objects. Starting from the root
object, the hierarchy can be explored by opening child-level branches of the
underlying tree. In the case of mobile networks, the root object is the Public Land
Mobile Network (PLMN) object. Under this main level there are central objects like
RNCs, MSS, MGW, NT HLR FE network elements. Under these high-level objects,
the corresponding child objects are shown, for example Platform object under NT
HLR FE.
The user needs to expand each node to view the associated child objects. By
default, the arrow mark to expand the tree is shown for all the nodes irrespective of
whether the node has child objects. This is to enable better performance of the
Object Explorer. From the shortcut menu, the user can select context-sensitive
actions for the selected managed objects.
On selecting the object or network element in Object Explorer, the software version
is displayed on top of the Object Explorer windows in the header. This feature
visualizes the full software version of the NE including the Service
Pack/Enhancement Pack information if it is populated in the NE software load. If the
exact version is shown in NetAct Monitor (instead of the base adaptation version),
operators can look up specific troubleshooting hints for the appropriate release
notes version.
The number of child managed objects below a parent object is limited to
10000 objects by default. When the limit is exceeded, only the first 10000
objects received from the database are displayed. An additional node is
added at the end of the child managed objects to indicate that not all objects
are displayed.
In the Tree-Table view, the Object Explorer tool does not support natural sorting of
the managed objects.
With Object Explorer users can perform the following tasks:
• Create objects
• Switch between Tree view and Tree-Table view
• Open notes for a particular managed object
• Navigate to other tools
• Display the object attributes
• Edit the object attributes in the Properties tool
• Upload alarms
• Activate/Deactivate maintenance mode for a managed object and for the
subtree
• Delete all alarms for a managed object and subnetwork
• Select the object attributes in the Tree-Table view
• Drag objects
• Filter objects
With Object Explorer, you can select objects to be used in other tools. For example,
one or more selected objects can be moved with drag-and-drop to the Network View
Editor tool where they are used to model a view, or the objects can be moved to
Alarm List where the objects filter the shown alarms to the corresponding alarms.

125
Figure 82: Object Explorer

Displaying Managed Objects Attributes

Properties
The Properties tool shows detailed information about the attributes of selected
objects and instances. These objects or instances can be managed objects, network
views, rules, or alarms. The tool supports an automatic follow mode. When the
Properties tool is launched from the main menu, it automatically shows the attributes
of any selected instance as user selects them. This way the user instantly get an
overview of all the attributes. The Properties tool can also be launched context-
sensitively from the pop-up menu from a selected object. In this case it keeps the
scope.
The attributes shown in the Properties tool are grouped according to the aspects of
the selected objects. The combination of these aspects depends on the selected
object class.
Attribute values can be edited by selecting the editor button on the right of each
attribute, and multiple selected objects can be modified in one go. Modification of
these values is subject to authorization.
Notes
Working in the network operations is a team exercise. Typically many users work on
the incoming alarms or objects of the network. Coordination and information sharing
between users takes place either by using Trouble Tickets or with the simpler means
of making notes, seen by all users.
The Notes tool enables the user to give comments on managed objects. These
comments will be visible to other users, so that they can easily see that somebody
has been working on a given object.
The notes attached to managed objects work like a logbook, where the user can for
example note down the work that has been carried out during the lifetime of this
object. These log entries can contain any free text. Operators might use these to
track special problems, changed units and so on.
The notes for each object can have many records, where each record is stored with
the username and the time of editing.
Other tools can indicate that a note exists. The Object Explorer tool can show a
column indicating notes and the Network View tool will show a secondary state icon
decoration.
Notes can be attached also to Alarm. Notes Indicator attribute in Alarm List shows if
there exists note for an alarm. Alarm notes are also visible in Notes tool.
You can display the object attributes in three ways:
• Using the Tools menu
• Using the shortcut keys
• Using the shortcut menu
In the Object Explorer window, select an object. To display the object attributes,
select any one of the options:
• On the menu bar of Desktop, select Tools ► Properties. Or
• In the keyboard, press the Ctrl + 1 keys. Or
• In the Object Explorer window, right-click an object and select the Properties
option.

127
The object displays all the attributes. The related attributes are displayed in attribute
groups.
The common attributes of the selected objects are displayed when multiple objects
are selected. When attributes with a common value are selected, then the common
value is displayed.
When attributes with different values are selected, then different values are shown.
When a Managed Object is selected, only the properties of the selected object are
shown.
You can only open one window of the Properties tool at a time.
Figure 83: Object Explorer and Properties tool

Alarm Operations in an Object

Users can perform an alarm operation (for example, acknowledgement) on a
selected managed object and its subtree.
For example, by selecting an object and acknowledging its alarms, then all the
alarms of the object are acknowledged. You can also acknowledge all alarms of a
subtree.
The following alarm operations can be performed from the Object Explorer and View
Explorer:
• Acknowledging all alarms
• Unacknowledging all alarms
• Canceling all alarms
You can perform these operations only if Alarm View, Alarm Operation
permission are given and object is within the Scope (for example, MR or
Site).
Acknowledging / Unacknowledging all alarms of an object or its subtree

The user can select an object and acknowledge (unacknowledge) all alarms of
selected object or its subtree.
Navigate to the managed object using any of the following methods:
• On the Desktop menu bar, select Tools ► Managed Objects ► Object
Explorer. Or
• On the Desktop menu bar, select Tools ► Managed Objects ► View

Explorer.
To view the managed object in view tool, drag and drop a managed object
from object explorer while view tool is set in monitor mode.
The Object Explorer opens with managed objects or View Explorer opens with
available view for an object in view window.
You can acknowledge (un-acknowledge) the alarms using any of the following
methods:
• In the Object Explorer, select an object, right-click and select Acknowledge All
Alarms ► Acknowledge Alarms for Object. Or
• In the view tool, select of an object, right-click and select Acknowledge All
Alarms ► Acknowledge Alarms for Object.
You can also acknowledge all alarms of the subnetwork depending upon the
requirement.
The Confirmation dialog appears. Click Yes to acknowledge all alarms of the
selected object. All alarms of the selected managed object are acknowledged.
Select one object at a time to acknowledge all alarms.

129
If there are no alarms present to process for selected object, the following message
is displayed: No alarms available to process for operation
Acknowledge
Canceling all alarms of an Object

In order to cancel all alarms object and its object tree, navigate to the managed
object using any of the following methods:
• On the Desktop menu bar, select Tools ► Managed Objects ► Object
Explorer. Or
• On the Desktop menu bar, select Tools ► Managed Objects ► View
Explorer.
The Object Explorer opens with managed objects or the View Explorer opens with
the available view for an object in the view window.
The user can cancel the alarms using any of the following methods:
In the Object Explorer, select an object, right-click and select Cancel All Alarms ►
Cancel Alarms for Object. Or
In the view tool, select of an object, right-click and select Cancel All Alarms ►
Cancel Alarms for Object.
The Confirmation dialog appears.
The user can also cancel all alarms of the subnetwork in the previously
mentioned ways depending upon the requirement.
Click Yes to cancel all alarms of the selected object.
Select one object at a time to cancel all alarms.
If there are no alarms present to process for selected object, the message
No alarms available to process for operation Cancel is displayed.
Canceling all alarms of an object takes some time to process the alarms.
This operation is not displayed in progress tracker.
Alarm Operations in an Object

The figure illustrates the alarm operations in an object.

Figure 84: Alarm Operations in an Object

131
Searching for managed objects

Context
Object Search enables you to retrieve managed objects. You can search for
managed objects using Criteriatab. Criteria tab enables you to define a search
criteria for managed objects.
Perform the following steps to search for managed objects:
Procedure
1 Log in to the NetAct Start Page.
2 Click Monitoring ► Monitor.
Result of this step

The Monitor application opens.
3 From the Tools menu, select Managed Objects ► Object Search.
Result of this step

The Object Search appears. By default, Criteria opens.

4 In Criteria, select the checkbox against the attribute based on which you want
to search the objects.
Information
If you select Object Class, the list of attributes displayed varies based on the
selected object class.
a) Select the logical operator (for example, =) for the attribute, if applicable.
Information
• If you select like operator, you can use wildcard characters (% and *) for
multi character match and (? and _) for single character match.
• If special characters (*, ?, _, \) is part of the search criteria itself (name or
DN), then use backslash (\) to escape.
• If you are not escaping backslash ( \ ) character in the above case, the
Object Search tool would do it automatically.
• Special character % is always treated as wild character even if it is part
of the search criteria.
Information
For example:
• If object search is performed using PLMN-TEST/BSC-TEST*TEST\ as the
distinguished name, then the input search criteria should be
PLMN-TEST/BSC-TEST\*TEST\\.
• If object search is performed using PLMN-TEST/BSC-TEST?TEST\ as the
distinguished name, then the input search criteria should be
PLMN-TEST/BSC-TEST\?TEST\\.
5 Enter the appropriate value or select from the drop-down list.

133
Managed Objects List

Managed Object List is a tool, which displays managed objects in form of a table
display. Unlike the Object Explorer tool, the focus is not the orientation inside a
hierarchy, but more the information on selected attributes and states of the network
elements represented by the managed objects.
The health of the network is not only described by the sum of all alarms, which are
displayed in the Alarm List, but also by the operational and administrative state of
the network elements.
The Managed Object List tool display can be adjusted with respect to the attributes
shown in columns of the table. The table can be sorted by any column.
If a user has the task to manage e.g. WCDMA Cell with respect to their
administrative state, the Managed Object List would be configured to show the
administrative state of those objects. Sorting by the column “admin state” would
show object with disturbed state on the top. By applying a filter to the Managed
Object List, the user can restrict his view to show only WCDMA Cell objects. The list
gets updated as states change.
It is possible to monitor any attribute of managed objects using this tool.
Figure 85: Managed Object List

Switching the view mode and selecting columns attributes

You can view the Object Explorer tool in two modes:
• Tree view shows the icons and displays names of managed objects in a Tree
view.
• Tree-Table view extends the Tree view with additional columns showing further
properties of the objects. In this view, you can compare the attributes of objects.
You can switch views in two ways:
• Right-click an object and select Switch View from the shortcut menu.
Or
• Right-click in the background of Object Explorer window and select Switch
View from the shortcut menu.
The selected view mode displays the objects:
• In the Object Explorer, right-click and select Switch view ► Tree-Table.
• To open the Select Visible Columns dialog:
• Right-click the table header.
Or
• Click the Select Visible Columns icon.
Select the desired column attributes.
Duplicate attributes present in different object classes of same or
different adaptation is displayed with adaptation ID, class ID and
release in the Select Visible Columns dialog.
• To confirm your selection, click OK.
Sorting of the managed objects is not supported.
Figure 86: Switching the View Modes and Selecting visible columns

135
Filtering managed object classes

The users can include or exclude managed objects in the Object Explorer based on
the object class.
To open the Object Class Filter dialog use one of the following methods:
• Right-click in the background of the Object Explorer window and select Object
Class Filter from the shortcut menu.
Or
• Right-click an object and select Object Class Filter from the shortcut menu.
Select either Include or Exclude.
In the dialog, select the check-box of the object class to include or exclude the
associated managed objects in the Object Explorer.
• When Show release is selected, the dialog displays object class with
different adaptation releases.
• When Show release is selected, the object class selection applies only to
an adaptation release where the object class is present.
• The parent’s check-box is grayed when a child object is selected. The
grayed check-box of the child indicates that some of the children are
selected.
The Selected Classes pane displays the selected object classes.
To clear the selection, click the Clear Selection button.
Click OK.
If you have selected Include, the Object Explorer displays all the managed objects
corresponding to the object class selected in the Object Class Filter dialog. If you
have selected Exclude , the Object Explorer excludes all the managed objects
corresponding to the object class selected in the Object Class Filter dialog.
If a child class is selected, the Object Explorer displays both parent and child
objects.
By default, the filter is turned off. If the workspace is saved by keeping the
filter on in the previous session, the same is applied during the next log in.
You can turn filter on or off by clicking the filter icon in the Object Explorer.
When the filter is on, the filter icon is highlighted in the Object Explorer and
the following message is displayed: Filter is ON.

Figure 87: Filtering the Object Tree

137
Object Search
The Object Search tool allows performing the following:
• Enter simple filter criteria to retrieve required managed objects in the Criteria
tab.
• Drag and drop managed objects that user can define to view as default
managed objects in the search result. The user can drag and drop the managed
objects in the Objects tab.
• Add advanced filter criteria by entering a SQL query in the Advanced tab.
You can enter the filter criteria for a working set in the Object Search window.
You can open the Object Search window, selecting on the Desktop menu bar,
Tools ► Managed Objects ► Managed Objects.
The Object Search window that appears has three tabs namely which are as
follows:
• Criteria
• Objects
• Advanced
Criteria: This tab displays all the attributes that are used to perform a search.
Specify the search criteria using the available attributes such as Scope, Basic
Object, Managed Object, Modification Attributes, Notes Attributes and Network
Element. For example, you can perform any of the following actions:
• To search for the managed objects that fulfill the search criteria and their
respective child objects, click Include All Children.
• To select the Root, click the custom editor button.
• To select the Object Class, click the custom editor button.
For the desired attribute, select the logical operator from the operator drop-down list.
Objects: This tab is used to drag and drop objects while performing a search. Based
on the selection made, a filter is created while performing a search. Click the
Objects tab, and drag and drop the desired managed objects from the Object
Explorer window.
To select more than 100 objects, save the filter criteria and continue the
search.
Advanced: This tab is used to enter an SQL query and perform a search. To filter the
objects, click the Advanced tab and enter the SQL query where /* edit here
*/ is displayed.
Click Search.

Figure 88: Object Search
The following figure illustrates the adding information and exporting object search
results.
Figure 89: Adding Information and Exporting Object Search results

139
Viewing objects associated with a Maintenance Region or Site

You can view objects associated with a Maintenance Region or Site by using the
Show Associated Objects option in the Object Explorer.
On the Desktop menu bar, select Tools ► Managed Objects ► Object Explorer.
The objects pane lists the managed objects.
Right-click a Maintenance Region or Site, and select Show Associated Objects.
If Maintenance Region is selected, the Object List window displays both managed
objects and NEs associated with the Maintenance Region.
If Site is selected, the Object List window displays the managed objects associated
with the Site.
You can view the following information of managed objects:
• Name
• Maintenance Region
• Site
For more information on the Object List, see About Object List in Object List Help.
The Show Associated Objects option is disabled when multiple Maintenance
Regions or Sites are selected. The Show Associated Objects option is
disabled when objects other than Maintenance Region or Site is selected.
Figure 90: Object Explorer: Showing Associated Objects to a Maintenance

Region

Navigating to other tools

You can navigate to other tools in the Desktop by selecting an object in the Object
Explorer window.
The following are some of the tools which displays various information related to a
selected object:
• Alarm List
• Alarm History
• Warning List
• Network View
To navigate to a tool:
1. Right-click an Object and select Find In.
2. Select the tool you want to open.
Figure 91: Navigating from Object Explorer to Other tools

141
Customize user interface
Figure 92: Customize user interface to show relevant NE types
In NetAct Monitor user interfaces, all the NE types are available where shown
wherever NE type selection was possible. This means, even if NetAct was being
used to manage only a specific domain or technology, all the NE types or object
classes would be visible wherever object selection is possible. This feature makes it
possible for an admin user to specify which object classes/NE types are to be shown
in the various user interfaces of NetAct Monitor. This acts like a filter to show only a
relevant object classes. A text file can be populated with the list of classes that have
to be shown. The following UIs can be filtered out for Object creation wizard:
• Object class filter in Object Explorer
• Rule Editor object class selector
• File Editor object class selector
• Working Set object class selector

Lab exercise: Object Explorer Tool

Context
• Describe the main functionalities of Object Explorer.
• Use Object Explorer for managing network topology.
• Use Object Explorer to find properties of MOs.
Procedure
1 Open Object Explorer tool in Monitor Application.
Result of this step

Describe the main functionalities of Object Explorer and its relationship with
other monitor tools (like Alarms and Warning lists, Working Set Manager,
Network Views).
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

143
2 In the Object Explorer tool, select one of the MOs and open the Properties Pane
for this Object.
Result of this step

Write down the data for the following parameters of the MO:
Object Class:
________________________________________________________
Class Release:
________________________________________________________
Object State:
________________________________________________________
Global ID:
___________________________________________________________
Distinguished Name:
____________________________________________________
Parent Object:
________________________________________________________
3 Create one new Managed Object.
a) List the steps for this task.
Information
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
Result of this step

What is the difference between a root object and a child object in the creation
process?
Use the properties pane to set basic properties for your Managed Object.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

4 Filter the Object Explorer managed objects tree using the Managed Object class
filter.
Result of this step

Which filtering options can you find there?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
5 Switch the tree view of Object Explorer to Tree-table view.
Result of this step

What is the difference between the two view types?
In the Tree-table view, select more columns for visualization and describe the
process.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
6 Insert a note for any Managed Object in the Object Explorer tree.
Result of this step

What tool do you use for that?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

145
Lab exercise: Object Search

Context
• Identify the relationship between Object Search tools.
• Use Object Search to browse the network topology.
• Create Static and Dynamic Working Sets.
Figure 93: Lab exercise: Object Search
Prerequisites
You need to open the Object Search tool in Monitor desktop.

Procedure
1 Export to excel the list of all ONE NDS network elements in the NetAct database
(or any other type of NEs available) whose operational state is "non -
Operational"
Result of this step

List the steps you follow for executing this task.
What is the purpose of Working Sets in NetAct?
How are they related to other Monitor tools?
What is the difference between a static working set and a dynamic working set?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 Create a static working set with all the managed objects in Operational State in
your system.
Result of this step

List the main steps for this task.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

147
3 Create a Dynamic Working Set with all the managed objects in Operational
State in your system.
Result of this step

List the main steps for this task.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: Configuration Database Modification

Context
This section tests the students on configuration database modification.
• Creating an object
• Modification of an object
• Deleting objects
Procedure
1 From the Monitor tool, select the parent object of the object you want to create.
Result of this step

What parameters need to be filled out? Are any optional?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 Using the object you created, right click and select Properties.
a) Click on the bubbles with the 3 dots to change parameters.
Result of this step

Can you modify all of the parameters of this object?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

149
3 Select the object you created in previous step, right click and Delete.
Result of this step

Are there any other tools that allow you to change the configuration database?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: Network Views

Context
• Identify the components in network views.
• Monitor Alarms using Network Views.
• Create and manage Network views.
Procedure
1 Open the View Explorer Tool in Monitor.
Result of this step

What are network views?
What is the usage of network views in NetAct?
What components can you find in a network view?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

151
2 List some of the views already created in the system.
a) Select one of the views and list some of the MOs monitored in that view.
Result of this step

How can you identify the alarm status of the objects in the views?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
3 Switch the alarm mode visualization for the Network Views (balloons of
blinking).
Result of this step

What tool in Monitor do you use for that?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
4 Create a new view.
a) Select in the "Views" window and navigate to New ► View. Enter the name
and press Finish.
b) Select a MO in the "Objects" window and drag it to view.
c) Identify the additional visual configuration you can add to the view: text,
background images, lines, geometrical figures, and so on. Reconfigure for
example colors for background and text, icons alignment and so on.
d) Create another view to be linked to the first one as a subview.
Information
Select the background in the new view and select with the right mouse button
Switch to Monitor Mode. The actual alarm status for the MOs in the view is
uploaded.
Result of this step

________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: Alarm Lists and Warning Lists

Context
• Use the Alarm List.
• Use of Alarm History.
• Use of Warning List for network monitoring.
Procedure
1 Open Alarm List, Alarm History and Warning List tools.
Result of this step

What is the purpose of each of the Alarm and Warning lists?
What are the differences among them?
What tasks can you execute in an Alarm in Alarm List or Alarm History List?
See the context menu for the alarm.
What information can you find in the Alarm Details?
Explain how to change the order of column presentation. How can you change
the number of columns you want to see in your Alarm List?
Test changing the corresponding order and selecting different configurations for
columns presentation for example using sorting functionality. Export the current
alarm list.
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

153
2 Create and activate an Alarm Filter in Alarm List for all critical and major alarms
for the last 24 hours.
Result of this step

List the steps for this task.
How can you filter the Alarm List using the Object Explorer or Working Set
tools?
What is the result?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Alarm Statistics Reporting

Alarm Reports Dashboard
Alarm Reports Dashboard enables detecting, storing the failures in the network, and
scheduling the report generation. It is for collecting and storing real-time information
from the network to detect and analyze faults in most alarming network elements
and for monitoring the quality of service provided by the network.
With Alarm Reports Dashboard, you can get the report of indicated alarm reports in
a specific duration. After logging in Alarm Reports Dashboard from NetAct Start
Page, in menu bar, you can access the following graphical user interfaces:
• Search Alarms
• Schedule Search
• Schedule Task Report
Figure 94: Alarm Reports Dashboard

155
Alarm Reports Dashboard Configuration

Context
This function is for defining the time period to keep the search results and reports
data in system cache. After the defined time period, system cleans the data in cache
automatically.
Using system cache to save the data improves the system performance, and saves
the time for daily report generation.
The figure illustrates the configuration.
Figure 95: Configuration
To define the configuration for Alarm Reports Dashboard, perform the following
steps:
Procedure
1 On View Reports, on top of menu bar, click Configuration.
Result of this step

Configuration opens as a pop-up window.

2 On Configuration, select the check box if you want to store the defined alarm
search result in system cache.
Information
When Alarm Report Dashboard gets the same defined search criteria, this
option helps to save the time and system load for getting the search result in
cache instead of system database.
3 Change the interval for cache clean.
Information
In the combo box of Clean cache every, you can enter a specific number, or
click the scroll button of the combo box to change the number.
In the corresponding drop-down list, select the dedicated time type as needed,
and there are three options: days, weeks, and months.
4 Change the interval for report data clean.
Information
In the combo box of Clean report data every, you can enter a specific number, or
click the scroll button of the combo box to change the number.
In the corresponding drop-down list, select the dedicated time type as needed,
and there are three options: days, weeks and months.

157
Search Alarms
Context
The figure illustrates the searching alarms: Most Frequent Alarms or Most Alarming
NEs.
Figure 96: Searching Alarms: Most Frequent Alarms or Most Alarming NEs
To get the most frequent alarms in NetAct with Alarm Reports Dashboard, perform
the following steps:
Procedure
1 On Search Alarms, in the drop-down list of Search type, select
Most frequent alarms.

2 In Search Period, define a specific period.
Information
There are three options:
• Today provides you the duration from last midnight to the midnight of today.
• The second option provides you a dedicated duration.
You can choose the specific time by clicking the calendar icon next to the
fill-in box of From and To.
• The third option provides you the relative duration.
You can choose a specific length (days, or weeks) to be the relative
duration, and define the end time of the duration.
The maximum duration is 180 days.
3 Under Alarm Properties, in Alarms numbers, enter the specific numbers. Use

comma to separate the numbers.
4 In Alarm text, enter the specific alarm text.
5 In Supplementary information, enter the specific information.
6 In the drop-down list of Alarm Class, select a specific alarm class.
Information
There are six severity levels: All, Critical Alarms, Major Alarms, Minor Alarms,
Alarms Only, and Warnings Only.
7 In the drop-down list of Alarm type, select a specific type.
Information
There are five alarm types: All, Communication, Equipment, Processing, and
Quality of Service.
8 In Managed Objects, define the specific managed objects.
Information
There are four options for defining the managed objects: All Managed Objects,
Select managed objects, Distinguished Name, and Global IDs.
All Managed Objects is for collecting data from all the existing managed objects.
Select managed objects is for selecting specific managed objects as needed.
9 Under Alarm Filters, in the drop-down list of Maximum amount of results,

select a dedicated range.
10 In the drop-down list of Alarms in total, select the dedicated range. In the drop-
down list of Mark, set a boundary for displaying the search result. The result,
which is over the boundary, is marked in red while displaying.

159
11 Click Search to start a search based on the defined criteria.
Result of this step

Search Result opens, and shows the search result. To reset the search criteria,
click Reset.

Search Result
Search result shows the result after clicking Search on Search Alarms.
When searching for the most frequent alarms, the search result consists of alarm
class, alarm number, alarm text, NE count, percentage, and 28_days. The following
list gives you explanation on each item:
• ALARM_CLASS shows the severity of the alarm.
• ALARM_NUMBER shows the unique numeric identifier of the alarm.
• ALARM_TEXT shows all textuary alarm information sent by Fault Management
Pipe.
• ALARM_COUNT shows the occurrence of the alarm stored in system database.
• NE_COUNT shows the amount of the network elements which triggered the
alarm.
• PERCENTAGE shows the proportion of the alarm to the amount of all alarms
listed on current page.
• 28_DAYS shows the occurrence of the alarm stored in system database in past
28 days.
When searching for the most alarm network elements, the search result consists of
object name, global id, alarm count, critical, major, minor, and 28_days. The
following list gives you explanation on each item:
• OBJECT_NAME shows the name of the network element.
• GLOBAL_ID shows the global id of the network element.
• ALARM_COUNT shows the amount of alarms triggered by the network element.
• CRITICAL shows the amount of critical alarms triggered by the network element.
• MAJOR shows the amount of major alarms triggered by the network element.
• MINOR shows the amount of minor alarms triggered by the network element.
• 28_DAYS shows the amount of alarms triggered by the network element, and
stored in system database in past 28 days.
On Search result, you can get the detailed result analysis by clicking the
corresponding item.
The available result analysis are marked in blue. Once you click any of the blue
analysis, Alarms Drill Down opens.
Alarms Drill Down shows the detailed result with a chart. According to the chart,
you can get the macroscopic view of the network elements’ performance, or the
most frequent alarms’ frequency.
On top of Search result, there are two options for exporting the search result:
• Export Excel
• Export CVS
To export the search result, click the corresponding icon to choose the format you
want to export, and then choose the directory where you want to save.

161
Figure 97: Search Results

Scheduling Task List

Under Schedule Search, on Schedule Task List, you can get an overview of all
existing schedule tasks.
The schedule task is for predefining search criterion and indicated search time. It is
essential for system performance management. For instance, you can define a
specific reporting duration, and make the schedule task work at midnight to avoid
the impacts from abnormal performance. Once the search task starts, the
corresponding search result is available on Schedule Task Report, and you can get
the result by clicking the task name on Schedule Task List.
On Schedule Task List, you can access the indicated functions by clicking the
corresponding buttons:
• New is for creating a new schedule task.
• Edit is for modifying the existing schedule task.
• Delete is for deleting the existing schedule task.
• Activate is for activating a defined schedule task.
• Deactivate is for deactivating an activated schedule task.
• Refresh is for refreshing Schedule Task List to get the latest schedule task data.
Schedule Task Report

Schedule task report lists all the real-time reports generated for the corresponding
scheduled search tasks. There are two pages to show you dedicated information.
On schedule Task report ► All tasks, it shows you the general information of all
existing reports, such as Task name, Created on, and Search criteria. In Task name
column, you can get the dedicated report by entering a specific task name to the
empty text box. Also, you can click the corresponding creation time of the search
task to get the detailed report.
Figure 98: Schedule Search and Schedule Task Report

163
Lab exercise: Alarm Report Dashboard

Context
This section tests the students on alarm report dashboard.
• Most frequent alarms
• Drill down
• Most Alarming Network Element
• Filters
Figure 99: Lab exercise: Alarm Report Dashboard
Prerequisites
You need to be logged in to NetAct and at start page.
Procedure
1 Open the Alarm report Dashboard and create a report of the top 20

Most frequent alarms in the network for the past week.
Result of this step

What alarm is the most frequent?
Keep that report and run another report for today. Has anything changed?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

2 Click on the most frequent alarm blue link by refering at both reports.
Result of this step

What object has the most alarms?
Is it the same object on both reports? When did the problem start?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
3 Run a most alarming NE report for the top 20 problems for the last week by
refering to the objects were shown in the previous reports.
a) Run one report for the today.
Result of this step

Do these reports match the information you got from the other reports?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
4 Run a report using any of the filters, maintenance region, severity, MO class.
Result of this step

How does this help isolate what and where the problem is?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

165
Summary: Basic Fault Management

Module Summary
• Explain how to use Fault Management and Topology based tools.
• Use the Common Desktop within Monitor to arrange a customized user
interface.
• Use the NetAct Monitor Tools to find problems within the Network and begin to
find a solution to fix them.
• Create reports on the most frequent alarms and the most alarmed network
elements in the network or in a part of it.


Advanced Fault Management with NetAct
167

Module Objectives
• Manage the alarm processing using alarm filtering and alarm reduction in
NetAct.
• Manage the NetAct Topology.
• Verify Fault Management pipe status.
• Perform alarm database upload.
• Perform alarm deletion for a MO.
Alarm Filtering and Reduction of Alarm Flow

Alarm flow reduction in NetAct
If no alarm reduction techniques are implemented, network monitoring becomes a
reactive process, where an immense flow of alarms arrive in NetAct from all parts of
the network. This reactive job includes:
• Filtering the enormous amount of information that is presented by alarms.
• Deciding which of the thousands of alarms that are visible in the alarm handling
applications are important.
• Making correlations between alarms, trying to decide which of them are caused
by the same original fault, and grouping those alarms together.
• Finding solutions for the problems that cause the alarms.
These daily activities require constant and intensive attention in network monitoring.
If strategic decisions have to be made under pressure, the risk is high that service
affecting faults remain unnoticed or unresolved, which results in a decrease in the
quality of service. Additionally, the immense flow of alarms to monitoring can set a
heavy load on the network capacity.
Alarm reduction with the NetAct tools include filtering unnecessary alarms and
correlating alarms so that only one alarm indicating the actual network fault is visible
in network monitoring. The hidden alarms can still be retrieved from the database for
closer inspection of the fault when needed.
Selecting the correct alarm reduction technique

Different alarm reduction techniques can be implemented depending on the
situation. The goal in reducing the number of alarms in the network can be either of
the following:
• Preventing alarms that are raised because of maintenance work from being
shown in the network monitoring application
• Correlating alarms that are all related to the same fault, so that one fault results
in one alarm in network monitoring
• Assigning a higher or lower priority to a particular alarm, depending on its effect
on the level of service
• Reducing the Alarm load on NetAct Database using Alarm Filtering
When selecting an alarm reduction technique that is feasible for a particular need,
consider the following:

• Can the alarm be filtered from the NetAct database, or can it be filtered only
from the NetAct alarm monitoring applications? Is it feasible to use local alarm
blocking in the network element?
• If the alarm cannot be filtered out, can it be suppressed by a primary alarm? Is it
enough to have only one primary alarm, or does the secondary alarm has to be
suppressed by two or more primary alarms?
Implementing feasible alarm reduction techniques

After selecting the correct alarm reduction technique accordingly to the analysis
before, the NetAct applications should be applied effectively for reducing the flow of
alarms in network monitoring with the corresponding reduction methods.
The type of alarm reduction techniques that are most feasible in each
network depend on the actual network situation.
The alarm reduction techniques offered by NetAct applications are:
• Reducing alarms caused by network maintenance
• Using Informing Delay for transitory alarms
• Using Alarm Filtering to reduce load on NetAct database
• Creating effective correlation rules
Alarm flow reduction techniques

The following figure illustrates the alarm flow reduction techniques in NetAct:
Figure 100: Alarm flow reduction techniques
Except for Maintenance mode, all the others are defined using Rule Explorer.

169
Maintenance Mode
When some maintenance work or network element integration is performed in the
network and some network functions are therefore temporarily non-operational, a lot
of unnecessary and irrelevant alarms are raised. Before starting the maintenance
work, the operator can exclude the network elements from monitoring so that the
maintenance alarms are not visible among the live network alarms in the NetAct
monitoring applications.
Maintenance is a state of the managed object. In the Alarm tools (Alarm List,
Alarm History, Warning List) and Object Explorer is possible to change the
managed object state with the following operations:
• Set under Maintenance:
Sets the managed object to maintenance, that is, new alarms from the managed
objects are discarded by the Fault Management (FM) platform.
• Set Subtree under Maintenance:
Sets the managed object and its children to maintenance.
• Resume Monitoring:
The managed object and children are removed from the maintenance state and
Alarm upload will be triggered automatically. If the associated children are not
set to maintenance, only managed object is removed from the maintenance
state.
From the same menus, you can select either Set under Maintenance or

Set subtree under maintenance.
The Maintenance mode for a managed object and its subtree can be activated from
the Alarm Tools (Alarm List, Alarm History, Warning List) or Object Explorer.
• From Alarm Tools (Alarm List, Alarm History, Warning List):
1. Right-click an Alarm and select Alarming Object ► Maintenance ► Set
under Maintenance.
Alternatively, Right-click an Alarm and select Controlling Object ►
Maintenance ► Set under Maintenance.
2. Right-click a Managed Object and select Maintenance ► Set under
Maintenance from Object Explorer.
The alarming object, controlling object or managing object is now set under
maintenance.
When a managed object is under maintenance, workstation alarm
9251 is raised with the text Network Element Under Maintenance.
The status of the managed object under maintenance is set to NE
under Maintenance state. The status of a managed object under
maintenance can be accessed from the Properties tool under
Maintenance Mode Attributes.

Figure 101: Maintenance Mode
Resume Monitoring
The following figure illustrates resuming from Maintenance mode:
Do not forget to resume monitoring after the maintenance is completed.
Figure 102: Resuming from Maintenance Mode
Automated Maintenance Mode during NE software upgrade

The automatic maintenance mode can be triggered directly from Software Manager
tool. When the operator selects in the software manager which Network Elements
he will update, he can select also how long he will set these Networks elements in
Maintenance Mode, for example, 4 hours. Therefore he does not need to resume
the maintenance mode after the software update, it is resumed automatically after
the maintenance period ended, in this case 4 hours.

171
Alarm filtering
Alarm Filter Explorer and Alarm Filter Editor are the tools used to manage alarm
filters. Users can create filters with different filter criteria for Alarm lists.
The default Filter folder in explorer contains all alarm related filters. Users can add
the folders to default Filters folder.
With Alarm Filter Explorer the user can:
• Create new filters
• Rename filters
• Delete filters
• Create new folders
• Drag and drop a filter
• Import/Export filter
• Set or unset a filter as a default filter
• Display filter properties
Figure 103: Alarm Filter Editor and Alarm Filter Explorer
Creating an Alarm Filter

Filters can be created using different filter criteria. When the user applies an alarm
filter to any of the Alarm Tools, the alarms matching the filter criteria are displayed.
Filters are created by setting different conditions (using the operators). For example,
the user can create a filter which lists only the Critical Alarms.
To create a new filter:
1. Open the Alarm Filter Explorer Tool and Right-click the Filters folder and
select New Filter. The New Alarm Filter window opens.
2. Enter the name of the filter and click Finish. A new Alarm filter is created. You
can edit the filter attributes in Alarm Filter Editor.
While naming a filter, special characters (*, | , \ , / , :, ", <, > and ?) are not
allowed.
Filter name should not exceed 256 characters.

You can create a filter if you have Create permission. To create an alarm
filter with filtering criteria, the user should have Modify and Create
permissions. Else, an empty filter without any filtering criteria is created.
If the user do not have any permission, the option New Alarm Filter is
disabled when you right-click on default Filters folder.
Configuring the filter conditions with Alarm Filter Editor

After creation of filter with Alarm Filter Explorer, the Alarm Filter Editor is opened in
the New Filter Window ready to define the filter condition. A filter condition has three
parts:
• Name of filter condition
• Operator, for example, '='
• Parameter(s)
To define the filter condition in the Alarm Filter Editor, right-click the Alarm pattern
and select a filter condition.
A pattern is a list of conditions. Within a pattern the conditions are connected
by AND operator, and patterns are connected by OR operator. An alarm
matches the filter only if all conditions of the pattern are fulfilled. Alarm
pattern is added by default when a filter is created.
In the Operator drop-down list, select an operator. Table gives the list of operators
that you can use to define filter conditions.
Edit a filter condition based on the type of editor.
• While defining an alarm pattern, either the Distinguished Name or the
Working Set Name can be used. Both cannot be used together.
• In the pop-up menu, the attribute names are displayed in the same order
as in the relevant Properties tool.
From the File menu, select Save.
A filter can be saved even if one or more fields are invalid, but if the filter is
applied, then it gives an error message.

173
Figure 104: Creating an Alarm Filter
Activating a filter in alarm or Warning Lists

The following figure illustrates the activation of an alarm filter:
Figure 105: Activating an alarm filter
In order to activate a filter in any of the Alarm or Warning lists there are several
options:
Drag and drop or copy and paste of a filter

From the Alarm Filter Explorer tool, drag the previously created filter on any Alarm
Tools (Alarm List, Alarm History or Warning List).
It is also possible to copy and paste a filter from the Alarm Filter Explorer to Alarm
tools in order to activate the filter.
You cannot drag and drop a filter if the Alarm List is locked.
Setting a filter as default filter

When a filter has been set as a default filter, when opening any Alarm tool (Alarm
List, Alarm History or Warning List), the filter is automatically applied. The filter name
is shown as the active filter.

To configure a previously created filter as a default filter, open the Alarm Filter
Explorer tool, right-click the filter and select the option Set as Alarm Tool default
filter.
There can be only one default filter. Any previous filter setting is replaced by
the new setting. If the option is selected again, the check mark is removed
and the filter no longer exists as the default filter.
Drag and drop (or copy and paste) a Selected Managed Object, a group of
selected Managed Objects
From the Object Explorer tool, drag the Managed Object, group of selected
managed Object on any Alarm Tools (Alarm List, Alarm History or Warning List).
It is also possible to copy and paste a filter from the Object Explorer to Alarm tools in
order to activate the filter.

175
Create Rules with Rule Editor

Rule Editor allows modifying the rule contents and properties. Based on the
definition given to a particular alarm, actions are performed.
Rule Editor structures each rule in a condition and an action part. The condition
can be a combination of alarm parameters that, when they match, trigger the action
part of the rule. Alarm conditions can be expressed in a flexible way so that lists of
values or wild card expressions are possible. Regular expression support enables
flexible and sophisticated rule design.
The correlation outcome is visible in the Alarm List tool where correlated alarms are
indicated with a symbol. Drilling down into the correlation raw alarms is possible in
the Alarm Details tool that shows the input alarms and also allows their direct
treatment as alarm objects.
With Rule Editor you can perform the following tasks:
• Add alarm definitions
• Apply relation conditions
• Add alarm actions
• Add schedule definitions to rules
Summary: The Alarm definitions and the Relation Conditions define the general
condition for the rule. The Alarm Actions define the Action part of the rule. Optionally
the Scheduling define the active times for the alarm.
Figure 106: Create rules with rule editor
Rule Explorer and Rule Editor

Rule Explorer provides hierarchical structure for managing larger amount of rules in
the form of multilevel folders. A folder in Rule Explorer is a container of multiple
rules. It is possible to create different folders that can contain groups of rules.
The Rule Explorer shows the alarm processing and correlation rules that are
currently available. The rules are arranged in folders for a better overview. You can
activate and deactivate rules within Rule Explorer.
The Rule Editor tool is used to create, modify and schedule rules.

Rule Editor structures each rule in a condition and an action part. The condition
can be a combination of alarm parameters that, when they match, trigger the action
part of the rule. Alarm conditions can be expressed in a flexible way so that lists of
values or wild card expressions are possible. Regular expression support enables
flexible and sophisticated rule design.
The correlation outcome is visible in the Alarm List tool where correlated alarms are
indicated with a symbol. Drilling down into the correlation raw alarms is possible in
the Alarm Details tool that shows the input alarms and also allows their direct
treatment as alarm objects.
Start with: Tools ► Monitoring Desktop ► Rule Explorer
Figure 107: Rule Explorer and Rule Editor
Managing Rules
The following figure illustrates the managing rules.

177
Figure 108: Managing Rules
Creating Rule Folders
1. Right-click Rule Explorer and select New ► Folder.

New Folder window opens.
Creating a rule
A rule is a generic template from which you can create any kind of alarm rule. The
procedure for creating a rule is as follows:
1. Right-click any second level folder and select New ► Rule.
2. In New Rule window, enter the Rule name in the Name field.
a. In Select Parent Folder, select the parent folder.
b. Click Select to save the parent folder.
c. Click Finish to create the rule under the parent folder.
While naming a rule, special characters such as *, |, \, /, :, ", <, > and ? are
not allowed. Rule name should not exceed 256 characters.
Changing the Rule mode

Rule mode represents the current state of a rule. There are two rule modes:
• Active

In the active mode, the rule is applied when a matching is generated in the
network. When a rule mode changes to Active, the rule name changes to purple
color with boldface.
When a rule is active, is not possible to edit the rule properties. The
rule editor opens in “Read Only” mode and editable fields remain
grayed out.
Active rule cannot be deleted.
• Inactive
In the inactive mode, the rule is just present and not applied. Inactive rule is
represented by grey color.
To change the rule mode:
1. Right-click a rule and select Change Mode.
2. To activate a rule, select Active.
To deactivate a rule, select Inactive.
It is possible to activate/deactivate all the rules present in a folder.
Right-click a desired Rule folder and select Activate all
rules/Deactivate all rules. If both active and inactive rules are present
in Rule folder, the user can select either Activate all rules or
Deactivate all rules depending on requirement.
Users can also activate/deactivate multiple rules. Select the desired
rules to activate/deactivate. If the selection contains combination of
activated and deactivated rules, then both activate and deactivate
options are enabled. Depending upon the selected option, relevant
rules are activated /deactivated.
Exporting Rules
Exporting rules helps to store the rule definitions in a secondary storage area. This
helps to prevent unnecessary recreation of the same rules in the new installation
site.
1. Right-click a rule and select Export Rule.
Save dialog opens.
2. Select the appropriate directory.
3. In the File name text field, enter the rule name.
While renaming a rule, special characters such as * (Asterisk), Pipe
(vertical bar), \ (Back slash), / (Forward slash), : (Colon), " (Quote),
<( Less than), > (Greater than) and ? (Question mark) are not
allowed.
Rule name should not exceed 256 characters.
Rename dialog opens.
4. Click Save.
Importing rules
This section describes the procedure for importing rules.

179
1. Right-click the target folder and select Import Rule.
A file selection dialog opens.
2. Navigate to the appropriate rule folder and select the rules. To select multiple
rules, press either Shift or Ctrl key.
3. Click Open.

Alarm Correlation
In a network, one fault generates multiple alarms. Even though all the alarms are
visible in the Alarm List, it is difficult to identify the real fault in the network.
Alarms that are associated with each other are correlated and as a result of this,
only fewer alarms are visible in the Alarm List.
You can define the following correlation rules using Rule Editor and Rule Explorer:
• Compression Rule
• Suppression Rule
• Count Rule
The following screenshot displays the Correlated Rules:
Figure 109: Correlated Rules
The correlating alarm is indicated by bell icon in correlation indicator field of
Alarm List.

181
Grouping types
For Correlation Rules four Grouping types are defined:
Single MO, Single Alarm Number

Alarms received from same object with same Alarm number are correlated.
Only the alarm arrived first is displayed after Hide Correlated Alarms (severity
independent).
The following figure illustrates the Single MO, Single Alarm Number:
Figure 110: Single MO, Single Alarm Number
Single MO, Multiple Alarm Number

A fault in a single monitoring object (for example, be1), produces multiple alarms
(and therefore multiple alarm numbers). Only the alarm arrived first is displayed after
Hide Correlated Alarms (severity independent).
The following figure illustrates the Single MO, Multiple Alarm Number:
Figure 111: Single MO, Multiple Alarm Number
Multiple MO, Single Alarm Number

Alarms with the same alarm number generated from different network elements (for
example, be1 and be2) are grouped and compressed.
independent).
The following figure illustrates the Multiple MO, Single Alarm Number:

Figure 112: Multiple MO, Single Alarm Number (1/2)
Single alarm number 35173 for multiple MO (be1, be2 and be3).
The following figure illustrates the Multiple MO, Single Alarm Number (2/2):
Figure 113: Multiple MO, Single Alarm Number (2/2)
Multiple MO, Multiple Alarm Number

Alarms with different alarm numbers generated from different network elements are
grouped and compressed.
independent).
The following figure illustrates the Multiple MO, Multiple Alarm Number:

183
Figure 114: Multiple MO, Multiple Alarm Number
Figure 115: Alarm details and correlated alarms

Creating Rules
The following are the types of creating rules:
• Compression Rule
• Count Rule
• Toggle Rule
• Threshold Rule
• Informing Delay Rule
• Reclassification Rule
• Suppression Rule
• Filtering Rule
• Trigger Rule
• AutoAck Rule
• AckWithCancel Rule
• ForwardAlarmToEmail Rule

185
Compression Rule
Sometimes a single fault generates a series of occurrences of the same alarm. But,
after the first one, none of the other occurrences provide any extra information on
the fault. In such cases, create a Compression Rule.
During Compression, any number of occurrences of the same alarm are grouped
under one correlating alarm. You can see only one alarm, despite the multiple
occurrences of the alarm.
Figure 116: Compression Rule flow
Figure 117: Compression Rule

For Alarm Number you can use:
• comma (,) as a separator for adding multiple values.
• hyphen (-) for a adding a range of values.
• both comma (,) and hyphen (-).
Figure 118: Compression Rule (correlated)

187
Count Rule
Certain alarms are not so important if they occur once or twice, but they become
important if they occur repeatedly in a short time period. A count condition can be
applied to this type of alarm. If there are enough occurrences of an alarm in a
certain time frame, it generates a new alarm with a user definable number.
The following figure illustrates the Count Rule flow:
Figure 119: Count Rule flow
The following screenshot displays the Count Rule:
Figure 120: Count Rule
The following screenshot displays the Correlated Count Rule:

Figure 121: Correlated Count Rule

189
Toggle Rule
Toggle Rule enables you to filter toggling alarms from Alarm List. If an alarm is
raised and cancelled more often than a specified period of time, it goes to toggle
state.
In the toggle state, further alarm repetitions are filtered as long as the alarm toggles,
and appear in Alarm History. However, the toggled alarm is displayed for a longer
time to gain operator attention.
The display stops if the alarm does not toggle further.
The following figure illustrates the Toggle Rule flow:
Figure 122: Toggle Rule flow
In this example, the alarm cancel is delayed for 60 seconds. and displayed as active
during the time. Setting period starts after the 3rd toggle.
The following screenshot displays the Toggle Rule:

Figure 123: Toggle Rule

191
Threshold Rule
Threshold Rule filters an alarm which arrives at least a user-configurable number of
times within a user-configurable time interval.
Original alarms are not displayed until it occurred threshold times.
The following figure illustrates the Threshold Rule flow:
Figure 124: Threshold Rule flow
The following screeshot displays the Threshold Rule:
Figure 125: Threshold Rule

Informing Delay Rule

Informing Delay Rule allows you to delay alarms as per your time definition before
they are shown in monitoring applications. If you cancel the alarm within the defined
time, the alarm is not forwarded to the pipe, however, it is inserted directly into the
database.
The following figure illustrates the Informing Delay flow:
Figure 126: Informing Delay flow
The following figure illustrates the Informing Delay Rule:
Figure 127: Informing Delay Rule

193
Reclassification Rule
Using Reclassification Rule, new classifications for alarms can be done by either
raising or reducing the severity.
The following screenshot displays Reclassification Rule:
Figure 128: Reclassification Rule

Suppression Rule
A Suppression Rule causes the primary alarm to suppress the secondary alarm so
that it is not shown in the presence of the primary alarm. Also you can define a new
alarm which will be generated, whenever the suppression happens.
The following figure illustrates the Suppression Rule flow:
Figure 129: Suppression Rule flow
The following screenshot displays the Suppression Rule:
Figure 130: Suppression Rule

195
Filtering Rule
Some insignificant alarms are not sent to a specified target in the Fault Management
system. For example, when a server id down, several alarms will be produced but
only the most significant should appear in the alarm list. Using filtering rule, alarms
can be filtered from the User Interface (UI), Database, Alarm correlation server and
North Mediation Target.
Several alarms can be filtered, separated by comma.
The following figure illustrates the Filtering Rule flow:
Figure 131: Filtering Rule flow
The following screenshot displays the Filtering Rule:

Figure 132: Filtering Rule

197
Trigger Rule
The Alarm Trigger Rule action compares the defined Alarm definitions with the
Alarm coming from the network and triggers the process.
When a defined alarm number (14819141) arrives in NetAct, a ssh session (as user
rtp99) is opened to the NE (with address 10.58.129.9) and a script (status.sh), which
is stored in /tmp is executed.
The following screenshot displays the Trigger Rule:
Figure 133: Trigger Rule
AckWithCancel Rule
Some unacknowledged cancels do not require operator attention and should be
automatically acknowledged. Such unacknowledged alarms are autoacknowledged
using AckWithCancel Rule.
AutoAck Rule
Some alarms do not require operator attention. It can be automatically resolved
without operator involvement. These alarms are required to be acknowledged
automatically and are auto-acknowledged using AutoAck Rule.
ForwardAlarmToEmail Rule
The Forward Alarm to email action compares the defined Alarm definitions with the
Alarm coming from the network and forwards it to the e-mail addresses in the
specified format.
Delayed Auto-Clear Rule

DelayedAutoClear alarm allows clearing the alarms when the required alarm criteria
is matched as per the time and threshold count definition. This helps to reduce load
on the system when similar kind of alarms are received continuously.

Alarm definitions
To add an Alarm definition, right-click a rule and select Add alarm definition. An entry
is created for the new Alarm. By default, the first Alarm is Alarm A, the second is
Alarm B and so on. Each Alarm pattern in the rule should be within 4096 characters.
Adding patterns
• To apply a rule, Alarm pattern should be defined. In some cases, you must
create more than one pattern for an Alarm. If an incoming Alarm matches the
defined pattern, it triggers an appropriate rule action.
To add a pattern, right-click on an Alarm and select Add pattern. To remove a
pattern, right-click on the Alarms pattern and select Remove pattern.
You can use operators to associate different operators to define the alarm and
managed object attributes in Alarm Pattern. The following table lists the types of
operators, meaning and example.
You can use the "in" operator while defining the object properties.
You can add one or more patterns for an Alarm using the OR
operator. For example, two Alarm patterns, Alarm pattern 1 and
Alarm pattern 2 can be created under the same Alarm A, using the
OR operator.
Maximum number of OR patterns supported in rule is 15.
The alarm patterns can be from the following types:
• Alarm Properties: like Alarm Number, Alarm Type and so on.
• Object Properties: like Object Class, Distinguished name and so
on.
• Object MR/Site properties: Maintenance Region Name, Site
Name and so on.
• Controlling Object Properties: like Controlling Object Name and
so on.
Figure 134: General rules definition: Alarm definitions

199
Operator Meaning Text Number Example

= operator allows you to define
both Text and Number values.
However, this depends upon the
selected attribute. For example,
If you select Alarm Text attribute,
then value can be both text and
number.
= Equal To Yes Yes
If you select Alarm Number
attribute then, value should be
only number.
This operator allows to display
alarms whose attribute value is
equal to one given in the rule.
<> operator allows you to define
both Text and Number values.
However, this depends upon the
selected attribute. For example,
Not Equal If you select Alarm Text attribute
< > Yes Yes then value can be both text and
To
number.
If you select Alarm Number
attribute then value should be only
number.
A regular expression =(regexp) is
a pattern of characters that
describes a set of strings. For
example, if the value defined for
the alarm text is Alarm
Equal to and Text=(regexp) .*net.*, alarms
= (regexp) regular Yes No containing text net are displayed.
expression For example, alarms with text -
internet, network and so on.
Regular expression can be
defined with all the java supported
characters (*,?, + and so on).
<>(regexp) - operator allows you
to define the text which does not
contain the strings of text with
operator. For example, if the alarm
text is defined as Alarm
Text<>(regexp) .*net.*, rule is
Not equal to
<>(regex applied on all the alarms which
and regular Yes No
p) does not contain word or pattern
expression
of the word net. For example, rule
is not applied on the alarms with
text as internet, network and so
on. Regular expression can be
defined with all the java supported
characters (*, ?, + and so on).

Relation Conditions
You can define certain relation conditions between alarms. The actions are
triggered, only if the relation conditions are met.
There are four types of relation conditions:
MO Relation This includes the relationship of the Managed Objects
(MO), that sends the respective alarms.
Time Window This defines the time interval in which the alarms arrive

for a meaningful correlation.
Count Condition This defines the number of times an alarm occurs.
Order Condition This defines the number of alarms that occur for a given

time interval with respect to the alarm time.
The conditions are combined with the AND operator.
In the table, you can find the description of the different types of MO relations:
Table 12: Types of MO relations (1/2)
Network Scope A Scope B Description
Topology
Alarms to be correlated must be
The same as Any Any
generated by the same MO.
In the object containment tree, the
object in Scope A is below the
Child of Any Any
object in Scope B or the object in
Scope A is the same as in Scope B.
Descendent of Any Any object in Scope A is below the
object in Scope B.
object in Scope B is below the
Parent of Any Any
object in Scope A or the object in
Scope B is the same as in Scope A.
Antecedent of Any Any object in Scope B is below the
object in Scope A.
Combination of child of and parent
of relation types. The objects in
Relative of Any Any Scope A and Scope B have to be in
the same branch of the object
containment tree.
Alarming objects have the same
Sibling of Any Any parent object in the object
containment tree.

201
Table 13: Types of MO relations (2/2)

Network Scope A Scope B Description
Topology
Alarming objects must be
the closest possible
instances of the object
class to each other in the
As near as managed object hierarchy.
Any Any
possible The relation checks if an
alarming object is close
enough to the other
alarming object to allow the
correlation.
The PCM card carries a
BCF / BTS /
Connecting to PCM TRX signaling link used by
TRX
the BCF, BTS, or TRX.
The PCM card carries a
BCF / BTS /
Connected by PCM TRX signaling link used by
TRX
the BCF, BTS, or TRX.
In the object containment
tree, the object in Scope A
is directly below the object
in Scope B.In the object
All direct child of Any Any
containment tree, all the
objects in Scope A are
directly below the objects in
Scope B.
tree, the object in Scope B
Direct parent of Any Any
is directly below the object
in Scope A.
tree, all the objects in
Direct child of Any Any
Scope A are directly below
the objects in Scope B.
tree, the object in Scope A
Independent of Any Any
has no relation to the object
in Scope B

Figure 135: General Rules Definition: Relation Conditions
Actions
When an alarm definition matches with an alarm, some specific action is triggered
accordingly with the "actions" definition of the rule. The following are the possible
alarm actions:
• Compressing an alarm
When a single fault causes series of multiple occurrences of same alarm, then
you can create a compression rule. You can see only one Alarm, despite the
multiple occurrences of the same Alarm.
• Suppressing an alarm
• Creating a new alarm
You can create a new Alarm for the current MO within the range 0 to
2147483647 with user definable texts and severity for the same object.
• Defining informing delay
The informing delay action is executed if an Alarm arrives, that fulfils the criteria
defined for the Alarm delay. This action takes precedence, when defined with
filter toggle Alarm having same Alarm patterns.
• Canceling an alarm immediately
You can cancel an Alarm immediately by a correlation rule. These Alarms are
stored in the database. They can also trigger other rules, such as counting.
• Filtering an alarm
The Filter Alarm action compares the defined Alarm definitions in the rule with
the Alarm coming from the network and filters them from database, user
interface, Alarm correlation server and North Mediation Target.
• Reclassifying an alarm
Reclassify Alarm action allows you to reclassify the Alarms from existing state.
For example, from MINOR to CRITICAL.
• Automatically acknowledging an alarm
The Alarm coming from the network is acknowledged automatically.
• Acknowledging with cancel alarm
The Ack With Cancel action compares the defined Alarm definitions with the
Alarm coming from the network and acknowledges the cancel Alarm
automatically.
• Triggering a rule

203
The Alarm Trigger Rule action compares the defined Alarm definitions with the
Alarm coming from the network and triggers the process.
• Forwarding an alarm to email
The Forward Alarm to email action compares the defined Alarm definitions with
the Alarm coming from the network and forwards it to the e-mail addresses in
the specified format.
• Filtering a toggle alarm
This action is executed if an Alarm fulfils the defined criteria and toggles at least
a configurable number of times within a configurable time interval. However,
when the alarm settles down for a configurable time, it is no longer shown as
active.
• Filtering a threshold alarm
This action is executed if an Alarm fulfils the defined criteria and occurs less
than a configurable number of times within a configurable time interval.
• Delayed auto clear rule
An equivalent of that in Monitor is the Count rule. However, there is a small
difference in the behavior of Count rule. In Count rule, even the canceled
secondary alarms are counted when raising the new alarm (root cause alarm).
This is not an incorrect behavior because the intention of the count rule is to get
a statistical idea about the number of times a certain alarm is appearing in a
time window. The Delayed Suppression rule will raise the new alarm only when
n number of alarms are actually active. That is, when certain secondary alarm
instances are canceled, they are removed from the counting.
• Text modulation alarm
Text modulation rule allows you to modify the alarm text attributes. In some
cases the operator would like to modify the text of an alarm. For instance, the
operator would like to send some special instruction through the Alarm Text to
Northbound so that the operator at the Network Operations Center (NOC) can
quickly identify the special instruction from the alarm text without having to look
into the alarm details or opening the alarm manual page on the NetAct side.
Figure 136: General Rules Definition: Actions

Scheduling Definitions
Optionally, you can set schedule definitions for your rule. Once activated, the rule
will follow the schedule. Without schedule, the rule will permanently be activated
until manual deactivation occurs.
Figure 137: General Rules Definition: Scheduling Definitions
Rule Analyzer
Rule Analyzer allows determining whether an alarm with a given set of attributes
would match a rule or not.
With Rule Analyzer you can perform the following tasks:
• Search for rules by defining the required alarm property such as alarm number,
alarm severity and so on.
• Select and open the matching rules in Rule Explorer and Rule Editor.
• Perform quick search operation using Ctrl+ F.
Rule Analyzer displays the following rule details:
• Rule ID:
Indicates the unique ID of a rule.
• Rule Name:
Indicates the rule name as seen in Rule Editor.
• Rule Path:
Indicates the path of the rule as seen in Rule Explorer.
For example, In Rule Explorer if you have rule X under folder folder1/subfolder1,
then the rule path will befolder1/subfolder1/X.
• Action Type:
Indicates the action type of a rule participating in the search operation.
Examples for action types:
• Compress alarm
• Suppress alarm
• Informing delay
• Forward alarm

205
• Auto Ack alarm
• Rule Status:
Indicates if the rule is active or inactive.
• Rule Match
Can have a value of COMPLETE or PARTIAL.
Example for Rule match, Consider a rule with the following alarm properties:
{alarmNumber = 123,alarmText = "communication
failure",alarmType="COMMUNICATION OR
ENVIRONMENTAL",severity="MAJOR or CRITICAL"}
COMPLETE: If the rule criteria match the search attributes completely, then the
match is termed as COMPLETE.
Figure 138: Rule Analyzer

Lab exercise: Rule Explorer and Rule Editor

Context
The students test the skills to differentiate the different cases for:
• Alarm reduction
• Alarm forwarding
• Alarm triggering in NetAct
Use Rule Explorer and Rule Editor to manage different alarm processing rules.
Procedure
1 Open the Rule Explorer tool in Monitor.
Result of this step

How can you differentiate between active and inactive rules in the
Rule Explorer?
Can you modify an active rule?
What is correlation? What are the three cases for correlations in NetAct and
describe each case?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

207
2 Create a new alarm (using a rule type: rule) with the severity MINOR for the
alarm numbers 35011, 35007 and 35005 with a certain alarm number (for
example 39000).
Information
If one of the directory servers is down several critical alarms are produced from
corresponding directory servers.
Result of this step

________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
3 Create an Alarm Forwarding rule that forwards all critical alarms from NT
HLRFE managed object (or other available MO) on Sundays to a certain Email
address. Activate the rule in Rule Editor.
Result of this step

________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: Alarm Filters

Context
The aim of this exercise is to create a filter to display only critical alarms from
BSC/RNC.
Prerequisites
• Log in to NetAct. Select Monitoring. Start the Monitor tool.
• Open Tools ► Monitoring Desktop ► Alarm Filter Explorer.
Procedure
1 In the Alarm Filter Explorer, right click the alarm folder and select New Filter.
2 Enter the name of the new filter and select Finish.
3 Right-click in the Alarm pattern field and select Severity.
4 In the pull down menu select critical Right-click in the Alarm pattern field and
select Object Class.
5 In the pull down menu select BSCC/RNC and Add.
Information
If your network element is BSC, select BSCC. If your network element is RNC,
select RNC.
6 Press OK.

209
7 Select File ► Save all.
8 Test your filter by dragging and dropping it into one of the Alarm Lists.

Lab exercise: Alarm Rules

Context
This Lab exercise access the students to work with alarm rules.
Figure 140: Lab exercise: Alarm Rules
Prerequisites
• Log in to NetAct. Select Monitoring. Start the Monitor tool.
• Open Tools ► Monitoring Desktop ► Rule Explorer.
Use parameters given by the instructor.
Procedure
1 Create an Alarm Forwarding rule that forwards all critical alarms from
BCF/WBTS managed object (or other available MO) on Sundays to a certain e-
mail address.
2 Activate the rule in the Rule Editor.
Information
Right click in Alarm definitions, Relation Conditions and Actions to view the
available options and select the right options when creating the rule.

211
Topology Management
Managing Network Views
Hierarchical and scalable views over the entire managed network are visualized in
the Network View tool. The graphical views can be adjusted to the different
monitoring needs from network-wide monitoring to object-level and technology-
specific monitoring. In the upper-level views, users can quickly see the general
situation of the managed network. Moving to a sub-view shows the alarming objects.
Monitoring Desktop provides a range of monitoring tools that can be accessed from
Network View.
A common concept in network management is to have views to the managed
network that is typically arranged according to the object hierarchy, connectivity, or
other information levels. These views can model either logical or geographical
aspects of the underlying network.
View Explorer visualizes the view hierarchy that has been implemented. It shows the
views in folders that can be used to structure views for a better overview. The View
Explorer tool provides a search facility that can be used to find views for different
aspects, for example for contained managed objects.
You can select a view for manipulation or display the different attributes of the
chosen view in the Properties window. You can also create new folders for new
views or move views from one folder to another.
The sections covered in the next topics are as follows:
• Network Views Monitor Modes
• Creating and Editing Network Views
• Adding a link between two objects
• Linking and unlinking a sub-view
• Adding new symbols, background graphics and background images
• Saving a view
• Creating Children Objects’ Subviews
• Automatic View Generation

Network Views Monitor Modes

You can view the Network View tool in two modes:
• Monitoring mode
Views are constructed from the view objects and represent the monitored
network. In this mode, you can monitor complete state information of the
monitored objects.
The tool displays two states:
• Topology state
• Alarm state
In this mode, you can also search for managed objects. Drag and drop
managed object from Object Explorer to network view to view all the network
views in which the object exist. If the managed object does not exist in any view,
a message is displayed.
• Edit mode
In the Edit mode, you can modify the views. In this mode the state information is
suppressed.
Edit mode is restricted to some users, requires additional
authorization.
When another user modifies the views in the database, a message
to reload the view is displayed and the views are automatically
updated.
The tools in the lower toolbar are available only in the Edit mode. In the
toolbar, you can select one tool at a time. By default, deselecting a tool
activates the Select tool and the Move and Resize tool.
Some tools are active only for a single operation and get de-activated
automatically, while others are permanent and hence you must activate a
different tool (usually the Select tool and the Move and Resize tool to switch
it off.
Switching between Monitor and Edit mode

Open the shortcut menu of the tool by right clicking anywhere and selecting Switch
to Edit Mode or Switch to Monitor Mode, depending on the current operation mode.
When changing a view and switch to Monitor mode, the users are still prompted to
save changes when closing the view.

213
Figure 142: Network View Window

Creating and Editing Network Views

Network Editor is the tool used to create or edit network Views. To create a new
view, open network editor via the View Explorer:
On the Desktop menu bar, select Tools ► Managed Objects ► View Explorer. In
View Explorer right click on the background and select New Folder or new view. The
views have to be created into folders.
To Edit a View, select the corresponding view in the View Explorer Tool, open the
view and switch the mode to "Edit Mode".
All the tasks in the following sections apply for both creating new views and
editing existing views.
Adding Objects and Moving objects in the view

The figure illustrates the adding of objects and moving objects in the view.
Figure 143: Adding Objects and Moving objects in the view
Adding an object
You can add an object to a view in the following ways:
1. Drag an object from another tool and drop it at the desired position.
2. Paste the objects from the clipboard. When pasting from the clipboard, objects
are placed in the center of the view.
Cutting, copying and pasting objects

In the Edit mode, cutting, copying, and pasting can be used to copy objects into the
view. The following two rules must be taken into consideration:
• Objects copied from another tool are added as view symbols to the centre of the
view.
• Objects and background graphics copied from another Network View tool
preserve their view-specific information. This means that the relative positions of
the objects, links, the icon used to visualize the object, and other properties are
copied as well.
The following describes the steps for cutting, copying and pasting objects.

215
1. To cut or copy in the view, select the object to cut or copy, and paste into the
clipboard.
2. To open the shortcut menu, right-click the selected element. Select Cut, Copy
or Paste.
Cut and Copy are enabled only if objects in the view are selected, while Paste is
available only if the system clipboard contains data that can be pasted into the view.
Cut, Copy and Paste can be performed using keyboard shortcuts shown in the
menu, directly from the Edit menu, or using the associated toolbar buttons.
Moving objects
1. Select an object to move.
2. You can move view objects as well as background graphics.
3. Click the selected object and move it around keeping the mouse button pressed
down.

Adding a link between two objects

Context
You can add link only between two symbols by the following steps:
Figure 144: Procedure: Adding a link between two objects
Procedure
1 In the lower toolbar, activate the Make Link tool.
2 Drag the link, from the first symbol to the second symbol by pressing the left
mouse button.
3 Release the mouse button on the second symbol, when you see that the symbol
is selected.
4 To cancel the link creation, release the mouse button on the view background.
Result of this step

Links are automatically laid out.
5 Right-click the link for changing the link type.
6 In the Change Link Type... submenu, select the link type.

217
Linking and unlinking a sub-view

The following figure illustrates adding links and subviews.
Figure 145: Adding Links and Subviews
Sub-view links can be attached to view objects. This allows the construction of a
view hierarchy from high level to detailed views.
1. Right-click the view object and select Sub-view.
2. In the Select Sub-view dialog, browse to the view you want to link and select it
in the open view.
3. To create a link, click Select.
To stop the operation, click Cancel.
4. To unlink, select the view object that has a sub-view, and select the Remove
sub-view option from the shortcut menu.
Navigation Links
A Navigation Link is used to create a link to navigate between any two views. The
alarm state of an underlying view, associated with a Navigation Link, is not
propagated to the views at the upper level.
• Creating Navigation Links
Open the view in Edit mode. In the lower toolbar, click Add Navigation Link,
and place in the desired position in the view.
• Associating views to Navigation Links
To navigate to a view, associate it to a Navigation Link in the Network View
pane.
Adding new symbols, background graphics and background images

The following figure illustrates the adding of new symbols, background graphics and
background images.

Figure 146: Adding new symbols, background graphics and background

images
Adding background graphics

To activate the graphic tool for adding the graphic object, press its button in the
lower toolbar:
Create the graphic object.
Depending on the tool, follow the instructions:
• To create a line
define the endpoints with two mouse clicks. When two objects are connected
with a line, the line end is not connected to the objects. This is clearly visible
when you zoom in.
Or
• To create a rectangle
drag the rectangle open while holding down the left mouse button. Release the
mouse button to insert the rectangle.
Or
• To create an ellipsis
drag the definition rectangle open while holding down the left mouse button.
Release the mouse button to insert the ellipsis.
Or
• To create a polygon
set the definition points by clicking in the view. End with a double-click.
Or
• To create a polyline
set the definition points by clicking in the view. End with a double-click.
Or
• To create a label
Click in the view to open a text edit box. Enter the label text and move the label
to the required position. You can edit the label later by activating the Label tool
and clicking on the label. Alternatively, when the select tool is active, you can
use Ctrl + click on a background label, to edit it.

219
Adding background image to network view

Background images can be added to a network view using the Select Background
Image button available in the lower toolbar of the view.
The following image formats are supported:
• jpg
• png
• gif
1. To add background image, switch to Edit mode.
2. In the lower toolbar, click the Select Background Image button.
The Select Background Image window opens.
3. In the Select Background Image window, select the desired background image
from the local file system.
4. You can preview the selected image on the right side of the Select Background
Image window.
5. Click Open.
By default the background image is set as the lowest layer of the network view.
New or existing decorations are always placed on top of background image. The
order of the background image can be changed like any other decorations. For
information on how to change the order, see Stacking the background objects in
Monitor Online Help.
When a background image is added to the network view, its actual size is
detained. However, on re-opening the view, the zoom factor of the background
image and other contents of the view is adjusted so that all the contents fit in the
view.
6. Save the view.
The background image can be resized and moved around the view.
To remove the background image, right-click the background image and select
Remove.
Each background image requires the following amount of memory:
Width * Height * 4 bytes
where, width and height are the dimensions of the image.
Accordingly, the number of views, with background images, that can be
simultaneously opened is subject to the client heap memory available.
Rotate background graphics as follows:
1. Select an object for rotating.
2. Handles around the object appear.
3. Select the Rotate tool.
4. Click one of the handles and hold the mouse button down while turning around
the object with the mouse.

Saving a view
Open the shortcut menu of the tool, select Save to save the view, or Save As to
save a copy of the view with a different name.
You can also save the views in following ways:
• In the shortcut menu, use the displayed shortcut keys.
• From the file menu, choose Save or Save As.
• In the toolbar, click the associated Save button.
Figure 147: Saving a view

221
Creating Children Objects’ Subviews

You can create subviews automatically for all managed objects that have child
objects. There are two options for creating subviews.
For a selected managed object:
• One Level can be used to create subview for its immediate children.
• All Levels can be used to create subview for its children at all levels.
Ensure that the adaptations are deployed for the selected managed objects
and its children before creating subviews.
Figure 148: Creating Child Object Subviews 1/2
Figure 149: Creating Child Object Subviews 2/2

Automatic View Generation

Automatic view generation is possible via the option “Create Subviews”. This
enables the creation of the full hierarchy of views and subviews (up to the last child
object level) for any given parent object.
With this feature, it is possible to create the subviews and simultaneously link the
child view to the parent object automatically. This is possible only in the Edit mode of
the Network View.
Figure 150: Automatic View Generation

223
Working Set Manager
A working set is a collection of managed objects. Working Set Manager enables you
to create, view, browse, combine, export and remove working sets. You can create
working sets based on preferred criteria:
• DN list
• Area
• FM Query
• CM Query
• CM Advanced Query
Additionally, you can create a new working set based on existing working sets in the
Combine tab.
Working sets can be managed by the Working Set Manager application or
Command Line Interface (CLI).
There are two kinds of working sets:
• Static working sets - where the list of managed objects is invariable.
• Dynamic working sets - based on constant criteria, but the managed objects are
added to or removed from a working set based on network changes.

The maximum number of managed objects in each working set is 100 000.
There are three working set types:
• DN List - a type of working set that consist of a static list of managed
object DNs.
• Area, CM Query, FM Query, CM Advanced Query, Combined - types of
working sets dynamically changing content, based on the selected
criteria.
• Legacy - a working set type that was not migrated to the new data
representation, or its migration script was not executed correctly. This
working set cannot be edited.
The following figure illustrates the creation of working set based on FM query.
Figure 152: Creating Working Set - FM Query
The following figure illustrates the creation of working set based on on CM
Advanced Query.

225
Figure 153: Creating Working Set - CM Advanced Query
The following figure illustrates the combination of working sets.
Figure 154: Combining Working Sets

Creating managed objects

You can create new objects in the Managed Object Framework (MOF) database
with the Object wizard. You can edit the optional attributes of the managed objects
by using the Properties tool.
Managed objects can define any manageable network resources present in a
communication network. A managed object represents a physical or logical network
element or a piece of equipment that belongs to the network. Managed objects are
often hierarchical, with certain objects controlling and containing others.
The Object wizard consists of two screens. The first screen provides all the available
object classes and their releases, and the next screen populates all the mandatory
attributes defined for the selected class.
With the Object wizard you can perform the following tasks:
• Create root managed objects
• Create child managed objects
You can open the New Object wizard in three ways:
• Right-click an object, and select New ► Object from the shortcut menu.
Or
• Right-click on the background of the Object Explorer window, and select New
► Object from the shortcut menu.
Or
• From the File menu, select New ► Object.
The New ► Object option is available in the shortcut menu and on the File
menu only if CM_ManagedObject_Create permission is within the scope of
the selected object. For more information on the scope, see
Scope based authorization for managed objects in the online help.
Creating managed object procedure

The figure illustrates the creating of new managed objects.
Figure 155: Creating New Managed Objects

227
This section describes the procedure for creating a managed object.
1. On the Desktop menu bar, select Tools ► Managed Objects ► Object
Explorer.
The Object Explorer window opens. Managed objects, from the MOF database
are loaded in the Objects pane.
2. In the File menu, select New ► Object.
Alternatively, right-click in the background of the Objects pane and select New
► Object.
The New Object wizard for root managed object creation opens.
3. In the Object Class drop-down list, select an object class.
At this stage, you can switch to create a child managed object for an
existing parent managed object by clicking the Browse button.
The Object Class drop-down list displays Presentation Name and Object Class
ID inside the parenthesis.
The Root Object check box is already selected and disabled for the root object
creation.
4. Click Next.
The Fill Attribute Values screen appears.
5. In the text field, enter the attribute values for the corresponding attributes of the
managed object (for example, Instance) and click Finish.
If the length of the text field is insufficient to display the complete
information, click on the extreme right. This opens a new window
where you can enter, edit, and view the complete information
regarding the attribute values.
The new root managed object is created.

Associating a Managed Object to Maintenance Region

Context
You can associate a managed object to Maintenance Region using the Maintenance
Region option.
You cannot associate a Maintenance Region to another Maintenance
Region.
This section describes steps for associating a managed object to maintenance
region.
Prerequisites
You must have CM_ManagedObject_MR_Association permission.
Procedure
1 Right-click a Managed Object and select Maintenance Region Association.
Result of this step

The Associate Maintenance Region dialog appears.
2 Select the Maintenance Region to which you want to associate.
Information
To deselect the Maintenance Region, select No Maintenance
Region Selected check-box.
3 To propagate the selected Maintenance Region to the sub tree, select
Propagate Maintenance Region to the sub tree check-box.
4 Click OK.

229
Associating a Managed Object to Site

Context
The following figure illustrates the associating Managed Objects to MRs or sites.
Figure 156: Associating Managed Objects to MRs or Sites

You can associate a managed object to Site using the Site Association option.
You cannot associate a Site to another Site.
Figure 157: Editing object attributes in the Properties tool
Prerequisites
You must have CM_ManagedObject_Site_Association permission.

Procedure
1 Right-click a Managed Object and select Site Association.
Result of this step

The Associate Site dialog appears.
2 Select the Site to which you want to associate.
Information
To deselect the Site, select No Site Selected check-box.
3 To propagate the selected Site to the sub tree, select
Propagate Site to the sub tree check-box.
4 Click OK.

231
Editing object attributes in the Properties tool

Context
The following figure illustrates editing managed objects properties.
Figure 158: Editing Managed Objects Properties

After creating managed objects, you can set the values for non-mandatory object
attributes in the properties tool.
This section describes the steps for editing object attributes in the properties tool.
Figure 159: Procedure: Editing object attributes in the Properties tool
Prerequisites
You need to have CM_ManagedObject_Edit permission.

Procedure
1 Select Tools ► Properties.
Information
Alternatively, on the keyboard, press the Ctrl + 1 keys.
2 To edit, select the attribute value.
3 Enter the new value.
4 To open the external editor, press the Custom editor button for editing
attributes with complex data types.
5 To accept the new value, Press Enter.
Information
Alternatively, in the external editor, click OK.
6 Save the modified object attributes using one of the following methods:
a) In the Properties editor, click Save.
b) Alternatively, from the File menu, select Save or Save All.
Information
When several objects are selected, the updated values are saved in all the
objects.
You can edit the properties of a managed object only if the
CM_ManagedObject_Edit permission is within the scope of the
selected object.
Only power group users or users with global scope (that is if all
maintenance regions and associated network elements are
within the scope) can assign or remove relationship of an
object to a maintenance region.
The current state of the managed object in the managed
system is defined using the attribute Object State. The
manages objects are mainly in three stages: Operational, Non
Operational and Created From Network.
For more information on the scope, Scope based authorization
for managed objects in online documentation.

233
Object Deletion
You can delete one or more managed objects and their child managed objects only
if you are authorized to delete them.
You require the permission CM_ManagedObject_Delete to delete managed objects.
The Managed objects are in three states which are as follows:
• Operational
• Non Operational
• Created From Network
While deleting managed objects, the managed objects in Created From Network
state holds the same conditions as in Non operational state.
The state of a managed object is set using the Properties tool.
Deletion of objects in the Operational state can lead to loss of network
information. When you delete an object, all its child objects are also deleted.
Deleting managed objects in the non-operational state

You can delete managed objects using the desktop tools like Object Explorer and
Object List. The following procedure explains how to delete managed object using
Object Explorer tool.
1. On the Desktop menu bar, select Tools ► Managed Objects ► Object
Explorer.
The object pane lists the managed objects from the MOF database.
2. Select one or more managed objects to be deleted.
3. On the Desktop menu bar, select Edit ► Delete.
a. Right-click the Managed Objects and select Delete from the context menu.
b. Alternatively, From the Tool bar, click the Delete icon.
c. Alternatively, Press Delete on the keyboard.
The Confirm Object Deletion dialog displays.
4. Click Yes.
The managed objects are deleted.

Deleting managed objects in the operational state

Context
The figure illustrates the deleting objects.
Figure 160: Deleting Objects

You can delete managed objects using the desktop tools like Object Explorer and
Object List.
Figure 161: Procedure: Deleting managed objects in the operational state
Prerequisites
You require the permission CM_ManagedObject_Delete to delete managed objects.
Procedure
1 On the Desktop menu bar, select
Tools ► Managed Objects ► Object Explorer.
Result of this step

The object pane lists the managed objects from the MOF database.

235
2 Select the managed objects.
3 On the Desktop menu bar, select Edit ► Delete.
a) Right click the managed objects and select Delete from the context menu.
b) Alternatively, from the Tool bar, click the Delete icon.
c) Alternatively, Press Delete on the keyboard.
Result of this step

The Confirm Object Deletion dialog displays.
4 Select the Delete authorized and operational objects option.
5 Click Yes to delete the managed objects.
Information
In the Confirm Object Deletion dialog box, click Details to view information
about the Unauthorized objects and Operational objects.

Handling of Alarm Processing

Fault Management Pipe Status
The Fault Management (FM) Pipe represents alarm collection and correlation in FM
platform. The FM Pipe collects, processes and stores alarms. It also supports
synchronization of alarms between the network and the FM database.
The figure illustrates the alarm pipe status.
Figure 162: Fault Management Pipe Status
Fault Management pipe displays the status of NetAct Monitor. By default, a bell icon
is displayed in the right bottom corner of the status bar. The color of the icon
determines the status of the FM pipe. If the color of bell icon is green, FM pipe is
active and if the color of the bell icon is red, FM pipe is inactive.
You can choose to either display or not display the FM pipe status. If the FM pipe
status is not visible in the status bar, from Monitor window, click Tools ►
Monitoring Desktop ► FM Pipe Status to display the FM pipe status in the status
bar.
Double-click the bell icon on status bar to view the FM pipe latency. An Information
dialog box opens with the pipe status and its latency information.
• When the processing threshold is exceeded, the FM pipe becomes slow.
As a result, the alarm status is red. The following message appears:
FM pipe processing threshold exceeded.
• The connection to FM services may fail indicating a problem with
network or database. To retain the FM Pipe Status display, click
Window► Save Current Workspace.

237
Alarm database upload

Manual upload of Alarms
Due to various reasons such as network connection failure, the alarms raised from
the network element may not reach the management system and therefore, are not
available in the database.
The FM platform recognizes the uploadable and non-uploadable alarms received
from the different Network Elements. Alarm upload process synchronizes these
alarms with the network management system database. The non-uploadable alarms
do not get canceled and remain active during alarm synchronization process.
• Uploadable Alarms:
The alarms from the Network Element will be uploaded to management
system database during synchronization.
• Non-uploadable Alarms:
The alarms from the Network Element will not be uploaded to
management system database during alarm synchronization. These
alarms might not state the actual status of the problem in Network
Element and hence, need to be left active unless they are manually
canceled.
The user can initiate an alarm upload process in Alarm Tools (Alarm List, Alarm
History, Warning List) or Object Explorer.
• Alarm Tools (Alarm List, Alarm History, Warning List)
• Right-click an alarm and select Alarming Object ► Alarm Upload.
Or
• Right-click an alarm and select Controlling Object ► Alarm Upload.
• Object Explorer
• Right-click a Managed Object and select Alarm Upload.
The Alarm Upload option is enabled only for Network
Elements.
Result: The non-uploadable alarms available in management system remains
active.
Press Shift or Ctrl key to select the multiple managed objects for alarm
uploading.

Figure 163: Alarm Database Upload

239
Alarm Deletion for a MO

Deleting Alarms of an Object
It is possible to delete all the alarms of a managed object.
This helps in clearing the alarms for troubleshooting purposes.
This process can be performed using the Alarm Tools (Alarm List, Alarm History,
Warning List) or Object Explorer.
• Alarm Tools (Alarm List, Alarm History, Warning List)
• Right-click a managed object and select Delete All Alarms from Database
► Delete Alarms For Object.
Or
• Right-click an alarm and select Controlling Object ► Delete All Alarms
from Database ► Delete Alarms For Object.
• Object Explorer
• Right-click a managed object and select Delete All Alarms from Database
► Delete Alarms For Object.
All the alarms of a managed object are deleted from the database.
The Delete All Alarms option is enabled in the context menu of the managed
object only when the corresponding object class in adaptation includes Alarm
States attribute group.
Figure 164: Deleting all Alarms from an MO

Lab exercise: Enable FM Pipe

Context
This section tests the skills on the enabling of the FM pipe status.
Procedure
1 Navigate to Monitor application.
2 Click Tool ► Monitoring Desktop.
3 Select FM Pipe Status.
Post-requisites
What should you do if the FM Pipe is not running?
Did anything happen?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

241
Summary: Advanced Fault Management with NetAct

Module Summary
• Manage the alarm processing using alarm filtering and alarm reduction in
NetAct.
• Manage the NetAct Topology.
• Verify Fault Management pipe status.
• Perform alarm database upload.
• Perform alarm deletion for Managed Object.


Basic Performance Management with NetAct
243

Module Objectives
• Explain the purpose of Performance Management and describe what is a
KPI.
• Explain the Performance Manager tools.
• Create, customize and generate performance management reports and
dashboards.
Performance Management Principles

Performance Management process
This topic covers the additional information for the trainer.
The performance management process comprises the description of a view on the
PM tasks the operators follow in order to monitor, assess the quality of the network
and obtain the requested output information for the different users and processes
inside the operator’s organization.
Figure 165: Performance Management process
Defining or revising Quality of Service goals

When managing a particular network, the Quality of Service (QoS) represents the
effective maintenance state of the quality for the network services according to some
agreed criteria. Maintaining and improving the QoS of the network includes regular
monitoring of the service performance and the evaluation of the service performance
problems with respect to the targeted level of service delivery.

To improve the service, it is necessary to define QoS goals that guide the evaluation
of network and service performance. These goals can represent, for example, the
point of view of the operator (efficient hardware usage, for example efficient use of
network elements considering the type and capacity of the NEs, their location and
number to support the services) or the point of view of the subscriber (availability,
speed, and accuracy of the service).
As the network evolves and expands, these QoS goals might have to be updated
and revised. Mature operators competing for more market share benefit from
introducing new services to differentiate themselves from other service providers. At
this point, all kinds of service and profile measurements are useful. The quality of
service becomes extremely important and, for example, optimization measurements
must be taken. The following tasks belong to this stage:
• Setting objectives for the desired level of quality.
• Measuring the quality of service by monitoring real-time data and long-term
trends.
• Planning corrective actions.
Translating Quality of Service goals to network performance requirements

To achieve the defined QoS goals, it is necessary to prepare or update the detailed
requirements for the network, including the requirements on network performance.
For example, the quality of a voice service can be correlated with the number and
ratio of dropped calls, while the accuracy of an IP service can be correlated with the
number of received packets.
Defining reporting requirements

The network performance requirements serve as the basis for reporting
requirements and provide information on which measurements you have to monitor
with the PM applications.
Identifying other reporting needs

Monitoring the day-to-day performance of the network is not the only reason for
using performance reports. Information from reports can be used, for example, to
examine short-term changes due to system upgrades or to revise long-term trends
to gather information for optimizing or expanding the existing network.
If these reporting needs are translated into measurements, the reporting
requirements are then clear and can be translated into measurement activation
criteria. However, some reporting requirements can give rise to a need for a new or
an additional PM application. You might also need a new or additional PM report
when you are investigating uncommon situations or when you have upgraded or
expanded your network.
Before establishing new reports, it is recommended that you check whether the
active measurements already provide the counter information that you need, or
whether the required measurements are available but have not been activated yet,
or whether it is sufficient to change the measurement settings to obtain the needed
information.
Defining reports
You can define and schedule your reports based on the reporting requirements. The
details of defining reports mostly depend on the Operations Support System (OSS)
solution.

245
Adapting the measurement load and the OSS

If you need a new measurement, you have to ensure that the capacity of the OSS,
for example, disk space and insertion time, is not exceeded when the new
measurement is implemented and activated. If the OSS capacity could be
exceeded, you can adapt the entire measurement set by reducing the number of the
measurements or increase the measurement intervals, or you can increase the OSS
capacity, for example, with additional processors. If the capacity has not been
exceeded, you can proceed with initializing the additional measurements.
Initializing measurements
Activating all the necessary measurements across the network could impose a
significant but unnecessary load on the database and the PM processes. So, it is
recommended to consider the following factors:
• Period when measurements are active in the network element or the
measurement information is uploaded from the network element to the network
management system.
• Measurement intervals.
• Number and distribution of the network elements for which the measurement is
activated.
Defining thresholds
Network management systems allow you to define thresholds for the
measurements. When a measurement value exceeds a threshold, an alarm is
raised. So, you can follow the status of network performance with the fault
management applications in which the alarm is visible and also with the
performance management applications in which the measurement information is
processed. The details of defining thresholds mostly depend on the OSS solution.
Collecting data
The measurement information can be preprocessed in the network element,
depending on the NE type and the configuration of the NE. If preprocessing is
applied, the data is filtered, that is, not all of the measurement information is
forwarded to the network management system) or some calculation is done on the
measurement data before it is uploaded to the OSS through the NE-specific
interface.
The data can also undergo further processing in a post-processing phase, for
example, when busy hour information is needed for a report. The results of the post-
processing are also stored in the OSS database. The data is used by the reporting
applications or is exported through the open interfaces to external systems.
Monitoring network performance

You can typically find performance-related problems by checking the alarms, the
measurements, and the customer complaint reports. You also can use information
from drive tests and Call Detail Reports (CDRs).
Regular reporting such as running a report once a day or once a week is too slow
for continuous network monitoring. Furthermore, the default measurement interval
for most counters, one hour, may create a huge delay. However, you can also
analyze the traffic statistics and collect detailed information from the network for
further analysis with reports when you discover a problem. Prompt reaction is
sometimes required. So, it is recommended that you set thresholds for the
performance indicators so that the OSS raises alarms based on the indicator values
in unusual situations or when errors occur.

Generating and distributing reports

When you defined the reporting requirements, you also gathered information on the
user groups and on the types and frequency of the reports that they need. You have
to ensure that the users of the OSS have access to or receive the reports that best
support their work.
Reporter applications allow you to turn the often overwhelming amount of
measurement data into information on the performance of the resources in your
network, which you can use for determining whether the network performance goals
are met and whether problem-determination procedures should be initiated based
on performance.
Analyzing the results

PM reports are mostly used for two purposes:
• Short-term reports and ad-hoc reports to gather information for troubleshooting
and fault prevention.
• Longer-term reports for developing the network and the services.
For example, the top management of an operator can use PM reports for obtaining
high level information on the network operation at a glance. It is possible to use a
report about the length of the calls to determine whether the service is becoming
more or less popular among the subscribers and in what times of the day
subscribers use particular services the most. The call durations plotted against the
day gives information on the preferences of the subscribers and helps you decide
about marketing campaigns, special rates for busy hours or off-peak hours.
You can also monitor whether a network expansion has the expected results on the
quality of services by regularly checking your own customized reports. With regular
checks you can avoid significant negative impact by taking corrective actions as
soon as deviations are observed in the quality of the service. When you have to
optimize your network or when you consider an expansion, you can use various PM
reports to gather information on the past.
You can also use the reports for monitoring the network performance over a certain
period of time and check how the QoS and other quality objectives are met and
identify possible problem areas in the network. For optimization, for example, you
might need detailed quality information on particular measurements in a particular
BSS. For expansion and planning, you might need a less detailed report but over a
longer period of time to observe trends in the subscriber behavior or network
resource usage.

247
Purpose of Performance Management
The aim of any performance management activity is to collect data to support the
following activities:
• Verifying the physical and logical configuration of the telecommunications
network.
• Monitoring continuously how the network functions.
• Localizing potential problems as early as possible.
• Monitoring subscriber behavior.
• Providing optimum services to mobile subscribers.
Depending on how the performance management applications use the collected
data, they can be divided into two main types: performance monitoring and
performance reporting applications. Performance monitoring is online-oriented and
provides you with relatively real-time information on the network. So, performance
monitoring applications generally use shorter measurement output intervals because
faster reaction is needed in severe problem cases, in which a 24 hour interval would
be too long. The outputs of performance monitoring applications are mainly used as
additional information for problem cases in which no alarm information is available.
Performance monitoring rules are intelligent threshold rules and can be calculated
before or after the measurements are stored in the database.
Performance reporting is offline-oriented and provides information on what
happened in the network over a certain period of time. Performance reporting
applications mainly rely on counters, kpis and produce reports, which you can use,
for example, when you are troubleshooting, planning, or optimizing the network.

Reporting Needs
Networks continuously produce an enormous amount of performance data. PM
applications need to filter the information to suit the needs of various users:
• Management and operational levels at the operator.
• Technical considerations in the network, for example monitoring the radio
access and the core network separately.
• End-user perception of the services about traffic, quality, or availability of the
services.
The following figure shows reporting needs in a combined model. Each chunk of the
pyramid corresponds to a report set or report group that PM applications can
provide to the various user groups.
The applications allow turning the often overwhelming amount of measurement data
into information on the performance of the resources in your network, which can be
used for determining whether the network performance goals are met and whether
problem-determination procedures should be initiated based on performance.
Various user groups can use performance measurement data for managing the
network and what kind of PM applications they can use depend on the objectives.
Figure 166: Reporting Needs
Performance Management User Groups

The following tables represent the Performance Management user groups:

249
Table 14: Using Performance Information - User Groups 1/5

User Group PM Objectives Report Needs Report Type
• Monitoring the
current
network status
with ad-hoc • Monthly or
reports longer periods
• PLMN-level
• Forecasting information • Historical
future trends condensed in information,
with longer- few reports trends
term reports • Mainly about • With graphs
• Following the trends
Top Management • For example,
trends of the • In graphical network
network format outages of the
development, last month
for example, • Mainly offline
(number,
monitoring report
length, and
QoS and generation
number of
usage affected sites)
statistics of
various
services


• Higher-level
information
with drilling
possibility to
problem areas
• Observing • Checking daily
subscriber the most • Weekly or
behavior and important monthly, with
capacity counters at the more details
issues from PLMN level or on the last day
longer-term for each or week
reports based maintenance
Technical • Graphs or
on QoS and region, and if
Management and tables
usage necessary, for
Marketing statistics • BSC level is
each NEs
important
• Planning new • Tracking
services by measures and • For example
analyzing the observations service usage
recent and accurately to statistics
current trends monitor, for
example, the
MSC, BSC,
and BTS
levels
separately

251

• Low-level
information
• Detecting and easy
faults by access to all
enabling the counter
measurement- information
based alarms
• Fast • Daily KPI
• Localizing navigation,
potential reports,
switching especially on
problem areas between
by evaluating failing NEs
Operations and counters,
longer-term when checking • Mainly textual
Maintenance
reports on for particular and some
network counters in a graphical
coverage certain reports
• Solving faults network
by using PM element or a
reports for group of
root-cause network
analysis elements for
troubleshootin
g


• BSC and MSC
level that can
• Monitoring be processed
network into traffic
capacity by profiles to
evaluating provide
longer-term information on
reports on the subscriber
use of network behavior and
resources the overall
• Tendency
performance
• Monitoring reports at
of the network
network quality higher or lower
and the
by evaluating level,
network usage
reports that depending on
through time
include the planning
and locations
counters or work
PM Analysis KPIs about the • Quality of
• Both raw and
quality of the service (QoS)
Optimization summarized
services monitoring,
information if
Planning which can
• Verifying radio performed at
include
network the lowest
monitoring the
coverage by level
quality of
evaluating service as • Mainly textual
reports that seen by the and some
include subscribers, graphical
counters or and the quality reports
KPIs such as of the network
the number from the
and technical point
percentage of of view
hand over
failures in a • Longer-term
geographic traffic profiles
distribution to determine
pricing
strategies

253

• Informing
subscribers
about current
problems by
obtaining and
analyzing up-
to-date
information on Frequent,
the network preferably daily,
status from ad- status reports on
Frequent and
Customer Care hoc reports the status of the
regular
network and on the
• Responding status of failing
more quickly NEs
to service
complaints by
identifying the
cause of
network
problems

Counters, Measurements and Observations

The counter, measurement and observation are discussed in detailed as follows:
• Counter
A counter is a register which is updated in the NE each time an event occurs.
There are different types of counters based on how they can be updated.
Cumulative counters represent a running count of, for example, how many times
an event occurred while gauge counters take the value of what they measure,
for example how many data packets are in a buffer.
When a measurement interval ends, the values of the measurement counters
are transferred to the OSS and the counters are reset for the next period.
A counter provides the result in specified units, for example, in integers or
Erlangs. The term counter is used as a synonym of Performance Indicator.
• Measurement
A measurement is an action where the system collects information about, for
example, traffic and network events and then processes this information.
A measurement is a fixed set of counters.
• Observation
An observation is a function where the system either collects information about
certain events or directly produces information about single events in the
system.
It is possible to set certain objects under observation and to set conditions which
must be fulfilled before the system produces reports or alarms.
Observations are typically used to locate the part of the network system causing
problems.
A measurement is in fact a collection of statistics, or to be more precise, a collection
of counters. All of these counters are counting a particular event that relates to the
measurement name. The measurements are grouped in this manner to allow better
functionality and handling. This provides the user with easier selection of certain
measurements necessary at a particular time. All measurements are independent of
each other but the same user interface is used for handling all measurements.
Each network element can have only one instance of each measurement running. In
other words, the measurement is either active or not. Each measurement has a
reporting period, therefore at set intervals, each counter will return with a value for
each object.
The output interval determines for how long counters are collected into a
measurement. Measurements can be collected at regular intervals: 15 - 30 - 60
minutes, 2 - 3 - 4 - 6 - 12 - 24 hours.

255
Figure 167: Traffic Measurements and Counters

Logical Counters and KPIs

A Logical Counter is a formula which combines, with arithmetical operations, data
collected from measurement counters. Logical Counters that describe the most
important aspects of the network operations are referred to as Key Performance
Indicators (KPIs).
A KPI can also include counters from different measurements. The
measurements/counters must, however, all be of the same object level for you to be
able to include them in one KPI.
The operators decide individually what the KPIs are when they define the contents
of the reports.
Figure 168: Logical Counters and KPIs

257
Key Performance Indicators and Reports

Network performance can be evaluated based on KPI. The users finally decide what
key performance indicators are used when they define the contents of the reports.
Key performance indicators use the counters received from one or various
measurements. To create formulas, all the measurements used in the formula must
be activated, and in addition, the measurements have to have the same output
intervals. In case the measurements have different intervals, the measurements can
be examined only according to the longer intervals.
For example: Data is received from two NEs. The interval for one NE is set to be 15
minutes and the interval for the other NE is one hour. The KPI values can then be
examined only with the minimum time period of one hour.
Figure 169: KPIs and Reports

Knowledge Check: Performance Management Concepts

• What groups inside an organization can benefit from the PM data and why?
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
• Explain what is KPI?
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________

259
NetAct Performance Manager tools

Performance Management system
Performance Manager acts as the centralized data warehousing solution where
applications can find a holistic and vendor agnostic view of the network’s
performance and where reports can be defined on the fly using advanced tool sets.
Performance Manager is delivered with a set of comprehensive pre-defined reports
and KPIs that meet the most common customer needs and allow immediate use of
product.
Data is collected from multiple systems and placed in one centralized data
warehouse.
The received data is then transformed to the NetAct Base native PM data format.
Required conversion configurations or scripts are part of the respective adaptation.
Once measurements are inserted into the NetAct Base database the respective data
is available for further reporting and usage.
The following figure illustrates the PM data flow:
Figure 170: PM data flow
Part of NE Integration: The network element has to be configured to send
measurement data by using the NetAct application
Administration of Measurements.

Performance Manager tools
Figure 171: Performance Manager start page
A menu bar is located at the top of the main window and provides access to system
wide functionalities or tools. These are as follows:
• Navigate ► Reporting Suite: This view displays the default content delivered
by Nokia. Only administrators can customize this content, create and publish
shared reports in the tree for all users. The customization is performed via
Reporting Suite Publisher.
• Navigate ► Saved reports: Allows browsing the reports and dashboards
created by the users and stored in the system for future visualization and
execution.
• Reporting Tools ► Report Creator: Is used to create reports in a faster and
easier way through a GUI wizard that guides you through all the required steps.
• Reporting Tools ► KPI Creator: Allows you to create and change KPI
formulas.
• Administration ► Publisher: Allows you to publish your reports in the
Reporting Suites tree.
• Administration ► Scheduler: Allows the user to define a timetable to run a
specific report.
• Administration ► Reporter Admin Toolkit: Administration of multiple servers
can be very complex, since there are many configuration files that need to be
synchronized. With this application, administrators can easily configure PM pipe
settings in a graphical user interface.
• Administration ► Thresholder and Profiler: You can define thresholds and
rules on performance counters or KPIs.
• Preferences: Users can define their own preferences regarding the application
look and feel and behavior

261
The Home area is the default view presented after a successful login. The menus
are available on top. When the user starts navigating, the areas are kept in tabs at
the bottom in the View Bar and the user can always access the opened areas with
all the settings previously defined. The arrow on the left side of the View Bar allows
toggling it.
Figure 172: Performance Manager GUI
The navigation tree on selected pages provides, for example, choices of
object to select when the task is to view, edit and/or save.
Figure 173: Performance Manager tools

Performance Manager start page

To be able to prevent problems in the network before they occur, it is important to
have a good understanding of the data as well as powerful tools to sort out the most
important indicators.
With Performance Manager, operators can view and analyze the network
performance data coming from different sources. Raw data becomes meaningful
information that is aggregated and visualized in graphical and textual reports. KPIs
are the most important indicators of the network’s performance. KPI reports allow
the operator to detect the first signs of performance degradation, prevent the
development of critical network problems, troubleshoot specific elements and
analyze performance trends.
Performance Manager provides a wide range of functionalities and reporting tools
that are targeted for all user groups of a performance management system. These
functionalities and tools are described in the following sections.
Performance Manager Functions

The Performance Manager enables the user to:
The easy-to-use GUI allows executing general web configuration, advanced
reporting, threshold supervision, profiling and trending on long term raw and
aggregated data. With the web portal functions, the users are able to:
• Configure web page user preferences.
• Create and edit reports, for private or public usage with Report Creator.
• Create and edit KPIs, for private or public usage with KPI Creator.
• Browse for existing KPIs and reports.
• Customize dashboards with tables and multiple chart types.
• Schedule reports and distribute them via email in CSV or XLS format.
• Customize the web portal look and feel and setup user's preferences.
Reporting functions
The following specific reporting functionalities are available in Performance Manager
portal:
• Table and chart report views
• Export to Excel (table and chart views) and CSV (table view only)
• Saved Reports and Report Navigator (act as bookmarks in the reports tree)
• Report documentation (including KPI formulas)
• Report scheduling
• Data Reliability
• Table filtering
• Advanced filtering
• KPI thresholding within reports
• Drills
• Time overlay

263
• Top N analysis
• Multi-technology & multi-vendor reports

Lab exercise: Performance Manager tools

Context
This section tests the students to explain the purpose of the Performance Manager
tool.
Procedure
1 Login to NetAct and at start page.
2 Navigate to Performance Manager application.
Result of this step

What is the general purpose of the Performance Manager?
Write down the functional tabs you can see at the top level.
The Navigation menu, provides users with access to already created reports.
What is the difference between the Reporting Suite View and the
Saved Reports View in the Navigation menu?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

265
Knowledge Check: Performance Manager applications

• Describe in general terms, how PM data is collected and processed in NetAct
and how data is available to be used by the reporting applications.
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
• How Network Elements’ traffic measurements are administrated?
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________

Create, customize and generate performance management

reports and dashboards
Creating reports
Context
The Report Creator is used to create reports in a faster and easier way through a
GUI wizard that guides you through all the required steps with a minimal number of
clicks and user decisions.
The functions and services available in the report creator tool:
Figure 174: Creating reports

267
Procedure
1 Select the technology, network object or hierarchy of network objects for which
the report shall be produced.
Information
After selecting Reporting Tools ► Report Creator you have to select in the
following order: Technology, Hierarchy, Report Level and Object.
The list for KPI or Counter Selection should contain at least 5 items.
Use * wildcard to match any character. There is no limitation on the
number of wildcards used. Select multiple objects using the Shift (to
select several consecutive objects) or Ctrl (to select several non
consecutive objects) keys. You can only select a maximum of 20
objects.
a) Select Edit Configuration Management Selection.
Information
This optional tab is only available for 3GRAN and LTE radio and allows to
select configuration parameters for the selected object.
b) Select the time period in which the report runs by clicking on the
Edit Time Selection button.
Information
On selecting one option in the Hierarchy, the corresponding Object Level is
automatically selected to increase the navigation speed. User is able to
change it afterwards if needed.
Result of this step

A new window opens to define the time period.

2 Select the time level that shall be used in the report.
Information
Time Level The Time Selection panel allows you to select the

time granularity for the report.
Time Type has three options:
Relative The time period queried is the time period of the
server time zone.
Absolute The time period queried is the local user time
zone. If the server is in a different time zone you
may find useful to adjust the local user time.
Real Time You can define the time period in minutes (Look

back period) from current time that monitors in a
Real time report. If, for example, you define the
Look back period to 50 minutes, the report shows
historical data from 50 minutes back to the current
time and adds new data until the maximum default
of 120 minutes time interval window. After this,
older data is removed from the report, always
keeping the 120 minutes maximum window.
Selected Time Level must be RAW.
After defining the time Level/Time Type you have to select the counter for the
report (KPI/Counter Selection or Edit KPI Selection).

269
3 Select the KPIs, KPI groups, counters and previously defined reports to be used
or included in the new report that is being created.
Information
When selecting a KPI, a counter or a report, the info box below the list of items
displays specific information on the selected item (for example, name,
description, formula of the selected KPI).
In the KPIs pane, you can add to the report the available KPIs, which are listed
alphabetically.
In the Counters pane, you can add the available counters.
In the Reports pane, you can add KPIs from predefined reports. The reports are
grouped into different purposes and available in the drop-down list. When you
select the report group, the KPI list is populated accordingly.
4 Preview and save the report.

Saving and generating reports
Figure 175: Preview Reports window
The next step allows you to preview the report. In this step you can:
• Name the report.
• Provide a textual description of the report.
• Configure the report as private (access limited to the creator and administrator)
or shared (other users allowed to access it).
• Save the report.
• See how the display of the report looks like. You can also experiment changing
the visualization options of the data (for example, change from table view to
chart).
• Trigger the report execution (generate).

271
Figure 176: Save Report Window

Real-time PM display with dashboards
Figure 177: Real-time PM display with dashboards
The features of real -time PM display with dashboards are as follows:
• It is possible to add RTPM reports to the dashboards.
• Dashboards support for 1 minute auto-refresh (configurable).
• Auto- refresh options is saved together with dashboard definitions.
• No scrollbars in the dashboards charts, or if they are there, the location of the
bar is memorized.
• Main settings of the dashboard and its panels are kept after refreshing (for
example, layout, output type and axis limits).
• Quick reactions to upcoming problems in SDM network.
• Avoidance of network outages.
• Abstract PM monitoring can be a powerful tool for experienced SDM network
operators, to see dependencies that current automatic threshold tools cannot
detect.
• Improved user experience.
Supported Network Elements

• NT HLR
• One-NDS
• One-AAA
• CMS-8200 FE (HSS FE)
• CMS-8200 SLF
• CMS-8200 DRA
• CFX-5000 (CSCF)
• PCS-5000 and Flexi NG

273
Rehoming support for 2G and 3G
Figure 178: Rehoming support for 2G and 3G
In mobile network operations a rehoming is the reassignment of the network
elements to a different parent in the topology.
Rehoming support enables the operator to have automatic update on the PM reports
every time a network objects moved from one location to another location in 2G and
3G networks.
Historical data is preserved for the rehomed object allowing continuous and
consistent reporting.
• Reports for a region will always reflect the correct data.
• Transparency to the tool end user, no difference noticed between a rehomed
object and a regular one.

Lab exercise: Create report for active user equipment with category 5 for
MRBTS
Context
Execute the following steps for creating report for active user equipment with
category 5 for MRBTS:
Procedure
1 Select Reporting Tools ► Report Creator.
2 Select LNBTS-NSN LTE Base Transceiver Station under the

NSN Adaptation Support folder in the Technology pane.
3 Select PLMN/MRBTS in the Hierarchy Panel.
4 Select MRBTS in the Object Level Pane.
5 Select the available NE which appears in the Object Filtering Pane.
6 Click on Edit Configuration Management Selection.
7 Skip the CM Parameter Set Selection and click on Edit Time Selection.
8 Select HOUR in the Time Level Pane.
9 In the Time Type Pane select: Relative, 1 day and Last Midnight.
10 Click KPI/Counter Selection.
11 Click Counters ► LTE Cell Load of the filter.
12 Choose the counter ACTIVE_UE_CAT_5_AVG and move the counter into the
Selected KPIs/Counters plane by clicking the button.
13 Click Preview Report.

275
14 Enter a name for the report and click Generate & Save.
15 Save it under MyReports.
Information
If needed generate a new folder with this name.
Result of this step

The following screenshot is the result of the data table:
16 Change the output type by clicking on the gear and choose
Output type ► Line Chart.
Result of this step

Creating Dashboards
Context
This functionality gives you the ability to add arbitrary and independent report panels
into the same dashboard view. It acts as a blank canvas for grouping various
reporting panels within the application.
You can easily create new dashboards or add panels to existing ones. That can be
easily done by selecting the corresponding option in a panel belonging to a
generated report.
Figure 179: Add to Dashboard
Not for Real Time.
Procedure
1 Generate a Report.
2 Add Panel to new, existing or active Dashboard.
3 Click Save.
4 Save and name it.
Example
The following screenshot shows three panels in a single dashboard:

277
Figure 180: Display reports in Dashboards - Three Panels in Dashboard

Viewing and customizing reports

Context
Execute the following steps to view and customize reports:
Procedure
1 Select Navigate ► Saved Reports and click on selected Report.
Result of this step

The following screenshot shows the report result in form of a data table:

279
2 Customize Reports.
Information
The following screenshot depicts the Output Type available:
The following screenshot shows an alternate viewing option:

Report Navigator
The Report Navigator allows you to display, search and access all user specific and
shared reports stored in the system.
The Report Navigator is accessible via the Explore option within the list of saved
reports.
Select Navigate ► Saved Reports ► Explore and select Report to
customize.
Figure 181: Report Navigator
The Report Navigator allows you to:
• Search reports based on user specified criteria
• Trigger reports execution
• Schedule reports
• Edit report details and parameters
• Share the report with other users
• Save the report with a different name (for example, for customization purposes)
• Delete reports
• Export reports
Figure 182: Report Navigator - Customize report

281
Report Suite Publisher
Figure 183: Report Suite Publisher - Publish report
The Report Publisher tool allows you to publish your reports in an own folder in the
Reporting Suites tree if you had shared your report before.
It comprises a very convenient filtering panel, which helps you to quickly locate the
report to be shared.
Select Administration ► Publishers ► Reporting Suite Publisher.

Lab exercise: Report Creator

Context
Perform the following steps create a report for a specific counter:
Procedure
1 Open Report Creator and filter for an MRBTS.
2 Create and generate a hourly report for the Active TTI based on the two
counters for the last three days back from last midnight.
3 Search for the counters ACTIVE_TTI_DL (M8012C90) and ACTIVE_TTI_UL
(M8012C89).
4 Change the Output Type of the report to Line Chart.
5 Share the report for other users.

283
Summary: Basic Performance Management with NetAct

Module Summary
• Explain the purpose of Performance Management and describe what is KPI.
• Explain the Performance Manager tools.
• Create, customize and generate performance management reports and
dashboards.


Advanced Performance Management
285

Module Objectives
• Create, modify and publish KPIs.
• Manage preferences and schedule reporting.
• Set threshold values for alarms.
• Create and activate measurement plans.
Create, modify and publish KPIs

KPI Creator introduction
The KPI Creator tool allows you to create and change KPI formulas and has the
following features:
• Technology-based KPI creation
• Create/Edit Custom KPIs from existing KPIs/Counters
• Source KPI/Counter Search and Filter options
• ORACLE® functions support
• Automatic Divide-By-Zero checks
• Custom KPIs available for use in Reports
• Delete Custom KPIs
• KPI Title and Unit specifications for the Report Output
• KPI Formula validation
Select Reporting Tools ► KPI Creator
The following figure illustrates the steps to create KPIs:

Figure 184: Create KPIs

287
Creating KPIs
Context
Perform the following steps for creating a KPI:
Figure 185: Procedure: Creating a KPI

Procedure
1 Select the KPI technology from the drop-down list. If the KPI list is not
automatically updated, click the Refresh button.
Information
In the KPI Selection tab, the available KPIs are listed alphabetically, according
to the technology selected.
2 Insert a name up to 30 characters.
Information
The Name is a mandatory field and must be unique.
3 Insert a title and choose the unit.
Information
The Title is a mandatory field and is useful to identify the KPI column header.
The Unit is also a mandatory field and all the available units for the custom KPI
are provided in the drop-down list.

289
4 Click the Formula Options tab and select the KPIs or Counters, or both.
a) Click the arrow button to insert the formula in the text box.
Information
The Formula is a mandatory field and is fully editable.
To filter the KPI list type the KPI name in the text box. The filtering is dynamic
according to the KPI name written.
To use the KPIs formula in the custom KPI, select the desired KPI and click the
button. The formula is copied to the Formula field in the KPI Editor area.
If you want to reuse all KPI information select the desired KPI and click the
New from Selected KPI button. All the KPI information is copied in KPI Editor
area fields, but the word ‘New’ is added to the name and the title fields, since
the system KPIs cannot be edited.
By clicking the New button, all the fields in the KPI Editor area are
deleted and it enables you to start editing a new KPI.
You can delete custom KPIs by selecting the KPI and clicking the
Delete Custom KPI button.
If you click the New from Selected KPI button the information from

that specific KPI is added to the KPI Editor area and all fields are
editable.
To filter the Counters list, type the counter name in the text box. The
filtering is dynamic according to the counter name.
To use the counter formula in the custom KPI, select the desired
counter and click the button.
The formula is copied to the Formula field in the KPI Editor area.
Check the Use NVL flag if you want to use the counter formula with
the NULL VALUE LOGIC function applied, which replaces a value
when a null value is found.

5 Insert the operators in the formula or select from the Functions tab.
Information
The Functions tab allows you to use pre-defined functions in the custom KPI
formula.
In the Name selection box, select the desired function and click the
button.
The function is copied to the Formula field in the KPI Editor area. The Usage
description box is available below the Name selection box and provides
additional information on the selected function.
The description box includes the syntax, expression, conditions, results and
other information, depending on the selected function.
The following operators are accepted:
• Addition
• Subtraction
• Multiplication
• Division
• The parentheses are also valid and help the creation of more complex KPI
formulas.
6 Enter a KPI description in the Description field.
Information
It is visible to all users. The Description is an optional field and is useful to
describe in more detail the KPI usage and the KPI formula.
The Permission is a non-editable field and informs if the editing KPI is private
(not published) or public (published).

291
7 Click the Validate button to validate the formula syntax and all the mandatory
KPI fields in the KPI Editor area.
Information
If some field is not valid, a pop-up window is displayed, informing which field is
not valid. The KPI Publisher tool can be used to share the KPI with other users.
8 Click the Save button to save the KPI.
Information
A quick validation of the KPI fields is performed before saving the new KPI
information.

Example KPI creation

The following shows a formula to calculate the ratio between the number of active
users and the number of the RRC connected users in a cell:
Figure 186: Example: Formula for KPI creation
Unit is in %.
SUM_ACTIVE_UE This measurement provides the sum of sampled values
(M8001C320) for measuring the number of simultaneously Active UEs.
This counter divided by the denominator
DENOM_ACTIVE_UE provides the average of Active
UEs per cell.
DENOM/ACTIVE_UE The number of samples taken for counter
(M8001C321) SUM_ACTIVE_UE used as a denominator for average
calculation.
SUM_RRC_CONN_UE This measurement provides the sum of sampled values
(M8001C318) for measuring the number of simultaneously RRC
Connected UEs. This counter divided by the denominator
DENOM_RRC_CONN_UE provides the average number
of RRC Connected UEs per cell.
DENOM_RRC_CONN_ The number of samples taken for counter
UE (M8001C319) SUM_RRC_CONN_UE used as a denominator for
average calculation.
The following screenshot is an example to create own KPI:

293
Figure 187: Creating KPIs using formula

KPI Publisher
By default, it is not visible to anyone except the user who created the formula. The
KPI Publisher tool described in the following chapter can be used to share the KPI
with other users.
Select Administration ► Publisher ► KPI Publisher.
Figure 188: KPI Publisher
• The administrator can define the general policy for the KPI visiblity:
private or public. By default all the KPIs are created as private.
• This is done via configurator file and applicable to all the new KPIs
created after the configuration change.

295
Lab exercise: Creating, modifying and publishing KPI

Context
Perform the following to create and modify a KPI using the formula provided:
Prerequisites
Check that the Radio NEs (MRBTS) are available.
Procedure
1 Create a KPI using the following formula:
Information
Active user equipment with Category 5 + active user equipment with Category 8.
2 Validate and Save the KPI.
3 Modify KPI.
a) Open the existing KPI and modify KPI title using the formula description.
Information
Active user equipment with Category 5 + active user equipment with
Category 6.
Active user equipment with Category 7 + active user equipment with
Category 8.
4 Validate and Save the KPI.
5 Publish the KPI.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________

Manage preferences and schedule reporting

Preferences
The Nokia Performance Manager users can define their own preferences regarding
the application's look and feel and behavior such as:
• Define the default view displayed when the user logs in the application.
• Define the colors to be used in the report charts.
• Filter out the colors that cannot be recognized by color-blind users.
• Define the application theme, which determines, for example, the colors of the
menu bars, fonts and backgrounds.
Figure 192: Preferences
The administrator can set the presentation pattern for Measurements,
counters and KPIs centrally in the configuration file. This pattern is then used
throughout the PM application (Report and KPI creator).

297
Report Scheduler
This functionality shows all reports which were created with the option Schedule
Report.
After starting the Schedule Browser you get a timetable to modify scheduled
reports is displayed.
The list of scheduled reports is managed through the schedule browser window
(administrator privileges required). All the reports scheduled through the report
scheduler are listed within this window.
The schedule browser works as cockpit or control center for the management of all
scheduled reports. The administrator can:
• Access detailed information on the scheduled report (for example, report
information, schedule details, current execution status).
• Trigger the report execution according to the defined schedule.
• Pause the report schedule execution .
• Edit the schedule.
• Delete the report schedule.
• Filter the list of schedules (all, running, paused).
This level of control allows the administrator to check and approve the scheduling of
each report execution making sure that the execution of the scheduled reports does
not affect the daily operations of other users.
Select Administration ► Scheduler.
Figure 193: Report Scheduler - Schedule Browser

Lab exercise: Scheduling a report

Context
Perform the following to schedule a report:
Prerequisites
Check that the Radio MRBTS are available.
Procedure
1 Choose a report for scheduling from the saved reports plane.
Information
Schedule a report with the following parameters:
Run daily starting Monday this week ( choose actual date) at 10 pm every day.
Report should be sent to email address (for example, me@mywork.com) in xlsx
format.
2 Explore the report.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

299
Set threshold values for alarms

Thresholder and Profiler
You can define thresholds and rules on performance counters or KPIs. When a
threshold has been crossed, an alarm notification is created and can be either
forwarded through the Fault Management system or via SMS/e-mail.
This allows for proactive performance monitoring where the operations department
is actively alerted on potential network problems rather than having to manually
analyze various different performance reports.
Select Administration ► Thresholder and Profiler
Figure 197: Thresholder and Profiler - Define thresholds

Lab exercise: Object selection

Context
A minor alarm should be generated if the average number of active UEs with UE
Category 5 (active_UE_CAT_5_AVG) falls below 10 within 1 hour.
Perform the following steps to select an object:
Prerequisites
You need to click Administration ► Thresholder and Profiler.
Procedure
1 Select LNBTS-NSN LTE Base Transceiver Station in the Technology Pane.
2 Select PLMN/MRBTS in the Hierarchy Panel.
3 Select MRBTS in the Report Level Pane.
4 Select the available NE which appears in the Objects Pane.
5 Click on Edit Time Selection.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

301
Lab exercise: Time Selection

Context
Perform the following steps to select an object:
Evaluation period Time interval in which report is re-executed to check

for new values. It can also be seen as the period
duration.
Evaluation delay Delay between the period ends and the report is

executed in order to fetch data that comes late. If
the delay is set too low, there is no PM data in the
database for the corresponding KPIs/PIs and that is
why no threshold violations can occur.
Procedure
1 Select HOUR in the Time Level Pane.
2 In the Time Type Pane select: Evaluation Period and Evaluation delay.
3 Click Edit Alarm Settings.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Lab exercise: Alarm Settings

Context
Perform the following steps to modify the Alarm Settings:
Figure 198: Threshold and Profiler - Alarm Settings
Procedure
1 In the Counters pane browse for, LTE Cell Load and select

ACTIVE_UE_CAT5_AVE.
2 In the Formula creation pane, click on Minor.
3 With the add button, the selected counter is shifted to the Minor field.
4 Create the formula <10.
5 Click Edit Threshold Information and Notification.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

303
Lab exercise: Threshold information and notification

Context
Execute the following steps to set the Threshold information and Notification:
Supported alert methods are:
• Alarm forwarded to the fault management system.
• E-mail notification sent to a configurable address.
• SMS sent to a configurable telephone number.
Procedure
1 Define a name for this threshold.
2 Activate check box so that the threshold alarm appears in Alarm List.
3 Define a new Alarm id for this alarm.
4 Define Alarm text for this number.
5 Save it.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

Create and activate measurement plans

Administration of Measurements
Administration of Measurements (AoM) application enables you to manage
(enable/disable) measurements on network elements to allow data collection from
network elements to NetAct.
This application can be used to view, create, modify and delete measurement plans
and templates.
Measurement plans can be used to start and stop the measurements on the network
elements. AoM also helps to upload measurement plans from the network elements
to NetAct.
Figure 199: AoM-Start window
The tool contains four tabs. These tabs are as follows:
Network Overview It enables you to view the activation status of
measurements in the network.
Plans It enables you to create, modify, delete, activate and
deactivate plans.
Templates It enables you to create, modify and delete a template. It
also allows you to create a plan based on an existing
templates.
Operation Overview It enables you to view a summary of all the operations

carried out during a specific time period for specific NE
types.
Before we prepare a plan for activation we have to find out the relevant counter for
our measurement and the related measurement type.
This can be done easily using Object Information Browser.
Figure 200: Object Information Browser

305
Creating plan
Context
A plan enables you to select and schedule measurements and counters in a single
network element.
You can also create a plan based on an existing template by adding specific plan
parameters such as network element instances and start or stop dates. This allows
an administrator to define a template, for example, for each network element type.
Other users can create plans for the specific network element instances using the
existing template.
Creating a plan is done in three steps.
Procedure
1 Click on New in the Plans tab to open the configure schedule items.

2 Configure schedule items.
a) In the Name field, enter a name for the plan.
b) In the Description field, enter the description for the new plan.
c) Select an Adaptation from the drop-down list (see in application
Dynamic Adaption on NetAct startpage). An Adaptation provides the
interface through which data originating from network elements enters NetAct
and can be handled by NetAct applications.
d) Select a measurement type from the Measurement type checklist.
e) Define schedules for the selected measurement type.
f) Click Add to List (List of available measurement types). A list can contain
one or more measurement types and/or adaptions.
g) Press Next to continue with Step 3.

307
3 Add managed objects.
a) Select the supported MO class means the specific product and the release.
Information
For example, MRBTS-FLF16.
b) Select the Measurement type and the Managed object.
Information
For example, LTE Cell Load for MRBTS-38.
c) Click Add to List (List of available managed objects).
d) Click Save.

Activating plan
Context
The measurements in the uploaded plans are active in the corresponding network
elements.
Perform the following steps to open the Plan tab in Administration of Measurement
application:
Procedure
1 Select the plan name by checking the selection box.

309
2 Press Activate to confirm activation.
Information
This process may take several minutes.
Result of this step

The Operation Overview screen opens and you can check the status of the
activation.
Result
The measurements in the uploaded plans are active in the corresponding network
elements.

Lab exercise: Creating new measurement plan for LTE cell load
Context
Perform the following to create a new plan:
Prerequisites
Check that the Radio NEs (MRBTS) are available.
Procedure
1 Create and activate a plan for LTE Cell Throughput.
2 Check the measurement details in the Object Information Browser.
Post-requisites
________________________________________________________
________________________________________________________
________________________________________________________

311
Summary: Advanced Performance Management

Module Summary
• Create, modify and publish KPIs.
• Manage preferences and schedule reporting.
• Set threshold values for alarms.
• Create and activate measurement plans.


Configuration Management
313
Module Objectives
• Explain the purpose of Configuration Management.
• List the NetAct Configurator applications and explain their purpose.
• Use the Configurator tools for executing basic tasks for configuration
management.
• Explain the Radio Optimization Process in NetAct and the main
functionalities of Optimizer.
Configuration Management in NetAct

Overview
NetAct Configurator is a component in the scalable NetAct framework for operating
mobile networks. Configurator gives access to real-time network configuration data
and provides tools to manage network configuration.
The main functionalities of NetAct Configurator are:
• Storing the network parameters in the database
• Data exchange with external tools
• Setting, modifying, viewing and comparing network configuration data
• Mass modification on the network: integrating sites, extending and optimizing
the network
• Tuning of the network configuration
The network architecture can be functionally grouped into the access network and
the core network. The access network handles all radio-related functionality while
the core network is responsible for routing calls and data connections to external
networks. With NetAct Configurator, the access network and core network are
managed in a centralized way.
Figure 201: Configuration Management Overview

Configuration Management Process

NetAct Configurator is a fully integrated application which provides common
configuration management functionality for multi-technology networks.
Single data storage, common applications and processes enable efficient and
reliable management of complex networks comprising of different technologies.
High operational efficiency is achieved through:
• Automated processes
• Mass operations
• High network quality through
• Reducing human errors
• Working on use case and data level
• Several data auditing options
The following chart shows the basic process of Configuration Management in
NetAct:
1. By uploading configuration, the operator gets the current active operative status
of the network (network elements). This information will be the base for all
configuration activities.
2. Configurator provides different tools for creating and checking the desired
configurations on the network level, ranging from single parameter changes up
to complete network configurations.
3. The provisioning activities are carried out by Configurator after operator
confirmation on demand or scheduled, being able also to create also fallback
configurations as a backup for the changes executed on the network.
Figure 202: Configuration Management Processes

315
Configurator Basic Concepts

The Configurator applications in NetAct use a group of basic concepts which
describe the network and the actions that those tools execute on it.
The Network resources are represented as managed objects in NetAct.
Configurator supports managed object classes in the core network.
The actual configuration refers to the current configuration of the managed
network. There is only one actual configuration in the system.
The changes to be executed on the actual configuration are implemented using
plans. A plan contains a configuration change that will be performed or has been
performed to the network.
The reference configuration is a data set that describes the desired or the target
configuration of the network for comparing it with the actual configuration due to
consistency checks.
When the network is expanded and optimized, templates offer ready-made
parameter sets for defining new managed objects in the network. Templates allow
using patterns in object creation and decrease manual typing.
The consistency of the network parameters is vital for the optimum functioning of the
network. Configurator provides rules and tools to check the consistency of the
actual configuration or a single plan.
Site template mechanism allows you to create a base station configuration model
and use this configuration model when generating configuration data for a new base
station. Site templates are applicable for GSM, WCDMA, LTE, and Single RAN
managed objects.
The benefit of the mechanism is that the user needs to define only a few mandatory
parameters for a new base station, whereas the rest of the configuration is
automatically generated by Configurator. The user can define the scope of managed
objects and their parameters included in the site templates. Additionally, there are
functionalities for import, export, create, modify and delete site templates.
Site templates can be generated from the actual or planned configuration. The site
template functionality is part of the autoconfiguration and autoconnection
functionality.
Figure 203: Configuration Management Basic Concepts

Managed Objects
The commonly used definition of Managed Object is also applicable within the
context of Configurator:
A Managed Object is understood as an abstract representation of a network
resource, where the resource can either be a physical entity or a logical entity.
A Managed Object Class defines the information model of a network resource type
(For example, BTS information model). Information model in this context includes:
• Overall information about the network resource (network resource type name,
For example, “BTS”, network resource model release, For example, “Release 1"
and so on.)
• Parameter information about the network resource (parameter name, parameter
description, parameter data type, parameter range, and so on.)
A Managed Object Instance represents a specific network resource (For example,
BTS installed in site x in region y). The representation of the specific network
resource means:
Identification information about the specific network resource (For example, fully
qualified distinguished name, supplementary identification parameters such as User
Label, Cell ID and so on.)
Parameter value data about the specific network resource.

317
Working sets
Working sets allow NetAct users to group particular network elements according to
their own criteria. One network element can be assigned to more than one working
set. Working sets are available in CM Editor and CM Operations Manager after
creating them with the Working Set Manager tool.
For more information on working sets, see NetAct Administration ► NetAct
Administration Helps ► Working Set Manager Help.
For information on viewing and filtering working sets, see Viewing the list of working
sets and managing working sets content and Selecting Working Set to be used as
filter in CM Editor Help.
The maximum number of managed objects in each working set is 100 000.
If you add new elements in the working set after having set a scheduled
upload, these new elements are not added in the scheduled upload scope.
Figure 204: Basic Concepts: Managed Objects

Configuration Types
Figure 205: Configuration Types
In the context of Configurator, the configuration is a set of Managed Objects.
Configurator supports the following types of Configurations:
Actual Configuration Set of Managed Objects that represent the current
configuration of the network (there is only one Actual
Configuration stored/managed in the system).
Reference Set of Managed Objects that represent the desired
Configuration configuration of the network (there is only one Reference
Configuration stored/managed in the system).
Plan Configuration Set of Managed Objects that represent a configuration

change that will be performed or has been performed to
the network (there is no theoretical limit as to how many
Plan Configurations are stored/managed in the system).
Planned Set of Managed Objects that represent what would be the
Configuration status of the network if a certain Plan Configuration would
be implemented (Planned Configurations are not stored
as such in the system, but instead they are calculated on
real time).
Actual configuration
The actual configuration comprises of the following:
• Managed objects, location in topology, and object identification in topology
database.
• Parameter values in Configurator database.
• Parameters with interface from Configurator to network element.
• Non-network parameters and non-network objects without a management
interface from Configurator.
• Object administrative state (locked, unlocked) in topology database.
• Object state (operational, non-operational) in topology database.

319
Non-operational objects are stored in the topology and they are not part of the active
network. The non-operational objects may have been planned for future use, or they
have been deleted from network.
Reference Configuration
The reference configuration is stored in the system as a separate data set from
actual and planned configurations. Reference configuration can describe the desired
configuration that should be kept in the network, but it can also describe the target
configuration of the network. For both cases it is possible to find out if there have
been changes in the actual configuration in the network, and if the changes are valid
and expected.
Plans
A plan is a configuration containing a set of modifications of the actual configuration.
A plan contains only modifications and it can be viewed on top of the actual
configuration.
Plans can include the following types of modifications:
• Add new managed objects with mandatory parameters (create operation).
• Remove an existing managed object (delete operation).
• Modify parameters (including administrative state) of an existing managed
object in a certain configuration (update operation). The distinguished name or
version cannot be modified using a plan. Modifying parameters of some future
version of managed object in target configuration is not possible.
Figure 206: Configuration Types and Network Plans
The figure illustrates the comparison between actual configuration and planned
configuration.

Figure 207: Actual Configuration vs. Planned Configuration
Configuration Templates
In the context of Configurator, template is a set of default values that are applicable
to a specific Managed Object Class.
Templates are useful in several contexts:
• When parameters have the same values in different Managed Object Instances
across the network
In this case the activity of populating such parameter values is extremely
simplified, as the only required activity is to fill a template and then apply the
template to the needed Managed Object Instances.
• When enforcement of a specific parameter policy is required
In this case templates can be filled with the policy requirements, those templates
then are audited against the Actual Configuration and deviations are reported.
There are two different types of Templates in Configurator:
• System Template
Is a set of default values that represent the factory presets. There is one System
Template per Managed Object Class and it is not user editable.
• User Template
Is a set of default values that represent default values applicable under user
defined conditions, For example, there can be one user template that defines
the default values applicable to a rural BTS, while there can be another user
template that defines the default values applicable to an urban BTS. There is no
theoretical limit to the number of User Templates stored/managed in the system.
Using templates
A template is primarily used to define an initial parameter set for a new managed
object by assigning a template to the object. The user can define assignments for
each planned object manually. Assignment information can also be imported as part
of the plan into NetAct Configurator. The assignment is shown as the name of the
template in user interfaces. Values from the assigned template for new managed
objects are automatically utilized by CM Applications the same way as they would
have been defined directly in plan.

321
Figure 208: Templates

Configuration Rules and Checks

During network configuration planning and plan data building, many types of
constraints and dependencies need to be noted and taken care of. The risk that a
new, erroneous, or incomplete plan harms the network functioning after activation to
network elements needs to be minimized. NetAct Configurator rules and check
functionality by CM Analyzer can be used for that purpose.
CM Analyzer contains predefined rule sets that can be used in different procedures
with network configuration. Also new rules can be added and tailored into the
system by the user. Rules can be collected into rule sets. The sets must contain an
appropriate selection of rules that can be meaningfully executed at the same time.
Rule or rule set execution is called a check in CM Analyzer.
The target of the check can be an actual network configuration, reference
configuration or a plan that is edited or built using, for example, CM Editor.
Erroneous objects and violations are shown to the user in the user interface for
corrective actions. In some cases, the correction or addition is straightforward, and
CM Analyzer is able to add automatic corrections to the plan.
Figure 209: Rules and Checks

323
NetAct Configurator Applications

Configurator Architecture
The following figure illustrates the configuration architecture.
Figure 210: Configurator Architecture

CM Editor
CM Editor provides intuitive parameter editing, both in minor parameter
modifications and mass modification purposes. In CM Editor, it is possible to filter
more than one parameter at a time. CM Editor functionality includes the following
operations:
• Managing plans: Creating, modifying, and deleting plans
• Creating, and mass creating of managed objects, editing, and mass editing
parameter values of managed objects
• Managing the actual configuration
• Viewing actual network configuration
• Send to network to make configuration changes on network elements without
creating any plan in CM Editor
• Managing administrative states of GSM, WCDMA, LTE and core network
objects
• Managing GSM routing areas: uploading and downloading Routing Area IP
Addresses from/to DNS
• Managing the reference configuration
• Managing planned and actual configuration with Table Editor
• Managing templates: Creating and deleting templates, Editing templates
• Managing maintenance regions
• Visualizations to indicate the status of the managed objects and parameters
• Backward and forward arrows to navigate between different views chosen by
the user
• Remove objects from plans to undo any changes to them
Figure 211: CM Editor

325
CM Analyzer
CM Analyzer is the tool for checking the consistency rules in the radio and core
network parameters and managed objects.
CM Analyzer functionality includes the following operations:
• Checking radio network and core network parameters and managed objects,
and ensuring that the parameters are defined according to consistency rules.
• Checking for discrepancies in actual configuration, planned configurations and
in reference configuration.
• Auto correction: defining a rule for automatic inconsistency correction.
Figure 212: CM Analyzer

CM Rule Editor
CM Rule Editor is a web application in NetAct Configurator. It enables operations to
create and delete user-defined rules in a simple way. Rules can be used in the CM
Analyzer application to check the network consistency. You can choose a desirable
template type and then follow the wizard.
Custom rules and rule sets can be defined in xml files and stored in the following
location:
$ETCROOT/custom/conf/rac/rules.
Make sure that you have access to the directory
$ETCROOT/custom/conf/rac/rules.
In the CM Analyzer user interface a custom rule looks as follows: <rule name> and a
custom rule set looks as follows: User.<rule set name>.

327
Selecting a template type

Context
In the CM Rule Editor start page you can select a preferred template.
The rule deletion performance is decreased when a number of user-defined
rules is greater than 1000.
The steps to select a template is as follows:
Figure 213: Procedure: Selecting a template type
Procedure
1 In a Search field, type a required phrase to narrow the list of the available
templates and then click on the template name.
Information
Alternatively, from the templates list, select the desired template by clicking on
the template's name.
Result of this step

The template description appears in the Rule template description field and the
Next button is enabled.
2 Click the Next button, to move to the templates wizard.
Result
You are redirected to the selected template.

Filling in the templates parameters

To create a rule, you need to follow the wizard. Each template has different wizard
steps to be performed.
Fields marked with a red star are obligatory to fill in. You can use helper for
the drop-down list fields. You can also narrow the scope of the drop-down list
by entering some letters in the text field.
In the case that the first object which you selected from the Managed object
or Managed object class combobox belongs to an external RAT, the rest of
the displayed objects belong to the chosen RAT.
Figure 214: CM Rule Editor

329
CM Operations Manager
The overall function of the CM Operations Manager is to transfer configuration data
between planning tools, NetAct Configurator, and the network. It provides both real-
time feedback and history information on the operations. Operations can be filtered
by days, hours, or minutes. Automated table update is turned off and on depending
on the number of operations.
CM Operations Manager functionality includes the following operations:
• Provisioning plans to the network
• Preparing, pre-activating, activating
• Scheduling provisioning operations
• Generating and activating backup plans
• Uploading actual configuration
• Scheduling upload operations
• Exporting actual configuration and plans
• Managing plans
• Creating and deleting plans, Importing and exporting network plans, Comparing
plans to actual configuration and reporting the differences, Validating plans
against actual or reference configuration
• Importing and exporting reference configuration
• Managing templates: Deleting templates, Importing and exporting templates
• Visualizing MML commands for R4 core network
• Executing MML commands and MML command files for R4 core network and
SGSN with built-in command manager tool.
Figure 215: CM Operations Manager

CM Reference
The CM Reference application is used for managing the reference configuration.
With CM Reference you can, for example
• initialize the reference configuration
• generate and analyze deltas
• commit the needed changes in the actual or reference configuration
Delta handling in CM Reference involves various steps. In the first stage, you need
to initialize the reference configuration. After this, deltas are generated for
visualizing and analyzing. You can select the deltas for a closer analysis and decide
on the necessary actions to correct them. These corrective actions are called
alignments.
Updates can then be implemented either in the actual configuration or in the
reference configuration.
Figure 216: CM Reference

331
Flexible CM Search
Figure 217: Flexible CM Search
Flexible CM Search is a web-based application for searching configuration
management data in the actual configuration. In addition, you can also view the data
in CM Editor and upload the actual configuration.
You can search data based on:
• Name
• Distinguished name
• Instance ID
• Cell identification
• Hardware Serial Number
• Managed object class
Flexible CM Search is a web application in NetAct Configurator. You can use it for
searching GSM, WCDMA and LTE configuration management data in the actual
configuration. You can also view the data in CM Editor and upload the actual
configuration.
Some functions may be disabled due to your license or permission.
Opening Flexible CM Search

1. Log in to NetAct Start Page.
2. Click Configuration ► Flexible CM Search.
Flexible CM Search opens.

CM History
CM History is a diagnostic and analytic tool which allows you to display all
parameter value changes in a selected scope and time slot. Additionally, you can
view managed object configuration in a given point of time and see managed object
hierarchy in network topology. Moreover, you can compare the configuration of
either one network element or two network elements and see the differences
between the selected points in time. It is also possible to restore the selected
configuration changes.
CM History data requires a CM History technology-specific license.
It is also possible to use the command line interface for initializing and synchronizing
the CM History database, and for generating change report in the configuration data.
The CM History database contains information on all changes such as creation,
update, and deletion of managed object that have taken place in the network. The
following configuration management operations can trigger these changes:
• Updates on the Configurator's actual database as a result of executing network
element upload.
• Updates of the Configurator's actual database originated from CCNs
(Configuration Change Notifications) received from network element.
• Updates of the actual configuration performed by internal CM services, which is
for troubleshooting purposes, such as for example, Post Upload.
• Network element integration.
• Updates of the reference configuration performed by initializing or merging plans
or the actual configuration.
Figure 218: CM History

333
Hardware Management functionality
Figure 219: Hardware Management functionality and benefits
The Hardware Management functionality is designed to manage hardware
equipment in the network. NetAct Hardware Management offers the operator an up-
to-date knowledge of the existing network hardware equipment used in the service
delivery.
Hardware Management is designed to store and provide hardware resource
inventory from the entire managed network. The users can easily search and
examine hardware data from a remote location. The system saves the hardware
information in the NetAct database, which can be updated regularly and viewed on a
daily basis.
By using the CM Operations Manager application, the user can perform the
following operations for hardware management:
• Synchronize Hardware information and Schedule upload of NE data with
NetAct: Included in the Actual Configuration Upload functionality.
• Export data to XML / CSV file: Included in the Actual Configuration export
functionality.
By using the CM Editor application, the user can perform the following operations for
hardware management:
• Browse Hardware information
• Search for information on a selected Hardware unit

Figure 220: Hardware Information
Benefits of Hardware Management

Hardware Management provides the following benefits:
• Better visibility of Hardware inventory, which then eliminates unnecessary site
visits.
• Reduction of downtime of a site after Hardware failure. Hardware Management
provides information on a faulty unit.
• An accurate serial number display facilitates tracking plug-in units as well as
following the warranty of repaired units in more detail.
• Boost of network operation and maintenance thanks to data integrity, accurate
knowledge of network components, their status and availability.
• Expedition of network troubleshooting actions resulting from the awareness of
the equipment whereabouts.
• Reduction of operational costs owing to fewer site visits and a smaller number of
resources required for upgrades.

335
Command Line Operations in Configurator

The racclimx.sh is the command line interface used to execute different
operations in configurator. This command has to be executed by omc user (NetAct
administrator super user) directly from the console of one of the Netact Virtual
machines running the WebSphere Applications Server.
As the operations are executed by WebSphere Application Server in a clustered
environment, make sure that all the files used by the racclimx.sh command line
interface are placed in a location shared between all the nodes and are accessible
by the Linux user (system) that runs the WebSphere process.
The NetAct user can choose the command line options as required. When entering
only the command racclimx.sh without any options, all the options are displayed
on the screen.
To see the help text for a specific command, enter -h after the command, for
example,
[omc]$ racclimx.sh -op Import_Export -h
To be able to use native character sets, for example Scandinavian characters
in the racclimx.sh commands, you need to have UTF-8 configured in the
local PC terminal settings (for example PuTTy).The new racclimx command
supports plan audits and separate import, export command along with legacy
import_export command .
Figure 221: Command Line Operations

Intelligent feature activation

The following figure illustrates the intelligent feature activation:
Figure 222: Intelligent feature activation
With this functionality, the roll-out of new radio features for 2G and LTE technology
using NetAct Configurator is made easy. The user can activate a feature using a
wizard which decreases the number of parameters to be configured to absolute
minimum. NetAct Configurator ensures that new radio feature are properly
configured on a network element immediately after roll-out. This is useful for
launching various traffic steering related functionalities.
This functionality also supports adding 2G or LTE as new radio technology to the
existing site. Whenever it is needed to expand the capabilities of an existing site,
NetAct Configurator simplifies Configuration Management for technologies that are
being added and resolves the dependencies. It allows for interworking with the
NetAct Working Set manager to determine the scope of where a particular SW
feature is planned to be activated.
It also allows for creating own configuration versions different from the default one(s)
for various phases of the feature deployment. Alternatively, it enables the user to
select appropriate configuration template, for differentiating configurations
depending on the application type of the network element. It provides full overview
of the configuration parameter dependencies but use of the dependency level
filtering capability.

337
Configurator Basic User Tasks

General Workflow
The following figure illustrates the general data flow.
Figure 223: General Data Flow

Sychronize Network Data

Context
In the Upload dialog you can sychronize network data and schedule an upload
operation.
Figure 224: CM Operations Manager: Sychronize Network Data
Perform the following steps to sychronize network data:

339
Figure 225: Procedure: Sychronize Network Data
Procedure
1 From any view, click Upload ► New Upload
Result of this step

The Upload dialog opens.
2 In the Upload dialog, select the target objects you want to upload under the
tabs. Under each tab there is a tree listing the possible objects you can select.
Result of this step

The selected objects are shown in the Scope of Upload pane.
If you do not have the correct license, some upload options are
disabled.

3 Select additional options for the upload (specific fort he NE type, for example
HW upload).
4 In the Upload Information pane, enter a name of the upload operation
(optional).
5 In the Upload Information pane, enter a description of the upload operation
(optional).
6 In the Upload Information pane, select the level of information shown in the
Feedback dialog.
7 To start the upload, click Start.
8 A confirmation dialog opens. Click Yes.
Result
The Feedback dialog opens and the status of the upload operation changes to
Started. You can monitor the progress of the operation on the Operation History
tab or the Feedback dialog.

341
Locking NE configuration data for exclusive usage

The following figure illustrates Locking NE configuration data for exclusive usage:
Figure 226: NE configuration data
NetAct CM functionality enables users to set the network element configuration to
an exclusive use mode, so that other users are not allowed to make any
configuration changes to this network element when the network element
configuration is reserved for exclusive usage. Exclusive reservation can be enabled
at Actual Configuration or while creating plans. After the required configuration
changes are carried out, the network element configuration can be released by the
user who exclusively reserved the network element configuration. While the network
element is in the exclusive reserve mode, other users cannot perform operation like
send to network, provision, export/import, Plan – Actual compare, NE-NE compare,
CM Analyser and CM reference on the reserved network element. The System
reservation plans can be unreserved by all users having permission to delete all
plans. User Reservation plans can be unreserved by all users having permission to
delete user specific plans or user belonging in SYSOP-group The network element
should be exclusively released by the user or the administrator or in the case of
exclusively reserved plans, the network element configuration released
automatically when the expiration time exceeds for that particular plan. The
functionality is fully supported for IMS, NTHLR FE, PCC, oMGW, and oBGW. Only
visualization support is available for R4 core and Radio NEs but preventing the
configuration changes is not supported for R4 core and Radio NEs.
• Reserving an object at network element level with ‘reserve with children option’
reserves all the objects under that network element for the user who has
reserved it and only this user can make the changes.
• Reserving an object at network element level with ‘prevent changes’ prevents
configuration changes on the particulate managed object by any user including
the user who has reserved this managed object.
• Reserving an object at network element level with ‘prevent changes with
children’ prevents configuration changes on the entire network element by any
user including the user who has reserved this network element.
• Provision of reserved managed objects is prevented for other users.

Hardware Configuration Upload / Export

For importing the network elements hardware configuration to NetAct, execute the
Operation "Actual Configuration Upload" as described in the corresponding previous
section. In the same way, to export the hardware configuration execute "Actual
Configuration Export" Task.
Figure 227: Single or bulk upload of HW configuration data bundled with CM

upload
The following figure illustrates the status of hardware synchronization.
Figure 228: Hardware Synchronization Status
The following figure illustrates the single or bulk export of HW Configuration data to
XML or CSV.

343
Figure 229: Single or Bulk Export of HW Configuration data to XML or CSV

Viewing Actual Configuration

Context
Actual configuration contains actual values from the network. These values can be
edited to change actuals in the network or they can be used as planned values.
The Actual Configuration node contains all objects in the topology, both operational
(actual objects) and non-operational objects that exist in the topology. You can view
actual parameter values only for the operational objects.
The MO classes and their parent objects that are selected in the Editor View
are shown in the CM Editor navigation tree.
Figure 230: CM Editor: Display of Current Configuration
Opening multiple plans at the same time has always been available, but now,
they have been organized into a tabular view to help users switch between
and identify which plan they are currently working on.
The following figure illustrates the tabs of current configuration.

345
Figure 231: CM Editor: Display of Current Configuration - Tabs
Perform the following steps to view actual managed objects:
Figure 232: Procedure: Viewing Actual Configuration
Procedure
1 Select Target Configuration ► Actual Configuration.
2 Expand the Actual Configuration node in the navigation tree.
Result of this step

A list of root objects is shown. They are sorted alphabetically in ascending order
based on class and object instance.

3 Expand the root objects.
Information
When expanding the managed objects, the hierarchy is shown first. The names
of the managed objects are fetched separately and added to the tree when they
are available.
Result of this step

A list of managed objects is shown.
4 Select the objects that you want to view.
Result
The Parameters by Actual Managed Object view opens. Here you can see the
values for the actual managed objects in the network.

347
CM Editor: View Filter

Editor View defines which parameters and managed object classes are shown in
plans, in the actual and reference configuration and how the parameters are
grouped.
The definitions in the selected editor view affect the navigation tree, as well as
parameters by managed object, parameters by managed object classes, parameters
by actual managed object and parameters by reference managed object views.
Figure 233: CM Editor: View Filter – Basic Parameters
The following figure illustrates the advanced parameters of the view filter:
Figure 234: CM Editor: View Filter – Advanced Parameters
The following figure illustrates the obselete parameters of the view filter.

Figure 235: CM Editor: View Filter – Obsolete Parameters

349
Managing Working Sets

Context
You can view the list of existing working sets to use them in NetAct Configurator as
well as view the content of working sets to see managed objects and their content.
You can also navigate to related object(s) in the actual and reference configuration
and copy the selected managed objects with or without their parameter values to a
selected open plan.
Figure 236: CM Editor: Managing Working Sets
Perform the following steps to view the list of existing working sets and manage
working set content:
Figure 237: Procedure: Listing of existing working sets
Procedure
1 In the CM Editor main window, click the Working Sets mode in the navigation
tree.
Information
On the right side of the window, the available working sets are listed in the
Working Set Name pane, and the managed objects related to these working
sets are listed in the Assigned Managed Objects pane.

2 To navigate to a related managed object, in the Assigned Managed Objects

pane select one or more managed objects and click the Navigate to MO(s)
button.
Result of this step

The target configuration with the selected corresponding managed objects is
opened.
3 To copy the selected managed objects to an opened plan, in the
Assigned Managed Objects pane click the Copy MO(s) to plan button.
Result of this step

The selected managed object(s) are copied to the selected plan.

351
Selecting Working Set to be used as filter

Context
You can also use working sets as a filter for the CM Editor navigation tree. You can
filter actual, reference and planned configuration according to your selected options.
Managed objects of an incoming relationship type, for example, adjacencies,
mediators are not filtered out by working sets.
Working sets selected as a filter prevent showing planned managed objects
(objects whose state has been changed to: create, delete, modify) in the
opened plans.
Figure 238: Procedure: Selecting Working Set to be used as filter
Procedure
1 In the CM Editor tree, click the Working Sets mode.
2 Click Working Set(s) you are interested in to see the content of particular
working set(s) in the Assigned Managed Objects pane.

3 Select Working Set(s) you want to use for filtering by clicking the
Filtering by Working Set(s)... button or right-clicking a given working set and
from the context menu selecting Filter by Working Set(s)... or from the CM Editor
menu bar selecting View and from the drop down menu selecting
Filter by Working Set(s)... or press Ctrl + Shift + W.
Information
If you select working set(s) in the table you want to use for filtering,
you can see their content. By selecting the option
Filter by Working Set(s)... from the context menu or using the
Filter by working Sets(s)... button, the chosen working set(s) are
preselected in the Filter by Working Sets dialog. You can confirm
the selection or change it, if needed.
Result of this step

The Filter by Working Sets dialog opens with a list of available working sets.
4 Select Include children to see managed objects with all their child objects.
Result of this step

The selected filtered working sets are shown in the status bar at the bottom of
the window. The actual configuration and plan nodes show managed objects
based on whether you have chosen the Include children option or not in the
filtered working sets.
Additional information
Information about your selection: Children included or Children excluded is visible in
the status bar.

353
Adding managed objects to working set(s)

Context
You can add the managed objects that fulfill the defined criteria in the Search and
Modify Target Configuration dialog to a new or an already existing working set by
clicking the Add to Working Set... button.
You can also select one or multiple managed objects in the actual configuration tree
or in a plan, regardless of their states (non-operational objects can be also selected)
by right clicking managed object and, from the pop-up menu, selecting Add to
Working Set....
If you want to return to the original state where all the managed objects are visible,
right-click a given working set, from the context menu select Filter by Working
Set(s)..., select desired working set(s), click the Filter by Working Set(s)... button,
and from the Filter by Working Sets dialog uncheck a given working set.
Alternatively, you can select Working Sets node from the tree view, select a given
working set, click the Filter by Working Set(s)... button and from the Filter by
Working Sets dialog uncheck a given working set.
Perform the following steps to add managed objects to working set(s):
Figure 239: Procedure: Adding managed objects to working set(s)
Procedure
1 In the CM Editor tree in the actual configuration or in the plan, select one or
multiple managed objects, right click one of them and from the pop-up menu,
select the Add to Working Set... option.
Information
Alternatively, in the Search and Modify Target Configuration dialog, click the
Add to Working Set... button.
Result of this step

The Add to Working Set dialog opens.
2 In the Name field, provide a unique name for a new working set you want to add
manged objects to.
Information
Alternatively, select the Add to existing working sets radiobox, and in the
Working set name panel, select checkboxes of the working set(s) you want to
add managed objects to. You can use the Filter field to find a desired working
set.

3 Click Add.
Result
The selected managed objects have been created in a new working set or added to
an already existing one(s), depending on the option you have chosen.

355
Creating working set from CM Query

Context
Perform the following steps to create a working set from CM Query:
Figure 240: Procedure: Creating working set from CM Query
Procedure
1 Click Create new in the Working Sets pane.
Result of this step

The Create New Working Set pane opens.
2 Select the CM Query tab.
3 Enter the parameter name, select the adaptation and MO class from the drop-
down list, and select a required operator and value.
Information
Alternativey, you can create more advanced queries by selecting And or Or
operators and typing in the next parameter criteria.
You can also narrow down your list, by entering an MO class name in the
Include only certain managed object classes field.
Result of this step

And and Or radio buttons and a new input field appears. In the Save Working
Set pane, a list of managed objects with chosen criteria is displayed.
4 Enter a name of the created working set and choose either the
Dynamic working set or Static working set option in the Save Working Set
pane.
5 Click Save.
Result
A new working set based on CM Query is created.

Modifying Parameters via Working Set

Context
Perform the following steps to modify parameters via working set:
Figure 241: Procedure: Modifying Parameters via Working Set
Procedure
1 Open Working Set Manager under Administration category and create a

working set from CM Advanced Query.
Information

357
2 In CM Editor, create a New Plan or select an existing plan to update your

changes.
Information
Figure 243: Modifying Parameters: New Plan
Information
Working Sets automaticaly populate into other NetAct tools once created.

3 Open the Plan.
a) Select your working set.
b) Select the Managed Objects you want to modify parameters on
c) Use Ctrl+A to select all.
a) Push the Copy Managed Objects to Plan button located on the right.
4 Select the plan you want to modify.

359
5 Go to Edit, select New Search and Modify from Selection.
6 Click on the little arrow located beside Modify.

7 Modify and confirm which plan you want to insert changes.
Information
Figure 244: Search and Modify Target Configuration
Information
Grayed out parameters cannot be modified.
a) Press the Put Modifications to Plan button.
b) Analyze and provision.

361
Deleting Objects from the NetAct CM Database

Context
Perform the following steps to delete the objects from the NetAct CM database.
Figure 245: Procedure: Deleting Objects from the NetAct CM Database
Procedure
1 In CM Operations Manager, click Tools ► Workflow Engine.
Information
Figure 246: CM Operations Manager: Tools
2 In the drop down list located on the left, select
NE data deletion from Configurator.

3 In CM Editor, click Actual configuration and select the object you want to

delete.
a) Right click and select Copy.
Information
Figure 247: NE data deletion from configurator: copy

363
4 Paste the object to be deleted in the left pane.
Information
Figure 248: NE data deletion from Configurator
a) Press the little green arrow just below to move the MO to the right pane.
b) Press start to complete the operation . The finished status can be viewed at
the top of the pane.
Result

Additional Information
The Interrupt button on the bottom grays out as shown in the image.

365
If there are errors, you can use this screen or Operation History to get more
information.
Figure 249: NE data deletion from Configurator: Operation History

Exporting Configuration
Context
Figure 250: CM Operations Manager: Actual Configuration Export and Import

Plan Data
The following steps describes the exporting configuration.
Figure 251: Procedure: Exporting Configuration
Procedure
1 From the File menu, open the Export dialog.
2 In the Scope of Export pane, click Options.
Result of this step

The Export Options dialog opens.

367
3 Select Actual or Reference Configuration.
a) From the Export drop-down list, select either Actual Configuration or
Reference Configuration.
Result of this step

The plan is exported on the top of actual or reference configuration.
4 Select Export format, Profile file, and Parameters.
a) From the Export format drop-down list, select either RAML2.0 or CSV.
Information
If you have selected RAML2.0, Profile file is not active.
If you have selected CSV, click the ... button next to the Profile file field.
Select the profile that you want to use. For information about profile files, see
Working with profile files and CSV data files in CSV Interface for
Configuration Management Data in Operating Documentation.
Result of this step

A file selection dialog opens.
b) In the Export pane, select the parameter values that you want to use.
Information
Internal values - These are values used in the database.
Alternatively, UI values - These are the values that you can see in other
applications (for example, CM Editor).
The selected format will be used for the export, and for CSV export, the
selected profile file and parameters will be used.

Export / Import data with CM Editor

The Export / Import data with CM Editor is described in the following sections:
• To export relationship plan using CM Editor ► Table Editor.
• To import relationship plan using CM Editor.
• To interrupt the import operation.

369
CM Express Data Exchange

The following figure illustrates the CM Express Data Exchange from CLI and CM
Editor actuals:
Figure 252: CM Express Data Exchange

Exporting relationship plan using CM Editor - Table Editor

Context
Figure 253: CM Editor: Export Plan
Perform the following steps to export relationship plan using CM Editor ► Table
Editor.
Figure 254: Procedure: Exporting relationship plan using CM Editor

371
Procedure
1 In the CM Editor application, open Table Editor.
Information
For planned managed objects with assigned template, parameters
not changed directly by user (which value is inherited only from
template) are not exported. Exported info about used template is
used during import to assign values to managed objects.
2 In the Table Editor, click the Export button.
Information
You can also choose the Export relationship plan option in CM Editor by
clicking the Plan tab.
Result of this step

The Export relationship plan dialog opens.
3 In the Export relationship plan dialog, click ....
4 In the File Name field, type a name for the export file.
5 From the Files of Type drop-down list, choose the .csv file type.
6 Click OK.
Information
You can also select different parameters by ticking the following checkboxes:
• Include children
Exports parameters of all the managed objects' descendants.
• Include incoming adjacencies
Includes parameters of incoming adjacencies.
• Include related objects
Exports parameters of managed objects which are in a close logical relation.
For example: WBTS ► IPBR, IPBR ► WBTS, WCEL ► RET,
RET ► WCEL, ADJS ► HOPS, HOPS ► ADJS.
• Include all parameters definitions
exports all parameters including parameters without value.
7 Cick the Start button.
Result
The export file is generated. The Progress bar indicates the progress of the
operation both in percentage and in number of the managed objects. When the
operation finishes, the selections are available again.

If you want to import relationship plan exported from Table Editor, you need
to perform it using CM Editor.

373
Importing relationship plan using CM Editor

Context
Perform the following steps to import relationship plan using CM Editor:
Figure 255: Procedure: Importing relationship plan using CM Editor
Procedure
1 Open CM Editor.
2 In the navigation tree, select Open Plans and choose the desired plan.
3 Click Plan ► Import Relationship Plan.
Information
You can also open the Import Relationship Plan dialog by right-clicking the
plan in the list and from the pop-up menu select Import Relationship Plan.
4 Click ... and choose the IPlan csv file which you want to import.
5 Click the Start button.
Result
After the Import operation, you can see the number of objects involved in errors and
warnings generated by the Import operation. This information is visible in the Import
Status pane of the Import dialog. The current situation of the operation is indicated
in Action. When the file is Imported , you can access the Import log with the buttons
in the Import Status pane: Full Log..., Errors..., Warnings...

Displaying plans
Context
When you open a plan, it is shown in the navigation tree under the Opened Plans
node.
Figure 256: CM Editor: Display of Plans
Perform the following steps to open a plan.
Procedure
1 Click Plan ► Open Plan.
Information
Alternatively, Right-click the Opened Plans node in the navigation tree and
select Open Plan from the pop-up menu.
Alternatively, on the toolbar, click the Open Plan icon.
Alternatively, try to expand the Opened Plans node when it does not contain
any opened plans.
The Open Plan dialog opens containing a list of plans in the NetAct Configurator
database. The plans are sorted alphabetically in ascending order based on the
plan name. The table also contains the plans you have already opened in the
navigation tree.
The table contains the following information on each plan:
• Plan
• Owner
• Created
You can filter the listed plans by selecting the check box on the left and entering
the filter criteria in the Filter Plans by field.

375
Mass parameter changes and plan creation

The following figure illustrates the mass parameter changes and plan creation.
Figure 257: CM Editor: Mass Parameter change and Plan Creation
The following figure illustrates the view of plan details.
Figure 258: CM Editor – Viewing Plan Details

Changing Mass Parameter

Context
You can mass modify managed objects from the actual configuration based on given
criteria.
The Modify extension only works if the search returns the objects of one object
class. If there are objects from several object classes, the Modify extension will not
open.
Perform the following steps to mass modify the managed objects:
Figure 259: Procedure: Mass modify managed objects

377
Procedure
1 Search for the corresponding managed objects from the database.
a) When you want to search the whole network, Select
Edit ► Search and Modify Target Configuration...
Information
Alternatively, Select Search and Modify Target Configuration... from the
Managed Objects pop-up menu.
Alternatively, Select Search and Modify Target Configuration... from the
Actual Configurations or Reference Configurations pop-up menu
Select Search and Modify Target Configuration... from a pop-up menu of
any MO in the plan or in the actuals/reference tree.
Click the Search and Modify Target Configuration icon on the toolbar.
b) From the Name drop-down list, select the name of the search.
Information
You can filter the searches by adding, for example, abc to the Name field and
then clicking Enter.
c) If needed, edit the searches in the Query field. Validate the changes to the
syntax by clicking Validate Syntax.
d) Enter a value for the required parameters into the Parameter table.
Information
The values should be entered as UI values. A short description of the
parameter is shown in the tooltip when you move the cursor over the value
field. The value field is shown in red if the value is not valid.
e) Click Count Objects if you want to see how many managed objects can be
found with the given criteria.
Information
The count is shown next to the button after you have pressed it. In case the
count takes a long time, it can be interrupted by clicking Stop.
f) Click Search to start the search for the MO(s) with the criteria you have
given.
2 Click Modify to open the mass modify extension to the
Search and Modify Target Configuration dialog.

3 Enter the values for the parameters to be modified in the parameter list.
Information
The parameter list contains parameters for all versions of the selected MO
class. If a modified object does not have the given parameter, it is ignored.
Values are given as UI values and a cell is shown in red if the value is not valid
for any of the versions of the MO class. In case a parameter has an invalid
value, the Create New Plan With Modifications button is also disabled.
4 Click Create New Plan With Modifications to add the given values for the

objects found by the given criteria into a new plan.
Result
A working dialog is shown until the operation is ready, after which an information
dialog is shown informing you of how many objects were modified. A new plan is
created with the default name, and the plan node is selected from the tree. The plan
contains the modified managed objects.

379
Creating Plan
Context
You can create a new plan by creating an empty plan and adding modifications to it.
Perform the following steps to create a new plan:
Figure 260: Procedure: Creating a new plan
Procedure
1 Select Plan ► New Plan...
Information
Alternatively, In the toolbar, click New Plan.
Alternatively, Right-click the Opened Plans node in the Navigation tree and
select New Plan from the pop-up menu.
Result of this step

The new plan is added to the navigation tree. The Plan Header view is shown in
the main view. The application has given a name for the plan, but you can
modify the plan name.
2 Type in a new name and a description for the plan.
3 To save the modified information, click Update.

4 To add modifications to the plan and to see managed objects, check that the
Show Managed Objects in Plans option is selected and expand the nodes under
the Managed Objects node.
Information
You can select objects in the tree and change their operation.
For instructions, see Changing the managed object operation. You can also
directly edit managed object parameters.
5 To create new managed objects, see Creating new managed objects in the plan

in Operating Documentation.
6 To modify the parameter values of the managed objects, see Editing parameters
in Operating Documentation.

381
Early plan validation in network controllers

The following figure illustrates about the Network configuration changes validation
prior to provisioning.:
Figure 261: Audit Plan

More granular provisioning permissions

The following figure illustrates the Provision configuration changes under controlled:
Figure 262: Provision configuration changes under controlled

383
Checking Plans
Context
CM Analyzer allows the user to check radio network and core network parameters
and managed objects to ensure that the parameters are defined according to
consistency rules and that no essential information is missing. The user can check
for discrepancies in the actual and reference configurations.
Nokia provides a set of basic consistency rules. The user can also create own rules
using an external text or XML editor.
To check for errors and inconsistencies in network configuration, you need to define
a target for your check, and select the rule(s) against which the target configuration
is checked.
Figure 263: CM Analyzer Usage: Checking Plans
Perform the following steps to start a new check:
Figure 264: Procedure: Checking Plans

Procedure
1 Click Check ► New Check....
Information
Alternatively, in the toolbar, click New Check.
Alternatively, in table of checks, right-click and select New Check... from the
pop-up menu.
Result of this step

The New Check dialog opens.
2 In the Check Name field, enter a name for the check.
Information
This step is optional.
3 On the Rules tab, you can select the individual rules and rule sets that you want
to run. Select an item from the List rules by drop-down list.
Information
The tree in the pane below the List rules by drop-down list is organized
according to the selected item.
4 To select a rule or a rule set, check the boxes to the left of the rule or rule sets in
the upper pane.
Information
You can also drag and drop, or copy and paste rules from the upper pane or
from the Rules tab of the main window.
For instructions on drag and drop, see Using drag and drop in Generic Help.
For instructions on copying and pasting, see Copying/cutting and pasting. You
can also click on the rule or rule set to select it and then right-click and select
Add to Selected Rules from the pop-up menu or select a rule and press the
Space bar. You can also drag and drop, or copy and paste rules from the Rules
tab of the main window. To select several rules at once, press the SHIFT key
and select the rules of your choice.
Result of this step

They will automatically be displayed in the lower pane.
5 To remove a rule from the lower pane, select a rule and press the Delete key.
Information
Alternatively, Right-click the selected rule and select
Remove From Selected Rules from the pop-up menu.

385
6 On the Check Target tab, Check Target drop-down menu, select the target
configuration for the check.
Information
The target can be:
1. Actual Configuration
2. Plan on top of Actual Configuration
3. Reference Configuration
4. Plan on top of Reference Configuration
7 If you selected Plan on top of Actual Configuration or

Plan on top of Reference Configuration, select a name or any user from the
Show plans owned by drop-down list.
a) Select one plan from the table.
Information
A description for the selected plan is shown in the Description of Plan (plan
name) pane at the bottom of the tab.
Alternatively, if you selected Actual Configuration or
Reference Configuration, mark the desired checkboxes to display the
managed objects in the lower pane. You can also drag and drop, or copy and
paste the managed objects to the lower pane. You can also drag and drop, or
copy and paste the objects, for example, from CM Editor or from the
Check Scope tab in the main window.
8 On the Post-Check Actions tab, you can set CM Analyzer to automatically
correct the inconsistencies it has found (if the rules support autocorrection).
Information
You can also set CM Analyzer to automatically send e-mail messages about the
checks it has completed and automatically include check results in these e-mail
messages.
9 Click Start Check.
Result
The dialog closes and the check starts. The check will appear in the table of checks
in the main window, where you can monitor its progress.

Provisioning Plans
Context
You can prepare a plan, provision a plan, schedule a provision operation, and create
a backup plan in the Provision dialog. The provisioning operations are: Activate,
Pre-Activate, Activate Pre-Activated Plan, Fall Back RNC RNW, Validate.
Plan preparation can be run as part of the provisioning operation or it can also be
run before provisioning as a separate operation. In the Plans list, you can see the
preparation status for your plan. It is recommended that the entire plan is
provisioned as one operation.
Figure 265: CM Operations Manager: Plan Provisioning 1/2
Perform the following steps to prepare a plan:
Figure 266: Procedure: Preparing Plans

387
Procedure
1 In the Plans tab, select the plan you want to prepare.
2 Open the Provision dialog. Click Plan ► Provision...
Information
Alternatively, Right-click the plan and select Provision... in the pop-up menu.
Result of this step

The Provision dialog opens.
3 In the Provision pane, enter an optional name and description for the
provisioning operation.
4 In the Operation pane of the Provision dialog, check Prepare Plan operation
and uncheck Provision operation.
Information
The provision operation is checked by default. If the plan has not
been prepared yet, the prepare plan operation is also checked by
default.
Result of this step

A confirmation dialog opens.
6 In the confirmation dialog, click Yes.
Information
Procedure: Provisioning plans is described in the next topic.
Result
The Feedback dialog opens and the status of the operation changes to Started. You
can monitor the progress of the operation on the Operation History tab or in the
Feedback dialog.

Procedure: Provisioning plans

Context
Figure 267: CM Operations Manager: Plan Provisioning 2/2
Perform the following steps to provision plans:
Figure 268: Procedure: Provisioning plans
Procedure
1 On the Plans tab, select the plan you want to provision.
2 Open the Provision dialog. Click Plan ► Provision...
Information
Right-click the plan and select Provision... in the pop-up menu.
Result of this step

The Provision dialog opens.
3 In the Provision pane, enter an optional name and description for the provision
operation.
4 In the Scheduling pane, you can define a schedule for the operation.

389
5 In the Backup pane, you can create a backup plan for your plan.
Information
By using the backup plan, you can roll back the network changes made by your
original plan.
The backup plan is always created for the entire plan. The default name of the
backup plan is derived from the plan name:
<planname>_backup_<date>_<time>. In the default name, <date> is the current
date in yyyymmdd format, and <time> is the activation time in hhmm format.
Another backup plan is automatically created for a GSM plan when file-based
provisioning is not used.
6 In the Operation pane, select the provisioning operation you want to run.
7 If you want to provision the plan partially, deselect Entire Plan and select the
objects to be included in the operation from each tab.
Information
In the Scope pane, Entire Plan is selected by default.
Select the Upload after activation checkbox in the Options pane to
automatically upload actual configuration from network after
provisioning operation.
Result of this step

Result
The Feedback dialog opens and the status of the provision operation changes to
Started. You can monitor the progress of the operation on the Operation History
tab or in the Feedback dialog.

Comparing plans to actual configuration

Context
You can compare your plans to the actual configuration by using the Compare
dialog. You can review radio network change plans, compare reports and
configuration data history as well as verify that all planned changes were
implemented correctly.
Figure 269: CM Operations Manager: Plan Actual Compare
Perform the following steps to compare plans to actual configuration:
Figure 270: Procedure: Comparing plans to actual configuration

391
Procedure
1 Click Plan ► Compare.
Result of this step

The Compare dialog opens.
2 Enter the name of the operation to the Name field (optional).
3 Check the Generate Delta Plan check box (optional).
Information
When checked, a delta plan of the differences between the plan and actual
configuration will be generated. Plan will contain the actual configuration values
of the differences. You can give a new name to the delta plan, or accept the
default name that is given in the Name field.
4 Select Level of Feedback.
Information
The possible values are Summary, Object, or Parameter. The default value is
Summary.
• Summary
Gives a short summary in a format of number of differences found from the
plan against the actual configuration.
• Object
Lists the managed object differences and number of parameter differences
against the actual configuration. One feedback summarizes non-existing
managed objects in the actual configuration or the number of differences
found in parameters per managed object in the plan against the actual
configuration.
• Parameter
Gives feedback about non-existing managed objects in actual configuration
and parameters whose values are different in the plan against the actual
configuration.
Result of this step

Result
The Feedback dialog opens and the status of the operation changes to Started.
You can monitor the progress of the operation on the Operation History tab or the
feedback dialog.

Executing Commands in Network Elements using Command Manager

Command Manager window in CM Operations Manager provides a fast way to
execute commands of the network elements. It allows performing the following
operations:
• Executing a single command to one network element
• Executing a single command to multiple network elements
• Executing a command file to one network element
• Executing a command file to multiple network elements
The output of the executed command or command file can be viewed in the
Command Manager window and exported to a file.
The user can schedule the command execution to be performed at a specified time.
Command Manager allows managing network elements as user-defined groups for
faster command execution on several network elements at one time. There is also
the possibility to execute command at once on more than one group at one time.
The user can also define dangerous commands for all network element types. This
is special handling for commands which are service affecting or of sensitive nature.
Execution of dangerous commands needs to be explicitly confirmed by a user.
Figure 271: CM Operations Manager: Command Manager

393
Searching Managed Objects with Flexible CM Search
Figure 272: Flexible CM Search Operations: CM Upload from CM Search

Results
You can search data based on:
• Name
• Distinguished name
• Instance ID
• Cell identification
• Hardware Serial Number
• Managed object class
The searching of managed objects with flexible CM search is described as follows:
Searching data by distinguished name (DN)

You can search managed objects by DN or part of a DN. It is not necessary to
include the PLMN-PLMN prefix. For example,
• LNBTS-767/LNCEL-1
• RNC-184/WBTS-174
• WBTS-174/WCEL-1
• BSC-74150/BCF-20/BTS-21
Searching data by instance ID

Search controller-level MRBTS, RNC, and BSC objects by instance ID. The
managed object class and instance ID are required. For example,
• RNC-123
• BSC-123
Searching data by cell identification

Search LTE, WCDMA, and GSM cells by cell identification parameters, CI, and LAC,
which match the network parameters.

Table 19: Cell Identification parameters

Technology Object class Cell identification parameters
LTE LNCEL E-UTRAN cell identifier (eutraCelId)
WCDMA WCEL Cell identifier (Cid)
GSM BTS CI(cellId and LAC (locationAreaIdLAC)
Examples:
ci 436737
ci=8 lac=9
ci 8 lac 9
Viewing details
To see the name and identification parameters of a search result, click Details. You
can see the following parameters if they are defined in the actual configuration.
• WCEL identification
• WCELMCC / WCELMNC
• Cid / Rncld
• Additional parameters for WCEL
• UARFCN
• LAC / RAC
• PriScrCode
• earfcnDL, earfcnUL
• phyCellId
• tac
• BTS identification
• cellId
• locationAreaIdLAC, locationAreaIdMCC, locationAreaIdMNC
• Additional parameters for BTS
• rac
• bsIdentityCodeBCC, bsIdentityCodeNCC
• LNCEL identification
• mcc, mnc
• parent LNBTS ID (title: Macro eNB identifier)
• lcrId
Opening search hits in CM Editor

You can open the search hits in CM Editor. You need to have CM Editor open to be
able to click Open in CM Editor... In CM Editor, the managed objects in your search
hits are selected in the actual configuration tree.

395
Operations with CM History

The sections covered in the following topics:
• Generating report on parameter changes
• Viewing historical configuration snapshots of NEs

Generating report on parameter changes

Context
The Timeline tab allows you to search configuration changes for a provided
managed object DN in a given time slot. The search scope can be limited by a
desired editor view or by a particular change context option. As a result, you get a
report with all the changes made in the network. This data can be utilized for
searching, browsing, and analyzing configuration changes, which can help in
network troubleshooting. The results can be exported to a CSV file for further
analysis.
Figure 273: CM History Operations: Generating Reports on Parameter

Changes
Perform the following steps to generate report on parameter changes:
Figure 274: Procedure: Generating Reports on Parameter Changes
Procedure
1 Select the Timeline tab.

397
2 From the drop-down list, select a scope for the changes.
Information
If you select the Entire network option, all network configuration changes are
displayed. You can also select DNs containing, and in the field next to it you can
provide one of the following:
• Whole DN of the managed object you are interested in, and then you have
only one result of the search.
• Exact segment of the DN, for example, ANTL-1, which shows all MRBTSs
which have ANTL-1 managed object/
• Partial DN with asterisk, for example, if you type
MRBTS-1/LNBTS-1/LNCEL*, all LNCEL managed objects under this
MRBTS-1/LNBTS-1 with child objects are displayed.
3 From the drop-down list, select Actual Configuration or
Reference Configuration.
4 From the Past drop-down list, select one of the options such as: 24 hours,
7 days or 1 month.
Information
You can also set the exact time period by clicking the small arrows and selecting
the dates from the calendar views. In the calendar, click the Now button to set
the current date and time.
5 From the Editor View drop-down list, you can select a desired editor view to
limit the displayed data.
6 To update the Editor View drop-down list, click the Refresh Editor Views icon

next to it.
Result of this step

All the editor views visible in CM History were created in CM Editor and are
stored in the database.
7 From the Change context drop-down lists, select a pair of values you are
interested in.
Information
Change context is additional information about changes performed on a given
managed object.
8 Select the Include children checkbox to see the children of the selected
managed object DN.
9 Select the Show only changes checkbox to view only the managed objects

which contain changes for a given DN.

10 Click the Generate Report button.
Information
If you have provided the whole DN in the field, then the whole tree is expanded.
If there are few search results, then only the first level of managed objects is
shown. Due to technical limitations, in some cases it is not possible to expand
the whole tree.
In the brackets next to the managed objects listed in the tree, there are a
number of changes on this object and its children performed at different
timestamps.
Expand the tree as needed and select one or more managed objects:
• In the tree, right click on a managed object and from the pop-up menu
choose Select children.
As a result, all changes of the selected managed object along with the
changes to its child objects are loaded into the results table. In case of a
lack of virtual memory on the system, results may not be displayed. In such
a case, narrow the selection scope by choosing a child object under the
originally selected managed object.
• Alternatively, Press the Ctrl key and select the desired managed objects.
As a result, all their changes are loaded into the results table.
• Alternatively, In the tree, select one managed object. Hold down the Shift
key and select an additional managed object.
As a result, all managed objects between the selected two are automatically
selected. Only expanded managed objects which are visible in the tree are
selected. All changes of the selected managed objects are loaded into the
results table. Their child objects are not loaded into the results table.
Managed object's parameter value changes are presented in the table on
the right hand side of the window.
Result of this step

On the left side of the window, you can see the navigation tree with the
managed objects hierarchy matching the earlier selected search criteria.
11 In the Comments field, you can provide additional information on the selected
change. When you click the Save comment button, the comment for the
selected change is saved in the database.
12 Under the main table, on the right hand side, click the Export button to export
the results to a CSV file.
Result of this step

Only the changes visible in the table are exported to a file. The exported file also
contains the Change context information.

399
Viewing historical configuration snapshots of NEs

Context
This functionality allows viewing a historical configuration snapshot of a network
element at a given point of time. You can display the configuration for both actual
and reference configuration. You can select a suitable editor view and include or
exclude child objects. As a result, you get a configuration snapshot report based on
your selection.
The View Configuration tab look and feel is based on CM Editor and you can see
the managed object hierarchy in the navigation tree. You can view parameters and
their values of a selected managed object in a configuration snapshot report.
Additionally, you can manipulate the way data is displayed in a generated report
according to your preferences and filter the report content.
Figure 275: CM History Operations: Viewing Historical Configuration Snapshot

of NE
Perform the following steps to view historical configuration:
Figure 276: Procedure: Viewing Historical Configuration Snapshot of NE

Procedure
1 On the View Configuration tab, enter the entire managed object path.
Information
For example PLMN-PLMN/BSC-1/BCF-1, or exact segment, for example
BCF-1 or BSC-1/BCF-1, in the DN containing field. Use the * (asterisk)
wildcard after or before the managed object DN in the DN containing field to
search for all managed objects consisting of a typed string. If you type BCF*, all
the BCF managed objects with child objects are displayed.
2 Define the target by selecting either Actual Configuration or
Reference Configuration in the Target field.
3 Define the date and time for the selected snapshot.
4 Select an editor view to limit the content displayed in the configuration snapshot
report.
a) In the Editor View field click the arrow on the right side of the field and select
a desired view.
5 Click the Refresh Editor Views icon on the right side of the editor view field to

make sure that the latest changes on editor views are included.
Information
If you want to change the editor view, you need to press the
View Configuration button after changing it.
6 Check the Include children checkbox if you want to have the child objects
included and displayed in the configuration snapshot report.
Information
The Include children option is checked by default. If you uncheck this option,
you get the managed object(s) defined in the DN containing field.
In case of using the * (asterisk) wildcard after the managed object DN, even if
you uncheck the Include children option, child objects are included in the
configuration snapshot report.
7 Click View Configuration.
Result of this step

You get a configuration snapshot report that consists of:
• Navigation tree
• Table including the Parameter column which displays all parameters and the
Value column which shows parameter values within the selected target and
timestamp
• Parameter Description pane

401
Command Line Operations: Massive Provisioning via CLI

Command line tool racclimx.sh is used for executing (and scheduling) almost any
configurator operation from command line.
Figure 277: Command Line Operations: Mass Provisioning via CLI
Mass modification plan is created and provisioned to the network with the given
scope and options. The operation scope must be defined with one or more of the
following options: -DN, WS, MR or -scopeDnRange. The operation supports
modifications to only one object class at a time.The operation scope is a sum of DNs
retrieved from DN, WS, MR and/or scopeDnRange.
The operation does not support modification of list parameters.
Following is the list of command line operations:
• 3GPP_Download
• 3GPP_Upload
• Activate_Pre-Activation
• Actual_Check
• Add_ENBs_Into_MBSFN_Area
• Admin_Manage_Queue
• Align_MBMS_Actual_Configuration
• Audit_Plan BCUBTS_Autoconfiguration
• BCUBTS_Configuration_After_HW_Replacement
• BCUBTS_Prepare_Autoconfiguration
• Binary_Download
• BTS_Automated_Site_Plan_Preparation
• BTS_SEM_Export
• Calibrate
• Check_Customized_Value_File

• Check_Inter_RAT_UTRAN_mobility_configuration_based_on_actual_WCDMA_
relations
• Check_MBMS_Actual_Configuration
• Check_MBMS_Plan_Configuration
• Commit_Align_Network
• Commit_Align_Reference Compare
• Delete_Plans_Older_Than Delta_Export
• Delta_Generation Diff_History
• eNB_Automated_Site_Plan_Preparation
• Flexi_Direct_Site_State_Clean
• Import_Export
• ImportExportView
• Init_History Init_Reference_Conf
• IPA_Activation
• IPA_Validation
• LTE1992_Prepare_for_configuration_restore
• LTE1992_Restore_configuration_manually
• Mass_Modify_MBMS_Parameters
• Merge_Plan MMLCommandExecution
• MOKeyBased_Delta_Generation NE3S_RenewRegistration
• NE3S_UnRegistration
• NE_Data_Deletion_From_Configurator
• Plan_Check planDeletion Policy_Based_Compare
• Policy_Based_Compare_For_Plan
• Provision
• Provision_Broadcast
• Provision_LTE_With_Priority Provision_Mass_Modification
• Reference_Check
• Remove_History Restore_Configuration
• Restore_FlexiBTS_Configuration
• Send_To_Network
• SRAN_BTS_Automated_Site_Preparation
• Synchronize_History Upload Validate
Example
racclimx.sh -op Provision_Mass_Modification -DN PLMN-PLMN/MRBTS-1 -WS Wroclaw

-parameterValuesByNames actEthernetSec=0 -bypassUnreachableLteBts true -v
racclimx.sh -op Provision_Mass_Modification -MR secureMRBTS -scopeDnRange

403
PLMN-PLMN/MRBTS-2500,PLMN-PLMN/MRBTS-2510 -objectClass NOKLTE:LNCEL

-parameterValuesByNames ulsMinTbs=32 -v
racclimx.sh -op Provision_Mass_Modification -WS WroclawEast,WroclawCentral

-objectClass NOKLTE:LNCEL -parameterValuesByNames enableDl16Qam=1
-serviceAffectingAllowed true -v

Lab exercise: HW Inventory Management

Context
This section tests the students on:
• Ensuring synchronization of NetAct and the NEs.
• Export of the HW data.
Figure 278: Lab exercise: HW Inventory Management
Procedure
1 Perform an upload of the Network Elements you want to see. Ensure to select
the HW button located at the bottom.
Result of this step

Why should we upload before anything else?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
2 From CM operations manager, Perform an export actual configuration of the

NEs you need.
Information
Ensure you select the HW button and unselect everything else to ensure you
only get the HW data.
Result of this step

Which tools can be used to view the output of this command?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________

405
Lab exercise: CM tools

Context
Perform the following steps for CM tools:
Figure 279: CM tools, 1/2
Figure 280: CM tools, 2/2
Procedure
1 Create a new plan. Modify and/or delete some objects in your plan.
2 Create a new WBTS to your plan (under RNC-11).
a) Add WCEL under your WBTS.
Information
Remember to fill all the mandatory parameters.
b) Create additional two WCELs under your WBTS by using
New MO from Selected MO functionality.
c) Create new SITE object and assign it to your WBTS.

3 Create new ANTE (antenna) object under ANTC (Antenna collection).
a) Create new WCAL (WCDMA Cell Antenna Link) under your ANTE.
b) Link your WCAL to one of your WCELs.
Information
Enter Linked Cell DN parameter from WCAL object to do that. You should
now be able to view WCAL as related managed object under your WCEL.
Result of this step

What is the difference between deleting and removing object?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
4 Create your own Editor view.
Information
You can decide the kind of view you want to create. For example, view for
creating 3G Sites, WCEL parameter retuning view.
5 Create your own template for WBTS object.
a) Create a plan by using your own template.
b) Create another template for WCEL by using values of
PLMN-PLMN/WBTS-26/WCEL-261.
Information
To create the template, you have to first copy parameters from actual to
(temporary) plan and then from plan to actual.
c) Create one WCEL under your WBTS by using the template you created.
6 Mass modify by using Table Editor and Editor View created in step 4.
7 Use Search and Modify to select all WCELs from your actual configuration and
create a backup plan.
8 Use Search and Modify to build a search that will search all WCELs that have
the cell id greater than 100 and are HSDPA capable.
Information
Save the search after you have tested it.

407
9 Use CM Analyzer to analyze the plan you created in step 1.
a) Add Creating_Sites_3G rule set to your check.
b) Fix as many errors as you can with CM Editor and keep analyzing your plan.
10 Use CM Rule Editor to create rules of both different types (Compare and

Condition) and test it with the CM Analyzer.
11 Make Actual data export with CM Operations Manager of your actual

configuration (Select RNC-11 and/or some MRBTS’s) in RAML format.
12 Import the data you exported in the previous step with CM Operations Manager

as a plan.
a) Check the plan with the CM Editor.
13 Create a new SITE Template for eNodeB (use eNB26 or 27).
a) Input name and description to the template.
b) Open ASC_template.xml file from G:\ drive in Warsaw lab environment
and save it under a different name.
c) Edit this template file so that the MRBTSs parameter
siteTemplateDescription is matching the description that you gave to
your site template.
d) Further edit the template file and replace all XXXs with your (unique) site id
and save the file.
14 Open workflow engine from CM Operations manager and select
Autoconfiguration eNodeB planning workflow.
a) Start executing the workflow with your own template (now an initial plan).
b) Check the output of operations and check the plan file in the CM Editor
between the steps.
Result of this step

What does it contain and how does it change after different steps?
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
15 Activate auto identification from workflow engine and check if the PREBTS
object was created under dedicated iOMS.

Optimizer
Optimizer Overview
NetAct Optimizer is used in the statistical network-wide optimization process in
NetAct. Optimizer provides visibility to current network behavior by combining actual
GSM, WCDMA and LTE network configuration parameters and measured
performance statistics with advanced visualization and analysis functionality.
Parameters can be optimized manually for small changes or automatically by
choosing from the range of optimization solutions provided by Optimizer. Optimizer
can be used for a single cell or for a whole region, or even across multiple regions.
The result of optimization algorithms can be visualized on a geographical map
before downloading the optimization plan to the network. The plan with the changed
parameters is sent to the NetAct Configurator where it is validated and provisioned
to the network.
• Optimizer uses statistical performance measurement data
As the input data for algorithms is accurate (measurements of a real network),
the output is also more accurate than with a signal-propagation-estimate-based
process in a planning tool.
• Using measurements makes the tuning process faster
Instead of heavy calculations based on raster map - where, for example, the
interference matrix is calculated by considering signal strengths in each map
pixel - a mobile measurement report is used. When the data is processed in
Optimizer, only some analysis is needed.
• Increased level of automation
With Optimizer, the whole optimization cycle is faster than with planning tools.
As Optimizer is implemented in the NetAct Framework, the actual configuration
data and measurement reports are available for processing. The network
topology in Optimizer is always consistent with the actual network data. When
running Optimizer for the first time, some customizing is needed, such as
parameters needed to guide the generation algorithms. Once the parameters
are set, the next optimization round is more effortless.
• Self Organizing Networks solution
NetAct Optimizer is a key component in the Nokia Self Organizing Networks
Suite. The Optimizer for SON solution provides complete element level
optimization for real time SON functions.
The Optimizer solution is composed of basic and optional functionalities. The basic
licenses for GSM, WCDMA and LTE include, for example, visualization based on a
geographical map and manual adjacency and parameter management. The
following functionalities are optional and require separate licenses:
• GSM – WCDMA automated adjacency optimization
• GSM –WCDMA performance optimization
• GSM - WCDMA capacity analysis
• Call location analysis
• Antenna tilt optimization
• Optimization of intra LTE neighbor relations (adjacency blacklisting)
• Mobility robustness optimization
• Multivendor support

409
Figure 281: Functionality Overview NetAct Optimizer
The following figure illustrates the NetAct optimizer concept.
Figure 282: NetAct Optimizer Concept

Optimizer main user interface
Figure 283: Optimizer : Main User Interface
The following figure illustrates the efficient visualization and analysis.
Figure 284: Optimizer: Efficient visualization and analysis
The following figure illustrates seamless multi-vendor network optimization.
Figure 285: Optimizer: Seamless multi-vendor network optimization

411
The Optimizer main user interface consists of the following panes: the Navigator
pane, the Map/Tool pane, the Browser pane, the Scopes pane, and the Cell Groups
pane. The tool views open into these panes. If several tool views open into the same
pane, each tool view has its own tab that you can close if needed. The main user
interface also contains the main menu bar and the main toolbar.
The availability of a tool view depends on the purchased Optimizer software license.
The tool views can be accessed from the Tools menu of the main menu bar or by
using the pop-up menus of Navigator, Browser, Map or the Scopes pane.
The practical optimization and analysis work happens always in the context of tool
view(s) and with the defined optimization scope (target). The optimization scope is
selected from the main window, which opens by default when Optimizer is started. It
is the core workspace for object browsing, navigation, and manual optimization.
Each tool view may have different scope selected for optimization at the same time.
Navigator pane
By default, Navigator opens into this pane.
Navigator offers four tree views that are suitable for different optimization purposes:
the Default view, the Hardware Topology view, the Adjacency Management view,
and the Capacity Management view. For example, you can use a different tree view
presentation depending on whether you optimize adjacencies or browse or tune
objects of the hardware topology.
Navigator contains objects that can be selected for optimization and for closer
viewing and modifying. From Navigator, the selected network objects can also be
located on Map and listed to Browser.
Right-clicking an object in Navigator opens a pop-up menu that allows you to, for
example, list elements to Browser or start optimization tools. The contents of
Navigator’s pop-up menu depend on the view that is currently open in Navigator,
which object has been selected, and what is the status of the object (actual, deleted,
modified, created).
Map/Tool pane
By default, Map opens into this pane.
Map is used to show the network objects and related configuration and performance
data, and optimization results on a geographical (scanned and/or digital) map. Map
can also be used for manual adjacency management.
Cell Groups/Scopes
By default, the Scopes tool view and the Cell Groups tool view open into this pane.
In the Scopes tool view, you can create, modify, and delete tailored scopes. You can
use the tailored scope as a starting point for different optimization tools. Scopes are
always global.
The Cell Groups tool view helps in visualizing and managing cell groups. You can
create, modify, delete, hide, unhide and rename cell groups, revert to default cell
groups and change the generality of the cell groups.

To be able to manage cell groups (create, modify, and so on) you need either
the Optimizer Administrator role or the Optimizer Provisioning User role
assigned to you. Other than admin users can only view the cell groups as
well as cell group properties.
The cell groups are arranged in a particular order both in the Cell Groups
pane and in the Visualization pane, the most general cell group being highest
on the list and the least general cell group lowest on the list. The generality
of the cell groups can be modified using the Move cell group up and Move
cell group down icons in the Cell Groups pane toolbar.
Browser pane
By default, Browser and the Use Cases tool view open into this pane. Note that
Browser is not open when Optimizer is started but only when an element or
elements are listed to Browser.
In Browser, you can visualize CM or PM data and any combination of CM and PM
data. With Browser, you can browse and edit objects in a table view. Object filtering
and mass editing are supported. From Browser, you can export data to a CSV
(Comma Separated Values) file. For instructions, see Using the Find/Replace
functionality of Browser and Exporting data from Browser in Optimizer Help.
You can change the view in Browser. You can hide rows by using filtering, change
the column order by dragging and dropping them, and change the columns to be
displayed through editing Browser profiles. For instructions, see Changing the view
in Browser in Optimizer Help.
In Browser you can view and edit the parameter values of multiple objects. You can
sort the object parameters in Browser for the session only or on a more permanent
basis by defining a profile. For instructions, see Sorting objects in Browser in
Optimizer Help.
With the Browser profile management functionality you can customize the view of
the object parameters and the object relations for your own purposes, or you can
share your profiles with other users. The Browser profiles support object hierarchy
but are always determined according to the parent object. The lower level (child)
objects can be freely selected. Browser has a set of default profiles (for each object
type) that all users can always use when Optimizer is open. For more information,
see Managing profiles in Browser in Optimizer Help.
Visualizations pane
This pane opens by clicking the Visualizations icon on the Map tool bar. The
Visualizations pane allows you to define which objects are visualized on Map as well
as quality indicators for these objects. You can also manage visualization profiles in
this pane.
The tabbed windows of Optimizer - for example Map, Browser, Key
Performance Indicators - can be opened in a new window. To do this, right-
click the tab and select Open in New Window. This functionality is particularly
useful if you have a dual-screen monitor in use.

413
Summary: Configuration Management

Module Summary
• Explain the purpose of Configuration Management.
• List the NetAct Configurator applications and explain their purpose.
• Use the Configurator tools for executing basic tasks for configuration
management.
• Explain the Radio Optimization Process in NetAct and the main functionalities of
Optimizer.


License management in NetAct
415

Module Objectives
• Describe NetAct licensing concepts.
• Describe NetAct Software Asset Protection.
• Use License Manager to check licenses.
• Use Software Asset Monitoring.
• Describe LTE and SRAN Licenses.
NetAct licensing concepts

NetAct Licensing
The NetAct system as such is delivered with all the functions, called the NetAct
sales features, that are implemented in a particular release. On the other hand, not
all functions are available for use. You can unlock these functions, using license key
files ordered from Nokia. Only a valid software license allows you to use a license-
based application, service, solution, or function. This behavior is related to the
NetAct software asset protection concept which assumes that all the NetAct sales
features are protected with license keys and without the order of proper license, the
NetAct software is not used. The NetAct software asset protection concept
introduces license protection for the NetAct features, network elements integration,
the NetAct capacity, the NetAct software release upgrade, as well as term licensing
model.
As a part of the NetAct software asset protection concept, NetAct software release
upgrade, NetAct hard lock and NetAct license alarms functions are implemented to
ensure proper system operation, and lucid way of the NetAct licenses handling.
License Manager is the application that is used for managing software licenses in
NetAct.
Software Asset Monitoring is the application that enables monitoring of the NetAct
Standard Software capacity features for NetAct Radio.
Figure 286: NetAct SW Licensing Overview
License keys
The following figure illustrates the license keys:

Figure 287: License types
NetAct Sales Features are protected with License Keys. To unblock desired feature
or function you need to order and install a proper License Key.
All the licenses are bound to each NetAct instance with own Target ID, which
means they cannot be moved between different instances.
NetAct is licensed with using different types of licenses. In general licenses
can be divided into:
• Term licenses
• Functional and capacity licenses
Functional and capacity licenses

The functional and capacity licenses are categorized as follows:
• On/Off licenses
On/Off licenses enable functions and permit the use of licensed software
functionality for one or more features or applications.
• Capacity licenses
Capacity licenses enable functions with volume/capacity limitation based on
indicators agreed in the contract.
Time based licensing notifications

The following figure illustrates the time based licensing notifications:

417
Figure 288: Time based licensing notifications

NetAct software asset protection

NetAct hard lock
Figure 289: Hard Lock mechanism
The NetAct software asset protection concept includes the NetAct software release
upgrade protection, the NetAct hard lock protection, and the NetAct alarms.
As a part of the NetAct software asset protection concept, NetAct hard lock is
introduced.
NetAct hard lock is associated with validity of the license file and affects licensed
features availability. Hard lock is triggered for license keys which are expired or if
license key capacity is exceeded and results in turning features off in case of no
RTU (Right To Use).
Figure 290: NetAct capacity Standard SW: Concept
NetAct hard lock for capacity licenses

Hard lock for NetAct capacity licenses applies to the NetAct Standard software sales
features. For capacity licenses hard lock is activated in case licensed feature
capacity is crossed. As a result new network element integration is blocked, as well
as configuration management functionality.
If the Software Asset Monitoring application detects that capacity of the NetAct
Standard SW license is exceeded, critical alarm is raised and hard lock mechanism
starts after one day grace period. Grace period lasts 24 hours and allows you to

419
order a new license key. Otherwise, hard lock is triggered, and as a consequence
new network elements integration is not possible. What is more configuration
management functions, like upload and provisioning, do not work. To avoid hard lock
activation you are notified with two other alarms, minor and major, with configurable
threshold limits. It allows you to order a new license key before hard lock activation
and with no harm to NetAct operability. The hard lock for capacity licenses is
released and related alarm is cleared after installation of new valid license with
additional capacity or after removal of integrated of element.
NetAct hard lock for NetAct term licenses
Hard lock for the NetAct term licenses concerns all the NetAct Sales Features which
are protected with On/Off or Capacity licenses. For term licenses hard lock is
triggered in case license key end date expires, which means if license validity period
ends. Without a valid license key, the NetAct licensed function is blocked from usage
or license capacity is deducted.
NetAct Alarms
The figure illustrates the NetAct alarms.
Figure 291: NetAct Alarms
The NetAct alarms functionality is designed to inform you about closing the NetAct
software license keys validity end date, as well as exceeding the NetAct software
licenses capacity thresholds. Alarms are related to the NetAct hard lock protection
function for the NetAct software licenses. The purpose of alarms function is to
remind you about need of ordering new licenses, and to provide seamlessly NetAct
system work.
The NetAct alarms are divided into two groups:
• Alarms for NetAct capacity licenses
The responsibility of exceeding capacity alarms belongs to the Software Asset
Monitoring application. Software Asset Monitoring monitors and reports used
capacity of software licenses and in case of capacity thresholds are crossed,
respective alarm is raised and visible in the NetAct Monitor application.
• Alarms for NetAct term licenses
For alarming about NetAct software licenses which are about to expire, the
License Manager is responsible. The License Manager handles validity dates of
term licenses and in case of validity time comes to the end, user is informed with
several levels of alarms which are shown in the NetAct Monitor application.

Licenses for OEM software

The figure illustrates the OEM SW licenses:
Figure 292: OEM SW licenses

The new License Management Model in NetAct is split in two areas:
The traditional management of license keys with the License Management
Application. The Monitoring of the usage of features for invoicing accordingly as an
alternative for the payment of a fixed license. NetAct License Manager provides
centralized solution for managing network element licenses. However, in NetAct the
functionality of License Manager has been extended as well to manage NetAct
applications licenses. All license key management operations can be performed
using License Manager. Software Asset Monitoring application collects and
processes the configuration and measurement data based on customer specific
settings. It generates a report on the feature usage and forwards the formatted
monitoring data to the customer and Nokia Customer Team via an encrypted e-mail.
The encrypted e-mail can be read and validated by Customer and Nokia Customer
Team only. The report on the feature usage is used to generate an invoice. One
software monitoring report comprises information related to one NetAct cluster.
Software Asset Monitoring enables speed and efficiency with fast software
activations through bypassing the pre-activation procurement process, and applying
alternative pricing models where invoicing is based on network configuration or on
used functionality. This results in OPEX savings and in an increased flexibility.
Monitoring data is CM parameters and PM counters. Software Asset Monitoring
application stores the data for further handling such as pre-processing to make raw
monitoring data is more accurate and usable, for example, data size is reduced and
data are presented in more convenient way to the user. Local storing of data is
needed before and after data processing. A report is periodically generated based
on monitoring data and sent to Nokia side where later on it is used for invoicing
purposes.
The Monitoring modules are product specific elements, which allow an incorporation
of specific reporting methods. Monitoring modules are divided into two groups: PM
and CM, particular for each network technology.

421
Figure 293: Monitoring as the alternative for license key management
Monitoring based license management for LTE and SRAN

Centralized License Server with SWEM introduces support for monitoring-based
license management.
Monitoring-based license management is part of a new license protection concept
for network-level licensing.
Figure 294: Monitoring based license management for LTE and SRAN
Monitoring based license management is applicable for LTE and Single RAN
technology.
Monitoring based license management is a mechanism that enables automatic
monitoring of licensed feature usage and license management on the network. The
new mechanism involves SWEM that monitors features usage and interworks with
Centralized License Server to manage licenses on the network.
In NetAct, a new license protection concept is introduced for network-level licensing.
CLS is an application that enables centralized, semi-automatic license management
in the whole network. License management takes place from one central place,
CLS, for many NetAct Regional Clusters. CLS reserves and releases capacity for a
specific feature based on a network element request sent by SWEM and without
manual work. Such behavior ensures that licensing smoothly follows changes in
network management.

License Manager to check licenses

License Management Overview
Figure 295: Managing License Keys Overview
Licenses are used to enable new features or functionality. For example, you may
need new licenses when you want to upgrade software or hardware, activate new
services, add capacity or optimize or expand the network. Licenses are ordered
from Nokia as any other functionality. You must then distribute the license to the
network elements in order to make the feature or functionality available in the
network.
License
A license is an agreement from the owner of a product that gives permission to use
or produce the product according to the agreed conditions. The information that
enables the use of licensed software is called a license key. Nokia implements
license keys as Nokia-specific license files. Each license file gives the permission to
use one or several features or functionalities in the specified network elements.
A license file contains the information to which network element the license is
targeted. This is done by using each network element's unique identifier which is
called a target identifier.
There are two types of licenses:
• On/Off license
NE licenses are installed to network elements either using the License Manager
application or element managers.
License Manager
The License Manager is a web-based application, which is a centralized solution for
managing license files.

423
Figure 296: License Manager
The graphical user interface can be used to perform the following operations:
Figure 297: License Manager Features (1/2)
The following figure illustrates the license features:
Figure 298: License Manager Features (2/2)
You need to have special permission to perform operations using License
Manager.
Licensing Concepts: NE Licensing

Network element license management allows you to control the network element
feature licenses from a centralized location, taking into account the number of
network elements in the network and variety of licensed features within one network
element. The NE licenses are issued for specific target ID.

The network elements to which you will use the license should be known in
advance. Once the license is issued for the specific target, it is not valid for other
ones. NE licenses are installed to network elements using either the License
Manager application or element managers.
Network elements license concept is supported for AXC, BSC, CDS, FLEXINS,
HLR, MGW, MSC, RNC, SGSN, WBTS network elements.
The following figure below illustrates the network element license concept:
Figure 299: Licensing Concepts: NE Licensing

425
Licensing Concepts: Pool License

Pool licenses contain license information for a large number of network elements of
the same type.
They are used for AXCs, WCDMA BTSs, and Flexi Direct BTSs. Pool licenses are
specific to one NetAct cluster and they contain the NetAct Target ID of the NetAct
cluster to which the pool license file is designated. They also contain the size of the
pool, which is interpreted differently for on/off licenses and capacity licenses.
• For on/off licenses
The size of the pool defines the number of network elements, which are
permitted to use the functionality. This means that you can create licenses for
that number of network elements.
• For capacity licenses
The size of the pool represents the total amount of capacity, which can be
divided between the network elements. This means that you can generate
licenses with different amounts of capacity for several network elements as long
as there is capacity left in the pool.
In order to take the license into use in the network elements, a license file needs to
be generated for the network elements from the pool license. The generated file is
called an NMS generated license file and it contains the target identifiers of the
network elements. Generating a license from the pool license decreases the amount
of free capacity in the pool.
The figure illustrates the pool license concept.
Figure 300: Licensing Concepts: License Pools

Licensing Concepts: License Sets

License sets functionality allows dividing pool licenses into groups and then
assigning them, by means of license set, to chosen Maintenance Region (MR). This
concept is useful for managing licenses in more effective way and gives flexibility of
managing pool license consumption.
License set is an advanced configuration, which enables turning features on/off
during automated license distribution by allocating pool licenses to be consumed by
network elements running in dedicated maintenance regions.
When a license belongs to a license set which is assigned to some maintenance
region, it can be used in automatic license distribution only if requested network
element also belongs to this maintenance region. In other words, network elements
can only request licenses assigned to the same maintenance region.
When network element sends a request to generate a license for some feature,
License Manager check which maintenance region this NE belongs to, and only
uses licenses from the pool assigned to that maintenance region.
A license cannot be assigned twice, if license is assigned to one license set, it
cannot be used again.
Figure 301: Licensing Concepts: License Sets

427
License States
The section covers license states as follows:
• Network Elements and OSS Generated Licenses (NMS licenses)
• Pool and SW Licenses
Table 20: Network Elements and OSS Generated Licenses (NMS licenses)
License States Description
Distributed The license is distributed to its network element.
Not Distributed The license file has not been distributed to the network element
which is in the target identifier list of license file.
Deleted The license file which was previously distributed to its network
element, has been removed from this network element.
Expired The license validity period has ended or the license signature
certificate has expired.
Expired still in The license file has been distributed to the network element, but
NE the validity period of license has ended or the license signature
Not Integrated The network element is not integrated to NetAct anymore.
Conflicting The license file in the NetAct repository, and the license file in
the NE have different content. For NE licenses the correct
license version should be identified.
In case the correct version is present in the NE, it should be re-
imported to NetAct. For NMS licenses, the license should be
deleted from the NE. In case the capacity is needed on the NE,
new capacity should be distributed from valid pool license.
Invalid The license file exists in the network element, but it is not used
by the network element because the network element does not
accept it or xml file has been corrupted.
Table 21: Pool and SW Licenses

License Description
State
Valid The license file has been accepted by the License Manager
application, which means the license xml file and signature are
correct.
Expired The license validity period has ended or the license signature
Invalid The xml file has been corrupted or the license file has signature,
signed with a test certificate, which is not accepted.

Figure 302: NetAct Licenses
The following figure illustrates the network elements licenses.
Figure 303: Network Elements Licenses

429
License Management Tasks

License management tasks are covered in the following sections:
• License Import
• Viewing Licenses
• Uploading Licenses
• Exporting Licenses
• Distributing Licenses
• Feature Templates
• Network Element Audit against Feature Template
• License Pool Substitution
• Licenses Reports

License Import
Context
Import operation view of the License Manager Web UI makes it possible to introduce
a license into the management system in a very easy way. Imported licenses can be
totally new, or new versions of already existing licenses in the NetAct.
Individual licenses or .zip archives of multiple licenses can be imported from any
available folder.
Figure 304: License Import
Perform the following steps to import licenses to NetAct:
Figure 305: Procedure: License Import
Procedure
1 In the main menu click License and select Import License from the drop-down
menu.

431
2 Click the Upload button and browse the folder where the license files are
stored.
Information
The License files table is refreshed and shows uploaded licenses. If any license
is already imported, it contains information about date of previous import in Last
imported column and label, if it was assigned before to this license. If the
uploaded license expired or is faulty, it does not contain check box and cannot
be imported. Status column in the table provides detailed information about
license failure.
To remove licenses from the table click the Clear button.
You can upload license file in the XML format or you can upload
multiple, archived licenses in the following formats: zip, tgz, tar.gz.
You can check the detailed information about the license by clicking
on the license file name.
Result of this step

The upload operation starts and progress bar appears.
3 Perform the following steps for attaching a label to the license file.
a) To create a new label and attach it to a license(s), check the license(s), click
the Labels button and select Create new. Type or paste new label into text
field and click OK.
b) To assign existing label to the license file, check the license(s), click the
Labels button and select an appropriate label from the list.
c) To remove label from the license, click the Labels button and select Remove
current from the list.
Information
You can attach the label to the uploaded license files for an easier identification.
You must create a label, before it is attached to the license file.
4 Select licenses you want to import and click the Import button.
Information
If you do not have LIC_ImportPermission, Import button is disabled.
To see the import operation details, follow the link into notification. The Recent
Operations view appears with the latest operation highlighted. In the table below
there are listed certain tasks of selected request.
Successfully imported licenses are available in the License Key Browser view.

Viewing Licenses
Context
You can browse all types of licenses using the License Key Browser view. You can
also download NE licenses to network elements and distribute pool licenses.
Figure 306: Viewing Imported Licenses and Licenses details
Perform the following steps for viewing licenses:
Figure 307: Procedure: Viewing Licenses
Procedure
1 In the main menu click License and select License Key Browser from the

drop-down menu.
Information
You can choose a type of displayed licenses by selecting appropriate tab in the
License Key Browser view.
If you highlight a license by clicking on it, second table appears below with
information about the license target. You can also click license file name to get
the detailed information about the license.
Result of this step

License Key Browser view appears.

433
2
You can filter licenses displayed in the table. To filter licenses, click the
button.
Information
In order to browse the installed license easier, you can filter out the irrelevant
entries. Filter settings are memorized for each tab. Licenses in the following
views: NetAct Software Licenses, NE Licenses, Pool Licenses are filtered by
license type and this criterion cannot be removed from the filtering criteria.
You can filter which licenses are shown, according to the following criteria:
Target type, Feature Code, Feature Name, Label, License code, License name,
License file, Serial number, Target ID.
a) Select a criterion from Filter by: drop-down menu. You can select multiple
criteria by clicking the Add criterion icon. To remove filtering criterion, click
the Remove criterion icon.
Information
You can merge the filtering criteria using (OR) and (AND) operators.
Operator (OR) means that in the License keys table all licenses are shown
which fulfill first or second criterion. If you select (AND) operator, in the
License keys table only, the licenses which fulfill both criteria will be shown.
b) You can define by checking the check boxes, if expired licenses and
downloaded to their all or filtered targets licenses in case of NE licenses, or
empty pool (capacity equals zero) in case of pool licenses, are shown in the
License Keys table.
c) Click the OK button to filter licenses in the License keys table according to
the selected criteria.
Result of this step

The License keys table displays licenses according to selected criteria, which
are listed above the table.
Information
To clear filtering criteria, click the button.
If you checked an expired or empty pool (remaining capacity equals
zero) check boxes, Clear filter button does not clear this choice. If
you want to uncheck them, you must do it manually.
To refresh the License keys view, click the button.
You can check the license detailed information by clicking the license
file name.
Result of this step

The Filter dialog appears.
Edit the label of the license files

You can remove the existing license label or change it. You can also add a new one
if the label does not exist. NMS generated licenses have the same label as the pool
license, it was generated from.
To add a label, check the license(s) and click the Labels button. Then select Create
new button and type or paste new label into a text field and click OK.
To assign an existing label to the license file, check the license(s), click the Labels
button and select appropriate label from the list.
To remove label from the license, click the Labels button and select Remove
current.
Exporting License Files
You can also export license files to the local workstation by clicking the
Export button.

435
Uploading Licenses
The purpose of upload license status operation is to synchronize the latest license
and feature information from the network elements with the NetAct database and to
keep License Manager up-to-date.
Synchronization is performed by uploading the status of all licenses from the
selected network elements.
In case there are licenses on network elements which are not present in the NetAct
database, they are uploaded and added to the NetAct database.
You can schedule license information synchronization for desired network elements
of particular type.
Figure 308: Uploading Licenses
Figure 309: Upload Licenses Scheduling

Exporting Licenses
Exporting license is an operation which allows you to download license file to your
local drive. You can download one license as a .xml file or multiple licenses as a .zip
archive.
Figure 310: Export Licenses

437
Distributing Licenses
Distributing license files entails downloading the selected licenses to the designated
network elements.
The features can then be taken into use according to the feature activation
instructions.
There are following distribution options:
• NE license distribution is used to distribute NE licenses, and to redistribute NMS
generated licenses.
• Pool license distribution is used to create and distribute NMS generated
licenses.
Distributing NE licenses
NE license distribution involves downloading licenses to network elements in one or
multiple operation.
NetAct users can download an NE license, or an NMS generated license to all
integrated network elements mentioned in the license file as a single operation.
Download can be executed in several operations so that only some of the network
elements are selected at a time. If new targets have been added to the license, the
download operation is needed only for the added target network elements.
Figure 311: License Distribution: Distributing NE licenses
Distributing Licenses from a Pool

Distributing licenses from a pool functionality enables multiple pool license
distribution to multiple network elements in one operation.
When a license from a pool is distributed, network element specific licenses (NMS
generated licenses) are created by the License Manager application. NMS
generated licenses are then automatically distributed to the network elements.
During capacity feature distribution, the user defines the amount of capacity for each
element.

Figure 312: License Distribution: Distributing Pool licenses 1/2
Figure 313: License Distribution: Distributing Pool licenses 2/2
Distributing Licenses Using Guided Distribution

Guided distribution allows you to distribute multiple licenses, based on a feature
template, to one or multiple network elements.
During guided distribution operation, license situation on network element is
compared to the one in the feature template and capacity needed for distribution is
calculated and then sent to the network element.
Needed capacity is summarized from remaining capacity of different pools. This
functionality assures that network elements will reach feature template definition.
Figure 314: License Distribution: Guided Distribution
Automatic Licenses Distribution

Automatic license distribution functionality allows to distribute licenses to network
elements without manual operations and based on a certain configuration.
Mechanism of automatic license distribution provides that licenses automatically
follow network configuration.

439
Automatic license distribution is based on network element request. NE request is
sent to a NetAct system in case network element needs new license or capacity.
The needed licenses are generated out of available pool and sent to the network
element automatically. For capacity licenses available pool is summarized from
remaining capacity of different pools. Deleted licenses can also be concerned as the
available pool and distributed automatically, provided that proper configuration for
automatic license distribution is set.
Available pool can be defined by license sets functionality. During automatic license
distribution you can limit a pool of licenses which can be distributed, by assigning
license set to desired maintenance region.
Figure 315: License Distribution: Automatic license key distribution 1/2
Figure 316: License Distribution: Automatic license key distribution 2/2

Feature Templates
Creating feature templates are the operations which allow you to define a set of
features and their capacity desired on a network element. Feature templates
concepts are used in guided distribution operation and during auditing network
elements.
A template can be defined based on existing network element and as a custom
template by selecting features from these available in a pool licenses.
If you generate a template from an existing network element, only the
distributed licenses are taken into consideration.
All features and their capacity values, which are distributed to a network
element, are going to be included in the template. If multiple licenses per
feature exist in the network element, they will be represented in the template
as a single entry for the feature with capacity value which is equal to the sum
of all licenses for the feature.
By defining a label in a template, you can narrow down the pool licenses
which will be used in the guided distribution.
Figure 317: Feature Templates 1/2
The features are as follows:
• Create feature template to be used as the pattern of distribution.
• Use feature template for auditing NEs.
• Apply template to elements by starting guided distribution.
• Select features for templates based on NEs or define from available licenses.
• Use labels for automated license keys selection in guided distribution.
The following figure illustrates the feature template.

441
Figure 318: Feature Templates 2/2

Network Element Audit against Feature Template

License Manager offers the possibility to audit network elements against previously
defined feature templates.
This functionality compares the licensed features status of the network element with
the one defined in a feature template and check if the network elements have
sufficient licenses distributed.
This option allows user to see if network element status is insufficient, equal or
exceeding against to the feature template and to start guided distribution to all
network elements having too less licenses.
Figure 319: Network Element Audit against Feature Template

443
License Pool Substitution

The pool license substitute process allows you to replace a pool license in case you
selected a wrong target in pool license distribution or in case of broken hardware.
License pool substitution process consist of three phases, registering licenses for
pool substitution, exporting license pool substitution request, and importing license
pool substitute permission.
If you have selected a wrong target in pool license distribution, the only way to revert
the allocation is by applying the pool license substitute process. The incorrect
license capacity is released back to the pool. By default, the substitution process
delete the substituted licenses from the network element.
Figure 320: License Pool Substitution

Licenses Reports
You can generate the following reports via the license Manager graphical user
interface:
• Report on NetAct software features
• Report on operations history
• Report on license files of network elements
• Report on license substitutions
• Report on network element license files of given state
• Report on licensed features of network elements
• Report on remaining capacity in pool licenses
• Report on comparison of templates to network element
• Report on comparison of templates to network element on feature level
• Report on NetAct software features
The following information is available in this report: Area, Feature name, Feature
code, Feature description, Sales item, Network Technology, License state, Capacity,
Expiration date.
For all reports you can generate via graphical user interface, data export to a CSV
files is available.
Figure 321: License Reports
The following figure illustrates the feature reports.

445
Figure 322: Feature Reports

Viewing Recent Operations

Recent operation functionality shows history of operations performed in the License
Manager application and provides an overview of all operations performed by the
user, system or network element. You are able to see detailed information about
recently executed operations, ongoing or finished, with their status of completion.
The overview of the following operations are available:
• Delete from network
• Download
• Feature state change
• Guided distribution
• Import
• License generation request
• License state change
• Pool distribution
• Substitution
• Synchronization request
• Target Id verification
• Terminate
• Upload status
Figure 323: Viewing Recent Operations

447

Introduction to Software Asset Monitoring
Figure 324: Software Asset Monitoring
The Software Asset Monitoring application collects and processes the configuration
and measurement data based on customer specific settings. It generates a report on
the feature usage and forwards the formatted monitoring data to the customer and
Nokia Customer Team via an encrypted e-mail. The encrypted e-mail can be read
and validated by Customer and Nokia Customer Team only. The report on the
feature usage is used to generate an invoice. One software monitoring report
comprises information related to one NetAct cluster.
For LTE and Flexi Direct, software monitoring is the only way of usage
control as License Keys are not implemented for these technologies.
Monitoring data are configuration management (CM) parameters and Performance
Management (PM) counters. The Software Asset Monitoring application stores the
data for further handling, to make raw monitoring data more accurate and usable. A
report is periodically generated based on monitoring data and sent to Nokia, where
later on it is used for invoicing purposes. Monitoring modules are product specific
elements, which allow an incorporation of specific reporting methods. Monitoring
modules are divided into two groups, PM and CM, particular for each network
technology.
The following monitoring modules are currently available:

Table 22: Monitoring Module Types (1/3)

Monitoring Module Description
GSM CM Monitors GSM configuration management parameters.
IMS CM Monitors IMS configuration management parameters.
LTE FDD CM Monitors LTE FDD configuration management
parameters.
LTE TDD CM Monitors LTE TDD configuration management
parameters.
LTE FZ CM Monitors LTE Flexi Zone Micro configuration
management parameters.
LTE FZC CM Monitors LTE Flexi Zone Controller configuration
NetAct Radio Monitors NetAct Standard SW configuration
NT HLR FE CM Monitors NT HLR FE configuration management
parameters.
RACS CM Monitors configuration management parameters from
the Radio Applications Cloud Servers.
The NetAct Radio monitoring module is a default, permanent module which
is not configurable.

SRAN CM Monitors Single RAN configuration management
parameters.
WCDMA CM Monitors WCDMA configuration management
parameters.
Flexi NG PM Monitors Flexi NG counters.
Flexi NS PM Monitors Flexi NS counters.
GSM PM Monitors Flexi GSM counters.
IMS PM Monitors Flexi IMS counters.
LTE FDD PM Monitors LTE FDD counters.
LTE TDD PM Monitors LTE TDD counters.
LTE FZ PM Monitors LTE Flexi Zone Micro counters.

449

LTE FZC PM Monitors LTE Flexi Zone Controller counters.
NT HLR FE PM Monitors NT HLR counters.
One-EIR PM Monitors One-EIR counters.
One-MNP PM Monitors One-MNP counters.
One- NDS PM Monitors One-NDS counters.
One TAS PM Monitors One TAS counters.
WCDMA PM Monitors WCDMA counters.

Software Asset Monitoring Notifications

Software Asset Monitoring supports e-mail notifications and provides information for
users about generating reports, as well as warns users about misusing application
and crossing capacity thresholds for features.
E-mail notifications are sent right after report generation in case one of the following
events occurs:
• Summary report (monthly or quarterly) has been generated.
• Unauthorized modifications have been made to monitoring data or in formerly
generated report.
• Feature threshold value, set during module creation, has been exceeded.
Notifications are configurable globally, as well as for particular feature during module
creation.
Software Asset Monitoring supports also alarms for NetAct software capacity
licenses related to NetAct hard lock protection for capacity licenses.
Figure 325: Notifications

451
Software Asset Monitoring Reports

The purpose of Software Asset Monitoring is to monitor and report features usage.
As a result of this a monitoring report is created. Software Asset Monitoring
application allows to view reports, download reports as CSV or XML file, and backup
a report in form of raw monitoring data.
Software Asset Monitoring application creates following types of reports for CM and
PM based monitoring:
• Daily report
It contains information about daily change of features/counters usage. In case of
CM based monitoring it contains feature parameters collected and reported
once a day. In case of PM based monitoring it contains information on counters
which have been collected during a day and counters values are reported for
every hour.
• Periodic detailed report
It contains information on features/counters usage for each day of the whole
invoicing period. In case of CM based monitoring it assembles features/counters
daily values. In case of PM based monitoring it shows results with aggregation
approach applied. Reporting results are listed for each network element.
• Periodic aggregated report
Periodic aggregated report shows aggregated features/counters values for the
invoicing period by applying the logic as defined by SWAM parameters. Results
are listed for each network element.
• Summary report
Summary report contains summary values for each feature/counter that is
applied for invoicing during the invoicing period for the dedicated NetAct Cluster.
In summary reports every Sales Item is listed only once as a basis for invoicing.
Figure 326: Monitoring Reports
The following tables show the rows and the columns which can be visible in every
Software Asset Monitoring report.

Table 25: Monitoring Reports Content 1/3

Row Name Description Comment
Module name Module name which is the
same module name that is
created during module
creation.
Module type Represents technology for
which report was created and
indicates what type of report it
is, CM (configuration
management) or PM
(performance management),
for example: LTE FDD CM,
WCDMA PM.
Day/Period It shows for what time report
was created. In case of daily
reports there is a Day row,
which shows the exact day
for which report was created.
In case of periodic reports
there is a Period row, which
shows the period of time for
which report was created.

Aggregation This row informs about type of
aggregation which has been
used to create a report.
Available options are Off,
NetAct Cluster, RNC, BSC,
Site.
Pricing model Type of pricing model which For CM reports
has been used to create a
report.
Nth highest value Number of Nth highest value For Periodic detailed
used for calculation. report
Sum up Channel It shows the way in which For WCDMA PM
Elements uplink/downlink Channel Elements uplink and Daily report
downlink values have been
counted.

453

Processing It shows method of calculating For WCDMA PM reports
Sets processing sets. Available options
are: Off, On,
Incremental capacity units.
HSxPA Shows unit taken into account when For WCDMA PM reports
Processing calculating processing sets. Available using Processing Sets
Sets trigger options are User and
User and Mbps.
Processing Set It shows if only processing set 2 is For WCDMA PM reports
2 only used. in case of
Processing Sets = On
Processing Set It shows the weight of processing set For WCDMA PM reports
3 weight factor 3 compare to processing set 2. in case of Processing Set
2 only = No
TargetId Identification number of NetAct.
Customer Shows the customer name
names
Excluded days Shows periods excluded from
monitoring scope.
Signature Hash value used for checking the
data integrity.

LTE and SRAN Licenses

LTE and SRAN License Management
The following figure illustrates the LTE and SRAN License Management.
Figure 327: LTE and SRAN License Management
Introduction to license management in LTE and Single RAN

From NetAct 16.2 onwards, Nokia introduces a new software (SW) license
management, which is an evolution of the mechanism currently existing in WCDMA
RAN. After a customer’s order, SW License Keys can be retrieved by Nokia Central
Licensing System (CLicS), which generates SW License Keys (LKs). The LKs have
to be uploaded to the Centralized SW License Server (CLS). The LKs are assigned
automatically to the SBTSs/LTE eNB’s according to the usage of SW LK protected
Sales Items. The LKs are not physically downloaded to the SBTSs and LTE eNB’s.
They are kept in the CLS from where NetAct SWEM assigned Right To Use (RTU) to
the particular NE’s. There is one CLS per the whole operator’s network. The CLS
cooperates with SWEMs in NetAct Regional Clusters (NetAct RCs).
Pool licenses in license management

Pool licenses are used for SBTS’s and eNB’s. All pool licenses are stored in the
CLS. They are available to all NetAct RCs of the operator’s network.
Pool licenses specify the size of the pool.
The size is interpreted in two different ways:
• On/Off licenses
For the On/Off licenses, the size of the pool defines the number of entities, for
example network elements that are permitted to use the functionality. This
means that you can create licenses for a particular number of entities.
For the capacity licenses, the size of the pool represents the total amount of
capacity that can be divided among network elements in the operator’s network.
This means that the CLS can grant or deny Right-To-Use (RTU) of required
capacity available in the pool.

455
Components of the Single RAN SW License Management

Nokia introduces the physical software License Keys (SW LKs) concept for the
SBTSes in Single RAN. In the operator’s network there is one network-wide pool
within a single CLS. The pools of licenses are not split into the NetAct RCs as it was
implemented for WCDMA BTSes.
The components of the Single RAN SW License Management and their roles:
Figure 328: Single RAN SW License Management components
• Central Licensing System (CLicS)
The ClicS is an application and interface for creating and delivering SW license
keys that Nokia generates based on the customer’s order.
• Centralized License Server (CLS)
The CLS is an application that provides a central control point for granting or
denying right-to-use (RTU) to Nokia software. There is one CLS per a whole
customer’s network. All NetAct Clusters are connected to the CLS.
• NetAct Regional Cluster (NetAct RC)
The NetAct RC is a framework that offers a versatile network and a mobile
service management solution. In Single RAN each NetAct RC runs its own SW
Entitlement Manager (SWEM).
• Software Entitlement Manager (SWEM)
The SWEM, as a component of existing SWAM, is a software component
located in a NetAct RC. It continuously checks configuration data and counter
information provided by the NetAct RC for relevant Sales Items (SIs). The
SWEM verifies the activation and the capacity of Standard, High-value, and
Hardware (STD/HVF/HWA) features. The SWEM cooperates with the CLS to
verify if sufficient SW license capacity exists. The SW license keys are not
physically installed at the eNB. They are booked in the CLS and SWEM as an
RTU. In case of missing SW license capacity, the SWEM generates a limitation
command to the related SBTS.
• Software Asset Monitoring (SWAM)
For the customer purposes, the SWAM is a process of monitoring the
performance management, charging statistics, and configuration management
data that is related to software assets in the customer network. The SWEM and
the SWAM are using the same calculation methods for checking license usage.
The monitoring happens in the customer network, but it is controlled and
invoiced by Nokia according to the customer contract.
Migration from WBTS to SBTS

The migration from a WCDMA BTS (WBTS) to an Single RAN BTS (SBTS) is a
simple process. The license capacity, as required for SBTSs, needs to be ordered
and loaded to the pool. After startup, according to the configuration and usage, the

software license keys (SW LKs) provide capacity which is automatically allocated
from the pool. The pool capacity is reduced respectively. After the upgrade, the SW
LKs become ineffective as they already exist in the WBTS. They do not block or
harm anything. After the migration, these SW LKs can be removed without any
impact on NEs. For the new SBTS, the SW LKs are in the CLS, whilst in the WBTS
the SW LKs are physically installed on the NEs. As the approaches differ in the
WBTS and the SBTS, no direct migration is possible.
Figure 329: Before migrating WBTS to SBTS
The following figure illustrates the after startup of the BTS:
Figure 330: After startup of BTS
Planning and Ordering

The principles of planning required pool licenses are as follows:
• The SBTS HW needs to be defined for an initial rollout or for a capacity
upgrade.
• The SW functionality needs to be defined and parameterized.
The process of ordering required licenses is as follows:
1. Network planning identifies the need for a capacity upgrade to guarantee a
certain service.
2. The amount of required capacity is identified.
3. A purchase order for licenses with the required capacities is issued.
4. Nokia delivers the licenses taking respective lead times into account.
5. The licenses are imported to the network's CLS.
6. The operations department performs the license distributions according to
specified processes.

457
Summary: License management in NetAct

Module Summary
• Describe NetAct Licensing concepts.
• Describe NetAct Software Asset Protection.
• Use License Manager to check licenses.
• Use Software Asset monitoring.
• Describe LTE and SRAN Licenses.


Software Management
459
Software Management
Module Objectives
• Use Software Manager for network element software synchronization,
reporting and import.
• Perform backup tasks for the supported network elements.
Software Management
Software Management in NetAct
Configuration changes are constantly needed to evolving networks to secure,
maintain, or improve the service level perceived by the end users. With the
introduction of new services, networks are enhanced to meet high demands of new
generation consumers. The configuration changes to complex and large networks
must be well planned, documented, controlled, approved, and executed to avoid
unplanned conflicts and symptoms in the network, which might cause service level
degradation. Software management play a central role in configuration changes and
in the change control process.
Change requests including software updates in the network can originate from
various sources, such as:
• Faults in current software, which need to be fixed
• Changes in other elements, which creates a need for compatibility changes in
interfacing elements
• Introduction of new services, and enhancements to existing ones
• Hardware changes in elements (for example, capacity increase)
• Security patches
• End of life of products, causing software replacements
Figure 331: Centralized software management
The following describes the main functionalities and benefits of centralized software
management.

Figure 332: Functionality and benefits of Centralized Software Management

Software Management
461
Software Manager
Software Manager allows remote management of software configurations in network
elements. It allows the user to upload the software configuration information from
NE to Nokia NetAct, download the NE software from NetAct to NE, import NE SW,
and activate the NE SW. Users can easily search and examine software
configuration data from a remote location. The system saves the software
configuration information in the NetAct database, which can regularly be updated.
An important feature of this application is also that the NEs' software can be stored
to the NetAct disk and be downloaded to the managed objects from a remote
location. All executed and ongoing tasks can be reviewed in the status view.
With Software Manager Functionalities, the users can:
• View the task and corresponding NE details
• Network Element information
• Latest task information
• Software tree
• Software details
• Upload software configuration information from NE to NetAct
• Download NE software from NetAct to NE
• Activate NE software in network element
• Compare network elements’ software versions
• Schedule tasks and manage schedules
• Manage SW packages in centralized Software Archive

Figure 333: Functionality in NetAct
Figure 334: Software Manager Tasks

Software Management
463
Software Manager Operations

The Software Manager user interface consists of following views:
Figure 335: Operations
Network Status: Software

Network Software Status provides a centralized software configuration register for
the network element software of the managed network.
Network Operations
The Tasks view is intended for monitoring the status of the software management
tasks. The status of the individual operations can be seen in the Tasks main view.
The Details tab includes more detailed information of each operation.
Software Archive
Software Archive provides a centralized network element software storage for
network element releases and NetAct change deliveries. After the software is
imported, the software is stored in the NetAct disks in one directory specific per
network element type.
The following sections are covered in the next topics:
• Software Manager Graphical User Interface
• Network Software Status
• Viewing Details of a Managed Object
• Uploading software configuration information from NE to NetAct
• Network Operations- Tasks
• Software Archive
• Attaching / Viewing Software Package
• Viewing Compatible Managed Objects
• Changing status of software package in Software Archive

Software Manager Graphical User Interface

The following screenshot displays the graphical user interface operations:
Figure 336: Operations: Graphical User Interface

Software Management
465
Network Software Status

Network Software Status implements a centralized, up-to-date software
configuration status for the network element software of the managed network.
Network Software Status is especially useful in troubleshooting cases and when
planning software installations. This is because there is no longer need to use
remote MML commands for viewing the software configuration, nor to record the
existing software manually on spreadsheet documents.
Network Software Status provides the following functionalities:
• View the software status
Certain network element type in the whole network.
• View the software configuration of a network element
Software builds, change deliveries, change notes, and files are listed.
• Upload software configuration from network element(s)
You can schedule an upload from network element(s) to the Software Manager
at any time. It is also possible to define repeatable tasks (daily, weekly, monthly).
Upload status can be monitored in Tasks tab.
• Download software to network elements
You can schedule software download so that the system automatically
downloads software to the network elements as required. Download status can
be monitored in Tasks tab.
• Activate certain network elements
When you download software to network elements, you can set the software to
be automatically activated after the download. This is supported for MGW
network elements. You can schedule the activation of downloaded network
element as required. Activation status can be monitored in Tasks tab.
• Compare SW status for selected NEs
You can compare currently installed software for MSS and MGW (only) by
selecting the network elements and pressing Compare SW button. You can also
use filtering to see in which network elements a particular CD set is installed.
• Search network elements
You can have a list of the network elements which fulfill the search criteria.
Search can be run based on any saved database information.
• Managing own sets
You can create own sets of network elements, export from and import into
Software Manager. Import/Export functionality allows you to use other tools (for
example Excel) to manage a list of network elements to be downloaded,
activated, or uploaded via Software Manager.

Figure 337: Viewing Network Software Status

Software Management
467
Viewing details of a Managed Object

Context
This section allows viewing detailed information such as software version
information or tasking related information of the selected network element.
Peform the following steps for viewing details of a managed object:
Figure 338: Procedure:Viewing details of a managed object
Procedure
1 Select the Network Status view.
2 Select the Software tab.
3 Select Parent from View drop-down list.
Information
You can also choose Maintenance region option, to view the network divided
into maintenance regions.
4 Select managed object type from MO type list.

5 Select parent managed object from the list located on the left side of the
window.
Information
If the Maintenance region option was chosen from View drop-down
list, then select a maintenance region in this step.
6 Click (the Show NE Details icon) located on the left of NE name.
Information
You can view detailed information such as Managed Object information, Latest
task information and Software details.
Result of this step

The details window appears.

Software Management
469
Uploading software configuration information from NE to NetAct

Context
This section describes how to upload the software configuration information from
network elements to NetAct (synchronize NE with NetAct). Before downloading and
activating new software in any network element it is necessary to know the previous
configuration or software version information.
If a task is in the Ongoing state on a particular network element, then you
cannot create a new task on the same network element to be run
immediately. If you try to create such a task, then an error message is
displayed.
The following screenshot displays the Uploading SW Configuration:
Figure 339: Uploading SW Configuration
Perform the following steps to upload the software configuration:
Figure 340: Procedure: Uploading software configuration information from NE

to NetAct
Procedure
1 Select Software from the Network Status menu bar.

2 Select Parent from View drop-down list.
Information
You can also choose Maintenance region option, to view the network divided
into maintenance regions.
3 Select managed object type from the MO type list.
4 Select parent managed object from the list located on the left side of the
window.
Information
If the Maintenance region option was chosen from View drop-down list, then
select a maintenance region in this step.
5 Select the network element by clicking the check box placed at the extreme left
in the Network Elements table.
6 Click New Task... button.
Result of this step

New Task wizard appears.
7 In step 1 of the wizard select Software Upload from Task Type drop-down list

and click Next.
Information
You can also do the following:
• Fill in the Task name field. Default value is MO name.
• Write a description of the task in Task description field.
Click the icon to display operation description and the default
timeout.

Software Management
471
8 In step 2, decide when to start the task from the following information.
Information
• If Frequency is set to Immediately, the task will be started when the wizard
is completed.
• If Frequency is set to Once, fill the Start date field.
• If Frequency is set to Periodically, fill all fields to schedule the number of
task executions.
• Choose the method of starting tasks and click Next.
• Parallel- tasks on selected network elements are started simultaneously.
• Sequence- tasks on selected network elements are started sequentially.
Checking the Interrupt on failure check box causes canceling tasks by the
system if the previous task in the sequence failed.
If the Interrupt on failure check box is not checked, system retries running task
on the network element on which the task could not be done at the first time
because the other task was in the Ongoing state on that particular network
element.
Tasks in group- determines the number of tasks that can be started
simultaneously.
9 In step 3 click Finish to create Software Upload task.
Information
In this step you can see the summary of the created task. You can also correct
task data by clicking the Previous button or close the wizard without creating a
new task by clicking the Cancel button.
Result of this step

After completing all the steps, a new Software Upload task is created.
Steps from 6 to 9 can be substituted by pressing the Synchronize button that also
causes that a new Software Upload task is created and can be seen from the
Network Operations view’s Tasks tab.
If there are more than 250 NEs selected for a task, they are not viewed by
default. If you want to view them all, click the available link.
In the main view in the Status column, a current status of the Software Upload
(synchronization) operation is displayed. If you have failed status you can click the
status to see further information on the failed uploads in the Status column.
If you have completed the steps successfully, the Networks Elements are
synchronized with NetAct.

Network Operations- Tasks

Context
For a selected NE type, you can view scheduled, ongoing and executed tasks.
Figure 341: Operations-Tasks
Perform the following steps for viewing scheduled, ongoing and executed tasks.
Figure 342: Procedure: Network Operations- Tasks
Procedure
1 Select the Network Operations view.
2 Select the Tasks tab.

Software Management
473
3 Select the NE type from the MO type drop-down list.
Information
All tasks for selected managed object type are displayed in a tasks table and
automatically sorted descending by Start date.
4 Click on Started/Finished time box or (the calendar icon) to set the time range of
displayed tasks.
Result of this step

The pop-up calendar appears, where you can select the date and enter the
hour.
5 Submit changes by clicking the Apply button.
Information
You can sort the data in the table by the content in each column.
Sorting in the following columns: MO DN, MO name, Finished,
alternates the order of subtasks in the single group. Sorting in the
following columns: Task Name, Task Type, Created on, Start date,
Creator alternates task groups order.
Result of this step

The list of tasks is updated accordingly to selected time range.
You can view all the tasks for selected network element type and time range.
6 Click the icon to expand the task group onto single tasks.
7 Follow the link in the Status column to show the details of single task.

Software Archive
The Software Archive tab allows managing software packages, which are already
stored in Software Archive. You can examine the details of a single software
package, see the list of managed objects compatible with the browsed software
package and download the package to compatible network elements. For managed
objects for which multi package management is defined, you can create a virtual
package, which combine physical software packages stored in Software Archive into
one virtual software.
The operations available for Software Archive are:
• Import software to the archive
For the selected MO type, the user can import software from a CD, from the
workstation, or from NetAct directory into the software archive and store them in
Software Archive. The import SW operation is executed with the SW Import
Manager java application.
• Browse and view archived software
You can have a view of the software stored in the software archive.
• Remove archived software
You can remove software stored in the software archive.
• Rename archived software
You can rename software stored in the software archive.
• Change
Change the internal lifecycle of software build status.
• Declare different statuses
Declare different statuses for software builds according to operator-internal
business process.
Additionally, the information about the Software Archive current disk space divided
into disk usage and available free space is included in the upper right corner of the
Software Archive tab.
The following screenshot displays Software Archive:
Figure 343: Software Archive
The following screenshot displays the software import manager operations:

Software Management
475
Figure 344: SW archive - Import manager

Attaching / Viewing Software Package Documentation

Context
In the Software Archive tab you can also attach additional documentation to the
software packages, both for physical software packages and virtual ones. In
particular, for network elements which require additional installation scripts for some
operations, you can attach installation scripts to the regular software packages.
Documentation can be attached only to software packages that are located
in Software Manager repository, both for packages from Local repository and
virtual packages.
Figure 345: Operations: View / Attach Software package release

documentation
Perform the following steps to attach documentation to the software packages.
Figure 346: Procedure: Attaching / Viewing Software Package Documentation

Software Management
477
Procedure
1 Select the Software Archive tab.
2 From the MO type drop-down list, select the managed object type or subtype.
3 From the list located on the left side of the window, select a package name
under a desired release folder.
Result of this step

The selected software package is highlighted with blue color.
The software package information is populated in the Summary tab.
4 Click the Documentation tab.
5 Click the Attach... button.
Result of this step

The Attach Documentation to Software Package dialog opens.
6 In the Attach Documentation to Software Package dialog click the

Attach file... button.
7 By using the file chooser, select the file you want to attach to the software
package.
Information
The maximum file size for import to Software Manager is 25 MB.
8 Click the Open button.
Information
The selected file is attached to the Software Archive. In the
Attach Documentation to Software Package dialog, you can see the progress
message of the uploaded file.

9 Click the Close button.
Information
The selected file is added to the software package. In the Documentation table
there is information about file size. In the Action column, there are two options
available.
If you add more than one file with the same name, the next files are
visible in the Documentation table as <name of the file>_x.<file
extension>.
Where,
x- numbers {1,2,3,...} added after the file name depending on the
attaching files with the same name order.
Example, If you add three documentation.txt files they are visible in
Documentation table in the following way:
• documentation.txt
• documentation_1.txt

Software Management
479
Viewing Compatible Managed Objects

Context
The conditions listed below determine the software package compatibility:
• Software package is assigned to the same MO type/subtype and has at least
one common release version.
• Software package is assigned to the common Maintenance Region which is
defined by Lifecycle status.
Figure 347: View Compatible network elements for SW package installation
Perform the following steps to see the compatible managed objects.
Figure 348: Procedure: Viewing Compatible Managed Objects
Prerequisites

The prerequisite for searching database against the compatible managed object is
the support of the Active Software operations, which require a software package as
a parameter (for example Software Download, Software Provision).
Procedure
3 From the navigation tree located on the left side of the window, select a package
name under a desired release folder.
Result of this step

4 Click the Compatible Managed Objects tab to see a table listing managed

objects that are compatible with the browsed software package.
Information
The list of compatible managed objects to the selected virtual package is
generated based on the given virtual package properties (MO Type, Release,
Lifecycle status). In that case, the target dependencies of physical software
packages forming the given virtual package are not taken into account.
Result of this step

All managed objects that can use the selected software package are listed in the
network element table.
If, during the importing of a software package the managed object subtype was
defined, in the Compatible Managed Objects frame you can see the network
element table filtered by MO type and set MO subtype.
If the selected MO type does not support the backup operations, the last column
showing the backup information in the network element table becomes hidden.

Software Management
481
Changing status of software package in Software Archive

Context
Figure 349: Setting Software package Lifecycle Status support and software
Quality Enforcement
To change status of the software package in the Software Archive, execute the
following steps:
Figure 350: Procedure: Changing status of software package in Software

Archive
Procedure

3 From the list located on the left side of the window, select a package name
under a desired release folder by clicking a desired node.
Result of this step

The software package information is populated in the Summary tab.
4 Click change status... link next to the Lifecycle status attribute in the Summary
tab.
Result of this step

The Change lifecycle status dialog opens.
5 From drop-down list, select a desired lifecycle status.
6 Click OK.
Information
Click See history link to see the history of lifecycle status changes.You can see
maximum 10 previous statuses in the list.
Result of this step

The Lifecycle status is updated in Summary tab.

Software Management
483
Network Element Backup

Network Elements Remote Backup from NetAct
Taking a regular backup of the software and databases of the network elements
ensures that you have a functional copy of the software which you can use if there
are any problem with the software or hardware of the network element. This backup
is called a fallback. How often you need to take a fallback depends on various
factors.
It is recommended to take a fallback before and after changes in the software or
hardware of a network element. Make sure that the network element works with the
new software or hardware before taking a fallback after the changes.
The procedure of creating a fallback and storing and copying the fallback build of the
network element data remotely from a NetAct Server comprises three main phases:
1. Controlling a fallback of the network software build
Take an automatic fallback of the network element software build. The fallback
build is saved on a disk in the network element. The fallback build may comprise
all files (full fallback), data files (data fallback), or only the changed files (archive
fallback).
2. Copying a fallback build into a network element local media
There are two options available for copying a fallback build into a local media:
• You can copy the fallback build from the disk of the network element onto a
DDS tape in the network element.
• You can copy the fallback build from the disk of the network element onto a
MOD in the network element.
3. Copying a fallback build into the fallback archive in NetAct
You can copy the fallback build from the disk in the network element to a disk in
NetAct (fallback archive) using FTP.
Figure 351: NE Backup Support

Network Elements Backup Archive

Software Manager supports Flexi Platform based Network Elements (OMS, mcRNC,
FlexiNG) data file backup from NE to NetAct. Data files are stored in a global disk in
NetAct. The size of one file may exceed 2 GB, so the global disk space can be
easily consumed after several rounds of backup operations. It is recommended to
estimate the needed space for NE backups in order to have at least 30% of the
global disk free.
Filling up the global disk to its maximum can endanger the correct operations
of the whole NetAct system.
In order to prevent disturbances in normal operation of NetAct, it is possible
to link the default backup repository to different storage location. The default
solution is to add a shared storage for NetAct Software Manager application
and link it as a default backup storage folder.
It is recommended to perform this operation by Nokia Technical Support.
The Network Elements Backup Archive view displays all existing backups of the

selected network element. The created backups are stored on the network element's
disks and additionally can be sent to an external device or to NetAct. With the
Storage type filter can be used to display data in a desired manner.
If the backup is stored in NetAct you can also find the URL Images, from where the
NetAct user can download the backup files.
In the upper right corner of this tab you can find the information about the Backup
Archive current disk space divided into disk usage and available free space.
Figure 352: Network Elements Backup Archive
Creating Network Elements Backups

A backup operation allows to transfer important configuration information from a
network element, store it and use it in case of possible disaster. You can create
backup directly on the network element as well as in an external device or in NMS.
Additionally, you can proceed with a full backup option or choose a partial backup.
Network element defines the content of the partial backup. Depending on the
backup type and the storage type, the following backup operations are formed:
• Full Backup
• Full Backup to External Device

Software Management
485
• Full Backup to NMS
• Partial Backup
• Partial Backup to External Device
• Partial Backup to NMS
For some network elements, you can also create the Custom Backup to NMS
operation. By using the custom attributes you determine the scope of data to
backup.
Figure 353: Creating Network Elements Backups

Summary: Software Management

Module Summary
• Use Software Manager for network element software synchronization, reporting
and import.
• Perform backup tasks for the supported network elements.

NetAct Training Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetAct Training Manual

Uploaded by

Copyright:

Available Formats

Nokia

Network Operations and

Safety statements in Student Handouts

Presents information to identify and warn of a situation where improper

Presents information to identify and warn of a situation where improper

Presents information to warn of a potentially hazardous situation where

Presents information to identify and warn of a potentially hazardous situation

Displaying Managed Objects Attributes............................................................126

Filtering Rule.................................................................................................... 195

Activating plan.................................................................................................. 308

Exporting Configuration.................................................................................... 366

Getting started with NetAct

Nokia Operations and Support System

Figure 1: Nokia and OSS portfolio

Nokia Cloud Application Manager

Figure 2: Nokia Cloud Application Manager Overview

Cloud Network Director

Figure 3: Nokia Cloud Network Director

NetAct Managed Network Model

Global Level Products

Figure 4: NetAct Managed Network Model

Knowledge Check: NetAct functionality

Knowledge Check: NetAct Managed Network Model

NetAct Architecture and virtualization

Business logic tier Business logic tier hosts the business logic and data

Data tier Data tier hosts NetAct data storages, that is, the database

Figure 5: NetAct Architecture

Figure 6: NetAct Architecture - Virtual environment

Benefits of virtualization in NetAct

Figure 7: Benefits of virtualization

Scalability in virtualized infrastructure

Table 1: NetAct Deployments: EMC solution

Mainstream – HP BL460c Gen9 2p8c 6 VNX Medium:

Large – 35 HP BL460c Gen9 2p12c 6 VNX Large:

2x10GbE LAN; fc controller VNX Backup:

Table 2: NetAct Deployments: HP solution

Mainstream – HP BL460c Gen9 2p8c 6 HP Medium:

Large – 35 HP BL460c Gen9 2p12c 6 HP Large:

Figure 8: NetAct Interfaces - Northbound and Southbound

Knowledge Check: Virtualization

Knowledge Check: NetAct Deployments

Figure 9: Accessing NetAct

New applications visualization modes

Figure 10: Start Page View modes

Lab exercise: Connecting to NetAct

Figure 11: Lab exercise: Connecting to NetAct

Result of this step

Lab exercise: NetAct Start Page

Figure 12: Lab exercise: NetAct Start Page

Result of this step

2 Change the visualization mode of NetAct Start Page from Show All Application

Result of this step

NetAct Application Categories

Table 3: NetAct Applications Categories

Figure 13: NetAct Application Categories

Figure 14: NetAct Applications Categories - Reporting

Thresholder and Profiler

Software Asset Monitoring

Figure 15: Performance Management Functions

Software Manager, License Manager

Self-Organizing Networks Scheduler

Figure 16: NetAct Applications Categories - Configuration

Maintaining up-to-date picture of the network

Configuring the network