No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.

Deploying, Commissioning, and Integrating
Cloud RAN BTS

DN276085968
Issue 01 DRAFT
Revised on 2024-02-14

AirScale Cloud RAN BTS System

Rel. 24R2-CR Pre-release

Operating Documentation

© 2024 Nokia. Nokia Condential Information. Use subject to agreed restrictions on disclosure and use.
Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
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 condential 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 nd 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 modied.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

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.

© 2024 Nokia.

2 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table of Contents

Summary of changes ................................................................................................................. 12

1 Overview and requirements for Cloud RAN BTS startup ..................................................... 13

1.1 Cloud RAN BTS LCM overview ....................................................................................... 18
1.2 Central container registry in Cloud RAN BTS solution .............................................. 22
1.3 Cloud RAN BTS solution interworking .......................................................................... 24
1.4 Deploying Cloud RAN BTS .............................................................................................. 29

2 Cloud RAN BTS software delivery ............................................................................................ 38

2.1 Downloading software packages from SWSt .............................................................. 40

3 Preparing RAN configuration .................................................................................................... 42

3.1 vCU and vDU parameters .............................................................................................. 42
3.2 Site configuration file ..................................................................................................... 47
3.2.1 Configuring vCU parameters in SCF ................................................................. 48
3.2.2 Configuring vDU parameters in SCF ................................................................. 50
3.3 Filling in the values override files for the vCU ........................................................... 51
3.4 Filling in the values override files for the vDU ........................................................... 72
3.5 Filling in the values override files for the Nokia proprietary Kubernetes operators
for Cloud RAN BTS .......................................................................................................... 95

4 Deploying cloud infrastructure .............................................................................................. 101

5 Deploying and commissioning FHGW ................................................................................... 104

6 Preparing CNF deployment in MantaRay NM ....................................................................... 111

6.1 Configuring MantaRay NM for Cloud RAN BTS life cycle management operations
.......................................................................................................................................... 111
6.1.1 Configuring and integrating CCR with MantaRay NM .................................. 113
6.1.2 Integrating NEAT with MantaRay NM ............................................................. 117
6.2 Integrating a cloud instance with MantaRay NM ..................................................... 119
6.2.1 Integrating a cloud instance with MantaRay NM using MantaRay NM GUI 120
6.2.2 Integrating a cloud instance with MantaRay NM using MantaRay NM CLI 123
6.2.3 Integrating a cloud instance with MantaRay NM using MantaRay NM REST API
.................................................................................................................................. 127

7 Creating a CNF deployment plan .......................................................................................... 130

7.1 CNF object parameters in LCM operation plans ..................................................... 132
7.2 Creating a deployment plan using a text editor ..................................................... 134
7.3 Creating a deployment plan using MantaRay NM GUI ............................................ 137
7.4 Updating Helm chart configuration values from values override files ................ 143
7.4.1 Updating Helm chart configuration values using MantaRay NM GUI ........ 144
7.4.2 Updating Helm chart configuration values using MantaRay NM CLI ......... 148
7.5 Creating secrets for CNF objects ............................................................................... 150
7.5.1 Creating an image pull secret for the vDU deployment ............................. 151
7.5.2 Adding secrets to MantaRay NM SSD using MantaRay NM GUI ................. 153
7.5.3 Adding secrets to MantaRay NM SSD using MantaRay NM REST API ........ 156

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 3

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
8 Onboarding software packages to MantaRay NM .............................................................. 159
8.1 Installing MantaRay NM fast pass service package for the Cloud RAN BTS release
.......................................................................................................................................... 159
8.2 Uploading certificates to MantaRay NM Software Integrity Protection Trust Store
.......................................................................................................................................... 160
8.3 Onboarding software packages to MantaRay NM manually .................................. 161
8.4 Onboarding the PDL validation plugin to MantaRay NM ........................................ 169
8.5 Onboarding software images to the container registry ........................................ 170
8.5.1 Onboarding software images to the container registry using MantaRay NM
GUI .......................................................................................................................... 171
8.5.2 Onboarding software images to the container registry using MantaRay NM
CLI ........................................................................................................................... 175
8.5.3 Onboarding software images to the CCR using MantaRay NM CLI ........... 178

9 Deploying a CNF in MantaRay NM without autoconfiguration ......................................... 181

9.1 Deploying a CNF without autoconfiguration using MantaRay NM GUI ................ 183
9.2 Deploying a CNF without autoconfiguration using MantaRay NM CLI ................. 187
9.3 Deploying a CNF without autoconfiguration using MantaRay NM REST API ....... 190

10 Deploying a CNF in MantaRay NM with autoconfiguration (PnP) ................................... 193

10.1 Deploying a CNF with autoconfiguration using MantaRay NM GUI (one-button
planning) ........................................................................................................................ 195
10.2 Deploying a CNF with autoconfiguration using MantaRay NM CLI (zero-touch
planning) ........................................................................................................................ 202

11 Commissioning Cloud RAN BTS ........................................................................................... 206

11.1 Software version verification ................................................................................... 208
11.1.1 Verifying a software version with CU WebEM ............................................. 209
11.1.2 Verifying a software version with vDU WebEM ........................................... 210
11.2 Commissioning with CU WebEM ............................................................................... 211
11.2.1 Loading an SCF to CU WebEM ....................................................................... 212
11.2.2 Creating a configuration plan in CU WebEM ............................................... 215
11.2.3 Validating an SCF in CU WebEM .................................................................... 221
11.2.4 Activating an SCF in CU WebEM .................................................................... 224
11.2.5 Saving an SCF in CU WebEM .......................................................................... 228
11.3 Commissioning with vDU WebEM ............................................................................ 229
11.3.1 Loading an SCF to vDU WebEM .................................................................... 230
11.3.2 Creating a configuration plan in vDU WebEM ............................................. 233
11.3.3 Validating an SCF in vDU WebEM .................................................................. 238
11.3.4 Activating an SCF in vDU WebEM .................................................................. 240
11.3.5 Saving an SCF in vDU WebEM ........................................................................ 244
11.4 Verifying vCU-vDU connection ................................................................................. 245

12 Terminating a CNF in MantaRay NM ................................................................................... 247

12.1 Creating a CNF termination plan ............................................................................. 248
12.1.1 Creating a termination plan using a text editor ........................................ 249
12.1.2 Creating a termination plan using MantaRay NM GUI ............................... 250
12.2 Terminating a CNF using MantaRay NM GUI .......................................................... 254
12.3 Terminating a CNF using MantaRay NM CLI ........................................................... 258

4 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
12.4 Terminating a CNF using MantaRay NM REST API ................................................. 260

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 5

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
List of Figures
Figure 1 Cloud RAN BTS components ..................................................................................... 14
Figure 2 Cloud RAN BTS deployment models ........................................................................ 16
Figure 3 Overview of the systems, tools, and use cases involved in the Cloud RAN BTS
LCM ................................................................................................................................... 19
Figure 4 CNF artifact distribution workflow ........................................................................... 23
Figure 5 OCP artifact distribution workflow .......................................................................... 24
Figure 6 Cloud RAN BTS communication diagram ................................................................ 25
Figure 7 Updating Helm chart configuration values from values override files .............. 52
Figure 8 Structure of the values-override.aic-vcu.yaml file ................................................ 55
Figure 9 Structure of the global.externalNetwork section in values-override.aic-vcu.yaml
........................................................................................................................................... 60
Figure 10 Updating Helm chart configuration values from values override files ............ 73
Figure 11 Structure of the values_override.aic-vdu.yaml file ............................................. 77
Figure 12 Structure of the global.externalNetwork section in values-override.aic-vdu.yaml
........................................................................................................................................... 85
Figure 13 Updating Helm chart configuration values from values override files ............ 96
Figure 14 Overview of the OCP deployment ....................................................................... 101
Figure 15 Overview of the FHGW deployment with the MantaRay NM Plug and Play (PnP)
method .......................................................................................................................... 104
Figure 16 Cloud RAN BTS elements interacting with FHGW .............................................. 106
Figure 17 CCR configuration and integration process ...................................................... 114
Figure 18 NEAT configuration and integration process .................................................... 118
Figure 19 Connection between the integrated network elements and MantaRay NM
......................................................................................................................................... 118
Figure 20 MantaRay NM start page view .............................................................................. 121
Figure 21 CM Operations Manager view .............................................................................. 121
Figure 22 Workflow Engine›Operation list›Cloud Operations view .................................. 122
Figure 23 CNF package ............................................................................................................ 131
Figure 24 MantaRay NM start page ....................................................................................... 138
Figure 25 Creating a new plan in CM Editor›Plan ................................................................ 139
Figure 26 Plan Header view ................................................................................................... 140
Figure 27 Creating a new MO for a plan ............................................................................... 141
Figure 28 Defining the MO class as CNF (com.nokia.cnf.lcm) ........................................... 142
Figure 29 Updating Helm chart configuration values from values override files .......... 143
Figure 30 MantaRay NM start page view .............................................................................. 145
Figure 31 Opening the Workflow Engine for a selected plan ............................................ 146
Figure 32 CNF Plan Prepare view ........................................................................................... 147
Figure 33 MantaRay NM start page view .............................................................................. 154
Figure 34 Opening the Workflow Engine for a selected plan ............................................ 155
Figure 35 CNF Secret Import view ........................................................................................ 156

6 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 36 MantaRay NM start page view .............................................................................. 162
Figure 37 Software Manager›Software Archive view .......................................................... 163
Figure 38 Selecting theApplication menu option ............................................................... 163
Figure 39 Choosing Software manager (Classical) ............................................................. 164
Figure 40 Software Manager›Add software package view ............................................... 164
Figure 41 Selecting the MO type in the SW Import Manager view ................................... 165
Figure 42 SW Package Details view ....................................................................................... 167
Figure 43 MantaRay NM start page view .............................................................................. 172
Figure 44 Opening the Workflow Engine for a selected plan ............................................ 173
Figure 45 CNF Distribute Software view .............................................................................. 174
Figure 46 Overview of the CNF deployment without autoconfiguration ....................... 181
Figure 47 MantaRay NM start page view .............................................................................. 184
Figure 48 Opening the Workflow Engine for a selected plan ............................................ 185
Figure 49 CNF Deployment view ........................................................................................... 186
Figure 50 Overview of the CNF deployment with autoconfiguration ............................. 193
Figure 51 MantaRay NM start page view .............................................................................. 197
Figure 52 Opening the Workflow Engine for a selected plan ............................................ 198
Figure 53 Unified PnP - One-button planning view ............................................................ 199
Figure 54 Overview of the CNF commissioning .................................................................. 206
Figure 55 Software information in CU WebEM .................................................................... 209
Figure 56 Checking the software version in CU WebEM .................................................... 210
Figure 57 Software information in vDU WebEM .................................................................. 210
Figure 58 Checking the software version in vDU WebEM .................................................. 211
Figure 59 Loading an SCF file ................................................................................................ 213
Figure 60 Creating an example plan by uploading a test SCF file ................................... 213
Figure 61 Loading an SCF progress bar .............................................................................. 214
Figure 62 Creating a new plan in CU WebEM ....................................................................... 216
Figure 63 Duplicating a configuration plan .......................................................................... 216
Figure 64 Selecting planned configurations ........................................................................ 217
Figure 65 Adding the base object in CU WebEM ................................................................. 217
Figure 66 Adding MRBTS ID .................................................................................................... 218
Figure 67 Adding MRBTS parameters in CU WebEM ........................................................... 218
Figure 68 Adding a new object .............................................................................................. 219
Figure 69 Selecting a class name .......................................................................................... 219
Figure 70 Adding the object ID .............................................................................................. 220
Figure 71 Adding all mandatory parameter values ............................................................ 221
Figure 72 Selecting a plan for validation .............................................................................. 223
Figure 73 Displaying validation errors .................................................................................. 223
Figure 74 Activating configuration plan ............................................................................... 225
Figure 75 Downloading plan without activation ................................................................. 226
Figure 76 Activating plan progress bar ................................................................................ 226
Figure 77 vCU reset notification ........................................................................................... 227

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 7

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 78 Successful plan activation .................................................................................... 227
Figure 79 Saving the SCF from the Dashboard widget ..................................................... 228
Figure 80 Saving an SCF in CU WebEM ................................................................................. 229
Figure 81 Loading an SCF file ................................................................................................ 231
Figure 82 Creating an example plan by uploading a test SCF file ................................... 232
Figure 83 Loading an SCF progress bar .............................................................................. 232
Figure 84 Creating a new plan in vDU WebEM ..................................................................... 234
Figure 85 Duplicating a configuration plan .......................................................................... 235
Figure 86 Selecting planned configurations ........................................................................ 235
Figure 87 Adding a new object .............................................................................................. 236
Figure 88 Selecting a plan for validation .............................................................................. 239
Figure 89 Displaying validation errors .................................................................................. 239
Figure 90 Activating configuration plan ............................................................................... 241
Figure 91 Downloading plan without activation ................................................................. 242
Figure 92 Activating plan progress bar ................................................................................ 242
Figure 93 vDU reset notification ........................................................................................... 243
Figure 94 Successful plan activation .................................................................................... 243
Figure 95 Saving the SCF from the Dashboard widget ..................................................... 244
Figure 96 Saving an SCF in vDU WebEM ............................................................................... 245
Figure 97 Verifying vCU and vDU connection ...................................................................... 246
Figure 98 Overview of the CNF termination ........................................................................ 247
Figure 99 MantaRay NM start page ....................................................................................... 251
Figure 100 Creating a new plan in CM Editor›Plan .............................................................. 252
Figure 101 Plan Header view ................................................................................................. 253
Figure 102 MantaRay NM start page view ........................................................................... 255
Figure 103 Opening the Workflow Engine for a selected plan ......................................... 256
Figure 104 CNF Terminate view ............................................................................................ 257

8 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
List of Tables
Table 1 Cloud RAN BTS deployment models ......................................................................... 15
Table 2 Cloud RAN BTS LCM communication matrix ............................................................ 27
Table 3 Software packages used in Cloud RAN BTS life cycle management operations
........................................................................................................................................... 39
Table 4 vCU and vDUs parameters requiring identical settings ......................................... 43
Table 5 Common vCU and vDU parameters .......................................................................... 44
Table 6 Common vCU and vDU parameters used for pairing ............................................. 45
Table 7 vCU parameters required for a working connection to vDU ................................. 46
Table 8 vDU parameters required for a working connection to vCU ................................. 46
Table 9 f1Cplane parameters for configuration ................................................................... 49
Table 10 f1Uplane parameters for configuration ................................................................. 49
Table 11 f1Cplane parameters for configuration ................................................................. 50
Table 12 f1Uplane parameters for configuration ................................................................. 51
Table 13 remotef1CplaneIpAddr parameter configuration ................................................ 51
Table 14 Parameters in values-override.aic-vcu-cluster-preparation.yaml ..................... 53
Table 15 Network parameters under aic-vcu-network.devicePoolList in values-
override.aic-vcu-prerequisite.yaml ............................................................................ 54
Table 16 Storage parameters under global in values-override.aic-vcu-prerequisite.yaml
........................................................................................................................................... 55
Table 17 General parameters under global in values-override.aic-vcu.yaml ................... 57
Table 18 LRIP round-check configuration parameters in values-override.aic-vcu.yaml
........................................................................................................................................... 59
Table 19 global.devicePoolList parameters in values-override.aic-vcu.yaml .................. 60
Table 20 global.externalNetwork.<network name> parameters in values-override.aic-
vcu.yaml .......................................................................................................................... 62
Table 21 global.internalE1Network.internalE1 parameters in values-override.aic-vcu.yaml
........................................................................................................................................... 64
Table 22 Additional network parameters for network slicing under
global.externalNetwork.<network name> in values-override.aic-vcu.yaml ........ 67
Table 23 Additional network parameters for interfaces with TWAMP configured under
global.externalNetwork.twamp_f1c in values-override.aic-vcu.yaml ................... 69
Table 24 Parameters for vCU autoconnection under global in values-override.aic-
vcu.yaml ........................................................................................................................... 70
Table 25 Parameters for automated certificate management under certman-auto-
cmp.configuration.cmp in values-override.aic-vcu.yaml ......................................... 71
Table 26 Initial certificate enrolment secrets in cmp_secret.yaml .................................... 72
Table 27 Initial certificate enrolment secrets in taTrustChain_secret.yaml ..................... 72
Table 28 Parameters in values-override.aic-vdu-cluster-preparation.yaml .................... 74
Table 29 General parameters under global in values-override.aic-vdu-prerequisite.yaml
........................................................................................................................................... 75

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 9

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 30 Network parameters under aic-intnet in values-override.aic-vdu-
prerequisites.yaml ......................................................................................................... 75
Table 31 Storage parameters in values-override.aic-vdu-prerequisite.yaml .................. 76
Table 32 General parameters under global in values-override.aic-vdu.yaml ................... 78
Table 33 l2nrt pod capacity parameters in values-override.aic-vdu.yaml ....................... 80
Table 34 l2rt pod capacity parameters in values-override.aic-vdu.yaml .......................... 81
Table 35 healing-controller parameters in values-override.aic-vdu.yaml ........................ 81
Table 36 nodeSelector parameters in values-override.aic-vdu.yaml ................................ 82
Table 37 global.devicePoolList parameters in values-override.aic-vdu.yaml .................. 83
Table 38 Fhm network parameters in values-override.aic-vdu.yaml ................................ 84
Table 39 global.networkInfo.<network name> parameters in values-override.aic-vdu.yaml
........................................................................................................................................... 85
Table 40 global.externalNetwork.<network name> parameters in values-override.aic-
vdu.yaml .......................................................................................................................... 86
Table 41 global.externalNetwork.ahm-<x> parameters in values-override.aic-vdu.yaml
........................................................................................................................................... 87
Table 42 Additional network parameters for network slicing for the F1-U interface under
global.externalNetwork.f1u_slice<slice number>in values-override.aic-vdu.yaml
88
Table 43 Additional network parameters for interfaces with TWAMP configured under
global.externalNetwork.twamp_<interface> in values-override.aic-vdu.yaml ... 90
Table 44 Parameters for vDU autoconnection under global in values-override.aic-
vdu.yaml .......................................................................................................................... 91
Table 45 Parameters for automated certificate management under certman-auto-
cmp.configuration.cmp in values-override.aic-vdu.yaml ........................................ 92
Table 46 Initial certificate enrolment secrets in cmp_secret.yaml .................................... 93
Table 47 Initial certificate enrolment secrets in taTrustChain_secret .............................. 93
Table 48 Parameters for the vDU internal fronthaul network DHCP server under aic-
oamfh.dhcp.service in values-override.aic-vdu.yaml ............................................... 94
Table 49 Parameters in ran-nic-sw-controller.yaml ............................................................. 97
Table 50 Parameters in nokia-sync-operator.yaml .............................................................. 99
Table 51 MantaRay NM permissions specific for the Cloud RAN BTS LCM operations
......................................................................................................................................... 112
Table 52 MantaRay NM permissions specific for the Cloud RAN BTS LCM operations
......................................................................................................................................... 113
Table 53 CNF parameters in Cloud RAN BTS LCM operation plans ................................. 133
Table 54 Starting parameters for the CNF Distribute Software operation in MantaRay NM
CLI .................................................................................................................................. 177
Table 55 Starting parameters for the CNF Distribute Software operation in MantaRay NM
CLI .................................................................................................................................. 179
Table 56 Starting parameters for the CNF Deployment operation in MantaRay NM CLI
......................................................................................................................................... 189

10 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 57 Starting parameters for the Unified_PnP_COAM_Site_Preparation operation in
MantaRay NM CLI ......................................................................................................... 204
Table 58 Starting parameters for the CNF Terminate operation in MantaRay NM CLI
......................................................................................................................................... 259

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 11

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Summary of changes

A list of changes between document issues. You can navigate through the respective changed
topics.

This is the first issue of the document.

12 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
1. Overview and requirements for Cloud RAN BTS startup

AirScale Cloud RAN BTS (Cloud RAN BTS) deployment and commissioning processes involve
installation and configuration of hardware and software. The cloud-native network functions
(CNFs) of the gNB are deployed on the Red Hat OpenShift Container Platform (OCP), which must
be installed and configured on host hardware servers.

Cloud RAN BTS logical and physical entities

In the Cloud RAN BTS architecture, part of the gNB functionality is moved from the physical
hardware on the gNB side to the cloud in a radio cloud data center. It means that the cloud gNB is
split into two main logical and functional entities:

Virtualized gNB distributed It is a distributed data center unit that hosts virtualized, real-time (RT)
unit (vDU) functions of the radio access cloud (RAC).

Virtualized gNB central unit It is a central data center unit that hosts virtualized, non-real-time
(vCU) (NRT) functions of the gNB and controls the operation of one or
more vDUs.

The vDU and vCU are installed on the cloud infrastructure, deployed on hardware servers. The
servers connect to the management network through a cell site router (CSR).

In addition to the hardware servers, the physical entities of the Cloud RAN BTS deployment
include:

Radio units (RUs) Entities that host the RF functionality of the gNB. The RU is a physical
radio supporting either the Common Public Radio Interface (CPRI) or
the Enhanced Common Public Radio Interface (eCPRI) fronthaul
connectivity. The RU may also host layer 1 (L1) processing in the
solution based on an L1 functional split.

Nokia AirFrame Fronthaul Gateway, which can work either as a conversion device or an Ethernet
Gateway (FHGW) switch. It is responsible for converting the CPRI traffic in the time
domain to the eCPRI traffic in the frequency domain. It provides
switching of the eCPRI-native RU to the vDU.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 13

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Nokia Cloud RAN SmartNIC System on Chip (SoC)-based Peripheral Component Interconnect
(RAN NIC) Express (PCIe) network interface card (NIC) that terminates the vDU
fronthaul interfaces coming from the RUs and processes the radio L1
function of the vDU.

RAN NICs are installed and controlled using the following Nokia proprietary Kubernetes operators
for Cloud RAN BTS, deployed on cloud infrastructure together with the vDU CNF:

RAN NIC Software Nokia proprietary Kubernetes operator for Cloud RAN BTS which
Controller controls the life cycle management (LCM) operations of RAN NICs.

Nokia Advanced Nokia proprietary Kubernetes operator for Cloud RAN BTS , which
Synchronization provides the Precision Time Protocol (PTP) time reference for the
Kubernetes Operator vDU.
(Nokia Synchronization
Operator)

Figure 1: Cloud RAN BTS components

Cloud RAN BTS supported deployment models

Cloud RAN BTS supports two deployment architecture models designed to serve different use
cases:
Distributed RAN (D-RAN)

14 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Centralized RAN (C-RAN)

Notice:
This section presents the target Cloud RAN BTS deployment models. C-RAN configurations
will be supported in future releases.

D-RAN and C-RAN deployment models provide several options for the vDU and vCU locations.

Table 1: Cloud RAN BTS deployment models

Deployment model vDU locations vCU locations

C-RAN (large deployment) Cell site Edge data center

D-RAN (small deployment) Cell site (co-located with a Cell site (co-located with a
vCU) vDU)

C-RAN (large deployment) Far-edge data center Edge data center

C-RAN (small deployment) Far-edge data center (co- Far-edge data center (co-
located with a vCU) located with a vDU)

In both deployment models, RUs connect with vDUs through the fronthaul interface using CPRI or
eCPRI protocols. The eCPRI is a low-latency Ethernet-based fronthaul interface towards legacy and
new RUs in the Cloud RAN BTS network. Legacy RUs use the CPRI interface, which requires FHGW
between an RU and a vDU. FHGW converts the CPRI to the eCPRI.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 15

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 2: Cloud RAN BTS deployment models

The vCU and the vDU are deployed on the cloud infrastructure using Kubernetes containers,
organized into pods. Containers are a type of software that can virtually package and isolate
applications. This way, applications can share access to an operating system without the need for
a virtual machine (VM). Pod deployment is automated using Helm, which is a system for simplifying
container management. The Helm charts are provided as part of the deployment package and
contain the details of resource creation and pod deployment with default values of the CNF
deployment parameters. You can override the default configuration values with parameters
specific to your infrastructure and the chosen deployment type by modifying the
values.override YAML files included in the deployment package.

The hardware servers which host the CNFs use the Container-as-a-Service (CaaS) framework
provided by OCP. You need to install and configure OCP on the hardware servers before the CNF
deployment. For detailed information on the supported hardware configurations, see Reference
Documentation/AirScale Cloud RAN BTS Supported Configurations.

Automation of the CNF deployment is possible thanks to the use of Nokia MantaRay NM and
other management tools, such as Nokia AirFrame Data Center Manager (NADCM) for hardware
management and Nokia Edge Automation Tool (NEAT) for OCP deployment and cloud
infrastructure management. Additional tools, such as Data Collection and Analytics Platform
(DCAP) and Unified Troubleshooting Framework (UTF), enable monitoring and troubleshooting
Cloud RAN BTS.

16 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For more information, see Cloud RAN BTS LCM overview.

Hardware acceleration in Cloud RAN BTS

To increase the performance of Cloud RAN BTS, the radio L1 function of the vDU is processed by
RAN NICs. The number of RAN NICs equals the number of l2rt pods in the deployment.

RAN NICs software doesn't belong to the vDU CNF. To deploy it with the vDU CNF, first install the
RAN NIC Software Controller on the target Kubernetes cluster. The RAN NIC drivers are installed
on the target cluster in the post-configuration phase of the OCP deployment. For more
information, see Deploying cloud infrastructure.

Cloud RAN BTS Enterprise MPW solution

Cloud RAN BTS is targeted at two prominent use cases:
Communication service providers (CSPs), which are large networks with multiple levels of data
centers.
Enterprise modular private wireless (MPW), which are small networks with coverage limited to a
few cells and no existing own data centers.

Cloud RAN BTS Enterprise MPW solution consists of:

Management tools and systems: MantaRay NM, NADCM, and NEAT
CNFs: vCU, vDU, Nokia Compact Mobility Unit (CMU)
FHGW

For detailed information on the supported hardware configurations, see Reference

Documentation/AirScale Cloud RAN BTS Supported Configurations.

Cloud RAN BTS deployment process overview

The end-to-end Cloud RAN BTS deployment procedure involves:

Installation of the The management software necessary for the deployment of Cloud
management applications RAN BTS includes:
• NADCM for hardware management
• NEAT for installation and management of the cloud infrastructure
and pre-configuration of the FHGW and RAN NIC software
• MantaRay NM as a network management system (NMS)

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 17

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Preparation and planning The preparation and planning steps include:
• Dimensioning the system
• IP Planning, including network planning
• Downloading and preparing needed software packages
• Preparing a site configuration file (SCF) and the values override files
• Preparing Cloud RAN BTS licenses
• Integration of the central container registry (CCR) with NEAT and
MantaRay NM

Installation of hardware The selected deployment model defines the hardware configurations.
components at their
locations

Deployment of the cloud Deployment of the cloud infrastrucure is automated with NEAT.
infrastructure

Deployment of the FHGW Deployment of the FHGW and RAN NIC software is automated with
and RAN NIC software NEAT and MantaRay NM.

Deployment of the vCU, Deployment of the CNFs and the Kubernetes operators is automated
vDU, and Nokia proprietary with MantaRay NM.
Kubernetes operators for
Cloud RAN BTS

Commissioning of the vCU Commissioning process involves software and parameter

and vDU configurations in BTS element managers: CU WebEM and vDU WebEM.

For detailed end-to-end Cloud RAN BTS deployment procedure, see Deploying Cloud RAN BTS.

For an overview of the tools used in the Cloud RAN BTS deployment procedure, see Cloud RAN
BTS LCM overview.

1.1 Cloud RAN BTS LCM overview

Systems and tools involved in the AirScale Cloud RAN BTS (Cloud RAN BTS) life cycle management
(LCM)

Cloud RAN BTS LCM includes the following areas:

18 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Installation, upgrade, and termination of the management tools
Software delivery
Hardware preparation
Cloud infrastructure deployment, upgrade, backup, and termination
Nokia AirFrame Fronthaul Gateway (FHGW) LCM
CNF deployment, upgrade, rollback, and termination

For detailed information on the Cloud RAN BTS LCM, see the Operating Documentation/AirScale
Cloud RAN BTS Features/Cloud RAN BTS Site Solution Features/Cloud RAN BTS Life Cycle
Management.

The Cloud RAN BTS LCM workflow with the tools and systems responsible for the process
presents in the following way:

Figure 3: Overview of the systems, tools, and use cases involved in the Cloud RAN BTS LCM

CNF cloud-native network function

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 19

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
DCAP Data Collection and Analytics Platform

NADCM Nokia AirFrame Data Center Manager

NEAT Nokia Edge Automation Tool

OCP Red Hat OpenShift Container Platform

UTF Unified Troubleshooting Framework

OCP overview
Nokia Red Hat OCP is the Container-as-a-Service (CaaS) infrastructure that hosts the Cloud RAN
BTS CNFs. It's based on Kubernetes. Deployment of the Cloud RAN BTS CNFs is orchestrated
using Helm, with instructions for the deployment specified in Helm charts. In the Cloud RAN BTS
deployment process, OCP is deployed using NEAT.

MantaRay NM overview
MantaRay NM serves as the LCM orchestrator of the CNFs. It executes the Helm charts to deploy
the CNFs and coordinates the involved resources. Equally important is the configuration manager
applying the configuration plans to the CNFs. The configuration plans are specified in site
configuration files (SCFs).

Central container registry (CCR) runs in the management cluster alongside MantaRay NM and
stores the container images of the CNFs, cloud infrastructure, and Nokia proprietary Kubernetes
operators for Cloud RAN BTS.
For more information, see MantaRay NM Operating Documentation.

NEAT overview
NEAT is the infrastructure manager, providing edge cloud automation of:
edge site hardware, cloud infrastructure, and cloud infrastructure manager deployment.
configuration modification.
cloud infrastructure upgrade.
Kubernetes cluster creation and configuration.

20 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Additionally, it's used for cloud infrastructure monitoring, inventory management, and access
management.

In the Cloud RAN BTS deployment process, NEAT is used for:

deploying and commissioning the cloud infrastructure for the CNFs.
providing information about the cloud infrastructure and the Kubernetes configuration to the
NMS when deploying the CNFs.
automatically deploying and integrating FHGW.

For more information, see Operating Documentation/Nokia Edge Automation Tool.

NADCM overview
NADCM is a management system for optimizing and automating data center operations and
resource usage. It provides the following functionalities:
A single view over distributed data centers
Operations across distributed data centers
Hardware and embedded software inventory
Alarm monitoring, performance management, and event management for the distributed data
centers
Device configuration and firmware management

NADCM and NEAT provide a single real-time view of cloud infrastructure and data center
resources. They allow you to manage faults, performance, and configuration.

In the Cloud RAN BTS deployment process, NADCM and NEAT are used to plan and commission
hardware and networking resources.

For more information, see Operating Documentation/Nokia AirFrame Data Center Manager.

DCAP overview
DCAP Suite is a Nokia solution for data collection, analysis, and troubleshooting. It includes several
different products and serves all radio technologies. DCAP Basic is a part of the solution, which is
integrated with MantaRay NM. In Cloud RAN BTS, DCAP can be used optionally for troubleshooting
data at the call level.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 21

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
UTF overview
UTF is a troubleshooting tool for network topology, credentials, and alarm information. It provides
an automated and manual way to start radio-related troubleshooting of log collections and traces.
In Cloud RAN BTS, using UTF is optional.

1.2 Central container registry in Cloud RAN BTS solution

Central container registry (CCR) is an Open Container Initiative (OCI) compliant registry that
provides a storage and content delivery system for OCI artifacts. In AirScale Cloud RAN BTS
(Cloud RAN BTS) solution, the CCR is integrated with MantaRay NM.

The role of the CCR in Cloud RAN BTS

CCR has been introduced into the Cloud RAN BTS life cycle management (LCM) solution by the
CB009813: Central Container Registry for Cloud RAN BTS solution feature. Cloud RAN BTS
uses Harbor, an open-source registry, as a default CCR for the following software images:
Red Hat OpenShift Container Platform (OCP) images
Cloud-native network function (CNF) images

The content stored in the CCR is available:

for direct use by Kubernetes, which controls the applications running in Containers-as-a-
Service (CaaS) clusters.
for indirect use by distributed container registries located closer to the Kubernetes cluster,
which controls the running cloud applications.

During the installation of MantaRay NM, CCR is installed as a container service on Compute1
virtual machine (VM), which is an optional VM for the MantaRay NM LCM. After the CCR is installed,
configured, and integrated with Nokia Edge Automation Tool (NEAT) and MantaRay NM, you can
use the respective tools to onboard the software images to the CCR:
NEAT for OCP images
MantaRay NM for CNF images

For more information on the installation and configuration of the CCR, see Administering CCR in
MantaRay NM Operating Documentation.

