Plug and Play For Radio Network Elements

NetAct™ 22
Configuring Radio Network Elements with

Plug and Play
DN1000023667
Issue: 1-0 Final
Dr aft
© 2021 Nokia. Nokia Confidential Information
Use subject to agreed restrictions on disclosure and use.

Configuring Radio Network Elements with DN1000023667 1-0 Disclaimer
Plug and Play
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and consulting with standards
bodies to ensure that terminology is inclusive and aligned with the industry. Our future customer documentation will be updated accordingly.
This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without
the prior written consent of Nokia.
This document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a product purchased or licensed from any company
within Nokia Group of Companies. Use this document as agreed. You agree to notify Nokia of any errors you may find in this document;
however, should you elect to use this document for any purpose(s) for which it is not intended, You understand and warrant that any
determinations You may make or actions You may take will be based upon Your independent judgment and analysis of the content of this
document.
Nokia reserves the right to make changes to this document without notice. At all times, the controlling version is the one available on Nokia’s
site.
No part of this document may be modified.
N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY
OR F IT NE SS FO R A PA RT ICU LAR PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T.
IN NO EVEN T WI L L NOK IA B E LI ABLE F OR AN Y DA M A G E S , I N C L U D I N G B U T N O T L I M I T E D TO S P E C I A L ,
D IRE CT, IN D IRECT, I NCI DE NTAL OR C ON SEQ UE N T IA L OR A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D TO LO SS
OF PRO F IT, REVE NU E, B US IN ESS IN T ER RU PT I ON , B U S I NE S S O P P O RT U N I T Y O R D ATA T H AT M AY A R I S E
FRO M T HE USE O F TH IS DO CU M EN T O R T HE IN F OR M AT IO N I N I T, E V E N I N T H E C A S E O F E R R O R S I N O R
OM IS SI O NS FRO M T HI S DOC UM EN T O R IT S CO NT E N T.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the
prior written consent of Nokia.
Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be
trademarks of their respective owners.
© 2021 Nokia.
© 2021 Nokia. Nokia Confidential Information
Use subject to agreed restrictions on disclosure and use.

Configuring Radio Network Elements with DN1000023667 1-0 Table of Contents
Plug and Play
Contents
1 Introduction to Plug and Play........................................................................................................................6
1.1 PnP overview............................................................................................................................................ 6
1.2 PnP scenarios........................................................................................................................................... 7
2 Upgrading factory software with Compatibility Service............................................................................12
3 Automatic rollback........................................................................................................................................ 13
4 Unified PnP workflows..................................................................................................................................14

4.1 Mediated Integration Planning................................................................................................................ 14
4.1.1 Prerequisites for Mediated Integration Planning............................................................................ 14
4.1.1.1 Applications for Mediated Integration Planning......................................................................15
4.1.1.2 Licenses for Mediated Integration Planning...........................................................................15
4.1.1.3 Preconfiguring NetAct for Autoconnection Service................................................................ 16
4.1.1.3.1 Creating a new Maintenance Region object..................................................................16
4.1.1.3.2 Setting up a new service user in NEAC........................................................................16
4.1.1.4 Preparing network for Mediated Integration Planning............................................................17
4.1.1.4.1 Site preparation..............................................................................................................17
4.1.1.4.2 DHCP server preparation.............................................................................................. 18
4.1.1.4.3 Certificate server preparation.........................................................................................18
4.1.1.4.4 Site routers preparation................................................................................................. 19
4.1.1.4.5 Secure and unsecure mode of autoconnection............................................................. 19
4.1.2 Preparation phase of Mediated Integration Planning..................................................................... 19
4.1.2.1 Planning a new mediated MRBTS.........................................................................................20
4.1.2.1.1 Preparing the configuration plan....................................................................................20
4.1.2.2 Planning the mediated MRBTS autoidentification operation..................................................21
4.1.2.3 Importing the MRBTS software package............................................................................... 23
4.1.2.4 Zero-touch planning................................................................................................................23
4.1.2.5 One-button planning using the workflow................................................................................24
4.1.2.6 Mediated MRBTS planning with the workflow....................................................................... 25
4.1.2.6.1 Starting the configuration planning with Workflow Engine.............................................26
4.1.2.6.2 Creating the configuration plan......................................................................................27
4.1.2.6.3 Integrating the mediated MRBTS to NetAct.................................................................. 28
4.1.2.6.4 Searching and applying the site template (optional)......................................................29
4.1.2.6.5 Validating and activating the configuration plan............................................................ 30
4.1.2.6.6 Activating the autoidentification..................................................................................... 30
4.1.3 Autoconnection phase of Mediated Integration Planning............................................................... 31
4.1.4 Autoconfiguration phase of Mediated Integration Planning............................................................31
4.1.5 Monitoring Mediated Integration Planning...................................................................................... 32
4.1.5.1 Operations History tab........................................................................................................... 32
4.1.5.2 CM Editor................................................................................................................................32
4.1.5.3 BTS Site Manager..................................................................................................................33
4.2 Direct Integration Planning......................................................................................................................33
NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 3

Final Use subject to agreed restrictions on disclosure and use.
Plug and Play
4.2.1 Prerequisites for Direct Integration Planning..................................................................................34

4.2.1.1 Applications for Direct Integration Planning........................................................................... 35
4.2.1.2 Licenses for Direct Integration Planning................................................................................ 35
4.2.1.3 Preconfiguring NetAct for Autoconnection Service................................................................ 36
4.2.1.3.1 Creating a new Maintenance Region object..................................................................36
4.2.1.3.2 Setting up a new service user in NEAC........................................................................36
4.2.1.4 Preparing network for Direct Integration Planning................................................................. 36
4.2.1.4.1 Site preparation..............................................................................................................37
4.2.1.4.2 DHCP server preparation.............................................................................................. 37
4.2.1.4.3 Certificate server preparation.........................................................................................38
4.2.1.4.4 Site routers preparation................................................................................................. 38
4.2.1.4.5 Secure and unsecure mode of autoconnection............................................................. 39
4.2.2 Preparation phase of Direct Integration Planning.......................................................................... 39
4.2.2.1 Planning a new direct network element.................................................................................40
4.2.2.1.1 Preparing the configuration plan....................................................................................40
4.2.2.2 Planning the direct network element autoidentification operation.......................................... 42
4.2.2.3 Importing the MRBTS software package............................................................................... 43
4.2.2.4 Zero-touch planning................................................................................................................43
4.2.2.5 One-button planning using the workflow................................................................................44
4.2.2.6 Direct network element planning with the workflow............................................................... 45
4.2.2.6.1 Starting the configuration planning with Workflow Engine.............................................46
4.2.2.6.2 Creating the configuration plan......................................................................................47
4.2.2.6.3 Searching and applying the site template (optional)......................................................49
4.2.2.6.4 Validating the configuration plan....................................................................................50
4.2.2.6.5 Activating the autoidentification..................................................................................... 50
4.2.3 Autoconnection phase of Direct Integration Planning.................................................................... 51
4.2.4 Autoconfiguration phase of Direct Integration Planning................................................................. 52
4.2.5 Monitoring Direct Integration Planning........................................................................................... 52
4.2.5.1 Operations History tab........................................................................................................... 53
4.2.5.2 CM Editor................................................................................................................................53
4.2.5.3 BTS Site Manager..................................................................................................................54
5 Restore BTS configuration with Plug and Play......................................................................................... 55

5.1 Overview of Restoring BTS configuration...............................................................................................55
5.2 Supported Network Element Releases...................................................................................................56
5.3 Prerequisites for BTS Configuration Restore......................................................................................... 56
5.3.1 Applications for BTS configuration restore..................................................................................... 57
5.3.2 Licences for BTS Configuration Restore........................................................................................57
5.3.3 Preconfiguring NetAct for Autoconnection Service........................................................................ 58
5.3.3.1 Creating a new Maintenance Region object.......................................................................... 58
5.3.3.2 Setting up a new service user in NEAC................................................................................ 58
5.4 Performing BTS configuration restore.................................................................................................... 59
5.4.1 Preparing Configuration Restore plan in NetAct............................................................................ 59
5.4.1.1 Starting Configuration Restore workflow with Workflow Engine............................................ 59
5.4.1.2 Performing the Configuration Restore Planning operation.....................................................59
5.4.1.3 (Optional) Updating a plan with any required changes..........................................................61

Plug and Play
5.4.2 Triggering Configuration restore from the BTS.............................................................................. 61

5.4.3 Automatic Rollback......................................................................................................................... 61
6 Centralized Plug and Play planning for multiple NetAct clusters............................................................ 62

6.1 Centralized PnP overview.......................................................................................................................62
7 NetAct DHCP service for PnP......................................................................................................................64

7.1 Overview..................................................................................................................................................64
7.2 Configuring NetAct DHCP service for PnP.............................................................................................64
7.2.1 Preparing input file for DHCP configuration................................................................................... 64
7.2.2 Generating PnP DHCP Configuration............................................................................................ 69

Configuring Radio Network Elements with DN1000023667 1-0 Introduction to Plug and Play
Plug and Play
1 Introduction to Plug and Play
1.1 PnP overview

Plug and Play (PnP) for radio network elements is a functionality that helps to efficiently deploy new
sites by simplifying the planning process and providing the automated site commissioning and configu-
ration once the new site is connected and identified by NetAct.
Typically the Plug and Play procedure consists of several steps. As a reference, see Figure 1:
Overview of Plug and Play.
Figure 1: Overview of Plug and Play
The generic PnP infrastructure is based on microservices located in NetAct and includes the following
components:
• PnP Autoconnection Service facilitates the new BTS identification and configuration. It uses
the NE3S protocol for the communication between BTS and NetAct. For more information, see
Overview of the Autoconnection Service in Administering Autoconnection Service.
• Compatibility Service performs the update of the factory software on BTS if a legacy factory
software (that is, without the NE3S support) is detected. It uses the BTS O&M protocol for the
communication between BTS and NetAct.
• NMS Load Balancer with DNAT routing function handles the routing of a new BTS message
between different PnP components throughout the PnP process. The DNAT router is configured
to route NE3S messages (port numbers 80/443) to PnP Autoconnection Service. Furthermore,
the DNAT router is configured to route BTS O&M messages to an iOMS as long as the iOMS is
deployed in your network. Otherwise, if no iOMS is deployed, the DNAT routes BTS O&M PnP
message Autoconnection Established Indication (AEI) to Compatibility Service.
For PnP scenarios and use-case examples, see PnP scenarios.

Plug and Play
1.2 PnP scenarios

In this section you learn to select a proper Plug and Play (PnP) scenario for a specific network
element. It also leads you through a few PnP exemplary use cases.
Before getting down to any PnP operations, see Table 1: PnP scenarios for radio network elements to
learn what PnP procedures are recommended for particular network elements.
Network element PnP procedure
Flexi Multiradio BTS LTE (FLF, TLF) Direct Integration Planning
Flexi Multiradio BTS LTE (FL, TL, SRAN) via Mediated Integration Planning
BTSMED
Flexi Multiradio BTS LTE (SRAN) Direct Integration Planning
AirScale 5G Classical BTS and DU Direct Integration Planning
AirScale Indoor Radio Direct Integration Planning
Classical 5G Direct Integration Planning
Single RAN BTS via BTSMED Mediated Integration Planning
Single RAN BTS (SRAN) Direct Integration Planning
Table 1: PnP scenarios for radio network elements

Plug and Play
Examples of PnP use cases
Autoconnection using the factory software (with the NE3S support) to BTS with NetAct and
BTSMED (SOAM architecture)
Figure 2: Autoconnection using the factory software (with the NE3S support) to BTS with NetAct and BTSMED (SOAM architec-
ture)
Description
1. Factory software with the NE3S support gets information from DHCP that the NE3S protocol can
be applied.
2. Factory software with the NE3S support registers to the PnP service IP address via the NE3S
agent discovery.
In case of a successful agent discovery, the PnP service triggers the topology update in NetAct
System Data Access (NASDA), which informs NetAct mediations (Configuration Management
(CM) or Software Management (SWM)) about a new node element.
3. Using the NE3S interface, Network Management System (NMS) manager (common mediation)
registers to the new node element with the factory software with the NE3S support still running
there. The temporary BTS IP address given from DHCP/ BTSEM is still in use.
4. Factory software with the NE3S support requests software update from Software Manager (SWM).

