You are on page 1of 90

NetAct 8

Configuration Management

Version 1

Nokia Solutions and Networks

1 (90)

Legal notice

Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Solutions and Networks training
documentation, product documentation and slide presentation material, all of which are
forthwith known as Nokia Solutions and Networks training material, are the exclusive property
of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to copying,
modification, translation, adaptation or derivatives including any improvements or
developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend,
modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and
Networks training material. Individuals can use the Nokia Solutions and Networks training
material for their own personal self-development only, those same individuals cannot
subsequently pass on that same Intellectual Property to others without the prior written
agreement of Nokia Solutions and Networks. The Nokia Solutions and Networks training
material cannot be used outside of an agreed Nokia Solutions and Networks training session
for development of groups without the prior written agreement of Nokia Solutions and
Networks.
Indemnity
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia Solutions and Networks customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or
transmitted in any form or means without the prior written permission of Nokia Solutions and
Networks. The document has been prepared to be used by professional and properly trained
personnel, and the customer assumes full responsibility when using it. Nokia Solutions and
Networks welcomes customer comments as part of the process of continuous development
and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability
arising in connection with such hardware or software products shall be defined conclusively in
a separate agreement between Nokia Solutions and Networks and the customer. However,
Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain
issues which may not be covered by the document.
Nokia Solutions and Networks will correct errors in the document as soon as possible. IN NO
EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY
LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT
This document and the product it describes are considered protected by copyrights and other
intellectual property rights according to the applicable laws.
The NSN logo is a trademark of Nokia Solutions and Networks. Nokia is a registered
trademark of Nokia Corporation. Other product names mentioned in this document may be
trademarks of their respective owners, and they are mentioned for identification purposes
only.
Export Control Marks:
AL: N and ECCN=5E991 or AL: N and ECCN=N (as in TCM course core data)
This course is subject to the European Export Control Restrictions.
Copyright 2014 Nokia Solutions and Networks. All rights reserved.
.

Version 1

Nokia Solutions and Networks

2 (90)

Contents

Contents
1
Configuration Management in NetAct
1.1
Overview
1.2
Configurator Basic Concepts
1.3
Configurator for Radio Networks
1.4
Configurator for Core Networks
2
NetAct Configurator Applications
2.1
Configurator Architecture
2.2
CM Editor
2.3
CM Analyzer
2.4
CM Operations Manager
2.5
CM Reference
2.6
Hardware Management functionality
3
Configurator Basic User Tasks
3.1
General Workflow
3.2
Actual Configuration Upload
3.3
Viewing Actual Configuration
3.4
Exporting Configuration
3.5
Displaying Plans
3.6
Mass Parameter Changes and Plan Creation
3.7
Checking Plans
3.8
Provisioning Plans
3.9
Comparing plans to actual configuration
3.10
Hardware Configuration Upload / Export
4
Optimizer
4.1
Optimizer main user interface
4.2
Radio network optimization process in NetAct
5
Exercise
Exercise 1
Exercise 2
6
Solution
Solution

Version 1

Nokia Solutions and Networks

5
6
12
24
29
34
35
36
38
40
42
44
48
49
50
52
54
56
58
61
64
68
70
72
75
78
81
83
84
87
89

3 (90)

Contents

Version 1

Nokia Solutions and Networks

4 (90)

Configuration Management in NetAct

Version 1

Configuration Management in NetAct

Nokia Solutions and Networks

5 (90)

Configuration Management in NetAct

1.1

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.

Version 1

Nokia Solutions and Networks

6 (90)

Configuration Management in NetAct

Configuration Management
Overview
Configurator gives access to real
time network configuration data
and provides tools to manage the
network configuration

Plan Import
Actual / Reference
Config export

Plan
Provisioning

Actual Config
Upload

Actual Config
Upload

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 1

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7 .(90)
.
.
.

Configuration Management in NetAct

CC

1.1.1

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

2.

3.

network (network elements). This information will be the base for all configuration
activities.
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.
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.

Version 1

Nokia Solutions and Networks

8 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Processes
Why do we need a Configuration Management System ?

Because:
We need to know the actual
configuration of network
=> Upload

Upload

Configure

We need to plan configuration


changes to network
=> Configure

We need to download the


changes to the network
=> Provision

Provision

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 2

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9 .(90)
.
.
.

Configuration Management in NetAct

1.1.2

Data flow and Network Planning Cycle

NetAct 7 Configurator provides view for configuration management data and workflows, with
features such as:
Powerful set of tools: from the smallest change to large network retunes, Configurator tools
allow end users to proficiently and accurately perform network configuration management
tasks in a systematic and efficient manner. This provides major OPEX savings while
improving the overall quality of the network. In general, the CM applications are the same
than available in NetAct OSS5 releases.
End to end coverage of network management use cases, e.g.:
Consistency check and audit of the network
In practice any user defined task sequence is a candidate for automated single operation
with CM Workflow Manager
Single standard integration point for other OSS systems:
Configurator provides standard interfaces (e.g.: Bulk CM XML and CSV) for both import
and export directions. Other OSS systems do not need to care anymore about the variety
of proprietary protocols used by its different providers
Continuously developing Multi-Technology features and synchronized support also with
NetAct OSS5 systems:
New technologies and adaptations developed on top of NetAct 7 (i.e. direct integrations to
network elements)
Existing technologies and adaptations from NetAct OSS5 (i.e. OSS interface based
integrations)
All the Configurator product functionalities are designed to meet the challenges in following a
daily network planning cycle. This is the basis of Configurator and for all different concepts
and features presented in the configuration applications.

Version 1

Nokia Solutions and Networks

10 (90)

Configuration Management in NetAct

Network Configuration in NetAct


Data flow and Network Planning Cycle

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 3

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.11 .(90)
. .
. .
. .

Configuration Management in NetAct

1.2

Configurator Basic Concepts

The Configurator applications in NetAct use a group of basic concepts which allow to
describe the network and the actions that those tools execute on it.
The Network resources are represented as managed objects in NetAct. Configurator 7
supports managed object classes in 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.

Version 1

Nokia Solutions and Networks

12 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Basic Concepts
Network Resources

MANAGED OBJECTS

Network resources are represented as managed objects in


NetAct. Configurator supports managed object classes in
GSM, WCDMA, I-HSPA, and core network.

CM Configurations

CONFIGURATION TYPES

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.

SYSTEM AND USER TEMPLATES

Templates
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.
CONSISTENCY CHECK RULES

Parameters Consistency
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.
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 4

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.13 .(90)
. .
. .
. .