For more information on the CCR integration to MantaRay NM, see Integrating Container

22 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Registry in MantaRay NM in MantaRay NM Operating Documentation.

CNF artifact distribution workflow

CNF software image package needs to be onboarded to the MantaRay NM Software Manager
(SWM) using the graphical user interface (GUI) or the northbound interface (NBI). Only then, you
can onboard such a package to the CCR. As the software image package is delivered to the
MantaRay NM SWM:
the CNF software images are stored in the SWM Network File System (NFS).
the CNF metadata is stored in the SWM metadata.

The MantaRay NM Workflow Engine provides LCM operations, which fetch the artifacts from
the SWM NFS and push them to the CCR.​

Figure 4: CNF artifact distribution workflow

OCP artifact distribution workflow

OCP software image package needs to be onboarded to the NEAT software manager through the
NEAT GUI. Only then, you can onboard such a package to the CCR. For more information, see
Operating Documentation/AirScale Cloud RAN BTS System/Operation/Deploying and
Operating Nokia Red Hat OCP.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 23

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 5: OCP artifact distribution workflow

1.3 Cloud RAN BTS solution interworking

The AirScale Cloud RAN BTS (Cloud RAN BTS) life cycle management (LCM) operations involve
communication between several cooperating tools and systems. To perform Cloud RAN BTS LCM
operations, you need to enable communication between the relevant tools and systems.

Cloud RAN BTS deployment is based on the cooperation between the following tools and systems:
Nokia AirFrame Data Center Manager (NADCM) for hardware management
Nokia Edge Automation Tool (NEAT) for installation and management of the cloud
infrastructure and preparation of the Nokia AirFrame Fronthaul Gateway (FHGW) deployment
MantaRay NM as network management system (NMS)
Central container registry (CCR) as an Open Container Initiative (OCI) artifacts repository and
content delivery system

24 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 6: Cloud RAN BTS communication diagram

CaaS Containers-as-a-Service

CM configuration management

CMP Certificate Management Protocol

CNF cloud-native network function

FM fault management

OCP Red Hat OpenShift Container Platform

PM performance management

RU radio unit

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 25

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
SWSt Nokia Software Supply tool

To perform the Cloud RAN BTS LCM operations, you need to enable the following connections
between relevant tools and systems:

26 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 2: Cloud RAN BTS LCM communication matrix

Connectio Operation requiring the Element 1 Element 2 Port

n number connection
on the
diagram

1 Configuration delivery User NEAT 443 (for HTTPS)

operator 80 (for HTTP)

2 Cloud instance repository CaaS LCM NEAT 443

synchronization OAuth
server

NEAT 443
application
programmi
ng interface
(API)

3 Hardware commissioning NEAT NADCM 443

4 Hardware commissioning NADCM Hardware 443

server -
Redfish

Hardware 67, 68 (DHCPv4)

server - 546, 547 (DHCPv6)
hardware
discovery

Hardware 69 (TFTP)
server - 6996 (NADCM HTTP)
FHGW
deployment
with
Preboot
Execution
Environmen
t (PXE)
method

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 27

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Connectio Operation requiring the Element 1 Element 2 Port
n number connection
on the
diagram

5 OCP cluster networking, NEAT Hardware 30090, 30050 ( OCP

creation, and server - deployment)
customization OCP 6443 (OCP API)
deployment 53 (DNS)

Hardware 22 (NEAT file transfer with

server - SFTP)
FHGW
deployment
with PXE
and Plug
and Play
(PnP)
methods

Hardware 8080 (NEAT file transfer

server - with HTTP)
FHGW 6996 (NADCM file transfer
deployment with HTTP)
with PXE 3180, 3181 (FHGW
methods deployment monitoring
with HTTP)
22 [configuring FHGW over
Secure Shell (SSH)]
8080 (configuring FHGW
over NE3S)

6 CNF image delivery OCP cluster CCR 8443

or Podman

7 CNF image delivery Nokia Cloud CCR 8443

RAN
SmartNIC
(RAN NIC)
Software
Controller

8 OCP image delivery NEAT CCR 8443

28 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Connectio Operation requiring the Element 1 Element 2 Port
n number connection
on the
diagram

9 CNF deployment vCU, vDU, MantaRay 6443

and Nokia NM
proprietary
Kubernetes
operators
for Cloud
RAN BTS
CNFs

10 CNF monitoring vCU and MantaRay 8080

vDU CNFs NM

11 CNF configuration vCU and MantaRay 8080

vDU CNFs NM

12 Certificate enrollment vCU and CMPv2 8080

vDU CNFs

1.4 Deploying Cloud RAN BTS

An overview of the full end-to-end AirScale Cloud RAN BTS (Cloud RAN BTS) deployment process,
including references to detailed instructions for the individual steps

Purpose
To deploy Cloud RAN BTS, you need the following supporting tools and systems:
MantaRay NM, which is a network management system (NMS).
Nokia AirFrame Data Center Manager (NADCM), which is a hardware infrastructure
management system.
Nokia Edge Automation Tool (NEAT), which is a cloud infrastructure management system.

If there are no existing instances of the supporting tools in your network, you need to deploy and
commission them first. After that you can start the deployment of the actual Cloud RAN BTS
components:
Virtualized gNB central unit (vCU)

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 29

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Virtualized gNB distributed units (vDUs) with Nokia Cloud RAN SmartNICs (RAN NICs)
Nokia proprietary Kubernetes operators for Cloud RAN BTS
Nokia AirFrame Fronthaul Gateways (FHGWs)
Cell site routers (CSRs)
Radio units (RUs)

For detailed information on the role of the supporting tools and systems in the overall Cloud RAN
BTS deployment process, see Cloud RAN BTS LCM overview.

The order of the steps presented in this procedure is a guideline. Some steps can be performed
simultaneously.

Integrating the vCU, vDU, FHGW, and RUs with each other and with the core network is not
treated as a separate step, but is done as part of the configuration provisioning.

The steps that describe operations on the vDUs, RUs, CSR, and FHGW are referring to a particular
site. You need to repeat these steps for every site.

Before you start

Make sure that:

the hardware is delivered to the destination site.
the Certificate Management Protocol (CMP) server is installed in the network.
the central container registry (CCR) is installed in the network.
the customer Domain Name Server (DNS) is provisioned to IP mapping with Kubernetes
application programming interface (API) fully qualified domain name (FQDN).

Note:
CCR runs in the management cluster alongside the NMS and stores the cloud-native
network function (CNF) and cloud infrastructure container images. You can access the CCR
using MantaRay NM.

Procedure
1 Deploy and integrate the supporting tools and systems.

You need to perform this step only if there are no existing instances of the supporting tools
in your network.
1.1 Deploy MantaRay NM.

30 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For instructions, see the Installation chapter in MantaRay NM Operating
Documentation.

1.2 Integrate MantaRay NM with CCR.

For more information, see Configuring and integrating CCR with MantaRay NM.

1.3 Deploy NADCM and NEAT.

NADCM and NEAT need to be installed on the same Kubernetes cluster. Installation of
NADCM is a step in the NEAT installation procedure. The NADCM software is included
in the NEAT installation package. For instructions, see Operating
Documentation/Nokia Edge Automation Tool//Installation/Installing NEAT.

Note:
The NEAT installation package also includes NEAT Planner Application, which is
used to create edge data center deployment plans, needed as input for the
NEAT workflows. For more information, see Operating Documentation/Nokia
Edge Automation Tool/Operations and Maintenance/Operating NEAT
Planner Application.

1.4 Integrate NEAT with MantaRay NM.

For more information, see Integrating NEAT with MantaRay NM.

1.5 Integrate NEAT with the CCR.

For instructions, see Operating Documentation/Nokia Edge Automation

Tool/Operations and Maintenance/Operating and Maintaining NEAT.

2 Onboard the required software packages to MantaRay NM.

You need to onboard the following software packages:

FHGW
vCU
vDU
Nokia proprietary Kubernetes operators for Cloud RAN BTS

For instructions, see Onboarding software packages to MantaRay NM.

3 Onboard the CNF packages to the CCR.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 31

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
You can onboard CNF packages to the CCR during their onboarding to MantaRay NM
or during the CNF deployment operation. If neecessary, you can also onboard the CNF
packages to CCR independently. For more information, see Onboarding software
images to the container registry.

4 Onboard the Nokia Red Hat OpenShift Container Platform (OCP) images to the CCR.

For instructions, see Operating Documentation/AirScale Cloud RAN BTS

System/Operation/Deploying and Operating Nokia Red Hat OCP.

5 Prepare the RAN configuration and edge data center plan.

5.1 Prepare the site configuration files (SCFs) and the value override files for your
deployment.

For instructions, see Preparing RAN configuration.

5.2 Create an edge data center plan in NEAT Planner Application.

For instructions, see the Planning workflow chapter in the Operating

Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating NEAT Planner Application document.
You need an edge data center plan for running NEAT workflows. NEAT workflows allow
you, for example, to automatically discover the hardware of your edge data center,
deploy OCP on hardware servers, and create FHGW configuration.

6 Configure and integrate the CSR.

You can configure and integrate the CSR using NADCM. For instructions, see Operating
Documentation/Nokia AirFrame Data Center Manager/Operations and
Maintenance/Operating and Maintaining NADCM.

7 Configure and integrate the leaf switches.

You can configure and integrate the leaf switches:

manually in NADCM.
automatically in NEAT, using workflows.

For instructions, see Operating Documentation/Nokia AirFrame Data Center

32 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Manager/Operations and Maintenance/Operating and Maintaining NADCM and Operating
Documentation/Nokia Edge Automation Tool/Operations and Maintenance/Operating and
Maintaining NEAT.

8 Deploy and commission the vCU.

8.1 Install the hardware servers at the edge site.

Note:
In some deployment models, the vCU can also be co-located with the vDU at
the far edge or cell site. In such a case, you install the hardware simultaneously
for both the vDU and the vCU. For more information on the Cloud RAN BTS
deployment models, see Overview and requirements for Cloud RAN BTS
startup.

8.2 Configure and integrate the networking.

You can configure and integrate the networking:

manually in NADCM.
automatically in NEAT, using workflows.

For instructions, see Operating Documentation/Nokia AirFrame Data Center

Manager/Operations and Maintenance/Operating and Maintaining NADCM and
Operating Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating and Maintaining NEAT.

8.3 Commission the hardware servers.

You can commission the hardware:

manually in NADCM.
automatically in NEAT, using workflows.

For instructions, see Operating Documentation/Nokia AirFrame Data Center

Manager/Operations and Maintenance/Operating and Maintaining NADCM and
Operating Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating and Maintaining NEAT.

8.4 Deploy an OCP cluster for the vCU using NEAT.

You need to select a target deployment profile, specific to your configuration. For

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 33

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
more information on the Cloud RAN BTS deployment models, see Overview and
requirements for Cloud RAN BTS startup.

For more information, see Deploying cloud infrastructure.

Tip:
If the vCU and vDU are co-located, you only need to deploy one OCP cluster for
both CNFs.

8.5 Prepare MantaRay NM for the CNF deployment.

Follow the instructions in Preparing CNF deployment in MantaRay NM.

8.6 Prepare a CNF deployment plan and Kubernetes secrets for a CNF object in MantaRay
NM.

Follow the instructions in Creating a CNF deployment plan.

8.7 Deploy the vCU.

Follow the instructions in Deploying a CNF in MantaRay NM without autoconfiguration

or Deploying a CNF in MantaRay NM with autoconfiguration (PnP).

Note:
You need to set a target deployment profile, specific to your configuration,
with the correct parameter value in the values override files. For more
information, see Filling in the values override files for the vCU.

8.8 [Optional] Commission the vCU.

For instructions, see Commissioning with CU WebEM.

Note:
You need to commission the vCU in CU WebEM only if you didn't use
autoconfiguration during the deployment.

34 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
9 Install the RUs at the cell site.

10 Deploy and commission the vDU.

10.1 Install the hardware servers and the IXR switches (if used) at the far edge or cell site .

Note:
In some deployment models, the vCU can be co-located with the vDU at the far
edge or cell site. In such a case, you install the hardware simultaneously for
both the vDU and the vCU. For more information on the Cloud RAN BTS
deployment models, see Overview and requirements for Cloud RAN BTS
startup.

10.2 Configure and integrate the networking.

You can configure and integrate the networking:

manually in NADCM.
automatically in NEAT, using workflows.

For instructions, see Operating Documentation/Nokia AirFrame Data Center

Manager/Operations and Maintenance/Operating and Maintaining NADCM and
Operating Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating and Maintaining NEAT.

10.3 Commission the hardware servers and the IXR switches (if used).

You can commission the hardware:

manually in NADCM.
automatically in NEAT, using workflows.

For instructions, see Operating Documentation/Nokia AirFrame Data Center

Manager/Operations and Maintenance/Operating and Maintaining NADCM and
Operating Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating and Maintaining NEAT.

10.4 Deploy an OCP cluster for the vDU using NEAT.

You need to select a target deployment profile, specific to your configuration. For
more information on the Cloud RAN BTS deployment models, see Overview and
requirements for Cloud RAN BTS startup.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 35

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For more information, see Deploying cloud infrastructure.

Tip:
If the vCU and vDU are co-located, you only need to deploy one OCP cluster for
both CNFs.

10.5 Deploy and commission FHGW.

For more information, see Deploying and commissioning FHGW.

10.6 Prepare MantaRay NM for the CNF deployment.

Follow the instructions in Preparing CNF deployment in MantaRay NM.

10.7 Prepare a CNF deployment plan and Kubernetes secrets for a CNF object in MantaRay
NM.

Follow the instructions in Creating a CNF deployment plan.

10.8 Deploy Nokia proprietary Kubernetes operators for Cloud RAN BTS on the vDU
Kubernetes cluster.

Nokia proprietary Kubernetes operators for Cloud RAN BTS include the RAN NIC
Software Controller and Nokia Advanced Synchronization Kubernetes Operator (Nokia
Synchronization Operator). You need these operators to install and use the RAN NICs.
For instructions, see Deploying a CNF in MantaRay NM without autoconfiguration.

10.9 Deploy the vDU.

Follow the instructions in Deploying a CNF in MantaRay NM without autoconfiguration

or Deploying a CNF in MantaRay NM with autoconfiguration (PnP).

Note:
You need to set a target deployment profile, specific to your configuration,
with the correct parameter value in the values override files. For more
information, see Filling in the values override files for the vDU.

36 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Tip:
If the vDU deployment fails, you may need to update the RAN NIC firmware.
For instructions, see Operating Documentation/AirScale Cloud RAN
BTS/Upgrade/Upgrading Cloud RAN BTS System.

10.10 [Optional] Commission the vDU.

For instructions, see Commissioning with vDU WebEM.

Note:
You need to commission the vDU in vDU WebEM only if you didn't use
autoconfiguration during the deployment.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 37

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
2. Cloud RAN BTS software delivery

Nokia provides software packages for the cloud-native network functions (CNFs), physical
network functions (PNFs), cloud infrastructure, Nokia proprietary Kubernetes operators for
AirScale Cloud RAN BTS (Cloud RAN BTS), and hardware. To execute the deployment, the software
packages need to be delivered to the following tools: MantaRay NM, Nokia Edge Automation Tool
(NEAT), or Nokia AirFrame Data Center Manager (NADCM).

Software package types

Cloud RAN BTS uses the following software package types for life cycle management (LCM)
operations:

38 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 3: Software packages used in Cloud RAN BTS life cycle management operations

Software package Tool executing the Software package function

type deployment

CNF MantaRay NM Holds the container images and deployment

instructions for the virtualized gNB central unit
(vCU) and virtualized gNB distributed unit (vDU)
deployment, including the Nokia Cloud RAN
SmartNIC (RAN NIC) software.

Nokia proprietary MantaRay NM Holds the container images and deployment

Kubernetes operators instructions for Nokia proprietary Kubernetes
for Cloud RAN BTS operators for Cloud RAN BTS, such as the RAN
NIC Software Controller and the Nokia
Advanced Synchronization Operator (Nokia
Synchronization Operator).

Cloud infrastructure NEAT Holds the images for deploying Red Hat
OpenShift Container Platform (OCP).

PNF MantaRay NM Holds the software image for Nokia AirFrame

Fronthaul Gateway (FHGW) and radio units
(RUs).

Embedded software NADCM Holds the embedded software and operating

system images for deploying hardware.

Note:
The following software packages are collected and distributed as a part of the Cloud RAN
BTS software releases:
CNF
Nokia proprietary Kubernetes operators for Cloud RAN BTS
Cloud infrastructure
PNF

The embedded software packages are distributed as a part of the AirFrame product
releases.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 39

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
2.1 Downloading software packages from SWSt

You need to download the AirScale Cloud RAN BTS (Cloud RAN BTS) software packages from
Nokia Software Supply Tool (SWSt) before you can manually import and onboard them to the tool
executing the deployment.

Purpose
To deploy Cloud RAN BTS, you need to first download the following software packages from SWSt:

Nokia Red Hat OpenShift Container Platform (OCP)

Nokia AirFrame Fronthaul Gateway (FHGW)
Virtualized central unit (vCU)
Virtualized distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Procedure
1 Go to SWSt on Nokia Support Portal.

2 Navigate to Services›Downloads: SwST›Software Catalog›Radio

Network›Base Stations›AirScale Cloud RAN BTS and find the desired Cloud
RAN BTS release.

Step example
24R1-CR SW:›ID: 24R1-CR AirScale Cloud RAN BTS 0.0TD

3 Check the box next to the selected file and click DOWNLOAD.

Note:
You can select and download multiple files at the same time.

4 Save the selected packages locally on your computer disc.

40 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Postrequisites
After downloading the software packages, you need to import and onboard the packages to the
tool executing the deployment:
Nokia Edge Automation Tool (NEAT) for Nokia Red Hat OCP. For instructions, see Deploying
cloud infrastructure.
MantaRay NM for FHGW, vCU, vDU, and Nokia proprietary Kubernetes operators for Cloud RAN
BTS. For instructions, see Onboarding software packages to MantaRay NM manually.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 41

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
3. Preparing RAN configuration

You need to prepare the configuration for both the virtualized gNB central unit (vCU) and the
virtualized gNB distributed units (vDUs) before you deploy AirScale Cloud RAN BTS. The
configuration consists of two sets of parameters: BTS parameters in a site configuration file (SCF)
and deployment parameters collected in Helm values override files.

3.1 vCU and vDU parameters

The cloud gNB is configured using managed object (MO) parameters. The gNB split introduces
common and separate parameters for the virtualized gNB central unit (vCU) and virtualized gNB
distributed units (vDUs). Matching values of the common parameters must be set in the vCU and
the vDUs for correct operation.

You can correct the inconsistencies between vCU and vDU parameters and MO definitions in the
MantaRay NM CM Analyzer view. For more information, see the CM Analyzer Help chapter in
MantaRay NM Operating Documentation.

In AirScale Cloud RAN BTS (Cloud RAN BTS), the following parameters require identical settings in
interconnected vCUs and vDUs:

42 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 4: vCU and vDUs parameters requiring identical settings

Parameters Required settings

NRBTS New Radio Basestation The value must be the same for the vCU and
instance identifier (nrBtsId) all interconnected vDUs.

NRDU New Radio Distributed Unit The value must be the same on both the vCU
instance identifier (nrDuId) and vDU side for a pair of NRDU objects having
the same value of the gNbDuId parameter.

NRCELL Local cell resource ID The lcrId parameter together with the
(lcrId) nrBtsId parameter identify a cell within a
public land mobile network (PLMN).1

NRCELLGRP New Radio Cell Group Two NRCELLGRP objects, one in the vCU and
instance identifier (nrCellGrpId) one in the vDU, which contain the same list of
NRCELL objects must have the same value of
the nrCellGrpId parameter.2

1
After any cell addition or reconfiguration, you need to check the cell parameters using the MS
Excel-based Adaptive PDCCH Configuration Tool. Only then, the cell is configured correctly. You
can find the tool in Discovery Center under Reference Documentation/Product
Configurations/Adaptive PDCCH Configuration Tool.

2
Keep the value of the NRCELL New Radio Cell instance identifier (nrCellId)
parameter equal in the vCU and vDUs. Managed object IDs in counters and alarms are created
using the nrCellId parameter.

Note:
The above parameter list is partial. For the full parameter list, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document.

Some parameters are common to the vCU and vDUs, although there are also parameters that
exist only in the vCU and others that exist only in vDUs. Common parameters must have the same
values for interconnected object instances, meaning corresponding objects, in both the vCU and
the vDUs.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 43

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 5: Common vCU and vDU parameters
Full parameter name Abbreviated parameter name MO path

Activate carrier aggregation actCarrierAggregation MRBTS/NRBTS

Activate DDDS period optimization actDDDSPeriodOptimization MRBTS/NRBTS

Activate multi DRBs per NSA UE actMultiDrbNSA MRBTS/NRBTS

Activate non-GBR service differentiation actNonGbrServiceDiff MRBTS/NRBTS

gNB id length gNbIdLength MRBTS/NRBTS

MCC in PLMN mcc MRBTS/NRBTS

MNC in PLMN mnc MRBTS/NRBTS

MNC length of PLMN ID in primary PLMN of gNB mncLength MRBTS/NRBTS

SRB3 Support Enabled srb3SupportEnabled MRBTS/NRBTS

Activate connected DRX actCDrx MRBTS/NRBTS/NRCELL

Cell deployment type cellDepType MRBTS/NRBTS/NRCELL

Cell name cellName MRBTS/NRBTS/NRCELL

Channel bandwidth chBw MRBTS/NRBTS/NRCELL

Frequency band Indicator NR freqBandIndicatorNR MRBTS/NRBTS/NRCELL

NR Absolute radio frequency channel number nrarfcn MRBTS/NRBTS/NRCELL

Physical cell identifier physCellId MRBTS/NRBTS/NRCELL

DRX Long Cycle drxLongCycle MRBTS/NRBTS/NRCELL/drxProfile

1

SSB Frequency ssbFrequency MRBTS/NRBTS/NRCELL/NRHOIF

SCS scs MRBTS/NRBTS/NRCELLGRP

SP-Cell change enabled spCellChangeEnabled MRBTS/NRBTS/NRCELLGRP

Multi-frequency band Indicator NR multiFreqBandIndicatorNR MRBTS/NRBTS/NRCONNECTMODE_PR

OFILE

DL flow control algorithm dlFlowControlAlgo MRBTS/NRBTS/NRDRB

Performance measurement counter group pmCounterGroup MRBTS/NRBTS/NRDRB

List of 5QI values fiveqiValueList MRBTS/NRBTS/NRDRB_5QI

List of QCI values qciValueList MRBTS/NRBTS/NRDRB_QCI

Activate DDDS reduction actDddsReduction MRBTS/NRBTS/NRDRB/nsaDrbPara

m

Frequency band indicator NR freqBandIndicatorNR MRBTS/NRBTS/NRMULTIBANDINFO_PR

OFILE

New Radio band priority nrBandPriority MRBTS/NRBTS/NRMULTIBANDINFO_PR

OFILE/nrMultibandInfoList

New Radio Network Signaling Pmax Profile nrNsPmaxProfileDN MRBTS/NRBTS/NRMULTIBANDINFO_PR

distinguished name OFILE/nrMultibandInfoList

NR NS Pmax priority nrNsPmaxPriority MRBTS/NRBTS/NRNSPMAX_PROFILE/n

rNsPmaxList

Additional Pmax additionalPmax MRBTS/NRBTS/NRNSPMAX_PROFILE/n

RNSPmaxList

Additional spectrum emission additionalSpectrumEmission MRBTS/NRBTS/NRNSPMAX_PROFILE/n

RNSPmaxList

Multi-frequency band Indicator NR multiFreqBandIndicatorNR MRBTS/NRBTS/NRSYSINFO_PROFILE/N

RIAFIM

44 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Full parameter name Abbreviated parameter name MO path

New Radio Multiband Information Profile user label userLabel MRBTS/NRBTS/NRMULTIBANDINFO_PR

OFILE

New Radio Network Signaling Pmax Profile user label userLabel MRBTS/NRBTS/NRNSPMAX_PROFILE

Note:
The above parameter list is partial. For the full parameter list, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document.

For each managed object class (MOC), there is a parameter which defines that an instance on the
vCU side is interconnected with an instance on the vDU side. The pairing object attribute is not
always the MOC ID.

Table 6: Common vCU and vDU parameters used for pairing

Full parameter name Abbreviated parameter name MO path

New Radio Basestation instance nrBtsId MRBTS/NRBTS

identifier

Local cell resource ID lcrId MRBTS/NRBTS/NRCEL

L

List of NR cells assigned to nrCellList MRBTS/NRBTS/NRCEL

cell group LGRP

New Radio DRB Profile instance nrDrbId MRBTS/NRBTS/NRDR

identifier B

New Radio 5QI to DRB Profile nrDrb5qiId MRBTS/NRBTS/NRDR

Mapping instance identifier B_5QI

New Radio QCI to non-GBR DRB nrDrbQciId MRBTS/NRBTS/NRDR

Profile Mapping instance B_QCI
identifier

gNB DU ID gNbDuId MRBTS/NRBTS/NRDU

Note:
The above parameter list is partial. For the full parameter list, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 45

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
To connect the vCU to the vDU, you need to configure vCU parameters listed in Table: vCU
parameters required for a working connection to vDU. These parameters can be configured using
CU WebEM or the site configuration file (SCF). For more information, see Creating a configuration
plan in CU WebEM and Configuring vCU parameters in SCF.

Table 7: vCU parameters required for a working connection to vDU

Full parameter name Abbreviated parameter name MO path

Reference to an Ethernet link, an linkSelectorDN MRBTS/TNLSVC/TNL/ETHSV

external or internal bridgeport C/ETHIF

UnderLying Interface used by the underLyingInterface MRBTS/TNLSVC/TNL/ETHSV

Ethernet link C/ETHLK

Layer 2 interface reference interfaceDN MRBTS/TNLSVC/TNL/IPNO/I

PIF

IP address allocation method ipAddressAllocationMethod MRBTS/TNLSVC/TNL/IPNO/I

PIF/IPADDRESSV4

Unique IP address identifier uniqueIpAddressIdentifier MRBTS/TNLSVC/TNL/IPNO/I

PIF/IPADDRESSV4

Note:
The above parameter list is partial. For the full parameter list, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document.

You also need to configure the vDU parameters listed in Table: vDU parameters required for a
working connection to vCU. These parameters can also be configured using vDU WebEM or the
SCF. For more information, see Creating a configuration plan in vDU WebEM and Configuring vDU
parameters in SCF.

Table 8: vDU parameters required for a working connection to vCU

Full parameter name Abbreviated parameter name MO path

Remote F1 C-Plane IPv4/v6 address of remotef1CplaneIpAddr MRBTS/NRBTS/NRDU

second vCU

Label of the connector by the connectorLabel MRBTS/TNLSVC/TNL/ETH

Ethernet link SVC/ETHLK

46 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
The above parameter list is partial. For the full parameter list, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document.

vDU preconfiguration parameters

The parameter NRTBS F1 Non-UE Proc Guard Timer (timerf1NonUeProcGuard)
needs to be adjusted to the downtime of the transport component switch, for example, the Nokia
7250 IXR-e2 or third-party components switch. When the transport switch carrying the F1 traffic is
down and the timerf1NonUeProcGaurd parameter is configured to a lower value than the
downtime of the transport switch, fault 1806 Communication failure is raised. The fault
triggers the cloud-native network function (CNF) restart, which results in the outage of the service
availability. Nokia recommends setting the timerf1NonUeProcGuard parameter to 300
seconds, with the assumption that the Nokia AirFrame Fronthaul Gateway (FHGW) is included in
the deployment configuration.

3.2 Site configuration file

The site configuration file (SCF) contains all cloud gNB parameters. Modify the SCF to customize
the requirements for the cloud gNB.

The SCF contains all necessary configuration details for management, hardware, and transmission
for the network elements. This configuration is required for the gNB to work properly, and to
commission the virtualized gNB central unit (vCU) and the virtualized gNB distributed units (vDUs).
You can configure and modify the SCF in two ways:

Offline Prepare a golden SCF template. For related procedures, see:

• Loading an SCF to vDU WebEM
• Loading an SCF to CU WebEM

Online • Using vDU WebEM to create an SCF. For more information, see
Creating a configuration plan in vDU WebEM.
• Using CU WebEM to create an SCF. For more information, see
Creating a configuration plan in CU WebEM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 47

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
The SCF template comes with the software package that can be downloaded from
Support Portal.

The SCF is an XML file in the RAML 2.0 or 2.1 format.

3.2.1 Configuring vCU parameters in SCF

You need to configure a site configuration file (SCF) before uploading it to the virtualized gNB
central unit (vCU).

Purpose
The SCF is a configuration file that can be applied to the gNB directly. The SCF template is part of
the software package that can be downloaded from Support Portal. The template contains
parameters with recommended values, but it requires modification to your specific deployment,
feature activation, and feature configuration.

Note:
Edit the file locally before uploading it from your local device.

Procedure
1 Open the SCF in a text editor.

Note:
To edit the SCF, you can also use the Parameter Editor in CU WebEM. For more
information, see Creating a configuration plan in CU WebEM.

2 Configure the f1c IP address and static route parameters.

Go to f1Cplane and configure the IP data for the cpif pod fronthaul interface.

48 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 9: f1Cplane parameters for configuration
Managed object (MO) path Parameter name Description Example

MRBTS/TNLSVC/TNL/ETHSVC/ETHIF/VLANIF vlanIfName Identifier used for discovering a VLAN interface. Its value f1cplane
needs to be the same as the value of the vlName
parameter of the network in the values override file. For
more information, see Filling in the values override files
for the vCU.

MRBTS/TNLSVC/TNL/ETHSVC/ETHLK underLyingInterfac Underlying interface in the cloud-native network function fronthaul

e (CNF) environment used by the Ethernet link. For
f1Cplane set this parameter to fronthaul.

MRBTS/TNLSVC/TNL/IPNO/IPIF interfaceDN Data link layer interface reference. MRBTS-2205/TNLSVC-1/TNL-2/ETHSVC-1/ET

HIF-2

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 f1Cplane/ipV4Addre The primary IPv4 address discovered on the vCU F1 MRBTS-2205/TNLSVC-1/TNL-2/IPNO-1/IPIF
ssDN1 control plane (C-plane). -2/IPADDRESSV4-1

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 ipAddressAllocatio The IP address allocation method for a fronthaul IP in the DISCOVERED
nMethod cpif pod. The IP address DISCOVERED is for the IP
address allocated during the vCU deployment.

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 uniqueIpAddressIde The IPv4 interface in a CNF environment F1-C

ntifier

3 Configure the f1u IP address.

Go to f1Uplane and configure the IP data for the upue pod fronthaul interface.

Table 10: f1Uplane parameters for configuration

MO path Parameter name Description Example

MRBTS/TNLSVC/TNL/ETHSVC/ETHIF linkSelectorDN Reference to the internal bridgeport, external bridgeport MRBTS-2205/TNLSVC-1/TNL-3/ETHSVC-1/ET

(BRGPRT) or the Ethernet link HLK-2

MRBTS/TNLSVC/TNL/ETHSVC/ETHIF/VLANIF vlanIfName Identifier used for discovering a VLAN interface. Its value f1cplane
needs to be the same as the value of the vlName
parameter of the network in the values override file. For
more information, see Filling in the values override files
for the vCU.

MRBTS/TNLSVC/TNL/ETHSVC/ETHLK underLyingInterfac Underlying interface in a cloud-native network function fronthaul

e (CNF) environment used by the Ethernet link. For
f1Uplane set this parameter to fronthaul.

MRBTS/TNLSVC/TNL/IPNO/IPIF interfaceDN Data link layer interface reference. MRBTS-2205/TNLSVC-1/TNL-3/IPNO-1/IPIF

-2/IPADDRESSV4-1

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 f1Uplane/ipV4Addre The primary IPv4 address discovered on the vCU F1 user MRBTS-2205/TNLSVC-1/TNL-3/IPNO-1/IPIF
ssDN1 plane (U-plane). -2/IPADDRESSV4-1

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 ipAddressAllocatio The IP address allocation method for a fronthaul IP in the DISCOVERED
nMethod upue pod. The IP address DISCOVERED is for the IP
address allocated during the vCU deployment.

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 uniqueIpAddressIde The IPv4 interface in a CNF environment. F1-U

ntifier

4 Save the SCF.

Postrequisites
Once your SCF file is configured and all the parameters are set, you can upload the file to CU
WebEM. For more information, see Loading an SCF to CU WebEM.

To validate the SCF in CU WebEM, follow Validating an SCF in vDU WebEM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 49

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
3.2.2 Configuring vDU parameters in SCF