Plug and Play
Note: SWM retrieves the BTS target software version from BTS plan parameter Active
software release version (activeSwReleaseVersion).
5. Factory software with the NE3S support activates the SBTS target software and BTS is restarted.
6. At startup, the SOAM BTS reads a parameter file stored by the factory software and sets up the
connection to BTSMED.
7. BTSMED detects that the new connected SOAM BTS is in the uncommissioned state and sends
the prevalidated plan to BTS. SOAM BTS activates the plan and restarts. After the restart, BTS
informs BTSMED that its actual configuration has been modified by sending configuration change
notifications, next forwarding them to NetAct. The PnP status is updated.
Autoconnection using the factory software with the NE3S support into flat architecture
This scenario describes the BTS PnP high-level procedure when it is executed by COAM BTS soft-
ware and when PnP is supported by the PnP services in NetAct.
Figure 3: Autoconnection using the factory software with the NE3S support into flat architecture
Description
1. Factory software with the NE3S support is available and connects PnP Service via the NE3S
reRegistrationRequest message.
2. PnP service registers the new network element (NE3S agent on the factory software with the
NES3 support).

Plug and Play
3. After the network element identification, the topology update is triggered in NASDA and NetAct
registers to the factory software (with the NES3 support) with temporary BTS IP address.
4. CM/ SWM registers to the new network element.
5. Factory software with the NE3S support requests the BTS target software download from NetAct
SWM.
6. After the restart, the target COAM BTS sends the reRegistrationRequest message to PnP
Autoconnection (AC) Service.
7. PnP service triggers topology update in NASDA and NetAct registers to the agent on target COAM
BTS.
8. Target COAM BTS requests configuration data from CM by sending the
commissioningRequest notification.
9. After configuration provision and BTS restart the BTS sends Configuration Change Notification
(CCN) with the final IP address.
Update of the factory software without the NE3S support
This is a PnP scenario with autoconnection and the factory software without the NE3S support to
SBTS with NetAct and BTSMED (SOAM architecture). The PnP is supported by the PnP services in
NetAct.
Figure 4: Autoconnection using the factory software without the NE3S support to BTS with NetAct and BTSMED (SOAM
architecture)

Plug and Play
Note: The section above shows the scenario for SOAM BTS, while the similar flow may
apply also for flat COAM BTS in case an older factory software version without the NE3S
support is deployed on the BTS system module.
Description
1. Factory software without the NE3S support gets the IP address of PnP service from DHCP.
2. Factory software without the NE3S support sends BTS O&M AEI message to the DNAT router and
is routed to Compatibility Service.
Compatibility Service constructs the AER reply message so that the BTS reconnects with the mes-
sages to Compatibility Service.
3. Factory software without the NE3S support connects with Compatibility Service and downloads the
factory software with the NE3S support.
4. Factory software with the NE3S support is activated using restart and restarts autoconnection.
5. Factory software with the NE3S support gets information from the DHCP server that the NE3S
protocol can be applied.
6. Factory software with the NE3S support registers to PnP Service IP address via the NE3S agent
discovery. In case of the successful agent discovery, the PnP service triggers the topology update
in NASDA, which informs NetAct mediations (CM/ SWM) about the new node element.
7. Using the NE3S interface, the NMS manager (common mediation) registers to the new node
element with the factory software (with the NE3S support) still running there. The temporary BTS
IP address given from the DHCP is still in use.
8. Factory software with the NE3S support requests software update from the SWM.
9. Factory software with the NE3S support activates the BTS target software and BTS is restarted.
10. At startup, the SOAM BTS reads a parameter file stored by the factory software and sets up the
connection to BTSMED.
11. BTSMED detects that the newly-connected SOAM BTS is in the uncommissioned state and sends
the prevalidated plan to BTS. The SOAM BTS activates the plan and restarts.
12. After the restart, BTS informs BTSMED that its actual configuration has been modified by sending
configuration change notifications, next forwarding them to NetAct. The PnP status is updated.
13. Data cleanup, for example removing MRBTS from PLMN-PNP.

Configuring Radio Network Elements with DN1000023667 1-0 Upgrading factory software with
Plug and Play Compatibility Service
2 Upgrading factory software with Compatibility

Service
This section describes how to use Compatibility Service for upgrading your factory software or factory
release so that it supports Unified Plug and Play (PnP).
Compatibility Service (CS) enables an automatic upgrade of the factory software or the factory release
of radio products so that it supports the NE3S-based solution (hereinafter referred to as Unified PnP).
The upgrade, required before any Unified PnP operations, is executed using CS, which is deployed in
NetAct. The upgrade is required for all legacy releases, including FDSW 18A or preceding versions,
TLF/FLF 18A or preceding versions for Small Cell.
Tip: For more information on CS, see Overview of Compatibility Service in Administering
Compatibility Service.

Configuring Radio Network Elements with DN1000023667 1-0 Automatic rollback
Plug and Play
3 Automatic rollback
If an error occurs during the execution of the autoconnection process, the automatic rollback is
triggered. The automatic rollback removes temporary AgentDiscovery objects created during
the autoconnection process, which allows the system to retry the autoconnection when the network
element sends a re-register request.
You can check the reason for the rollback and track its progress using CM Operations Manager. For
more information on the rollback state, see PnP states in Administering Autoconnection Service.
The automatic rollback is enabled by default. For more information, see Configuring Automatic Roll-
back in Administering Autoconnection Service.

Configuring Radio Network Elements with DN1000023667 1-0 Unified PnP workflows
Plug and Play
4 Unified PnP workflows
4.1 Mediated Integration Planning

Mediated Integration Planning is a Workflow Engine procedure that enables you to prepare the da-
ta needed for the autoconnection of network elements, such as MRBTS, in NetAct. Mediated Integra-
tion Planning works with the Single Operations and Maintenance (SOAM) architecture, which utilizes
BTSMED, the mediator in the communication between NetAct and network elements.
Mediated Integration Planning can be performed in three variants:
• You launch the following operations one-by-one:
– Create BTS configuration plan

– Integrate BTS to NetAct
– Search and apply Site Template (optional)
– Validate and activate configuration plan
– Activate autoidentification
• One-button planning
You launch the whole planning process with one action, which automatically triggers all the other
planning operations in sequence. Optional steps can be easily disabled if needed.
• Zero-touch planning
You launch the planning process with CLI.
4.1.1 Prerequisites for Mediated Integration Planning

This section provides you with information on how to check if all requirements for Mediated Integration
Planning are met from the NetAct side.
Preconditions for Mediated Integration Planning:
• All required applications are present.
For more information, see Applications for Mediated Integration Planning.
• All necessary licenses are installed.
For more information, see Licenses for Mediated Integration Planning.
• Compatibility Service is configured to automatically upgrade the hardware with the NE3S-
compatible factory software.
For more information, see Upgrading factory software with Compatibility Service.
• Autoconnection Service is configured to orchestrate the Plug and Play process.

Plug and Play
For more information, seeConfiguring Autoconnection Service in Administering Autoconnection

Service.
• Network is configured to provide transmission and transport parameters for the new MRBTS.
For more information, see Preparing network for Mediated Integration Planning.
• An XML or CSV plan file is created and exported from a planning tool to a location in the NetAct
file system where you have access.
For more information, see Preparing the configuration plan.
• This step is optional. If required, NetAct DHCP service is configured to provide basic parameters
to the BTS. For more information see, Configuring NetAct DHCP service for PnP.
4.1.1.1 Applications for Mediated Integration Planning

The following applications are used during Mediated Integration Planning:
• Workflow Engine (available in NetAct CM Operations Manager) or CLI (racclimx.sh)

• NetAct Software Manager
Note: Software Manager is responding to BTS notification during the Plug and Play
process. This means that notification processing should be enabled in Software Manager
for the end to end PnP flow to work correctly. For details on enabling handling of these
notifications, see Notifications Preferences in Software Manager Help.
4.1.1.2 Licenses for Mediated Integration Planning

To perform Mediated Integration Planning, you need to have all the relevant licenses active in NetAct.
Required licenses depend on the configuration of MRBTSs, as Table 2: Licenses required for Mediat-
ed Integration Planning shows.
License
MRBTS configuration License name [code] Note
needed
MRBTS with only LTE LTE license Automated Site Creation In the plan, MNL
installed for LTE [4605] object's parameter
productVariantPlanned
is set to lteBTS.
MRBTS supporting Either SRAN • Automated Site Cre- In the plan, MNL
SRAN with only LTE in- license or ation for LTE [4605] needs parameter
stalled LTE license • CM Fast Network Roll- productVariantPlanned
out for SRAN [20281] set to a value other than
lteBTS.

Plug and Play
License
MRBTS configuration License name [code] Note
needed
All the other MRBTS SRAN license CM Fast Network Roll-out -

configurations for SRAN [20281]
Table 2: Licenses required for Mediated Integration Planning
Note: Table 2: Licenses required for Mediated Integration Planning are only general license
requirements for Mediated Integration Planning. To autoconnect and autoconfigure a
particular radio network element (NE) via Mediated Integration Planning, you may also need
NE-specific licenses. For more information, see relevant sections on NE-specific licenses in
Technology-specific PnP operations.
Note: When importing the plan in the CSV format, licenses for CSV are needed. For more
information, see NetAct Configurator licenses for radio network in NetAct Configuration
Management Licenses.
To check if you have the required licenses, follow instructions in Browsing licenses in License Manag-
er Help. For information on how to import licenses, see About License Manager in License Manager
Help.
4.1.1.3 Preconfiguring NetAct for Autoconnection Service
4.1.1.3.1 Creating a new Maintenance Region object
Autoconnection (AC) Service is configured to use the MR-PNP maintenance region by default. This
Maintenance Region (MR) needs to be created in NetAct Monitor before the Configuration restore
procedure is executed. This MR is used for temporary AgentDiscovery objects created during the
Configuration restore process.
For instructions on how to create a new MRobject, see Creating maintenance region in Object Explor-
er Help.
To configure AC Service to use a different MR name, see Autoconnection Service configuration file in
Administering Autoconnection Service.
4.1.1.3.2 Setting up a new service user in NEAC
New service user wsuser with service type SOAM Web Service Access needs to be created and
associated with the MR-PNP maintenance region. For the instructions, see Creating a service user in
NetAct repository in Network Element Access Control Help.
Verify application groups of the created service user to check if the user still needs to have any group
credentials to be granted or revoked. For the instructions on how to grant and revoke credentials, see
Granting or revoking service users for user groups in Network Element Access Control Help.

Plug and Play
Note: The service user needs access to the sysop application group.
Note: Default maintenance region and planned target maintenance region should have the
same wsuser credentials.
4.1.1.4 Preparing network for Mediated Integration Planning

You have to prepare the network and ensure it is configured properly so that you can follow up to au-
toconnection and autoconfiguration. Figure 5: Tasks to prepare network for Mediated Integration Plan-
ning shows the operations you need to perform for this purpose.
St art
Sit e preparat ion
DHCP server preparat ion
Cert ificat e server preparat ion
Sit e rout ers preparat ion
Secure and unsecure

m ode of aut oconnect ion
End
Figure 5: Tasks to prepare network for Mediated Integration Planning
Note:
PnP only works out of the box with the default network element password.
• If you want to use a different password during the PnP process, it should be changed
manually on the network element before triggering autoconnection.
• If you want to use a different password after the PnP process is completed, it should be
changed manually after the network element has reached the commissioned status.
4.1.1.4.1 Site preparation
Make sure that all necessary hardware and connections are operational on the site, for example, pow-
er cable, transmission link, antenna, and actual base station.

Plug and Play
4.1.1.4.2 DHCP server preparation
Autoconnection with the DHCP server
By default, BTS tries to execute the Plug and Play (PnP) autoconnection part completely autonomous-
ly, for example it tries to learn the transport and network configuration from the DHCP server.
In some networks, it can be impossible to operate the DHCP server for PnP. If so, the field installer
provides the needed minimized configuration with the factory software Rescue Console (RC).
Rescue Console
FDSW17SP introduces the GUI called Rescue Console (RC) to show alarms and the status of the
BTS software. It allows the user to perform operations to make the target software work properly. RC
is accessible using a web browser and no additional software installation is needed on the terminal.
If there is no PnP DHCP server deployed in the network, BTS loops in scanning for the DHCP serv-
er. This state is visible as the busy indication for DHCP Server Connection in the Plug and Play
progress section of the factory software RC Autoconnection tab. The field installer enters the need-
ed parameter configuration into the Autoconnection tab and starts the PnP sequence.
Autoconnection without the DHCP server
DHCP-less mode parameters can be either entered completely with the factory software RC Autocon-
nection tab or imported using an XML file and completed on demand.
Mandatory parameters:
• BTS IP address (local management plane IP address):
This parameter represents a temporary IP address used until the final site configuration gets
downloaded. With activation, the pre-configured final local M-plane IP address is taken in service
instead.
• Gateway (default gateway IP address)
• IP address (IP address of Autoconnection Service)
• BTS Operation and maintenance Peer Protocol (BtsOamPeerProtocol)
This parameter informs the factory software which Nokia PnP protocol is supported by NetAct. It
needs to be set to NE3S to be able to connect to Autoconnection Service.
4.1.1.4.3 Certificate server preparation
Certificate server needs to be preconfigured with the Nokia signing factory CA certificate and the
operator's root certificate as well as all the operator’s trusted certificates (trust anchors) that are to be
installed in MRBTS. For the automated initial deployment of the operator's certificates, the security
server needs to support CMPv2 Appendix E.7.
MRBTS uses the factory CA certificate to authenticate itself to the operator's CA server and automati-
cally acquires operator's certificates via CMP.