Configuration Management in NetAct

1.2.1

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 (e.g.:
BTS information model). Information model in this context includes:
Overall information about the network resource (network resource type name, e.g.: BTS,
network resource model release, e.g.: Release 1)
Parameter information about the network resource (parameter name, parameter
description, parameter data type, parameter range, etc.)
A Managed Object Instance represents a specific network resource (e.g.: BTS installed in
site x in region y). The representation of the specific network resource means:
Identification information about the specific network resource (e.g.: fully qualified
distinguished name, supplementary identification parameters such as User Label, Cell ID,)
Parameter value data about the specific network resource

Version 1

Nokia Solutions and Networks

14 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Managed Objects
Topology
Managed Object (MO)

The Managed Objects are arranged in


a hierarchical structure according to the
Object Model.

Refers to an abstract representation of a


network resource, either a physical or logical
entity in a network managed by NetAct.

Distinguished Name
Distinguished name uniquely identifies an
MO in NetAct Topology.
The DN consists of relative distinguished
names of its superiors in the topology,
separated by a slash (/), starting from the
root object and advancing towards the
managed object that is identified (for
example,
PLMN-PLMN/BSC-2318/BCF-1/BTS-3).

Managed Object Class (MOC)


Defines the characteristics of the MO, such
as its parameters, operations, notifications,
and behavior. Class contains information
on:
the network resource type (for example,
BTS), release (for example, S14),
parameter characteristics.

Site
The SITE object is a way of storing the
geographical location of the managed objects
in the managed network. CM tools provide
functionalities for Site Management and
assignment of MOs to sites.

Maintenance Region
Group of network elements and their subordinate
managed objects, which are managed by a certain
part of an organization. Maintenance regions are
modified by assigning and removing managed objects.

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 5

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.15 .(90)
. .
. .
. .

Configuration Management in NetAct

1.2.2

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 Configuration: set of Managed Objects that represent the desired
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 Configuration: set of Managed Objects that represent what would be the 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)

1.2.2.1

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

Version 1

Nokia Solutions and Networks

16 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Configuration Types

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 6

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.17 .(90)
. .
. .
. .

Configuration Management in NetAct

1.2.2.2

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.

1.2.2.3

Plans

A plan is a configuration containing a set of modifications f the actual configuration. Plan


contains only modifications and it can be viewed on top of the actual configuration.
Plan 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.

Version 1

Nokia Solutions and Networks

18 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Network Plans

Network plans hold the configuration data for transferring an


actual configuration into a target configuration and include:
Create operations for new object instances
Modify operations for existing object instances

Delete operations for existing object instances


Network Plan
(abstraction)
actual configuration

delete
modify

new actual configuration


(target configuration)

create

Plan Provisioning

Network Element

Network Element
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 7

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.19 .(90)
. .
. .
. .

Configuration Management in NetAct

1.2.2.4

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, e.g.: 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.

1.2.2.5

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.

Version 1

Nokia Solutions and Networks

20 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Templates
A template is a set of default values that are applicable to a
specific Managed Object Class.
When parameters have the same
values in different Managed Object
Instances across the network.
When enforcement of a specific
parameter policy is required.
System Template is a set of default values that represent the
factory presets. There is one System Template per MOC and it is
not editable
User Template is a set of default values that represent default values applicable under
user defined conditions, e.g.: there can be one user template that defines the default
values applicable to a rural WBTS, while there can be another user template that
defines the default values applicable to an urban WBTS.
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 8

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.21 .(90)
. .
. .
. .

Configuration Management in NetAct

1.2.3

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 new erroneous or incomplete
plan harms 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.
Configurator 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.

Version 1

Nokia Solutions and Networks

22 (90)

Configuration Management in NetAct

Configuration Management in NetAct


Configuration Rules and Checks
Upload

New erroneous or incomplete plan might harm


network functioning after activation to network
elements
many types of constraints and
dependencies need to be noted
and taken care of.

Configure

Provision

The sets must contain an


proper selection of rules
that can be meaningfully
executed at the same time

Configurator
Predefined Rule Sets

Plan

Check

Correct

User Defined Rules

Target of the Checks


Actual
Configuration

Reference
Configuration

Erroneous objects and violations


are shown to the user in the user
interface for corrective actions.

Planned
Configuration

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 9

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.23 .(90)
. .
. .
. .

Configuration Management in NetAct

1.3

Configurator for Radio Networks

Radio technologies are evolving fast, with GSM/EDGE, WCDMA and LTE all used widely
and often within the same network. NetAct enables operators to use the same management
platform independent of their current network status and to facilitate a smooth evolution
towards new radio access technologies in the future.
NetAct pursues a multiradio approach, achieving harmonized network management for
existing GSM/EDGE and WCDMA as well as Flexi Direct and LTE radio access
architectures. NetAct for radio networks is suitable for multi-technology and multi-vendor
environments. The following figure shows some of the most important applications and the
radio adaptations within the overall NetAct framework.
NetAct offers a constant view of the status and performance of the radio network.
WCDMA/HSPA upgrades to LTE can be carried out easily due to the similar flat network
architecture introduced by Flexi Direct. The operators can re-use their existing infrastructure
to the maximum, changes are mainly necessary on the software level.
Managing radio access networks involves complex operations and frequent feature
activations. iSON Manager offers highly automated tasks, self-optimizing network
functionality and energy savings, and is tightly linked into the operational processes and
functionalities provided by NetAct. The co-operation of SON and NetAct for radio networks
translates into further savings for the operator while increasing the quality of the network
significantly.
Development of network elements and NetAct goes hand in hand so as to always offer the
latest management functionality for all radio network elements in NSN product offering.

1.3.1

GSM / EDGE

NetAct for GSM/EDGE offers a complete set of sophisticated applications for managing
GSM/EDGE Base Station Controllers, Base Stations and so on. Remote BTS site
configuration file management (NetAct Configurator), for instance, reduces the number of
visits on site and shortens the roll-out time for new base stations. Simple installation steps as
well as auto-connection scenarios for first time commissioning and system configuration file
uploads reduce the risk of human error.
GSM networks are still widely up and running. However, the equipment is aging and
simultaneously, the users demand bandwidth increases. Modernizing the existing
infrastructure can be done while running and maintaining the existing network.
NetAct for GSM/EDGE with its flexibility and modular structure for multiple elements,
technologies and vendors enable the operators to modernize their GSM networks and
evolve towards new radio access technology networks. NetAct brings about operational
efficiency by supporting various system consolidation options.

1.3.2

WCDMA/HSPA