You need to configure a site configuration file (SCF) before uploading it to the virtualized gNB
distributed unit (vDU).

Purpose
The SCF is a configuration file that can be applied to the gNB directly. The SCF template is part of
the software package that can be downloaded from Support Portal. The template contains
parameters with recommended values, but it requires modification to your specific deployment,
feature activation, and feature configuration.

Note:
Edit the file locally before uploading it from your local device.

Procedure
1 Open the SCF in a text editor.

Note:
To edit the SCF, you can also use the Parameter Editor in vDU WebEM. For more
information, see Creating a configuration plan in vDU WebEM.

2 Configure the f1c IP address and static route parameters.

Go to f1Cplane and configure the Virtual Local Area Network (VLAN) IP address used for
connection between the virtualized gNB distributed unit (vDU) and the virtualized gNB central
unit (vCU).

Table 11: f1Cplane parameters for configuration

Managed object (MO) path Parameter name Description Example

MRBTS/TNLSVC/TNL/ETHSVC/ETHIF/VLANIF vlanIfName Identifier used for discovering a VLAN interface. Its value f1cplane
needs to be the same as the value of the vlName
parameter of the network in the values override file. For
more information, see Filling in the values override files
for the vDU.

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 f1Cplane/ipV4Addr The primary IPv4 address discovered on the vCU F1 MRBTS-2205/TNLSVC-1/TNL-1/IPNO-1/IPI
essDN1 control plane (C-plane). F-2/IPADDRESSV4-1

50 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
3 Configure the f1u IP address.

Go to f1Uplane and configure the IP data.

Table 12: f1Uplane parameters for configuration

MO path Parameter name Description Example

MRBTS/TNLSVC/TNL/ETHSVC/ETHIF/VLANIF vlanIfName Identifier used for discovering a VLAN interface. Its value f1uplane
needs to be the same as the value of the vlName
parameter of the network in the values override file. For
more information, see Filling in the values override files
for the vCU.

MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4 f1Uplane/ipV4Addr The primary IPv4 address discovered on the vCU F1 user MRBTS-2205/TNLSVC-1/TNL-1/IPNO-1/IPI
essDN1 plane (U-plane). F-2/IPADDRESSV4-1

4 Configure the remotef1CplaneIpAddr IP address.

Table 13: remotef1CplaneIpAddr parameter configuration

MO path Parameter Description Example

name

MRBTS/NRBTS/NRDU remotef1Cpl The remote F1 C-plane IPv4 or IPv6 10.44.71.88

aneIpAddr address at the vCU. The IP address is
the cpif pod fronthaul IP address.

5 Save the SCF.

Postrequisites
Once your SCF file is configured and all the parameters are set, you can upload the file to vDU
WebEM. For more information, see Loading an SCF to vDU WebEM.

To validate the SCF in vDU WebEM, follow Validating an SCF in vDU WebEM.

3.3 Filling in the values override files for the vCU

The virtualized gNB central unit (vCU) is deployed using Helm charts. Before the deployment, you
need to provide the Helm charts with configuration parameters and information about your
environment. You do this by editing YAML files included in the vCU deployment package.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 51

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Purpose
In AirScale Cloud RAN BTS (Cloud RAN BTS), the cloud-native network function (CNF) deployment is
automated using Helm. The details of resource creation and pod deployment are contained in the
Helm charts, included in the CNF deployment package. The Helm charts contain default
configuration values provided by Nokia. You need to provide the CNF instance-specific
configuration override values to the default configuration values by editing the values override
YAML files provided with the Helm charts.

Figure 7: Updating Helm chart configuration values from values override files

In the CNF deployment package, there are three values override files:
values-override.aic-vcu-cluster-preparation.yaml
values-override.aic-vcu-prerequisite.yaml
values-override.aic-vcu.yaml

Before the deployment, you need to fill in the mandatory parameters in the values-
override.aic-vcu.yaml file and all parameters in the remaining files. After the deployment,
you can provide additional parameter values in CU WebEM.

It's possible to deploy the CNF using autoconfiguration. In such a case, the CNF automatically
downloads the planned configuration from the network management system (NMS) and you don't
need to provide additional information after the deployment. Using autoconfiguration requires
you to provide additional parameter values for autoconnection and certificate managemet in the
values-override.aic-vcu.yaml, as well as the initial certificate enrolment secrets in the
cmp_secret.yaml and taTrustChain_secret.yaml files. You can find the files inside the
Secret folder of the CNF deployment package.

Before you start

Download the vCUCNF<version>.zip software package from Support Portal. For

instructions, see Downloading software packages from SWSt.

52 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Procedure
1 Extract the values override files.

Extract the following files from the HelmChart folder inside the vCUCNF<version>.zip
package:
values-override.aic-vcu-cluster-preparation.yaml
values-override.aic-vcu-prerequisite.yaml
values-override.aic-vcu.yaml

2 Edit the values-override.aic-vcu-cluster-preparation.yaml file in a text

editor and save the changes.

Table 14: Parameters in values-override.aic-vcu-cluster-preparation.yaml

Parameter name Description

sccName This parameter defines the security context constraints (SCC) name.
It allows administrators to control permissions for pods.
If the sccName parameter value is set to privileged, a new SCC
isn't created and a privileged SCC is bound to the
serviceaccounts parameter.
If the sccName parameter value isn't set to privileged or is set
to null, a new SCC is created and bound to the
serviceaccounts parameter.
The default value is cnf5g.

userName This parameter defines a user name of an object class (oc) user.
When the userName parameter value is different from null, roles
are added for an oc user so that the vCU can be deployed.

3 Edit the values-override.aic-vcu-prerequisite.yaml file in a text editor and

save the changes.

3.1 Update the network parameters.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 53

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 15: Network parameters under aic-vcu-network.devicePoolList in
values-override.aic-vcu-prerequisite.yaml

Parameter name Description

fastPathDevicePool This parameter defines the single-root input/output

virtualization (SR-IOV) device pool used by the external-u
network.

fastPathDevicePoolBa This parameter defines the SR-IOV device pool used by the
ckup external-u-s network. Its value should be different from the
fastPathDevicePool parameter value.

slowPathDevicePool This parameter defines the SR-IOV device pool used by the
external-c and internale1 networks.

slowPathDevicePoolBa This parameter defines the SR-IOV device pool used by the
ckup external-c-s and internal-s networks. Its value should be
different from the slowPathDevicePool parameter
value.

3.2 Update the storage parameters.

54 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 16: Storage parameters under global in values-override.aic-vcu-
prerequisite.yaml

Parameter name Description

accessModes This parameter defines the access modes of the persistent volume.
The supported values are:
• For the Red Hat OpenShift Container Platform (OCP) single-node (SNO):
ReadWriteOnce
• For OCP multi-node (MNO): ReadWriteMany

storageClassName This parameter defines the storage class name of the persistent volume. If
its value isn't specified, the default storage class is used.
The supported values are:
• For OCP SNO: localfs-lvm-sc
• For OCP MNO: ocs-storagecluster-cephfs

image.registry This parameter defines the image registry address.

For OCP, the default value of this parameter is image-
registry.openshift-image-registry.svc:5000/{{
.Release.Namespace }}.

restoreData This parameter defines whether to restore data which was backed up
when the permanent virtual circuit (PVC) was created. For more
information, see Operating Documentation/AirScale Cloud RAN BTS
System/Upgrading Cloud RAN BTS System.
The default value of this parameter is true.

4 Edit the values-override.aic-vcu.yaml file in a text editor and save the changes.

The values-override.aic-vcu.yaml file has the following structure:

Figure 8: Structure of the values-override.aic-vcu.yaml file

To deploy the vCU, you need to fill in the parameters in the following sections:
global (general parameters, network parameters, autoconnection parameters)
certman-auto-cmp (certificate management configuration parameters)
aic-vcu-upue, aic-vcu-cpif, aic-vcu-cpe2, and aic-oamext (subchart LRIP
round-check configuration parameters)

The values depend on your environment. For guidance, use the following tables and the

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 55

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
comments inside the file.

4.1 Fill in the general parameters.

56 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 17: General parameters under global in values-override.aic-
vcu.yaml

Parameter name Description

cnfLayout This parameter defines the CNF layout in the deployment.

The basic value means that the vCU doesn't support high availability (HA).
The redundant value means that the vCU supports HA.
The mini value means that fewer CPUs are used to deploy one vCU and that it
is deployed with one vDU on SNO.
The default value of this parameter is basic.

cpifInstanceCount This parameter defines the number of the 2N cpif redundancy instances.
You need to fill in the value of this parameter only if the value of the
cnfLayout parameter is set to redundant.
The supported values range from 1 to 4.

cpclInstanceCount This parameter defines the number of the 2N cpcl redundancy instances.
You need to fill in the value of this parameter only if the value of the
cnfLayout parameter is set to redundant.
The supported values range from 1 to 4.

cpueCount This parameter defines the number of cpue pods.

The maximum value of this parameter is 4.
If the cnfLayout parameter value is basic, the cpueCount parameter
values range from 1 to 8.
If the cnfLayout parameter value is redundant, the cpueCount
parameter values range from 2 to 8, and a value of 1 is automatically changed
to 2.
If the cnfLayout parameter value is mini, the cpueCount parameter values
range from 1 to 2.

upueCount This parameter defines the number of upue pods.

The maximum value of this parameter is 44.
If the cnfLayout parameter value is basic, the upueCount parameter
values range from 1 to 44.
If the cnfLayout parameter value is redundant, the upueCount
parameter values range from 2 to 44, and a value of 1 is automatically changed
to 2.
If the cnfLayout parameter value is mini, the upueCount parameter value
is 1.

upueFlavor This parameter defines the deployment flavor of the upue pod and indicates the
number of l2hicu containers and the resources requested for creation of new
trsfp containers.
Allowed values:
• small, if the value of the cnfLayout parameter is set to mini, basic, or
redundant. In such a case, the upueCount parameter values range from 2
to 44.
• medium, if the value of the cnfLayout parameter is set to redundant. In
such a case, the upueCount parameter values range from 2 to 22.
• large, if the value of the cnfLayout parameter is set to redundant. In
such a case, the upueCount parameter values range from 2 to 11.

cpe2Count This parameter defines the number of cpe2 pods. Redundancy of the cpe2 pod
is not supported.
Allowed values:
•0
•1

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 57

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Parameter name Description

minCapacityCPUE This parameter defines the minimum number of cpue pods to fulfil the capacity
requirements. If the requirement specified by the value of this parameter is not
met, the gNB raises an alarm.
The maximum value of this parameter is 8.
If the cnfLayout parameter value is basic, the minCapacityCPUE
parameter values range from 1 to 8.
If the cnfLayout parameter value is redundant, the minCapacityCPUE
parameter values range from 2 to 8, and a value of 1 is automatically changed
to 2.

minCapacityUPUE This parameter defines the minimum number of upue pods to fulfil the capacity
requirements. If the requirement specified by the value of this parameter is not
met, the gNB raises an alarm.
The maximum value of this parameter is 44.
If the cnfLayout parameter value is basic, the minCapacityUPUE
parameter values range from 1 to 44.
If the cnfLayout parameter value is redundant, the minCapacityUPUE
parameter values range from 2 to 44, and a value of 1 is automatically changed
to 2.

coreDumpPath This parameter defines the directory for host path volume to store the
coredump information.

storageClassName This parameter defines the storage class name of the persistent volume. If its
value isn't specified, the default storage class is used.
The supported values are:
• For OCP version 4.12 or higher SNO and SNO+1: lvms-vg1
• For OCP version lower than 4.12 SNO: localfs-lvm-sc
• For OCP MNO: ocs-storagecluster-cephfs

accessModes This parameter defines the access mode of the persistent volume.
The supported values are:
• For OCP SNO: ReadWriteOnce
• For OCP MNO: ReadWriteMany

image.registry This parameter defines the image registry address.

The default value of this parameter is image-registry.openshift-
image-registry.svc:5000/{{ .Release.Namespace }} for OCP.

timezone This parameter defines the time zone as a string in a Region/City format. The
default value of this parameter is UTC.
Example:
• Europe/Helsinki
• UTC

externalNetworkInterfaceEn This parameter defines whether the external network interface is enabled in
abled context of the system upgrade. For more information, see Operating
Documentation/AirScale Cloud RAN BTS System/Upgrading Cloud RAN BTS
System.
The default value of this parameter is true.

swReplacementType This parameter defines the type of software replacement operation for software
upgrade . For more information, see Operating Documentation/AirScale Cloud
RAN BTS System/Upgrading Cloud RAN BTS System.
The default value of this parameter is Rip & Replace.

blueGreenRollback This parameter defines the type of software replacement operation to be

performed for a network element (NE). For more information, see Operating
Documentation/AirScale Cloud RAN BTS System/Upgrading Cloud RAN BTS
System.
The default value of this parameter is false.

upgradeUserAccountSecretNa This parameter defines the name of the secret which is used in the blue-green
me upgrade post installation hook You need to create the secret vefore upgrading
the vCU. For more information, see Operating Documentation/AirScale Cloud
RAN BTS System/Upgrading Cloud RAN BTS System.

58 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Parameter name Description

nodeSelector This parameter assigns the pods to specific nodes. It's mainly used in the OCP
SNO+1 deployment, where the vCU needs to be deployed on the
Master+Worker+Storage node. You need to pre-define the node labels in
advance.

seLinux This parameter defines whether the Security-Enhanced Linux (SELinux) policies
are enforced.
If the value of the seLinux parameter is set to true, the SELinux mode is set
to enforcing.
If the value of the seLinux parameter is set to false, the SELinux mode is
set to permissive. Note that when the seLinux parameter value is set to
enforcing, audit logs are not available.
The allowed value of the seLinux parameter is true.

stackTraceEnabled This parameter enables global stack trace collection.

The collection of stack trace needs to be enabled as an alternative for
debugging. It prevents the program from crashing when files (other than core
dump files) are not achievable.
Allowed values:
• true
• false (default)

highPerformanceRunTimeClas This parameter enables Kubernetes RuntimeClass used for high performance.
s The default nokia-performance class is installed with OCP provided by
Nokia. Change the value if the deployment is performed on non-Nokia
infrastructure.

4.2 Fill in the subchart LRIP round-check configuration parameters under <sub
chart>.lripRoundcheckInfo.

Subchart names:
aic-vcu-upue
aic-vcu-cpif
aic-vcu-cpe2
aic-oamext

Table 18: LRIP round-check configuration parameters in values-override.aic-

vcu.yaml

Parameter name Description

instanceID This parameter defines the instance ID for the LRIP

round-check configuration.
The default value of this parameter is 1.

vlanId This parameter defines the VLAN ID as specified in the

network plan.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 59

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
4.3 Fill in the network parameters under the global.devicePoolList path.

Table 19: global.devicePoolList parameters in values-override.aic-

vcu.yaml

Parameter name Description

fastPathDevicePool This parameter defines the SR-IOV device pool used by the external-u network.
Its value must be the same as the value of the aic-vcu-
network.devicePoolList.fastPathDevicePool parameter in the
values-override.aic-vcu-prerequisite.yaml file.

fastPathDevicePoolBackup This parameter defines the SR-IOV device pool used by the external-u-s
network.
Its value must be the same as the value of the aic-vcu-
network.devicePoolList.fastPathDevicePoolBackup parameter
in the values-override.aic-vcu-prerequisite.yaml file.

slowPathDevicePool This parameter defines the SR-IOV device pool used by the external-c network.
Its value must be the same as the value of the aic-vcu-
network.devicePoolList.slowPathDevicePool parameter in the
values-override.aic-vcu-prerequisite.yaml file.

slowPathDevicePoolBackup This parameter defines the SR-IOV device pool used by the external-c-s network.
Its value must be the same as the value of the aic-vcu-
network.devicePoolList.slowPathDevicePoolBackup parameter
in the values-override.aic-vcu-prerequisite.yaml file.

4.4 Fill in the network parameters under the global.externalNetwork path.

Figure 9: Structure of the global.externalNetwork section in values-

override.aic-vcu.yaml

You need to configure the following networks:

In all deployments: oam, tracing, f1c, and f1u
In a 5G SA deployment, in addition to those for all deployments: ngc, xnc, xnu, and

60 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
ngu
In a 5G NSA deployment, in addition to those for all deployments: x2c, s1u, and x2u

Fill in the following fields:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 61

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 20: global.externalNetwork.<network name> parameters in
values-override.aic-vcu.yaml

Parameter name Description

vlanInfo.vid This parameter defines the guest VLAN for the corresponding
interface.
Make sure that the vlanInfo.vid parameter values are different
for the VLAN interfaces which have the same values of the
defaultUnderlyingIface parameter.

vlanInfo.vlName This parameter defines the name for further identification of the VLAN,
for example, in the case of configuring transport separation in the
NMS.
The vlanInfo.vlName parameter needs to be the same as the
VLAN interface name in the site configuration file (SCF).

vlanInfo.defaultUnderly This parameter defines the default underlying Ethernet interface for
ingIface the corresponding VLAN interface.

vlanInfo.secUnderlyingI This parameter defines the secondary underlying Ethernet interface for
face the corresponding VLAN interface.
It is not applicable to the transport network.

ipInfo.rangeStart TheipInfo parameters define the IP pool information.

You need to fill in both the rangeStart and rangeEnd
parameters. If the pool consists of only one IP address (IPv4 or IPv6),
use the same value for both.
ipInfo.rangeEnd Example:
• 192.168.254.33
• 2001:db8::1
The ipInfo.subnet defines the subnet including a mask.
ipInfo.subnet Example:
• 192.168.254.0/24
• 2001:db8::0/128

ipInfo.role This parameter defines the role of the interface when the transport
separation is configured in the NMS.
Its value needs to be the same as the value of the IPADDRESSV4
Unique IP address identifier
(uniqueIpAddressIdentifier) parameter or the
IPADDRESSV6 Unique IP address identifier
(uniqueIpAddressIdentifier) parameter for the network in the
SCF.
If there are multiple roles, separate them by space in the SCF.
Example: F1-U_customname1

policyRouteInfo.gateway This parameter defines the gateway IP address. It is applicable only to

the OAM network.
Allowed value of this parameter is an IPv4 or IPv6 address, for example:
• 192.168.254.33
• 2001:db8::1

physicalIpGroup.usePhys This parameter defines the group which will be using the set up OAM
icalIpGroup physical IP.
The supported values are:
• groupA
• groupB
• empty (default)

62 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Parameter name Description

physicalIpGroup.subnet This parameter defines the subnet including a mask. It is applicable only
to the OAM network.
Example:
• 192.168.254.0/24
• 2001:db8::0/128

physicalIpGroup.role This parameter defines the role of the interface when the transport
separation is configured in the NMS. It is applicable only to the OAM
network.
The value of the physicalIpGroup.role parameter needs to be
the same as the value of the IPADDRESSV4 Unique IP address
identifier (uniqueIpAddressIdentifier) parameter or the
IPADDRESSV6 Unique IP address identifier
(uniqueIpAddressIdentifier) parameter for the network in the
SCF.
If there are multiple roles, separate them by space in the SCF.

physicalIpGroup.groupA. The physicalIpGroup.groupA and

rangeStart physicalIpGroup.groupB parameters define the IP pool
information. These parameters are applicable only to the OAM network.
physicalIpGroup.groupA. You need to fill in both the rangeStart and rangeEnd
rangeEnd parameters. If the pool consists of only one IP address (IPv4 or IPv6),
use the same value for both.
physicalIpGroup.groupB.
Example:
rangeStart
• 192.168.254.33
• 2001:db8::1
physicalIpGroup.groupB.
rangeEnd

4.5 Fill in the network parameters under the

global.internalE1Network.internalE1 path.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 63

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 21: global.internalE1Network.internalE1 parameters in values-
override.aic-vcu.yaml

Parameter name Description

vlanInfo.vid
This parameter defines the ID for the internale1 VLAN interface.

vlanInfo.vlName
This parameter defines the name for further identification of the VLAN, for
example, in the case of configuring transport separation in the NMS.
The vlanInfo.vlName parameter needs to be the same as the VLAN
interface name in the site configuration file (SCF).

vlanInfo.defaultUnderlyin
gIface This parameter defines the default underlying Ethernet interface for the
corresponding VLAN interface.

vlanInfo.secUnderlyingIfa
ce This parameter defines the secondary underlying Ethernet interface for the
corresponding VLAN interface.

useGroup This parameter defines the group, from which the IP adresses will be used.

ipInfo.subnet This parameter defines the subnet for the internale1 network.

ipInfo.role
This parameter defines the role of the internale1 interface when the
transport separation is configured in the NMS.

ipInfo.ipAddress.groupA.c
pif.rangeStart TheipInfo parameters define the IP pool information.
You need to fill in both the rangeStart and rangeEnd parameters for
ipInfo.ipAddress.groupA.c groupA and groupB.
pif.rangeEnd In case of the blue-green upgrade of the vCU, you need to configure IP
addresses for groupA and groupBas different IP adresses from the same
ipInfo.ipAddress.groupA.c
subnet.
pnrt.rangeStart

ipInfo.ipAddress.groupA.c
pnrt.rangeEnd

ipInfo.ipAddress.groupB.c
pif.rangeStart

ipInfo.ipAddress.groupB.c
pif.rangeEnd

ipInfo.ipAddress.groupB.c
pnrt.rangeStart

ipInfo.ipAddress.groupB.c
pnrt.rangeEnd

lripInternalE1Info.gatewa
yList This parameter defines the gateway list of the IP address.

in the file, including all the spaces. For F1-U, copy the f1u_slice1 example:

64 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
f1uSlice1:

vlanInfo:

vlName: "f1u_slice1"

defaultUnderlyingIface: "extu"

secUnderlyingIface: "extus"

vid: ""

ipInfo:

- rangeStart: ""

rangeEnd: ""

subnet: ""

role:

- "F1-U_slice1"

For S1-U, copy the s1u_slice1 example:

s1uSlice1:

vlanInfo:

vlName: "s1u_slice1"

defaultUnderlyingIface: "extu"

secUnderlyingIface: "extus"

vid: ""

ipInfo:

- rangeStart: ""

rangeEnd: ""

subnet: ""

role:

- "S1-U_slice1"

For NG-U, copy the ngu_slice1 example:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 65

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
nguSlice1:

vlanInfo:

vlName: "ngu_slice1"

defaultUnderlyingIface: "extu"

secUnderlyingIface: "extus"

vid: ""

ipInfo:

- rangeStart: ""

rangeEnd: ""

subnet: ""

role:

- "NG-U_slice1"

- rangeStart: ""

rangeEnd: ""

subnet: ""

role:

- "NG-U_slice1"

Fill in the fields as follows:

66 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 22: Additional network parameters for network slicing under
global.externalNetwork.<network name> in values-override.aic-
vcu.yaml

Parameter name Description

vlanInfo.vid This parameter defines the guest VLAN for the slice. If its value isn't
set, a host VLAN is used.

vlanInfo.vlName This parameter defines the VLAN name used for identifying the
VLAN in the context of configuring transport separation in the NMS.
Examples:
• f1u_slice1
• s1u_slice1
• ngu_slice1

vlanInfo.defaultUnderl This parameter defines the default underlying Ethernet interface for
yingIface the corresponding VLAN interface.

vlanInfo.secUnderlying This parameter defines the secondary underlying Ethernet interface

Iface for the corresponding VLAN interface.

ipInfo.rangeStart TheipInfo parameters define the IP pool information.

You need to fill in both the rangeStart and rangeEnd
parameters. If the pool consists of only one IP address (IPv4 or IPv6),
use the same value for both.
ipInfo.rangeEnd Example:
• 192.168.254.33
• 2001:db8::1
The ipInfo.subnet defines the subnet including a mask.
ipInfo.subnet Example:
• 192.168.254.0/24
• 2001:db8::0/128

ipInfo.role This parameter specifies the role of the interface in the context of
configuring the transport separation in the NMS.
Its value needs to be the same as the value of the IPADDRESSV4
Unique IP address identifier
(uniqueIpAddressIdentifier) parameter or the
IPADDRESSV6 Unique IP address identifier
(uniqueIpAddressIdentifier) parameter for the network in
the SCF.
If there are multiple roles, separate them by space in the SCF.
A role needs to be unique and have the following format: NG-U_X.
X is the dynamic part which can be customized by the operator. The
maximum length for X is 24 and the allowed characters include [A-
Za-z0-9].
Examples:
• F1-U_slice1
• S1-U_slice1
• NG-U_slice1

4.7 [Optional] If you use the Two-Way Active Measurement Protocol (TWAMP), fill in the

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 67

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
additional network parameters.

Note:
This is relevant only if the CB008468: IP Transport Network Measurements
in Cloud RAN feature was activated after the deployment. This feature makes
TWAMP available for all mid- and backhaul interfaces of the vDU and the vCU.
For more information, see the Operating Documentation/AirScale Cloud RAN
BTS Features/CB008468: IP Transport Network Measurements in Cloud
RAN document.

For each interface with the configured TWAMP, copy the example in the file under
global.externalNetwork.twamp_f1c, including all the spaces:

twampF1c:

vlanInfo:

vlName: "twamp_f1c"

defaultUnderlyingIface: "twamp"

secUnderlyingIface: "twamps"

vid: ""

ipInfo:

- rangeStart: ""

rangeEnd: ""

subnet: ""

role:

- "twamp_f1c"

Fill in the fields as follows:

68 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 23: Additional network parameters for interfaces with TWAMP configured under
global.externalNetwork.twamp_f1c in values-override.aic-
vcu.yaml

Parameter name Description

vlanInfo.vid This parameter defines the guest VLAN for TWAMP. If its value is not
set, a host VLAN is used.

vlanInfo.vlName This parameter defines the VLAN name used for identifying the
VLAN in the context of configuring the transport separation in the
NMS.
Allowed value of this parameter is a string, for example:
twamp_f1c

vlanInfo.defaultUnderl This parameter defines the default underlying Ethernet interface for
yingIface the corresponding VLAN interface.

vlanInfo.secUnderlying This parameter defines the secondary underlying Ethernet interface

Iface for the corresponding VLAN interface.

ipInfo.rangeStart TheipInfo parameters define the IP pool information.

You need to fill in both the rangeStart and rangeEnd
parameters. If the pool consists of only one IP address (IPv4 or IPv6),
use the same value for both.
ipInfo.rangeEnd Example:
• 192.168.254.33
• 2001:db8::1
The ipInfo.subnet defines the subnet including a mask.
ipInfo.subnet Example:
• 192.168.254.0/24
• 2001:db8::0/128

ipInfo.role This parameter specifies the role of the interface in the context of
configuring the transport separation in the NMS.
Its value needs to be the same as the value of the IPADDRESSV4
Unique IP address identifier
(uniqueIpAddressIdentifier) parameter or the
IPADDRESSV6 Unique IP address identifier
(uniqueIpAddressIdentifier) parameter for the network in
the SCF.
Allowed value of this parameter is a string, for example:
twamp_ngc

4.8 [Optional] Fill in the vCU autoconnection parameters.

If you use vCU autoconnection, fill in the following parameters. Otherwise leave them
unfilled.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 69

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 24: Parameters for vCU autoconnection under global in values-
override.aic-vcu.yaml

Parameter name Description

siteDescription This parameter defines the unique ID of the vCU. Its value needs to be the same
as the value of the MRBTS AutoConnSiteID parameter specified to identify
the vCU.
Example: MRBTS-1234

urlNMS This parameter defines the URL of the NE3S registration endpoint of the NMS.
Example: http://<NMS_SBI_VIP or
hostname>/NE3S/1.0/NE3SRegistrationNotificationsService

agentIP This parameter defines the external IP address that the NMS uses to connect
back to the vCU. Its value needs to be the same as the vCU OAM IP address,
because the NE3S agent runs in the OAM container.

When you use vCU autoconfiguration, also follow 4.9. [Optional] Configure certificate
management options.

4.9 [Optional] Configure certificate management options.

You need to provide the initial certificate enrolment secrets in the

cmp_secret.yaml and taTrustChain_secret.yaml files. You can find the
files inside the Secret folder of the vCUCNF<version>.zip delivery package.
The parameters in cmp_secret.yaml and taTrustChain_secret.yaml files
are mandatory if you are using the vCU autoconfiguration.

Note:
If you didn't use autoconfiguration, you need to configure these parameters in
CU WebEM after the deployment. For more information on certificate
management, see the Configuring Security in Cloud RAN BTS document.

70 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 25: Parameters for automated certificate management under certman-
auto-cmp.configuration.cmp in values-override.aic-vcu.yaml

Parameter name Description

cmp_secret_name This parameter defines the name of the Kubernetes secret

containing the pre-shared key (PSK) and the reference number
used for connecting to the Certificate Management Protocol
(CMP) server. Its value needs to be the same as the value of the
name parameter in the cmp_secret.yaml file.

additionalTACertSecr This parameter defines the name of the additional trust anchor
etName (TA) certificate secret name. Its value needs to be the same as
the value of the name parameter in the
taTrustChain_secret.yaml file.

ip This parameter defines the CMP server IP address (Pv4 or IPv6).

Example:
• 192.168.254.33
• 2001:db8::1

port This parameter defines the CMP server port.

The allowed value of this parameter is a string, for example:
8080.

path This parameter defines the operator-configured CMP directory.

The allowed value of this parameter is a string, for example:
pkix.

ca_subject_name This parameter defines the subject name of the Certificate

Authority (CA) certificate.
The allowed value of this parameter is a string, for example:
C=PL, O=Common, CN=IPSEC.

ee_subject_name This parameter defines the subject name of the End Entity (EE)
certificate (the certificate of the BTS).
The allowed value of this parameter is a string, for example:
CN=MRBTS-1234.

ee_subject_fqdn This parameter defines the fully qualified domain name (FQDN)
to be set as a subject alternative name for the EE certificate. It
is optional.
The allowed value of this parameter is a list of strings, for
example: mrbts1234.nokia.example.

ee_subject_ip_addr This parameter defines the IP address to be set as a subject

alternative name for the EE certificate. It is optional.
The allowed value of this parameter is a list of strings, for
example: 192.168.254.33.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 71

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 26: Initial certificate enrolment secrets in cmp_secret.yaml

Parameter name Description

name This parameter defines the name of the Kubernetes

secret containing the PSK and the reference number
used for connecting to the CMP server.

psk This parameter defines the CMP server PSK.

refnum This parameter defines the CMP server reference

number.

Table 27: Initial certificate enrolment secrets in taTrustChain_secret.yaml

Parameter name Description

name
This parameter defines the name of the additional TA
certificate secret name.

additional_tacert
This parameter defines the base-64 encoded PEM
format TA trust chain.

Result
You have defined the CNF instance-specific parameters in the values override files. For
instructions on replacing the default parameters with the CNF instance-specific parameters, see
Updating Helm chart configuration values from values override files.

3.4 Filling in the values override files for the vDU

The virtualized gNB distributed unit (vDU) is deployed using Helm charts. Before the deployment,
you need to provide the Helm charts with configuration parameters and information about your
environment. You do this by editing YAML files included in the vDU deployment package.

72 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Purpose
In AirScale Cloud RAN BTS (Cloud RAN BTS), the cloud-native network function (CNF) deployment is
automated using Helm. The details of resource creation and pod deployment are contained in the
Helm charts, included in the CNF deployment package. The Helm charts contain default
configuration values provided by Nokia. You need to provide the CNF instance-specific
configuration override values to the default configuration values by editing the values override
YAML files provided with the Helm charts.

Figure 10: Updating Helm chart configuration values from values override files

In the CNF deployment package, there are three values override files:
values-override.aic-vdu-cluster-preparation.yaml
values-override.aic-vdu-prerequisite.yaml
values-override.aic-vdu.yaml

Before the deployment, you need to fill in the mandatory parameters in the values-
override.aic-vdu.yaml file and all parameters in the remaining files. After the deployment,
you can provide additional parameter values in vDU WebEM.

It's possible to deploy the CNF using autoconfiguration. In such a case, the CNF automatically
downloads the planned configuration from the network management system (NMS) and you don't
need to provide additional information after the deployment. Using autoconfiguration requires
you to provide additional parameter values for autoconnection and certificate managemet in the
values-override.aic-vdu.yaml, as well as the initial certificate enrolment secrets in the
cmp_secret.yaml and taTrustChain_secret.yaml files. You can find the files inside the
Secret folder of the CNF deployment package.

Before you start

Download the vDUCNF<version>.zip software package from Support Portal. For

instructions, see Downloading software packages from SWSt.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 73

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Procedure
1 Extract the values override files.

Extract the following files from the HelmChart folder inside the vDUCNF<version>.zip
package:
values-override.aic-vdu-cluster-preparation.yaml
values-override.aic-vdu-prerequisite.yaml
values-override.aic-vdu.yaml