Plug and Play
The operator's certificate is used by both MRBTS and NetAct to verify the certificate information of
each other and to establish the TLS connection.
Certificate management requires specifying the IP and the port of the CMP/CA server. The CMP/CA
server is the point that the network element contacts for certificate download. Examples of the port
used in the CMP/CA server are 8080 and 8081.
4.1.1.4.4 Site routers preparation
Site routers have to be preconfigured to allow a new MRBTS to establish needed connections to the
DHCP server, security servers, and DNAT.
4.1.1.4.5 Secure and unsecure mode of autoconnection
NetAct supports both secured and unsecured mode of autoconnection. Secured connection is estab-
lished using IPSec and TLS to communicate with security gateway and Autoconnection Service. To
enable secured connections, MRBTS needs to receive the following information through DHCP offer:
• Security gateway IP address to enable IPSec connection towards security gateway.

• CMP server IP/port and subject name to enable secured connection with TLS towards AC Service.
If no PKI certificate server is part of the DHCP offer, then neither IPsec nor TLS connection is possi-
ble and MRBTS tries to connect to NetAct unencryptedly. If the certificate server address is delivered
but no VPN/SeGW address is provided, MRBTS tries to connect to NetAct with TLS protection for the
OAM traffic.
4.1.2 Preparation phase of Mediated Integration Planning

Before performing Mediated Integration Planning, the following prerequisites need to be met in NetAct
Configurator:
• Instructions in Prerequisites for Mediated Integration Planning are followed.
• New MRBTSs (not yet connected and commissioned) are configured in the plan file.
• At least one of the listed MRBTS identification mechanisms is configured in the plan:
– Autoconnection hardware ID to PnP (AutoConnHWID), defined in the MRBTS object

– Autoconnection site ID to PnP (AutoConnSiteID), defined in the MRBTS object
– Latitude, Longitude, and Ground Height, defined in the SITE object
For more information, see Autoidentification process in Administering Autoconnection Service.
• If GPS coordinates are used in the identification, the new MRBTS is assigned with the SITE
object: plan file contains the SITE object assigned to LNBTS.
For more information on how to assign the SITE object, see Assigning managed objects to a site
in CM Editor Help.

Plug and Play
• MRBTS software package is imported to NetAct and configured in the plan as in Importing the
MRBTS software package.
• If the CSV plan is used, the profile file is available for the plan. For more information, see Creating
the configuration plan.
• For both CSV and XML file formats, attribute operation needs value create for all managed
objects in the configuration plan.
XML example
<managedObject class="com.nokia.integrate:INTEGRATE"
version="INT_01" distName="PLMN-PLMN/MRBTS-1/INTEGRATE-1"
operation="create">
CSV example
PLMN-PLMN/MRBTS-1/INTEGRATE-1,,$operation,create
You can plan RNW, transmission, and site configuration for the new MRBTS using one of the fol-
lowing options:
– One-button planning using the workflow

– Zero-touch planning with CLI
– Manual Mediated MRBTS planning with the workflow
4.1.2.1 Planning a new mediated MRBTS

You can plan RNW, transmission, and site configuration for the new MRBTS into one plan file using
a suitable planning tool. A single plan file can contain one or multiple MRBTSs to be planned by the
workflow. For information on the preconditions for the preparation phase, see Preparation phase of
Mediated Integration Planning.
Note: In import, the detailed adaptation versions can be hidden from the planners and
planning tools using a simplified version. The planning tools can provide a plan file that
has the same simple version defined for every object. For more information on how to
configure simplified version in plan import, see Configuring simplified version in plan import in
Administering Configurator
As an alternative, Site Template can be used for planning new MRBTS. Site Template can be assigned
automatically. You only need to define a minimal set of parameters.
Site Template can be assigned in two ways: either Site Template name is defined in a plan or an iden-
tification string is included in Site Template and in the input file. For more information about Site Tem-
plates, see Site templates in CM Editor Help.
4.1.2.1.1 Preparing the configuration plan
You need to prepare the XML or CSV plan before Mediated Integration Planning. Your plan gets vali-
dated partially along Mediated Integration Planning.

Plug and Play
There are requirements and limitations you need to follow while preparing the plan:
• Only MRBTS under com.nokia.srbts or com.nokia.srbts.lte adaptations is supported.

• Executing the create operation needs to be possible for all the objects in the plan.
• For the CSV plan, the profile file is needed for executing the import operation.
• Each MRBTS needs properly-set identification parameters so that it can be identified by Autocon-
nection (AC) Service. The mandatory set is:
– Autoconnection hardware ID to PnP (AutoConnHWID)

– Autoconnection site ID to PnP (AutoConnSiteID)
– Latitude, Longitude, and Ground Height, defined in the SITE object assigned to
MRBTS
NOTICE: All network elements to be planned with AC Service using Mediated Integration
Planning have to be uniquely identifiable with identification parameters. If more than one
network element are identified with the same parameters, the Plug and Play (PnP) pro-
cedure is discontinued from the identification step. For more information, see Autoidenti-
fication process in Administering Autoconnection Service.
• Definitions of objects used during the Plug and Play process, such as INTEGRATE or NeIdentity-
Data, are available in Object Information Browser on NetAct Start Page.
• Each MRBTS needs one INTEGRATE object and one MNL object with all their parameters set
properly.
• Each MRBTS needs a properly-associated Maintenance Region (MR). The target MR can be
planned as a different MR but with default wsuser credentials.
• Value of the plannedSWReleaseVersion parameter is copied from the INTEGRATE object
to the MNL object. plannedSWReleaseVersion needs to match the software package up-
loaded in Software Manager (SWM). The software package in SWM is set up for both MRBTS and
BTSMED.
Note: If the MNL object has its own value set for plannedSWReleaseVersion, it gets
overwritten with the INTEGRATE object's parameter value.
4.1.2.2 Planning the mediated MRBTS autoidentification operation

Executing the Unified PnP - SOAM - Activate autoidentification operation is mandatory for the
MRBTS autoconnection operation.
You have to plan the MRBTS autoidentification before autoconnection as a part of the MRBTS configu-
ration plan.
Note: You can plan the MRBTS autoidentification operation when creating a new MRBTS
plan file. If not, you have to do it after importing the plan file using the Unified PnP - SOAM -
Create BTS configuration plan workflow.

Plug and Play
You should configure MRBTS identification parameters using the imported plan file. For instructions on
creating the configuration plan, see Creating the configuration plan.
Note: Alternatively, you can configure MRBTS identification parameters manually using CM
Editor. For more information, see Planning a new mediated MRBTS.
There are three possible ways of the MRBTS autoidentification:
• Autoconnection Hardware ID
It is a module serial number provided by the MRBTS manufacturer.
To use this identification type, the Autoconnection Hardware ID parameter value of the
MRBTS managed object has to be planned as a part of the MRBTS configuration plan or,
alternatively, configured in the CM Editor application by setting the Autoconnection hardware
ID to PnP (AutoConnHWID) parameter of the MRBTS object in the plan. If nothing is planned/
configured, this mechanism is not used.
• Autoconnection Site ID
Autoconnection Site ID is a string value freely defined at the planning phase by the planner user.
To use this identification type, the Autoconnection Site ID parameter value of the MRBTS
managed object has to be planned as a part of the MRBTS configuration plan or, alternatively,
configured in the CM Editor application by setting the Autoconnection site ID to PnP
(AutoConnSiteID) parameter of the MRBTS object in the plan. It has to match the value defined
using BTS Element Manager locally on the site (by the installation team) during the planning
phase. If nothing is planned, this mechanism is not used.
• GPS-based identification
This type of identification is based on geographic location information of MRBTS. GPS data can
be retrieved from the GPS module of MRBTS (installed optionally) or configured into MRBTS by
the installation team.
You can enable the GPS-based identification with operation parameters while planning. For more
information, see: Zero-touch planning, One-button planning using the workflow, and Activating the
autoidentification.
Note: There is no need to use all of the identification mechanisms. However, if the GPS
autoidentification is used and more than one MRBTS are installed in the same place, you
can additionally use either Site ID or Hardware ID to distinguish between MRBTSs.
To plan GPS-based identification parameters using CM Editor, open CM Editor and set the GPS-
based identification parameters, which are Ground Height, Latitude, and Longitude of the
SITE object assigned to the LNBTS object of the eNB in the plan.
For more information on how to modify parameters values in the plan, see Editing parameters in CM
Editor Help.

Plug and Play
4.1.2.3 Importing the MRBTS software package
You have to import a software package for the new MRBTS to NetAct using Software Manager.
For instructions, see Importing software package to Software Archive in Software Manager Help.
Additionally, the value of the Planned software release version

(plannedSWReleaseVersion) parameter from the INTEGRATE object has to be planned as a
part of the MRBTS configuration plan to identify and download a proper software to MRBTS during
autoconfiguration.
4.1.2.4 Zero-touch planning

Zero-touch BTS configuration option enables the MRBTS configuration to be imported from a planning
tool to Configurator using a command line request without user attention. Configurator processes the
imported files using the autoconfiguration workflow operations in Configurator autonomously so that
the initial configuration is completed, validated, and the auto-identification is activated. As a result of
these operations, NetAct is ready to autoconnect and autoconfigure MRBTS.
1. As the omc user, log in to a virtual machine where the cmwas-<nodeName> service is running.
For more information, see Locating the right virtual machine for a service in Administering NetAct
Virtual Infrastructure.
2. Enter the following command:
racclimx.sh -op Unified_PnP_SOAM_Site_Preparation \

-planName [name of the plan] \
-fileFormat [format of plan file, RAML2/CSV] \
-inputFile [full name of the input file] \
-profileFile [name of profile file, used when fileFormat is CSV] \
-UIValues [whether param values should be treated as UI ones in
plan file, values: true/false, default: false] \
-integrateBTS [whether the 'Integrate BTS to NetAct' step should
be executed, values: true/false, default: true] \
-activateSiteTemplate [whether the 'Search and apply Site
Template' step should be executed, values: true/false, default: true]
\
-GPSIdentificationUsed [whether the GPS based identification
should be used, values: true/false, default: false] \
-GPSTolerance [Tolerance for GPS coordinates in meters, values:
range from 0 to 5000]
Note:
• If you enter only the racclimx.sh -op

Unified_PnP_SOAM_Site_Preparation command without any options, all the
available options are displayed in the screen.
• If a plan with a given name already exists in the CM database, the plan creation
operation fails.

Plug and Play
• -inputFile default location is /var/opt/nokia/oss/global/racops/

import/
• GPS-based identification is disabled by default. If you want to use it, set
GPSIdentificationUsed to true and GPSTolerance to a desired tolerance for
GPS coordinates in meters within range from 0 to 5000.
• Parameter names in the commands are case sensitive. Quotes are needed around
the argument value if the value contains space characters. For example, if the value
of planName argument is New Plan, the argument and the value should be entered
as follows: -planName "New Plan".
• The Search and apply Site Templates operation is optional and launched by default.
Use the activateSiteTemplate parameter to disable it.
Expected outcome
As a result, the creation of the MRBTS plan, validation, and autoidentification are finished and details
are presented as the command line output.
4.1.2.5 One-button planning using the workflow
Note: One-button planning can be used for the maximum of 150 MRBTSs in one plan.
The Unified PnP - SOAM - One-button planning operation is introduced to minimize your effort dur-
ing MRBTS configuration planning. Instead of performing each task separately, you can start automat-
ically performing a set of operations and following feedback for details. To use this functionality, follow
the instruction:
1. Open CM Operations Manager and in the menu bar select Tools and then Workflow Engine.
2. From the Operation List drop-down list, select the Unified PnP - Mediated Integration Planning
option.
3. Select Unified PnP - SOAM - One-button planning by clicking Start next to the operation name.
4. Fill in the Plan Name field with a desired plan name.
Note: Your Plan Name needs to be unique. If your plan name duplicates any existing
plan name, the plan creation operation fails.
5. Navigate to the desired plan file using Plan file chooser.

a) Provide the Input file location.
b) Choose either the RAML2 file format or the CSV file format.