NetAct for WCDMA provides functionality for managing WCDMA networks. The look and feel
of the available tools is the same as for other radio access technologies. In addition, network
operating can be made even more efficient with the use of iSON Manager for WCDMA.
NetAct for WCDMA also supports smooth evolution towards LTE.
NetAct for WCDMA offers fault, performance and configuration management functionality for
IPA-based RNC and multi-controller mcRNC, Flexi WCDMA BTS and UltraSite BTS and
Version 1

Nokia Solutions and Networks

24 (90)

Configuration Management in NetAct

ATM cross-connected AXC and also for Flexi Direct. In addition, there is automatic license
distribution to FlexiBTS. The data content of, for example, measurements may vary
according to the type of the monitored network element (RNC or mcRNC).
NetAct for WCDMA includes fault and performance related management functionalities for,
for example, circuit-switched voice over HSPA, MIMO, dual-cell HSDPA, IP based Iu to name
but a few.
NetAct Configurator supports WCDMA network configuration visualization (planned and
current radio network), plan provisioning, plan and template management, radio network
configuration uploading from RNC, AXC and FlexiWCDMA BTS into Configurator database,
as well as WCDMA re-hosting. In addition BTS auto-connection and auto-configuration for
WCDMA are supported via iSON Manager. Furthermore, NetAct for WCDMA supports NSN
3G Femto solution for home or small enterprise access/

1.3.3

LTE

Long Term Evolution (LTE) is the next generation mobile network technology for packet
switched traffic, evolving from WCDMA/HSPA. It has a flat architecture, basically moving the
functionality of the RNC into the eNodeB and, to a lesser degree, the EPC. This allows for a
maximum re-use of existing network equipment, for example, only a software upgrade is
required for Flexi Multiradio BTS. Fast roll-outs, operational efficiency and also decreased
power consumption bring about savings for the operator, while higher bitrates, reduced
latency and higher spectral efficiency are other highlights of LTE.
NetAct offers common applications also for LTE network management. New LTE FDD and
TDD management data can be accessed and handled via NetAct. For example, new radio
network parameters can be adjusted with NetAct Configurator to activate and configure a
new radio feature while new counters can be collected to allow monitoring the new feature.
By using NetAct also as LTE network management system, operators can ensure simple,
efficient automated system integrations and a flat operation and maintenance architecture in
their networks, which translates into direct cost savings.
In addition, iSON Manager for LTE capabilities are available, which further automate network
operations and thus improve their efficiency and quality. For example, SON Plug and Play
allows the BTS to automatically integrate itself into the existing network with minimal or no
manual intervention. The new base station can then be configured by just connecting it to the
transmission system. After the BTS has been connected and configured, automatic
neighbour management (ANR) helps to establish, configure and maintain connectivity with
neighbouring LTE eNodeB.

1.3.4

SON for Radio Access Networks

The entity called self-organizing network or SON refers to a group of individual features
each automating certain key operational tasks and processes in radio and core networks.
With SON, it is possible to optimize efficiency and service quality. SON functionality has been
divided into three main categories: self configuration, self optimization and self healing.
Self configuration means simplified installation procedures, faster roll-outs, less drive tests
and reduced site planning. The target of self optimization is to increase network quality and
performance, optimize parameters and reduce OPEX. Self healing provides automation for
error self-detection, thus reducing manual intervention. It also provides faster maintenance
and reduced outage times.

Version 1

Nokia Solutions and Networks

25 (90)

Configuration Management in NetAct

Net Acts approach on SON is a hybrid one. This means that part of the functionality, in
particular when it comes to complex, mid- and long term optimization, resides within NetAct.
Simple, quick and short term optimization functionality, on the other hand, resides inside the
network elements.
SON concepts, interfaces and measurements are standardized by 3GPP for LTE networks.
NSN intelligent SON solution, that is, iSON, helps the operator to assess the best SON
deployment strategies, implement new network elements on a plug-and-play basis, automate
key operational tasks and automatically optimize the network to adapt and balance itself to
changing traffic load and other network conditions. iSON is designed for multi-technology and
to some extent, supports also multi-vendor networks.
iSON uses existing parts of NetAct, such as Monitor, Configurator and Optimizer and makes
them work together via a SON workflow coordinator. Thus, when a failure is detected in the
network, a corresponding workflow can be triggered which, in turn, checks how to proceed
and launches the necessary algorithms for failure recovery.

Version 1

Nokia Solutions and Networks

26 (90)

Configuration Management in NetAct

Configuration Management
Radio Networks
Single data storage
Actual and planned data

Automation
Use case specific workflows
Scheduled jobs, SON
Scheduler
Auto-configuration workflows
Rehosting tool with Wizard
Site Templates

Planning Center / Network Wide CM


Northbound interface

Data editing
Display actual parameter
values
Create, modify and delete plans
Direct send to network

NetAct
Configurator
Data
editing

Data management
Update via network element
events or upload network
element data
Provision plans to network
Control data exchange via
northbound interface
Keep track of executed and
scheduled operations
Automatic backup plan creation
NE command management
(Core)
Multipoint Configuration
Assistant (Core)

Data
management

Automation

GSM

Core
Rel. 4

GSM-R

Run consistency checks


Define user-specific
consistency checks
Reference data management
Configuration history
Policy-based parameter
management
Compare plan with actual CM
data

Automation

DB

WCDMA

Packet
Core

Data analysis and


auditing

Data
analysis

SDM

I-HSPA

LTE

IMS

Multivendor

Northbound interface
Import plans / templates
Export planned / actual /
reference / template
configuration

integration

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 10

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.27 .(90)
. .
. .
. .

Configuration Management in NetAct

Configuration Management
Radio Networks: Supported NEs

GSM
- RG20 EP1, RG20 EP2, RG30, RG30
EP1, RGR20, mcBSC rel1
WCDMA
- RU30 EP2, RU40, Flexi Direct, mcRNC
rel2
LTE
- RL40, RL50, RL35TD

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 11

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.28 .(90)
. .
. .
. .

Configuration Management in NetAct

1.4

Configurator for Core Networks

The core network consists of the circuit switched (CS) and packet switched (PS) domains
and the IP multimedia subsystem (IMS) as well as complementing offerings from customer
insight and experience (CIE).
NetAct for core networks is a domain-specific adaptation which provides the computing
platform and common basic software. Network element support for different technologies can
be released separately from each other and separately from platform/applications.
The main benefits of NetAct for core networks are:
Improved flexibility to respond to customer demands

One combined view for different core domains

New application features can be released separately

Adaptations are part of the technology release