2 Edit the values-override.aic-vdu-cluster-preparation.yaml file in a text

editor and save the changes.

Table 28: Parameters in values-override.aic-vdu-cluster-preparation.yaml

Parameter name Description

sccName This parameter defines the security context constraints

(SCC) name. It allows administrators to control permissions
for pods.
If the sccName parameter value is set to privileged, a
new SCC isn't created and a privileged SCC is bound to the
serviceaccounts parameter.
If the sccName parameter value isn't set to privileged
or is set to null, a new SCC is created and bound to the
serviceaccounts parameter.
The default value is cnf5g.

userName This parameter defines a user name of an object class (oc)

user. When the userName parameter value is different
from null, roles are added for an oc user so that the vDU
can be deployed.

3 Edit the values-override.aic-vdu-prerequisite.yaml file in a text editor and

save the changes.

3.1 Update the general parameters.

74 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 29: General parameters under global in values-override.aic-vdu-
prerequisite.yaml

Parameter name Description

image.registry This parameter defines the image registry address.

For the Red Hat OpenShift Container Platform (OCP), the default value is
image-registry.openshift-image-registry.svc:5000/{{
.Release.Namespace }}.

nodeSelector This parameter assigns the pods to specific nodes. It's mainly used in the
OCP SNO+1 deployment, where the vDU needs to be deployed on the
worker node. You need to pre-define the node labels in advance.

3.2 Update the network parameters.

Table 30: Network parameters under aic-intnet in values-override.aic-

vdu-prerequisites.yaml

Parameter name Description

<network name>VLanMode This parameter defines the Host VLAN network or the Guest VLAN
network.
Allowed values:
• HOST
• GUEST (default)

VLanID.<network name> This parameter defines the VLAN ID for <network name> network for
the Host VLAN mode. Leave it empty in case of the Guest VLAN
mode.

devicePoolList.fastPath This parameter defines the single-root input/output virtualization (SR-

CommonPool IOV) device pool used by the f1u and bip networks.

devicePoolList.slowPath This parameter defines the SR-IOV device pool used by the
CommonPool operations, administration, and maintenance (OAM), tracing, f1c, fhm,
and twamp networks.

devicePoolList.fastPath This parameter defines the SR-IOV device pool used by l1up networks
RanNicPool (fast path).

devicePoolList.slowPath This parameter defines the SR-IOV device pool used by l1cp networks
RanNicPool (slow path).

3.3 Update the storage parameters.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 75

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 31: Storage parameters in values-override.aic-vdu-
prerequisite.yaml

Parameter name Description

aic-pvc.pvcName This parameter defines the persistent volume claim (PVC)

name. It ensures that each vDU has a unique PVC name.
Allowed values:
• Lowercase alphanumeric characters
•-
•.
The PVC name must start and end with an alphanumeric
character.
Example: vdupvc

global.accessModes This parameter defines the access modes of the persistent

volume.
Allowed values:
• OCP single-node (SNO): ReadWriteOnce
• OCP multi-node (MNO): ReadWriteMany

global.storageClass This parameter defines the storage class name of the

Name persistent volume. If its value isn't specified, the default
storage class is used.
Allowed values:
• For OCP SNO: localfs-lvm-sc
• For OCP MNO: ocs-storagecluster-cephfs

global.restoreData This parameter is used to restore the data, which was

backed up during the PVC creation.
Allowed values:
• true (default)
• false

4 Edit the values_override.aic-vdu.yaml file in a text editor and save the changes.

The values_override.aic-vdu.yaml file has the following structure:

76 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 11: Structure of the values_override.aic-vdu.yaml file

To deploy the vDU, you need to fill in the parameters in the following sections:
global (general parameters, network parameters, autoconnection parameters)
certman-auto-cmp (certificate management configuration parameters)
healing-controller (healing controller parameters)
aic-oamfh (internal fronthaul network DHCP server configuration parameters)
aic-vdu-l2nrt (l2nrt pod configration parameters)
aic-vdu-l2rt (l2rt pod configration parameters)

Additionally, you need to fill in the value of the nodeSelector parameter under the
global section and in all subcharts except for certman-auto-cmp.

The values depend on your environment. For guidance, use the following tables and the
comments inside the file.

4.1 Fill in the general parameters.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 77

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 32: General parameters under global in values-override.aic-
vdu.yaml

Parameter name Description

cnfLayout This parameter defines the deployment type: distributed RAN (D-RAN) or
centralized RAN (C-RAN).
Allowed values:
• DRAN (default). The DRAN value means that the vDU will be deployed in
SNO with vDU only or SNO+1 .
• CRAN. The CRAN value means that the vDU will be deployed in MNO.
• mini. The mini value means that the vDU will be deployed in SNO
together with the mini virtualized gNB distributed unit (vCU) with multi-
tenancy.

coreDumpPath This parameter defines the directory for host path volume to store the
coredump information.

l2nrtCount This parameter defines the number of l2nrt pods to be deployed. The
l2nrtCount parameter value depends on the F1-U throughput.
Supported values range from 0 to 3. The default value is 1.

upInstanceCount This parameter defines the number of ahm or l2rt pods and Nokia Cloud
RAN SmartNICs (RAN NICs) to be deployed.
Supported values range from 1 to 12. The default value is 1.

pvcName This parameter defines the PVC name. Its value needs to be unique for each
vDU, and remain unchanged between the vDU upgrades. It also needs to be
the same as the value of the aic-pvc.pvcName parameter in the
values-override.aic-vdu-prerequisite.yaml file.
Allowed values:
• Lowercase alphanumeric characters
•-
•.
The PVC name must start and end with an alphanumeric character.
Example: vdupvc

storageClassName This parameter defines the storage class name of the persistent volume. Its
value must be the same as the value of the aic-
pvc.storageClassName parameter in the values-override.aic-
vdu-prerequisite.yaml file. If the value isn't specified, the default
storage class is used.
The supported values are:
• For OCP SNO: localfs-lvm-sc
• For OCP MNO: ocs-storagecluster-cephfs

image.registry This parameter defines the image registry address.

Example: image-registry.openshift-image-
registry.svc:5000/{{ .Release.Namespace }}

image.imagePullSecret This parameter defines the name of the Kubernetes secret which stores the
credentials for authentication during the connection to the image registry.
Allowed values are supported secret types. The supported secret types are:
• kubernetes.io/dockercfg
• kubernetes.io/dockerconfigjson

timezone This parameter defines the time zone as a string in a Region/City format.
The default value of this parameter is UTC.
Example:
• Europe/Helsinki
• UTC

78 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Parameter name Description

custom_extensions.labels This parameter defines the custom extensions for labels to be injected into
ConfigMap›Service›Pod resources.
Example: labels: {nf-type: 5g-nf-producer}

seLinux This parameter defines whether the Security-Enhanced Linux (SELinux)

policies are enforced.
If the value of the global.seLinux parameter is set to true, the
SELinux mode is set to enforcing.
If the value of the global.seLinux parameter is set to false, the
SELinux mode is set to permissive. Note that when the seLinux
parameter value is set to enforcing, audit logs are not available.
The allowed value of the global.seLinux parameter is true.

stackTraceEnabled This parameter enables global stack trace collection.

The collection of stack trace needs to be enabled as an alternative for
debugging. It prevents the program from crashing when files (other than
core dump files) are not achievable.
Allowed values:
• true
• false (default)

highPerformanceRunTimeCla This parameter enables Kubernetes RuntimeClass used for high

ss performance.
The default nokia-performance class is installed with OCP provided by
Nokia. Change the value if the deployment is performed on non-Nokia
infrastructure.

4.2 Fill in the l2nrt pod capacity parameters.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 79

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 33: l2nrt pod capacity parameters in values-override.aic-vdu.yaml

Parameter name Description

aic-vdu-l2nrt.deploymentType This parameter defines the deployment type.

Supported values:
• NR_L2NRT_3CL2HI

aic-vdu- This parameter defines whether the hyperthreading is enabled in the Kubernetes
l2nrt.activeSiblingCore cluster.
Allowed values:
• true (default)
• false (only for Nokia internal purposes)

aic-vdu- This parameter defines whether the L2HI container runs with the privileged
l2nrt.l2hi.securityContext.p permission.
rivilegedMode The default value of this parameter is false.

aic-vdu- This parameter enables or disables the dptrace function of the L2HI container.
l2nrt.l2hi.dptrace.enable Allowed values:
• 0 (function disabled - default)
• 1 (function enabled)

aic-vdu- This parameter enables or disables the L2HI container payload dump.
l2nrt.l2hi.dptrace.dump_payl Allowed values:
oad • 0 (function disabled - default)
• 1 (function enabled)

aic-vdu- This parameter defines the configuration of the L2HI dptrace filter.
l2nrt.l2hi.dptrace_filter The parameter value format is <messageID>:<queueID>.
The default value of this parameter is none:none.

4.3 Fill in the l2rt pod capacity parameters.

80 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 34: l2rt pod capacity parameters in values-override.aic-vdu.yaml

Parameter name Description

aic-vdu- This parameter defines the deployment type.

l2rt.deploymentType Supported values:
• NR_L2RT_2CL2PS_2CL2LO for RAN NIC RINLINE1 TDD
• NR_L2RT_4CL2PS_2CL2LO for RAN NIC RINLINE1 FDD
• NR_L2RT_6CL2PS_4CL2LO for RAN NIC RINLINE2 TDD
• NR_L2RT_8CL2PS_4CL2LO for RAN NIC RINLINE2 TDD (default)
• NR_L2RT_1CL2PS_HT_2CL2LO for RAN NIC RINLINE1 TDD or FDD

aic-vdu- This parameter defines whether the hyperthreading is enabled in the

l2rt.activeSiblingCore Kubernetes cluster.
Allowed values:
• true (default)
• false (only for Nokia internal purposes)

global.l2rtL2PSHyperThre This parameter enables a sibling core for the L2PS application.
ading Allowed values:
• true
• false (default)
When the value of thel2rtL2PSHyperThreading parameter is set to
true, the value of the aic-vdu-l2rt.deploymentType parameter
needs to be set to NR_L2RT_1CL2PS_HT_2CL2LO.

aic-vdu- This parameter enables or disables the dptrace function of the L2RT
l2rt.l2rt.dptrace.enable container.
Allowed values:
• 0 (function disabled - default)
• 1 (function enabled)

aic-vdu- This parameter enables or disables the L2RT container payload dump.
l2rt.l2rt.dptrace.dump_p Allowed values:
ayload • 0 (function disabled - default)
• 1 (function enabled)

aic-vdu- This parameter defines the configuration of the L2RT dptrace filter.
l2rt.l2rt.dptrace.filter The parameter value format is <messageID>:<queueID>.
The default value of this parameter is none:none.

4.4 Fill in the healing controller parameters.

Table 35: healing-controller parameters in values-override.aic-

vdu.yaml

Parameter name Description

syncOperatorNamespa This parameter defines the namespace of the Nokia

ce Advanced Synchronization Operator (Nokia
Synchronization Operator).
The default value of this parameter is nokia-sync-
operator.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 81

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
4.5 Fill in the nodeSelector parameter values under global and then under each
subchart (except for the certman-auto-cmp).

Table 36: nodeSelector parameters in values-override.aic-vdu.yaml

Parameter name Description

global.nodeSelecto These parameters assign the pods to specific nodes.

r You need to pre-define the node labels in advance.

<sub
chart>.nodeSelecto
r

4.6 Fill in the network parameters under the global.devicePoolList path.

82 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 37: global.devicePoolList parameters in values-override.aic-
vdu.yaml

Parameter name Description

fastPathCommonPool This parameter defines the SR-IOV device pool used by the f1u
and bip networks.
Its value must be the same as the value of the aic-
intnet.devicePoolList.fastPathCommonPool
parameter in the values-override.aic-vdu-
prerequisite.yaml file.

slowPathFhPool This parameter defines the SR-IOV device pool used by the fhm,
f1c, oam, tracing and twamp network.
Its value must be the same as the value of the aic-
intnet.devicePoolList.slowPathFhPool in the
values-override.aic-vdu-prerequisite.yaml file.

fastPathRanNicPool This parameter defines the SR-IOV device pool used by l1up
networks (fast path).
Its value must be the same as the value of the aic-
intnet.devicePoolList.fastPathRanNicPool
parameter in the values-override.aic-vdu-
prerequisite.yaml file.

slowPathRanNicPool This parameter defines the SR-IOV device pool used by l1cp
networks (slow path).
Its value must be the same as the value of the aic-
intnet.devicePoolList.slowPathRanNicPool
parameter in the values-override.aic-vdu-
prerequisite.yaml file.

4.7 Fill in the network parameters for the fhm network.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 83

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 38: Fhm network parameters in values-override.aic-vdu.yaml

Parameter name Description

fhmSiso This parameter defines the fhm network connectivity mode.

Allowed values:
• direct-connect (fhm VLAN is deployed over RAN NIC)
• switch-network (fhm VLAN is deployed over OAMFH -
default)

fhmInternalNetworkIpP This parameter defines the fhm plane internal network IP pool.
ool You need to set this parameter only if the value of the fhmSiso
parameter is direct-connect.
The IP number should be equal to or higher than the number of
the fhm RAN NICs + 3.
The IP number can't conflict with the subnets of eth0, OCP,
aic-oamfh.dhcp.service.dhcpv4.subnetsForDC,
and global.fhmIpForDC.ipAddress.

fhmIpForDC.ipAddress This parameter defines the fhm master agent IP. You need to set
this parameter only if the value of the fhmSiso parameter is
direct-connect.
The IP number can't conflict with the subnets of eth0, OCP,
aic-oamfh.dhcp.service.dhcpv4.subnetsForDC,
and global.fhmIpForDC.ipAddress.

fhmIpForDC.role This parameter defines the role of the interface when the
transport separation is configured in the NMS.

4.8 Fill in the network parameters under the global.networkInfo.<network

name> path.

Fill in the parameters for the following networks:

fhm
tracing
oam
f1c
bip
fhuc
f1

84 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 39: global.networkInfo.<network name> parameters in values-
override.aic-vdu.yaml

Parameter name Description

mtu This parameter defines the maximum transmission unit

(MTU) of the <network name> network.
Allowed values of this parameter are strings containing
a number. The range is from 1280 to 9500.
The default value is 1500, except for the bip network,
where the default value is 9000.

4.9 Fill in the network parameters under the global.externalNetwork path.

Figure 12: Structure of the global.externalNetwork section in values-

override.aic-vdu.yaml

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 85

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 40: global.externalNetwork.<network name> parameters in
values-override.aic-vdu.yaml

Parameter name Description

vlanInfo.vid This parameter defines the guest VLAN for the interface. If
its value is not specified, a host VLAN is used.
For the l2biprt and l2biphi networks, the host VLAN is not
supported.

vlanInfo.vlName This parameter defines a VLAN name used for identifying

the VLAN in a RAN-sharing setup.
Allowed value of this parameter is a string, for example:
f1uplane

vlanInfo.pcp This parameter defines the priority code point (PCP) for the
VLAN.

ipInfo.rangeStart The ipInfo parameters define the IP pool information.

You need to fill in both the rangeStart and rangeEnd
parameters. If the pool consists of only one IP address (IPv4
or IPv6), use the same value for both.
ipInfo.rangeEnd Example:
• 192.168.254.33
• 2001:db8::1
The ipInfo.subnet defines the subnet including a mask.
ipInfo.subnet Example:
• 192.168.254.0/24
• 2001:db8::0/128

ipInfo.role This parameter defines the role of the interface when

configuring the transport separation in the NMS.
Its value needs to be the same as the value of the
IPADDRESSV4 Unique IP address identifier
(uniqueIpAddressIdentifier) parameter or the
IPADDRESSV6 Unique IP address identifier
(uniqueIpAddressIdentifier) parameter in the SCF.
If there are multiple roles, separate them by space in the
SCF.
Example: F1-U_customname1

policyRouteInfo.gat This parameter defines the gateway IP address. It is

eway applicable only to the OAM network.
Allowed value of this parameter is an IPv4 or IPv6 address,
for example:
• 192.168.254.33
• 2001:db8::1

86 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 41: global.externalNetwork.ahm-<x> parameters in values-
override.aic-vdu.yaml

Parameter name Description

fhuc.vlName This parameters define the interface list for the fhuc under the
RAN NIC on the node with the running ahm-<x> pod. The x
value can range from 0 to 11.
fhuc.defaultUnderlyin
Example:
gIface
fhuc:
- vlName: "fhucplane01"
defaultUnderlyingIface: "ecpri0"
fhuc.vid vid: "301"
pcp: "7"

fhuc.pcp The value of the fhuc.vlName parameter must be unique

and needs to include the fhuc prefix.

fhm.vlName This parameters define the interface list for the fhm under the
RAN NIC on the node with the running ahm-<x> pod, when the
value of the fhmSiso parameter is set to direct-connect.
fhm.defaultUnderlying The x value can range from 0 to 11.
Iface Example:
fhm:
- vlName: "fhmplane01"
defaultUnderlyingIface: "ecpri0"
vid: ""
fhm.vid
The value of the fhm.vlName parameter must be unique and
needs to include the fhm prefix.

"

role:

- "F1-U_slice1"

Modify the f1Slice1 section key name in each copy, for example f1uSlice2 and
so on, and fill in the fields as follows:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 87

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 42: Additional network parameters for network slicing for the F1-U interface
under global.externalNetwork.f1u_slice<slice number>in values-
override.aic-vdu.yaml

Parameter name Description

vlanInfo.vid This parameter defines the Guest VLAN for the F1-U
slice. If its value isn't set, a host VLAN is used.

vlanInfo.vlName This parameter defines the VLAN name used for

identifying the VLAN when configuring transport
separation in the NMS.
Allowed value of this parameter is a string, for example:
f1u_slice1.

ipInfo.rangeStart TheipInfo parameters define the IP pool information.

You need to fill in both the rangeStart and
rangeEnd parameters. If the pool consists of only one
IP address (IPv4 or IPv6), use the same value for both.
ipInfo.rangeEnd Example:
• 192.168.254.33
• 2001:db8::1
The ipInfo.subnet defines the subnet including a
mask.
ipInfo.subnet
Example:
• 192.168.254.0/24
• 2001:db8::0/128

ipInfo.role This parameter defines the role of the interface when

configuring the transport separation in the NMS.
Its value needs to be the same as the value of the
IPADDRESSV4 Unique IP address
identifier (uniqueIpAddressIdentifier)
parameter or the IPADDRESSV6 Unique IP
address identifier
(uniqueIpAddressIdentifier) parameter for
the network in the SCF.
If there are multiple roles, separate them by space in
the SCF.
Example: F1-U_customname1

4.11 [Optional] If you use the Two-Way Active Measurement Protocol (TWAMP), fill in the
additional network parameters.

88 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
This is relevant only if the CB008468: IP Transport Network Measurements
in Cloud RAN feature was activated after the deployment. This feature makes
TWAMP available for all mid- and backhaul interfaces of the vDU and the vCU.
For more information, see the Operating Documentation/AirScale Cloud RAN
BTS Features/CB008468: IP Transport Network Measurements in Cloud
RAN document.

For each interface with the configured TWAMP, copy the example in the file under
global.externalNetwork.twamp_f1c, including all the spaces:

twampF1:

vlanInfo:

# vlName should be set the same as the VLAN interface name in SCF

vlName: "twamp_f1"

defaultUnderlyingIface: "twamp"

vid: ""

ipInfo:

- rangeStart: ""

rangeEnd: ""

subnet: ""

type: "physical"

role:

- "twamp_f1"

Modify the twampF1 section key name in each copy, for example, twamp_ng,
twamp_f1c, and similarly. Fill in the fields as follows:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 89

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 43: Additional network parameters for interfaces with TWAMP configured under
global.externalNetwork.twamp_<interface> in values-
override.aic-vdu.yaml

Parameter name Description

vlanInfo.vid Guest VLAN for TWAMP for the <interface>

interface.

vlanInfo.vlName VLAN name used for identifying the VLAN in the SCF.
Allowed value is a string, for example: twamp_f1

ipInfo.rangeStart IP pool information. You need to fill in both the

rangeStart and the rangeEnd parameters. If the
pool consists of only one IP address (IPv4 or IPv6), use
the same value for both.
ipInfo.rangeEnd
Example:
• 192.168.254.33
• 2001:db8::1
ipInfo.subnet Subnet including mask. Example:
• 192.168.254.0/24
• 2001:db8::0/128

ipInfo.role This parameter specifies the role of the interface in the

context of configuring the transport separation in the
NMS.
Its value needs to be the same as the value of the
IPADDRESSV4 Unique IP address
identifier (uniqueIpAddressIdentifier)
parameter or the IPADDRESSV6 Unique IP
address identifier
(uniqueIpAddressIdentifier) parameter for
the network in the SCF.
Allowed value of this parameter is a string, for example:
twamp_ngc

4.12 [Optional] Fill in the vDU autoconnection parameters.

If you use the vDU autoconnection, also fill in the following parameters. Otherwise
leave them unfilled.

90 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 44: Parameters for vDU autoconnection under global in values-
override.aic-vdu.yaml

Parameter name Description

siteDescription This parameter defines the unique ID of the vDU. Its value needs to be the same
as the value of the MRBTS AutoConnSiteID parameter specified to identify
the vDU.
Example: MRBTS-1234

urlNMS This parameter defines the URL of the NE3S registration endpoint of the NMS.
Example: http://<NMS_SBI_VIP or
hostname>/NE3S/1.0/NE3SRegistrationNotificationsService

agentIP This parameter defines the external IP address that the NMS uses to connect
back to the vDU. Its value needs to be the same as the vDU OAM IP address,
because the NE3S agent runs in the OAM container.

When you use the vDU autoconfiguration, also follow 4.13. [Optional] Configure
certificate management options.

4.13 [Optional] Configure certificate management options.

You need to provide the initial certificate enrolment secrets in the

cmp_secret.yaml and taTrustChain_secret.yaml files. You can find the
files inside the Secret folder of the vCUCNF<version>.zip delivery package.
The parameters in cmp_secret.yaml and taTrustChain_secret.yaml files
are mandatory if you are using the vDU autoconfiguration.

Note:
If you didn't use autoconfiguration, you need to configure these parameters in
vDU WebEM after the deployment. For more information on certificate
management, see the Configuring Security in Cloud RAN BTS document.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 91

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 45: Parameters for automated certificate management under certman-
auto-cmp.configuration.cmp in values-override.aic-vdu.yaml

Parameter name Description

cmp_secret_name This parameter defines the name of the Kubernetes secret

containing the pre-shared key (PSK) and the reference number
used for connecting to the Certificate Management Protocol
(CMP) server. Its value needs to be the same as the value of the
name parameter in the cmp_secret.yaml file.

additionalTACertSecr This parameter defines the name of the additional trust anchor
etName (TA) certificate secret name. Its value needs to be the same as
the value of the name parameter in the
taTrustChain_secret.yaml file.

ip This parameter defines the CMP server IP address (Pv4 or IPv6).

Example:
• 192.168.254.33
• 2001:db8::1

port This parameter defines the CMP server port.

The allowed value of this parameter is a string, for example:
8080.

path This parameter defines the operator-configured CMP directory.

The allowed value of this parameter is a string, for example:
pkix.

ca_subject_name This parameter defines the subject name of the Certificate

Authority (CA) certificate.
The allowed value of this parameter is a string, for example:
• C=PL
• O=Common
• CN=IPSEC

ee_subject_name This parameter defines the subject name of the End Entity (EE)
certificate (the certificate of the BTS).
The allowed value of this parameter is a string, for example:
CN=MRBTS-1234.

ee_subject_fqdn This parameter defines the fully qualified domain name (FQDN)
to be set as a subject alternative name for the EE certificate. It
is optional.
The allowed value of this parameter is a list of strings, for
example: mrbts1234.nokia.example.

ee_subject_ip_addr This parameter defines the IP address to be set as a subject

alternative name for the EE certificate. It is optional.
The allowed value of this parameter is a list of strings, for
example: 192.168.254.33.

92 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 46: Initial certificate enrolment secrets in cmp_secret.yaml

Parameter name Description

name This parameter defines the name of the Kubernetes

secret containing the PSK and the reference number
used for connecting to the CMP server.

psk This parameter defines the CMP server PSK.

refnum This parameter defines the CMP server reference

number.

Table 47: Initial certificate enrolment secrets in taTrustChain_secret

Parameter name Description

name This parameter defines the name of the additional TA

certificate secret name.

additional_tacert This parameter defines the base-64 encoded PEM

format TA trust chain.

4.14 Configure the Dynamic Host Configuration Protocol (DHCP) server options for the
fronthaul network.

The radio units (RUs) use the DHCP server to obtain their IP addresses and identify the
vDU. You can use either an internal DHCP server located in the vDU, or an external
DHCP server located in the operator environment. For more information, see DHCP
process in the Configuring Cloud RAN BTS Transport document.

When the internal vDU DHCP server is enabled, you need to fill in the following
parameters:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 93

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 48: Parameters for the vDU internal fronthaul network DHCP server under aic-
oamfh.dhcp.service in values-override.aic-vdu.yaml

Parameter name Description

dhcpv4.subnets.pools.sta The dhcpv4.subnets.pools parameters define the IP pool

rtAddress information.
The startAddress and endAddress parameters define the actual
dhcpv4.subnets.pools.end part of the subnet that is governed by the DHCP server.
Address Example: 192.168.254.33
The dhcpv4.subnets.subnet parameter defines the subnet which
includes the mask.
dhcpv4.subnets.subnet
Example: 192.168.254.0/24

dhcpv4.subnets.data.clie This parameter defines a list of client identifiers for the RUs in the
ntIdentifier <product code>/<serial number> format. If left empty, the
DHCP server doesn't check the client identifier part of the DHCP packets
(DHCP option 61).
The allowed value is a list of strings, for example:
clientIdentifier:
- "753/001"
- "753/002"
- "753/003"
- "755/001"
- "755/002"
This parameter is optional.

service.dhcpv4.subnetsFo This parameter defines the subnets used when the value of the
rDC.subnet fhmSiso parameter is set to direct-connect.

service.dhcpv4.subnetsFo This parameter defines the interface type.

rDC.type Allowed values:
• CPRI
• eCPRI

Result
You have defined the CNF instance-specific parameters in the values override files. For
instructions on replacing the default parameters with the CNF instance-specific parameters, see
Updating Helm chart configuration values from values override files.

Postrequisites
Before deploying the vDU, you need to deploy the Nokia proprietary Kubernetes operators for
Cloud RAN BTS:

RAN NIC Software Controller, which controls and handles the life cycle management (LCM)
operations of the RAN NICs.
Nokia Advanced Synchronization Kubernetes Operator (Nokia Synchronization Operator), which
provides the Precision Time Protocol (PTP) time reference for the vDU.

94 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
The software packages of Nokia proprietary Kubernetes operators for Cloud RAN BTS have
separate values override YAML files that you need to fill in to override the default configuration
values. For instructions, see Filling in the values override files for the Nokia proprietary Kubernetes
operators for Cloud RAN BTS.

3.5 Filling in the values override files for the Nokia

proprietary Kubernetes operators for Cloud RAN BTS

The Nokia proprietary Kubernetes operators for AirScale Cloud RAN BTS (Cloud RAN BTS) are
deployed using Helm charts. Before the deployment, you need to provide the Helm charts with
configuration parameters and information about your environment. You do this by editing YAML
files included in the operator deployment package.

Purpose
The Nokia proprietary Kubernetes operators for Cloud RAN BTS hold specific functions related to
the virtualized gNB distributed unit (vDU) operations:
Nokia Cloud RAN SmartNIC (RAN NIC) Software Controller oversees and handles the life cycle
management (LCM) operations of RAN NICs.
Nokia Advanced Synchronization Kubernetes Operator (Nokia Synchronization Operator)
provides the Precision Time Protocol (PTP) time reference for the vDU.

The operators have a structure similar to the cloud-native network functions (CNFs), and their
deployment is automated using Helm. Resource creation and pod deployment details are in the
Helm charts included in the operator deployment package. The Helm charts contain default
configuration values of the mandatory parameters. You need to provide the CNF instance-specific
configuration override values to the default configuration values by editing the values override
YAML files provided with the Helm charts.. After the deployment, you can provide additional
parameter values in vDU WebEM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 95

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 13: Updating Helm chart configuration values from values override files

Note:
The virtualized gNB central unit (vCU) and the vDU deployment packages contain three
value override files. The operator deployment packages contain a single value override file.

Note:
You need to deploy the operators in their own namespaces on the same Red Hat
OpenShift Container Platform (OCP) cluster as the vDU. You need to deploy the operators
before deploying the vDU.

Before you start

Download the operator software packages from Support Portal. For instructions, see
Downloading software packages from SWSt.

Note:
You need to perform the procedure separately for each operator.

Procedure
1 Extract the values override file for the selected operator.

Use:
ran-nic-sw-controller<version>.zip for RAN NIC Software Controller.
nokia-sync-operator<version>.zip for Nokia Synchronization Operator.

96 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
2 Open the value override file in a text editor and fill in the parameters specific to your
configuration.

Step example

Table 49: Parameters in ran-nic-sw-controller.yaml

Parameter name Description

image.registry This parameter defines the image registry address.

Example: image-registry.openshift-image-
registry.svc:5000/{{ .Release.Namespace }}

sccName This parameter defines the security context constraints (SCC) name. It
allows administrators to control permissions for pods.
If the sccName parameter value is set to privileged, a new SCC isn't
created and a privileged SCC is bound to the serviceaccounts
parameter.
If the sccName parameter value isn't set to privileged or is set to
null, a new SCC is created and bound to the serviceaccounts
parameter.

Step example
Example of the RAN NIC Software Controller values override file:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 97

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
# Default values for ran-nic-sw-controller.

# This is a YAML-formatted file.

# Declare variables to be passed into your templates.

image:

registry:

pullPolicy: IfNotPresent

controller:

repository: "controller"

tag: "2.2.1"

labeler:

repository: "labeler"

tag: "2.2.1"

agent:

repository: "agent"

tag: "2.2.1"

tftp-init:

repository: "tftp-init-container"

tag: "2.2.1"

tftp:

repository: "tftp"

tag: "2.2.1"

dhcp:

repository: "tftp-dhcp-container"

tag: "2.2.1"

# description: SecurityContextConstraints name. It will allow administrators to

control permissions for pods.

# if sccName is "privileged", it won't create a new SCC, only bind privileged SCC

to serviceaccounts.

# if sccName isn't "privileged", it will create a new SCC and bind new SCC to

serviceaccounts.

# default value is "privileged" and the value should not be empty

sccName: "privileged"

98 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step example

Table 50: Parameters in nokia-sync-operator.yaml

Parameter name Description

global.image.registry This parameter defines the image registry address.

Example: image-registry.openshift-image-
registry.svc:5000/{{ .Release.Namespace }}

global.timezone This parameter defines the time zone as a string in a Region/City format.
The default value of this parameter is UTC.
Example:
• Europe/Helsinki
• UTC

Step example
Example of the Nokia Synchronization Operator values override file:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 99

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
# - Override values for deployment in cloud-development environment

# - Operator need to set the values base on the real scenario.

# - This is a YAML-formatted file.

# - Declare variables to be passed into your templates.

global:

provisioner: Prometheus

image:

registry: image-registry.openshift-image-registry.svc:5000/{{

.Release.Namespace }}

timezone: UTC

provisionerSpecific:

Prometheus:

authorization:

kind: ClusterRole

name: cluster-monitoring-view

dataSource:

endpoint:

https://prometheus-k8s.openshift-monitoring.svc.cluster.local:9091

3 Save the changes and close the editor.

Result
You have defined the CNF instance-specific parameters in the values override files. For
instructions on replacing the default parameters with the CNF instance-specific parameters, see
Updating Helm chart configuration values from values override files.

100 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
4. Deploying cloud infrastructure

You need to install Red Hat OpenShift Container Platform (OCP) on hardware servers to provide a
Container-as-a-Service (CaaS) framework for the deployment of the cloud-native network
functions (CNFs) of the AirScale Cloud RAN BTS (Cloud RAN BTS).

Figure 14: Overview of the OCP deployment

CSR cell site router

FHGW Nokia AirFrame Fronthaul Gateway

NIC network interface card

Nokia Sync Operator Nokia Advanced Synchronization Operator

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 101

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
RAN NIC Nokia Cloud RAN SmartNIC

RU radio unit

vCU virtualized gNB central unit

vDU virtualized gNB distributed unit

In Cloud RAN BTS, the CNFs are deployed on the cloud infrastructure using Kubernetes containers,
organized into pods. Containers are a type of software that can virtually package and isolate
applications. This way, the applications can share access to an operating system without the need
for a virtual machine (VM).