Plug and Play
Note: For the CSV file format, Profile file chooser gets active.
6. If your chosen plan contains UI values (not internal ones) as values of parameters, change the
value in the UI values combo box from the default one to Yes.
7. If you want to skip optional workflow steps Integrate BTS to NetAct and/ or Activate site
templates, change values displayed in corresponding combo boxes to No. For more information
see, Integrating the mediated MRBTS to NetAct and Searching and applying the site template
(optional).
8. If you want to enable the GPS-based identification operation, set GPS identification used to
Yes and GPS tolerance (m) to a desired tolerance for GPS coordinates in meters within range
from 0 to 5000.
9. Select Start.
10. In the confirmation dialog, select Yes to confirm the operation.
Expected outcome
As a result, the creation of the MRBTS plan starts, and details are presented in the feedback pane.
4.1.2.6 Mediated MRBTS planning with the workflow

Figure 6: Tasks in the manual Mediated MRBTS planning shows the steps you need to perform in the
MRBTS planning workflow.

Plug and Play
Figure 6: Tasks in the manual Mediated MRBTS planning
NOTICE: You need to perform the workflow operations one after another in the required
order, except for the optional Search and apply Site Template operation.
4.1.2.6.1 Starting the configuration planning with Workflow Engine
1. Open CM Operations Manager.
2. Select Tools → Workflow Engine...
You can also open Workflow Engine by right-clicking the plan in the plan list and from the pop-up
menu select Workflow Engine for Plan...
3. From Operation list, select Unified PnP - Mediated Integration planning.

Plug and Play
As a result, all the operations available for Unified PnP - Mediated Integration planning are dis-
played on a list, including steps for the MRBTS manual configuration planning.
4.1.2.6.2 Creating the configuration plan
You can either create your plan from scratch, which is done with procedure Creating the configuration
plan from scratch, or merge a newly-created configuration to the existing one, done with procedure
Merging a newly-created configuration to the existing one. Either way, with this operation, you import
your plan to CM. This plan is required in the subsequent workflow steps.
4.1.2.6.2.1 Creating the configuration plan from scratch
1. From the Operation column, select Unified PnP - SOAM - Create BTS configuration plan by
clicking Start next to the operation name.
2. To use plan file in a particular format, go to the Start pane and choose
• CSV format
1. Choose CSV file format from the File format drop-down list.
2. Click the ... button next to the Input file field, and navigate to the directory where generic
CSV plan file is stored, select proper file, and click Open (or double-click the CSV file).
3. Click the ... button next to the Profile file field, and choose a proper profile file for the pre-
viously selected CSV plan file.
Or
• RAML format
1. Choose RAML format from the File format drop-down list.

RAML plan file is stored, select proper file, and click Open (or double-click the RAML file).
3. Fill in the Plan name field with a desired plan name.
Note: Your Plan name needs to be unique. If your plan name duplicates any existing
plan name, the plan creation operation fails.
5. In the Start pane, select Start.

Plug and Play
Expected outcome
As a result, the configuration plan is updated for MRBTS in the Configurator plan database and it is
selected as default for further workflow operations.
4.1.2.6.2.2 Merging a newly-created configuration to the existing one
1. Start Workflow Engine by right-clicking the plan in the plan list and selecting Workflow Engine
for Plan... from the pop-up menu.
2. From Operation list, select Unified PnP - Mediated Integration Planning and, in the Operation
column, click Unified PnP - SOAM - Create BTS configuration plan.
3. To use plan file in a particular format, go to the Start pane and choose
• CSV format
Or
• RAML format

Expected outcome
As a result, the configuration plan is updated for MRBTS in the Configurator plan database and it is
4.1.2.6.3 Integrating the mediated MRBTS to NetAct
Each MRBTS should have the INTEGRATE object with all the parameters set properly in the plan. For
more information, see Preparing the configuration plan.

Plug and Play
Note: If any MRBTS misses the INTEGRATE object or any of the object's parameters is not
set properly, the operation fails. Missing objects and parameters are listed in the feedback
pane so that you can fix the plan manually with CM Editor.
With this operation, you set up objects in Configuration Management tools and NetAct Monitor.
Note: You can skip this operation if you opt to integrate objects manually and mark them as
operational in Configuration Management tools. These actions are mandatory before pro-
ceeding to Searching and applying the site template (optional).
1. From the Operation column, select Unified PnP - SOAM - Integrate BTS to NetAct by clicking
Start next to the operation name.
2. In the Start pane, click Start.
3. In the confirmation dialog, click Yes to confirm triggering the operation.
Expected outcome
The desired MRBTS is integrated to NetAct and visible in all NetAct applications, for example Monitor
or Software Manager.
Note: If the corresponding MRBTS already exists in NetAct applications, its integration is
skipped.
4.1.2.6.4 Searching and applying the site template (optional)
You can import all necessary MRBTS parameters using the plan file. Alternatively, the import plan file
can contain only a subset of MRBTS parameters and the rest can be defined using site template oper-
ations. For more information about creating site templates, see Site templates in CM Editor Help.
Note: To find the corresponding site template using the Site Template description parameter
under the MRBTS managed object, you can use regular expressions.
1. From the Operation column, select Unified PnP - SOAM - Search and apply Site Template by
3. In the confirmation dialog, click Yes to confirm the operation.
Expected outcome
As a result, a suitable site template, if exists, is found and applied for MRBTS. If more than one site
templates is found for the same MRBTS, no template is applied. Available templates are listed in the
feedback dialog and can be assigned manually using CM Editor by configuring the Site template
name (siteTemplateName) parameter value for the MRBTS object with a desired template name.

Plug and Play
4.1.2.6.5 Validating and activating the configuration plan
The imported plan is sent to BTSMED and validated at the same time. The validation is done for the
complete plan.
1. In the Operation column, select Unified PnP - SOAM - Validate and activate configuration plan
by clicking Start next to the operation name.
Note: If the validation fails, you need to correct the plan in CM Editor and repeat the
validation operation.
Expected outcome
As a result, potential planning errors are corrected and the plan is provisioned to BTSMED for
download and activation to MRBTS. The planned configuration is also visible in CM Editor.
4.1.2.6.6 Activating the autoidentification

This operation sends identification parameters to Autoconnection (AC) Service.
For information on AC Service, see Overview of the Autoconnection Service in Administering Autocon-
nection Service.
1. In the Operation column, select Unified PnP - SOAM - Activate autoidentification by clicking
2. If you want to enable the GPS-based identification operation, set GPS identification used to
Yes and GPS tolerance (m) to a desired tolerance for GPS coordinates in meters within range
from 0 to 5000.
Expected outcome
The identification parameters are sent to the AC service.
Note: Check that the feedback of this operation is successful. You can check the list
of network elements planned in AC Service by referring to Command line options in

Plug and Play
4.1.3 Autoconnection phase of Mediated Integration Planning

After you have successfully completed the preparation phase, the autoconnection phase can be trig-
gered.
1. MRBTS gets vendor-specific parameters and the IP address of NetAct load balancer from DHCP.
2. MRBTS sends a request for integration to NetAct.
3. Plug and Play (PnP) Autoconnection (AC) Service:

a) Creates an AgentDiscovery object under PLMN-PNP with a connectivity data as the
temporary MRBTS. All NetAct applications, such as Monitor, CM Editor, and Software
Manager, are informed about the new object.
b) Uploads the identification data from MRBTS. As a result, the NeIdentityData object
is created. It contains information on a selected identification method in the following
parameters: Global Navigation Satellite System receiver coordinates
(geoCoordinates), Serial number (serialNumber), and Site description
(siteDescription).
c) Identifies MRBTS based on the planned data and the data received in the NeIdentityData
object.
d) Sends results to MRBTS by provisioning the NeIdentificationResults object.
e) Deletes the temporary AgentDiscovery object used as the temporary MRBTS.
4.1.4 Autoconfiguration phase of Mediated Integration Planning

After a successful autoconnection, MRBTS requests for configuration.
1. MRBTS requests for the target software from Software Manager.

2. MRBTS downloads and installs the software. Then, it restarts.
3. At startup, MRBTS sets up the connection to BTSMED.
4. BTSMED provisions the prevalidated plan to MRBTS.
5. Upload is triggered to get the full actual configuration from MRBTS.
Note: After successful autoconfiguration, optionally you can run the Unified PnP - Plan
actual compare operation to check possible errors that might have occurred during the plan
activation. The Unified PnP - Plan actual compare operation is a part of the Unified PnP -
Maintenance operations and troubleshooting workflow.
Note: If the first instance of a new network element release is deployed using the PnP
process, Software Manager cannot recognize it immediately as a supported network element
version. As a result, the software download operation to the network element fails with error:
missing support for the requested software version. The PnP process can
be resumed after Software Manager has updated its cache, which is refreshed every 10

Plug and Play
minutes. Within this time frame, Software Manager acquires the information on the new
network element version and the next software download completes successfully.
4.1.5 Monitoring Mediated Integration Planning
There are several possibilities to view the status of Mediated Integration Planning operations.
The following Configurator applications can be used:
• Operations History tab in CM Operations Manager.
For more information, see Operations History tab.
• E-mail and SMS notification.
For more information, see Configuring e-mail notification settings in CM Operations Manager Help.
• CM Editor.
For more information, see CM Editor.
• BTS Site Manager.
For more information, see BTS Site Manager.
4.1.5.1 Operations History tab
The Operations History tab in the CM Operations Manager application allows you to view statuses of
Mediated Integration Planning steps one by one in real-time.
4.1.5.2 CM Editor
With the CM Editor application, you can verify whether the autoconnection is successful and see a cur-
rent status of the autoconfiguration by checking parameter values.
If the autoconnection is successful, the CommissioningRequest object is created according to the

CCN request.
To monitor the autoconfiguration process, you can check a value of the Auto Configuration
Status (autoConfStatus) parameter under the AgentDiscovery-1/BtsState-1 managed
object. See available statuses in Table 3: Values of parameter autoConfStatus.
autoConfStatus value Visibility
0 - Not started Not visible
1- Planning started Not visible
2 - Planning failed Not visible
3 - Planning completed Not visible

Plug and Play
4 - Identification requested PLMN-PNP/AgentDiscovery/BtsState
5 - Identification finished PLMN-PNP/AgentDiscovery/BtsState
6 - Identification failed PLMN-PNP/AgentDiscovery/BtsState
7 - Software download requested PLMN-PNP/MRBTS/AgentDiscovery/BtsState
8 - Software download started PLMN-PNP/MRBTS/AgentDiscovery/BtsState
9 - Software installation finished PLMN-PNP/MRBTS/AgentDiscovery/BtsState
10 - Software installation failed PLMN-PNP/MRBTS/AgentDiscovery/BtsState
11 - Configuration download requested PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
12 - Configuration download started PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
13 - Configuration activation started PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
14 - Configuration provision failed PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
15 - Autoconfiguration completed PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
Table 3: Values of parameter autoConfStatus
4.1.5.3 BTS Site Manager

Installation team can also monitor autoconnection and autoconfiguration using the BTS Site Manager
tool.
The status of each operation is presented in the autoconfiguration window.
Successful operations are marked with green color, failed with red. In addition, tooltips are shown for
finished operations.
4.2 Direct Integration Planning

Direct Integration Planning is a Workflow Engine procedure that enables you to prepare the data need-
ed for the autoconnection of network elements, such as MRBTS and ASI, in NetAct. Direct Integration
Planning works with the Common Operations and Maintenance (COAM) architecture or any other type
of the flat architecture that provides the direct communication between NetAct and network elements
without mediators.
Direct Integration Planning can be performed in three variants:
• You launch the following operations one-by-one:
– Create BTS configuration plan

– Search and apply Site Template (optional)

Plug and Play
– Validate configuration plan

– Activate autoidentification
• One-button planning
You launch the whole planning process with one action, which automatically triggers all the other
planning operations in sequence. Optional steps can be easily disabled if needed.
• Zero-touch planning
You launch the planning process with CLI.
4.2.1 Prerequisites for Direct Integration Planning

This section provides you with information on how to check if all requirements for Direct Integration
Planning are met from the NetAct side.
Preconditions for Direct Integration Planning:
For more information, see Applications for Direct Integration Planning.
For more information, see Licenses for Direct Integration Planning.
For more information, seeConfiguring Autoconnection Service in Administering Autoconnection