NetAct for core networks combines all core domains under one umbrella network
management system. The network can be readily viewed via a single screen. Simple
architecture, harmonized platform and open interfaces enable NetAct for core networks to
help operators to reduce their administration, maintenance and system integration costs.
Additional features such as SON bring about clear advantages by raising the level of
automation.

1.4.1

Mobile Voice

NetAct for Mobile Voice offers extensive remote management functionalities for DX200based MSS, CDS, HLR, Acta-based MSS, MGW as well as IPA-based MGW network
elements. It supports network element alarms, measurements, configuration management,
software and hardware management, license management, network element backup and
restore, log management via Audit Trail, network element user management, security
management and remote launch of network element manager or command line interface for
local administrative tasks.

1.4.2

Mobile Data

NetAct for Mobile Data offers management functionality for Flexi NG, Flexi NS SGSN, Flexi
NS MME, Flexi ISN and Flexi LIG. NetAct for Mobile Data includes support for network
element alarms, measurements, configuration management, software management,
hardware management, license management, network element backup, Audit Trail and
network element user management.

Version 1

Nokia Solutions and Networks

29 (90)

Configuration Management in NetAct

1.4.3

SON for core networks

NSN SON for core implements intelligent, dynamic network management to improve the
operation of core network elements. SON for core networks introduces automation that helps
operators to proactively detect, analyze and react to changes in traffic demand and network
status.
Ranging from automated, event-based, real-time actions to automated element configuration,
SON for core networks self-aware, self-adapting capabilities monitor and help to prevent
harmful bottlenecks caused by traffic peaks. Core network investments are used to their
maximum, while increased automation improves operational efficiency and network stability.
SON for core networks can offer traffic load balancing, optimized transport capacity
distribution, smart phone signaling and voice call distribution. Resources such as processing
capacity can be flexibly allocated.
SON can either be implemented as a distributed function or as a centralized iSON solution.

1.4.4

Centralized iSON for Core

Centralized iSON for Core is a set of flexible service-oriented applications based on SOA
technology. All applications target at closed-loop automation with time- or event- based
triggering of processes and to automated adaptation to changing network requirements.
There are automated process applications related to MSS Pooling. The multipoint Iu/A
feature balances the subscriber and traffic load between different MSC servers in a MSC
server pool. Over time, the traffic load may become unbalanced, and that is when Core MSS
pool optimization applications step in. The feature ensures that the subscribers are evenly
balanced between MSC servers in a pool and the A-interface transmission resources are
aligned with the traffic. The applications make sure that the MSS pool load balancing
configuration (NNSF) is optimally configured and that subscriber distribution follows the
network plan on location area granularity. It also makes sure that the E1 transmission
resources are dynamically allocated to the traffic needs. These self-optimization functions
ensure efficient use of network resources and eliminate bottlenecks in core networks with
reduced investment. Similar pooling applications exist also for different technologies packet
core networks.
SGSN Pool Balancer automates balancing of NSN SGSN pools in the operator network.
SGSN Pool Balancer monitors pool load and initiates subscriber off-loadings at SGSNs when
needed. All actions suggested by application can be manually approved before the whole
process can be fully automated. In addition, the application provides flexible way to perform
SGSN maintenance.
Serving Gateway Load Balancer (S-GW LB) allows the efficient use of network resources by
keeping the load on the Serving Gateways on equal level. Serving Gateway load distribution
is done based on the number of sessions, the real throughput and the CPU load. With SG-W
there is no need to over-dimension the core network to cope with potential traffic peaks.
Process automation enables the operator to gain operational savings in the maintenance
process.

Version 1

Nokia Solutions and Networks

30 (90)

Configuration Management in NetAct

1.4.5

MSC Server Pool Monitor

MSS pooling provides valuable functionality to operators as it increases system resilience,


load distribution and balancing as well as backup possibilities. However, usually operators
have to collect and combine MSS pool data manually and from a large amount of network
elements, a task which is time consuming and error-prone.
OSS for MSS pooling is an optional product offering for the MSS pooling and resilience in
core networks. OSS for MSS pooling includes the MSC Server Pool Monitor, Multipoint
Configuration Assistant and Centralized iSON for Core applications as optional additions to
the core networks offering. MSC Server Pool Monitor can be used for monitoring the load
distribution in MSC Server pools.
The tool allows the operator to view the number of subscribers in the MSS pool (VLR) during
the last 24 hours and to run selected MML commands in order to view the pool-related
information in more detail. It also polls the number of subscribers in 5-minute intervals for
each polled MSC server in order to provide near real-time information. The system will raise
an alarm if there is an uneven load among the MSC servers in a pool that exceeds a
configured value.

1.4.6

Multipoint Configuration Assistant application for pooling


in REl4 Core

Creating and maintaining multipoint configurations in Rel4 Core network poses particular
challenges due to the huge amount of data and many data items which need to be correlated
to each other. Building and managing configuration is challenging when full radio network is
required to be configured for multipoint in all MSC Servers of a pool. Modification of pools, for
example, when adding an MSC Server to a pool is a comprehensive configuration task which
is prone to human error.
Multipoint Configuration Assistant (MCA) is a sophisticated application offering a wizard-like
functionality to create, browse and manage multipoint configuration of Rel4 Core networks
(MSS and MGW). Focus of the application is on facilitating consistent configuration in all NEs
of a pool as well as modification of pooling data in a user-friendly, efficient and reliable way.
Complexity of correlated data is hidden behind user friendly configuration operations
offered by this specialized application.
Application supports following use cases:
Create/delete a pool
Add/remove MSS to a pool
Add/remove radio area to a pool
Show Multipoint related inconsistencies
Activate off-loading mode for a single MSS
Solve inconsistencies of pooling data
Display and configuration of Virtual MGWs serving in pool (RAN independent
multipoint)
Multipoint Configuration Assistant helps the operator to achieve high operational efficiency,
reduce human errors through automation and improved Multipoint configurations through
pointing at and resolving of pooling data inconsistencies.
Version 1

Nokia Solutions and Networks

31 (90)

Configuration Management in NetAct

Configuration Management
Core Networks
Data analysis and
auditing

Single data storage


Actual and planned data

Planning Center / Network Wide CM

Data editing

Run consistency checks


Define user-specific consistency
checks
Reference data management
CM Auditing Policy based
parameter management
Compare plan with actual CM
data
Compare NE-NE actual and
reference configuration
CM History --- full access to
historical configurations all NEs at
any given time
Provides possibility to compare
data at two different time intervals

Northbound interface

Display actual parameter values


Create, modify and delete plans
Direct send to network

