Rakuten Symphony Company
5G_CU Manual Deployment Guide (NSA)
Build version: 3800_dsch Build #6
DRAFT VERSION: 1.0
DRAFT DATE: FEBRUARY 17, 2022
MOP Execution Duration: 60 minutes
Outage Risk Level: Low
MOP Complexity: Low
MOP Priority: Low
IMPORTANT
The user must read, understand, and follow the Warnings, Notes and Information provided.
It is imperative that this document be read and implemented in its entirety with no deviations from the
procedures as written. It is the responsibility of the person(s) implementing this Activity Plan to ensure
proper system operation with minimum service interruption.
Purpose: The purpose of this document is to ensure that all of the steps required to be taken in the
initiation of a customer system or product upgrade or install have been assigned and understood by all of
the parties involved. An Activity Plan is required prior to on-site personnel performing any changes on a
customer’s system. This document provides a high-level overview of the procedure for performing any
hardware and software configuration changes at a site. It is intended to inform the on-site personnel of
the work to be performed, regardless of whether the system is accepted or in commercial service.
This MOP is based on template version: 8.5
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 2 of 13
Table of Contents
Revision History ................................................................................................................................................... 3
1 Special Considerations ................................................................................................................................. 4
1.1 Scope .................................................................................................................................................... 4
1.2 Required Access ................................................................................................................................... 4
1.3 Dependencies....................................................................................................................................... 4
2 Description ................................................................................................................................................... 5
3 Installation / Upgrade steps: ........................................................................................................................ 5
4 Post Installation Checks: ............................................................................................................................ 12
5 Post Deletion Checks:................................................................................................................................. 13
6 CU Installation with Altiostar self-signed certificate- ................................................................................ 13
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 3 of 13
Revision History
Revision Changes/Comments Date Author
1.0 Initial Version 17-February-2020 Bidesh Sarkar
1.1
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 4 of 13
1 Special Considerations
1.1 Scope
This MOP provides steps for 5G DU-CU 3800_dsch Build #6 build installation. It covers the steps for fresh
Installation of DU and CU. It does not cover upgrade steps.
The following required logins should be available prior to this MOP for new nodes:
1.2 Required Access
Network Element User ID/PASSWORD
Image Repository Artifactory XXXX/XXXX
DU cluster (Primary master host) XXXX/XXXX
CU cluster (Primary master host) XXXX/XXXX
1.3 Dependencies
The following list provides the dependencies for the successful implementation of this MOP
1. All the hosts are in “Ready|ONLINE” state in cluster, [master + worker][for both CU and DU]
$ robin host list
Note:
Check for CPU and memory availability as well in all the nodes.
2. Docker registry is configured and reachable from cluster.
$ robin docker-registry list
$ ping6 <artifact fqdn>
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 5 of 13
3. Robin ip-pool should be defined for 5G CU and DU in its respective cluster.
$ robin ip-pool list --full
Note:
If the above criteria are not met, do not continue with the execution of this MOP.
2 Description
5G CU consists with two application CUCP and CUUP.
Required SW: Docker images and Robin bundle for particular build.
CUCP and CUUP installation is handled by two different scripts. Available in corresponding
robin bundle and procedure is described in below sections.
Robin bundle example for 3800_dsch Build #6,
pkg-artifact-0.0.11-6-Linux.tar.gz - CUCP and CUUP bundle available within this bundle
ani-oss-stub-nrcucp-for-robin-0.0.11-6.tar.gz --- CUCP scripts and config bundle
ani-oss-stub-nrcuup-for-robin-0.0.11-6.tar.gz --- CUUP scripts and config bundle
3 Installation / Upgrade steps:
a) Upload Docker images and robin bundle in Docker registry (Artifact).
Docker image or robin bundle will be automatically pushed from Bangalore to Drillisch
artifact for any particular build. Mainly we need to copy robin bundle in Distri PoP
cluster during manual onboarding, docker image will be automatically pulled in Distri
PoP during installation. Installation steps are described below.
b) Copy pkg-artifact-xxxx-Linux.tar.gz bundle (robin bundle) in Master node.
Run below command in master node
curl -vvv -g --user <artifcact_username>:<artifact_password> -v
http://<bundle_URL_In_artifact> -O
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 6 of 13
During execution of curl command remove “443” port from URL part in the curl
command and keep like below -
Example (rigel_3800_6 build)-
curl -vvv -g --user altiostar-gen:qC2pEHSYJbtVU28nkXfk -v
http://[2001:1438:902:1f01:0:9130:0:10]/artifactory/Mobility-Solutions-
Group/Vendors/Altiostar/VCU-5G/Early-Releases/0.0.11-6/pkg-artifact-0.0.11-6-Linux.tar.gz
–O
[ Note : pkg-artifact-0.0.11-6-Linux.tar.gz bundle can be manually copied in
master as well if above curl command facing any issue]
c) Login to the Master node and untar pkg-artifact-xxxx-Linux.tar.gz bundle. In pkg-artifact-
xxxx-Linux/pkg-artifact/ , CUCP and CUUP bundle available.
ani-oss-stub-nrcucp-for-robin-xxxx.tar.gz – CUCP bundle
ani-oss-stub-nrcuup-for-robin-xxxx.tar.gz – CUUP bundle
d) After final untar, below directory will be available ,
ani-oss-stub-nrcucp-for-robin-xxxx -- for CUCP
ani-oss-stub-nrcuup-for-robin-xxxx -- for CUUP
e) which will be used to instantiate and configuration of CUCP and CUUP, mentioned in next
steps.
As example for (3800_dsch Build #6) :
Say copy pkg-artifact-0.0.11-6-Linux.tar.gz bundle in /home/altiostar/pkg/5G_BUNDLE path in
master node. Then
$ tar -zxvf pkg-artifact-0.0.11-6-Linux.tar.gz
$ cd pkg-artifact-0.0.11-6-Linux
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 7 of 13
$ cd pkg-artifact
$ tar -zxvf ani-oss-stub-nrcucp-for-robin-0.0.11-6.tar.gz
$ tar –zxvf ani-oss-stub-nrcuup-for-robin-0.0.11-6.tar.gz
f) Enter into “scripts” directory of robin bundle and modify day0 configuration for CUCP and
CUUP before installation.
CUCP DAY 0 modification:
$ cd ani-oss-stub-nrcucp-for-robin-0.0.11-6/scripts/
$ vi oss-deploy-nrcucp.sh
$ There is a section named “DAY 0 PARAMETERS”. Modify the required parameter in that section
and save it. Example -
##########################################################################################
##
# DAY 0 PARAMETERS
#
##########################################################################################
##
DEFINE_DAY_0 VRAN_GNB_CU_CP_HOSTNAME "16720_cucp" - ->cucp host name
DEFINE_DAY_0 VRAN_GNB_CU_CP_FQDN ""
DEFINE_DAY_0 VRAN_GNB_ID "16720" - - >gnode ID
DEFINE_DAY_0 VRAN_NF_ID "1" -- > Network function id
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_PROTOCOL ""
DEFINE_DAY_0 VRAN_CMAAS_FQDN "127.0.0.1"
DEFINE_DAY_0 VRAN_CMAAS_PORT "65535"
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_FQDN "240b:c020:101:5538:6101:2::" -- > Operator CA
server IP
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_PORT "8085"
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_PATH ""
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_SUBJECT ""
DEFINE_DAY_0 VRAN_GNB_CU_CP_TLS_SRP_USER "ncm-riu-10101" -- > Operator CA server user
DEFINE_DAY_0 VRAN_GNB_CU_CP_TLS_SRP_PASSWORD "Atf5zkhlG4" - -> operator CA served password
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_REFERENCE_NUMBER ""
DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_SHARED_SECRET ""
DEFINE_DAY_0 VRAN_FM_KAFKA_TOPIC "rm.cdc.obf.altiostar.fault" #Set kafka topic name
DEFINE_DAY_0 VRAN_FM_KAFKA_URL
"[240b:c0e0:101:5dc0:b432:2:1:0]:32492,[240b:c0e0:101:5dc0:b432:2:2:0]:32493,[240b:c0e0:10
1:5dc0:b432:2:3:0]:32494" #Set kafka URL
DEFINE_DAY_0 VRAN_FM_KAFKA_CONFIG "YES" #NO : Uses kafka url and topic only from confd,
YES : Uses kafka url and topic from this file above 2 variables while bring up and later
user confd configuration
DEFINE_DAY_0 DEF_NETWORK "robin-default"
DEFINE_DAY_0 CP_ASDB_NETWORK "CP-db-nw"
DEFINE_DAY_0 CP_F1C_NETWORK "CP-f1c-nw" All the network name can be found with “robin
ip-pool list” command in cluster,modify according.
DEFINE_DAY_0 CP_X2C_NETWORK "CP-x2c-nw"
DEFINE_DAY_0 CP_NGC_NETWORK "CP-ngc-nw"
DEFINE_DAY_0 CP_XNC_NETWORK "CP-xnc-nw"
DEFINE_DAY_0 CP_MGMT_NETWORK "CP-mgmt-nw"
DEFINE_DAY_0 CP_E1C_NETWORK "CP-e1c-nw"
DEFINE_DAY_0 CP_LB_NETWORK "IPsec-5GvRAN"
DEFINE_DAY_0 DOCKER_REPO "ml-stg" -- >docker repo name
DEFINE_DAY_0 RPOOL_NAME "default" -- > provide rpool name for 5G, can be found with
“robin host list” commands.
DEFINE_DAY_0 DOCKER_REPO_PROJECT "altiostar/gnb-5g/" -- > docker repo project name
DEFINE_DAY_0 EXT_DOCKER_REPO_PROJECT "altiostar/ext-5g/"
DEFINE_DAY_0 DEBUG_KEEP_POD_ALIVE "FALSE"
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 8 of 13
DEFINE_DAY_0 DEBUG_PM_TEST_MODE "FALSE"
DEFINE_DAY_0 DELAY_APP_START_SEC "2"
DEFINE_DAY_0 NF_DEPLOYMENT_MODE "CU_CP_NSA"
DEFINE_DAY_0 NF_PROFILE "256_CARRIERS_1000_UES"
DEFINE_DAY_0 NF_CONFIG_XML "INJECT" #EMPTY or GOLDEN or INJECT
DEFINE_DAY_0 E1C_NETWORK_STATIC_IP ""
DEFINE_DAY_0 E1C_LB_NETWORK_STATIC_IP ""
DEFINE_DAY_0 X2C_NETWORK_STATIC_IP "'240b:c012:1e1:28c6:d18:2:20:9e75'" -- > static
IP definition , x2c static IP is used
DEFINE_DAY_0 F1C_NETWORK_STATIC_IP "'240b:c012:1e1:28c5:d18:2:10:cc72'" -- >
f1c_ike static IP is used
DEFINE_DAY_0 F1C_LB_NETWORK_STATIC_IP
"'fd00:ffff:ffff:ffff:2111:120e:0000:6887'" -- > f1c or loopback static ip is used .
DEFINE_DAY_0 NGC_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
If required we can define all the static IP in day0, in this part
DEFINE_DAY_0 XNC_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
If static IP is not required , keep its blank like as it is
DEFINE_DAY_0 ASDB_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 CONFD_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 CONFDPROXY_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 PERFMGR_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 NOTIFMGR_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 CERTMGR_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 ASDB_DISABLE true -- > If in robin ip-pool db-nw is not available keep
true , if db-nw is available keep false.
CUUP DAY 0 modification –
$ cd ani-oss-stub-nrcuup-for-robin-0.0.11-6/scripts/
$ vi oss-deploy-nrcuup.sh
$ There is a section named “DAY 0 PARAMETERS”. Modify the required parameter in that section
and save it. This is similar like cucp day0 , so description can be followed from cucp day0 example
above -
##########################################################################################
##
# DAY 0 PARAMETERS
#
##########################################################################################
##
DEFINE_DAY_0 VRAN_GNB_CU_UP_HOSTNAME "16720_cuup" – > cuup host name
DEFINE_DAY_0 VRAN_GNB_CU_UP_FQDN ""
DEFINE_DAY_0 VRAN_GNB_ID "16720" -- > gnode id
DEFINE_DAY_0 VRAN_NF_ID "1"
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_PROTOCOL ""
DEFINE_DAY_0 VRAN_CMAAS_FQDN "127.0.0.1"
DEFINE_DAY_0 VRAN_CMAAS_PORT "65535"
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_FQDN "240b:c020:101:5538:6101:2::"
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_PORT "8085"
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_PATH ""
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_SUBJECT ""
DEFINE_DAY_0 VRAN_GNB_CU_UP_TLS_SRP_USER "ncm-riu-10101010"
DEFINE_DAY_0 VRAN_GNB_CU_UP_TLS_SRP_PASSWORD "Atf5zkhlG"
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_REFERENCE_NUMBER ""
DEFINE_DAY_0 VRAN_GNB_CU_UP_CA_SHARED_SECRET ""
DEFINE_DAY_0 VRAN_FM_KAFKA_TOPIC "rm.cdc.obf.altiostar.fault" #Set FM kafka topic name
DEFINE_DAY_0 VRAN_FM_KAFKA_URL
"[240b:c0e0:101:5dc0:b432:2:1:0]:32492,[240b:c0e0:101:5dc0:b432:2:2:0]:32493,[240b:c0e0:10
1:5dc0:b432:2:3:0]:32494" #Set FM kafka URL
DEFINE_DAY_0 VRAN_FM_KAFKA_CONFIG "YES" #NO : Uses kafka url and topic only from confd,
YES : Uses kafka url and topic from this file above 2 variables while bring up and later
user confd configuration
DEFINE_DAY_0 DEF_NETWORK "robin-default"
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 9 of 13
DEFINE_DAY_0 UP_ASDB_NETWORK "UP-db-nw"
DEFINE_DAY_0 F1U_NETWORK "UP-f1u-nw"
DEFINE_DAY_0 BHU_NETWORK "UP-s1u-nw" All the network name can be found with “robin ip-
pool list” command in cluster,modify according.
DEFINE_DAY_0 UP_MGMT_NETWORK "UP-mgmt-nw"
DEFINE_DAY_0 UP_E1C_NETWORK "UP-e1c-nw"
DEFINE_DAY_0 UP_LB_NETWORK "IPsec-5GvRAN"
DEFINE_DAY_0 DOCKER_REPO "ml-stg"
DEFINE_DAY_0 RPOOL_NAME "default" -- > provide rpool name for 5G
DEFINE_DAY_0 DOCKER_REPO_PROJECT "altiostar/gnb-5g/"
DEFINE_DAY_0 EXT_DOCKER_REPO_PROJECT "altiostar/ext-5g/"
DEFINE_DAY_0 DEBUG_KEEP_POD_ALIVE "FALSE"
DEFINE_DAY_0 DEBUG_PM_TEST_MODE "FALSE"
DEFINE_DAY_0 DELAY_APP_START_SEC "2"
DEFINE_DAY_0 NF_DEPLOYMENT_MODE "CU_UP"
DEFINE_DAY_0 NF_PROFILE "6GB_2UP" -- > number of userplane instance to be installed ,
This for 2 userplane instance. 6GB_4UP and 6GB_8UP also can be configured as per
requirement to install 4 or 8 userplane.
DEFINE_DAY_0 NF_CONFIG_XML "INJECT" #EMPTY or GOLDEN or INJECT
DEFINE_DAY_0 E1C_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 E1C_LB_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 F1U_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 BHU_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 ASDB_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 CONFD_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 CONFDPROXY_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 PERFMGR_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 NOTIFMGR_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 CERTMGR_MGMT_NETWORK_STATIC_IP "" #"'ip1'" or "'ip1','ip2'"
DEFINE_DAY_0 ASDB_DISABLE true
g) Place the correct configuration file for CUCP and CUUP in robin bundle for corresponding
gnodeB before installation. Configuration file will be in .xml format-
CUCP configurations file name –
sub6_cp-day-1.xml , cucpconfig_template.xml
CUUP configurations file name –
sub6_up-day-1.xml
cu_config_3800_6_build.zip
Place sub6_cp-day-1.xml, sub6_up-day-1.xml,cucpconfig_template.xml, config_push_cu.sh,
netconf-console and netconf-console-tcp . These files in cucpconfig directory within CUCP
bundle.
$ cd ani-oss-stub-nrcucp-for-robin-0.0.11-6/config_map/cucpconfig/
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 10 of 13
h) Modify the config files according to the each gnodeB. Prepare these config files before
installing CU.
sub6_cp-day-1.xml - Modify below part primarily
ManagedElement id.
gNBId
Plmn (mcc , mnc)
NRCell information within NRCellCU block. [IMPORTANT]- this NRcellCU block needs to copy
multiple times as per number of cell want to connect with this CU. Say if only one DU with
3 ORU (i.e. 3 cell) needs to connect then NRcellCU block needs to configured 3 times in
cp-day1 and modify “id” and “celllocal id” according (i.e. 0-3) . If 2 DU and 6 ORU needs
connect then 6 times above block needs to be copied and modify “id” and “celllocal id”
(i.e. 0-6), and so on.
Configure 4G BH-s1 IP in EP_X2CRemote block as remoteAddress param.
Kafka enpoint url and topic name for perfmgr , notifmgr.
sub6_up-day-1.xml – Modify the below part primarily.
ManagedElement id
Kafka enpoint url and topic name for perfmgr , notifmgr.
gNBId, gNBCUUPId
Plmn (mcc , mnc)
cert_name – This is for certificate name , we need to provide whole certificate string.
Example -
<cert_name>/O=Altiostar/CN=ca.altiostar.com</cert_name> - Altiostar self signed
certificate
If operator cert is available then we need to provide full string of operator certificate
name.
cucpconfig_template.xml - attached in this doc . Use that as a reference.
[NOTE]: All the configurations is attached as per present running configuration for
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 11 of 13
manually Installed CUs. This might varies for different build and environment. So, It is
suggested to prepare and verify configuration with ASN members before pushing it to
the CU.
i) To create/install the application, enter into “scripts” directory of corresponding Robin
bundle and run below command from Master node.
CUCP application create or delete :
$ cd ani-oss-stub-nrcucp-for-robin-0.0.11-6/scripts/
$ ./oss-deploy-nrcucp -o create
#########################################
INFO : Starting CU CP vNF: cucpapp-16720-cp1
#########################################
Job: 45286 Name: BundleAdd State: VALIDATED Error: 0
Job: 45286 Name: BundleAdd State: PREPARED Error: 0
Job: 45286 Name: BundleAdd State: FINALIZED Error: 0
Job: 45286 Name: BundleAdd State: COMPLETED Error: 0
#########################################
INFO : Starting CU CP vNF: cucpapp-16720-cp1
#########################################
Job: 45287 Name: ApplicationCreate State: PROCESSED Error: 0
Job: 45287 Name: ApplicationCreate State: PREPARED Error: 0
Job: 45287 Name: ApplicationCreate State: WAITING Error: 0
Job: 45287 Name: ApplicationCreate State: NOTIFIED Error: 0
Job: 45287 Name: ApplicationCreate State: COMPLETED Error: 0
Job: 45326 Name: ApplicationUpdate State: PROCESSED Error: 0
Job: 45326 Name: ApplicationUpdate State: COMPLETED Error: 0
$ ./oss-deploy-nrcucp -o delete
CUUP application create or delete :
$ cd ani-oss-stub-nrcuup-for-robin-0.0.11-6/scripts
$ ./oss-deploy-nrcuup.sh -o create
#########################################
INFO : Starting CU UP vNF: cuupapp-16720-up1
#########################################
Job: 45327 Name: BundleAdd State: VALIDATED Error: 0
Job: 45327 Name: BundleAdd State: PREPARED Error: 0
Job: 45327 Name: BundleAdd State: COMPLETED Error: 0
#########################################
INFO : Starting CU UP vNF: cuupapp-16720-up1
#########################################
Job: 45328 Name: ApplicationCreate State: PROCESSED Error: 0
Job: 45328 Name: ApplicationCreate State: WAITING Error: 0
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 12 of 13
Job: 45328 Name: ApplicationCreate State: COMPLETED Error: 0
Job: 45350 Name: ApplicationUpdate State: PROCESSED Error: 0
Job: 45350 Name: ApplicationUpdate State: COMPLETED Error: 0
$ ./oss-deploy-nrcuup.sh -o delete
[NOTE] : If user wants to create multiple CUCP or CUUP application , then copy the robin
bundle with another name and run the creation scripts from that bundle. Because
different CUCP and CUUP would have different configuration file , so to segregate the
application and corresponding configuration this procedure needs to follow.
Example-
Created separate robin_bundle directory with corresponding configuration to create
two CUs, gnb_id “1111149” and “1111150”.
j) Push the configuration once CUCP and CUUP is installed.
Go to the cucpconfig directory for corresponding gnodeB. All configuration file should be
there as per previous steps (steps V) mentioned. Run “config_push_cu.sh” after
modifying “gnb_id” and “namespace”.
$ cd ani-oss-stub-nrcucp-for-robin-0.0.11-6/config_map/cucpconfig
$ vi config_push_cu.sh , modify gnb_id and namespace according .
$ ./config_push_cu.sh
4 Post Installation Checks:
a) After creating the application, check all the pods are running for CUCP and CUUP app for
corresponding gnodeB.
$ kubectl get pods –n <namespace> from Master node.
b) Check all the pods are available for corresponding CU release for particular gnodeB.
$ kubectl get pods –n <namespace> | wc -l from Master node.
c) Check the corresponding cucp and cuup apps are created and Ready|ONLINE state.
$ robin app list from Master node.
d) Check e1c status , it should be up .
$ kubectl exec -it cucpapp-<gnb_id>-cp1-nrcpconfd-01 –n <namespace> -- bash -c
'/opt/ani/bin/confd_cli -A $ANI_CONFD_SERVICE_IPADDRESS -P $ANI_CONFD_SERVICE_PORT -u
root'
> request cuup-status-all
cuup_info {
cuup_id 1
state E1C_INTERFACE_UP_STATE
5G_CU Manual Deployment Guide (NSA)
MOP Date: February 17, 2022 Version: 1.0 Page 13 of 13
5 Post Deletion Checks:
a) After deleting the application, check all the CUCP and CUUP pods are deleted for
corresponding gnodeB.
$ kubectl get pods –n <namespace> from Master node.
b) Check the cucp and cuup apps are deleted for corresponding gnodeB.
$ robin app list from Master node.
c) Check CUCP and CUUP bundles are deleted for corresponding gnodeB.
$ robin bundle list from Master node
6 CU Installation with Altiostar self-signed certificate-
CU can be installed with Altiostar self-signed certificate. During CUCP and CUUP
installation comment out below 4 line in day0 (steps IV ) or don’t provide any input for
these 4 parameters ,Then run “oss-deploy-nrxxxx.sh” scripts to install CUCP and CUUP.
#DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_FQDN "240b:c020:101:5538:6101:2::"
#DEFINE_DAY_0 VRAN_GNB_CU_CP_CA_PORT "8085"
#DEFINE_DAY_0 VRAN_GNB_CU_CP_TLS_SRP_USER "ncm-riu-10101010"
#DEFINE_DAY_0 VRAN_GNB_CU_CP_TLS_SRP_PASSWORD "Atf5zkhlG4"
Others steps are as it is and same like described in this docs.