Service.
• Pre-validation is enabled.
To enable the pre-validation, follow the instruction in Enabling pre-validation in Administering Con-
figurator.
• Network is configured to provide transmission and transport parameters for the new BTS.
For more information, see Preparing network for Direct Integration Planning.
• An XML or CSV plan file is created and exported from a planning tool to a location in the NetAct
file system where you have access.
For more information, see Preparing the configuration plan.
• This step is optional. If required, NetAct DHCP service is configured to provide basic parameters
to the BTS. For more information, see Configuring NetAct DHCP service for PnP.

Plug and Play
4.2.1.1 Applications for Direct Integration Planning
The following applications are used during Direct Integration Planning:
• CM Editor
• CM Operations Manager (Workflow Engine) or CLI for racclimx.sh
• Software Manager
• BTS Element Manager (optionally)
4.2.1.2 Licenses for Direct Integration Planning

To perform Direct Integration Planning, you need to have all the relevant licenses active in NetAct. Re-
quired licenses depend on the configuration of MRBTSs, as Table 4: Licenses required for Direct Inte-
gration Planning shows. In case of ASI the licenses are checked based on the Host MRBTS.
Site Technology License needed License code
SRAN Only 2G SRAN CM Fast Network Roll-

out for SRAN [20281]
Only 3G SRAN CM Fast Network Roll-

Only LTE SRAN or LTE • Automated Site

Creation for LTE
[4605]
• CM Fast Network
Roll-out for SRAN
[20281]
LTE (FL/TL/FLF/TLF) Only LTE LTE Automated Site Cre-

ation for LTE [4605]
5G Only 5G 5G CM Fast Network Roll-

out for 5G [55031]
Table 4: Licenses required for Direct Integration Planning
Note: When importing the plan in the CSV format, licenses for CSV are needed. For more

Plug and Play
Note: In case of ASI the licenses based on Host MRBTS can have 5G or SRAN-LTE license.
Help.
4.2.1.3 Preconfiguring NetAct for Autoconnection Service
4.2.1.3.1 Creating a new Maintenance Region object
er Help.
4.2.1.3.2 Setting up a new service user in NEAC
4.2.1.4 Preparing network for Direct Integration Planning

You have to prepare the network and ensure it is configured properly so that you can follow up to au-
toconnection and autoconfiguration. Figure 7: Tasks to prepare network for Direct Integration Planning
shows the operations you need to perform for this purpose.

Plug and Play
St art
Sit e preparat ion
DHCP server preparat ion
Cert ificat e server preparat ion
Sit e rout ers preparat ion
Secure and unsecure

m ode of aut oconnect ion
End
Figure 7: Tasks to prepare network for Direct Integration Planning
Note: PnP only works out of the box with the default network element password.
• If you want to use a different password during the PnP process, it should be changed
manually on the network element before triggering autoconnection.
• If you want to use a different password after the PnP process is completed, it should be
changed manually after the network element has reached the commissioned status.
4.2.1.4.1 Site preparation
Make sure that all necessary hardware and connections are operational on the site, for example, pow-
er cable, transmission link, antenna, and actual base station.
4.2.1.4.2 DHCP server preparation
Autoconnection with the DHCP server
By default, BTS tries to execute the Plug and Play (PnP) autoconnection part completely autonomous-
ly, for example it tries to learn the transport and network configuration from the DHCP server.
In some networks, it can be impossible to operate the DHCP server for PnP. If so, the field installer
provides the needed minimized configuration with the factory software Rescue Console (RC).
Rescue Console
FDSW17SP introduces the GUI called Rescue Console (RC) to show alarms and the status of the
BTS software. It allows the user to perform operations to make the target software work properly. RC
is accessible using a web browser and no additional software installation is needed on the terminal.

Plug and Play
If there is no PnP DHCP server deployed in the network, BTS loops in scanning for the DHCP serv-
er. This state is visible as the busy indication for DHCP Server Connection in the Plug and Play
progress section of the factory software RC Autoconnection tab. The field installer enters the need-
ed parameter configuration into the Autoconnection tab and starts the PnP sequence.
Autoconnection without the DHCP server
DHCP-less mode parameters can be either entered completely with the factory software RC Autocon-
nection tab or imported using an XML file and completed on demand.
Mandatory parameters:
• BTS IP address (local management plane IP address):
This parameter represents a temporary IP address used until the final site configuration gets
downloaded. With activation, the pre-configured final local M-plane IP address is taken in service
instead.
• Gateway (default gateway IP address)
• IP address (IP address of Autoconnection Service)
• BTS Operation and maintenance Peer Protocol (BtsOamPeerProtocol)
This parameter informs the factory software which Nokia PnP protocol is supported by NetAct. It
needs to be set to NE3S to be able to connect to Autoconnection Service.
4.2.1.4.3 Certificate server preparation
Certificate server needs to be preconfigured with the Nokia signing factory Certification Authority (CA)
certificate and the operator's root certificate as well as all the operator’s trusted certificates (trust an-
chors) that are to be installed in network element (NE). For the automated initial deployment of the
operator's certificates, the security server needs to support CMPv2 Appendix E.7.
MRBTS uses the factory CA certificate to authenticate itself to the operator's CA server and automati-
cally acquires operator's certificates via CMP.
The operator's certificate is used by both NE and NetAct to verify the certificate information of each
other and to establish the TLS connection.
Certificate management requires specifying the IP and the port of the CMP/CA server. The CMP/CA
server is the point that the network element contacts for certificate download. Examples of the port
used in the CMP/CA server are 8080 and 8081.
4.2.1.4.4 Site routers preparation
Site routers have to be preconfigured to allow a new network element to establish needed connections
to the DHCP server, security servers, and DNAT.

Plug and Play
4.2.1.4.5 Secure and unsecure mode of autoconnection
NetAct supports both secured and unsecured mode of autoconnection. Secured connection is estab-
lished using IPSec and TLS to communicate with security gateway and Autoconnection Service. To
enable secured connections, network element (NE) needs to receive the following information through
DHCP offer:
• Security gateway IP address to enable IPSec connection towards security gateway.

• CMP server IP/port and subject name to enable secured connection with TLS towards AC Service.
Note: To allow minimum autoconnectivity procedure, at least the IP address of the

management peer, for example, NetAct load balancer of the responsible NetAct OAM
system has to be delivered as a DHCP vendor-specific attribute. If this is not received by
NE, the autoconfiguration procedure fails. If it fails, it waits for a manual autoconfiguration
performance of the operation, which is a file based delivery of the missing IP connectivity
information with the help of the BTS Site Element Manager.
If no PKI certificate server is part of the DHCP offer, then neither IPsec nor TLS connection is possible
and NE tries to connect to NetAct unencryptedly. If the certificate server address is delivered but no
VPN/SeGW address is provided, NE tries to connect to NetAct with TLS protection for the OAM traffic.
4.2.2 Preparation phase of Direct Integration Planning

Before you can perform the network element (NE) autoconnection and autoconfiguration, the following
prerequisites need to be met in NetAct Configurator:
• Instructions described in the Prerequisites for Direct Integration Planning chapter are fulfilled.
• New NEs (not yet connected and commissioned) are configured in the plan file.
• At least one of the listed NE identification mechanisms is configured in the plan:
– Hardware ID - NE: the Auto connection hardware ID parameter

– Site ID - NE: the Auto connection site ID parameter
– GPS based identification
For more information, see Autoidentification process in Administering Autoconnection Service.
• If GPS coordinates are used in the identification, the new NE is assigned with the SITE object.
For more information on how to assign the SITE object, see Assigning managed objects to a site
in CM Editor Help.
• NE software package is imported to NetAct and configured in the plan.
• Profile file is created if you use the CSV plan file format.
• For both CSV and XML file formats, attribute operation needs value create for all managed
objects in the configuration plan.

Plug and Play
XML example
<managedObject class="com.nokia.integrate:INTEGRATE"
version="INT_01" distName="PLMN-PLMN/MRBTS-1/INTEGRATE-1"
operation="create">
CSV example
PLMN-PLMN/MRBTS-1/INTEGRATE-1,,$operation,create
You can plan RNW, transmission, and site configuration for the new NE using one of the following:
– One-button planning using the workflow

– Zero-touch planning with CLI
– Manual Direct network element planning with the workflow
4.2.2.1 Planning a new direct network element

You can plan RNW, transmission, and site configuration for the new network element (NE) in one plan
file using a suitable planning tool. For information on preconditions for the preparation phase, see
Preparation phase of Direct Integration Planning.
There is no need to put all new NEs into the same plan file. You can divide them into several plan files.
During the plan file import into the Configurator database, you can keep the plan file content separated
by creating another plan.
Note: In import, the detailed adaptation versions can be hidden from the planners and
planning tools using a simplified version. The planning tools can provide a plan file that
has the same simple version defined for every object. For more information on how to
configure simplified version in plan import, see Configuring simplified version in plan import in
Administering Configurator.
As an alternative, Site Template can be used for planning the new NE. Site Template can be assigned
automatically. You only need to define a minimal set of parameters.
Site Template can be assigned in two ways: either Site Template name is defined in a plan or an iden-
tification string is included in Site Template and in the input file. For more information about Site Tem-
plates, see Site templates in CM Editor Help.
4.2.2.1.1 Preparing the configuration plan
You need to prepare the XML or CSV plan before Direct Integration Planning. Your plan gets validated
partially along Directed Integration Planning.
There are requirements and limitations you need to follow while preparing the plan:
MRBTS ASI
• Only MRBTS under the com.nokia.srbts and • Only ASI under com.nokia.asi adaptation are
com.nokia.mrbts adaptation are supported. supported.

Plug and Play
MRBTS ASI
• Executing the create operation needs to be • Executing the create operation needs to be
possible for all the objects in the plan. possible for all the objects in the plan.
• For the CSV plan, the profile file is needed • For the CSV plan, the profile file is needed
for executing the import operation. for executing the import operation.
• Each MRBTS needs properly-set identifica- • Each ASI needs properly-set identification
tion parameters so that it can be identified by parameters so that it can be identified by Au-
Autoconnection (AC) Service. The mandatory toconnection (AC) Service. The mandatory
set is: set is:
– Autoconnection hardware ID to PnP: the – Autoconnection hardware ID to PnP: the

AutoConnHWID parameter. AutoConnHWID parameter.
– Autoconnection site ID to PnP: the Au- – Autoconnection site ID to PnP: the Au-
toConnSiteID parameter. toConnSiteID parameter.
– GPS based identification (defined in the – GPS based identification (defined in the
SITE object). SITE object).
• Each MRBTS needs one INTEGRATE object • Each ASI needs one INTEGRATE object (no
and one MNL object with all their parameters MNL object is needed)
set properly. • Each ASI needs a properly-associated Main-
• Each MRBTS needs a properly-associated tenance Region (MR). The target MR can be
Maintenance Region (MR). The target MR planned as a different MR but with default
can be planned as a different MR but with de- wsuser credentials.
fault wsuser credentials. • All ASI objects should have the 'hostDN' pa-
• Value of the PlannedSWReleaseVersion rameter value provided.
parameter is copied from the INTEGRATE
object to the MNL object. PlannedSWRe-
leaseVersion needs to match the soft-
ware package uploaded in Software Manager
(SWM). The software package in SWM is set
up for both MRBTS and BTSMED.
Table 5: Configuration plan requirements
NOTICE: All network elements to be planned with AC Service using Direct Integration Plan-
ning have to be uniquely identifiable with identification parameters. If more than one network
element are identified with the same parameters, the Plug and Play (PnP) procedure is dis-
continued from the identification step. For more information, see Autoidentification process in
Note: If the MNL object has its own value set for PlannedSWReleaseVersion, it gets
overwritten with the INTEGRATE object's parameter value.

Plug and Play
4.2.2.2 Planning the direct network element autoidentification operation
Note: Planning the Unified PnP - COAM - Activate autoidentification operation is

mandatory for the network element (NE) autoconnection operation.
You have to plan the NE autoidentification before autoconnection as a part of the MRBTS configura-
tion plan.
Note: You can plan the NE autoidentification operation when creating a new NE plan file. If
not, you have to do it after importing plan file using the Unified PnP - COAM - Create BTS
configuration plan workflow.
You should configure NE identification parameters using imported plan file. For instructions on creating
configuration plan, see Creating the configuration plan.
Note: Alternatively, you can configure NE identification parameters manually using CM

Editor. For more information, see Planning a new direct network element.
There are three possible ways of the NE autoidentification:
• Autoconnection Hardware ID
It is a module serial number provided by the NE manufacturer.
To use this identification operation, the Autoconnection Hardware ID parameter value of