NetAct
Configurator

Data management

Data
editing

Upload network element data


Provision plans to network
NE command management
Multipoint Configuration
Assistant
Control data exchange via
northbound interface
Keep track of executed and
scheduled operations
Automatic backup plan creation
for fast rollback

Automation
Use case specific workflows
Scheduled jobs, Wizards
Auto-configuration workflows

Data
management

Automation

Data
analysis

DB

Automation

GSM

GSM-R

WCDMA

I-HSPA

Core
Rel. 4

Packet
Core

SDM

IMS

Northbound interface

LTE-TDD /
LTE-FDD

Import plans / templates


Export planned / actual /
template / reference configuration
Support of XML, CVS and XLS
(MSSPLANT Databuild) file
formats

Multivendor
integration

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 12

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.32 .(90)
. .
. .
. .

Configuration Management in NetAct

Configuration Management
Core Networks: Supported NEs
MSC Server
Releases

M15.0 , M15.1
M16.0 (ATCA),
M16.0 EP1
Ma16.1 (ATCA )
Md16.1 (DX)
Md16.1 EP1
(DX)
M16.2 (ATCA,
DX)

MGW
Releases

Packet Core /
(Command Manager)

U5.0 EP2
U6.0
Ui5.0
Ui5.0
EP1
Ui5.0
EP2

Flexi NG 3.0. Flexi NG 3.1


Flexi NS 3.0
Flexi NS SGSN SG8.0 DX (CD2,

CDS
(Command Manager)

M15.0 , M15.1
Md 16.1
Md 16.1 EP1

CD3,CD3.1), ATCA (CD2, CD3,


CD4
Flexi NS SGSN SG9.1 (DX), 9.2
(DX)
Flexi ISN 5.0 ..5.0 CD7

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 13

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.33 .(90)
. .
. .
. .

NetAct Configurator Applications

Version 1

NetAct Configurator Applications

Nokia Solutions and Networks

34 (90)

NetAct Configurator Applications

2.1

Configurator Architecture

Configurator Applications
Architecture
Northbound Mediations
Exchange information with other OSS
systems

Applications
CM Operations Manager

Adaptations
Optimizer

CM Reference

Perform micro-workflows (e.g.:


upload, download, import, export, plan
actual compare)
Perform macro-workflows (e.g.: rehosting)

Audit the differences between actual


and reference configuration

Information Models
Customizable network resource
information models

Visualize and optimize the netw ork


in the context of a geographical
information system

Align differences to either actual or


reference configuration

Workflows

Report on-going and executed


workflows

Customizable micro and macroworkflows

CM Editor

CM Analyzer

Visualize the managed configurations


Single and mass edit the managed
configurations

Actual Configuration

CM Workflow Manager

Check consistency of the managed


configurations

Create user interfaces for workflow


data

Enforce parameter policies

Reference Configuration

Rules

Create custom operations

Customizable consistency
checks

Repository

Plan Configurations

Southbound Mediations
Exchange information with network
elements/element management
systems

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 14

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Version 1
. . .
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
Nokia Solutions and Networks
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
35 (90)
. .
. .
. .
. .

NetAct Configurator Applications

2.2

CM Editor

CM Editor provides intuitive parameter editing, both in minor parameter modifications and
mass modification purposes. 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 for GSM and core network, and Direct Activation for RNC functionalities
for modifying objects directly in the network.
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 planed and actual configuration with Table Editor
Managing templates: Creating and deleting templates, Editing templates,
Managing maintenance regions
Visualization for:

a) GSM Multi-BCF for Master BTS and BCCH TRX


b) Locked objects
c) Related objects

Version 1

Nokia Solutions and Networks

36 (90)

NetAct Configurator Applications

Configurator Applications
CM Editor
Editing & browsing through
actual and planned
configuration data
Integrated plan management

For all network elements


Parameter mass modification
Advanced search
Template management

Operator can compare


between actual and planned
parameters while editing
Find objects that match
specified criteria with
possibility to set new values
only to these objects
Templates to minimize user
errors

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 15

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.37 .(90)
. .
. .
. .

NetAct Configurator Applications

2.3

CM Analyzer

CM Analyzer is the tool for checking the consistency rules in radio network 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

Version 1

Nokia Solutions and Networks

38 (90)

NetAct Configurator Applications

Configurator Applications
CM Analyzer
Consistency checking for
Planned and actual configurations
Parameter values
Dependencies within a network
element and between network
elements
Overview of default rule check
Rule check result display

Possibility to define operatorspecific consistency checks

Scheduled start of consistency


checks
Automatic corrections of
inconsistencies
Detection of planning errors
including human errors at an
early stage
Higher quality of network plans

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 16

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.39 .(90)
. .
. .
. .

NetAct Configurator Applications

2.4

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. 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
Managing actual configuration:
Uploading actual configuration
Scheduling upload operations
Exporting actual configurations
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
Managing reference configuration:
Importing and exporting reference configuration, Creating plans on top of reference
configuration
Managing templates: Deleting templates, Importing and exporting templates
Visualising MML commands for R4 core network
Executing MML commands and MML command files for R4 core network and SGSN

Version 1

Nokia Solutions and Networks

40 (90)

NetAct Configurator Applications

Configurator Applications
CM Operations Manager
Efficient plan-based management
for large networks
Plan provisioning to network:
Prepare, pre-activate, activate,
fallback

Import plans from NSN or 3rd party


planning systems

Export actual data and plans


Compare planned with actual data

Keep NetAct Configurator up-todate with network element


Upload actual configuration
Operations Management:
Scheduling
All operations under control Real-time
feedback on progress of operation

History information on executed


operations

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 17

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.41 .(90)
. .
. .
. .

NetAct Configurator Applications

2.5

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.

Version 1

Nokia Solutions and Networks

42 (90)

NetAct Configurator Applications

Configurator Applications
CM Reference

Maintain Ideal Configuration


Ideal network
configuration as
reference configuration

Actual data upload


finished

Audit differences for


actual and reference

Statistical summary of
actual network and
reference configuration

View differences (delta)

Full control about


change process

Backup of approved
network configuration

Generate correction
plan to align NW
Provision plan to
NW

Implement change in
actual network
configuration, or accept
difference to reference
configuration

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 18

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.43 .(90)
. .
. .
. .

NetAct Configurator Applications

2.6

Hardware Management functionality

The Hardware Management functionality is designed to manage hardware equipment in the


network. NetAct Hardware Manager offers the operator an up-to-date knowledge of the
existing network hardware equipment used in the service delivery.
Hardware Manager 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