To prepare the cloud infrastructure for the CNF deployment, you need to install and configure the
CaaS framework on the hardware servers. In Cloud RAN BTS the CaaS framework is provided by
OCP.

For detailed information on the supported hardware configurations, see Reference

Documentation/AirScale Cloud RAN BTS Supported Configurations.

Preparing the deployment of cloud infrastructure

Before deploying the cloud infrastructure on the hardware servers, you need to:
1. Create an edge data center plan using Nokia Edge Automation Tool (NEAT) Planner application.
The NEAT Planner provides an MS Excel-based graphical user interface (GUI), which guides you
through the process of creating a new edge data center plan file. You can create plans based
on Nokia blueprints and user-defined site templates. The created edge data center plan is later
imported to NEAT and used as a data source for NEAT workflows. For instructions, see
Planning workflow in Operating Documentation/Nokia Edge Automation Tool/Operations
and Maintenance/Operating NEAT Planner Application.
2. Install the hardware infrastructure at their destination sites according to the edge data center
plan.
3. Configure and commission the networking for the installed hardware. You can either do this
manually using Nokia AirFrame Data Center Manager (NADCM) or automatically, using NEAT
workflows. For instructions, see Deploying an automatic edge data center with NEAT
workflows in Operating Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating and Maintaining NEAT.
4. Integrate NEAT with central container registry (CCR). For more information, see Operating

102 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Documentation/Nokia Edge Automation Tool/Operations and Maintenance/Operating and
Maintaining NEAT.
5. Onboard the cloud infrastructure installation package to the container registry, from which it is
accessed during the installation. For instructions, see Preparing the Nokia Red Hat OCP
release installation in Operating Documentation/AirScale Cloud RAN BTS
System/Operation/Deploying and Operating Nokia Red Hat OCP.
6. Onboard the edge data center plan to NEAT. For instructions, see Providing plans for NEAT in
Operating Documentation/Nokia Edge Automation Tool/Operations and
Maintenance/Operating NEAT Planner Application.

Deployment of cloud infrastructure

The cloud infrastructure is deployed using NEAT workflows. After completing the preparation,
follow the instructions in Cloud infrastructure deployment in edge data centers in Operating
Documentation/AirScale Cloud RAN BTS System/Operation/Deploying and Operating Nokia
Red Hat OCP.

Note:
The OCP host configuration is defined in the edge data center plan.

Notice:
Cloud RAN BTS supports CNF scale-out. The possibility of CNF scale-out when the CNF is
operational is subject to available cloud infrastructure resources. During initial cloud
infrastructure deployment and its initial capacity planning, Nokia recommends to consider
the following:
Failover capacity according to the CNF requirements
Additional capacity required for cloud infrastructure and CNF maintenance
Additional capacity to address expected network and traffic-related growth

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 103

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
5. Deploying and commissioning FHGW

You need to deploy and commission Nokia AirFrame Fronthaul Gateway (FHGW) at the virtualized
distributed unit (vDU) site to ensure connectivity between the vDU and the radio units (RUs),
Ethernet switching, radio connection aggregation, and synchronization of the connected RUs.

Purpose

Note:
The following procedure presents a high-level overview of the FHGW deployment,
integration, and commissioning process. For complete instructions, refer to the documents
listed in the procedure.

Figure 15: Overview of the FHGW deployment with the MantaRay NM Plug and Play (PnP) method

104 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
CaaS Container-as-a-Service

CM Configuration Management

CNF cloud-native network function

CSR cell site router

NIC network interface card

NADCM Nokia AirFrame Data Center Manager

NEAT Nokia Edge Automation Tool

Nokia Sync Operator Nokia Advanced Synchronization Operator

OCP Red Hat OpenShift Container Platform

RAN NIC Nokia Cloud RAN SmartNIC

SWM Software Management

In AirScale Cloud RAN BTS (Cloud RAN BTS), FHGW provides connectivity from the vDU to the
Common Public Radio Interface (CPRI) RUs, because direct CPRI connectivity from the
commercially available servers isn't possible in the cloud environment. The vDU uses Enhanced
CPRI (eCPRI), and FHGW uses CPRI towards the RUs.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 105

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 16: Cloud RAN BTS elements interacting with FHGW

NE network element

OAM Operations, Administration, and Maintenance

For more information on the FHGW in Cloud RAN BTS, see Operating Documentation/Cloud RAN
BTS System/Integrate and configure/Cloud RAN BTS Site Solution and Operating
Documentation/Nokia AirFrame Fronthaul Gateway/Integrate and configure/FHGW
characteristics for Cloud RAN BTS site solution.

The FHGW can be deployed using the following methods:

NEAT workflows using PnP method and Preboot Execution Environment (PXE) method
PnP installation and configuration with MantaRay NM

PnP installation and configuration with MantaRay NM is the default FHGW installation method for
Cloud RAN BTS. The procedure consists of the following main parts:
Manual preparing of the FHGW PnP configuration with NADCM and NEAT.
Integrating the FHGW with a network management system (NMS) using MantaRay NM.
Configuring the FHGW functionality with the configuration plan using MantaRay NM.

106 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
This high-level procedure describes the FHGW PnP installation method, where NEAT is used
for pre-planning and configuration of FHGW, and the installation is performed by MantaRay
NM. Alternatively, you can deploy the FHGW with the PXE method using the fhgw-
deployment workflow in NEAT. For more information, see the FHGW deployment
workflow chapter in Operating Documentation/Nokia Edge Automation Tool/Operating
and Maintaining NEAT.

Before you start

Make sure that:

the hardware is delivered to the destination site.
MantaRay NM is installed in the network.
NADCM is installed in the network.
NEAT is installed in the network.
IPv4 and IPv6 are configured. For instructions, see Configuring Radio Network Elements with
Plug and Play in MantaRay NM Operating Documentation.
Firewall is configured. For instructions, see Configuring Radio Network Elements with Plug
and Play in MantaRay NM Operating Documentation.
FHGW certificates are configured. For instructions, see Configuring Radio Network Elements
with Plug and Play in MantaRay NM Operating Documentation.
MantaRay NM certificates are configured. For instructions, see Configuring Radio Network
Elements with Plug and Play in MantaRay NM Operating Documentation.
Transport Layer Security (TLS) is configured. For instructions, see Configuring Radio Network
Elements with Plug and Play in MantaRay NM Operating Documentation.
the FHGW software package is imported to MantaRay NM. For instructions, see Onboarding
software packages to MantaRay NM.

Procedure
1 Install FHGW together with the vDU hardware servers at the far edge or cell site.

2 In NEAT Planner Application, prepare an edge data center plan, including FHGWs.

For instructions, see the Planning workflow chapter in the Operating Documentation/Nokia
Edge Automation Tool/Operations and Maintenance/Operating NEAT Planner Application
document.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 107

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Tip:
You need to create the edge data center plan before deploying Red Hat OpenShift
Container Platform (OCP) on the servers target for installation of the cloud-native
network functions (CNFs). Skip this step if you have already created the edge data
center plan.

3 Import the edge data center plan to NEAT.

For instructions, see the Adding a new edge data center chapter in the Operating
Documentation/Nokia Edge Automation Tool/Operations and Maintenance/Operating and
Maintaining NEAT document.

Tip:
You need to import the edge data center plan to NEAT before deploying OCP on the
servers target for installation of the CNFs. Skip this step if you have already imported
the edge data center plan to NEAT.

4 In NEAT, run the discover-edgedc-hw workflow to scan the edge data center hardware,
including FHGW, to the NADCM hardware inventory.

For instructions, see Operating Documentation/Nokia Edge Automation Tool/Operations

and Maintenance/Operating and Maintaining NEAT.

Note:
Instead of using the discover-edgedc-hw workflow, you can manually add FHGW
hardware to the NADCM hardware inventory using the NADCM graphical user interface
(GUI). For instructions, see Operating Documentation/Nokia AirFrame Data Center
Manager/Operations and Maintenance//Operating and Maintaining
NADCM/Managing data center layout/Adding new hardware.

5 In NEAT, run the fhgw-pnp-ucf-deployment workflow to provide the needed MantaRay

NM connection details to the FHGW and generate the FHGW RAML configuration files.

For instructions, see Operating Documentation/Nokia Edge Automation Tool/Operations

108 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
and Maintenance/Operating and Maintaining NEAT.

Note:
Before running the fhgw-pnp-ucf-deployment workflow, make sure that the
FHGW device is present in the NADCM hardware inventory.

Step result
The fhgw-pnp-ucf-deployment workflow produces three artifacts:
fhgw-user-config-pnp.yaml, which is not used in the later steps of the procedure
FHGW-124220-TL2_raml_autoconn.xml
FHGW-124220-TL2_raml.xml

You can access the generated files in the NEAT GUI under Edge Data Center
Inventory›ARTIFACTS›INITIAL SWITCH CONFIG.

6 Save the FHGW-124220-TL2_raml_autoconn.xml and FHGW-124220-

TL2_raml.xml files to your local computer.

7 Add information about the Maintenance Region (MR) for the FHGW Managed Object (MO) to
the FHGW-124220-TL2_raml_autoconn.xml file.

7.1 Open the FHGW-124220-TL2_raml_autoconn.xml file in a text editor.

7.2 Fill in the values of the maintenanceRegionId and maintenanceRegionCId

parameters under the FHGW MO.

7.3 Save the changes and close the file.

8 Start the FHGW PnP procedure in MantaRay NM.

For instructions, see Configuring Radio Network Elements with Plug and Play in MantaRay
NM Operating Documentation.

During the FHGW PnP procedure, use the prepared FHGW-124220-

TL2_raml_autoconn.xml configuration file as an autoconnection plan. You can
configure additional transport and radio parameters using the MantaRay NM GUI.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 109

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
The autoconnection plan is activated and MantaRay NM performs offline validation of the
FHGW configuration.

9 Start FHGW to automatically integrate it with MantaRay NM.

During the integration process:

the target-embedded software for FHGW is pulled from MantaRay NM and updated.
the FHGW receives the configuration data from MantaRay NM.

For more information, see Configuring Radio Network Elements with Plug and Play in
MantaRay NM Operating Documentation

and Operating Documentation/Nokia AirFrame Fronthaul Gateway/Install/Installing

software using Plug and Play.

10 To complete the FHGW configuration, import and provision the FHGW-124220-

TL2_raml.xml file to the FHGW in MantaRay NM.

For instructions, see Configuring Radio Network Elements with Plug and Play in MantaRay
NM Operating Documentation.

Notice:
To successfully complete the FHGW configuration, you need to import the
FHGW-124220-TL2_raml.xml file after completing the PnP procedure and
uploading the FHGW object topology to MantaRay NM.

110 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
6. Preparing CNF deployment in MantaRay NM

Before you can deploy the cloud-native network functions (CNFs) with MantaRay NM, you need to
set the correct permissions, integrate MantaRay NM with central container registry (CCR), install a
fast pass package for the current AirScale Cloud RAN BTS (Cloud RAN BTS) software version,
integrate the cloud instance with MantaRay NM, and prepare a CNF deployment plan.

6.1 Configuring MantaRay NM for Cloud RAN BTS life cycle

management operations

You need to configure Domain Name Server (DNS), firewall settings, and central container registry
(CCR), and set the correct permissions before you can perform any AirScale Cloud RAN BTS (Cloud
RAN BTS) life cycle management (LCM) operations in MantaRay NM.

MantaRay NM DNS configuration

To manage Cloud RAN BTS in MantaRay NM, you need to configure the DNS forwarding. It enables
communication between MantaRay NM and the Red Hat OpenShift Container Platform (OCP)
instance, which hosts the cloud-native network function (CNF), as the OCP instance is managed by
a DNS different than the MantaRay NM internal DNS.

For instructions, see the Configuring forwarder in MantaRay NM DNS chapter under the
Administering DNS category in MantaRay NM Operating Documentation.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 111

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
MantaRay NM firewall configuration
You need to configure the following rules of the MantaRay NM firewall to allow connections to
Kubernetes API endpoints and to the external DNS.

Table 51: MantaRay NM permissions specific for the Cloud RAN BTS LCM operations

Source Source port Destination Destination AL TL Service object

port

DNS Ephemeral External- 53 DNS TCP/UDP DNS

DNS

LCM Ephemeral External- 6443 HTTPS TCP/UDP https

K8S-API

For more information, see the Configuring Firewall for MantaRay NM chapter under the
Administering MantaRay NM System Security category in MantaRay NM Operating
Documentation.

CCR configuration
CCR is an Open Container Initiative (OCI) compliant registry which provides storage and content
delivery system for OCI artifacts. The content stored in the CCR is available:
for direct use by Kubernetes, which controls the applications running in Container as a Service
(CaaS) clusters.
for indirect use by distributed container registries closer to the Kubernetes cluster, which
controls the applications running in CaaS clusters.

Before you can push software images to the CCR, you need to configure it and integrate it with
MantaRay NM. For more information, see Configuring and integrating CCR with MantaRay NM.

NEAT integration with MantaRay NM

You need to integrate Nokia Edge Automation Tool (NEAT) with MantaRay NM to enable the cloud
instance integration and deintegration operations in MantaRay NM. For more information, see
Integrating NEAT with MantaRay NM.

112 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Permissions for Cloud RAN BTS LCM operations in MantaRay NM
All Cloud RAN BTS LCM operations require setting the correct permissions for a MantaRay NM user
in the MantaRay NM graphical user interface (GUI) and CLI.

Table 52: MantaRay NM permissions specific for the Cloud RAN BTS LCM operations

Default role name Permission object Permission operation

Lifecycle Management Lifecycle Management Lifecycle Management

of Cloud-Native of Cloud-Native of Cloud-Native
Network Functions Network Functions Network Functions
Operations

For general information on roles and permissions in MantaRay NM, see the Default roles and
permissions chapter under the Permission Management Help category in MantaRay NM
Operating Documentation.

For instructions on creating users, see the Creating users chapter under the User Management
Help category in MantaRay NM Operating Documentation.

6.1.1 Configuring and integrating CCR with MantaRay NM

You need to configure and integrate the central container registry (CCR) with MantaRay NM to
enable the possibility of the Open Container Initiative (OCI) software image distribution.

Purpose

Note:
The following procedure presents a high-level overview of the CCR configuration and
integration process. For complete instructions, see the following documents:
Administering Central Container Registry in MantaRay NM Operating Documentation
for CCR configuration
Integrating Container Registry to MantaRay NM in MantaRay NM Operating
Documentation for CCR integration with MantaRay NM

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 113

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
In AirScale Cloud RAN BTS (Cloud RAN BTS) life cycle management (LCM) operations, CCR provides
a storage and content delivery system for OCI artifacts, including RedHat OpenShift Container
Platform (OCP) images, and cloud-native network function (CNF) images.

During the installation of MantaRay NM, CCR is installed as a container service on Compute1
virtual machine (VM), which is an optional VM for the MantaRay NM . After the CCR is installed,
configured, and integrated with MantaRay NM, you can use MantaRay NM to automatically
onboard the CNF software images to the CCR.

Figure 17: CCR configuration and integration process

Note:
Instead of the CCR in MantaRay NM, you can use an external container registry and
integrate it to MantaRay NM. For more information, see Integrating Container Registry to
MantaRay NM in MantaRay NM Operating Documentation.

Before you start

Make sure that you have installed MantaRay NM and that the CCR is successfully installed on the
Compute1 VM. For instructions, see Checking Central Container Registry service status under
Administering Central Container Registry in MantaRay NM Operating Documentation.

Procedure
1 Open the CCR user interface (UI) in a web browser.

Step example

114 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
https://<FQDN of the Compute1 VM>:8443/

You can obtain the fully qualified domain name (FQDN) of the MantaRay NM load balancer or
MantaRay NM IP addresses for a VM, where the CCR is running, by following Locating the
right virtual machine for a service under Integration/Integrating Juniper Elements to
MantaRay NM/Preparation before integration/Prerequisites for MantaRay NM in
MantaRay NM Operating Documentation.

2 Log in to the CCR UI using the default user name ccradmin and the CCR admin password.

You can retrieve the password by running the following command:

/opt/nokia/oss/bin/syscredacc.sh -user ccradmin -type DB -instance CCR

3 Configure and prepare the CCR for integration with MantaRay NM.

3.1 Create separate projects in the CCR for the OCP and CNF software images.

For instructions, see Creating project under Administering Central Container

Registry in MantaRay NM Operating Documentation.

Note:
By default, all Cloud RAN BTS software images automatically onboarded into
the CCR are stored under the same project. However, Nokia recommends
configuring separate projects for OCP and CNF software artifacts, by modifying
the software onboarding operation plan in MantaRay NM. For more information
on the software onboarding operations in MantaRay NM, see Onboarding
software images to the container registry.

3.2 Create a robot account in the CCR.

Robot account is used by the OCP clusters Kubernetes operations for fetching
software images from the CCR.

For instructions, see Creating robot account under Administering Central Container
Registry in MantaRay NM Operating Documentation.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 115

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
If needed, you can change the robot account password. The changed robot
account password should follow the Network Element Access Control (NEAC)
policy for External Service Access. For instructions, see Changing the password
of the robot account under Administering Central Container Registry in
MantaRay NM Operating Documentation.

Step result
After creating a project and a robot account you can manually push and pull objects to the
container registry using curl commands. For instructions, see Pulling/pushing of artifacts
under Administering Central Container Registry in MantaRay NM Operating
Documentation.

4 Prepare MantaRay NM for integration with the CCR.

For instructions, see Preparing MantaRay NM for Container Registry integration under
Integrating Container Registry to MantaRay NM in MantaRay NM Operating
Documentation.

5 Set up the firewall rules for the CCR.

For instructions, see Setting up firewall rules under Integrating Container Registry to
MantaRay NM/Preparing the intermediate system in MantaRay NM Operating
Documentation.

6 Integrate the CCR with MantaRay NM.

6.1 Create the CONTAINER_REGISTRY managed object (MO).

For instructions, see Creating CONTAINER_REGISTRY managed object under

Integrating Container Registry to MantaRay NM/Integrating Container Registry in
MantaRay NM Operating Documentation.

6.2 Create the CONTAINER_DOCKER_API MO.

For instructions, see Creating CONTAINER_DOCKER_API managed object under

Integrating Container Registry to MantaRay NM/Integrating Container Registry in
MantaRay NM Operating Documentation.

6.3 [Optional] If you are using an external container registry, create OAuth MO.

116 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For instructions, see Creating OAuth managed object under Integrating Container
Registry to MantaRay NM/Integrating Container Registry in MantaRay NM
Operating Documentation.

Result
You have configured and integrated the CCR with MantaRay NM.

To check the CCR service status, seeChecking Central Container Registry service status under
Administering Central Container Registry in MantaRay NM Operating Documentation.

To check the CCR integration status, seeVerifying Container Registry integration under
Integrating Container Registry to MantaRay NM in MantaRay NM Operating Documentation.

To remove the CCR integration to MantaRay NM, see Removing Container Registry integration
under Integrating Container Registry to MantaRay NM in MantaRay NM Operating
Documentation.

6.1.2 Integrating NEAT with MantaRay NM

You need to integrate Nokia Edge Automation Tool (NEAT) with MantaRay NM to enable the cloud
instance integration and deintegration operations in MantaRay NM.

Purpose

Note:
The following procedure presents a high-level overview of the NEAT integration process.
For complete instructions, see Integrating Nokia Edge Automation Tool to MantaRay NM
in MantaRay NM Operating Documentation.

In AirScale Cloud RAN BTS (Cloud RAN BTS), the cloud-native network functions (CNFs) are
deployed on Red Hat OpenShift Container Platform (OCP) clusters. The OCP clusters are deployed
and managed by NEAT. You need to integrate NEAT with MantaRay NM to integrate or deintegrate
the target OCP cluster using MantaRay NM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 117

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 18: NEAT configuration and integration process

After the integration, NEAT is connected to MantaRay NM through an IP network, using HTTPS and
the Domain Name Server (DNS) backbone.
Figure 19: Connection between the integrated network elements and MantaRay NM

Before you start

Make sure you have installed NEAT and MantaRay NM.

Procedure
1 Prepare NEAT for integration with MantaRay NM.

For instructions, see Preparing NEAT for integration under Integrating Nokia Edge
Automation Tool to MantaRay NM in MantaRay NM Operating Documentation.

2 Prepare MantaRay NM for integration with NEAT.

For instructions, see Preparing MantaRay NM for NEAT integration under Integrating Nokia
Edge Automation Tool to MantaRay NM in MantaRay NM Operating Documentation.

3 Set up the firewall rules for NEAT.

118 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For instructions, see Setting up firewall rules under Integrating Nokia Edge Automation
Tool to MantaRay NM/Preparing the intermediate system in MantaRay NM Operating
Documentation.

4 Create the CLOUD_INFRA_MANAGER managed object (MO) to integrate NEAT with

MantaRay NM.

For instructions, see Creating CLOUD_INFRA_MANAGER managed object under

Integrating Nokia Edge Automation Tool to MantaRay NM/Integrating Container Registry
in MantaRay NM Operating Documentation.

Result
You have configured and integrated NEAT with MantaRay NM.

To check the NEAT integration status, see Verifying NEAT integration under Integrating Nokia
Edge Automation Tool to MantaRay NM in MantaRay NM Operating Documentation.

To remove the NEAT integration to MantaRay NM, see Removing NEAT integration under
Integrating Nokia Edge Automation Tool to MantaRay NM in MantaRay NM Operating
Documentation.

6.2 Integrating a cloud instance with MantaRay NM

You need to integrate the Red Hat OpenShift Container Platform (OCP) cluster with MantaRay NM
before you can deploy the cloud-native network functions (CNFs) on this OCP cluster.

In AirScale Cloud RAN BTS (Cloud RAN BTS), the CNFs are deployed on OCP clusters. You need to
integrate the target Kubernetes cluster with MantaRay NM before deploying the CNF using the
Cloud Integrate operation, performed by the MantaRay NM Workflow Engine.

You can start the Cloud Integrate operation in MantaRay NM with the following methods:

Integrating a cloud instance with MantaRay NM using MantaRay NM GUI

Integrating a cloud instance with MantaRay NM using MantaRay NM CLI

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 119

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
6.2.1 Integrating a cloud instance with MantaRay NM using
MantaRay NM GUI

You can integrate the Red Hat OpenShift Container Platform (OCP) instance with MantaRay NM by
using MantaRay NM graphical user interface (GUI).

Purpose
In AirScale Cloud RAN BTS (Cloud RAN BTS), the CNFs are deployed on OCP clusters. You need to
integrate the target OCP cluster with MantaRay NM before deploying the CNF using the Cloud
Integrate operation, performed by the MantaRay NM Workflow Engine.

As a result of the Cloud Integrate operation, the CLOUD and K8SAPI objects with the
Kubernetes configuration are created in MantaRay NM System Data Access (NASDA) database
under the PLMN-PLMN root object. Integrated objects are visible in MantaRay NM Monitor.

Note:
<CLOUD DN> is the distinguished name (DN) of the CLOUD object. You need to define it
during the OCP deployment. For more information, see Operating
Documentation/AirScale Cloud RAN BTS System/Operation/Deploying Nokia and
Operating Red Hat OCP.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have obtained the Kubernetes configuration kubeconfig YAML file from the OCP
cluster to be integrated. For more information, see Operating Documentation/AirScale
Cloud RAN BTS System/Operation/Deploying and Operating Nokia Red Hat OCP.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

120 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
Figure 20: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

Figure 21: CM Operations Manager view

3 In CM Operations Manager tab, selectTools›Workflow Engine.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 121

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
4 Go to the Operation list and select Cloud Operations.

Step result
Figure 22: Workflow Engine›Operation list›Cloud Operations view

5 Click the green arrow icon next to the Cloud Integration›Cloud Integrate
operation.

Step result
The Cloud Integrate dialog pops-up.

6 In the Cloud Integrate dialog, provide information about the CLOUD object.

6.1 Fill in <CLOUD DN>.

6.2 Select and upload the kubeconfig file with the Kubernetes configuration from your
local disc.

122 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Tip:
The kubeconfig file is created during the OCP deployment. It needs to
contain the embedded certificates, which allow setting up secure Transport
Layer Security (TLS) connectivity to the OCP Kubernetes application
programming interface (API).

6.3 In the Type field, select the type of the CLOUD object.

Available CLOUD object types:

Red Hat OCP
IBM ROKS

6.4 In the Version field, fill in the cloud software version.

Step example
Example of the cloud software version: ocp-4.12.25-nokia.23.8.2

6.5 Click Start.

Step result
The cloud instance has been integrated into MantaRay NM.
You can check the integrated CLOUD objects in MantaRay NM Monitor application. For
instructions, see Checking integrated CLOUD objects in Monitor under Managing cloud
services/Cloud operations/Cloud Integrate in MantaRay NM Operating Documentation.

6.2.2 Integrating a cloud instance with MantaRay NM using

MantaRay NM CLI

You can integrate the Red Hat OpenShift Container Platform (OCP) instance with MantaRay NM by
using MantaRay NM CLI.

Purpose
In AirScale Cloud RAN BTS (Cloud RAN BTS), the CNFs are deployed on OCP clusters. You need to

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 123

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
integrate the target OCP cluster with MantaRay NM before deploying the CNF using the Cloud
Integrate operation, performed by the MantaRay NM Workflow Engine.

As a result of the Cloud Integrate operation, the CLOUD and K8SAPI objects with the
Kubernetes configuration are created in MantaRay NM System Data Access (NASDA) database
under the PLMN-PLMN root object. Integrated objects are visible in MantaRay NM Monitor.

Note:
<CLOUD DN> is the distinguished name (DN) of the CLOUD object. You need to define it
during the OCP deployment. For more information, see Operating
Documentation/AirScale Cloud RAN BTS System/Operate/Deploying and Operating
Nokia Red Hat OCP.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have obtained the Kubernetes configuration kubeconfig YAML file from the OCP
cluster to be integrated. For more information, see Operating Documentation/AirScale
Cloud RAN BTS System/Operation/Deploying and Operating Nokia Red Hat OCP.

Procedure
1 Log in as the omc user to the MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Convert the kubeconfig.yaml file content to the JSON format by entering:

124 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
[omc<VM node>]$ python -c 'import json, yaml, sys;

print(json.dumps(yaml.load(sys.stdin)))' <

kubeconfig.yaml > kubeconfig_parameters.json

Tip:
The kubeconfig file is created during the OCP deployment. It needs to contain the
embedded certificates, which allow setting up secure Transport Layer Security (TLS)
connectivity to the OCP Kubernetes application programming interface (API).

Step result
You have created the kubeconfig_parameters.json file with the converted content
of the kubeconfig.yaml file.

3 To create the kubeconfig.json file, use the kubeconfig_parameters.json file

from step 2. and the following template:

Step example