the NE managed object has to be planned as a part of the NE configuration plan or, alternatively,
configured in the CM Editor application by setting AutoConnHWID parameter of the NE object in
the plan. If nothing is planned/configured, this mechanism is not used.
• Autoconnection Site ID
Autoconnection Site ID is a string value freely defined at the planning phase by the planner user.
To use this identification operation, you need to plan the Autoconnection Site ID parameter
value of NE as a part of the NE configuration plan and also configure it in NE using BTS Element
Manager locally on the site (by the installation team). If nothing is planned, this mechanism is not
used.
• GPS based identification
This type of identification is based on geographic location information of NE. GPS data can be re-
trieved from the GPS module of NE (installed optionally) or configured into NE by the installation
team.
You can enable the GPS-based identification with operation parameters while planning. For more
information, see One-button planning using the workflow, and Activating the autoidentification.
Note: There is no need to use all of the identification mechanisms. However, in case
GPS autoidentification is used and if more than one NE is installed in the same place,

Plug and Play
you can either additionally use Site ID or Hardware ID to distinguish NEs from each
other.
To plan GPS based identification parameters using CM Editor, open CM Editor and set the
GPS based identification parameters which are: GPS Antenna Altitude, GPS Antenna
Latitude, and GPS Antenna Longitude of the Site object assigned to the NE object of the
network element in the plan.
For more information on how to modify parameters values in the plan, see Editing parameters in CM
Editor Help.
4.2.2.3 Importing the MRBTS software package

You have to import a software package for the new network element (NE) to NetAct using Software
Manager.
For instructions, see Importing software package to Software Archive in Software Manager Help.
Additionally, the value of the Planned software release version parameter has to be planned
as a part of the NE configuration plan to identify and download a proper software to NE during
autoconfiguration.
4.2.2.4 Zero-touch planning

Zero-touch BTS configuration option enables the network element (NE) configuration to be imported
from a planning tool to Configurator using a command line request without user attention. Configura-
tor processes the imported files using the autoconfiguration workflow operations in Configurator au-
tonomously so that the initial configuration is completed, validated, and the autoidentification is activat-
ed. As a result of these operations, NetAct is ready to autoconnect and autoconfigure NE.
1. As the omc user, log in to a virtual machine where the cmwas-<nodeName> service is running.
For more information, see Locating the right virtual machine for a service in Administering NetAct
Virtual Infrastructure.
2. Enter the following command:
racclimx.sh -op Unified_PnP_COAM_Site_Preparation \

-planName [name of the plan to be created based on input file] \
-fileFormat [file format, RAML2 or CSV] \
-inputFile [full name of the input file] \
-profileFile [name of profile file, used when fileFormat is CSV] \
-UIValues [whether param values should be treated as UI ones in
plan file, values: true/false, default: false] \
-activateSiteTemplate [whether the 'Search and apply Site
Template' step should be executed, values: true/false, default: true]
\
-GPSIdentificationUsed [whether the GPS based identification
should be used, values: true/false, default: false] \

Plug and Play
-GPSTolerance [Tolerance for GPS coordinates in meters, values:

range from 0 to 5000]
Note:
• If you enter only the racclimx.sh command without any options, all the options are
displayed on the screen.
• If a plan with a given name already exists in the CM database, the plan creation
operation fails.
• -inputFile default location is /var/opt/nokia/oss/global/racops/
import/
• GPS-based identification is disabled by default. If you want to use it, set
GPSIdentificationUsed to true and GPSTolerance to a desired tolerance for
GPS coordinates in meters within range from 0 to 5000.
• Parameter names in the commands are case sensitive. Quotes are needed around
the argument value if the value contains space characters. For example, if the value
of the planName argument is New Plan, the argument and the value should be
entered as follows: -planName "New Plan"
• The Search and apply Site Templates operation is optional and launched by default.
Use the activateSiteTemplate parameter to disable it.
As a result, the creation of the NE plan, validation, and autoidentification are finished and details
are presented in the feedback pane.
4.2.2.5 One-button planning using the workflow
Note: One-button planning can be used for the maximum of 150 network elements (NE) in
one plan.
The Unified PnP - COAM - One-button planning operation is introduced to minimize your effort dur-
ing MRBTS configuration planning. Instead of performing each task separately, you can perform a set
of operations automatically and see resulting feedback for details. To use this functionality, follow the
instruction:
1. Open CM Operations Manager and in the menu bar select Tools and then Workflow Engine.
2. From the Operation List drop-down list, select the Unified PnP - Direct Integration Planning
option.
3. Select Unified PnP - COAM - One-button planning by clicking Start next to the operation name.
4. In the Plan Name field, type a desired plan name.

Plug and Play
Note: The plan name needs to be unique. If the plan name duplicates any existing plan
name, the plan creation operation fails.
5. Navigate to the desired plan file using Plan file chooser.

a) Provide the Input file location.
b) Choose either the RAML2 file format or the CSV file format.
Note: For the CSV file format, Profile file chooser gets active.
7. If you want to use optional workflow step Activate site templates, change the value displayed in
the corresponding combo box to Yes. For more information, see Searching and applying the site
template (optional).
8. If you want to enable the GPS-based identification operation, set:

a) GPS identification used to Yes
b) GPS tolerance (m) to a desired tolerance for GPS coordinates in meters within range from
0 to 5000
9. Click Start.
Expected outcome
The creation of the NE plan starts, and details are presented in the feedback pane.
4.2.2.6 Direct network element planning with the workflow

Figure 8: Tasks in the manual direct NE planning shows the steps you need to perform in the network
element (NE) planning workflow.

Plug and Play
Figure 8: Tasks in the manual direct NE planning
Note: You need to perform the workflow operations one after another.
4.2.2.6.1 Starting the configuration planning with Workflow Engine
1. Open CM Operations Manager.
2. Select Tools → Workflow Engine...
You can also open Workflow Engine by right-clicking the plan in the plan list and then selecting
Workflow Engine for Plan... from the pop-up menu.
3. From the Operation List drop-down list, select Unified PnP - Direct Integration planning.

Plug and Play
Expected outcome
All the operations available for Unified PnP - Direct Integration planning are displayed on a list,
including steps for the network element manual configuration planning.
4.2.2.6.2 Creating the configuration plan
You can either create your plan from scratch, which is done with procedure Creating the configuration
plan from scratch, or merge a newly-created configuration to the existing one, which is done with
procedure Merging a newly-created configuration to the existing one. Either way, with this operation,
you import your plan to CM. This plan is required in the subsequent workflow steps.
4.2.2.6.2.1 Creating the configuration plan from scratch
1. From the Operation column, select Unified PnP - COAM - Create BTS configuration plan by
2. To use plan file in a particular format, go to the Start pane and choose:
• CSV format
Or
• RAML format

3. Fill in the Plan name field with a desired plan name.

Plug and Play
Note: The plan name needs to be unique. If the plan name duplicates any existing plan
name, the plan creation operation fails.
4. If the chosen plan contains UI values (not internal ones) as values of parameters, change the
5. If your chosen plan contains site templates and you want to use it, change the value in the
Activate Site Templates combo box from the default one to Yes.
6. If your chosen plan contains NEs for which GPS base identification is defined, change change the
value in the GPS identification used combo box from the default one to Yes. Then fill in GPS
tolerance (m) field with proper value.
7. If your chosen plan contains NEs for which maintenance region is not defined fill in the
Maintenance Region DN field with desired data.
Note: Example of a valid format: MRC-1/MR-NE3S
Expected outcome
As a result, the configuration plan is updated for network element in the Configurator plan database
and it is selected as default for further workflow operations.
4.2.2.6.2.2 Merging a newly-created configuration to the existing one
1. Start Workflow Engine by right-clicking the plan in the plan list and selecting Workflow Engine
for Plan... from the pop-up menu.
2. From Operation List drop-down list, select Unified PnP - Direct Integration Planning.
3. In the Operation column, click Unified PnP - COAM - Create BTS configuration plan.
4. To use plan file in a particular format, go to the Start pane and choose:
• CSV format

Plug and Play
Or
• RAML format

5. If your chosen plan contains site templates and you want to use it, change the value in the
Activate Site Templates combo box from the default one to Yes.
6. If your chosen plan contains NEs for which GPS base identification is defined, change change the
value in the GPS identification used combo box from the default one to Yes. Then fill in GPS
tolerance (m) field with proper value.
7. If your chosen plan contains NEs for which maintenance region is not defined fill in the
Maintenance Region DN field with desired data.
Note: Example of a valid format: MRC-1/MR-NE3S
Expected outcome
The configuration plan is updated for network element in the Configurator plan database and it is
4.2.2.6.3 Searching and applying the site template (optional)
You can import all necessary network element (NE) parameters using the plan file. Alternatively, the
import plan file can contain only subset of NE parameters and the rest can be defined using the Site
Template operation. For more information about creating site templates, see Site templates in CM Edi-
tor Help.
Note: To find the corresponding site template using the Site Template description parameter
under the NE managed object, you can use regular expressions.

Plug and Play
4.2.2.6.3.1 To search and apply the site template as a part of manual planning
1. From the Operation column, select Unified PnP - COAM - Search and apply Site Template by
Expected outcome
A suitable site template, if exists, is found and applied for network element (NE). If more than one
site template is found for the same NE, no template is applied. Available templates are listed in the
feedback dialog and can be assigned manually using CM Editor by configuring the Site template
name (siteTemplateName) parameter value for the NE object with a desired template name.
4.2.2.6.4 Validating the configuration plan
The validation is performed for a complete plan.
1. In the Operation column, select Unified PnP - COAM - Validate configuration plan by clicking
Note: If the validation fails, you need to correct the plan in CM Editor and repeat the
validation operation.
Expected outcome
Potential planning errors are corrected and the plan is acceptable for network element to be
downloaded and activated.
4.2.2.6.5 Activating the autoidentification

This operation sends identification parameters to Autoconnection (AC) Service.
For information on AC Service, see Overview of the Autoconnection Service in Administering Autocon-
nection Service.

Plug and Play
Prerequisites
Make sure that a proper identification method is chosen and configured in the plan before proceeding.
For instructions, see Planning the direct network element autoidentification operation.
1. In the Operation column, select Unified PnP - COAM - Activate autoidentification by clicking
2. If you want to enable the GPS-based identification operation, set:

a) GPS identification used to Yes
b) GPS tolerance (m) to a desired tolerance for GPS coordinates in meters within range from
0 to 5000
Expected outcome
The identification parameters are sent to the AC service.
Note: Check that the feedback of this operation is successful. You can check the list
of network elements planned in AC Service by referring to Command line options in
4.2.3 Autoconnection phase of Direct Integration Planning

When the preperation phase is successfully completed, the autoconnection phase can be triggered.
1. Network element (NE) gets vendor-specific parameters and the IP address of NetAct load balancer
(DNAT) from DHCP.
2. NE sends the NE3S reRegistration request to NetAct.
3. Plug and Play (PnP) Autoconnection (AC) Service:

a) Creates an AgentDiscovery object under PLMN-PNP with a connectivity data as the
temporary NE. All NetAct applications, such as Monitor, CM Editor, and Software Manager, are
informed about the new object.
b) Uploads the identification data from NE. As a result, the NeIdentityData object is created. It
contains information about geoCoordinates, serialNumber, and siteDescription.
c) Identifies NE based on the planned data and the data received in the NeIdentityData
object.
d) Sends results to MRBTS by provisioning the NeIdentificationResults object.
e) Deletes the temporary AgentDiscovery object used as the temporary NE.

Plug and Play
4.2.4 Autoconfiguration phase of Direct Integration Planning

After a successful autoconnection, network element requests for configuration.
In case of MRBTS
1. MRBTS requests for the target software from Software Manager (SWM).
2. MRBTS downloads and installs the software. Next, it restarts.
3. At startup, MRBTS contacts CM to get the configuration plan.
4. CM provisions the prevalidated plan to MRBTS.
5. Upload is triggered to get the full actual configuration from MRBTS.
6. M-plane IP address of MRBTS gets updated in NetAct connectivity database.
In case of ASI
1. ASI contacts CM to get the configuration plan.

2. Upload is triggered to get the full actual configuration from ASI.
3. M-plane IP address of ASI gets updated in NetAct connectivity database.
Note: For M-plane IP address, only a pure IP address is supported - no support of Fully
Qualified Domain Name (FQDN).
Note: After successful autoconfiguration, you can run the Unified PnP - Plan actual
compare operation to check possible errors that might have occurred during the plan
activation. Unified PnP - Plan actual compare operation is optional.
Note: If the first instance of a new network element release is deployed using the PnP
process, SWM cannot recognize it immediately as a supported network element version.
As a result, the software download operation to the network element fails with an error:
missing support for the requested software version. The PnP process can
be resumed after SWM has updated its cache, which is refreshed every 10 minutes. Within
this time frame, SWM acquires the information on the new network element version and the
next software download completes successfully.
4.2.5 Monitoring Direct Integration Planning