2.6.1

Benefits of Hardware Management

Hardware Manager 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 Manager 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.

Version 1

Nokia Solutions and Networks

44 (90)

NetAct Configurator Applications

Configurator Applications
Hardware Management
Main functionality

Main Functionality

Consolidated hardware configurations


view of different vendors/domains
Single or scheduled hardware
configuration data upload
Single or bulk hardware configuration
data export to XML and CSV files for
further processing
Sophisticated search engine
Hardware configuration change history

Extended NetAct Configurator UI with


Network Element hardware data
Significant increase in processing of
configuration objects
Single and mass hardware
configuration upload

Hardware data searching


Hardware configuration change history

Benefits
Automatic or manual collection of network elements hardware configuration data
Centralized place for hardware inventory information

Keep data up-to-date by support scheduled hardware configuration upload and support for
hardware change notification
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 19

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.45 .(90)
. .
. .
. .

NetAct Configurator Applications

Configurator Applications
Hardware Management
NetAct 8 Configurator:
Hardware Management functionality
is included in Configuration
Management applications: CM
Operations Manager and CM Editor.

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 20

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.46 .(90)
. .
. .
. .

NetAct Configurator Applications

Version 1

Nokia Solutions and Networks

47 (90)

Configurator Basic User Tasks

Version 1

Configurator Basic User Tasks

Nokia Solutions and Networks

48 (90)

Configurator Basic User Tasks

3.1

General Workflow

Configurator Basic User Tasks


General Workflow
Configurator Applications
CM Editor

2
CM Analyzer

Create and edit plans

NetAct Database

Check plans

CM Operations Manager

Make corrections to plans

Provision
plan to NE

NE Database

Upload Actual
configuration (optionally
also HW Information)

NE

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 21

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Version 1
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.49 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.2

Actual Configuration Upload

In the Upload dialog you can upload actual configurations and schedule an upload operation.
To upload actual configurations

1. From any view, click Upload > New Upload....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.

WARNING
Note: If you do not have the correct license, some upload options are disabled.
3. The selected objects are shown in the Scope of Upload pane.
4. Select additional options for the upload (specific fort he NE type, for example HW
upload)

5. In the Upload Information pane, enter a name of the upload operation (optional).
6. In the Upload Information pane, enter a description of the upload operation (optional).
7. In the Upload Information pane, select the level of information shown in the Feedback
dialog.

8. To start the upload, click Start.


9. A confirmation dialog opens. Click Yes.
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.

Version 1

Nokia Solutions and Networks

50 (90)

Configurator Basic User Tasks

Configurator User Tasks


Uploading Actual Configuration

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 22

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.51 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.3

Viewing Actual Configuration

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. Note that the MO classes and their parent
objects that are selected in the Editor View are shown in the navigation tree under the
Opened Plans node.
To view actual managed objects

1. Select Target Configuration > Actual Configuration.


2. Expand the Actual Configuration node in the navigation tree.
3. A list of root objects is shown. They are sorted alphabetically in ascending order based
on class and object instance.

4. Expand the root objects.


5. A list of managed objects is shown.
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.
Select the objects that you want to view.
The Parameters by Actual Managed Object view opens. Here you can see the values
for the actual managed objects in the network.

Version 1

Nokia Solutions and Networks

52 (90)

Configurator Basic User Tasks

Configurator User Tasks


Display of Actual Configuration
Actual Configuration:
Parameters of a selected MOI are
displayed alphabetically in a list
Several MOIs can be presented in
a table.
The views can be customized
regarding displayed parameters
Online help for all parameters

MOI - Managed Object Instance


1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 23

Version 1

Nokia Solutions and Networks

53 (90)

Configurator Basic User Tasks

3.4

Exporting Configuration

From the File menu, open the Export dialog.


In the Scope of Export pane, click Options. The Export Options dialog opens.
To select Actual or Reference Configuration
From the Export drop-down list, select either Actual Configuration or Reference
Configuration.
The plan is exported on the top of actual or reference configuration.
To select Export format, profile file, and parameters
From the Export Format drop-down list, select either RAML2.0 or CSV (comma-separated
values).
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.
A file selection dialog opens.
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.
In the Export pane, select the parameter values that you want to use.
Internal values - These are values used in the database.
Or
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.

Version 1

Nokia Solutions and Networks

54 (90)

Configurator Basic User Tasks

Configurator User Tasks


Exporting Configuration
Exchange actual and planned configurations
with external planning systems
Export of configuration data:
CSV format
XML format (RAML2)

Export granularity:
Single MOC or selected MOCs or all
MOCs of a single NE
All MOCs of a set of NEs
All MOCs of all NEs
The CSV export enables selection of specific
parameters and parameter ordering according
to user-definable profiles

Import of configuration data:


Identical format as for export
GUI option with same granularity for
data import as for the data export
Imported data is handled as planned
configuration
Imported data as delta import

Integration of Configurator into a planning system or


network-wide configuration management system

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 24

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.55 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.5

Displaying Plans

Opening plans
When you open a plan, it is shown in the navigation tree under the Opened Plans node.
To open a plan
Choose one of the following alternatives:
Click Plan > Open Plan.
Or
Right-click the Opened Plans node in the navigation tree and select Open Plan from the popup menu.
Or
On the toolbar, click the Open Plan icon.
Or
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.

Version 1

Nokia Solutions and Networks

56 (90)

Configurator Basic User Tasks

Configurator User Tasks


Displaying Plans

Plans are populated through


Copy from actual configuration
CM Operations Manager feature
'Import via Northbound I/F

Editor features are provided

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 25

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.57 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.6
3.6.1

Mass Parameter Changes and Plan Creation


Mass Parameter Changes

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.
To mass modify managed objects

1. Search for the corresponding managed objects from the database


a) To implement this step, choose one of the following alternatives:
I) When you want to search the whole network, Select Edit Search and Modify
Target Configuration...
II) Select Search and Modify Target Configuration... from the Managed Objects
pop-up menu.
III) Select Search and Modify Target Configuration... from the Actual/Reference
Configurations pop-up menu.

IV) Select Search and Modify Target Configuration... from a pop-up menu of any
MO in the plan or in the actuals/reference tree.

V) Click the Search and Modify Target Configuration icon on the toolbar.
b) From the Name drop-down list, select the name of the search. 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. 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. 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. 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.

Version 1

Nokia Solutions and Networks

58 (90)

Configurator Basic User Tasks

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.

3.6.2

Plan creation

You can create a new plan by creating an empty plan and adding modifications to it. See To
create a new plan.
To create a new plan