"managedObjects": [

"moId": "PLMN-PLMN/CLOUD-1/K8SAPI-1/KUBECONFIG-1",

"moClass": {

"id": "com.nokia.mantaraynm.lcm.ssh:KUBECONFIG",

"version": "1.0"

},

"planOperation": "CREATE",

"parameters": "converted content of the kubeconfig_parameters.json file"

4 Save the kubeconfig.json file on your local disc.

5 Import the kubeconfig.json file content to the MantaRay NM Security Sensitive Data
(SSD) by entering:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 125

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
curl -k -i --data @kubeconfig.json -H "Content-Type:application/vnd.nokia-sm-

import-request-v1+json" -X POST -u username:password "https://<was server>/sm-

operations/api/sm/operations/v1/execute/ssd-import?overwrite=true" -v

6 Verify if the KUBECONFIG object was created in the MantaRay NM SSD by entering:

curl -k -d '{"operationAttributes": {"scope": ["PLMN-

PLMN/CLOUD-1/K8SAPI-1/KUBECONFIG-1"]}}' -H "Content-Type:application/vnd.nokia-

sm-export-request-v1+json" -u <user>:<password> https://<WAS load balancer

fqdn>/sm-operations/api/sm/operations/v1/execute/ssd-export?fileType=JSON

Step result
PLMN-PLMN/CLOUD-1/K8SAPI-1/KUBECONFIG-1 is visible in the output.

body={"managedObjects":[{"moId":"PLMN-

PLMN/CLOUD-1/K8SAPI-1/KUBECONFIG-1","moClass":{"id":"com.nokia.netact.lcm.ssd:KUB

ECONFIG","version":"1.0"},"planOperation":"CREATE","parameters":{"apiVersion":"",

"kind":"","clusters":"","contexts":"","current-

context":"","preferences":{},"users":""}}]}

7 Start the Cloud Integrate operation by entering:

racclimx.sh -op Cloud_Integrate -cloudDn PLMN_PLMN/CLOUD-1 -cloudType "Red Hat

OCP" -version ocp-4.12.25-nokia.23.8.2 -v

Example of the cloud software version: ocp-4.12.25-nokia.23.8.2

Step result
The cloud instance has been integrated into MantaRay NM.
You can check the integrated CLOUD objects in MantaRay NM Monitor application. For
instructions, see Checking integrated CLOUD objects in Monitor under Managing cloud
services/Cloud operations/Cloud Integrate in MantaRay NM Operating Documentation.

126 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
6.2.3 Integrating a cloud instance with MantaRay NM using
MantaRay NM REST API

You can integrate the Red Hat OpenShift Container Platform (OCP) instance with MantaRay NM by
using MantaRay NM REST application programming interface (API).

Purpose
In AirScale Cloud RAN BTS (Cloud RAN BTS), the CNFs are deployed on OCP clusters. You need to
integrate the target OCP cluster with MantaRay NM before deploying the CNF using the Cloud
Integrate operation, performed by the MantaRay NM Workflow Engine.

As a result of the Cloud Integrate operation, the CLOUD and K8SAPI objects with the
Kubernetes configuration are created in MantaRay NM System Data Access (NASDA) database
under the PLMN-PLMN root object. Integrated objects are visible in MantaRay NM Monitor.

Note:
<CLOUD DN> is the distinguished name (DN) of the CLOUD object. You need to define it
during the OCP deployment. For more information, see Operating
Documentation/AirScale Cloud RAN BTS System/Operation/Deploying and Operating
Nokia Red Hat OCP.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have obtained the Kubernetes configuration kubeconfig YAML file from the OCP
cluster to be integrated. For more information, see Operating Documentation/AirScale
Cloud RAN BTS System/Operation/Deploying and Operating Nokia Red Hat OCP.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 127

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Access the startOperation endpoint of the CM Operations REST API using the HTTP
POST method.

The request should contain the Content-Type header with the multipart/form-data
value.

Step example

https://<cluster hostname>/mantaraynm/cm/open-api/operations/v1/start

3 Start the Cloud Integrate operation by placing the JSON request.

Step example

"operationName": "Cloud Integrate",

"operationAlias": "<operation alias>",

"operationAttributes": {

"cloudDn": "PLMN-PLMN/CLOUD-1",

"cloudType": "Red Hat OCP or IBM ROKS",

"version": "ocp-4.12.25-nokia.23.8.2"

Example of the cloud software version: ocp-4.12.25-nokia.23.8.2

4 Save the operationId returned in the response for future use.

Result
The cloud instance has been integrated into MantaRay NM.

You can check the integrated CLOUD objects in MantaRay NM Monitor application. For

128 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
instructions, see Checking integrated CLOUD objects in Monitor under Managing cloud
services/Cloud operations/Cloud Integrate in MantaRay NM Operating Documentation.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 129

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
7. Creating a CNF deployment plan

You need a deployment plan to trigger the cloud-native network function (CNF) deployment
operation in MantaRay NM. You can prepare a deployment plan file in a text editor and import it to
MantaRay NM, or create it in MantaRay NM Configuration Management (CM) Editor.

In AirScale Cloud RAN BTS (Cloud RAN BTS), CNFs are deployed on the cloud infrastructure using
Kubernetes containers organized into pods. Pod deployment is automated using Helm, which is a
system for simplifying container management.

The CNF package contains all elements needed to instantiate the CNF, organized in several Helm
chart folders:

CNF manifest file JSON file that describes the complete package contents and serves
as a simple CNF workload descriptor.

Helm charts CNF orchestration artifacts, which contain definitions of Kubernetes

resources required to deploy a CNF.

Values override files YAML files that collect the CNF parameters which can be modified by
the operator.

ne_compatibility file YAML file that contains information about the compatible software
versions.

JSON schema JSON file that imposes a structure on the YAML value override files.

Container images CNF images that are onboarded to the container registry before the
CNF deployment or upgrade operation.

130 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 23: CNF package

The CNF deployment packages for different CNFs may contain a different number of Helm charts.
You can check the number of Helm charts in the manifest.json file in the deployment
package. MantaRay NM deploys the Helm charts contained in the CNF deployment package in an
order defined by the deployment plan.

MantaRay NM defines the following network elements as CNF objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

You can create a deployment plan for a CNF object using:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 131

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
a text editor. For more information, see Creating a deployment plan using a text editor.
MantaRay NM Configuration Management (CM) Editor. For more information, see Creating a
deployment plan using MantaRay NM GUI.

After creating the plan, you need to override the default configuration values in Helm charts with
parameters that you have defined in the values override files. For more information, see Updating
Helm chart configuration values from values override files.

7.1 CNF object parameters in LCM operation plans

Cloud-native network function (CNF) parameters used in AirScale Cloud RAN BTS (Cloud RAN BTS)
life cycle management (LCM) operation plans

132 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 53: CNF parameters in Cloud RAN BTS LCM operation plans

Parameter Description Possible values and examples Mandatory or

optional

cloudDN Distinguished name (DN) of cloud Cloud instance DN of the cloud instance intended for the Mandatory
integrated to MantaRay NM vDU or the vCU. The value of the parameter needs to be
unique in the MantaRay NM instance.

deploymentPr List of the Helm charts to be executed. For chart, use the names of the tgz packages containing Mandatory
ofile The number of items should be the the Helm charts in the HelmChart folder inside the CNF
same as the number of Helm charts distribution package. For the virtualized gNB distributed unit
containing the (vDU), these are:
deploymentSequence parameter • values-override.aic-vdu-cluster-
inside the manifest file. preparation.yaml
• values-override.aic-vdu-
prerequisite.yaml
• values-override.aic-vdu.yaml
For the virtualized gNB central unit (vCU), these are:
• values-override.aic-vcu-cluster-
preparation.yaml
• values-override.aic-vcu-
prerequisite.yaml
• values-override.aic-vcu.yaml

chart Name of the Helm chart in the Helm For example: aic-vcu-cluster- Mandatory
chart folder inside the CNF distribution preparation-17.250.398.tgz
package.

values The Base64-encoded values override If you used the CNF Plan Prepare operation, leave this Mandatory
file. parameter empty. For more information, see Updating
Helm chart configuration values from values override files.

order The deployment sequence value for a 0 (first structure) Mandatory

particular Helm chart inside the 1 (second structure)
software manifest file. 2 (third structure)

releaseName Name of a Helm chart instance <CNF id>-<chart name and release> Mandatory
running in the Kubernetes cluster.

operation Integration type of the managed create Optional

object.

CnfId Identified instance of of CNF object. For example: 1 Optional

The value of the parameter needs to be unique in the
MantaRay NM instance.

secrets Name of Kubernetes secrets. User defined name of the Kubernetes secret. Optional

containerReg Name of container registries used to User defined name of the container registry. Mandatory
istries install CNF.

name Name of the managed object. User defined name of the CNF object. Optional

cnfSwId Name of the CNF software package vDUCNF_<version> or vCUCNF_<version> Mandatory

imported to MantaRay NM.

neRelId Name of the network element this CNF For example: PLMN-PLMN/MRBTS-15 Optional
instance represents.

namespace Target Kubernetes cluster namespace, You can use either an already existing namespace or create Optional
where the CNF instance resources are a new one. If you provide an already existing namespace, it
deployed. will be used. If the namespace doesn't exist yet, it will be
created. Use a unique namespace for each CNF.

type Type of the deployed CNF or Nokia For example: vDUCNF, vCUCNF, NOP_ran-nic-sw- Optional
Kubernetes Operator for Cloud RAN controller, NOP_nokia-sync-operator
BTS.

release Main release of the CNF software For example: 24R2 Optional
package.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 133

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
7.2 Creating a deployment plan using a text editor

You can create a cloud-native network function (CNF) deployment plan using a text editor and
manually import it to MantaRay NM Configuration Management (CM) Editor.

Purpose
If you use a text editor, prepare a plan in one of the following formats:

RAML2.0
CSV
Simple CSV

Note:
XLSX format doesn't support long string values in the deploymentProfile/values
field of the CNF object. XLSX format supports up to 32,767 characters.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an integrated the target Kubernetes cluster with MantaRay NM. For more
information, see Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU.

Procedure
1 Base64-encode the filled-in value override files using the following Linux command:

base64 <values override file>.yaml | xargs | tr -d " "

Run the command for each file in the CNF deployment package and copy the output.

2 Create a deployment plan file using a text editor and manually fill the contents of the

134 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Base64-encoded values override files into the deploymentProfile/values field.

Plan mandatory and optional parameters according to CNF object parameters in LCM
operation plans.

Step example
Example of a virtualized gNB central unit (vCU) deployment plan in a RAML format:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 135

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE raml SYSTEM 'raml20.dtd'>

<raml version="2.0" xmlns="raml20.xsd">

<cmData type="plan" scope="all" name="vcu-T4-auto-1998"

id="PlanConfiguration( 34 )">

<header>

<log dateTime="2023-06-28T01:13:24.000+02:00"

action="created"appInfo="PlanExporter">UIValues are used</log>

</header>

<managedObject class="CNF" version="CNF2.0" distName="PLMN-PLMN/CNF-2127"

id="102397" operation="create">

<defaults name="System"/>

<list name="deploymentProfile">

<item>

<p name="values"><base 64 override value file for cluster preparation helm

charts></p>

<p name="chart">aic-vcu-cluster-preparation-17.402.0.tgz</p>

<p name="order">0</p>

<p name="releaseName">aic-vcu-cluster-preparation</p>

</item>

<item>

<p name="values"><base 64 override value file for prerequisite helm chart</p>

<p name="chart">aic-vcu-prerequisite-18.554.6.tgz</p>

<p name="order">1</p>

<p name="releaseName">aic-vcu-prerequisite</p>

</item>

<item>

<p name="values"><base 64 override value file for main helm chart</p>

<p name="chart">aic-vcu-19.250.59.tgz</p>

<p name="order">2</p>

<p name="releaseName">aic-vcu-main-chart</p>

</item>

</list>

<p name="cloudId">PLMN-PLMN/CLOUD-2127</p>

<p name="cnfSwId">vCUCNF23R3_19.250.59</p>

<list name="containerRegistries">

<p>ImageRegistry-1</p>

</list>

136 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
<p name="name">cnf2127</p>

<p name="namespace">cran1</p>

<p name="neRelId">PLMN-PLMN/MRBTS-2127</p><list name="secrets">

<p>CNF-cmp-secret</p>

<p>Mantaray-MN-taTrustChain-secret</p>

<p>pull-secret</p></list>

</managedObject>

</cmData>

</raml>

3 Import the deployment plan to MantaRay NM.

3.1 Log in to the MantaRay NM start page using a web browser.

3.2 Select CM Operations Manager›Tools›Editor.

3.3 From the top menu bar, select File›Import.

Step result
The Import window pops up.

3.4 Select the plan file to be imported and edit the plan name and import options if
necessary.

3.5 Click Start.

7.3 Creating a deployment plan using MantaRay NM GUI

You can create a cloud-native network function (CNF) deployment plan with MantaRay NM
Configuration Management (CM) Editor.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 137

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an integrated the target Kubernetes cluster with MantaRay NM. For more
information, see Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 24: MantaRay NM start page

2 Select Configuration ›CM Editor.

2.1 In the Opening cmedit.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Editor Java application opens.

3 From the top menu bar, select Plan›New Plan.

Step example

138 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 25: Creating a new plan in CM Editor›Plan

Step result
The new plan is added to the navigation tree. The Plan Header view is shown in the main
view. You can modify the plan name that has been automatically assigned by the application.

4 In the Plan Header view, define the plan parameters.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 139

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 26: Plan Header view

4.1 Type a new name and a description for the plan.

Note:
Maximum length of a plan name is 200 characters.

4.2 [Optional] Check the Enable policy plans box to define whether policy plans
(exception or reservation plans) are taken into account.

When you select Enable policy plans, the content of the plan is validated when
browsing or editing parameter values or managed objects (MOs) in the MO views.
When there are deviating parameter values or MOs, tooltips show the deviating
values, and the parameter field background is yellow.

4.3 [Optional] From the Group drop-down list, choose a group for the plan.

The default group for a new plan is General plans.

4.4 [Optional] From the Expiration drop-down list, select the plan expiration date.

The Expiration option defines how long the object or parameter modification is
prevented for the policy plan content.

4.5 From the Target configuration drop-down list, select the target configuration
for the plan.

140 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
5 Click Update.

Step result
The new plan name and the plan parameters you have configured are saved.

6 Add a CNF MO to the plan.

6.1 In the navigation tree on the left-hand side, expand the plan.

6.2 From the Managed Objects, right-click on the PLMN-xxx root object and select
New Managed Object.

Step example
Figure 27: Creating a new MO for a plan

Step result
The New Managed Object dialog opens. In this dialog, you can create a new MO
for the MO you have selected in the navigation tree.

6.3 From the MO class drop-down list, select CNF (com.nokia.cnf.lcm).

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 141

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 28: Defining the MO class as CNF (com.nokia.cnf.lcm)

6.4 In the MO ID field, enter a locally unique ID for the MO.

Locally unique means that the ID is unique under its parent object. If you leave this
field blank, an ID is automatically reserved when the instance ID data type is a number
without a validation pattern. For the rest of the instance IDs, including the MRBTS MO
under the PLMN-PLMN MO, you need to define a locally unique instance ID.

6.5 In the MO name field, enter a name for the object.

6.6 From the Template list, select a template you want to assign.

The template name is automatically selected from the parent object. If a template
with the same name cannot be found or the parent is not assigned, CM Editor
automatically selects a system template. There are different system templates for
different network element versions. If you want to change the template name for the
new MO, select another template name from the Template list. The Template list
presents the available templates for this MO class.

6.7 Click OK.

Step result
The CNF MO is added to the navigation tree under the created plan.

Result
You have created the CNF deployment plan. The DeploymentProfile structure parameter
under the CNF MO in the plan needs to be filled in with CNF configuration values from the
Base64-encoded CNF values override files according to CNF object parameters in LCM operation
plans. You can do this manually in CM Editor or automatically using the CNF Plan Prepare

142 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
operation in CM Operations Manager.

For more information on the CNF Plan Prepare operation, see Updating Helm chart
configuration values from values override files.

7.4 Updating Helm chart configuration values from values

override files

You need to update the cloud-native network function (CNF) deployment plan with the
configuration values defined in the values override files. You can either do this manually by
editing the CNF deployment plan in a text editor or automatically using the CNF Plan
Prepare operation in MantaRay NM.

Figure 29: Updating Helm chart configuration values from values override files

In AirScale Cloud RAN BTS (Cloud RAN BTS), CNFs are deployed on the cloud infrastructure using
Helm, which is a system for simplifying container management. The Helm charts contain the
details of resource creation and pod deployment with default values of the CNF deployment
parameters. You can override the default configuration values with parameters specific to your
infrastructure and the chosen deployment type by modifying the values override YAML files
included in the deployment package. Before the deployment, you need to provide the parameter
values from the values override files to the CNF deployment plan. You can either do this manually
by editing the CNF deployment plan in a text editor or automatically using the CNF Plan
Prepare operation in MantaRay NM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 143

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
7.4.1 Updating Helm chart configuration values using
MantaRay NM GUI

You can use the CNF Plan Prepare operation in MantaRay NM to update the cloud-native
network function (CNF) deployment plan with the configuration values from the values override
files. You can start the CNF Plan Prepare operation using MantaRay NM graphical user
interface (GUI).

Purpose
You can override the default CNF configuration values with parameters specific to your
infrastructure and the chosen deployment type by modifying the values override YAML files
included in the CNF deployment package. The CNF Plan Prepare operation in MantaRay NM
allows you to automatically import the content of the values override files to the deployment
plan.

Note:
If you add the content of the values override files to the CNF deployment plan manually,
you need to Base64-encode the values override files first. If you use the CNF Plan
Prepare operation, the Base64-encoding is automatic.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

144 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
Figure 30: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

3 In the Plans view, right-click on the prepared CNF deployment plan and select Workflow
Engine for Plan.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 145

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 31: Opening the Workflow Engine for a selected plan

Step result
The Workflow Engine window pops-up.

4 Go to Operation list and select Cloud RAN Management - CNF Deployment.

5 Click the green arrow icon next to the CNF Plan Prepare operation.

Step result
The CNF Plan Prepare dialog pops-up.

146 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 32: CNF Plan Prepare view

6 In the CNF Plan Prepare dialog, configure the settings for the operation.

6.1 [Optional] Define a name and a description for the operation.

6.2 In the Scope field, select a single CNF object.

6.3 In the Replace existing values field, select if the values of the parameters in
the plan should be replaced with the content of the values override files.

To replace the existing parameter values with the content from the values override
files, choose Yes.

6.4 Select and upload the prepared values override files from your local disc.

7 Click Start.

8 Repeat the procedure for all CNF objects in the Scope field.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 147

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Postrequisites
You can check if the content of the values override files was added to the deployment plan by
opening the plan in MantaRay NM CM Editor and navigating to the selected CNF object. In CM
Editor, you can also plan and modify all other mandatory and optional parameter values for a
selected CNF object.

7.4.2 Updating Helm chart configuration values using

MantaRay NM CLI

You can use the CNF Plan Prepare operation in MantaRay NM to update the cloud-native
network function (CNF) deployment plan with the configuration values from the values override
files. You can start the CNF Plan Prepare operation using MantaRay NM CLI.

Purpose
You can override the default CNF configuration values with parameters specific to your
infrastructure and the chosen deployment type by modifying the values override YAML files
included in the CNF deployment package. The CNF Plan Prepare operation in MantaRay NM
allows you to automatically import the content of the values override files to the deployment
plan.

Note:
If you add the content of the values override files to the CNF deployment plan manually,
you need to Base64-encode the values override files first. If you use the CNF Plan
Prepare operation, the Base64-encoding is automatic.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in

148 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Update the CNF deployment plan with the content of the main chart values override file by
entering:

racclimx.sh -op CNF_Plan_Prepare -planName CNF_deployment_plan_SAT -DN

PLMN-PLMN/CNF-<id> -replaceExistingValues true/false -mainChartValues

values-override.aic-<CNF_name>.yaml -v

3 Update the CNF deployment plan with the content of the cluster preparation chart,
prerequisites chart, and main chart values override files by entering:

racclimx.sh -op CNF_Plan_Prepare -<planName> CNF_deployment_plan_SAT

-DN PLMN-PLMN/CNF-<id> -replaceExistingValues true/false -

clusterPreparationValues values-override.aic-<CNF_name>-clusterpreparation.

yaml -prerequisitesValues values-override.aic-<CNF_name>prerequisites.

yaml -mainChartValues values-override.aic-<CNF_name>.yaml -v

Postrequisites
You can check if the content of the values override files was added to the deployment plan by
opening the plan in MantaRay NM CM Editor and navigating to the selected CNF object. In CM
Editor, you can also plan and modify all other mandatory and optional parameter values for a
selected CNF object.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 149

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
7.5 Creating secrets for CNF objects

You need to configure a secrets list for the cloud-native network function (CNF) to perform the
CNF deployment in MantaRay NM with autoconfiguration.

You can deploy the AirScale Cloud RAN BTS (Cloud RAN BTS) CNFs with autoconfiguration using a
Plug and Play (PnP) procedure in MantaRay NM. Using autoconfiguration requires you to provide
additional parameter values for autoconnection and certificate management in the CNF values
override files and in the additional secret files:
cmp_secret.yaml
taTrustChain_secret.yaml (optional)
pull_secret.yaml

Note:
You can find the cmp_secret.yaml and taTrustChain_secret.yaml files inside
the Secret folder of the CNF deployment package. The pull_secret.yaml file needs
to be prepared manually. For instructions, see Creating an image pull secret for the vDU
deployment.

For instructions on filling in the values overrides and secret files, see:
Filling in the values override files for the vCU
Filling in the values override files for the vDU

Note:
Cloud RAN BTS doesn't support autoconfiguration for the deployment of the Nokia
proprietary Kubernetes operators for Cloud RAN BTS. Therefore, you can provide additional
parameters only for the virtualized gNB central unit (vCU) and the virtualized gNB
distributed unit (vDU).

During the CNF deployment, before the installation of Helm charts, MantaRay NM creates secrets
in the appropriate namespace of the target Kubernetes cluster, based on the information from
the secrets list in a CNF object. To define secret items in the CNF object list, you need to add
appropriate secrets to MantaRay NM Security Sensitive Data (SSD). You can add secrets to
MantaRay NM SSD with the following methods:

150 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Adding secrets to MantaRay NM SSD using MantaRay NM GUI
Adding secrets to MantaRay NM SSD using MantaRay NM REST API

Note:
If during the deployment the vCU or the vDU gets a certificate from a different root CA
than MantaRay NM, you need to import the vCU or vDU root certificate to MantaRay NM.
For more information about certificate import, see the Adding additional trust anchors
chapter under Administering MantaRay NM System Security category in MantaRay NM
Operating Documentation.

Notice:
The name of the Certificate Management Protocol (CMP) secret needs to be unique for
each CNF and include a CNF instance-specific identifier, for example: CNF2127-cmp-
secret.

7.5.1 Creating an image pull secret for the vDU deployment

You need to manually create an image pull secret and save the contents in the pull-
secret.yaml file before you can deploy the virtualized gNB distributed unit (vDU).

Purpose
Before the deployment of the vDU, you need to create an image pull secret, which stores the
credentials for authentication during the connection with a container registry. You need the
credentials to enable the deployment of Nokia Cloud RAN SmartNICs (RAN NICs) together with the
vDU cloud-native network function (CNF).

Before you start

Make sure you have defined the value of the imagePullSecret parameter in values-
override.aic-vdu.yaml. For instructions, see Filling in the values override files for the vDU.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 151

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Procedure
1 Create a secret by entering:

oc create secret docker-registry pull-secret --docker-server=<server IP address>

--docker-username=neat --docker-password=neat

Note:
In this example, the secret is created in Nokia Edge Automation Tool (NEAT) Docker
registry. The same steps apply if you use another registry.

2 Save the content of the secret to the pull-secret.yaml file by entering:

oc get secret pull-secret -o yaml> pull-secret.yaml

3 Open the pull-secret.yaml file in a text editor and remove the

creationTimeStamp, resourceVersion, and uid parameters.

Step example

apiVersion: v1

data:

.dockerconfigjson:

eyJhdXRocyI6eyJjbGFiMTA2OG5vZGUxNy5uZXRhY3QubnNuLXJkbmV0Lm5ldDo4NDQzIjp7InVzZXJuY

W1lIjoiYWRtaW4iLCJwYXNzd29yZCI6IkFYZjZ2TVQwZnpJTGN2NlVxTTFna2V2RFYrT0VhcXlRdjZraU

NlV2tDTjA9IiwiZW1haWwiOiJuZXRhY3RAbm9raWEuY29tIiwiYXV0aCI6IllXUnRhVzQ2UVZobU5uWk5

WREJtZWtsTVkzWTJWWEZOTVdkclpYWkVWaXRQUldGeGVWRjJObXRwUTJWWGEwTk9NRDA9In19fQ==

kind: Secret

metadata:

creationTimestamp: "2023-07-25T13:19:41Z"

name: pull-secret

namespace: cran1

resourceVersion: "8065193"

uid: 3cae2177-3c32-4e24-ac25-700761b2cc7b

type: kubernetes.io/dockerconfigjson

152 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
The namespace needs to be the same as the namespace that will be used for the vDU
deployment. For more information, see Filling in the values override files for the vDU.

4 Save the modified file on your local computer.

Result
You have created a new Kubernetes secret and saved the contents locally as a pull-
secret.yaml file.

Postrequisites
You need to add the contents of the pull-secret.yaml file to MantaRay NM Security
Sensitive Data (SSD) for the target CNF object with one of the following methods:

Adding secrets to MantaRay NM SSD using MantaRay NM GUI

Adding secrets to MantaRay NM SSD using MantaRay NM REST API

7.5.2 Adding secrets to MantaRay NM SSD using MantaRay

NM GUI

You can use MantaRay NM graphical user interface (GUI) to add appropriate secrets to MantaRay
NM Security Sensitive Data (SSD).

Purpose
During the cloud-native network function (CNF) deployment, before the installation of Helm
charts, MantaRay NM creates secrets in the appropriate namespace of the target Kubernetes
cluster based on the information from the secrets list in a CNF object. To define secret items in
the CNF object list, add appropriate secrets to MantaRay NM SSD.

Before you start

Make sure that:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 153

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.

Note:
You need to perform the procedure separately for each secret file.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 33: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

154 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

3 In the Plans view, right-click on the prepared CNF deployment plan and select Workflow
Engine for Plan.

Step example
Figure 34: Opening the Workflow Engine for a selected plan

Step result
The Workflow Engine window pops-up.

4 Go to Operation list and select Cloud RAN Management - CNF Deployment.

5 Click the green arrow icon next to the CNF Secret Import operation.

Step result
The CNF Secret Import dialog pops-up.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 155

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 35: CNF Secret Import view

6 In the CNF Secret Import dialog, select and upload the secret file with the Kubernetes
configuration from your local disc.

7 Click Start.

7.5.3 Adding secrets to MantaRay NM SSD using MantaRay

NM REST API

You can use MantaRay NM REST application programming interface (API) to add appropriate
secrets to MantaRay NM Security Sensitive Data (SSD).

Purpose
During the cloud-native network function (CNF) deployment, before the installation of Helm
charts, MantaRay NM creates secrets in the appropriate namespace of the target Kubernetes

156 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
cluster based on the information from the secrets list in a CNF object. To define secret items in
the CNF object list, add appropriate secrets to MantaRay NM SSD.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.

Note:
You need to perform the procedure separately for each secret file.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Access the secrets storing endpoint using the HTTP POST method.

The request should contain the Content-Type header with the

application/vnd.nokiasecret+yaml value.

Step example

https://<cluster hostname>/mantaraynm/cm/internal-api/cnflcm/v1/secrets

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 157

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
3 Request to add the secret to MantaRay NM SSD by entering:

curl -X POST 'https://<cluster hostname>/mantaraynm/cm/

internal-api/cnflcm/v1/secrets' --header 'Content-Type: application/

vnd.nokia-secret+yaml' --header 'Authorization: Basic b21jOm9tYw=='

--data-raw 'apiVersion: v1

kind: Secret

metadata:

name: <secret name>

namespace: default

type: Opaque

stringData:

psk:

OGg3N1BMQng3SUVjY1Vra0YtWkRzelZlUEdzeDBBbGZQbi1nc3BuMG5saVFkYnla

refNum: VUR4cTMxUElRNWl5YUR6eVd0cTJpQg'

Note:
You need to include an authorization token in the in HTTP authorization header of the
request. For instructions on issuing the token, see the Authentication and
authorization chapter under RESTful Web Service Data Access API in MantaRay
NM Operating Documentation.

158 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
8. Onboarding software packages to MantaRay NM

Before deploying AirScale Cloud RAN BTS (Cloud RAN BTS) , you need to upload the required
software packages to MantaRay NM from your local computer.

The software packages used in the Cloud RAN BTS life cycle management (LCM) operations need
to be delivered and onboarded to the tool, which executes the deployment. The CNF packages
need to also be onboarded to the container registry, integrated with MantaRay NM.

Note:
You can onboard CNF packages to the central container registry (CCR) during their
onboarding to MantaRay NM or during the CNF deployment operation. If neecessary, you
can also onboard the CNF packages to CCR independently. For more information, see
Onboarding software images to the container registry.

8.1 Installing MantaRay NM fast pass service package for the

Cloud RAN BTS release

Before onboarding the components of a new AirScale Cloud RAN BTS (Cloud RAN BTS) software
release to MantaRay NM, you need to install a new fast pass service package.

The MantaRay NM fast pass service package is not a part of the Cloud RAN BTS software release.
However, it contains the new vCU, vDU, and FHGW adaptation model, compatible with the new
Cloud RAN BTS software release. Multiple adaptation packages can exist in MantaRay NM
simultaneously without disturbing the MantaRay NM or the integrated network elements (NEs)
operations. You can download the MantaRay NM fast pass service package for the selected Cloud
RAN BTS release from Nokia Software Supply Tool (SWSt).

For instructions on installation of the MantaRay NM fast pass service package, see the Installing
MantaRay NM fast pass Service Packages section in MantaRay NM Operating Documentation.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 159

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
You need to install a MantaRay NM fast pass package only once for each Cloud RAN BTS
release.

8.2 Uploading certificates to MantaRay NM Software

Integrity Protection Trust Store

You need to upload the Nokia Root Certificate Authority (CA) certificates to the Software Integrity
Protection Trust Store before you can upload the cloud-native network function (CNF)
deployment packages to MantaRay NM.

Purpose
The complete CNF deployment package includes two files:
CNF package in ZIP format
Signature file in PKC7 format

When you import the complete CNF package to MantaRay NM, MantaRay NM verifies the signature
file using Nokia Root CA certificates stored in Software Integrity Protection Trust Store. If the
operation fails, you can't import the CNF package to MantaRay NM.

Before you start

Make sure that:

you downloaded the Nokia Root CA certificate from Nokia Software Supply Tool (SWSt).
the Nokia Root CA certificate is in the PEM format.
you have the administrator permissions in MantaRay NM.

Procedure
1 Log in as the root user to the dmgr virtual machine (VM) of MantaRay NM using Secure Shell
(SSH).

160 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
To locate the dmgr VM, see the Locating the right virtual machine for a service
chapter in MantaRay NM Operating Documentation.

2 Get the password to Software Integrity Protection Trust Store by entering:

[root@<MantaRay NM DMGR VM Node> ~]# java -jar /opt/oss/NSN-

swm_filesystem/install/lib/password-store-cli.jar swm.global swip.keystore

Note:
Note the output for use in further steps.

3 Add the certificate PEM file to Software Integrity Protection Trust Store by entering:

[root@<MantaRay NM DMGR VM Node> ~]# keytool -import -alias <certificate_alias> -

file <certificate_file_path> -keystore

/var/opt/oss/global/swm/swm_keystore/swm_SWIP_truststore.jks

4 After the prompt, enter the password generated in step 2.

Result
You have added the Nokia Root CA certificate from SWSt to Software Integrity Protection Trust
Store. To list or remove the certificates available in Software Integrity Protection Trust Store, see
the Certificates management for Software Integrity Protection Trust Store chapter in MantaRay
NM Operating Documentation.

8.3 Onboarding software packages to MantaRay NM

manually

To deploy AirScale Cloud RAN BTS using MantaRay NM, you need to first import and onboard the
required software packages to Storage Archive in MantaRay NM Software Manager.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 161

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Before you start

Perform Downloading software packages from SWSt for the following network elements:
Nokia AirFrame Fronthaul Gateway (FHGW)
Virtualized gNB central unit (vCU)
Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Tip:
You need to have the id="swmPackageImportPermission" permission in MantaRay
NM to add software packages to the Software Archive. Otherwise, the Add
software package function is disabled.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 36: MantaRay NM start page view

2 Select Configuration›Software Manager.

3 Select the Software Archive tab.

162 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step example
Figure 37: Software Manager›Software Archive view

4 Go to the classic Software Manager.

4.1 Click the Application menu icon.

Step example
Figure 38: Selecting theApplication menu option

4.2 Click Software manager (Classical).

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 163

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 39: Choosing Software manager (Classical)

Step result
You are in the classic Software Manager.

5 Click the Add software package link above the navigation tree.

Step example
Figure 40: Software Manager›Add software package view

5.1 In the Opening webstart.jnlp dialog window, click use Java Web Start
Launcher.

5.2 Confirm all security questions about the digital signature and software provider.

164 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
The SW Import Manager Java application opens.

6 From the MO type drop-down list on the left-hand side, select the managed object (MO)
type.

Figure 41: Selecting the MO type in the SW Import Manager view

For the Cloud RAN BTS, you can choose the following MO types:
CNF for the vCU, vDU, and Nokia proprietary Kubernetes operators for Cloud RAN BTS
FHGW

Note:
Import of Signed Software Package is supported only for the CNF MO type.

7 Click Add MantaRay NM Files or Add Local Files.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 165

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
To use the Add MantaRay NM Files option, you need to first import the
software package to the MantaRay NM temporary directory.

Step result
The Open dialog window opens.

8 From the selected local or MantaRay NM directory, choose one or several files containing
software packages and click Open.

There can be an additional XML description file added to the software package. This file
contains all necessary information about the given software package.

Note:
The supported package extensions for all type of software packages are: ZIP, TAR,
TAR.GZ, and TGZ. Additionally, for unsigned software packages, extensions ISO, CPIO,
and RPM are supported.

MantaRay NM prevents using an incompatible package automatically. The descriptor XML file
defines software compatibility and incompatibility releases, versions, and regular expressions.

Step result
The selected file is placed in the list for import. The Status parameter informs you about
the software package validation result. If you want to delete a software package from the list,
click the Remove icon.

9 To open the SW Package Details dialog window, click the Details icon.

The SW Package Details dialog includes all the necessary information about the
imported software package. If an XML description file is added to the software package, the
SW Package Details is automatically filled in with the information taken from this file.
Otherwise, the SW Package Details is filled in by default only with the mandatory
parameters.

The Version ID and MO type parameters are mandatory for this form.

Step result
The SW Package Details dialog opens. Change or complement the software packages

166 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
data in this form.

Figure 42: SW Package Details view

To save your changes, click Save.

10 [Optiona] To automatically onboard the imported software images to the central container
registry (CCR), check the Distribute to Central Container Registry box.

The Distribute to Central Container Registry option allows for triggering ,

the CNF Distribute Software to CCR operation together with the software import.
The Software Manager window provides information on the status of the operation. The
following statuses are supported::
Distribute image fail
Software package imported successfully
Software package import failed

For detailed information, see Operation feedbacks window.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 167

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For instructions on the CNF Distribute Software to CCR operation, see
Onboarding software images to the container registry.

11 To import one file or all files at a time, click the Import icon in the selected software
package row or the Import all icon at the bottom of the SW Import Manager
window.

Importing the selected software packages begins. The import progress for the selected file is
presented in the Status field. If you want to stop the import of the selected software
package, click the Stop icon. The status changes to Import stopped. While the import
process is stopped, you can edit the software details in the SW Import Form. To proceed
with the file import, click the Import icon located in the selected software package row once
again.

Note:
If you stop the file import or it is stopped because of a failure, SW Import
Manager resumes the process from the breakpoint. The actual transfer status is
additionally visualized in the progress bar.

When you stop the transfer or it is interrupted by a failure, the already transferred file parts
are temporarily stored in the MantaRay NM software archive temporary directory. They are
checked against the storage time by Software Manager and automatically cleaned
according to the guidelines, which are defined in the Software Manager configuration
files. If you want to delete these files manually, use the Clean icon. From the Clean
MantaRay NM software temporary directory dialog window, select files for
deletion. Confirm the choice by clicking Delete.

Result
A new software package is imported to the Software Archive in MantaRay NM SM. The
package is listed in the navigation tree of available software under the suitable MO type and
release in the Software Archive tab. You can import the same software package multiple
times but with different software properties.

If you have checked the Distribute to Central Container Registry box during the
import operation, the software package has also been onboarded to the CCR.

If you want to close the SW Import Manager, click Close. Confirm the operation by clicking
OK.

168 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
Once the software package is imported to the Software Archive, you can't edit it. If
you need to change software package data, re-import a desired software package with
corrected data.

8.4 Onboarding the PDL validation plugin to MantaRay NM

You need to onboard the Parameter Description Language (PDL) validation plugin to MantaRay
NM before you can deploy the cloud-native network functions (CNFs).

Purpose

Note:
You need to perform this action only once for a MantaRay NM instance in a given AirScale
Cloud RAN BTS software release.

Before you start

Download the vDUCNF<version>_pdl_validation_service_plugin.zip or

vCUCNF<version>_pdl_validation_service_plugin.zip. For instruction, see
Downloading software packages from SWSt.

Procedure
1 Import the PDL package to MantaRay NM.

Follow the instructions in Onboarding software packages to MantaRay NM manually, but use
the vDUCNF<version>_pdl_validation_service_plugin.zip package.

2 Get the software release name from the PDL package.

2.1 Extract the pdl_validation_service_plugin.xml file from the

vDUCNF<version>_pdl_validation_service_plugin.zip or
vCUCNF<version>_pdl_validation_service_plugin.zip.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 169

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
2.2 Get the software release name from the
pdl_validation_service_plugin.xml file.

The file has the format:

<?xml version="1.0" encoding="utf-8"?>

<targetBD swReleaseVersionName="vDUCNF24R1_0.300.4384"/>

Keep the value of the swReleaseVesionName attribute, as you will need it for the
site configuration file (SCF). In the example, it's vDUCNF24R1_0.300.4384.

8.5 Onboarding software images to the container registry

When onboarding the cloud-native network function (CNF) software packages to the MantaRay
NM Software Archive, during the CNF deployment, and CNF upgrade, you can automatically
onboard the CNF software images to an external container registry or the central container
registry (CCR).

There are two operations in MantaRay NM, which allow onboarding the software packages for the
virtualized gNB central unit (vCU), virtualized gNB distributed unit (vDU), and Nokia proprietary
Kubernetes operators for AirScale Cloud RAN BTS (Cloud RAN BTS) to the container registry:
the CNF Distribute Software operation onboards the CNF packages to a container
registry which is integrated with MantaRay NM and defined by the containerRegistries
parameter of the deployment plan.

the CNF Distribute Software to CCR operation onboards the CNF software
packages to the CCR.

You can trigger the CNF software onboarding operations in MantaRay NM in the following ways:
By checking the Distribute Software to CCR box during the CNF package import to
MantaRay NM Software Archive. For instructions, see Onboarding software packages to
MantaRay NM manually.
By checking the Distribute CNF Software option in MantaRay NM Workflow Engine
during the CNF deployment or upgrade. For instructions, see Deploying a CNF without
autoconfiguration using MantaRay NM GUI.
Independently in the MantaRay NM Workflow Engine, using MantaRay NM graphical user
interface (GUI) (only the CNF Distribute Software operation) or MantaRay NM CLI (both
CNF Distribute Softwareand CNF Distribute Software to CCR) operations.

170 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For more information, see Configuration Management/Configuration Management Operating
Procedures/Managing Cloud Services/CNF Life Cycle Management Operations/CNF Distribute
Software operation - Distributing software to CCR in MantaRay NM Operating Documentation.

8.5.1 Onboarding software images to the container registry

using MantaRay NM GUI

The CNF Distribute Software operation in MantaRay NM allows you to onboard the cloud-
native network function (CNF) software images to the target container registry, integrated with
MantaRay NM. You can start the CNF Distribute Software operation in MantaRay NM
using MantaRay NM graphical user interface (GUI).

Purpose
With the CNF Distribute Software operation, you can onboard the CNF software images
to the container registry independently from the CNF software upload, CNF deployment, and CNF
upgrade operations.

For more information, see Configuration Management/Configuration Management Operating

Procedures/Managing Cloud Services/CNF Life Cycle Management Operations/CNF Distribute
Software CNF Distribute Software operation - Distributing software to CCR in MantaRay NM
Operating Documentation.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have integrated the OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 171

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 43: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

3 In the Plans view, right-click on the prepared CNF deployment plan and select Workflow
Engine for Plan.

Step example

172 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 44: Opening the Workflow Engine for a selected plan

Step result
The Workflow Engine window pops-up.

4 Go to the Operation list and select Cloud RAN Management.

5 Click the green arrow icon next to the CNF Distribute Software operation.

Step result
The CNF Distribute Software dialog pops-up.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 173

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 45: CNF Distribute Software view

6 [Optional] In the CNF Distribute Software dialog, configure the settings for the
operation.

6.1 [Optional] Define a name and a description for the operation.

6.2 In the containerRegistries field, fill in one or more distinguished names (DN) of
container registries integrated to MantaRay NM where the CNF software images are
to be distributed.

6.3 In the cnfSwId field, fill in the CNF software version imported to the MantaRay NM
Software Archive, for which CNF images are to be distributed.

174 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
If no container registry is defined in the containerRegistries parameter
of the deployment plan and is not present in the actual configuration, the CNF
software images are distributed to the CCR. For more information, see
Integrating Container Registry to MantaRay NM in MantaRay NM Operating
Documentation.

To replace the existing parameter values with the content from the values override files,
choose Yes.

7 Click Start and choose Yes in the confirmation dialog.

Step result
The Feedback dialog opens and the status of the CNF Distribute Software
operation changes to Started. When the operation is performed successfully, the status
changes to Finished.

Postrequisites
You can check the status of the operation in the following places:

Feedback dialog
Workflow Engine›Operation field
CM Operation Manager›Operation history tab

8.5.2 Onboarding software images to the container registry

using MantaRay NM CLI

The CNF Distribute Software operation in MantaRay NM allows you to onboard the cloud-
native network function (CNF) software images to the target container registry, integrated with
MantaRay NM. You can start the CNF Distribute Software operation in MantaRay NM
using MantaRay NM CLI.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 175

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Purpose
With the CNF Distribute Software operation, you can onboard the CNF software images
to the container registry independently from the CNF software upload, CNF deployment, and CNF
upgrade operations.

For more information, see Configuration Management/Configuration Management Operating

Procedures/Managing Cloud Services/CNF Life Cycle Management Operations/CNF Distribute
Software CNF Distribute Software operation - Distributing software to CCR in MantaRay NM
Operating Documentation.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have integrated the OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Start the CNF Distribute Software operation by entering:

176 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
/opt/oss/NSN-cmplatform/bin/racclimx.sh -op CNF_Distribute_Software -planName

<CNF plan name> -v

Table 54: Starting parameters for the CNF Distribute Software operation in
MantaRay NM CLI

Starting parameter Parameter description

-op This parameter defines the operation to be started.

-v This parameter turns on displaying the operation feedback

on the screen.

-planName This parameter specifies the deployment plan name.

- This parameter is optional and defines one or more

containerRegistries distinguished names (DN) of container registries integrated
to MantaRay NM where the CNF software images are to be
distributed. In case the parameter value is not defined and is
not present in the actual configuration, the software is
distributed to the central container registry (CCR).

-cnfSwId This parameter is optional and defines the CNF software

version imported to the MantaRay NM Software Archive, for
which CNF images are to be distributed. In case the value of
the parameter is not defined, it is taken from the actual
configuration.

For more information on the CLI operations in MantaRay NM, see the Executing command
line operations chapter under Command Line Operations in MantaRay NM Operating
Documentation.

Postrequisites
You can check the status of the operation in the following places:

Command line
CM Operation Manager›Operation history tab

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 177

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
8.5.3 Onboarding software images to the CCR using
MantaRay NM CLI

The CNF Distribute Software to CCR operation in MantaRay NM allows you to onboard
the cloud-native network function (CNF) software images to the central container registry (CCR).
You can start the CNF Distribute Software to CCR operation in MantaRay NM using
MantaRay NM CLI.

Purpose
Central container registry (CCR) is an Open Container Initiative (OCI) compliant registry that
provides a storage and content delivery system for OCI artifacts. The centrally stored content is
available:
for direct use by Kubernetes, which controls the applications running in Container as a Service
(CaaS) clusters.
for indirect use by distributed container registries closer to Kubernetes, which controls the
applications running in CaaS clusters.

With the CNF Distribute Software to CCR operation, you can onboard the CNF
software images to the CCR independently from the CNF software upload, CNF deployment, and
CNF upgrade operations.

For more information, see Configuration Management/Configuration Management Operating

Procedures/Managing Cloud Services/CNF Life Cycle Management Operations/CNF Distribute
Software CNF Distribute Software operation - Distributing software to CCR in MantaRay NM
Operating Documentation.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed an OCP cluster. For more information, see Deploying cloud infrastructure.
you have integrated the OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have configured MantaRay NM for life cycle management operations. For more

178 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Start the CNF Distribute Software operation by entering:

/opt/oss/NSN-cmplatform/bin/racclimx.sh -op CNF_Distribute_Software_To_CCR -

cnfSwId <CNF software release name> -v

Table 55: Starting parameters for the CNF Distribute Software operation in
MantaRay NM CLI

Starting parameter Parameter description

-op This parameter defines the operation to be started.

-v This parameter turns on displaying the operation feedback

on the screen.

-planName This parameter specifies the deployment plan name.

-cnfSwId This parameter is optional and defines the CNF software

version imported to the MantaRay NM Software Archive, for
which CNF images are to be distributed. In case the value of
the parameter is not defined, it is taken from the actual
configuration.

For more information on the CLI operations in MantaRay NM, see the Executing command
line operations chapter under Command Line Operations in MantaRay NM Operating
Documentation.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 179

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Postrequisites
You can check the status of the operation in the following places:

Command line
CM Operation Manager›Operation history tab

180 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
9. Deploying a CNF in MantaRay NM without
autoconfiguration

In AirScale Cloud RAN BTS (Cloud RAN BTS), the cloud-native network function (CNF) deployment
is automated with MantaRay NM.

Figure 46: Overview of the CNF deployment without autoconfiguration

CaaS Container-as-a-Service

CCR central container registry

CM Configuration Manager

CSR cell site router

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 181

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
FHGW Nokia AirFrame Fronthaul Gateway

LCM life cycle management

NIC network interface card

Nokia Sync Operator Nokia Advanced Synchronization Operator

OCP Red Hat OpenShift Container Platform

RAN NIC Nokia Cloud RAN SmartNIC

RU radio unit

SCF site configuration file

SWM Software Manager

vCU virtualized gNB central unit

vDU virtualized gNB distributed unit

To deploy a CNF without autoconfiguration, use the CNF Deployment operation. You can start
the CNF Deployment operation using MantaRay NM graphical user interface (GUI), MantaRay
NM CLI, or MantaRay NM REST application programming interface (API).

Note:
If you deploy a CNF without autoconfiguration, you need to commission it with CU WebEM
or vDU WebEM. For more information, see Commissioning Cloud RAN BTS.

The CNF Deployment allows you to also onboard the CNF software package to the CCR. For
more information about the CCR, see Central container registry in Cloud RAN BTS solution.

182 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
9.1 Deploying a CNF without autoconfiguration using
MantaRay NM GUI

The CNF Deployment operation in MantaRay NM allows you to deploy a cloud-native network
function (CNF) without autoconfiguration. You can start the CNF Deployment operation in
MantaRay NM using MantaRay NM graphical user interface (GUI).

Purpose
You can use the CNF Deployment operation in MantaRay NM to deploy the following CNF
objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed the target OCP cluster. For more information, see Deploying cloud
infrastructure.
you have integrated the target OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.
you have created secrets for the CNF. For more information, see Creating secrets for CNF

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 183

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
objects.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.
you have onboarded the CNF software images to container registry. For more information,
see Onboarding software images to the container registry.
before deploying the virtualized gNB distributed unit (vDU), you have deployed the Nokia
AirFrame Fronthaul Gateway (FHGW) . For more information, see Deploying and
commissioning FHGW.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 47: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

3 In the Plans view, right-click on the prepared CNF deployment plan and select Workflow
Engine for Plan.

184 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step example
Figure 48: Opening the Workflow Engine for a selected plan

Step result
The Workflow Engine window pops-up.

4 Go to the Operation list and select Cloud RAN Management - CNF

Deployment.

5 Click the green arrow icon next to the CNF Deployment operation.

Step result
The CNF Deployment dialog pops-up.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 185

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 49: CNF Deployment view

6 In the CNF Deployment dialog, configure the settings for the operation.

6.1 [Optional] Define a name and a description for the operation.

6.2 [Optional] In the Distribute CNF Software field, select if the CNF software
image should be distributed to the target container registry, integrated with
MantaRay NM.

7 Click Start and chose Yes in the confirmation dialog.

Step result
The Feedback dialog opens and the status of the CNF Deployment operation changes
to Started. When the operation is performed successfully, the status changes to
Finished.

186 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Result
When the CNF Deployment operation is finished, the following happens:
All Helm charts are validated.
The namespace is created.
All secrets defined in the plan are created.
All Helm releases defined in the deployment plan are created and the CNF is activated.
The CNF test is executed for the main release.

Postrequisites
You can check the status of the operation in the following places:

Feedback dialog
Workflow Engine›Operation field
CM Operation Manager›Operation history tab

9.2 Deploying a CNF without autoconfiguration using

MantaRay NM CLI

The CNF Deployment operation in MantaRay NM allows you to deploy a cloud-native network
function (CNF) without autoconfiguration. You can start the CNF Deployment operation in
MantaRay NM using MantaRay NM CLI.

Purpose
You can use the CNF Deployment operation in MantaRay NM to deploy the following CNF
objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 187

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed the target OCP cluster. For more information, see Deploying cloud
infrastructure.
you have integrated the target OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.
you have created secrets for the CNF. For more information, see Creating secrets for CNF
objects.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.
you have onboarded the CNF software images to container registry. For more information,
see Onboarding software images to the container registry.
before deploying the virtualized gNB distributed unit (vDU), you have deployed the Nokia
AirFrame Fronthaul Gateway (FHGW) . For more information, see Deploying and
commissioning FHGW.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Start the CNF Deployment operation by entering:

[omc]$ racclimx.sh -op CNF_Deployment -planName <plan name> -v

188 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Table 56: Starting parameters for the CNF Deployment operation in MantaRay NM CLI

Starting parameter Parameter description

-op This parameter defines the operation to be started.

-v This parameter turns on displaying the operation feedback

on the screen.

-planName This parameter defines the plans name.

-distribution This optional parameter defines whether CNF software

images should be distributed to Container Registries before
CNF deployment. The default value of the parameter is
true.

For more information on the CLI operations in MantaRay NM, see the Executing command
line operations chapter under Configuration Management Operating
Procedures/Command Line Operations in MantaRay NM Operating Documentation.

Result
When the CNF Deployment operation is finished, the following happens:
All Helm charts are validated.
The namespace is created.
All secrets defined in the plan are created.
All Helm releases defined in the deployment plan are created and the CNF is activated.
The CNF test is executed for the main release.

Postrequisites
You can check the status of the operation in the following places:

Command line
CM Operation Manager›Operation history tab

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 189

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
9.3 Deploying a CNF without autoconfiguration using
MantaRay NM REST API

The CNF Deployment operation in MantaRay NM allows you to deploy a cloud-native network
function (CNF) without autoconfiguration. You can start the CNF Deployment operation in
MantaRay NM using MantaRay NM REST application programming interface (API).

Purpose
You can use the CNF Deployment operation in MantaRay NM to deploy the following CNF
objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed the target OCP cluster. For more information, see Deploying cloud
infrastructure.
you have integrated the target OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.
you have created secrets for the CNF. For more information, see Creating secrets for CNF

190 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
objects.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.
you have onboarded the CNF software images to container registry. For more information,
see Onboarding software images to the container registry.
before deploying the virtualized gNB distributed unit (vDU), you have deployed the Nokia
AirFrame Fronthaul Gateway (FHGW) . For more information, see Deploying and
commissioning FHGW.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Access the startOperation endpoint of the CM Operations REST API using the HTTP
POST method.

The request should contain the Content-Type header with the multipart/form-data
value.

Step example

https://<cluster hostname>/mantaraynm/cm/open-api/operations/v1/start

3 Start the CNF Deployment operation by placing the following JSON request:

"operationName": "CNF Deployment",

"operationAlias": "<operation alias>",

"operationAttributes": {

"planName": "<plan name>",

"distribution": "<true or false>"

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 191

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For more information on the REST API operations in MantaRay NM, see the Starting an
operation chapter under CM Web Service RESTful API in MantaRay NM Operating
Documentation.

4 Save the operationId returned in the response for future use.

Result
When the CNF Deployment operation is finished, the following happens:
All Helm charts are validated.
The namespace is created.
All secrets defined in the plan are created.
All Helm releases defined in the deployment plan are created and the CNF is activated.
The CNF test is executed for the main release.

Postrequisites
You can check the status of the operation in the following places:

REST API using the saved operationId. For more information, see the Starting an
operation chapter under CM Web Service RESTful API in MantaRay NM Operating
Documentation.
CM Operation Manager›Operation history tab

192 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
10. Deploying a CNF in MantaRay NM with autoconfiguration
(PnP)

In AirScale Cloud RAN BTS (Cloud RAN BTS), the deployment of the virtualized gNB central unit
(vCU) and the virtualized gNB distributed unit (vDU) is automated with MantaRay NM and supports
autoconfiguration with Plug and Play (PnP).

Figure 50: Overview of the CNF deployment with autoconfiguration

CaaS Container-as-a-Service

CCR central container registry

CM Configuration Manager

CSR cell site router

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 193

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
FHGW Nokia AirFrame Fronthaul Gateway

LCM life cycle management

NIC network interface card

Nokia Sync Operator Nokia Advanced Synchronization Operator

OCP Red Hat OpenShift Container Platform

RAN NIC Nokia Cloud RAN SmartNIC

RU radio unit

SCF site configuration file

SWM Software Manager

Cloud RAN BTS supports autoconfiguration of vCU and vDU with the use of PnP. PnP is a
functionality that helps to efficiently deploy new sites by simplifying the planning process and
providing automated site commissioning and configuration once the new site is connected and
identified by MantaRay NM. This means that you can define the cloud-native network function
(CNF) parameters in SCF and import it to MantaRay NM before deploying the vDU or the vCU. For
more information on PnP, see Configuring Radio Network Elements with Plug and Play in
MantaRay NM Operating Documentation.

You can deploy the vCU or the vDU with autoconfiguration using the Unified PnP - Direct
integration planning workflow. The Unified PnP - Direct integration
planning workflow includes the following operations:
Unified PnP - Create BTS configuration plan
Unified PnP - Search and apply Site Template (optional)
Unified PnP - Validate configuration plan
Unified PnP - Activate autoidentification
Unified PnP - Deploying planned CNFs (optional)

In MantaRay NM GUI, you can either start the operations one by one or run the Unified PnP -
One-button planning operation, which automatically starts the next Unified PnP -

194 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Direct integration planning operation when the previous one is successfully
completed.

You can also start the Unified PnP - Direct integration planning workflow in
MantaRay NM CLI. This method is called zero-touch planning, as it allows you to run all Unified
PnP - Direct integration planning operations one by one with a single
Unified_PnP_COAM_Site_Preparation command.

10.1 Deploying a CNF with autoconfiguration using

MantaRay NM GUI (one-button planning)

The Unified PnP - Direct integration planning workflow in MantaRay NM allows

you to deploy a cloud-native network function (CNF) without autoconfiguration. You can start the
Unified PnP - Direct integration planning operations in MantaRay NM using
MantaRay NM graphical user interface (GUI).

Purpose
You can deploy the vCU or the vDU with autoconfiguration using the Unified PnP - Direct
integration planning workflow. The Unified PnP - Direct integration
planning workflow includes the following operations:
Unified PnP - Create BTS configuration plan
Unified PnP - Search and apply Site Template (optional)
Unified PnP - Validate configuration plan
Unified PnP - Activate autoidentification
Unified PnP - Deploying planned CNFs (optional)

In MantaRay NM GUI, you can either start the operations one by one or run the Unified PnP -
One-button planning operation, which automatically starts the next Unified PnP -
Direct integration planning operation when the previous one is successfully
completed.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 195

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
This procedure describes activation of the Unified PnP - One-button planning
operation. Before the start, you need to configure settings for all operations of the
Unified PnP - Direct integration planning workflow. If you want to
manually activate the procedures one by one, configure the settings for a specific
procedure before activating it.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed the target OCP cluster. For more information, see Deploying cloud
infrastructure.
you have integrated the target OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have prepared MantaRay NM for Direct Integration Planning. For more information, see
Configuring Radio Network Elements with Plug and Play in MantaRay NM Operating
Documentation.
you have prepared the network for Direct Integration Planning. For more information, see
Configuring Radio Network Elements with Plug and Play in MantaRay NM Operating
Documentation.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.
you have created secrets for the CNF. For more information, see Creating secrets for CNF
objects.

196 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.
you have onboarded the CNF software images to container registry. For more information,
see Onboarding software images to the container registry.
before deploying the virtualized gNB distributed unit (vDU), you have deployed the Nokia
AirFrame Fronthaul Gateway (FHGW) . For more information, see Deploying and
commissioning FHGW.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 51: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

3 In the Plans view, right-click on the prepared CNF deployment plan and select Workflow
Engine for Plan.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 197

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step example
Figure 52: Opening the Workflow Engine for a selected plan

Step result
The Workflow Engine window pops-up.

4 Go to the Operation list and select Unified PnP - Direct integration

planning.

5 Click the green arrow icon next to the One button planning›Unified PnP - One-
button planning operation.

Step result
The Unified PnP - One-button planning dialog pops up. By running the
Unified PnP - One-button planning operation, you launch the complete planning
process with one action, which automatically triggers all Unified PnP - Direct
integration planning operations in a sequence.

198 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 53: Unified PnP - One-button planning view

6 In the Unified PnP - One-button planning dialog, configure the settings for the
operation.

The Unified PnP - One-button planning sequence includes the following

operations:
Unified PnP - With this operation, you import your deployment plan to
Create BTS MantaRay NM CM. The deployment plan is required in the
configuration plan subsequent workflow steps. As a result, the configuration plan is
updated for the CNF NE in the MantaRay NM plan database and is
selected as default for further workflow operations.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 199

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Unified PnP - With this operation, you can import all necessary NE parameters
Search and Apply using the prepared site configuration file (SCF) and the values
Site Templates override files. Alternatively, the import plan file can contain only a
(optional) subset of CNF parameters and the rest can be defined using the
Site Template operation. A suitable site template, if it exists,
is found by MantaRay NM and applied for a CNF. For more
information on creating site templates, see the Site templates
chapter under CM Editor Help in MantaRay NM Operating
Documentation.

Unified PnP - With this operation, you perform validation of a complete plan. If
Validate the validation fails, you need to correct the plan in MantaRay NM
configuration plan CM Editor and repeat the validation operation.

Unified PnP - With this operation, identification parameters are sent to

Activate Autoconnection (AC) Service.
autoidentification

Unified PnP - With this operation, you can deploy CNFs from the plan. The
Deploy planned operation uses Helm installation to create Helm charts on the vCU
CNFs or vDU side.

Optional steps can be easily disabled if needed.

6.1 [Optional] Define a name and a description for the operation.

You can also provide this information in the dialogs of all Unified PnP - Direct
integration planning operations.

6.2 In the Input file field, select the prepared SCF file.

You can also provide this information in the dialog of the Unified PnP - Create
BTS configuration plan operation.

6.3 In the File format field, select the RAML2 or CSV file format.

You can also provide this information in the dialog of the Unified PnP - Create
BTS configuration plan operation.

6.4 In the UI field, if you used internal parameter values during the SCF preparation, set
the value to No.

You can also provide this information in the dialog of the Unified PnP - Create

200 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
BTS configuration plan operation. For more information, see Configuring
Radio Network Elements with Plug and Play in MantaRay NM Operating
Documentation.

6.5 In the Activate Site Templates field, select if you want to use a site template
during the autoconfiguration planning.

6.6 In the GPS identification used field, set the value to No.

You can also provide this information in the dialog of the Unified PnP -
Activate autoidentification operation.

6.7 In the Maintenance Region DN field, set the maintenance region for the CNF if
you haven't defined it in the SCF.

You can also provide this information in the dialog of the Unified PnP - Create
BTS configuration plan operation.

Note:
TheMRC-1/MR-PNP value is used by default in pnp_autoconnection
service. You can set any other value, but the same one should be configured in
the pnp_autoconnection properties.

7 Click Start and chose Yes in the confirmation dialog.

Step result
The Feedback dialog opens and the status of the Unified PnP - One-button
planning operation changes to Started. When the operation is performed successfully,
the status changes to Finished.

Postrequisites
You can check the status of the operation in the following places:

Feedback dialog
Workflow Engine›Operation field
CM Operation Manager›Operation history tab

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 201

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
10.2 Deploying a CNF with autoconfiguration using
MantaRay NM CLI (zero-touch planning)

The Unified PnP - Direct integration planning workflow in MantaRay NM allows

you to deploy a cloud-native network function (CNF) without autoconfiguration. You can start the
Unified PnP - Direct integration planning operations in MantaRay NM using
MantaRay NM CLI.

Purpose
You can deploy the vCU or the vDU with autoconfiguration using the Unified PnP - Direct
integration planning workflow. The Unified PnP - Direct integration
planning workflow includes the following operations:
Unified PnP - Create BTS configuration plan
Unified PnP - Search and apply Site Template (optional)
Unified PnP - Validate configuration plan
Unified PnP - Activate autoidentification
Unified PnP - Deploying planned CNFs (optional)

You can start the Unified PnP - Direct integration planning workflow in
MantaRay NM CLI. This method is called zero-touch planning, as it allows you to run all Unified
PnP - Direct integration planning operations one by one with a single
Unified_PnP_COAM_Site_Preparation command.

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have integrated the container registry with MantaRay NM. For more information, see
Configuring and integrating CCR with MantaRay NM.
you have deployed the target OCP cluster. For more information, see Deploying cloud
infrastructure.
you have integrated the target OCP cluster with MantaRay NM. For more information, see
Integrating a cloud instance with MantaRay NM.
you have filled in the values override files for the CNF. For more information, see Filling in the
values override files for the vCU or Filling in the values override files for the vDU, or Filling in

202 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
the values override files for the Nokia proprietary Kubernetes operators for Cloud RAN BTS.
you have configured MantaRay NM for life cycle management operations. For more
information, see Configuring MantaRay NM for Cloud RAN BTS life cycle management
operations.
you have prepared MantaRay NM for Direct Integration Planning. For more information, see
Configuring Radio Network Elements with Plug and Play in MantaRay NM Operating
Documentation.
you have prepared the network for Direct Integration Planning. For more information, see
Configuring Radio Network Elements with Plug and Play in MantaRay NM Operating
Documentation.
you have the prepared CNF deployment plan available in MantaRay NM. For more information,
see Creating a CNF deployment plan.
you have updated the CNF deployment plan with the content of the values override files. For
more information, see Updating Helm chart configuration values from values override files.
you have created secrets for the CNF. For more information, see Creating secrets for CNF
objects.
you have onboarded the CNF deployment package to MantaRay NM. For more information,
see Onboarding software packages to MantaRay NM.
you have onboarded the CNF software images to container registry. For more information,
see Onboarding software images to the container registry.
before deploying the virtualized gNB distributed unit (vDU), you have deployed the Nokia
AirFrame Fronthaul Gateway (FHGW) . For more information, see Deploying and
commissioning FHGW.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Start the Unified_PnP_COAM_Site_Preparation operation by entering:

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 203

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
[omc]$ racclimx.sh -op Unified_PnP_COAM_Site_Preparation -planName <plan name> -

fileFormat <RAML2 or CSV> -inputFile <full name of the input file> -profileFile

<name of profile file, used when fileFormat is CSV> -UIValues <true or false> -

activateSiteTemplate <true or false> -maintenanceRegionDn <DN of the maintenance

region to be assigned to the CNF> -deployPlannedCNFs <true or false> -v

Table 57: Starting parameters for the Unified_PnP_COAM_Site_Preparation

operation in MantaRay NM CLI

Starting parameter Parameter description

-op This parameter defines the operation to be started.

-planName This parameter defines the name of the plan to be created

based on the site configuration file (SCF).

-fileFormat This parameter defines the file format as RAML2 or CSV.

-profileFile This parameter defines the name of the profile file. It is used
when the value of the fileFormat parameter is CSV

-UIValues This parameter defines whether internal parameter values

were used during the SCF preparation.

- This parameter defines whether a site template is used during

activateSiteTemplate the autoconfiguration planning.

-maintenanceRegionDn This parameter defines the maintenance region for the CNF if
you haven't defined it in the SCF.

-deployPlannedCNFs This parameter defines whether the deployment of the CNF is

triggered after successful autoconfiguration planning.

-v This parameter turns on displaying the operation feedback on

the screen.

For more information on the CLI operations in MantaRay NM, see the Executing command
line operations chapter under Command Line Operations in MantaRay NM Operating
Documentation.

Postrequisites
You can check the status of the operation in the following places:

204 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Command line
CM Operation Manager›Operation history tab

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 205

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
11. Commissioning Cloud RAN BTS

Commission network elements by configuring the software and the parameters for AirScale
Cloud RAN BTS (Cloud RAN BTS).

Figure 54: Overview of the CNF commissioning

CaaS Container-as-a-Service

CCR central container registry

CM Configuration Manager

CSR cell site router

FHGW Nokia AirFrame Fronthaul Gateway

206 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
LCM life cycle management

NIC network interface card

Nokia Sync Operator Nokia Advanced Synchronization Operator

OCP Red Hat OpenShift Container Platform

RAN NIC Nokia Cloud RAN SmartNIC

RU radio unit

SCF site configuration file

SWM Software Manager

vCU virtualized gNB central unit

vDU virtualized gNB distributed unit

The commissioning process involves software and parameters configurations. For more
information, see:
Site configuration file (SCF)
Parameters and hardware database obtained from a gNB

The Cloud RAN BTS vDU and vCU cloud-native network functions (CNFs) support
autoconfiguration. This means that you can define the parameters in an SCF and import it to
MantaRay NM before deploying the vDU or the vCU. Deploying the vDU or the vCU involves then
creating a deployment plan, importing it to MantaRay NM, and executing the deployment and
autoconfiguration procedure with the network management system (NMS). For instructions, see
Deploying a CNF with autoconfiguration using MantaRay NM GUI (one-button planning).

If you didn't use autoconfiguration when deploying the vCU or the vDU, you can commission the
CNFs after deployment. The commissioning process after deployment covers the following:
1. Software upgrade if necessary. Ensure that you use the correct and compatible AirScale Cloud
RAN BTS software version. For more information, see Software version verification.
2. Initial configuration using an SCF. Once the configuration plan is activated, you need to validate

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 207

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
the SCF file to ensure that AirScale Cloud RAN BTS is working properly. The SCF contains all
necessary configuration details for management, hardware, and transmission for the gNB. For
more information, see Site configuration file.
3. Commissioning with an element manager (EM). With the cloud gNB functional split, you control
and configure each unit separately using a dedicated EM:
vDU WebEM for vDUs. For more information, see Commissioning with vDU WebEM.
CU WebEM for vCUs. For more information, see Commissioning with CU WebEM.
4. Installation and configuration of a gNB connection. You need to configure the connection
between the vCU and vDUs.

11.1 Software version verification

You can use CU WebEM and vDU WebEM to make sure that your version of the AirScale Cloud
RAN BTS (Cloud RAN BTS) software is correct and compatible.

All commissioning tasks ensure that the installation is correct, there are no faulty modules, and
the whole system is ready for the final integration. Once the virtualized gNB distributed unit (vDU)
connects to the virtualized gNB central unit (vCU) for the first time, the vCU starts checking if the
vDU is running a correct software version. To establish communication channels with cloud-native
network functions (CNFs) in the Cloud RAN BTS environment, you need to use the software that is
compatible with the gNB. You need to prepare the software on the hard disk of the system before
you start the commissioning process.

Note:
Always ensure you are using a proper software image that is included in the Cloud RAN BTS
software package. Also check if the CNF and radio units (RUs) software versions are an
exact match for the complete service.

To ensure that you are using a compatible software version:

Download an official gNB software package that has the RELEASED status from Support
Portal.
Check in vDU WebEM and CU WebEM the software version of the gNB and hardware configured
on the site. For more information, see Verifying a software version with vDU WebEM and
Verifying a software version with CU WebEM.

208 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For more information, see the Upgrading Cloud RAN BTS System document.

11.1.1 Verifying a software version with CU WebEM

You can use CU WebEM to check the software version of the virtualized gNB central unit (vCU)
and of the hardware configured on the site.

Procedure
1 Log in to CU WebEM.

2 Go to Navigation Panel›Status›CU Status.

Tip:
You can also check the software release version in the Main Panel bar.
Figure 55: Software information in CU WebEM

3 Check Software release version.

Ensure you are using a proper software image.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 209

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 56: Checking the software version in CU WebEM

11.1.2 Verifying a software version with vDU WebEM

You can use vDU WebEM to check the software version of the virtualized gNB distributed unit
(vDU) and of the hardware configured on the site.

Procedure
1 Log in to vDU WebEM.

2 Go to Navigation Panel›Status›Site Properties.

Tip:
You can also check the software release version in the Main Panel bar.
Figure 57: Software information in vDU WebEM

3 Check Software version under vDU-gNB Properties.

210 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Ensure you are using a proper software image.

Figure 58: Checking the software version in vDU WebEM

11.2 Commissioning with CU WebEM

You can use CU WebEM to create a site configuration file (SCF) and commission the virtualized
gNB central unit (vCU) that was deployed without autoconfiguration.

If you used autoconfiguration when deploying the vCU by following the Deploying a CNF with
autoconfiguration using MantaRay NM GUI (one-button planning) procedure, you do not need to
commission it with CU WebEM.

CU WebEM is a web-based application used for vCU administration, configuration management,

and commissioning. You can use it for various commissioning-related tasks, including:
Loading SCF
Validating SCF
Activating SCF
Saving SCF for the further use

Tip:
Before using CU WebEM for the first time, make sure that you use:
a recommended browser.
the correct software version of the vCU and of the hardware configured on the site.
For more information, see Verifying a software version with CU WebEM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 211

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
For more information, see the CU WebEM User Guide document.

11.2.1 Loading an SCF to CU WebEM

You can upload a prepared site configuration file (SCF) with a configuration plan using CU WebEM.

Before you start

Make sure that:

the virtualized gNB central unit (vCU) is successfully deployed.
CU WebEM is opened and a connection to the vCU is established.
the SCF file is correctly configured and ready for gNB commissioning.
the SCF file containing the full vCU configuration is available on your workstation or local drive.
The SCF template comes with a software package that can be downloaded from Support
Portal. For more information on configuration using CU WebEM, see Creating a configuration
plan in CU WebEM, and for more information on using SCF files, see Configuring vCU
parameters in SCF.
the maximum number of plans allowed in CU WebEM is not reached.

Procedure
1 Log in to CU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

3 Select Load SCF File.

Step result
A new window pops up.

212 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 59: Loading an SCF file

4 Click Browse and navigate to the SCF file on your local device.

5 Name the new plan.

6 [Optional] Fill in the Plan description field.

7 [Optional] Validate the new plan.

Before activating a plan, you need to validate it. To validate the SCF file while loading it, check
Yes. If you want to validate the SCF later, check No.

Step example
Figure 60: Creating an example plan by uploading a test SCF file

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 213

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
8 Click Load SCF.

Wait until the SCF file is uploaded. The green check mark icons in the Load SCF Status
indicate the steps of the process that have been completed.

Step example
Figure 61: Loading an SCF progress bar

9 Click Close.

Result
The new configuration plan is uploaded and visible in the Planned Configurations view.
New objects are added and parameter values are defined.

Postrequisites
You need to validate the plan before activating it in CU WebEM. For instructions, see Validating an
SCF in CU WebEM.

Once you commission and configure the connection between the vCU and the virtualized gNB
distributed unit (vDU), you can verify the connection status in CU WebEM. For more information,
see Verifying vCU-vDU connection.

214 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
11.2.2 Creating a configuration plan in CU WebEM

You can create a configuration plan from scratch using the Parameter Editor in CU WebEM.

Before you start

For parameters and their values used to configure the gNB, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document, and the
vCU and vDU parameters chapter.

Note:
Most parameters are not included in this procedure. For more information, see vCU and
vDU parameters.

Procedure
1 Log in to CU WebEM.

2 Go to the Navigation Panel›Configuration›Parameter Editor.

3 From the top menu, select Create Plan.

Step result
The new window pops up.

4 Type the new configuration plan name.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 215

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 62: Creating a new plan in CU WebEM

5 [Optional] Fill in the Plan description field.

6 [Optional] Duplicate the configuration from the already existing plan.

This is applicable if the plan is already uploaded, for example, with a site configuration file
(SCF) template. Download the SCF file from Support Portal and save it on your workstation
or local drive. For more information, see Loading an SCF to CU WebEM.
Check the Duplicate plan from box and, from the drop-down list, choose the plan
that you want to duplicate.

Step example
Figure 63: Duplicating a configuration plan

216 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
Every object and parameter from the chosen plan is duplicated to the new plan.

7 Click OK.

Step result
The plan creation operation starts. A notification appears in the bottom right-hand corner.

The new configuration plan is successfully created and visible under the Planned
Configurations view.

8 Select your plan from the Planned configurations.

Figure 64: Selecting planned configurations

9 Create the base object.

9.1 Click the Add button.

Figure 65: Adding the base object in CU WebEM

Step result
A new window pops up.

9.2 Insert the MRTBTS ID of the added object.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 217

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 66: Adding MRBTS ID

9.3 Click OK.

Step result
The successful operation notification appears in the bottom right-hand corner, and the new
object is visible in the Objects panel.

10 Set values for new object parameters.

Insert values for the MRBTS BTS name (btsName) and Multi Radio BTS Instance
Id (mrbtsId) parameters.
Figure 67: Adding MRBTS parameters in CU WebEM

11 Add a new object in the Objects panel.

11.1 Click the icon.

Step result
The new window pops up.

218 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 68: Adding a new object

11.2 From the drop-down list, select a class name.

Figure 69: Selecting a class name

11.3 [Optional] Load the default value for a chosen object class.

You can automatically set the default values for objects with defined default values by
checking the Load default values box.

11.4 Insert the ID of the added object.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 219

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 70: Adding the object ID

11.5 Click OK.

Step result
The successful operation notification appears in the bottom right-hand corner and the new
object is added under the object tree view in the Objects panel.

You can manage the created objects using:

to add a new object.
to copy an existing object.
to remove an object.

12 [Optional] Repeat step 11. Add a new object in the Objects panel to add all new required
objects.

13 Fill in all mandatory parameters marked with from the MRBTS tree with the correct values.

Mandatory parameters are required for the gNB to work properly. Expand the MRBTS list and
fill in the parameters according to the displayed messages regarding missing or invalid
parameters for your new plan. The icon indicates mandatory parameters, and the icon
indicates invalid parameter values.
To properly connect the vCU to the vDU, you need to set up:
the parameters listed in Table: vCU parameters required for a working connection to vDU
using CU WebEM.
the parameters listed in Table: vDU parameters required for a working connection to vCU
using vDU WebEM.

You can also configure these parameters using an SCF. For more information, see
Configuring vCU parameters in SCF and Configuring vDU parameters in SCF.

220 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Note:
Additionally, parameters must be set in vDU WebEM. For more information, see
Creating a configuration plan in vDU WebEM.

For more information on parameter validation, see Validating an SCF in CU WebEM.

Figure 71: Adding all mandatory parameter values

Result
The new configuration plan is uploaded and visible in the Planned Configurations view.
New objects are added and the parameter values are defined.

Postrequisites
Validate the plan before activating it in CU WebEM. For instructions, see Validating an SCF in CU
WebEM.

You can save your configuration plan for further use. For more information, see Saving an SCF in
CU WebEM.

Once you commission and configure the connection between the vCU and the virtualized gNB
distributed unit (vDU), you can verify the connection status in CU WebEM. For more information,
see Verifying vCU-vDU connection.

11.2.3 Validating an SCF in CU WebEM

You can validate a configuration plan in CU WebEM after uploading a site configuration file (SCF).

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 221

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Before you start

Make sure that CU WebEM is opened and a connection to the virtualized gNB central unit
(vCU) is established.
Load the SCF file to CU WebEM. For instructions, see Loading an SCF to CU WebEM.

Notice:
For any cell addition or reconfiguration, be sure to check the cell parameters by using the
Adaptive PDCCH Configuration Tool. This is mandatory to make sure that the cell
configuration is correct and potential configuration errors are eliminated.

Procedure
1 Log in to CU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

3 From the drop-down list, choose the configuration plan you need to validate.

Note:
The Validate Plan button is active in the Delta configurations and
Planned configurations views.

222 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 72: Selecting a plan for validation

4 In the top menu, click Validate Plan.

Step result
The validation is finished, and a notification appears in the bottom right-hand corner. If any
error occurs during validation, the red dot appears on the Errors tab.

Figure 73: Displaying validation errors

5 [Optional] Correct any errors that have appeared during the validation.

5.1 Go to the Errors tab, and verify a particular error type in a chosen plan.

Missing Mandatory Objects displays missing mandatory parameters

Parameter Errors displays parameter values out of range
Objects Quantity Errors displays objects for which the quantity is out of
range
Global Relation Errors displays violated global requirements and
configuration rules
Parameter Relation Errors displays conflicting parameter values

For more details on error troubleshooting, see the CU WebEM User Guide
document.

5.2 [Option 1] To manually fix errors, insert the correct value or select it from the drop-
down list in the Value field.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 223

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
5.3 [Option 2] To automatically create all missing mandatory objects, click Fix
Errors, and select the missing instances you want to create for a configuration plan
you want to edit.

Step result
All errors are fixed and validation is successful.

Postrequisites
Once the SCF is uploaded and validated, you can activate the configuration plan in CU WebEM. For
instructions, see Activating an SCF in CU WebEM.

11.2.4 Activating an SCF in CU WebEM

You can activate the successfully uploaded and validated plan from a site configuration file (SCF)
using CU WebEM.

Before you start

Make sure that CU WebEM is opened and a connection to the virtualized gNB central unit
(vCU) is established.
Load the SCF file to CU WebEM. For instructions, see Loading an SCF to CU WebEM.
Validate the configuration plan in CU WebEM. For instructions, see Validating an SCF in CU
WebEM.

Procedure
1 Log in to CU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

3 From the drop-down list, choose the planned configuration you want to activate.

4 In the top menu, click Activate Plan.

Select from the available options

224 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
The caution window pops up.
Figure 74: Activating configuration plan

5 In the Activating configuration plan window, choose the operation to be

executed.

Select from the available options

Check the Download plan without activation box and click Execute to save
the plan under Inactive configurations.
Click Execute to activate the plan, then click Continue to trigger the vCU reset once
the activation is finished.

Step result
If you check the Download plan without activation box and click Execute, the
downloading progress window appears. Once the download is complete, you can close the
window by clicking the Close button.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 225

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 75: Downloading plan without activation

If you click the Execute button without checking the Download plan without
activation box, the activation process starts and the progress window appears. The
activation process consists of four phases:
1. Plan activation started
2. Plan download
3. Plan validation
4. Plan activation finished

Figure 76: Activating plan progress bar

After the plan validation phase, the caution window pops up and you need to click

226 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Continue to trigger the vCU reset.

Figure 77: vCU reset notification

Once the activation process is completed, a notification pops up in the bottom right-hand
corner.

Figure 78: Successful plan activation

Result
The configuration plan is successfully activated and visible under the Active configuration
view. vCU reset is triggered. Cloud infrastructure and cells are available in the Status view and

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 227

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
ready for setup.

Postrequisites
Once you commission and configure the connection between the vCU and the virtualized gNB
distributed unit (vDU), you can verify the connection status in CU WebEM. For more information,
see Verifying vCU-vDU connection.

11.2.5 Saving an SCF in CU WebEM

You can save a site configuration file (SCF) using CU WebEM to back up your site configuration.

Procedure
1 Log in to CU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

Tip:
You can also save an SCF from Dashboard›Operation widget›CU
Operations by clicking the Save configuration button.
Figure 79: Saving the SCF from the Dashboard widget

3 Click the Save Plan button.

228 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
4 Select the required variant.

Figure 80: Saving an SCF in CU WebEM

5 Click OK.

Step result
The notification appears in the bottom right-hand corner. The SCF is saved in the default
download location on your local device.

11.3 Commissioning with vDU WebEM

You can use vDU WebEM to create a site configuration file (SCF) and commission the virtualized
gNB central unit (vCU) that was deployed without autoconfiguration.

If you used autoconfiguration when deploying the vDU by following the Deploying a CNF with
autoconfiguration using MantaRay NM GUI (one-button planning) procedure, you do not need to
commission it with vDU WebEM.

vDU WebEM is a web-based application for vDU maintenance, configuration management, and
commissioning. You can use it for various commissioning-related tasks, including:
Loading SCF
Creating SCF manually
Validating SCF
Activating SCF
Saving SCF for the further use

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 229

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Tip:
Before using vDU WebEM for the first time, make sure that you use:
a recommended browser.
the correct software version of the vDU and of the hardware configured on the site.
For more information, see Verifying a software version with vDU WebEM.

For more information, see the vDU WebEM User Guide document.

11.3.1 Loading an SCF to vDU WebEM

You can upload a prepared site configuration file (SCF) with a configuration plan using vDU
WebEM.

Before you start

Make sure that:

the virtualized gNB distributed unit (vDU) is successfully deployed.
vDU WebEM is opened and a connection to the vDU is established.
the SCF file is correctly configured and ready for gNB commissioning.
the SCF file containing the full vDU configuration is available on your workstation or local
drive. The SCF template comes with a software package that can be downloaded from
Support Portal. For more information on configuration using vDU WebEM, see Creating a
configuration plan in vDU WebEM, and for more information on using an SCF file, see
Configuring vDU parameters in SCF.
the maximum number of plans allowed in vDU WebEM is not reached.

Procedure
1 Log in to vDU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

3 Select Load SCF File.

230 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
The new window pops up.
Figure 81: Loading an SCF file

4 Click Browse and navigate to the SCF file on your local device.

5 Name the new plan.

6 [Optional] Fill in the Plan description field

7 [Optional] Validate the new plan.

Before activating a plan, you need to validate it. To validate the SCF file while loading it, check
Yes. If you want to validate the SCF later, check No.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 231

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 82: Creating an example plan by uploading a test SCF file

8 Click Load SCF.

Step result
Wait until the SCF file is uploaded. The green check mark icons in the Load SCF Status
indicate the steps of the process that have been completed.
Figure 83: Loading an SCF progress bar

9 Click Close.

232 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Result
The new configuration plan is uploaded and visible in the Planned Configurations view.
New objects are added and parameter values are defined.

Postrequisites
You need to validate the plan before activating it in vDU WebEM. For instructions, see Validating
an SCF in vDU WebEM.

Once you commission and configure the connection between the vDU and the virtualized gNB
central unit (vCU), you can verify the connection status in CU WebEM. For more information, see
Verifying vCU-vDU connection.

11.3.2 Creating a configuration plan in vDU WebEM

You can create a configuration plan from scratch using the Parameter Editor in vDU WebEM.

Before you start

For parameters and their values used to configure the gNB, see the Reference
Documentation/Reference document/AirScale Cloud RAN BTS Parameters document, and the
vCU and vDU parameters chapter.

Note:
Most parameters are not included in this procedure. For more information, see vCU and
vDU parameters.

Procedure
1 Log in to vDU WebEM.

2 Go to the Navigation Panel›Configuration›Parameter Editor.

3 From the top menu, select Create Plan.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 233

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Step result
The new window pops up.

4 Type the new configuration plan name.

Figure 84: Creating a new plan in vDU WebEM

5 [Optional] Fill in the Plan description field.

6 [Optional] Duplicate the configuration from the already existing plan.

This is applicable if the plan is already uploaded, for example, with a site configuration file
(SCF) template. Download the SCF file from Support Portal and save it on your workstation
or local drive. For more information, see Loading an SCF to vDU WebEM.
Check the Duplicate plan from box and choose the plan that you want to duplicate
from the drop-down list.

Step example

234 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 85: Duplicating a configuration plan

Step result
Every object and parameter from the chosen plan is duplicated to the new plan.

7 Click OK.

Step result
The plan creation operation starts. A notification appears in the bottom right-hand corner.

The new configuration plan is successfully created and visible under the Planned
Configurations view.

8 Select your plan from the Planned configurations.

Select your newly created configuration plan from the drop-down list.
Figure 86: Selecting planned configurations

9 Add a new MRBTS instance in the Objects panel.

By default, the parent object is the MRBTS instance.

9.1 Click the Add button.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 235

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
9.2 Insert the ID of an added object.

9.3 Confirm by clicking OK.

Step result
Successful operation notification appears in the bottom right-hand corner

and the new object is visible in the Objects panel.

10 Set values for new object parameters.

Insert values for BTS name and Multi Radio BTS Instance Id.

11 Add a new object in the Objects panel.

11.1 Click the icon.

Step result
A new window pops up.
Figure 87: Adding a new object

11.2 Select a class name from the drop-down list.

11.3 [Optional] Load the default value for a chosen object class.

You can automatically set the default values for objects with defined default values.
Check the Load default values box.

236 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
11.4 Insert the ID of the added object.

11.5 Click OK.

Step result
The successful operation notification appears in the bottom right-hand corner and the new
object is added under the object tree view in the Objects panel.

Manage created objects using:

to add a new object.
to copy an existing object.
to remove an object.

12 [Optional] Repeat step 11. Add a new object in the Objects panel to add all required new
objects.

13 Fill in all mandatory parameters marked with from the MRBTS tree with the correct values.

Mandatory parameters are required for the gNB to work properly. Expand the MRBTS list and
fill in the parameters according to the displayed messages regarding missing or invalid
parameters for your new plan. The icon indicates mandatory parameters, and the icon
indicates invalid parameter values.
To connect the vCU to the vDU, you need to set up:
the parameters listed in Table: vCU parameters required for a working connection to vDU
using CU WebEM.
the parameters listed in Table: vDU parameters required for a working connection to vCU
using vDU WebEM.

You can also configure these parameters using an SCF. For more information, see
Configuring vCU parameters in SCF and Configuring vDU parameters in SCF.

Note:
Additionally, parameters must be set in the CU WebEM. For more information, see
Creating a configuration plan in CU WebEM.

For more information on parameter validation, see Validating an SCF in vDU WebEM.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 237

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Result
The new configuration plan is uploaded and visible in the Planned Configurations view.
New objects are added and the parameter values are defined.

Postrequisites
Validate the plan before activating it in vDU WebEM. For instructions, see Validating an SCF in vDU
WebEM.

You can save your configuration plan for further use. For more information, see Saving an SCF in
vDU WebEM.

Once you commission and configure the connection between the vDU and the virtualized gNB
central unit (vCU), you can verify the connection status in CU WebEM. For more information, see
Verifying vCU-vDU connection.

11.3.3 Validating an SCF in vDU WebEM

You can validate a configuration plan in vDU WebEM after uploading a site configuration file (SCF).

Before you start

Make sure that vDU WebEM is opened and a connection to the virtualized gNB distributed unit
(vDU) is established.
Load the SCF file to vDU WebEM. For instructions, see Loading an SCF to vDU WebEM.

Notice:
For any cell addition or reconfiguration, be sure to check the cell parameters by using the
Adaptive PDCCH Configuration Tool. This is mandatory to make sure that the cell
configuration is correct and potential configuration errors are eliminated.

Procedure
1 Log in to vDU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

238 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
3 From the drop-down list, choose the configuration plan you need to validate.

Note:
The Validate Plan button is active in the Delta configurations and
Planned configurations views.

Figure 88: Selecting a plan for validation

4 In the top menu, click Validate Plan.

Step result
The validation is finished, and a notification appears in the bottom right-hand corner. If any
error occurs during validation, the red dot appears on the Errors tab.

Figure 89: Displaying validation errors

5 [Optional] Correct any errors that have appeared during the validation.

5.1 Go to the Errors tab, and verify a particular error type in a chosen plan.

Missing Mandatory Objects displays missing mandatory parameters

Parameter Errors displays parameter values out of range
Objects Quantity Errors displays objects for which the quantity is out of
range
Global Relation Errors displays violated global requirements and
configuration rules

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 239

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Parameter Relation Errors displays conflicting parameter values

For more details on error troubleshooting, see the CU WebEM User Guide
document.

5.2 [Option 1] To manually fix errors, insert the correct value or select it from the drop-
down list in the Value field.

5.3 [Option 2] To automatically create all missing mandatory objects, click Fix
Errors, and select the missing instances you want to create for a configuration plan
you want to edit.

Step result
All errors are fixed and validation is successful.

Postrequisites
Once the SCF is uploaded and validated, you can activate the configuration plan in vDU WebEM.
For instructions, see Activating an SCF in vDU WebEM.

11.3.4 Activating an SCF in vDU WebEM

You can activate the successfully uploaded and validated plan from a site configuration file (SCF)
using vDU WebEM.

Before you start

Make sure that vDU WebEM is opened and a connection to the virtualized gNB distributed unit
(vDU) is established.
Load the SCF file to vDU WebEM. For instructions, see Loading an SCF to vDU WebEM.
Validate the configuration plan in vDU WebEM. For instructions, see Validating an SCF in vDU
WebEM.

Procedure
1 Log in to vDU WebEM.

240 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
2 Go to Navigation Panel›Configuration›Parameter Editor.

3 From the drop-down list, choose the planned configuration you want to activate.

4 In the top menu, click Activate Plan.

Step result
The caution window pops up.
Figure 90: Activating configuration plan

5 In the Activating configuration plan window, choose the operation to be

executed.

Select from the available options

Check the Download plan without activation box and click Execute to save
the plan under Inactive configurations.
Click Execute to activate the plan, then click Continue to trigger the vDU reset once
the activation is finished.

Step result
If you check the Download plan without activation box and click Execute, the
downloading progress window appears. Once the download is complete, you can close the
window by clicking the Close button.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 241

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 91: Downloading plan without activation

If you click the Execute button without checking the Download plan without
activation box, the activation process starts and the progress window appears. The
activation process consists of four phases:
1. Plan activation started
2. Plan download
3. Plan validation
4. Plan activation finished

Figure 92: Activating plan progress bar

After the plan validation phase, the caution window pops up and you need to click

242 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Continue to trigger the vDU reset.

Figure 93: vDU reset notification

Once the activation process is completed, a notification pops up in the bottom right-hand
corner.

Figure 94: Successful plan activation

Result
The configuration plan is successfully activated and visible under the Active configuration
view. vDU reset is triggered. Radio modules, antenna line devices (ALDs), cloud infrastructure

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 243

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
(pods), and cells are available in the Status view and ready for setup.

Postrequisites
Once you commission and configure the connection between the vDU and the virtualized gNB
central unit (vCU), you can verify the connection status in CU WebEM. For more information, see
Verifying vCU-vDU connection.

11.3.5 Saving an SCF in vDU WebEM

You can save a site configuration file (SCF) using vDU WebEM to back up your site configuration.

Procedure
1 Log in to vDU WebEM.

2 Go to Navigation Panel›Configuration›Parameter Editor.

Tip:
You can also save an SCF from Dashboard›Operation widget›vDU
Operations by clicking the Save configuration button.
Figure 95: Saving the SCF from the Dashboard widget

3 Click the Save Plan button.

4 Select the required variant.

244 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 96: Saving an SCF in vDU WebEM

5 Click OK.

Step result
The notification appears in the bottom right-hand corner. The SCF is saved in the default
download location on your local device.

11.4 Verifying vCU-vDU connection

You can use CU WebEM to verify that the virtualized gNB central unit (vCU) is properly connected
to the virtualized gNB distributed unit (vDU).

Procedure
1 Log in to CU WebEM.

2 Go to Dashboard›DUs Status Summary or Navigation Panel›Status›DUs

Status.

3 Verify that the vDU is displayed and has F1 link status Available.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 245

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 97: Verifying vCU and vDU connection

246 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
12. Terminating a CNF in MantaRay NM

In AirScale Cloud RAN BTS (Cloud RAN BTS), the cloud-native network function (CNF) termination
is automated with MantaRay NM. To terminate a CNF, use the CNF Termination operation.
You can start it using MantaRay NM graphical user interface (GUI), MantaRay NM CLI, or MantaRay
NM REST application programming interface (API).

Figure 98: Overview of the CNF termination

CaaS Container-as-a-Service

CCR central container registry

CM Configuration Manager

CSR cell site router

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 247

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
FHGW Nokia AirFrame Fronthaul Gateway

LCM life cycle management

NIC network interface card

Nokia Sync Operator Nokia Advanced Synchronization Operator

OCP Red Hat OpenShift Container Platform

RAN NIC Nokia Cloud RAN SmartNIC

RU radio unit

SWM Software Manager

vCU virtualized gNB central unit

vDU virtualized gNB distributed unit

12.1 Creating a CNF termination plan

You need a termination plan to trigger the cloud-native network function (CNF) termination
operation in MantaRay NM. You can prepare a termination plan file in a text editor and import it to
MantaRay NM, or create it in MantaRay NM Configuration Management (CM) Editor.

In AirScale Cloud RAN BTS (Cloud RAN BTS), CNF termination is automated with MantaRay NM. To
perform any operation on the MantaRay NM CNF object, you need first to create a termination
plan.

MantaRay NM defines the following network elements as CNF objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

248 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
You can create a termination plan for a CNF object using:
a text editor. For more information, see Creating a termination plan using a text editor.
MantaRay NM Configuration Management (CM) Editor. For more information, see Creating a
termination plan using MantaRay NM GUI.

12.1.1 Creating a termination plan using a text editor

You can create a cloud-native network function (CNF) termination plan using a text editor and
manually import it to MantaRay NM Configuration Management (CM) Operations Manager.

Purpose
If you use a text editor, prepare a plan in one of the following formats:

RAML2.0
CSV
Simple CSV

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have the ID of the CNF you want to terminate.

Procedure
1 Create a termination plan file using a text editor.

Use the CNF ID.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 249

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE raml SYSTEM 'raml20.dtd'>

<raml version="2.0" xmlns="raml20.xsd">

<cmData type="plan" scope="all" name="Plan-CNF-terminate "

id="PlanConfiguration( 100 )">

<header>

<log dateTime="2023-06-16-05-31-47" action="created"

appInfo="PlanExporter">UIValues are used</log>

</header>

<managedObject class="com.nokia.cnf.lcm:CNF" version="CNF1.0"

distName="PLMN-PLMN/<CNF ID>" operation="delete"/>

</cmData>

</raml>

2 Import the termination plan to MantaRay NM.

2.1 Log in to the MantaRay NM start page using a web browser.

2.2 Select Configuration›CM Operations Manager.

2.3 From the top menu bar, select File›Import.

Step result
The Import window pops up.

2.4 Select the plan file to be imported, edit the plan name, and import options if
necessary.

2.5 Click Start.

12.1.2 Creating a termination plan using MantaRay NM GUI

You can create a cloud-native network function (CNF) termination plan with MantaRay NM
Configuration Management (CM) Editor.

250 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have the ID of the CNF you want to terminate.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result
Figure 99: MantaRay NM start page

2 Select Configuration ›CM Editor.

2.1 In the Opening cmedit.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Editor Java application opens.

3 From the top menu bar, select Plan›New Plan.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 251

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 100: Creating a new plan in CM Editor›Plan

Step result
The new plan is added to the navigation tree. The Plan Header view is shown in the main
view. You can modify the plan name that has been automatically assigned by the application.

4 In the Plan Header view, define the plan parameters.

Step example

252 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 101: Plan Header view

4.1 Type a new name and a description for the plan.

Note:
Maximum length of a plan name is 200 characters.

5 Click Update.

Step result
The new plan name and the plan parameters you have configured have been saved.

6 In the navigation tree on the left-hand side, expand the plan, and from the Managed
Objects select the PLMN-xxx root object.

7 Expand the PLMN-xxx root object and select the CNF object you want to delete.

8 Right-click on the selected CNF object and select Change to Delete.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 253

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
12.2 Terminating a CNF using MantaRay NM GUI

The CNF Terminate operation in MantaRay NM allows you to terminate a cloud-native network
function (CNF). You can start the CNF Termination operation in MantaRay NM using MantaRay
NM graphical user interface (GUI).

Purpose
You can use the CNF Terminate operation in MantaRay NM to terminate the following CNF
objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have the ID of the CNF you want to terminate.
you have the prepared CNF termination plan available in MantaRay NM. For more information,
see Creating a CNF termination plan.

Procedure
1 Log in to the MantaRay NM start page using a web browser.

Step result

254 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 102: MantaRay NM start page view

2 Select Configuration›CM Operations Manager.

2.1 In the Opening racpmc.jnlp dialog window, click use Java Web Start
Launcher.

2.2 Confirm all security questions about the digital signature and software provider.

Step result
The CM Operations Manager Java application opens.

3 In the Plans view, right-click on the prepared CNF termination plan and select Workflow
Engine for Plan.

Step example

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 255

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 103: Opening the Workflow Engine for a selected plan

Step result
The Workflow Engine window pops-up.

4 In Workflow Engine, go to the Operation list and select Cloud RAN

Management.

5 Click the green arrow icon next to the CNF Terminate operation.

Step result
The CNF Terminate dialog pops-up.

256 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Figure 104: CNF Terminate view

6 In the CNF Terminate dialog, configure the settings for the operation.

6.1 [Optional] Define a name and a description for the operation.

6.2 [Optional] In the Deintegrate MRBTS field, select Yes to deintegrate the
associated MRBTS objects (neRelId) from the actual configuration.

6.3 [Optional] In the Delete k8s objects field, select the secret and namespace
objects to delete them from the Kubernetes cluster together with the CNF object.

7 Click Start and chose Yes in the confirmation dialog.

Step result
The Feedback dialog opens and the status of the CNF Terminate operation changes to
Started. When the operation is performed successfully, the status changes to Finished.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 257

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Result
When the CNF Terminate operation is finished, the following happens:

Associated MRBTS objects are deintegrated based on the configured settings.

The CNF instance is removed from the Kubernetes cluster.
The secret and namespace objects are removed from the Kubernetes cluster based on the
configured settings.
The CNF MO is removed from the actual configuration.

Postrequisites
You can check the status of the operation in the following places:

Feedback dialog
Workflow Engine›Operation field
CM Operation Manager›Operation history tab

12.3 Terminating a CNF using MantaRay NM CLI

The CNF Terminate operation in MantaRay NM allows you to terminate a cloud-native network
function (CNF). You can start the CNF Terminate operation in MantaRay NM using MantaRay
NM CLI.

Purpose
You can use the CNF Terminate operation in MantaRay NM to terminate the following CNF
objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have the ID of the CNF you want to terminate.

258 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
you have the prepared CNF termination plan available in MantaRay NM. For more information,
see Creating a CNF termination plan.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Start the CNF Terminate operation by entering:

[omc]$ racclimx.sh -op CNF_Terminate -planName <plan name> -

deintegrateMRBTS false -deleteK8sObjects namespace -v

Table 58: Starting parameters for the CNF Terminate operation in MantaRay NM CLI

Starting parameter Parameter description

-op This parameter defines the operation to be started.

-v This parameter turns on displaying the operation feedback

on the screen.

-deintegrateMRBTS This parameter defines whether the associated MRBTS

objects (neRelId) should be deintegrated from the actual
configuration.

-deleteK8sObjects This parameter defines whether the secret and

namespace objects should be deleted from the
Kubernetes cluster together with the CNF object.

For more information on the CLI operations in MantaRay NM, see the Executing command
line operations chapter under Command Line Operations in MantaRay NM Operating
Documentation.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 259

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Result
When the CNF Terminate operation is finished, the following happens:

Associated MRBTS objects are deintegrated based on the configured settings.

The CNF instance is removed from the Kubernetes cluster.
The secret and namespace objects are removed from the Kubernetes cluster based on the
configured settings.
The CNF MO is removed from the actual configuration.

Postrequisites
You can check the status of the operation in the following places:

Command line
CM Operation Manager›Operation history tab

12.4 Terminating a CNF using MantaRay NM REST API

The CNF Termination operation in MantaRay NM allows you to terminate a cloud-native

network function (CNF). You can start the CNF Termination operation in MantaRay NM using
MantaRay NM REST application programming interface (API).

Purpose
You can use the CNF Termination operation in MantaRay NM to terminate the following CNF
objects:

Virtualized gNB central unit (vCU)

Virtualized gNB distributed unit (vDU)
Nokia proprietary Kubernetes operators for Cloud RAN BTS

Before you start

Make sure that:

you have the required roles and permissions in MantaRay NM. For more information, see
Configuring MantaRay NM for Cloud RAN BTS life cycle management operations.
you have the ID of the CNF you want to terminate.
you have the prepared CNF termination plan available in MantaRay NM. For more information,

260 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
see Creating a CNF termination plan.

Procedure
1 Log in as the omc user to the WAS MantaRay NM virtual machine (VM) node.

Note:
To locate the VM, see the Locating the right virtual machine for a service chapter in
MantaRay NM Operating Documentation.

2 Access the startOperation endpoint of the CM Operations REST API using the HTTP
POST method.

The request should contain the Content-Type header with the multipart/form-data
value.

Step example

https://<cluster hostname>/mantaraynm/cm/open-api/operations/v1/start

3 Start the CNF Terminate operation by placing the following JSON request:

"operationName": "CNF Terminate",

"operationAlias": "<operation alias>",

"operationAttributes": {

"planName": "<plan name>",

"deintegrateMRBTS": "<true or false, default value true, optional parameter>",

"deleteK8sObjects": "<none, namespace, or secrets, default value none, optional

parameter>"

For more information on the REST API operations in MantaRay NM, see the Starting an
operation chapter under CM Web Service RESTful API in MantaRay NM Operating
Documentation.

4 Save the operationId returned in the response for future use.

Issue 01 DRAFT. © 2024 Nokia. Nokia Confidential Information 261

Use subject to agreed restrictions on disclosure and use.

Deploying, Commissioning, and Integrating Cloud RAN BTS

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to pekka.ahonen@nokia.com on 12-03-2024.
Result
When the CNF Terminate operation is finished, the following happens:

Associated MRBTS objects are deintegrated based on the configured settings.

The CNF instance is removed from the Kubernetes cluster.
The secret and namespace objects are removed from the Kubernetes cluster based on the
configured settings.
The CNF MO is removed from the actual configuration.

Postrequisites
You can check the status of the operation in the following places:

REST API using the saved operationId. For more information, see the Starting an
operation chapter under CM Web Service RESTful API in MantaRay NM Operating
Documentation.
CM Operation Manager›Operation history tab

262 © 2024 Nokia. Nokia Confidential Information Issue 01 DRAFT

Use subject to agreed restrictions on disclosure and use.