There are several possibilities to view the status of network element autoconfiguration operations.
The following Configurator applications can be used:
• The Operations History tab in CM Operations Manager.
For more information, see Operations History tab.
• E-mail and SMS notification.

Plug and Play
For more information, see Configuring e-mail notification settings in CM Operations Manager Help.
• CM Editor.
For more information, see CM Editor.
• BTS Site Manager.
For more information, see BTS Site Manager.
4.2.5.1 Operations History tab

The Operations History tab in the CM Operations Manager application allows you to view statuses of
network element autoconfiguration steps one by one in real-time.
4.2.5.2 CM Editor
With the CM Editor application, you can verify whether the autoconnection is successful and see the
current status of the autoconfiguration by checking parameter values.
If the autoconnection is successful, the CommissioningRequest object is created according to the

CCN request.
To monitor the autoconfiguration process, you can check a value of the Auto Configuration
Status parameter under the AgentDiscovery-1/BtsState-1 managed object. See available statuses
in Table 6: Values of parameter autoConfStatus for MRBTS and Table 7: Values of parameter
autoConfStatus for ASI.
7 - Software download requested PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
8 - Software download started PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
9 - Software installation finished PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
10 - Software installation failed PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
11 - Configuration download requested PLMN-PLMN/MRBTS/AgentDiscovery/BtsState

Plug and Play
12 - Configuration download started PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
13 - Configuration activation started PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
14 - Configuration provision failed PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
15 - Autoconfiguration completed PLMN-PLMN/MRBTS/AgentDiscovery/BtsState
Table 6: Values of parameter autoConfStatus for MRBTS
11 - Configuration download requested PLMN-PLMN/ASI/AgentDiscovery/BtsState
12 - Configuration download started PLMN-PLMN/ASI/AgentDiscovery/BtsState
13 - Configuration activation started PLMN-PLMN/ASI/AgentDiscovery/BtsState
14 - Configuration provision failed PLMN-PLMN/ASI/AgentDiscovery/BtsState
15 - Autoconfiguration completed PLMN-PLMN/ASI/AgentDiscovery/BtsState
Table 7: Values of parameter autoConfStatus for ASI
4.2.5.3 BTS Site Manager
The installation team can also monitor autoconnection and autoconfiguration using the Rescue Con-
sole tool (for the factory software) and the BTS Site Manager tool (for the dedicated software).
The status of each operation is presented in the autoconfiguration window.
Successful operations are marked with green color, failed with red. In addition, tooltips are shown for
finished operations.

Configuring Radio Network Elements with DN1000023667 1-0 Restore BTS configuration with Plug and
Plug and Play Play
5 Restore BTS configuration with Plug and Play
5.1 Overview of Restoring BTS configuration

The configuration restore feature allows to activate new BTS configuration when:
• Replacing defective system module hardware.

• Configuration reset is triggered on BTS.
Dedicated configuration restore workflow allows to create new configuration based on actual config-
uration or historical data before process is started. Executing the workflow also sends BTS identifica-
tion information to Autoconnection Service which is required for successful identification of the hard-
ware. The hosting eNB restore planning will take care of ASiR planning as well. ASI can be planned
as a standalone operation. AsiDN must be set under MRBTS for the single eNB and ASIR restore
planning.
Used components:
• Autoconnection Service facilitates the new BTS identification and configuration. For more
information, see Overview of the Autoconnection Service in Administering Autoconnection
Service.
Note: BTS software upgrade scenario is not supported when the release version is
changed.
• Configuration Management

Plug and Play Play
Figure 9: Restoring BTS configuration overview
5.2 Supported Network Element Releases

Configuration restore is supported by the following network elements.
Network element Network element releases
Flexi Multiradio BTS LTE (FLF/TLF) LTE20B and onwards
Flexi Multiradio BTS LTE (FL/TL) SRAN20B and onwards
Single RAN BTS SRAN20B and onwards
ASIR ASI20C onwards
Table 8: Supported network elements
5.3 Prerequisites for BTS Configuration Restore

This section provides you with information on how to check if all requirements for BTS Configuration
Restore are met from the NetAct side.
Preconditions for BTS Configuration Restore:
For more information, see Applications for BTS configuration restore.

Plug and Play Play
For more information, see Licences for BTS Configuration Restore.
For more information, see Configuring Autoconnection Service in Administering Autoconnection

Service.
• Pre-validation is enabled.
To enable the pre-validation, follow the instruction in Enabling pre-validation in Administering Con-
figurator.
• All ASI objects should have the 'hostDN' parameter value provided.
5.3.1 Applications for BTS configuration restore

The following applications are used during BTS configuration restore:
• CM Editor
• CM Operations Manager (Workflow Engine) or CLI for racclimx.sh
• Software Manager
• BTS Element Manager (optional)

• CM History (optional)
5.3.2 Licences for BTS Configuration Restore

To perform BTS Configuration Restore, you need to have all the relevant licenses active in NetAct. Re-
quired licenses depend on the configuration of MRBTSs, as Table 9: Licenses required for BTS Con-
figuration Restore shows.
SRAN Only 2G SRAN CM Fast Network Roll-

Only 3G SRAN CM Fast Network Roll-


Plug and Play Play
Only LTE SRAN or LTE • Automated Site

Creation for LTE
[4605]
• CM Fast Network
Roll-out for SRAN
[20281]
LTE (FL/TL/FLF/TLF) Only LTE LTE Automated Site Cre-

ation for LTE [4605]
Table 9: Licenses required for BTS Configuration Restore
Note: When importing the plan in the CSV format, licenses for CSV are needed. CM History
license is also required if operator wants to restore historical configurations. For more
Help.
5.3.3 Preconfiguring NetAct for Autoconnection Service
5.3.3.1 Creating a new Maintenance Region object
er Help.
5.3.3.2 Setting up a new service user in NEAC

Plug and Play Play
5.4 Performing BTS configuration restore

This subchapter explains how to restore BTS configuration from NetAct.
5.4.1 Preparing Configuration Restore plan in NetAct

This chapter explains how to plan Configuration Restore using dedicated workflow.
5.4.1.1 Starting Configuration Restore workflow with Workflow Engine

This chapter describes how to start the Configuration Restore Planning operation.
1. Open CM Operations Manager. For instructions on how to open CM Operations Manager,

seeOpening CM Operations Manager in CM Operations Manager Help
2. Select the Tools → Workflow Engine... option.
3. From the Operation List drop-down list, select Configuration Restore.
Expected outcome
Configuration Restore Planning operations are displayed on a list. On the right pane there are
operations descriptions and available options.
5.4.1.2 Performing the Configuration Restore Planning operation

Configuration Restore Planning workflow is performed for both Configuration Reset and Hardware
Replacement scenarios. Only one MRBTS/ASI is allowed in the operation scope at once.
1. Drag and drop or copy-paste the selected MRBTS/ASI object into the MO(s) field.
2. In the Operation column, select the Configuration Restore planning operation, by clicking Start
next to the operation's name.
3. Choose any combination of the following identification methods. At least one identification methods
needs to be selected for successful planning:

Plug and Play Play
• AutoconnectionHardwareID - to choose this method, fill the Autoconnection hardware ID

panel.
• AutoconnectionSiteID - to choose this method, fill the Autoconnection site ID panel.
• GPS based method - to choose this method, check the GPS identification used option and
fill the GPS Tolerance panel. The MRBTS/ASI object from the scope must be assigned to the
selected SITE object that has assigned geographical coordinates.
Note: In Configuration Reset scenario, current identification data

methods should be used. For MRBTS this value can be found at
MRBTS/AgentDiscovery/NEIdentityData and for ASIR, it can be found at
ASI/AgentDiscovery/NEIdentityData managed object.
Note: In Hardware Replacement scenario, new identification data of new hardware

should be provided. Hardware ID is mandatory if you want the update to be properly
reflected in CM non-network parameters.
4. From the Select configuration for restore drop-down list select one of the following options:
• Actual Configuration - this option restores configuration from Actual Configuration, without
creating a plan. The final Plan will be automatically generated at runtime.
• Plan based on Actual - this option creates a plan based on Actual Configuration, but
configuration can be edited before provisioning it into network. This option can be used in
cases where some parameters need to be modified or a different software build is required on
the BTS.
Note: The software build should match the adaptation version in the CM plan.
Hence, only minor changes in software version are supported with this scenario.
• Historical Configuration - this option creates a plan based on any historical configuration
from CM History.
Note: CM History license is mandatory to use this option.
6. In the confirmation dialog, click Yes .
Expected outcome
The Activate Autoidentification operation finishes successfully, the identification data is provided to
Autoconnection Service. If the Plan based on Actual or Historical Configuration option was chosen,
than a CM Plan is created and can be viewed in CM Editor.

Plug and Play Play
5.4.1.3 (Optional) Updating a plan with any required changes
If Plan Based on Actual or Historical Configuration options were selected, a new plan should have
been generated. This plan can be opened in CM Editor and modified as required. Please make
sure to run validation on the plan once you have finished making changes to make sure that there
are no errors. For more information on working with plans,see Plan operations in CM Editor Help.
BTS software package can be planned under MNL.plannedSWReleaseVersion or

MRBTS:autoConfSWPackage parameter depending on the BTS product type. If it is not
configured in these parameters, than the value is taken from the INTEGRATE object. If there is no
value planned, the last activated software package is used during the restore operation.
Note: Please make sure that the same IP Version, IPv4 or IPv6, and TLS setting are
configured on the BTS as the previous integrated MRBTS. These properties will not be
updated during the restore process.
5.4.2 Triggering Configuration restore from the BTS
Hardware replacement scenario is triggered from the BTS like Plug and Play from a new hardware
unit and follows the same flow. For details Please refer to unified PnP. Configuration restore can
be triggered from the BTS UI. For details on how to trigger these operations please refer to the
documentation of your BTS product.
Note: During the flow, when BTS requests for its configuration to be provisioned, there
might be duplicate Commissioning requests visible in CM Operations Manager. One
of these operations will pass and the second will fail instantly or after timeout. This is
expected behavior due to a limitation in NetAct and BTS implementation and it does not
have any impact on the end to end process or the BTS integration. The limitation will be
removed with future releases.
Note: Please make sure that the same IP Version, IPv4 or IPv6, and TLS setting are
configured on the BTS as the previous integrated MRBTS. These properties will not be
updated during the restore process.
5.4.3 Automatic Rollback

In case of any issues during the process, the automatic rollback is triggered. For more information, see
Automatic rollback.

Configuring Radio Network Elements with DN1000023667 1-0 Centralized Plug and Play planning for
Plug and Play multiple NetAct clusters
6 Centralized Plug and Play planning for multiple

NetAct clusters
Centralized Plug and Play (Centralized PnP) helps to efficiently integrate radio network elements to
NetAct without the need to know the exact NetAct where the BTS plans are configured. In case DHCP
based PnP is used, this helps to remove the maximum 8 NetAct limit which are a result of the pro-
tocol limitations. If DHCP is not used, then the site engineer activating PnP does not need to know
which NetAct the BTS is planned on, they have to give just one IP for all installations. The network el-
ement always starts PnP procedure on single user-selected NetAct cluster (called Initial NetAct) and
this cluster is responsible for redirecting network element identification requests to all configured Tar-
get NetAct clusters in case it fails to recognize a network element. For more information, see Central-
ized PnP overview.
Note: In order to use Centralized PnP, mandatory configuration steps are required on
all involved NetAct clusters. For more information, see Configuring Centralized PnP in
Note: Centralized PnP functionality is not supported on systems with network segregation
enabled.
6.1 Centralized PnP overview

In typical Centralized PnP scenario, user should perform PnP planning only on selected Target NetAct.
NE software learns IP address of Initial NetAct (provided by DHCP or manually by installer) and sends
re-register request to it. Initial NetAct uploads identification parameters from the NE over NE3S pro-
tocol. If Initial NetAct fails to identify NE with given identification parameters through Autoconnection
Service, then it passes those parameters to all configured Target NetAct clusters. Autoconnection Ser-
vice from each Target NetAct tries to identify the eNB based on its planned data. When one of the Tar-
get NetAct clusters identifies planned eNB successfully then it finishes autoconnection and continues
autoconfiguration. All other Target NetAct clusters are simply checking and discarding such requests.
For more information on how PnP works, see PnP overview.
Additionally, the systems can be configured to use one of the Target NetAct clusters as a backup for
the Initial NetAct. If primary Initial NetAct becomes unavailable (for example due to a planned up-
grade), the user can switch the role of previously selected backup cluster to become a new Initial Net-
Act. The role change needs to be done manually on the Target NetAct as required. For more informa-
tion, see Changing role to Initial NetAct in Administering Autoconnection Service and Changing role
to Target NetAct in Administering Autoconnection Service. Please note that in case of DHCP based
PnP, the DHCP server should be configured to send IPs of both primary and backup Initial NetAct in
the DHCP offer. If DHCP is not used, the field installer has to give the IP of the backup initial NetAct
when it is switched to active role.