1. To implement this step, choose one of the following alternatives:


a) Select Plan New Plan....
b) In the toolbar, click New Plan.
c) Right-click the Opened Plans node in the Navigation tree and select New Plan from
the pop-up menu.
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.
Type in a new name and a description for the plan.
To save the modified information, click Update.

2.
3.
4. To add modifications to the plan and to see managed objects, check that the Show

5.
6.

Managed Objects in Plans option is selected and expand the nodes under the Managed
Objects node. 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. For instructions, see Editing parameters.
To create new managed objects, see Creating new managed objects in the plan.
To modify the parameter values of the managed objects, see Editing parameters.

Version 1

Nokia Solutions and Networks

59 (90)

Configurator Basic User Tasks

Configurator User Tasks


Mass Parameter Changes and Plans Creation
Parameter values can be changed for all selected MOIs in the table view:
Mass parameter changes also
through 'search & modify' feature

Possibility for complex search criteria


Search criteria can be used as criteria for mass
modification cases (i.e. change the LAC of the
cells that have current LAC value x)
Faster mass modifications: higher efficiency
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 26

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.60 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.7

Checking Plans

CM Analyser 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 Siemens Networks provides a set of basic consistency rules. The user can also create
own rules using an external text or XML editor.

Starting a new check


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.

1. To implement this step, choose one of the following alternatives:


a) Click Check New Check....
b) In the toolbar, click New Check.
c) In table of checks, right-click and select New Check... from the pop-up menu.
2.
3.

The New Check dialog opens


In the Check Name field, enter a name for the check. This step is optional.
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.
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. They will automatically be displayed in the lower pane. 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.

5. To remove a rule from the lower pane, select a rule and press the Delete key, or rightclick the selected rule and select Remove From Selected Rules from the pop-up menu.

6. On the Check Target tab, Check Target drop-down menu, select the target configuration
for the check. The target can be:

a) Actual Configuration
b) Plan on top of Actual Configuration
c) Reference Configuration
d) 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.

8. To implement this step, choose one of the following alternatives:


a) If you selected Plan on top of Actual Configuration or Plan on top of Reference
Configuration, the configurations are shown in the table below the Show plans owned

Version 1

Nokia Solutions and Networks

61 (90)

Configurator Basic User Tasks

by drop-down list. Select one plan from the table. A description for the selected plan is
shown in the Description of Plan (plan name) pane at the bottom of the tab.

b) If you selected Actual Configuration or Reference Configuration, mark the desired

9.

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.
On the Post-Check Actions tab, you can set CM Analyser to automatically correct the
inconsistencies it has found (if the rules support autocorrection). You can also set CM
Analyser to automatically send e-mail messages about the checks it has completed and
automatically include check results in these e-mail messages.

10. Click Start Check.


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.

Version 1

Nokia Solutions and Networks

62 (90)

Configurator Basic User Tasks

Configurator User Tasks


Checking Plans
Check procedure:
1. Start a new check

2. Select target for the check

(plan/ actuals)
3. Select one or several rules

for the check


4. Define post-check activities
5. Run the check
6. Analyze the results

High flexibility to check configurations

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 27

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.63 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.8

Provisioning Plans

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.
To prepare a plan

1. In the Plans tab, select the plan you want to prepare.


2. Open the Provision dialog. Click Plan > Provision.... Or
3. Right-click the plan and select Provision... in the pop-up menu. The Provision dialog
opens.

4. In the Provision pane, enter an optional name and description for the provisioning
5.

operation.
In the Operation pane of the Provision dialog, check Prepare Plan operation and
uncheck Provision operation.

TIP
The provision operation is checked by default. If the plan has not been prepared yet,
the prepare plan operation is also checked by default.
6. Click the Start button. A confirmation dialog opens.
7. In the confirmation dialog, click Yes.
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.

Version 1

Nokia Solutions and Networks

64 (90)

Configurator Basic User Tasks

Configurator User Tasks


Provisioning Plans

Open he Provision Dialog by selecting the Plan in the Plans list on the CM
Operations Manager pop-up menu or by selecting Provision from the
Operations Menu

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 28

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.65 .(90)
. .
. .
. .

Configurator Basic User Tasks

To provision plans

1. On the Plans tab, select the plan you want to provision.


2. Open the Provision dialog. Click Plan > Provision.... Or Right-click the plan and select
Provision... in the pop-up menu. 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.
5. In the Backup pane, you can create a backup plan for your plan.
6. By using the backup plan, you can roll back the network changes made by your original
7.

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.

8. Another backup plan is automatically created for a GSM plan when file-based
provisioning is not used.
In the Operation pane, select the provisioning operation you want to run.

9.
10. In the Scope pane, Entire Plan is selected by default. If you want to provision the plan
partially, deselect Entire Plan and select the objects to be included in the operation from
each tab.

TIP
Select the Upload after activation checkbox in the Options pane to automatically
upload actual configuration from network after provisioning operation.
11. Click the Start button. A confirmation dialog opens.
12. In the confirmation dialog, click Yes.
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.

Version 1

Nokia Solutions and Networks

66 (90)

Configurator Basic User Tasks

Configurator User Tasks


Provisioning Plans
2

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
Validate

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 29

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.67 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.9

Comparing plans to actual configuration

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.
To compare plans to actual configuration

1.
2.
3.
4.

Click Plan > Compare. The Compare dialog opens.


Enter the name of the operation to the Name field (optional).
Enter a short description for the operation in the Description field (optional).
Check the Generate Delta Plan check box (optional).
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.

5. Select Level of Feedback.


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.

6. Click the Start button. A confirmation dialog opens.


7. In the confirmation dialog, click Yes.
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..

Version 1

Nokia Solutions and Networks

68 (90)

Configurator Basic User Tasks

Configurator User Tasks


Comparing Plans with Actual Configuration
Reports differences between selected
plan and actual configuration :
Definable feedback level
Summary, object or parameter level

Delta plan generation & provisioning


Update the network according to the
plan. Operation supported in command
line interface

Review changes
Checking the plan effects to the network
before provisioning the plan

Verify plan implementation


Verifying that the plan has been
provisioned correctly to the network

Review history
To check if something changed after the
plan was provisioned to the network
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 30

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.69 .(90)
. .
. .
. .

Configurator Basic User Tasks

3.10

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.

Configurator User Tasks


Single or bulk upload of HW configuration data bundled with CM upload
CM Operations Manager:
Actual Configuration
Upload: Single or bulk
HW configuration upload.

Fig. 31

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Version 1
. . .
. . .
. . .

2014 Nokia Solutions and Networks. All rights reserved.

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.70 .(90)
. .
. .
. .

Configurator Basic User Tasks

Configurator User Tasks


Single or bulk export of hardware configuration data to XML and/or CSV
CM Operations Manager Actual
Configuration Export : Single and
multiple hardware configuration
export to CSV and XML file format.

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 32

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.71 .(90)
. .
. .
. .

Optimizer

Optimizer

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.
The advantages of the solution are:
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 (SON) solution: NetAct Optimizer is a key component in the
NSN 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 automated adjacency optimization
WCDMA automated adjacency optimization
GSM performance optimization
WCDMA performance optimization
GSM capacity analysis
WCDMA capacity analysis
Call location analysis
Antenna tilt optimization
Optimization of intra LTE neighbor relations (adjacency blacklisting)
Mobility robustness optimization

Version 1

Nokia Solutions and Networks

72 (90)

Optimizer

Multivendor support

Optimizer
Functionality Overview
Main functionality

Main functionality

Intelligent optimization in multivendor, multi-technology networks


Holistic view and full control of the
automated optimization networkwide
Automated handling of routine
tasks
Inbuilt intelligence in analysis and
algorithms

Easy trial and test bed licensing


with new and simple license
structure.
Optimizer is compatible with NetAct
Advanced Configurator enabling
faster multi-vendor integrations
KPI formulas aligned with NetAct
reporting functionality

Benefits
Automated, measurement based
optimization for operational GSM,
WCDMA and LTE radio networks.
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 33

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
Version 1
. . .
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
Nokia Solutions and Networks
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
73 (90)
. .
. .
. .
. .

Optimizer

NetAct Optimizer
Concept
Automation through NetAct
integration
Measurement based optimization

Actual CM data uploaded


automatically from NetAct
Automated access to KPIs
Optimisation results stored as plans
in NetAct database

GSM frequency and BSIC plan


optimization
Interference analysis for WCDMA
Antenna tilt optimization for
WCDMA
Seamless adjacency and
handover
management for GSM & WCDMA
Capacity and QoS optimization
Call Location Analysis for
WCDMA

Visualisation and analysis


functionality
Topology, parameters, KPIs in one
view

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 34

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.74 .(90)
. .
. .
. .

Optimizer

4.1

Optimizer main user interface

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.
The following figure shows the panes in the Optimizer main user interface:
The 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 Navigators 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).
The 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.
The Cell Groups/Scopes pane. 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.
Note:
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.
Version 1

Nokia Solutions and Networks

75 (90)

Optimizer

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.
The 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 andExporting 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, se 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.
The 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.
Note:
The tabbed windows of Optimizer - for example Map, Browser, Key Performance Indicators can be opened in a new window. To do this, righ-click the tab and select Open in New
Window. This functionality is particularly useful if you have a dual-screen monitor in use.

Version 1

Nokia Solutions and Networks

76 (90)

Optimizer

NetAct Optimizer
Main User Interface

Map / Tool
pane

Navigator
pane

Visualizations
Pane

Browser
Pane
Cell / groups
scope pane
1

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 35

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.77 .(90)
. .
. .
. .

Optimizer

4.2

Radio network optimization process in NetAct

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.
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 right 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.
Optimization can be targeted to improve the radio resource usage rate (optimization) by
changing the operating point on the capacity-coverage-cost trade-off curve. Statistical
optimization also sets the limits and operation targets for real time optimization loops, such
as radio resource management (RRM) in network elements.
Optimization is also involved when the network is enhanced with new cells or new services,
or changes are made in the service provisioning, and so on. As soon as elements are
activated in the network and they can be measured

Version 1

Nokia Solutions and Networks

78 (90)

Optimizer

Version 1

Nokia Solutions and Networks

79 (90)

Optimizer

NetAct Optimizer
Radio Optimization Process
Implement
with NetAct
Configurator

Measure and
Analyze with
Performance

Tune / Improve
with Optimizer

Manager

Analyze with
Optimizer

2014 Nokia Solutions and Networks. All rights reserved.

Fig. 36

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . 1.
Version
. . .
. . .
. . .

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

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

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

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

. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. Nokia
. . Solutions
. . . and
. Networks
. . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.80 .(90)
. .
. .
. .

Exercise

Version 1

Exercise

Nokia Solutions and Networks

81 (90)

Exercise

Version 1

Nokia Solutions and Networks

82 (90)

Exercise

Exercise 1
Title:
Objectives:

NetAct Configurator Concepts


Define the main concepts used in Configuration Management and
Optimizer
Explain the relationship between NetAct Configurator and Optimizer

Pre-requisite:

none

Query
1. What is the purpose of NetAct Configurator?

2. What is a plan in the Network Configuration?

3. What is the difference between the actual plan and all the other plans?. How the system
database gets the information for the actual plan?

4. List the main applications of NetAct Configurator

5. What is the main purpose of Optimizer? What ist he relationship between Optimizer and
the NetAct Configurator tools?

Version 1

Nokia Solutions and Networks

83 (90)

Exercise

Exercise 2
Title:
Objectives:
Pre-requisite:

Basic Configurator User Tasks


Use the Configurator applications to execute different configuration
tasks.
none

Task
1. Use one of the tools of NetAct Configurator to upload the configuration for one of the
Managed Objects in the system. Please also upload the HW Configuration. List the
steps required for this purpose.

Please see the procedure in the chapter material. For additional information see
the Online help manual for the application.

2. Use one of the tools of NetAct Configurator to see the configuration for the Managed
Object you selected in step 5. Please provide a list of some of the configuration
parameters for this MO. From where can you check the HW Information?

Please see the procedure in the chapter material. For additional information see
the Online help manual for the application.

Version 1

Nokia Solutions and Networks

84 (90)

Exercise

3. Use one of the tools of NetAct Configurator to see the plans created in the system.
Open one of those plans and Please provide a list of some of the configuration changes.
What MOs are involved?

Please see the procedure in the chapter material. For complementary


information see the Online help manual for the application.

Version 1

Nokia Solutions and Networks

85 (90)

Exercise

Version 1

Nokia Solutions and Networks

86 (90)

Solution

Version 1

Solution

Nokia Solutions and Networks

87 (90)

Solution

Version 1

Nokia Solutions and Networks

88 (90)

Solution

Solution
Title:
Objectives:
Pre-requisite:
Task
(Insert text and graphics here)

Query
(Insert text and graphics here)

Version 1

Nokia Solutions and Networks

89 (90)

Solution

Version 1

Nokia Solutions and Networks

90 (90)