Configuring Radio Network Elements with DN1000023667 1-0 Centralized Plug and Play planning for
Plug and Play multiple NetAct clusters
Note: If user wants to use setup with backup Initial NetAct, it is necessary to provide
additional IP address of this backup cluster in the DHCP server response or pre-configure in
the network element.
Note: Centralized PnP functionality is not supported on systems with network segregation
enabled.
Figure 10: Centralized PnP overview

Configuring Radio Network Elements with DN1000023667 1-0 NetAct DHCP service for PnP
Plug and Play
7 NetAct DHCP service for PnP
7.1 Overview
DHCP is used in Plug and Play to automate the process of providing required autoconnection para-
meters to the BTS. This means that the field installer only has to power on and connect the BTS to the
IP network for Plug and Play to start. This feature improves the end-user experience by providing the
DHCP server capabilities within the NetAct infrastructure environment, therefore no external DHCP
service is required. The service is installed but is inactive until it is properly configured and activated
by the user. Configuration requires appropriate IP network setup for the DHCP requests to reach Net-
Act.
7.2 Configuring NetAct DHCP service for PnP

This chapter covers details on how to generate DHCP configuration for supporting Plug and Play use
cases. For more details on NetAct DHCP service and its administration procedures, see Administra-
tion of DHCP service in Administering DHCP Service.
7.2.1 Preparing input file for DHCP configuration

NetAct Autoconnection Service provides a CLI interface to generate encoded DHCP configurations
from JSON input files. All parameters from the template must be added to each subnet to have a prop-
er configuration. Multiple subnets can be defined together as required by the network configuration.
IPv4 and IPv6 files are separated as they require different configurations on the DHCP side as well.
IP version 4
{
"subnets": [
{
"subnet": "10.63.65.16",
"netmask": "255.255.255.240",
"routers": [
"10.63.65.17"
],
"subnetMask": "255.255.255.248",
"range": [
"10.63.65.19",
"10.63.65.22"
],
"broadcastAddress": "10.63.65.23",
"vendorEncapsulatedOptions": {

Plug and Play
"vendorIdentification": "Nokia",
"identificationServersFDSWMacro": [
"10.106.161.40"
],
"identificationServersMicro": [],
"oamPeerProtocol": "1",
"cmpServerIp": "10.57.167.7",
"cmpPort": "8080",
"securityGatewayIp": "10.57.251.178",
"cmpName": "DC=cmp,O=nokia,OU=ivtrans,CN=IPsecTest",
"cmpDirectory": "pkix/",
"sfnAnt": ""
}
}
]
}
Note: Parameters marked as "mandatory" must have a value assigned to them, parameters
marked as "optional" can have no value assigned. Even when a parameter is optional it
cannot be removed from the file.
The file contains a list of subnets for IP version 4. Each subnet has several parameters:
Mandatory / Option-
Parameter Description
al
subnet mandatory Network address/subnet for BTSs.
netmask mandatory Subnet mask.
routers mandatory Default route for BTS.
subnetMask mandatory Subnet mask for BTS.
range mandatory Range is defined by two IP addresses with-

in the subnet. BTS will get one of the IPs
from this range.
broadcastAddress mandatory IP address for broadcasting.
Table 10: Main subnet parameters
Mandatory / Option-
al
vendorIdentification mandatory Used to configure Nokia DHCP vendor

identification. The parameter is optional,
and a default fixed value is used for all BTS
types.

Plug and Play
Mandatory / Option-
al
identifica- mandatory Defines a NMS IP address for FDSW/

tionServersFDSWMacro SRAN BTS. BTS will use this IP for PnP
autoconnection. Multiple NMS IPs can be
mentioned here.
Parameters
identificationServersFDSWMacro
and identificationServersMicro
should contain together between one to
eight IP addresses.
identifica- mandatory Defines NMS IP address for flexi zone mi-

tionServersMicro cro BTS. BTS will use this IP for PnP auto-
connection. Multiple NMS IPs can be men-
tioned here.
Parameters
should contain together between one to
eight IP addresses.
oamPeerProtocol optional Identifies if new NE3S protocol can be used

by BTS for connection setup to PnP Ser-
vices. DHCP server shall be configured to
assign a value of 1 for NE3S. If no value
is assigned, the FSDW that is capable of
supporting NE3S will perform protocol prob-
ing to detect whether NE3S can be applied.
oamPeerProtocol parameter must have
its value set as 1 or be left empty.
cmpServerIp optional IP address of a Certification Authority (CA)

server. BTS uses this server address to get
certificates.
cmpPort optional Port number of a CA server.
securityGatewayIp optional IP address of a VPN gateway in case the

BTS needs to setup IpSec Tunnel.
cmpName optional Subject name for a CA server in case of a

secure M-plane connection setup.

Plug and Play
Mandatory / Option-
al
cmpDirectory optional The CMP directory (URL) on CA server. It

is needed in case of secure M-plane con-
nection setup. If not configured BTS will
use default pkix. CMP directory length can
be up to 128 characters as long as CMP to-
tal limit (subject name and directory) of 176
characters is not exceeded.
sfnAnt optional Optional in DHCP server Plug and Play. It

is needed when Flexi Zone Micro (FZM) de-
vice operates as an antenna (use 1 if oper-
ates as an antenna, otherwise leave emp-
ty). sfnAnt parameter must have its value
set as 1 or be left empty.
Table 11: Vendor encapsulated options
IP version 6
{
"subnets": [
{
"subnet": "2A00:8A00:8000:136:10:57:251:100/124",
"range": [
"2A00:8A00:8000:136:10:57:251:102",
"2A00:8A00:8000:136:10:57:251:106"
],
"vendorEncapsulatedOptions": {
"vendorIdentification": "Nokia",
"identificationServersFDSWMacro": [
"0:0:0:0:0:FFFF:0A6A:A128"
],
"identificationServersMicro": [],
"oamPeerProtocol": "1",
"cmpServerIp": "2A00:8A00:8000:136:10:57:167:7",
"cmpPort": "8080",
"securityGatewayIp": "2A00:8A00:8000:136:10:57:251:BA",
"cmpName": "DC=cmp, O=nokia, OU=ivtrans, CN=IPsecTestv6",
"cmpDirectory": "pkix/",
"sfnAnt": ""
}
}
]
}

Plug and Play
The file contains a list of subnets for IP version 6. Each subnet has several parameters:
Mandatory / Option-
al
subnet mandatory Subnet for BTSs IP allocation.
range mandatory Range is defined by two IP addresses with-

in the subnet. BTS will get one of the IPs
from this range.
Table 12: Main subnet parameters
Mandatory / Option-
al
vendorIdentification mandatory Used to configure Nokia DHCP vendor

identification. The parameter is optional,
and a default fixed value is used for all BTS
types.
identifica- mandatory Defines an NMS IP address for FDSW/

tionServersFDSWMacro SRAN BTS. BTS will use this IP for PnP
autoconnection. Multiple NMS IPs can be
mentioned here.
At least one of the parameters

should have a value and together they can
have a maximum of 8 IP addresses.
identifica- mandatory Defines NMS IP address FZM BTS. BTS

tionServersMicro will use this IP for PnP autoconnection.
Multiple NMS IPs can be mentioned here.
At least one of the parameters

should have a value and together they can
have a maximum of 8 IP addresses.
oamPeerProtocol optional Identifies if a new NE3S protocol can

be used by BTS for connection setup to
PnP Services. DHCP server should be
configured to assign a value of 1 for NE3S.
If no value is assigned, the FSDW that can
support NE3S will perform protocol probing

Plug and Play
Mandatory / Option-
al
to detect whether NE3S can be applied.

oamPeerProtocol parameter must have
its value set as 1 or be left empty.
cmpServerIp optional IP address of a CA server. BTS uses this

server address to get certificates.
cmpPort optional Port number of a CA server.
securityGatewayIp optional IP address of a VPN gateway in case the

BTS needs to setup IpSec Tunnel.
cmpName optional Subject name for a CA server in case of a

secure M-plane connection setup.
cmpDirectory optional The CMP directory (URL) on CA server. It

is needed in case of secure M-plane con-
nection setup. If not configured, the BTS
will use default pkix. CMP directory length
can be up to 128 characters as long as
CMP total limit (subject name and directory)
of 176 characters is not exceeded.
sfnAnt optional Optional in DHCP server Plug and Play. It

is needed when FZM device operates as an
antenna (use 1 if the device operates as an
antenna, otherwise leave empty). sfnAnt
parameter must have its value set as 1 or
be left empty.
Table 13: Vendor encapsulated options
7.2.2 Generating PnP DHCP Configuration

Once the JSON configuration files are ready, the following script can be executed to generate the ef-
fective DHCP configuration. These files can be created anywhere on the file system and the output file
is generated in the location based on Autoconnection Service properties. If the output is generated on
a non-default location, it should be coped to the default path manually by a root user before proceed-
ing to next steps.
Example:
/opt/oss/Nokia-pnpautoconnection/bin/pnpclimx.sh -op
updatePnpDhcpConfiguration -ipVersion IPV4 -configurationFileName /tmp/
dhcp_configuration.json

Plug and Play
For more information, see Command line options in Administering Autoconnection Service.
Note: You must restart the DHCP service after manually configuring PnP_IPv4.conf
and PnP_IPv6.conf files. For more information, see Restarting the DHCP service in
Administering DHCP Service.


Plug and Play For Radio Network Elements

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Plug and Play For Radio Network Elements

Uploaded by

Copyright:

Available Formats

NetAct™ 22

Configuring Radio Network Elements with

© 2021 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.

No part of this document may be modified.

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

© 2021 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.

2 Upgrading factory software with Compatibility Service............................................................................12

4 Unified PnP workflows..................................................................................................................................14

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 3

4.2.1 Prerequisites for Direct Integration Planning..................................................................................34

5 Restore BTS configuration with Plug and Play......................................................................................... 55

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 4

5.4.2 Triggering Configuration restore from the BTS.............................................................................. 61

6 Centralized Plug and Play planning for multiple NetAct clusters............................................................ 62

7 NetAct DHCP service for PnP......................................................................................................................64

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 5

1 Introduction to Plug and Play

1.1 PnP overview

Figure 1: Overview of Plug and Play

For PnP scenarios and use-case examples, see PnP scenarios.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 6

1.2 PnP scenarios

Network element PnP procedure

Flexi Multiradio BTS LTE (FLF, TLF) Direct Integration Planning

Flexi Multiradio BTS LTE (SRAN) Direct Integration Planning

AirScale 5G Classical BTS and DU Direct Integration Planning

AirScale Indoor Radio Direct Integration Planning

Classical 5G Direct Integration Planning

Single RAN BTS via BTSMED Mediated Integration Planning

Single RAN BTS (SRAN) Direct Integration Planning

Table 1: PnP scenarios for radio network elements

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 7

Examples of PnP use cases

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 8

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 9

Update of the factory software without the NE3S support

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 10

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 11

2 Upgrading factory software with Compatibility

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 12

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 13

4 Unified PnP workflows

4.1 Mediated Integration Planning

Mediated Integration Planning can be performed in three variants:

• You launch the following operations one-by-one:

– Create BTS configuration plan

You launch the planning process with CLI.

4.1.1 Prerequisites for Mediated Integration Planning

Preconditions for Mediated Integration Planning:

• All required applications are present.

For more information, see Applications for Mediated Integration Planning.

• All necessary licenses are installed.

For more information, see Licenses for Mediated Integration Planning.

• Autoconnection Service is configured to orchestrate the Plug and Play process.

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 14

For more information, seeConfiguring Autoconnection Service in Administering Autoconnection

For more information, see Preparing the configuration plan.

4.1.1.1 Applications for Mediated Integration Planning

• Workflow Engine (available in NetAct CM Operations Manager) or CLI (racclimx.sh)

4.1.1.2 Licenses for Mediated Integration Planning

NetAct™ 22 © 2021 Nokia. Nokia Confidential Information 15