0% found this document useful (0 votes)

318 views

OpenStack Commissioning - MSS Cloud CFP5

Uploaded by

David

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

318 views

OpenStack Commissioning - MSS Cloud CFP5

Uploaded by

David

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 142

Commissioning Open MSS

Cloud on OpenStack
DN09241459
Issue 6-0-0

Commissioning Open MSS Cloud on OpenStack

The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.

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.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.

f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.

2 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0
Commissioning Open MSS Cloud on OpenStack

Table of Contents
This document has 142 pages

Summary of changes..................................................................... 8

1 Overview of the commissioning of Open MSS Cloud on
OpenStack................................................................................... 15
1.1 User roles and requirements........................................................15

2 Software requirements of the reference configuration................. 17
2.1 OpenStack components...............................................................17
2.2 Open vSwitch with Data Plane Development Kit (OVS-DPDK)... 17
2.3 Nokia components....................................................................... 18

3 HP hardware requirements.......................................................... 19
3.1 Optimizing performance............................................................... 20
3.2 Customizing the OpenStack on HP platform................................23

4 NDCS hardware requirements..................................................... 26
4.1 Customizing the OpenStack on NDCS platform.......................... 27
4.1.1 Customizing OpenStack in case of root volume deployment.......29

5 Application deployment requirements for OpenStack.................. 31
5.1 Open MSS capacity requirements............................................... 31
5.2 Open MSS internal storage architecture...................................... 32
5.3 Creating a Project........................................................................ 33
5.4 Creating the tenant user ..............................................................37
5.5 Changing quotas.......................................................................... 40
5.6 Adjusting maximum Heat stack size............................................ 43
5.7 Creating provider networks.......................................................... 44
5.8 Uploading the iPXE image........................................................... 48
5.9 Uploading the VSA image............................................................ 51
5.10 Creating VSA key pairs................................................................ 53

6 Application content provisioning...................................................56
6.1 Creating the OMU disk image...................................................... 57
6.2 Creating the OMU volumes..........................................................61
6.3 Creating CHU volumes in Cinder................................................. 64
6.4 Providing OVS-DPDK compatible flavors.................................... 65
6.5 Creating predefined flavors.......................................................... 65
6.5.1 Creating flavors using OpenStack command line........................ 66
6.5.2 Creating flavors in the dashboard................................................ 67
6.6 Deleting predefined flavors.......................................................... 71
6.6.1 Deleting a flavor using OpenStack command line....................... 72
6.6.2 Deleting a flavor using the dashboard..........................................72
6.7 Using root volumes...................................................................... 74

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 3
Commissioning Open MSS Cloud on OpenStack

7 Application deployment with Heat................................................ 75
7.1 Uploading the VNF template to the controller node..................... 75
7.2 Using the predefined flavor in case of Heat based deployment...78
7.3 Application variables.................................................................... 78
7.4 Creating the Heat stack and Open MSS application....................81

8 Application deployment with CloudBand Application Manager
(CBAM)........................................................................................ 83
8.1 Uploading the VNFD package to CBAM Catalog.........................83
8.2 Creating the MSS VNF in CBAM................................................. 85
8.3 Using the predefined flavor in case of CBAM based deployment....
88
8.4 Modifying the VNF attribute parameter values in CBAM..............88
8.5 Instantiating the MSS VNF in CBAM............................................96
8.6 Initializing the MSS VNF in CBAM............................................. 101
8.7 Automatic MSS unit bringup in CBAM....................................... 103
8.8 Setting IPv6 addresses on OaM network...................................106

9 Completion of deployment......................................................... 108
9.1 Accessing the OMU console...................................................... 108
9.2 Setting the C-number................................................................. 110
9.3 Checking the disk connections................................................... 111
9.4 Configuring system encryption keys...........................................112
9.5 Adding the spare OMU unit........................................................ 115
9.6 Configuring IP addresses for OMU.............................................115
9.6.1 Configuring IP addresses for OMU in case of DHCP usage...... 116
9.6.2 Configuring IP addresses for OMU manually............................. 117
9.7 Unit bringup in Open MSS Cloud............................................... 118
9.7.1 Adding the CMM units................................................................120
9.7.2 Adding the CMU units................................................................ 121
9.7.3 Adding the STU units................................................................. 122
9.7.4 Adding the CHU units.................................................................123
9.7.5 Adding the VLRU units...............................................................124
9.7.6 Adding the IPDU units................................................................126
9.7.7 Adding the GISU units................................................................128
9.8 Troubleshooting the DHCP service............................................ 130
9.9 Troubleshoot for failed unit bringup............................................131
9.10 Checking the GRO setting on VXLAN interfaces....................... 132
9.11 Troubleshooting predefined flavor use....................................... 133
9.12 NetAct registration of deployed MSS......................................... 134
9.13 Checking the operational status of the Open MSS Cloud..........137

Appendix: Checklist for Open MSS Cloud deployment..............141

4 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0
Commissioning Open MSS Cloud on OpenStack

List of Figures
Figure 1 HP blade BIOS setting power management.......................................20
Figure 2 HP blade BIOS setting for CPU power regulator................................21
Figure 3 Saving the new HP blade BIOS setting.............................................. 22
Figure 4 Rebooting the system.........................................................................23
Figure 5 High-level overview of the Open MSS disk connections.................... 33
Figure 6 Defining the project name on the Project Information tab.................. 34
Figure 7 Setting the maximum quotas for the project....................................... 36
Figure 8 Created Project...................................................................................37
Figure 9 Creating the user................................................................................ 38
Figure 10 The tenant user is created..................................................................39
Figure 11 Starting the image creation ................................................................49
Figure 12 Uploading the iPXE image..................................................................50
Figure 13 iPXE image is uploaded..................................................................... 50
Figure 14 Starting the image creation ................................................................51
Figure 15 Providing the VSA image data............................................................52
Figure 16 VSA image is uploaded...................................................................... 52
Figure 17 Creating key pairs...............................................................................54
Figure 18 Defining the key pair name.................................................................54
Figure 19 Automatic key pair download..............................................................55
Figure 20 Key pair is created..............................................................................55
Figure 21 Starting the image creation ................................................................58
Figure 22 Uploading the extracted raw disk image file and creating the image.....
59
Figure 23 Uploading the extracted qcow2 disk image file and creating the image.
60
Figure 24 Creating the volume........................................................................... 62
Figure 25 Finishing the OMU volume creation................................................... 63
Figure 26 Create Flavor window.........................................................................68
Figure 27 Flavor is successfully created.............................................................69
Figure 28 The created flavor...............................................................................69
Figure 29 Setting the hw:watchdog_action metadata.........................................70
Figure 30 Setting the hw:mem_page_size metadata......................................... 71
Figure 31 Choosing the Delete Flavor option..................................................... 73
Figure 32 Confirming the flavor deletion.............................................................73
Figure 33 The flavor is deleted........................................................................... 74
Figure 34 Adding the VNFD package................................................................. 84
Figure 35 Uploading the VNFD package............................................................ 85
Figure 36 Finishing the VNFD package upload.................................................. 85
Figure 37 Accessing the Create New VNF function...........................................86

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 5
Commissioning Open MSS Cloud on OpenStack

Figure 38 Adding the VNF name........................................................................ 87
Figure 39 List of VNFs in CBAM.........................................................................87
Figure 40 Accessing the Modify VNF function....................................................89
Figure 41 Accessing the Extensions section...................................................... 90
Figure 42 Changing the parameter values......................................................... 91
Figure 43 Completing the parameter value modification.................................... 95
Figure 44 Successful start of the VNF modification............................................95
Figure 45 Initiating instantiation.......................................................................... 97
Figure 46 Selecting the wanted instantiation level for the VNF.......................... 98
Figure 47 Adding the VIM password...................................................................99
Figure 48 Browsing for the parameter file and launching the instantiation....... 100
Figure 49 Successful start of the VNF instantiation..........................................100
Figure 50 Instantiation is completed................................................................. 101
Figure 51 Accessing the Initialize function........................................................102
Figure 52 Verifying the initialization.................................................................. 102
Figure 53 Initialization is completed..................................................................103
Figure 54 Accessing the bringup menu item.................................................... 104
Figure 55 Setting bringup parameters and starting the bringup....................... 105
Figure 56 Finnish keyboard layout....................................................................108
Figure 57 Displaying the console......................................................................109
Figure 58 Accessing the console...................................................................... 110
Figure 59 Console is accessed......................................................................... 110
Figure 60 Rebooting the VM.............................................................................132
Figure 61 Integrate with NetAct........................................................................ 137
Figure 62 Reset unit from dashboard............................................................... 140

6 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0
Commissioning Open MSS Cloud on OpenStack

List of Tables
Table 1 Changes made between issues 6-0-0 and 5-0-0..................................8
Table 2 Changes made between issues 5-0-0 and 4-0-0..................................9
Table 3 Changes made between issues 4-0-0 and 3-0-0................................10
Table 4 Changes made between issues 3-0-0 and 2-1-1................................12
Table 5 Sizes of deployment artifacts..............................................................32
Table 6 Open MSS storage requirements in case of small (3M BHCA) capacity
............................................................................................................33
Table 7 Quota values...................................................................................... 35
Table 8 Provider networks...............................................................................45
Table 9 Application variables...........................................................................78
Table 10 Parameter descriptions.......................................................................91
Table 11 Structure of the vimConnectionInfo section........................................96
Table 12 MSS unit bringup parameters and examples................................... 104
Table 13 Example for stuck unit in test phase.................................................131
Table 14 NetAct related parameter descriptions............................................. 135
Table 15 Checklist for Open MSS Cloud deployment..................................... 141

Summary of changes Commissioning Open MSS Cloud on OpenStack

Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.

Changes made between issues 6-0-0 and 5-0-0

Table 1 Changes made between issues 6-0-0 and 5-0-0
Affected sections Changes
Setting IPv6 addresses on OaM New section was added due to the automation of the VSA
network upgrade.
Creating provider networks A new, optional step was added to the topic due to the
automation of the VSA upgrade.
Modifying the VNF attribute New parameters were added to table Parameter descriptions
parameter values in CBAM due to the automation of the new VSA upgrade.
Open vSwitch with Data Plane New sections were added due to OVS-DPDK compatibility.
Development Kit (OVS-DPDK)
Providing OVS-DPDK
compatible flavors

Application content provisioning New values and steps were added due to OVS-DPDK
compatibility.
Creating predefined flavors
Creating flavors using
OpenStack command line
Creating flavors in the
dashboard

Application content provisioning Minor changes or corrections were made.
Adding the spare OMU unit
Adding the VLRU units

Deleting predefined flavors New sections were added to the document.
Deleting a flavor using
OpenStack command line
Deleting a flavor using the
dashboard

NetAct registration of deployed Paramters netact_mml_interface, netact_mml_port and
MSS ne_connect_mode were removed from table NetAct related
parameter descriptions.
Application content provisioning An option was added to upload the OMU disk image in qcow2
file format.
Creating the OMU disk image

Changes made between issues 5-0-0 and 4-0-0

Commissioning Open MSS Cloud on OpenStack Summary of changes

Table 2 Changes made between issues 5-0-0 and 4-0-0
Affected sections Changes
Automatic MSS unit bringup in CBAM New section added due to the internal IP pre-config
functionality.
Configuring IP addresses for OMU New section added due to the new CloudBand
Infrastructure Software version (CBIS 19).
Creating a Project Screenshots, descriptions or printouts were changed
due to the new CloudBand Infrastructure Software
Adjusting maximum Heat stack size version (CBIS 19).
Uploading the iPXE image
Uploading the VSA image
Creating VSA key pairs
Creating the OMU disk image
Creating the OMU volumes
Creating flavors in the dashboard
Accessing the OMU console
Configuring IP addresses for OMU in
case of DHCP usage
Configuring IP addresses for OMU
manually
Troubleshoot for failed unit bringup

Application content provisioning Screenshots, descriptions or printouts were changed
due to the new CloudBand Application Manager
Application deployment with CloudBand version (CBAM 19).
Application Manager (CBAM)
Uploading the VNFD package to CBAM
Catalog
Creating the MSS VNF in CBAM
Modifying the VNF attribute parameter
values in CBAM
Instantiating the MSS VNF in CBAM
Initializing the MSS VNF in CBAM
NetAct registration of deployed MSS

Open MSS capacity requirements Small corrections or amendments were made.
Creating CHU volumes in Cinder
Uploading the VNF template to the
controller node
Application variables
Creating the Heat stack and Open MSS
application
Accessing the OMU console
Checking the disk connections

Summary of changes Commissioning Open MSS Cloud on OpenStack

Table 2 Changes made between issues 5-0-0 and 4-0-0 (Cont.)
Affected sections Changes
Troubleshooting the DHCP service
Appendix: Checklist for Open MSS
Cloud deployment

Changes made between issues 4-0-0 and 3-0-0

Table 3 Changes made between issues 4-0-0 and 3-0-0
Affected sections Changes
Creating predefined flavors New sections added to the document due to the predefined
flavor creation functionality being introduced.
Creating flavors using OpenStack
command line
Creating flavors in the dashboard
Using predefined flavors in case
of Heat based deployment
Using predefined flavors in case
of CBAM based deployment
Troubleshooting predefined flavor
use

Application variables Table Application variables was updated with parameters on
predefined flavor creation.
Modifying the VNF attribute Table Parameter descriptions was updated with parameters
parameter values in CBAM on predefined flavor creation. A note was also added on
parameters not described in the table.
Configuring IP addresses for New sections added to the document due to DHCP usage.
OMU in case of DHCP usage
Troubleshooting the DHCP
service

Nokia components Small changes made due to DHCP usage.
Application content provisioning
Updating the Open MSS disk
image content
Creating the OMU disk image
Completion of deployment
Accessing the OMU console
Uploading the VNF template to
the controller node
Application variables
Modifying the VNF attribute
parameter values in CBAM

Commissioning Open MSS Cloud on OpenStack Summary of changes

Table 3 Changes made between issues 4-0-0 and 3-0-0 (Cont.)
Affected sections Changes
Application deployment with
CloudBand Application Manager
(CBAM)
Adding the CMU units
Adding the CHU units
Adding the VLRU units

Creating provider networks Additional information and step example of step 2 was
updated.
Initializing the MSS VNF in New section added to the document due to MSS VNF
CBAM initialization changes.

Appendix: Checklist for Open The references of step 15, 16, 17 and 18 were changed to
MSS Cloud deployment more accurate sections.

Configuring IP addresses for New sections added
OMU manually
Unit bringup in Open MSS Cloud
Adding the spare OMU unit
Troubleshoot for failed unit
bringup

Completion of deployment The order of the sub-sections was changed to make it more
logical.
Optimizing performance Small changes made throughout the sections to make the
document compatible with CBAM 18.
Open MSS internal storage
architecture
Creating a Project
Creating the tenant user
Changing quotas
Creating provider networks
Uploading the iPXE image
Uploading the VSA image
Creating VSA key pairs
Creating the OMU disk image
Creating the OMU volumes
Creating CHU volumes in Cinder
Uploading the VNF template to
the controller node
Creating the Heat stack and
Open MSS application
Application variables

Summary of changes Commissioning Open MSS Cloud on OpenStack

Table 3 Changes made between issues 4-0-0 and 3-0-0 (Cont.)
Affected sections Changes
Accessing the OMU console
Checking the disk connections

Application deployment with A note has been added to the section on CBAM 18.5
CloudBand Application Manager compatibility.
(CBAM)
Customizing OpenStack in case New sections added due to the new Cloud MSS Cinder
of root volume deployment Volume for all Disks functionality.

Using root volumes

Creating a Project Small changes made due to the new Cloud MSS Cinder
Volume for all Disks functionality.
Application content provisioning
Creating predefined flavors

Customizing the OpenStack on Small changes in printouts.
HP platform

Open MSS capacity Small change in capacity when using four hosts in the cluster.
requirements

Instantiating the MSS VNF in General updates were made in the sections, mostly related to
CBAM bringup.

Configuring system encryption
keys
Checking the operational status
of the Open MSS Cloud
Unit bringup in Open MSS Cloud

Creating predefined flavors Small changes made or additional steps added due to the
watchdog functionality.
Creating flavors using OpenStack
command line
Creating flavors in the dashboard

Creating the OMU disk image A new step was added on OMU disk image file
uncompression. Image Uploading the image file was
updated.

Changes made between issues 3-0-0 and 2-1-1

Table 4 Changes made between issues 3-0-0 and 2-1-1
Affected sections Changes
Overview of the Short description of the section has been updated.
commissioning of Open MSS
Cloud on OpenStack
OpenStack components OpenStack licensing related information has been removed since
licensing is not valid for OpenStack.

Commissioning Open MSS Cloud on OpenStack Summary of changes

Table 4 Changes made between issues 3-0-0 and 2-1-1 (Cont.)
Affected sections Changes
Nokia components The available minimum disk size has been increased from 40 to
120 GB.
Updating the Open MSS disk
image content OMU IP injector script related note has been added.

Customizing the OpenStack Previous Step 1 and Step 2 have been combined, and their
on HP platform codeblocks have been updated.
Command of Step 7 has been updated.

Open MSS capacity Documentation reference has been updated.
requirements
Adjusting maximum Heat New section has been added.
stack size
Creating provider networks MTU related note has been added.
Updating the Open MSS disk Codeblock of Step 7 has been corrected.
image content
Creating CHU volumes in Short description has been updated with web interface related
Cinder information.
Keystone credential file related information has been added into
part Before you start.
Part Postrequisites has been removed and added into section
Checking the disk connections.

Uploading the VNF template In Step 2: previous code has been replaced with the codeblock of
to the controller node unzip command. In the step result, the directory name has been
updated.
In Step 3: the example codeblock and its related information have
been updated.
In Step 4: step result has been added.

Creating the Heat stack and In Step 2: step command has been updated. The step result
Open MSS application information has been corrected.
In Step 4: in the codeblocks, the number of GISU related parts
have been corrected.

Application variables New entries have been added to table Application variables:
vsa1_volume_id_chu2, vsa1_volume_id_chu3,
vsa2_volume_id_chu2, vsa2_volume_id_chu3, num_gisu,
gisu_group_by, and cp_ipdu_group_by.
Modifying the VNF attribute Prerequisite information has been updated.
parameter values in CBAM
In Step 4: step command and related image have been updated
because of the usage of new CBAM version.
In Step 5: new entries have been added to table Parameter
descriptions: vsa1_volume_id_chu2, vsa1_volume_id_chu3,
vsa2_volume_id_chu2, and vsa2_volume_id_chu3.

Instantiating the MSS VNF in Step 1 has been updated with file location.
CBAM

Summary of changes Commissioning Open MSS Cloud on OpenStack

Table 4 Changes made between issues 3-0-0 and 2-1-1 (Cont.)
Affected sections Changes
Accessing the OMU console Keyboard layout related note has been added.
Checking the operational Step 1 has been updated.
status of the Open MSS
NetAct registration of Procedure has been added to the section.
deployed MSS

Commissioning Open MSS Cloud on OpenStack Overview of the commissioning of Open MSS Cloud on
OpenStack

1 Overview of the commissioning of Open MSS

Cloud on OpenStack
Before commissioning the Open MSS Cloud on OpenStack software platform, the basic
cloud infrastructure must be ready to use.

The Open MSS Cloud application is a Virtual Network Function (VNF), which can be
commissioned on top of the HP BladeSystem or Nokia AirFrame hardware with
OpenStack as the software platform.
Before commissioning the VNF, plan the network and configure the hardware and
software platforms in a way to accommodate the Open MSS Cloud.
There are basic hardware and software requirements and recommendations towards the
virtualized Open MSS deployment and operation. The hardware requirements originate
from the Nokia Cloud Infrastructure (NCI) reference architectures based on the HP
BladeSystem or Nokia AirFrame. For the correct deployment of the VNF, set up the
Virtual Infrastructure (VI) as well.
The Open MSS Cloud is a single virtual application, therefore all of its Virtual Machines
(VMs) must be deployed into the same Project.
Perform the deployment of the Open MSS Cloud. When the Open MSS Cloud
commissioning is successfully completed, it is integrated with NetAct and ready for
network integration. After deployment, it is possible to check the basic operation of the
VNF by following the health check procedure for generic operations.

1.1 User roles and requirements

The Open MSS Cloud commissioning must be performed by users with specific
knowledge areas. However, all users have to be able to install and configure the
OpenStack software platform.

Role Description Expected knowledge

Application HP AirFrame
Cloud A user who has
Administrator administrative
privileges on all
the OpenStack
components of
the Cloud
Infrastructure
(CI).
Infrastructure A user who has HP Virtual AirFrame
Network administrative Connect configuration and
Administrator privileges on all configuration and administration
the physical and administration
virtual networking AirFrame
of the CI. If the HP c7000 Datacenter
Cloud configuration and switching
Administrator is administration configuration

Overview of the commissioning of Open MSS Cloud on Commissioning Open MSS Cloud on OpenStack
OpenStack

Role Description Expected knowledge

Application HP AirFrame
the virtual HP Datacenter
networking switching
administrator, that configuration
user should be
the networking
administrator as
well.
Infrastructure A user who has EMC VNX
Storage administrative installation,
Administrator privileges on all configuration, and
the physical and administration
virtual storage of
the CI. If the
Cloud
administrator is
the virtual storage
administrator, that
user should be
the storage
administrator as
well.
Open MSS A user from OpenStack heat
Commissioning Nokia's customer service
Engineer support team who
commissions the Linux (basic)
Open MSS Cloud
Open MSS
on the OpenStack
software platform. installation and
configuration

Commissioning Open MSS Cloud on OpenStack Software requirements of the reference configuration

2 Software requirements of the reference

configuration
The Open MSS Cloud has minimum software requirements and recommendations
regarding the OpenStack and Nokia components.

2.1 OpenStack components

Setting up an OpenStack IaaS service appropriate for Telco applications like the Open
MSS Cloud requires the use of a compatible OpenStack release.

The OpenStack installation must contain the following mandatory components:
• Heat service: orchestrates composite cloud applications using a declarative template
format through an OpenStack-native REST API
• Nova
• Keystone
• Cinder
• Neutron
• Glance
• RabbitMQ
• MySQL database
• Host Operating System: RHEL 7.0 or equivalent (Kernel, KVM, Qemu, and Libvirt
version cannot be lower than in RHEL 7.0)

Commissioning Open MSS Cloud requires admin access rights for the OpenStack cloud
to create the project and the tenant user. However, you can carry out the Open MSS
Cloud deployment without admin access rights, using the predefined flavor option. For
more information, see section Creating predefined flavors.

Related descriptions
Creating predefined flavors on page 65

Related procedures
Creating a Project on page 33
Creating the tenant user on page 37

2.2 Open vSwitch with Data Plane Development Kit

(OVS-DPDK)
You can enable the OVS DPDK functionality in the cloud infrastructure to enhance
packet processing.

Software requirements of the reference configuration Commissioning Open MSS Cloud on OpenStack

Data Plane Development Kit (DPDK) provides high-performance packet processing
libraries and user space drivers. Open vSwitch (OvS), integrated with DPDK, provides an
option to use a DPDK-optimized virtual host (vhost) path in the OvS.
The OVS-DPDK feature can be enabled in the cloud infrastructure. The compatibility on
VNF level ensures that Open MSS Cloud can be deployed on a cloud infrastructure that
has the OVS-DPDK functionality enabled.
Enabling the OVS-DPDK functionality NFVI level enhances packet processing and
provides lower latencies.

g Note: This functionality has no effect on the VNF’s traffic handling capacity.

2.3 Nokia components

During the commissioning phase, Heat and CBAM are used for application management
and deployment.

CloudBand Application Manager (CBAM)

CBAM is a generic Virtualized Network Function Manager (VNFM) for OpenStack,
compliant with ETSI NFV. It automates VNF lifecycle management and cloud resource
management. Its standards-based APIs make it easy to work with any vendor's VNF,
Element Management System (EMS), Virtualized Infrastructure Manager (VIM), and
Network Function Virtualization Orchestrator (NFVO).

NetAct
NetAct is a set of VNF element management applications for managing and operating
network elements efficiently and remotely.
It provides standard Fault Management (FM), Performance Management (PM), and
Configuration Management (CM) functions for the VNF. NetAct requires access to the
OaM interface.

Commissioning Open MSS Cloud on OpenStack HP hardware requirements

3 HP hardware requirements
The hardware requirements originate from the Nokia Cloud Infrastructure on OpenStack
reference configuration, which is based on HP Blade Systems, HP Flex Networking, and
EMC Unified Storage solutions.

The reference configuration includes HP Gen 9 Half Height Blades in one or more HP
c7000 Enclosures. The number of blades and enclosures depends on the planned size
of the Infrastructure as a Service (IaaS) Cloud.
The required blade capacity is calculated based on the Hyper-threaded (logical) CPU
core capacity and the required memory capacity. The hypervisors require two Logical
Cores and minimum 2 Gigabytes of memory to operate. But this requirement can also
depend on the load of the emulated virtual I/O devices, for example, the virtual Network
Interface Cards (vNICs). The hardware hosts (blades) are organized into clusters to
provide High Availability (HA).
The HP hardware reference configuration relies on HP Flex Networking Architecture,
utilizing Data Center Bridging devices and FlexFabric converged networking. It is based
on Internet Small Computer Systems Interface (iSCSI) data access, however, the latest
hardware and firmware elements are able to provide Fiber Channel over Ethernet
(FCoE) data access as well. Already deployed Fiber Channel (FC) switching can also be
used, although in that case, the FlexFabric Interconnect modules have to be utilized in
the first two bays, instead of the Flex10/10D or an external FC to FCoE converged
switch.
The reference architecture is based on a solution that has a single rack configuration,
which has a maximum of two enclosures. However, the capacity can be extended with
similar setups. In a smaller setup with not more than 6-8 enclosures, 10/40Gbit Top of
Rack switches can be used for aggregating the enclosure network connections, which is
the case in the recommended reference setup. In larger designs, the collapsed core or
end row high capacity switches should be used for HP c7000 Blade Systems.
The hardware reference configuration includes EMC VNX 5400 Unified Storage
equipment.
Since the reference architecture recommends file-based services in addition to the block-
based ones, only the unified storage should be utilized. However, in very small
configurations where there are only a few enclosures in OpenStack, the Network File
System (NFS) can be replaced with iSCSI or FCoE.
To achieve robust HA of the clusters, the NFS can also be used as a secondary
datastore for host system logging.

Other resources

Web links
Nokia Cloud Infrastructure

HP hardware requirements Commissioning Open MSS Cloud on OpenStack

3.1 Optimizing performance

The optimal operation of the cluster built for real-time telco applications requires the
configuration of the HP blade CPU power regulator. Without these settings, the real-time
operating system’s performance may deteriorate.

Before you start

You can navigate in the BIOS settings using the arrows on your keyboard.

Procedure

1 Open the BIOS settings, navigate to the Power Management and press ENTER.

Step example

Figure 1 HP blade BIOS setting power management

Commissioning Open MSS Cloud on OpenStack HP hardware requirements

2 Navigate to Power Regulator and select OS Control Mode.

Step example

Figure 2 HP blade BIOS setting for CPU power regulator

HP hardware requirements Commissioning Open MSS Cloud on OpenStack

3 Press F10 to save the new option setting, then Y to save and exit.

Step example

Figure 3 Saving the new HP blade BIOS setting

Commissioning Open MSS Cloud on OpenStack HP hardware requirements

4 Press the ESC key to go back to the main System Utilities Menu and select Reboot the
System.

Step example

Figure 4 Rebooting the system

3.2 Customizing the OpenStack on HP platform

You must customize the software platform in order to successfully deploy and operate
the Open MSS Cloud on OpenStack.

Equipment preconditions
You need the following:
A text editor is needed. In the examples, VI text editor is used.

Before you start

You must execute this procedure with root privileges on each controller node of the
OpenStack. Execute Steps 6 and 7 on each compute node of the OpenStack as well.

HP hardware requirements Commissioning Open MSS Cloud on OpenStack

g Note: The instructions and examples in this section are valid for OpenStack releases
up to Liberty. For newer or customized OpenStack distributions, please refer to the
vendor documentation on how to set these parameters, if necessary. The mentioned
parameter values, however, are typically already set up as default values.

Procedure

1 Verify the Maximum Transmission Unit (MTU) setting on the cloud tenant interfaces.

Execute this step on each controller and compute node of the OpenStack.
Sub-steps

a) Execute the following command.

Step example
ip a | grep " en"

b) For each physical interface listed in UP state, verify that the MTU is set to a value
of 1550 or higher.

Step example
4: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq
master ovs-system state UP qlen 1000

2 Verify that the network_vlan_ranges = physnet0 parameter is in the
plugin.ini file.

Access the file through the sudo vi /etc/neutron/plugin.ini path.
Add the file if it is missing.

Step example
[ml2_type_vlan]
# (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
# specifying physical_network names usable for VLAN provider and
# tenant networks, as well as ranges of VLAN tags on each
# physical_network available for allocation as tenant networks.
#
network_vlan_ranges = physnet0
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2

3 If you made changes in the previous step, restart the plugin service.

Execute the following commands:
sudo systemctl restart neutron-server neutron-dhcp-agent neutron-l3-
agent neutron-metadata-agent neutron-openvswitch-agent

Commissioning Open MSS Cloud on OpenStack HP hardware requirements

4 Set the value of the enable_isolated_metadata parameter to True in the
dhcp_agent.ini file.

Access the file through the sudo vi /etc/neutron/dhcp_agent.ini path.

Step example
# The DHCP server can assist with providing metadata support on
isolated
# networks. Setting this value to True will cause the DHCP server to
append
# specific host routes to the DHCP request. The metadata service will
only
# be activated when the subnet does not contain any router port. The
guest
# instance must be configured to request host routes via DHCP (Option
121).
# This option doesn't have any effect when force_metadata is set to
True.
enable_isolated_metadata = True

5 If you made changes in the previous step, restart the dhcp_agent.

Step example
sudo systemctl restart neutron-metadata-agent

6 Set the value of the arp_responder parameter to False in the
openvswitch_agent.ini file.

Execute this step on each controller and compute node of the OpenStack.
Access the file through the sudo vi
/etc/neutron/plugins/ml2/openvswitch_agent.ini path.

Step example
# Enable local ARP responder. Requires OVS 2.1. This is only used by
the l2
# population ML2 MechanismDriver.
arp_responder = False

7 If you made changes in the previous step, restart the plugin.

Execute this step on each controller and compute node of the OpenStack.

Step example
sudo systemctl restart neutron-openvswitch-agent

NDCS hardware requirements Commissioning Open MSS Cloud on OpenStack

4 NDCS hardware requirements

Nokia AirFrame Data Center Solution is a common virtual hardware platform for cloud
deployments. It consists of the server, switch, and storage products. Power Distribution
Units, interconnection/power cables, and rack/installations accessories are additional
products to build system-level solutions.

Nokia AirFrame Data Center Solution (NDCS) is delivered in a pre-equipped rack. NDCS
hardware building blocks include a rack, Power Distribution Units (PDUs), server nodes,
switches, transceivers, and cables. You can build different configurations based on
different needs using these building blocks.
NDCS uses the following hardware building blocks:
Equipment rack Provides mounting positions to 19” standard rackmount HW
products.
PDUs Two types of PDUs are available for different market regions,
leading power from the site power feed to server nodes and
switches.
Server Nodes 1U rackmount dual socket Haswell-based server including
interconnection adapters, security modules, storage devices,
cooling, power, and HW management.
Ethernet switches Provide interconnection between server nodes and
aggregation switches or routers.
Interconnection Pluggable transceivers are available for optical and electrical
products connections, while the interconnection cables are available for
network and power connections.

Regarding hard disks, AirFrame configurations support 2.5” and 3.5” Hard Disk Drive
(HDD) and 2.5” Solid State Drive (SSD) for local storage. The disks use SAS and SATA
interfaces.
NDCS uses extension cards to configure server barebone based on different
interconnection needs. They are connected to processor sockets via PCIe lanes.
The interconnection products include transceivers and cables. Transceivers are
pluggable and available for optical and electrical connections, while the interconnection
cables are available for network and power connections.
The one-rack maximum configuration for the reference configuration is composed of:
• One rack system: AR - RS24S6 - S1A for North America, or AR - RS24S6 - S1 for
other areas.
• 24 Compute Node 2 (AR - COMN2 - SET)
• Two Leaf Switches : two A - QFX5100Q32 or two AR - SWI40GP - S1
• One HW Management Switch (AR - SWI01 G F - A)

Each Compute Node 2 is connected to two Leaf switches with six 10GbE SFP+ ports to
enable switch redundancy.
Each Compute Node 2 has one 1000Base - T port for HW management network. This
port is connected to the HW Management switch (AR - SWI01GF - A).

Commissioning Open MSS Cloud on OpenStack NDCS hardware requirements

Other resources

Web links
AirFrame Data Center Solution

4.1 Customizing the OpenStack on NDCS platform

To be able to successfully deploy and operate the Open MSS Cloud on OpenStack, you
must customize the AirFrame Data Center Solution software platform.

Equipment preconditions
You need the following:
A text editor is needed. In the examples, VI text editor is used.

Before you start

You must execute this procedure with root privileges on each controller node of the
OpenStack. Execute steps 6 and 7on each compute node of the OpenStack as well.

g Note: The instructions and examples in this section are valid for OpenStack releases
up to Liberty. For newer, or customized OpenStack distributions, please refer to the
vendor documentation on how to set these parameters, if necessary. The mentioned
parameter values, however, are typically already set up as default values.

Procedure

1 Verify the Maximum Transmission Unit (MTU) setting on the cloud tenant interfaces.

For each interface, the MTU must be set to a value of 1550 or higher.

Step example
ifconfig ens4f0

2 Verify that the network_vlan_ranges = physnet0 parameter is in the
plugin.ini file.

Access the file through the sudo vi /etc/neutron/plugin.ini path.
Add the file if it is missing.

NDCS hardware requirements Commissioning Open MSS Cloud on OpenStack

#
# network_vlan_ranges =
#network_vlan_ranges =physnet-external,physnet-provider
network_vlan_ranges = physnet0
# Example: network_vlan_ranges = physnet1:1000:2999,physnet2

3 If you made changes in the previous step, restart the plugin service with the following
command.

Step example
sudo systemctl restart neutron-server neutron-dhcp-agent neutron-l3-
agent neutron-metadata-agent neutron-openvswitch-agent

4 Set the value of the enable_isolated_metadata parameter to True in the
dhcp_agent.ini file.

Access the file through the sudo vi /etc/neutron/dhcp_agent.ini path.

5 If you made changes in the previous step, restart the dhcp_agent.

Step example
sudo systemctl restart neutron-metadata-agent

6 Set the value of the arp_responder parameter to False in the
openvswitch_agent.ini file.

Execute this step on each controller and compute node of the OpenStack.
Access the file through the sudo
vi/etc/neutron/plugins/ml2/openvswitch_agent.ini path.

Commissioning Open MSS Cloud on OpenStack NDCS hardware requirements

Step example
# Enable local ARP responder. Requires OVS 2.1. This is only used by
the l2
# population ML2 MechanismDriver.
arp_responder = False

7 If you made changes in the previous step, restart the plugin.

Execute this step on each controller and compute node of the OpenStack.

Step example
sudo systemctl restart neutron-openvswitch-agent

4.1.1 Customizing OpenStack in case of root volume

deployment
Using the root volume feature, as described in section Using root volumes, includes a
large amount of volume operations. Depending on the default values it may lead to
volume state inconsistency, especially during undeployment. To avoid potential
problems, make sure the following configuration values are set sufficiently high.

Before you start

g Note: Execute these steps on all controller nodes.

Procedure

1 Set the value of the rpc_conn_pool_size parameter to 128 in the cinder.conf
file.

The file is located in the sudo vi /etc/cinder/ folder.

Step example
# Size of RPC connection pool. (integer value)
rpc_conn_pool_size = 128

NDCS hardware requirements Commissioning Open MSS Cloud on OpenStack

2 Set the value of the max_overflow parameter to -1 in the cinder.conf file.

Step example
# If set, use this value for max_overflow with SQLAlchemy. (integer
value)
max_overflow = -1

3 Restart the cinder services.

Step example
sudo systemctl restart openstack-cinder-api
sudo systemctl restart openstack-cinder-scheduler
sudo systemctl restart openstack-cinder-volume

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

5 Application deployment requirements for

OpenStack
Whether the VNF configuration and installation is automatic or manual depends on the
software platform.

If the Virtual Network Function (VNF) is deployed on top of Nokia Cloud Infrastructure on
OpenStack, the configuration is executed during the installation automatically. However,
if a third party infrastructure is used, the configuration must be performed manually.

Related procedures
Modifying the VNF attribute parameter values in CBAM on page 88

5.1 Open MSS capacity requirements

In order to deploy a full capacity Open MSS on a cluster that has dual 12 core CPU
sockets, you must ensure that the cluster contains 8 hosts, including the one extra host
needed for high availability.

It is possible to start the Open MSS with the basic increment, which requires at least four
hosts in the cluster. The four hosts are enough to execute a subset of the Open MSS
Virtual Machines (VMs) if the application provides only 700k of the total 3M Busy Hour
Call Attempts (BHCA) capacity. The four host clusters can provide adequate computing
capacity for the basic increment, even if the VMs are running with maximum CPU
utilization. The cluster can tolerate one host failure without performance degradation.
The capacity can be extended up to 3M users or BHCA capacity in increments.
Before calculating the number of blades, you must know the number of physical and
logical cores in the blades in the specific cluster. The basic increment includes all the
VMs of the full-capacity Open MSS except for the Generic IP Signaling Units (GISUs).
The increments differ from each other in the number of additional GISUs.
For planning and calculation of the required blades in a cluster executing the Open MSS,
see document Open MSS CLOUD server blade, memory and storage requirements in
MSS Cloud CM CFP5 release - OpenStack. This calculation never includes the three
controller blades needed for High Availability (HA) for a two-host-failure tolerant setup.
The host operating system requires at least two vCPUs from the total number of vCPUs
for each compute node. These are always reserved before calculating the total number
of blades. The resources for the Open MSS deployment should be available within one
OpenStack availability zone. Due to anti-affinity rules that ensure resiliency, a minimum
of four separate hosts are required in the availability zone.

Other resources

References to other documents

Open MSS CLOUD server blade, memory and storage requirements in MSS Cloud CM
CFP5 release - OpenStack

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

5.2 Open MSS internal storage architecture

The Open MSS Cloud uses a storage architecture based on Virtual Storage Appliances.
The OpenStack data store is necessary for storing the Open MSS Virtual Machines’
different configuration files.

Virtual Storage Appliances (VSAs) are RedHat Enterprise Linux 7–based Virtual
Machines (VMs) that are not part of the Virtual Server Platform (VSP) cluster.
There are two VSAs in a Virtual Network Function (VNF): VSA-1 serving WDU-0 disks,
and VSA-2 serving WDU-1 disks. Each VSA has a root disk for booting the VSA. The
disk contains all software artifacts needed for the VSA and stores all the logs.
The purposes of the different types of disks are as follows:
16 GB root disk The system disk of the VSA with pre-installed RHEL 7 operating
system and iSCSI targets.
The root disks are not exposed on the iSCSI interface.

100 GB main disk These disks serve the Operation and Maintenance Units (OMUs).

The main disks are exposed on both iSCSI interfaces.

180 GB These disks serve the Charging Units (CHUs).
supplementary
The supplementary disks are exposed on both iSCSI interfaces.
disk

The Open MSS VMs are connected to the VSA VMs through iSCSI, where the OMU and
CHU VMs are the initiators and the VSA VMs are the targets.
Each VSA has its own Operation and Maintenance (OaM) connection connected to the
external OAM network. This connection is used for troubleshooting VSAs.
The sizes of the different deployment artifacts are indicated in table Sizes of deployment
artifacts.

Table 5 Sizes of deployment artifacts
Artifact Download size Needed storage in
datacenter
Open MSS CloudBand ~100 kB N/A
Application Manager (CBAM)
template file including VSAs
Open MSS Cloud Heat ~100 kB N/A
template file including VSAs
The File Allocation Table (FAT) ~4 MB 1 GB
disk image with iPXE for OMU
boot (cr3ipxtx.img)
VSA root disk images ~700 MB 16 GB
OMU disk image ~200 MB 100 GB (each)
CHU disk image N/A 180 GB (each)

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

VSAs are not managed by the recovery system of the VSP, they cannot write VSP logs
and alarms, and they boot independently from the OMU.

Figure 5 High-level overview of the Open MSS disk connections

The Open MSS storage requirements are as follows:

Table 6 Open MSS storage requirements in case of small (3M BHCA) capacity
Resource Allocations
Storage Area Network (SAN) requirements (2*100+4*180+2*16)+1GB per VM

5.3 Creating a Project

The Project collects all the resources and users to deploy the Open MSS.

Before you start

To create a project, you must have admin rights.

Procedure

1 Log in to Horizon, then on the menu bar, select the Identity menu.

g Note: Horizon is the OpenStack dashboard.

2 In the Identity menu, select the Projects menu item.

3 In the Projects pane, click Create Project.

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

4 In the Create Project pop-up window, on the Project Information tab, type the name of

the project in the Name field.

Step example

Figure 6 Defining the project name on the Project Information tab

5 In the Create Project window, on the Quota tab, set the maximum quotas for the project.
Then click Create Project.

Type the maximum quotas in the fields listed in table Quota values.

g Note: Value -1 means unlimited quota. Unlimited quote is also suitable for the
values in table Quota values.

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

g Note: The quota values for VCPUs, Instance,
Total size of Volumes and Snapshots and RAM vary by MSS capacity. Values
in table Quota values are for maximum supported capacity. To set more exact
values in case of smaller deployments, refer to document Open MSS CLOUD
server blade, memory and storage requirements in MSS Cloud CM CFP5 release
- OpenStack. Values for Networks, Ports and Subnets are the same for all
capacity deployments.
The quota values for Volumes and Snapshots should be set up considering the
planned backup methods. If volume-based backup is used, the quota needs to
be increased to accommodate the snapshot and volume copies for backup
purposes. For details about volume-based backup, see document
Backup and Redeployment of Open MSS Cloud on OpenStack.
If the Open MSS Cloud is deployed using root volumes, increase the volume
allocation to include +1 GB for all VM instances except VSA, and +16 GB for all
VSA instances. For more information on root volumes see section
Using root volumes.

Step example

Table 7 Quota values
Field name Value
VCPUs 500
Instances 200
Total size of Volumes and Snapshots (GB) 3000
RAM (MB) 500 000
Networks 100
Ports 1000
Subnets 500

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

Figure 7 Setting the maximum quotas for the project

Result

The new Project appears in the Projects list.

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

Figure 8 Created Project

Related procedures
Creating the tenant user on page 37
Changing quotas on page 40

5.4 Creating the tenant user

You must create a tenant user for the Open MSS on the controller node.

Before you start

A valid and active Project must exist in Horizon.

g Note: Throughout this document, the controller access is described for using
OpenStack related command line. However, if local policies forbid access to the
controller node, use the undercloud node for the same purpose, as that also provides
suitable access.

Procedure

1 Log in to Horizon and select the Identity tab.

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

2 In the Users menu, click Create User.

Step example

3 In the Create User window, provide the necessary data, and click Create User.

Step example

Figure 9 Creating the user

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

g Note: If you do not set the Role to admin at this time, you can do so later with
the openstack role add command:
openstack role add --project mss8 --user mss8 admin

Step result

Figure 10 The tenant user is created

4 Create a tenant user.

Sub-steps

a) Create a keystone credential file on the controller node. Use an existing
credential file for basis, such as overcloudrc.

Step example
cp overcloudrc keystonerc_mss

b) Add the following content to the file: user name (OS_USERNAME), project name
(OS_PROJECT_NAME), password (OS_PASSWORD).

The project name was created previously. For more information see section
Creating a Project.

Step example
vi keystonerc_mss

export OS_NO_CACHE=True
export COMPUTE_API_VERSION=1.1
export OS_USERNAME=mss8
export no_proxy=,172.17.1.10

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

export OS_PROJECT_NAME=mss8
export OS_CLOUDNAME=overcloud
export OS_AUTH_URL=http://172.17.1.10:5000/v2.0
export NOVA_VERSION=1.1
export OS_PASSWORD=password12
export PS1='[\u@\h \W(SYS17)]\$ '

c) Take the keystone credential file into use with the command source
keystonerc_mss.

Step example
[cbis-admin@overcloud-controller-0 ~]$ source keystonerc_mss
[cbis-admin@overcloud-controller-0 (mss) ~]$

Related procedures
Creating a Project on page 33
Changing quotas on page 40
Creating CHU volumes in Cinder on page 64
Creating the OMU disk image on page 57
Uploading the VSA image on page 51
Uploading the iPXE image on page 48
Uploading the VNF template to the controller node on page 75

5.5 Changing quotas

Quotas are operational limits that can be changed to prevent the exhaustion of system
capacity. They must be set using cloud administrator access.

Before you start

The tenant user and the Project must exist in Horizon.

Required preconditions links

Creating the tenant user on page 37

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

Procedure

1 Take keystone credential file into use with the source keystonerc_mss command.

Step example
[cbis-admin@overcloud-controller-0 ~]$ source keystonerc_mss
[cbis-admin@overcloud-controller-0 (mss) ~]$

g Note: You can get a list of the projects using the openstack project list

command.

2 Check the quotas in Nova with the openstack quota show command.

Step example
openstack quota show mss

Step result
[cbis-admin@overcloud-controller-0 (mss) ~]$ openstack quota show
+------------------------+----------------------------------+
| Field | Value |
+------------------------+----------------------------------+
| backup_gigabytes | 1000 |
| backups | 10 |
| cores | -1 |
| fixed-ips | -1 |
| floating-ips | -1 |
| gigabytes | -1 |
| gigabytes_tripleo-ceph | -1 |
| injected-file-size | 10240 |
| injected-files | 5 |
| injected-path-size | 255 |
| instances | -1 |
| key-pairs | 100 |
| networks | -1 |
| per_volume_gigabytes | -1 |
| ports | -1 |
| project | 6b3cc759d7244725b7a5238323497a1a |
| properties | 128 |
| ram | -1 |
| rbac-policies | 10 |
| routers | -1 |
| secgroup-rules | -1 |
| secgroups | -1 |
| server-group-members | 10 |
| server-groups | 40 |
| snapshots | -1 |
| snapshots_tripleo-ceph | -1 |
| subnetpools | -1 |
| subnets | -1 |

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

| trunk | -1 |
| volumes | -1 |
| volumes_tripleo-ceph | -1 |
+------------------------+----------------------------------+

3 Update the server-groups and server-group-members quotas using the openstack
quota-update command.

You can update the other quotas if necessary.

Step example
openstack quota set --server-groups 60 mss
openstack quota set --server-group-members 15 mss

Step result
[cbis-admin@overcloud-controller-0 (mss) ~]$ openstack quota show
+------------------------+----------------------------------+
| Field | Value |
+------------------------+----------------------------------+
| backup_gigabytes | 1000 |
| backups | 10 |
| cores | -1 |
| fixed-ips | -1 |
| floating-ips | -1 |
| gigabytes | -1 |
| gigabytes_tripleo-ceph | -1 |
| injected-file-size | 10240 |
| injected-files | 5 |
| injected-path-size | 255 |
| instances | -1 |
| key-pairs | 100 |
| networks | -1 |
| per_volume_gigabytes | -1 |
| ports | -1 |
| project | 6b3cc759d7244725b7a5238323497a1a |
| properties | 128 |
| ram | -1 |
| rbac-policies | 10 |
| routers | -1 |
| secgroup-rules | -1 |
| secgroups | -1 |
| server-group-members | 15 |
| server-groups | 60 |
| snapshots | -1 |
| snapshots_tripleo-ceph | -1 |
| subnetpools | -1 |
| subnets | -1 |
| trunk | -1 |
| volumes | -1 |

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

| volumes_tripleo-ceph | -1 |
+------------------------+----------------------------------+

Related procedures
Creating a Project on page 33
Creating the tenant user on page 37

5.6 Adjusting maximum Heat stack size

Adjusting the maximum Heat stack size is necessary at deploying with large capacity.
You must modify the heat.conf file and restart the Heat services.

Purpose
In case Cloud MSS is deployed with large capacity (more than 150 Virtual Machines
(VMs)), adjust the maximum size of one Heat stack.
This step is necessary even if CBAM based deployment is used.
Execute this procedure with root privileges on each controller node of the OpenStack.

Equipment preconditions
You need the following:
A text editor. VI text editor is used in the examples.

Procedure

1 Access the heat.conf file using the sudo vi /etc/heat/heat.conf command.

2 In the heat.conf file, set the value of the max_resources_per_stack parameter
to at least 2000, or unlimited.

Step example
# Maximum resources allowed per top-level stack. -1 stands for
unlimited.
# (integer value)
max_resources_per_stack = -1

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

3 If you made changes in the previous step, restart the Heat services.

Sub-steps

a) List the Heat services.

Step example
sudo systemctl status | grep "openstack-heat\-"
[cbis-admin@overcloud-controller-2 ~]$ sudo systemctl status |
grep "openstack-heat\-"
+-openstack-heat-api-cfn.service
+-openstack-heat-api.service
+-openstack-heat-engine.service
[cbis-admin@overcloud-controller-2 ~]$

b) Restart each Heat service.

Step example
[cbis-admin@overcloud-controller-2 ~]$ sudo systemctl restart
openstack-heat-api-cloudwatch.service
[cbis-admin@overcloud-controller-2 ~]$ sudo systemctl restart
openstack-heat-api-cfn.service
[cbis-admin@overcloud-controller-2 ~]$ sudo systemctl restart
openstack-heat-api.service
[cbis-admin@overcloud-controller-2 ~]$ sudo systemctl restart
openstack-heat-engine.service

5.7 Creating provider networks

Before deployment, create the provider networks for the tenant user on the controller
node of the OpenStack.

Procedure

1 Take the keystone credential file into use with the source keystonerc_mss
command.

Step example
[cbis-admin@overcloud-controller-0 ~]$ source keystonerc_mss
[cbis-admin@overcloud-controller-0 (mss) ~]$

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

2 Create the provider networks.

Create the provider networks according to table Provider networks.
neutron net-create <network name> --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id <xxx>

Table 8 Provider networks
Example provider network name Purpose
MSS_OaM MSS OAM
MSS_CP-SCTP-Mh-Pri MSS Core Control Plane Multi-homed
Primary
MSS_CP-SCTP-Mh-Sec MSS Core Control Plane Multi-homed
Secondary
MSS_CP-SCTP-Sh-TCP-UDP MSS Core Control Plane Single-homed
MSS_OaM-SCTP-Mh-Pri MSS Core OAM Multi-homed Primary
MSS_OaM-SCTP-Mh-Sec MSS Core OAM Multi-homed Secondary
MSS_OaM-SCTP-Sh-TCP-UDP MSS Core OAM Single-homed
MSS_CHA MSS Charging
MSS_LI MSS OLCM

When creating provider networks, allocate a segmentation ID for each one. The
segmentation ID is the VLAN ID for the given provider network.

Step example
neutron net-create MSS8_OaM --provider:network_type vlan --provider:physical_network
physnet0 --provider:segmentation_id 1660
neutron net-create MSS8_CP-SCTP-Mh-Pri --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id 1661
neutron net-create MSS8_CP-SCTP-Mh-Sec --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id 1662
neutron net-create MSS8_CP-SCTP-Sh-TCP-UDP --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id 1663
neutron net-create MSS8_OaM-SCTP-Mh-Pri --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id 1664
neutron net-create MSS8_OaM-SCTP-Mh-Sec --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id 1665
neutron net-create MSS8_OaM-SCTP-Sh-TCP-UDP --provider:network_type vlan --
provider:physical_network physnet0 --provider:segmentation_id 1666
neutron net-create MSS8_CHA --provider:network_type vlan --provider:physical_network
physnet0 --provider:segmentation_id 1667
neutron net-create MSS8_LI --provider:network_type vlan --provider:physical_network
physnet0 --provider:segmentation_id 1668

Step result

This example shows the MSS8_CP-SCTP-Mh-Pri result only.

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

3 Create the provider subnets.

DHCP is required for the OaM subnet if the OMU's DHCP client is used. The
subnet's allocation pool should contain 3 addresses for the DHCP agents - excluding
the IP addresses defined in the MSS application template - the OMU Logical IP
address and the Default Gateway IP address. The excluded addresses are the
following:
• DEF. GW.—192.0.2.65
• VSA0—192.0.2.66
• VSA1—192.0.2.67
• OMU-0 PHY—192.0.2.68
• OMU-1 PHY—192.0.2.69
• OMU LOG—192.0.2.70

g Note: Subnet naming usually follows the <network name>_subnet

convention.

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

Step example
Create the OaM subnet with the --enable-dhcp switch:
• With enabled OpenStack DHCP server:
neutron subnet-create --name MSS8_OaM_subnet --enable-dhcp --allocation-pool
start=192.0.2.76,end=192.0.2.78 --gateway 192.0.2.65 MSS8_OaM 192.0.2.64/28
• Without OpenStack DHCP server:
neutron subnet-create --name MSS8_OaM_subnet --disable-dhcp --no-gateway MSS8_OaM
192.0.2.64/28

Create the rest of the subnets the following way:
neutron subnet-create --name MSS8_CP-SCTP-Mh-Pri_subnet --disable-dhcp --no-gateway
MSS8_CP-SCTP-Mh-Pri 192.0.2.80/28
neutron subnet-create --name MSS8_CP-SCTP-Mh-Sec_subnet --disable-dhcp --no-gateway
MSS8_CP-SCTP-Mh-Sec 192.0.2.69/28
neutron subnet-create --name MSS8_CP-SCTP-Sh-TCP-UDP_subnet --disable-dhcp --no-gateway
MSS8_CP-SCTP-Sh-TCP-UDP 192.0.2.112/28
neutron subnet-create --name MSS8_OaM-SCTP-Mh-Pri_subnet --disable-dhcp --no-gateway
MSS8_OaM-SCTP-Mh-Pri 192.0.2.128/28
neutron subnet-create --name MSS8_OaM-SCTP-Mh-Sec_subnet --disable-dhcp --no-gateway
MSS8_OaM-SCTP-Mh-Sec 192.0.2.144/28
neutron subnet-create --name MSS8_OaM-SCTP-Sh-TCP-UDP_subnet --disable-dhcp --no-gateway
MSS8_OaM-SCTP-Sh-TCP-UDP 192.0.2.160/28
neutron subnet-create --name MSS8_CHA_subnet --disable-dhcp --no-gateway MSS8_CHA
192.0.2.176/28
neutron subnet-create --name MSS8_LI_subnet --disable-dhcp --no-gateway MSS8_LI
192.0.2.192/28

Step result

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

| revision_number | 2 |
| service_types | [] |
| subnetpool_id | None |
| updated_at | 2018-05-22T08:52:33Z |
+-------------------+--------------------------------------+

4 Optional step. If the OaM network uses IPv6, the subnets have to be created accordingly.

The subnet range in the example is 2001:DB8:6000:1000::/64.

Step example
neutron subnet-create --name MSS8_OaM_v6_subnet MSS8_OaM --ip-version
6
2001:DB8:6000:1000::/64 --disable-dhcp --gateway
2001:DB80:6000:1000::1

Step result
Created a new subnet:
+-------------------+-------------------------------------------------------------------------------------+
| Field | Value |
+-------------------+-------------------------------------------------------------------------------------+
| allocation_pools | {"start": "2001:db8:6000:1000::1", "end": "2001:db8:6000:1000:ffff:ffff:ffff:ffff"} |
| cidr | 2001:db8:6000:1000::/64 |
| created_at | 2019-08-16T09:08:03Z |
| description | |
| dns_nameservers | |
| enable_dhcp | False |
| gateway_ip | 2001:db80:6000:1000::1 |
| host_routes | |
| id | 9471e24c-476e-40df-bac6-7d432c449da6 |
| ip_version | 6 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | MSS08_OaM_v6_subnet |
| network_id | af030ca3-6b63-4097-912e-de4587a6b91a |
| project_id | 730f696e62a1416c9ef4d7ba4b3a8fcb |
| revision_number | 2 |
| service_types | |
| subnetpool_id | |
| tenant_id | 730f696e62a1416c9ef4d7ba4b3a8fcb |
| updated_at | 2019-08-16T09:08:03Z |
+-------------------+-------------------------------------------------------------------------------------+

Related procedures
Modifying the VNF attribute parameter values in CBAM on page 88

5.8 Uploading the iPXE image

iPXE supports the centralized boot procedure of the VSP cluster.

Procedure

1 Log in to the OpenStack dashboard (Horizon) under the created tenant user.

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

2 In the Project menu, select the Compute menu item.

3 In the Compute menu, select the Images menu item.

4 In the Images pane, click Create Image.

Step example

Figure 11 Starting the image creation

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

5 In the Create Image window, provide the necessary data for the iPXE and select the
image file. Once done, click Create Image.

Step example

Figure 12 Uploading the iPXE image

Result

Figure 13 iPXE image is uploaded

Related procedures
Uploading the VSA image on page 51

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

Creating the tenant user on page 37
Modifying the VNF attribute parameter values in CBAM on page 88

5.9 Uploading the VSA image

Virtual Storage Appliances are the storage servers for the Open MSS. The VSA images
are the disks of the VSAs.

Before you start

You must create the tenant user.

Required preconditions links

Creating the tenant user on page 37

Procedure

1 Log in to the OpenStack dashboard (Horizon) under the created tenant user.

2 In the Project menu, select the Compute menu item.

3 In the Compute menu, select the Images menu item.

4 In the Images pane, click Create Image.

Step example

Figure 14 Starting the image creation

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

5 In the Create Image window, provide the necessary data for the VSA, browse to the
image file, and click Create Image.

Step example

Figure 15 Providing the VSA image data

Result

Figure 16 VSA image is uploaded

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

g Note: The web based image upload may time out in case of large image files. Upload
is also possible using the openstack image create command.
openstack image create --disk-format qcow2 --container-format bare --
public --file ./vsa-root_4.4-0.qcow2 VSA_4.4-0

Related procedures
Uploading the iPXE image on page 48
Creating the tenant user on page 37
Creating VSA key pairs on page 53
Modifying the VNF attribute parameter values in CBAM on page 88

5.10 Creating VSA key pairs

Key pairs are SSH credentials that are injected into images when they are launched.

Before you start

You must upload the VSA image to Horizon.

Procedure

1 Log in to Horizon and select the Project menu.

g Note: You must login with the user that you created for the project, which is
mss8 in the example. If you login with a different one, for example with admin,
the Key Pair will not be recognized at application deployment.

2 In the Compute menu, open the Key Pairs menu item.

3 In the Key Pairs pane, click Create Key Pair.

g Note: It is also possible to import an existing key. For this option, choose the
Import Key Pair option. To import the key part, copy the public key in the dialog
box. The public key contains the string ssh-rsa followed by a space and the
public key string.

Application deployment requirements for OpenStack Commissioning Open MSS Cloud on OpenStack

Step example

Figure 17 Creating key pairs

4 In the Create Key Pair pop-up window, type the name of the key pair, then click Create

Key Pair.

Use the same name that is used in the example (vsa).

Step example

Figure 18 Defining the key pair name

Step result

The key pair is downloaded automatically.

w You can download the key only one time. Make sure the key is stored at a safe
location.

Commissioning Open MSS Cloud on OpenStack Application deployment requirements for OpenStack

Figure 19 Automatic key pair download

Result

Figure 20 Key pair is created

Related procedures
Uploading the VSA image on page 51
Modifying the VNF attribute parameter values in CBAM on page 88

Application content provisioning Commissioning Open MSS Cloud on OpenStack

6 Application content provisioning

Provisioning the Open MSS VSA and Open MSS application with Heat/CBAM templates
is required for the application deployment.

The template packages contain all the templates and configuration files that are needed
to deploy the Open MSS with Heat/CloudBand Application Manager (CBAM).
The template naming convention is the following:
NOKIA_<NE>_CLOUD_OPENSTACK_<VNF Manager>_<VNF manager
version>_<maximum BHCA capacity>_CFP5_<optional
customization>_<version>.ZIP
Where:
NE MSS or TRS
VNF Manager CBAM or Heat. Files marked with Heat are for deployment
without CBAM.
VNF manager 17_5_2 or 19_0_0
version (in
• Files marked with 17_5_2 are used with CBAM 17.5 SP2,
case of CBAM):
CBAM 18 or CBAM 18.5
• Files marked with 19_0_0 are used with CBAM 19 or later.

Maximum BHCA Maximum amount of BHCA the NE instance is planned to serve.

capacity This value determines also partial capacity steps and VM counts.
Please refer to document Open MSS CLOUD server blade,
memory and storage requirements in Open MSS Cloud CM
CFP5 release – OpenStack for definition of capacities.
Optional Feature indications which have effect on the template:
customization
• Files marked with [EF] contain support for predefined flavor
usage.
• Files marked with [RV] contain support for root volume
usage.
• Files marked with [DPDK] contain support for OVS-DPDK
usage.
• Files marked with EF, RV and DPDK ([EF] [RV] [DPDK])
contain support for predefined flavor, root volume usage and
OVS-DPDK.

Version Version number of template.

The following different disk images are also required:
cr3ipxtx.vmdk File Allocation Table (FAT) formatted disk image
with iPXE and boot configuration for Open MSS
Virtual Machines (VMs).
vsa-root.qcow2 Virtual Storage Appliance (VSA) root disk
MSS17OMU-W0.img.bz2 zipped raw disk image

Commissioning Open MSS Cloud on OpenStack Application content provisioning

MSS17OMU-W0.qcow2 qcow2 disk image

g Note: Use the file format (zipped raw or qcow2) that was distributed to you via the
Software Supply Tool.

Open MSS deployment files are distributed via the Support Portal for OpenStack
deployment.

Other resources

Web links
Support Portal

6.1 Creating the OMU disk image

After you have created the tenant user, create the OMU disk image in Horizon.

Before you start

g Note: The OMU disk image can either be in raw or qcow2 format. Choose the way of
creation in Step 6 according to the type of image you want to use.

Required preconditions links

Creating the tenant user on page 37

Procedure

1 Unzip the OMU disk image file using a suitable compression application, such as 7-Zip.

g Note: The size of the uncompressed image file is 100 GB. Make sure that there
is enough disk space on your hard drive.

2 Log in to the OpenStack dashboard (Horizon) under the created tenant user.

3 In the Project menu, select the Compute menu item.

4 In the Compute menu, select the Images menu item.

Application content provisioning Commissioning Open MSS Cloud on OpenStack

5 In the Images pane, click Create Image.

Step example

Figure 21 Starting the image creation

Commissioning Open MSS Cloud on OpenStack Application content provisioning

6 In the Create Image pop-up window, type the name of the OMU disk and click Browse
and select the image file in either raw of qcow2 format. Then click Create Image.

Step example

Figure 22 Uploading the extracted raw disk image file and creating the image

Application content provisioning Commissioning Open MSS Cloud on OpenStack

Step example

Figure 23 Uploading the extracted qcow2 disk image file and creating the image

g Note: The web based image upload may time out in case of large image files.
Upload of the uncompressed image is also possible using the
openstack image create command.
Create the image in either raw or qcow2 format.
openstack image create --disk-format <source format of image> --
container-format bare
--public --file ./<source file name and extension> <Name of image
to create>

Image creation in raw format:
openstack image create --disk-format raw --container-format bare
--public --file ./MSS8_OMU-W0.img MSS8_OMU-W0
Image creation in qcow2 format:
openstack image create --disk-format qcow2 --container-format bare
--public --file ./MSS8_OMU-W0.qcow2 MSS8_OMU-W0

Commissioning Open MSS Cloud on OpenStack Application content provisioning

Related procedures
Creating the tenant user on page 37
Creating CHU volumes in Cinder on page 64
Creating the OMU volumes on page 61

6.2 Creating the OMU volumes

After creating the OMU disk, create the OMU volume in Horizon.

Before you start

Verify that the OMU disk is uploaded.

Procedure

1 Log in to Horizon, then on the menu bar, select the Project menu.

g Note: Horizon is the OpenStack dashboard.

2 In the Project menu, select the Volumes menu item.

3 In the Volumes pane, click Create Volume.

4 In the Create Volume pop-up window, provide the necessary data.

The size of the volume must be 100 GB. Set the Volume Source to Image and
select the created OMU image in the Use image as a source field.

g Note: Nokia recommends that you use the following naming convention for OMU
volume names: <prefix>_OMU-W<disk index>.
Example: MSS8_OMU-W0

Application content provisioning Commissioning Open MSS Cloud on OpenStack

Step example

Figure 24 Creating the volume

Commissioning Open MSS Cloud on OpenStack Application content provisioning

5 In the Create Volume window, click the Create Volume button.

Step example

Figure 25 Finishing the OMU volume creation

6 Create the OMU volume for disk 1.

Repeat steps 3 through 5 using the same source image but index 1 in the volume
name.

g Note: In case of backed-up MSS disk image set redeployment, where both OMU
disks are saved, upload both images separately and create one volume from
each.

Related procedures
Creating the OMU disk image on page 57

Application content provisioning Commissioning Open MSS Cloud on OpenStack

Modifying the VNF attribute parameter values in CBAM on page 88

6.3 Creating CHU volumes in Cinder

You must create volumes for the OMU and CHU instances. You can create the CHU
volumes with Cinder commands on the controller node of OpenStack or on the web
interface.

Purpose
A volume is a detachable block storage device that can be attached to an instance to
enable persistent storage.

Before you start

You must create the tenant user.
Take keystone credential file into use with the source keystonerc_MSSxx
command.

Required preconditions links

Creating the tenant user on page 37

• Create the Charging Unit (CHU) disks.

Step example
openstack volume create MSS8_CHU0-W0 --size 180
openstack volume create MSS8_CHU0-W1 --size 180
openstack volume create MSS8_CHU1-W0 --size 180
openstack volume create MSS8_CHU1-W1 --size 180
openstack volume list

Result

Related procedures
Creating the tenant user on page 37
Creating the OMU disk image on page 57
Modifying the VNF attribute parameter values in CBAM on page 88

Commissioning Open MSS Cloud on OpenStack Application content provisioning

6.4 Providing OVS-DPDK compatible flavors

OVS-DPDK compatible VNF requires specific flavor settings.

OVS-DPDK compatible VNF requires the usage of huge memory pages. Therefore, you
must define the flavors the VNF uses accordingly. Define the hw:mem_page size
property of the flavors to value large.

• If the VNF uses default flavors, this flavor property is automatically set by the
provided official OVS-DPDK compatible template itself.
• If the VNF uses predefined flavors, this property must be set manually. For
instructions, see section Creating predefined flavors.

6.5 Creating predefined flavors

You can create flavors using a predefined flavor template.

In OpenStack, flavors define the computing, memory, and storage capacity of Nova
computing instances. By default, the MSS template creates the flavors, meaning that
Cloud administrator access rights are needed to create and modify flavors. With
predefined flavors, you can deploy Open MSS Cloud without Cloud administrator rights,
and include additional placement guidance in flavors.
The following flavor naming convention is used in the default environment file. You can
create flavors using the examples in sections Creating flavors using OpenStack
command line and Creating flavors in the dashboard. Creating predefined flavors is
optional.
• MSS_2_2
• MSS_2_3
• MSS_3_2
• MSS_3_3
• MSS_4_1
• MSS_6_2
• MSS_VSA

The naming convention is MSS_x_y, where
• x is the number of Virtual CPUs
• y is the RAM size in gigabytes

g Note: The disk size must be 1 GB in all flavors. When you deploy the MSS using root
volumes, the disk size can be 0.

g Note: Create the MSS_VSA flavor with two virtual CPUs, 1 GB of RAM and 16 GB of
hard disk. When you deploy the MSS using root volumes, the disk size can be 0.

Application content provisioning Commissioning Open MSS Cloud on OpenStack

g Note: Do not customize vCPU / RAM / disk values for any reason. Open MSS Cloud
operation is only supported when the exact specified values are used.

g Note: In case of Open TRS Cloud deployment, use MSS_1_1 flavor instead of
MSS_4_1.

g Note: Ephemeral and swap disk is not needed for any of the flavors.

g Note: Only the Cloud administrator can create flavors in both the dashboard and the
OpenStack command line. Same set of predefined flavors may be used for several
MSS deployments.

g Note: All created flavors should have the hw:watchdog_action property set to value
reset. This enables the Open MSS Cloud to take advantage of the emulated hardware
watchdog and recover frozen virtual machines in case of software failure.

g Note: For OVS-DPDK compatible VNFs all created flavors must use huge memory
pages, so the hw:mem_page_size property must be set to value large.

6.5.1 Creating flavors using OpenStack command line

In this example, we create a flavor with two virtual CPUs, 2 GB of RAM, and a 1 GB
Hard Disk.

Procedure

1 Create the flavor.

Step example
$ openstack flavor create --vcpus 2 --ram 2048 --disk 1 --public
MSS_2_2

Step result

+----------------------------+--------------------------------------+
| Field | Value |
+----------------------------+--------------------------------------+
| OS-FLV-DISABLED:disabled | False |
| OS-FLV-EXT-DATA:ephemeral | 0 |
| disk | 1 |
| id | b5ca2e8d-80da-45f9-a756-dc49f4e924c9 |
| name | MSS_2_2 |
| os-flavor-access:is_public | True |
| ram | 2048 |
| rxtx_factor | 1.0 |
| swap | |
| vcpus | 2 |
+----------------------------+--------------------------------------+

Commissioning Open MSS Cloud on OpenStack Application content provisioning

2 Add watchdog reset specification to the flavor.

Step example
$ openstack flavor set MSS_2_2 --property hw:watchdog_action=reset

3 Define huge page usage if the flavor is used for an OVS-DPDK enabled VNF.

Step example
$ openstack flavor set MSS_2_2 --property hw:mem_page_size=large

4 Verify the created flavor.

Step example
$ openstack flavor show MSS_2_2

Step result

6.5.2 Creating flavors in the dashboard

Following this procedure, you can create flavors in the dashboard.

Procedure

1 In Horizon, select the Admin menu, then select the Compute menu item.

2 In the Compute menu, select the Flavors menu item.

Application content provisioning Commissioning Open MSS Cloud on OpenStack

3 In the Flavors pane, click Create Flavor.

4 In the Create Flavor pop-up window, fill all fields with the appropriate information. Then
click the Create Flavor button.

Step example

Figure 26 Create Flavor window

Step result
Once the flavor is created, the Success: Created new flavor message
appears, and the flavor is visible.

Commissioning Open MSS Cloud on OpenStack Application content provisioning

Figure 27 Flavor is successfully created

Figure 28 The created flavor

Application content provisioning Commissioning Open MSS Cloud on OpenStack

5 Add hw:watchdog_action metadata to the flavor. Set the value to reset.

Step example

Figure 29 Setting the hw:watchdog_action metadata

Commissioning Open MSS Cloud on OpenStack Application content provisioning

6 Define huge page usage if the flavor is used for an OVS-DPDK enabled VNF. Add
hw:mem_page_size metadata to the flavor. Set the value to large.

Step example

Figure 30 Setting the hw:mem_page_size metadata

6.6 Deleting predefined flavors

Use OpenStack command line or the OpenStack dashboard to delete predefined flavors.

Application content provisioning Commissioning Open MSS Cloud on OpenStack

In OpenStack, flavors define the computing, memory and storage capacity of Nova
computing instances. By default, the MSS template creates and deletes the flavors. With
predefined flavors, you can deploy Open MSS Cloud without cloud administrator rights,
and include additional placement guidance in flavors.
You can delete predefined flavors after the MSS VNF is undeployed, using OpenStack
command line or the OpenStack dashboard. Both solutions achieve the same outcome,
there is no need to execute both.

g Note: Only delete the predefined flavors if you no longer need to use them or the MSS
VNF is undeployed. For more information on undeployment, see document
Backup and Redeployment of Open MSS Cloud on OpenStack.

6.6.1 Deleting a flavor using OpenStack command line

You can delete a flavor using OpenStack command line.

Procedure

1 Delete the flavor.

Step example
$ openstack flavor delete MSS_2_2

g Note: Due to a known OpenStack bug, in several OpenStack releases the
openstack flavor delete command is not working properly. In this case
use the nova flavor-delete command instead.

2 Verify that the flavor is deleted.

Step example
$ openstack flavor show MSS_2_2

Step result
No flavor with a name or ID of 'MSS_2_2' exists.

6.6.2 Deleting a flavor using the dashboard

Another way to delete predefined flavors is to use the OpenStack dashboard.

Commissioning Open MSS Cloud on OpenStack Application content provisioning

Procedure

1 Navigate to the Flavors page under the Admin section. Search for the flavor to delete,
and under Actions, choose Delete Flavor.

Step example

Figure 31 Choosing the Delete Flavor option

2 In the pop-up window click on the Delete Flavor button.

Step example

Figure 32 Confirming the flavor deletion

Result
The flavor is successfully deleted.

Application content provisioning Commissioning Open MSS Cloud on OpenStack

Figure 33 The flavor is deleted

6.7 Using root volumes

To avoid root disk usage, the Open MSS Cloud can be deployed using Cinder volumes
for all storage purposes.

In OpenStack, virtual machine disks can be defined in several ways. Open MSS Cloud
virtual machines use a configuration by default where the boot images are served by
Nova root disk, and OMU and CHU disks are served by Cinder volumes.
The backend solution for the Nova root disk may be different and less flexible, for
example it may be served by a local disk instead of a shared storage. However, it is
possible to deploy the Open MSS Cloud using Cinder volumes for all disk purposes. By
using a suitable template, the boot image contents will be transferred to one Cinder
volume for each virtual machine during deployment. Additionally, the root disk usage will
be eliminated. These root volumes are created using the template and are deleted upon
undeployment. No user action is needed regarding these volumes. Uploading iPXE and
VSA images is still needed as those are used for volume source.
Using root volumes brings no changes to the handling of OMU and CHU volumes, those
must still be created in advance and are not automatically deleted during undeployment.
Using root volumes increases the deployment, undeployment and scaling time due to the
times needed to create the volumes, but has no effect on the traffic handling capability of
the network element.

Commissioning Open MSS Cloud on OpenStack Application deployment with Heat

7 Application deployment with Heat

The deployment process includes the creation and deployment procedures of the VNF
from a template.

There are deployment options of Open MSS Cloud which are compiled into the template.
Make sure to select the appropriate template variant. There are variants for:
• different maximum traffic capacity
• predefined flavor usage

7.1 Uploading the VNF template to the controller node

Before starting the application deployment, you must upload the VNF template to the
controller node.

Before you start

You must create the tenant user.

Required preconditions links

Creating the tenant user on page 37

Procedure

1 Create a folder in the home directory on the controller node for the template files.

Step example
mkdir mss8_template

2 Upload the VNF template to the controller node, to the folder created in the previous
step.

3 Unzip the template files to the folder created in Step 1.

Step example
[cbis-admin@overcloud-controller-0 mss8_template]$ unzip
NOKIA_MSS_CLOUD_OPENSTACK_HEAT_10M_CFP5_X.X-X.ZIP
XXX is the version of the template.

Application deployment with Heat Commissioning Open MSS Cloud on OpenStack

Step result

Archive: NOKIA_MSS_CLOUD_OPENSTACK_HEAT_10M_CFP5_X.X-X.ZIP
inflating: environment.yaml
inflating: Open_MSS_Cloud_HEAT_10M.yaml
inflating: vsa_wrapper.yaml
inflating: definitions/chu.yaml
inflating: definitions/cmm.yaml
inflating: definitions/cmu.yaml
inflating: definitions/gisu.yaml
inflating: definitions/ipdu_cp.yaml
inflating: definitions/ipdu_om.yaml
inflating: definitions/omu.yaml
inflating: definitions/stu.yaml
inflating: definitions/vlru.yaml
inflating: definitions/vsa.yaml
extracting: _version_
The template folder contains an environment configuration yaml file, Heat template
files, and a definitions directory with several files.

4 Modify the environment the variables in the environment.yaml file. You can find the
environment variable descriptions in section Application variables.

Step example
vi environment.yaml

# All site specific configuration items for Heat base increment

template.
# Open MSS Cloud environment file for heat deployment.
# Site specific configuration items for the deployment should be set
here.
# For explanation of individual parameters, see the parameters
section of the template.
#
# Deployment with openstack stack create command, e.g.:
# openstack stack create MSS01 -e Open_MSS_Cloud_environment.yaml -t
Open_MSS_Cloud_template.yaml --wait

parameter_defaults:

prefix: MSS8
vsa_key_name: vsa_key
vsa_image_name: VSA_3_7_0
vsa_security_group: MSS8_SG
ipxe_image_name: CR3IPXTX_VMDK_2_4_0
availability_zone: zone1

vsa1_om_ip: 192.0.2.66
vsa2_om_ip: 192.0.2.67
vsa1_om_netmask: 255.255.255.240

Commissioning Open MSS Cloud on OpenStack Application deployment with Heat

vsa2_om_netmask: 255.255.255.240
vsa1_om_gateway: 192.0.2.65
vsa2_om_gateway: 192.0.2.65

vsa1_omu_vol_id: 733012f6-4e2b-469b-831a-946be6f527fb
vsa1_chu0_vol_id: d8cd4b55-50e5-4566-a51a-36dbf4085174
vsa1_chu1_vol_id: 4d2664ec-5e4b-437c-9264-9b8a7095dcad
vsa2_omu_vol_id: a0331c43-bb86-4632-840d-f7d4330fb11c
vsa2_chu0_vol_id: 6e4a66fa-b371-42b0-acb2-3bd146c1bae0
vsa2_chu1_vol_id: 2b244847-14cd-4d66-a84a-958a5f18bef6

OMU-0_ip: 192.0.2.68
OMU-1_ip: 192.0.2.69
OMU_logical_ip: 192.0.2.70

net_oam: MSS_OaM
net_cp_mh_pri: MSS_CP_MH_Pri
net_cp_mh_sec: MSS_CP_MH_Sec
net_cp_sh: MSS_CP_SH
net_oam_mh_pri: MSS_OaM_MH_Pri
net_oam_mh_sec: MSS_OaM_MH_Sec
net_oam_sh: MSS_OaM_SH
net_cha: MSS_CHA
net_olcm: MSS_LI

num_gisu: 6
gisu_group_by: 4
cp_ipdu_group_by: 4
You can collect the necessary information from the inputs previously provided and
the commands or dashboard screens listed in the previous sections.

g Note: The prefix has to be unique within one cloud environment.

5 Validate the template using the openstack orchestration template

validate command.

Step example
openstack orchestration template validate -e environment.yaml -t
Open_MSS_Cloud_HEAT_3M.yaml

Step result
If the stack validation command displays a list of stack parameters, it means that
there is not any error and you can proceed with the next procedure.

Related procedures
Creating the tenant user on page 37

Application deployment with Heat Commissioning Open MSS Cloud on OpenStack

7.2 Using the predefined flavor in case of Heat based

deployment
Carry out these steps only if you use predefined flavor capable template.

Procedure

1 Open the environment.yaml file and modify the following lines to alter the flavors.

Step example
flavor_vsa: MSS_VSA
flavor_2_2: MSS_2_2
flavor_2_3: MSS_2_3
flavor_3_2: MSS_3_2
flavor_3_3: MSS_3_3
flavor_4_1: MSS_4_1
flavor_6_2: MSS_6_2

For the recommended naming convention and the recommended predefined flavors,
see section Creating predefined flavors.

2 After creating the required flavors, commission or redeploy the Cloud MSS.

g Note: In case of Open TRS Cloud deployment, use the flavor_1_1 parameter
instead of the flavor_4_1 parameter.

7.3 Application variables

When creating the application, you must set the application variables based on the
previously configured provider networks. You can specify application variables in the
environment.yaml file of the template.

Table 9 Application variables
Variable name Description Example value
prefix prefix for the names of the MSS8
virtual machines of the MSS
application

g Note: It has to be
unique within a cloud
environment.

vsa_key_name name of the VSA SSH keypair vsa_key

Commissioning Open MSS Cloud on OpenStack Application deployment with Heat

Table 9 Application variables (Cont.)
Variable name Description Example value
vsa_image_name name of the VSA image (root VSA_3_7_0
disk)
ipxe_image_name name of the iPXE boot image CR3IPXTX_VMDK_2_4_0
availability_zone availability zone for the zone1
application. You can
interrogate existing availability
zones with the openstack
availability zone list
command. If left empty, virtual
machines are allowed to use
all hosts regardless of
availability zones.
vsa1_om_ip OaM address for VSA-1 192.0.2.194
vsa2_om_ip OaM address for VSA-2 192.0.2.195
vsa1_om_netmask netmask for OaM network of 255.255.255.240
VSA-1
vsa2_om_netmask netmask for OaM network of 255.255.255.240
VSA-2
vsa1_om_gateway gateway for OaM network of 192.0.2.193
VSA-1
vsa2_om_gateway gateway for OaM network of 192.0.2.193
VSA-2
vsa1_volume_id_omu Cinder volume ID of OMU disk c19285fd-a8b4-4e74-8c5d-
0 c0a6532669d0
vsa1_volume_id_chu0 Cinder volume ID of CHU disk 2c873806-6214-4ff1-850a-
0 ac4bbbffa01d
vsa1_volume_id_chu1 Cinder volume ID of CHU disk 14c23bfd-dbd2-4a61-9159-
1 c2246dbdccad
vsa1_volume_id_chu2 Cinder volume ID of CHU disk b92e593c-54f5-4519-887f-
2 6f79422a539a
vsa1_volume_id_chu3 Cinder volume ID of CHU disk 314f5fe5-489e-49ff-92c7-
3 1a314d926394
vsa2_volume_id_omu Cinder volume ID of OMU disk d5fdf574-ca8c-47cf-863c-
1 ba80a1e1637e
vsa2_volume_id_chu0 Cinder volume ID of CHU disk b5103134-7017-4ef9-a2a6-
0 05ea1dab9197
vsa2_volume_id_chu1 Cinder volume ID of CHU disk 4152c6b6-7691-486f-a982-
1 4cb679b5413c
vsa2_volume_id_chu2 Cinder volume ID of CHU disk d6fb0faf-c98b-4234-9545-
2 ef1843274a66
vsa2_volume_id_chu3 Cinder volume ID of CHU disk faf2fe55-1dc7-4605-8a04-
3 8ce82e93af80
OMU-0_ip physical IP address of OMU-0 192.0.2.68
EL4
OMU-1_ip physical IP address of OMU-1 192.0.2.69
EL4

Application deployment with Heat Commissioning Open MSS Cloud on OpenStack

Table 9 Application variables (Cont.)
Variable name Description Example value
OMU_logical_ip logical IP address of the OMUs 192.0.2.70
net_oam name of the external Operation MSS8_OaM
and Maintenance network
net_cp_mh_pri name of the external (media) MSS8_CP-SCTP-Mh-Pri
control LAN (SCTP primary) of
Control Plane traffic network
net_cp_mh_sec name of the external (media) MSS8_CP-SCTP-Mh-Sec
control LAN (SCTP secondary)
of Control Plane traffic network
net_cp_sh name of the external (media) MSS8_CP-SCTP-Sh-TCP-
control LAN (TCPUDP) SIP, UDP
Dia, H.248, M3UA of Control
Plane traffic network
net_oam_mh_pri name of the external MSS8_OaM-SCTP-Mh-Pri
Operational and Maintenance
LAN (SCTP Primary)
net_oam_mh_sec name of the external MSS8_OaM-SCTP-Mh-Sec
Operational and Maintenance
LAN (SCTP Secondary)
net_oam_sh name of the external Operation MSS8_OaM-SCTP-Sh-TCP-
and Maintenance Traffica UDP
network (TCPUDP)
net_cha name of the external Billing MSS8_CHA
network
net_olcm name of the external Lawful MSS8_LI
Interception network
num_gisu number of GISU units 6

gisu_group_by anti-affinity group size of GISU 4
VMs. Should be the same as
CP IPDU count.
cp_ipdu_group_by anti-affinity group size of CP 4
IPDU VMs. Should be the
same as CP IPDU count.
MSS_x_y name of the predefined MSS MSS_2_2
flavor that is already created in
OpenStack. The x stands for
the number of virtual CPUs,
the y for the RAM size in
gigabytes. Only in case of
predefined flavor capable
template.
MSS_VSA name of the predefined VSA MSS_VSA
flavor already created in
OpenStack. Only in case of
predefined flavor capable
template.

Commissioning Open MSS Cloud on OpenStack Application deployment with Heat

Related procedures
Creating the Heat stack and Open MSS application on page 81

7.4 Creating the Heat stack and Open MSS application

You must create the Open MSS application before the deployment procedure can begin.

Procedure

1 Take the keystone credential file into use with the command source
keystonerc_mss.

Step example
[cbis-admin@overcloud-controller-2 ~]$ source keystonerc_mss
[cbis-admin@overcloud-controller-2 ~(openstack_mss)]$

2 Verify that there is not any previous Heat stack with the openstack stack list

command.

Step example
[cbis-admin@overcloud-controller-2 ~(openstack_mss8)]$ openstack
stack list

Step result

+--------------------------------------+------------+-----------------+---------------------+--------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+-----------------+---------------------+--------------+
+--------------------------------------+------------+-----------------+---------------------+--------------+

The stack list is empty.

g Note: Depending on the OpenStack release, the stack list may contain stacks of
other users.

3 Create the MSS stack using the openstack stack create command.

openstack stack create -e environment.yaml [--parameter

num_gisu=<Number of GISU's> --wait] -t Open_MSS_Cloud_HEAT_3M.yaml
<name of the stack>

Select from the available options

Application deployment with Heat Commissioning Open MSS Cloud on OpenStack

• Creating the Heat stack with the same amount of GISUs as denoted in the
environment configuration file:
openstack stack create -e environment.yaml --wait -t
Open_MSS_Cloud_HEAT_3M.yaml MSS8
• Creating the Heat stack with a different number of GISUs than specified in the
environment configuration file:
openstack stack create -e environment.yaml --parameter num_gisu=27
--wait -t Open_MSS_Cloud_HEAT_3M.yaml MSS8

The deployment lasts approximately 30 minutes. This may increase depending on
the infrastructure and the usage of the root volume feature. You can check the status
of the deployment using the openstack stack list command. When the
deployment is complete, it will have the status CREATE_COMPLETE, or you can
follow the stack creation automatically on screen if you used the -wait parameter.

4 Verify that the stack is created using the openstack stack list command.

Step example
[cbis-admin@overcloud-controller-2 ~(openstack_mss8)]$ openstack
stack list

Step result

+--------------------------------------+------------+-----------------+---------------------+--------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+-----------------+---------------------+--------------+
| 85fde07d-24e6-46ad-9704-214feaaaa095 | MSS8 | CREATE_COMPLETE | 2017-03-23T10:09:38 | None |
+--------------------------------------+------------+-----------------+---------------------+--------------+

The CREATE_COMPLETE status indicates that the deployment is complete.

g Note: If the MSS stack creation fails with CREATE_FAILED stack status, you
can continue with checking the stack event list for investigating the root cause.
You can check the heat event list using the
openstack stack event list --nested 10 <stackname>
command.
To re-create the failed task, delete the failed deployment first using the
openstack stack delete <stackname> command.

Related references
Application variables on page 78

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

8 Application deployment with CloudBand

Application Manager (CBAM)
The deployment process includes the creation and deployment procedures of the VNF
from a CBAM template.

w NOTICE: The CBAM related procedures and screenshots in this document were
created using CBAM19. If you use another version, like CBAM18.5, see the same titled
document in release Open MSS Cloud CM CFP3.

g Note: Before deploying with CBAM, make sure the SSH connection between the
CBAM and the OaM network is working properly.

8.1 Uploading the VNFD package to CBAM Catalog

Before creating the MSS VNF, you must upload the VNFD package to CBAM.

Procedure

1 Open the CloudBand Application Manager (CBAM).

2 Click the menu icon, then select the Catalog menu item on the menu bar.

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

3 In the Catalog pane, click the plus icon to upload the new VNFD package.

Step example

Figure 34 Adding the VNFD package

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

4 Select the Virtualized Network Function Descriptor (VNFD) package ZIP file and click on
the Upload button.

Step example

Figure 35 Uploading the VNFD package

Result

The VNFD package appears in the Catalog.

Figure 36 Finishing the VNFD package upload

Now you can start creating the Virtual Network Function (VNF) in CBAM.

8.2 Creating the MSS VNF in CBAM

You must set the service provider and the VNFD version to create the VNF in CBAM.

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

Procedure

1 Open the CloudBand Application Manager (CBAM).

2 Click the menu icon, then select the Catalog menu item on the menu bar.

3 In the Catalog pane, in the line of the uploaded template, click the icon of the Create
VNF from Package function.

Step example

Figure 37 Accessing the Create New VNF function

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

4 Type the VNF name in the Name field, then click the Create button.

Step example

Figure 38 Adding the VNF name

Result

The created VNF is visible in the list of VNFs.

Figure 39 List of VNFs in CBAM

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

8.3 Using the predefined flavor in case of CBAM based

deployment

• For deploying in CBAM with predefined flavors, change the flavor name parameters in
VNF extensions.

See section Modifying the VNF attribute parameter values in CBAM. For the
parameter names, see section Creating predefined flavors.

8.4 Modifying the VNF attribute parameter values in

CBAM
You must set the parameter values according to the VNF needs.

Before you start

Perform the steps in section Application deployment requirements for OpenStack.

Required preconditions links

Application deployment requirements for OpenStack on page 31

Procedure

1 Open the CloudBand Application Manager (CBAM).

2 Click the menu icon, then select the Virtualized Network Functions menu item on the

menu bar.

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

3 In the Virtualized Network Functions pane, in the line of the created VNF, click the

three dot button and select the Modify menu item.

Step example

Figure 40 Accessing the Modify VNF function

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

4 In the Modify pane, click Continue twice (the first click brings you to the Metadata
section) to reach the Extensions section.

Step example

Figure 41 Accessing the Extensions section

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

5 Change the parameter values according to your VNF needs. Click Continue once all the
parameter values are set.

Step example

Figure 42 Changing the parameter values

You can collect the necessary information from the inputs provided and the
commands or dashboard screens listed in other sections of the document. For more
information, see the related links at the end of the procedure. In table Parameter
descriptions, you can find a short explanation of the parameter fields and example
values for them.

g Note: You can find the parameters that are not described below in section
NetAct registration of deployed MSS.

Table 10 Parameter descriptions
Extension parameter name Description Example
OMU_0_ip Physical IP adress of OMU-0 192.0.2.68

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

Table 10 Parameter descriptions (Cont.)
Extension parameter name Description Example
OMU_1_ip Physical IP adress of OMU-1 192.0.2.69
OMU_logical_ip Logical IP address of the 192.0.2.70
OMU
OMU_netmask_length Netmask length defined for 28
OMU logical IP address.
Used only if the OMU's
DHCP client is used.
availability_zone Availability zone for this MSS_AZ
application
ipxe_image_name Name of iPXE image to use CR3IPXTX_VMDK_2_4_0
for MSS
mss_c_number C number identifier of the 101978
MSS to be instantiated
mss_ssh_user Login username for MSS SYSTEM
(SSH)
mss_ssh_password Login password for MSS SYSTEM
(SSH)
net_oam Name of the External OaM MSS21_OAM
network
net_cp_mh_pri Name of the External (Media) MSS21_CP-SCTP-Mh-Pri
Control LAN (SCTP primary)
of Control Plane traffic
network
net_cp_mh_sec Name of the External (Media) MSS21_CP-SCTP-Mh-Sec
Control LAN (SCTP
secondary) of Control Plane
traffic network
net_cp_sh Name of the External (Media) MSS21_CP-SCTP-Sh-
Control LAN (TCPUDP) SIP, TCPUDP
Dia, H.248, M3UA of Control
Plane traffic network
net_oam_mh_pri Name of the External Multi- MSS21_OaM-SCTP-Mh-Pri
homed Primary OaM network
net_oam_mh_sec Name of the External Multi- MSS21_OaM-SCTP-Mh-Sec
homed Secondary OaM
network
net_oam_sh Name of the External Single- MSS21_OaM-SCTP-Sh-
homed OaM network TCPUDP
net_cha Name of the Charging MSS21_CHA
network
net_olcm Name of the External Legal MSS21_LI
Interception network
pre_scaling_gisu_count CBAM uses this parameter 0
internally.

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

Table 10 Parameter descriptions (Cont.)
Extension parameter name Description Example

g Note: Do not change
it!

prefix Prefix to be applied to all MSS21

resources
vsa_key_name Name of the VSA SSH key vsa_key
vsa_image_name Name of the VSA image VSA_3_7_0
vsa_keyboard Keyboard layout for VSA en
vsa_timezone Time zone for VSA UTC
vsa1_om_ip IP address of VSA1 192.0.2.165
vsa2_om_ip IP address of VSA2 192.0.2.166
vsa1_om_netmask IP netmask for VSA1 255.255.255.240
vsa2_om_netmask IP netmask for VSA2 255.255.255.240
vsa1_om_gateway IP gateway for VSA1 192.0.2.161
vsa2_om_gateway IP gateway for VSA2 192.0.2.161
vsa1_volume_id_omu Cinder volume ID for OMU d5ef955c-2210-47f4-b658-
disk 0 bb32ceb9366b
vsa1_volume_id_chu0 Cinder volume ID for CHU-0 ca52c60c-6efb-486e-abfd-
disk 0 43aeae4a4439
vsa1_volume_id_chu1 Cinder volume ID for CHU-1 5ee749d6-fd0d-4104-abf3-
disk 0 dadcfd4e47ce
vsa1_volume_id_chu2 Cinder volume ID for CHU-2 b92e593c-54f5-4519-887f-
disk 0 6f79422a539a
vsa1_volume_id_chu3 Cinder volume ID for CHU-3 314f5fe5-489e-49ff-92c7-
disk 0 1a314d926394
vsa2_volume_id_omu Cinder volume ID for OMU e8a132f3-b3aa-42ec-a1d6-
disk 1 428384df5df8
vsa2_volume_id_chu0 Cinder volume ID for CHU-0 0dc34e6a-f881-4c1a-be4b-
disk 1 d0343e3f3459
vsa2_volume_id_chu1 Cinder volume ID for CHU-1 b078d434-5e93-4326-a9a7-
disk 1 d45da0182b4f
vsa2_volume_id_chu2 Cinder volume ID for CHU-2 d6fb0faf-c98b-4234-9545-
disk 1 ef1843274a66
vsa2_volume_id_chu3 Cinder volume ID for CHU-3 faf2fe55-1dc7-4605-8a04-
disk 1 8ce82e93af80
MSS_x_y Name of the predefined MSS MSS_2_2
flavor that is already created
in OpenStack. The x stands
for the number of virtual
CPUs, the y for the RAM size

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

Table 10 Parameter descriptions (Cont.)
Extension parameter name Description Example
in gigabytes. Only in case of
predefined flavor capable
template
MSS_VSA Name of the predefined VSA MSS_VSA
flavor already created in
OpenStack. Only in case of
predefined flavor capable
template.

vsa_username1 Username for VSA vsa

vsa_privatekey 1 Private key for VSA VM of the MIIEoQIBA(….)PvkMrw==

vsa_user in PEM format.

g Note: Write in one line
without header or
footer.

vsa_image_server_username Username in case of admin

1 authenticated file access.

vsa_image_server_password Password in case of password

1 authenticated file access

g Note: 1 - These parameters are used only if the automatic VSA upgrade
procedure is used. For further information, see VSA Upgrade Guide.

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

6 Click Finish.

Step example

Figure 43 Completing the parameter value modification

Result

You are redirected to the Virtualized Network Functions pane. You receive a

notification about the successful start of the VNF modification at the bottom of the pane.
The Last Operation Status field of the VNF also reflects the state of the process.

Figure 44 Successful start of the VNF modification

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

Related descriptions
Application deployment requirements for OpenStack on page 31

Related procedures
Creating provider networks on page 44
Uploading the iPXE image on page 48
Uploading the VSA image on page 51
Creating VSA key pairs on page 53
Creating the OMU volumes on page 61
Creating CHU volumes in Cinder on page 64
NetAct registration of deployed MSS on page 134

8.5 Instantiating the MSS VNF in CBAM

You must set the VIM authentication parameters and add the instantiation settings to
instantiate the VNF and complete the deployment in CBAM.

Procedure

1 Set the Virtual Infrastructure Manager (VIM) authentication parameters in the CBAM
parameter file.

Edit the vimConnectionInfo section in the
mss.tosca_OpenStack_CBAM_API_4_0.json file. You can find this file in the
json directory, in the template.zip file.

Step example

Table 11 Structure of the vimConnectionInfo section
Field name Description
vimConnectionInfo / accessInfo / region OpenStack region

g Note: You can check it from the controller:
openstack endpoint list

vimConnectionInfo / interfaceInfo / Public OpenStack Authentication URL
endpoint

g Note: You can check it from the controller:
openstack endpoint list

vimConnectionInfo / accessInfo / project OpenStack tenant for the Virtualized Network
Function (VNF)
vimConnectionInfo / accessInfo / OpenStack user for the VNF
username

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

2 Open the CBAM.

3 Click the menu icon, then select the Virtualized Network Functions menu item on the

menu bar.

4 In the Virtual Network Functions pane, in the line of the proper Virtualized Network

Function (VNF), click the icon of the Instantiate function (play icon).

Step example

Figure 45 Initiating instantiation

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

5 In the General Data section of the Instantiate pane, select the applicable instantiation
level of the VNF from the drop-down list of the Instantiation level Id field.

Step example

Figure 46 Selecting the wanted instantiation level for the VNF

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

6 In the General Data section of the Instantiate pane, in the VIM password field, type the

VIM password of the cloud user defined in the json parameter file, then click Continue.

Step example

Figure 47 Adding the VIM password

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

7 In the Parameters section of the Instantiate pane, in the Parameters area, select in the
CBAM json parameter (mss.tosca_OpenStack_CBAM_API_4_0.json) file by
using the drag and drop function, or clicking the browse button. Then click Finish.

Step example

Figure 48 Browsing for the parameter file and launching the instantiation

Step result

You are redirected to the Virtualized Network Functions pane. You receive a

notification about the successful start of the instantiation at the bottom of the pane.
The Last Operation Status field of the VNF also reflects the state of the process.
Wait while it finishes.

g Note: Instantiating the Cloud MSS is expected to complete in approximately 30
minutes. This time frame may increase depending on the infrastructure and the
usage of the root volume feature. CBAM creates a stack for the VNF via Heat.

Figure 49 Successful start of the VNF instantiation

100 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

Result

The Last Operation Status of the VNF changes to Completed - Instantiate when the

operation ends.
The VNF is up and running.

Figure 50 Instantiation is completed

8.6 Initializing the MSS VNF in CBAM

You must initialize the VNF before actual use. Initialization of the VNF (including C-
number setting, system encryption keys configuration, and OMU IP address setting for
EL4 interface) is separated from instantiation.

Before you start

Make sure the VNF is instantiated successfully.

Required preconditions links

Instantiating the MSS VNF in CBAM on page 96

Procedure

1 Open the CloudBand Application Manager (CBAM).

2 Click the menu icon, then on the menu bar, select the Virtualized Network Functions

menu item.

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 101

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

3 In the Virtualized Network Functions pane, in the line of the created VNF, click the

three dot button, then select the Initialize menu item.

Step example

Figure 51 Accessing the Initialize function

4 You are asked to verify the initialization. Click OK.

Step example

Figure 52 Verifying the initialization

Result

You are redirected to the Virtualized Network Functions pane. If no error occurs, you

receive a notification about the successful initialization of the VNF at the bottom of the
pane. The Last Operation Status field of the VNF shows Completed - Initialize state.

102 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

Figure 53 Initialization is completed

Related procedures
Instantiating the MSS VNF in CBAM on page 96

8.7 Automatic MSS unit bringup in CBAM

The MSS unit bringup procedure creates a given number of MSS units, changes their
state and assigns internal IP addresses to all computer unit EL0 and EL1 interfaces, as
per recommendations in the Site Connectivity Configuration for Open MSS Cloud on
OpenStack document.

Before you start

Make sure the VNF is instantiated and initialized successfully.

Required preconditions links

Instantiating the MSS VNF in CBAM on page 96
Initializing the MSS VNF in CBAM on page 101

Procedure

1 Open the CloudBand Application Manager (CBAM).

2 Click the menu icon, then select the Virtualized Network Functions menu item on the

menu bar.

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 103

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

3 In the Virtualized Network Functions pane, in the line of the created VNF, click the

three-dot button and select the bringup menu item.

Step example

Figure 54 Accessing the bringup menu item

4 In the Custom operation bringup screen, set the bringup operation parameters and

click Finish to start the bringup.

Step example
See the description of the fields and example values in the following table:
Table 12 MSS unit bringup parameters and examples
Parameter Description Example
in a
medium
sized
MSS
internal_ipv6_configuration The script sets up the internal IPv6 configurations true
per examples in the Site Connectivity
Configuration for Open MSS Cloud on OpenStack
document. The possible values are true or false.
The parameter is valid only if the
internal_ip_configuration parameter is
set to true. IPv6 addresses are not configured if
either the internal_ipv6_configuration
or the internal_ip_configuration
parameter is set to false.

internal_ip_configuration The script sets up the internal IPv4 configuration true

per examples in the Site Connectivity

104 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

Table 12 MSS unit bringup parameters and examples (Cont.)
Parameter Description Example
in a
medium
sized
MSS
Configuration for Open MSS Cloud on OpenStack
document. The possible values are true or false.
num_gisu Number of GISUs to bringup.1 50

1 The amount of GISUs given cannot be greater than the number of the possible

GISUs.
All unit indices starts from zero.

g Note: The bringup operation sets the IP addresses based on the
Site Connectivity Configuration for Open MSS Cloud on OpenStack document. If
the MSS is already configured and the IP addresses on the units differ from the
ones specified in the documentation, the addresses which are already reserved
may not be added to the affected bringup units. Nokia suggests to check if the IP
addresses on the units are set according to the
Site Connectivity Configuration for Open MSS Cloud on OpenStack document.

Figure 55 Setting bringup parameters and starting the bringup

Result

If no error occurs, you receive a notification about the successful bringup of the VNF at
the bottom of the pane. The Last Operation Status field of the VNF shows Completed -
bringup state. All the units are brought up according to the VNF capacity and the
num_gisu parameter. The brought up units are in working or spare states.
• If internal_ip_configuration parameter is set to true:

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 105

Application deployment with CloudBand Application Commissioning Open MSS Cloud on OpenStack
Manager (CBAM)

EL0 and EL1 interfaces are created for all the units. IPv4 addresses on the EL0
interface are set, Internal Network Time Protocol Configuration (excluding external
primary, secondary, and tertiary NTP server configuration and local communication
address assignment, steps 4 and 5 in section Configuring IP routing support for
internal Network Time Protocol of the Site Connectivity Configuration for Open MSS
Cloud on OpenStack document) and Internal Lan Link Supervision configurations are
made, based on the Site Connectivity Configuration for Open MSS Cloud on
OpenStack document for all the units.
• If internal_ipv6_configuration parameter is set the true:
IPv6 addresses on the EL0 interfaces of GISUs and IPDUs are set based on the Site
Connectivity Configuration for Open MSS Cloud on OpenStack document.

Related procedures
Instantiating the MSS VNF in CBAM on page 96
Initializing the MSS VNF in CBAM on page 101

8.8 Setting IPv6 addresses on OaM network

Before starting the configuration, plan the IPv6 range for the O&M, and set up your cloud
networking part accordingly. This procedure is optional.

Procedure

1 Log in to VSA-1 via SSH connection, using username vsa an the keypair supplied during
deployment.

2 Edit the interface configuration with the following command.

Step example
sudo nano /etc/sysconfig/network-scripts/ifcfg-eth0

3 Add the following lines to the file, then save it.

IPV6INIT=yes
IPV6ADDR=<IPv6 address of VSA-1>/<netmask length>
IPV6_DEFAULTGW=<IPv6 address of gateway>

4 Repeat these steps in VSA-2.

f The next step causes temporary outage in the iSCI network. Carry out the restart
during a maintenance window.

106 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Application deployment with CloudBand Application
Manager (CBAM)

5 Restart each VSA network one by one, and wait until the network connection is restored
and the related alarms are cancelled in the MSS.

Step example
sudo systemctl restart network

6 Configure the logical IPv6 address for OMU.

Step example
ZQRN:OMU,0::EL4:"2001:DB8:6000:1000::2",64,L;

7 Configure the physical IPv6 address for OMU-0 and OMU-1.

Step example
ZQRN:OMU,0::EL4:"2001:DB8:6000:1000::3",64,L;
ZQRN:OMU,1::EL4:"2001:DB8:6000:1000::4",64,L;

8 Configure the gateway for the added IPv6 addresses.

Select from the available options

• In case of static route:
ZQKC:OMU,0:::"2001:DB8:6000:1000::1":LOG;
• In case of logical IP based route:
ZQKM:OMU,0::"2001:DB8:6000:1000::2":"2001:DB8:6000:1000::1":LOG;

9 Check that VSA-1 and VSA-2 can communicate via IPv6 using a ping6 command on
VSA-1.

Step example
ping6 <IPv6 address of VSA-2>

10 Check that OMU can communicate via IPv6 using the ZQRX command towards VSA-2.

Step example
ZQRX:OMU,0::PING6:IP="<IPv6 address of VSA-2>";

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 107

Completion of deployment Commissioning Open MSS Cloud on OpenStack

9 Completion of deployment
Perform several checks and configurations to ensure that the VNF is ready to use.

Check the following areas:

• Console access
• C-number setting
• Disk connections
• System encryption key configuration
• Adding the spare OMU unit
• IP address configuration for OMU
• Unit bringup
• DHCP service
• Failed unit bringup
• GRO setting on VXLAN interfaces
• Predefined flavor usage
• NetAct registration
• Operational status

9.1 Accessing the OMU console

You should only access the OMU console for troubleshooting. If the remote connection
to the working OMU is not working, follow this procedure.

Before you start

g Note: The console has an irregular keyboard layout. Make sure the keyboard layout of
the computer is set to EN-US. In this configuration, special characters are set according
to the Finnish keyboard layout.
Figure 56 Finnish keyboard layout

108 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Procedure

1 Log in to the OpenStack dashboard (Horizon).

2 Select the Admin menu, then select the Compute menu item.

3 In the Compute menu, select the Instances menu item.

4 In the Instances pane, search for OMU-0.

5 To display the console, click the name of the instance, then select the Console tab.

Step example

Figure 57 Displaying the console

6 Click the console header first, then click the console to access the content.

g Note: The terminal prints uppercase characters, even if you type lowercase
characters, but it is case sensitive. Make sure to enter the user name and
password using the correct case. To achieve uppercase characters, hold down
the Shift key. Caps Lock is not operational in the console.
a) To access the service terminal, login with the user name and password.
b) Access the MML terminal using the following command.
ZLE:1,VIMMLAGX
Z1C:

After these steps, another login is needed with the user name and password.

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 109

Completion of deployment Commissioning Open MSS Cloud on OpenStack

Step example

Figure 58 Accessing the console

Result

The OMU console can be accessed.

Figure 59 Console is accessed

9.2 Setting the C-number

The C-number identifies the NE and indicates that it belongs to the operator. The C-
number is also used for licensing. You must set the C-number for the Open MSS Cloud
so that all applicable licenses are available. This procedure is optional if you use the
Initialize button.

110 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Purpose

w Setting the C-number is only needed when you deploy the MSS using Heat templates.
If you are deploying the MSS with CloudBand Application manager (CBAM), the CBAM
sets the C-number from the mss_c_number CBAM parameter, therefore, you do not
need to complete this procedure.

Procedure

1 Log into the Open MSS Cloud using ssh.

2 Set the C-number using the DCN command.

Step example
ZDCN:C=<C-number>;

9.3 Checking the disk connections

Check the disk connections of the instances to ensure the commissioning procedure
was successful.

Procedure

1 List the Winchester Drive Unit (WDU) states, and execute a basic device listing in the
Service Terminals.

Step example
ZISI::WDU,:;

2 Check the availability of the WDUs for the Operation and Maintenance Unit (OMU).

All devices must be in WO-BU state.
MAIN LEVEL COMMAND <___>
< ZISI:,OMU:WDU;

I/O DEVICE WORKING STATE AND SPARE DEVICE

SYSTEM = FTvMSS03 UNIT = OMU
DEVICE STATE SPARE DEVICE DEVICE STATE INFO TAPE STATE TAPE TYPE

WDU-00 WO-BU - - -

DN09241459 Issue: 6-0-0 © 2019 Nokia. Nokia confidential. 111

Completion of deployment Commissioning Open MSS Cloud on OpenStack

WDU-01 WO-BU - - -

COMMAND EXECUTED

Postrequisites
You must format the CHU disks before they can be listed and before you can set them to
the proper (WO-BU) state. The initiation of the CHU disks does not take place
automatically. You must start them manually with MML commands. Disk formatting is not
possible while the disk is in the WO-BU state. You must first put the disk in the WO-ID
state.
ZISC:,CHU,0:WDU,1:WO-ID;
ZIWK:,CHU,0:WB,,CHU0_W1,FFF0,,XX;
ZISC:,CHU,0:WDU,1:WO-BU;

ZISC:,CHU,0:WDU,0:WO-ID;
ZIWK:,CHU,0:WB,,CHU0_W0,FFF0,,XX;
ZISC:,CHU,0:WDU,0:WO-BU;

ZISC:,CHU,1:WDU,1:WO-ID;
ZIWK:,CHU,1:WB,,CHU1_W1,FFF0,,XX;
ZISC:,CHU,1:WDU,1:WO-BU;

ZISC:,CHU,1:WDU,0:WO-ID;
ZIWK:,CHU,1:WB,,CHU1_W0,FFF0,,XX;
ZISC:,CHU,1:WDU,0:WO-BU;

g Note: Before formatting the CHU disks, you must create the CHUs. For more
information, see section Adding the CHU units.

9.4 Configuring system encryption keys

After installing a new package, you must create five system encryption keys. This
procedure is optional if you use the Initialize button.

Purpose

w The system encryption key configuration is only valid for Heat-based deployment. If you
are deploying the MSS with CloudBand Application Manager (CBAM), the encryption
keys are generated automatically during the Cloud MSS instantiation.

w Until you configure the system encryption keys, only a limited number of commands are
allowed to be executed (for example, AHO, WQO, or USI). Please note that after you
complete this task, you will no longer be able to modify the C-number.

Before you start

Required preconditions links

Setting the C-number on page 110

112 © 2019 Nokia. Nokia confidential. DN09241459 Issue: 6-0-0

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Procedure

1 Check the status of the OMU disks using the ISI command.

Step example
ZISI:,OMU:WDU;

Step result
LOADING PROGRAM VERSION 1.3-0

I/O DEVICE WORKING STATE AND SPARE DEVICE

SYSTEM = VSP - LAB UNIT = OMU
DEVICE STATE SPARE DEVICE INFO

WDU-00 WO-BU - -
WDU-01 WO-BU - -

COMMAND EXECUTED

Both disks should be in the WO-BU state before you proceed to the next step. If they
are not in the WO-BU state, you can use the ISC command to change their state.

2 Configure the system encryption keys using the I4C command.

g Note: When you execute the I4C command in the network element for the first
time, it creates the encryption keys. Any subsequent use of this command
renews the encryption keys. All the old encrypted data, for example, network
security keys are re-encrypted with the new encryption keys. But the Operability
Administration and Maintenance (OAM) password fingerprints are only renewed
on the corresponding subsequent user login.

Step example
ZI4C;

Step result
LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

WARNING: C NUMBER CANNOT BE CHANGED ANYMORE AFTER EXECUTING I4C

COMMAND

/* EXECUTION OF THIS MML COMMAND MAY RESULT IN HIGH CPU LOAD IN

COMPUTER UNITS.
ONLY EXECUTE THIS MML COMMAND DURING LOW TRAFFIC PERIODS OR IN
MAINTENANCE MODE.
DO YOU WISH TO PROCEED? TYPE YES OR NO. */

Completion of deployment Commissioning Open MSS Cloud on OpenStack

CONFIRM COMMAND EXECUTION: Y/N ? Y

MSS VSP - LAB 2017-05-16 13:42:48

START CHECKING PROCESS BEFORE CONVERSION

CHECKING USERS STATE ......

CHECKING ...... OK
PREPARE TO CONVERT, YOU CAN TRACE IT WITH I4I COMMAND

COMMAND EXECUTED

3 Interrogate the status of all encryption keys using the I4I command,

Step example
ZI4I;

Step result
LOADING PROGRAM VERSION 1.13-0
EXECUTION STARTED
MSCi MSS06 2016-09-09 15:35:15
KEY STATUS
------------------------------------------------------------
NORMAL
COMMAND EXECUTED
The KEY STATUS indicates NORMAL.

4 Change the SYSTEM user password using the IAG command.

After configuring the system encryption keys, the password of the current user
(SYSTEM) must be changed.

Step example
ZIAG;

g Note: In case of CBAM-based deployment, update the password in the VNF
parameters as well, as described in
Modifying the VNF attribute parameter values in CBAM.

Related procedures
Setting the C-number on page 110

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Modifying the VNF attribute parameter values in CBAM on page 88

9.5 Adding the spare OMU unit

You can add the spare OMU to the Open MSS Cloud with the USA command. After
adding the unit, change and check the unit state. This procedure is optional if you use
CBAM and the Initialize operation.

Procedure

1 Add the spare OMU using the USA command.

Step example
ZUSA:OMU,1;

2 Change the state of the new OMU using the USC command.

Step example
ZUSC:OMU,1:SE;
ZUSC:OMU,1:TE;
ZUSC:OMU,1:SP;

3 Check the state of the units using the USI command.

Step example
WORKING STATE OF UNITS
UNIT PHYS STATE LOCATION INFO
OMU-0 0000 WO-EX -
OMU-1 0001 SP-EX -

TOTAL OF 2 UNITS

COMMAND EXECUTED

9.6 Configuring IP addresses for OMU

After the first deployment, you have to configure the logical and physical IP addresses of
the OMU. Without an IP address, the OMU can only be accessed through the
OpenStack dashboard. You can configure it through DHCP client or manually.

Completion of deployment Commissioning Open MSS Cloud on OpenStack

Purpose
To configure the IP addresses for OMU, execute one of the following procedures.

• If you want to configure the IP addresses through DHCP client, execute chapter
Configuring IP addresses for OMU in case of DHCP usage.

• If you want to configure the IP addresses manually, execute chapter Configuring IP
addresses for OMU manually.

Related procedures
Configuring IP addresses for OMU in case of DHCP usage on page 116
Configuring IP addresses for OMU manually on page 117

9.6.1 Configuring IP addresses for OMU in case of DHCP usage

Execute a switchover on the OMU, then execute the IP address configuring command
through the DHCP server.

Purpose
If the OMU's DHCP client is used, after the first deployment the working OMU should
receive the IP address configured in the template via DHCP.
If the working OMU has neither physical nor logical IP address configured, it sends out a
DHCP request every 15 seconds.

Procedure

1 After the working OMU receives an IP address, execute a switchover procedure to
ensure that both OMUs receive IP addresses. Use the USC command.

Step example
ZUSC:OMU,0:SP;

Step result
The OMU-1 receives an IP address via DHCP.

2 Set the logical IP address manually, since the DHCP only sets the physical IP addresses.
Use the QRN command.

Step example
ZQRN:OMU,0::EL4,:"192.0.2.70",28,L,;

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Result

g Note: After both OMUs have physical IP addresses, and the logical IP address is
configured, the DHCP server is no longer needed on the OaM network. The IP
addresses reserved by the DHCP servers can be used.

Related procedures
Configuring IP addresses for OMU on page 115

9.6.2 Configuring IP addresses for OMU manually

You can configure manually the IP addresses for OMU in the OpenStack dashboard.
Manual IP address configuring consists of unit bring-up, EL4 interface creation, logical
and physical address and static route setting steps.

Purpose

g Note: In case of DHCP usage, follow the steps in section
Configuring IP addresses for OMU in case of DHCP usage.

Procedure

1 Access the OMU-0 from the OpenStack dashboard.

For more information, see section Accessing the OMU console.

2 Log into the OMU and access the MML terminal.

3 Bring up the OMU-1.

See section Unit bringup in Open MSS Cloud for instructions.

4 Create the EL4 interface to both OMUs using the QRA command.

Step example
ZQRA:OMU,0&1::EL4::UP:;

5 Set logical address to both OMUs using the QRN command.

Step example
ZQRN:OMU,0&1::EL4,:"192.0.2.70",28,L,;'

Completion of deployment Commissioning Open MSS Cloud on OpenStack

6 Set physical address to both OMUs using the QRN command.

Step example
ZQRN:OMU,0::EL4:"192.0.2.68",28,P,;
ZQRN:OMU,1::EL4:"192.0.2.69",28,P,;

7 Set static route to both OMUs using the QKC command.

Step example
ZQKC:OMU,0:::"192.168.2.65":PHY;
ZQKC:OMU,1:::"192.168.2.65":PHY;

Related procedures
Configuring IP addresses for OMU on page 115

9.7 Unit bringup in Open MSS Cloud

Since VNF is delivered with only 1 OMU, you must add the spare OMU, CMM, CMU,
STU, CHU, VLRU, IPDU and GISU units.

Purpose
You must bring up the units. If you are using CBAM, you can bring up the spare OMU
and CMM units under the Initialize operation, and the CMU, STU, CHU, VLRU, IPDU,
and GISU units under the Bringup operation, automatically. If you are not using CBAM,
you must add the units according to the following instructions, manually.

g Note: In the examples of the following unit bringup subsections, the MSS is prepared
for a specific capacity. Find the exact unit numbers necessary for the current
deployment in document Open MSS CLOUD server blade, memory and storage
requirements in Open MSS Cloud CM CFP5 release - OpenStack.

If the unit bringup fails, perform the procedure described in section Troubleshoot for
failed unit bringup.

Procedure

1 Log in to a new MML session via SSH.

Commissioning Open MSS Cloud on OpenStack Completion of deployment

2 Interrogate the unit state with the USI command.

Step example
ZUSI;

Step result
LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
OMU 0000 WO-EX -
EMB-0 WO-EX -
EMB-1 SP-EX -

TOTAL OF 3 UNITS

COMMAND EXECUTED

3 Add the computer units.

OMU Adding the spare OMU unit
CMM Adding the CMM units
CMU Adding the CMU units
STU Adding the STU units
CHU Adding the CHU units
VLRU Adding the VLRU units
IPDU Adding the IPDU units
GISU Adding the GISU units

Other resources

References to other documents

Open MSS CLOUD server blade, memory and storage requirements in Open MSS
Cloud CM CFP5 release - OpenStack

Completion of deployment Commissioning Open MSS Cloud on OpenStack

9.7.1 Adding the CMM units

You can add the CMM units to the Open MSS Cloud using the USA command. After
adding the unit, change and check the unit state. This procedure is optional if you use
CBAM and the Initialize button.

Procedure

1 Add the CMM units using the USA command.

Step example
ZUSA:CMM,0&&1:;

2 Change the states of the CMM units using the USC command.

Step example
ZUSC:CMM,0:SE;
ZUSC:CMM,0:TE;
ZUSC:CMM,0:WO;
ZUSC:CMM,1:SE;
ZUSC:CMM,1:TE;
ZUSC:CMM,1:SP;

3 Check the unit states using the USI command.

Step example
ZUSI:CMM;

Step result
LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
CMM-0 0004 WO-EX -
CMM-1 0005 SP-EX -

TOTAL OF 2 UNITS
INCORRECT STATES 1

Commissioning Open MSS Cloud on OpenStack Completion of deployment

COMMAND EXECUTED

9.7.2 Adding the CMU units

You can add the CMU units to the Open MSS Cloud using the USA command. After
adding the unit, change and check the unit state.

Procedure

1 Add the CMU units using the USA command.

Step example
ZUSA:CMU,0&&1;

2 Change the states of the CMU units using the USC command.

Step example
ZUSC:CMU,0:SE;
ZUSC:CMU,0:TE;
ZUSC:CMU,0:WO;
ZUSC:CMU,1:SE;
ZUSC:CMU,1:TE;
ZUSC:CMU,1:SP;

3 Check the unit states using the USI command.

Step example
ZUSI:CMU;

Step result
LOADING PROGRAM VERSION 1.19-0

EXECUTION STARTED

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO

Completion of deployment Commissioning Open MSS Cloud on OpenStack

CMU-0 000A WO-EX -

CMU-1 000B SP-EX -

TOTAL OF 2 UNITS

COMMAND EXECUTED

9.7.3 Adding the STU units

You can add the STU units to the Open MSS Cloud using the USA command. After
adding the unit, change and check the unit state.

Procedure

1 Add the STU units using the USA command.

Step example
ZUSA:STU,0&&1;

2 Change the states of the STU units using the USC command.

Step example
ZUSC:STU,0:SE;
ZUSC:STU,0:TE;
ZUSC:STU,0:WO;
ZUSC:STU,1:SE;
ZUSC:STU,1:TE;
ZUSC:STU,1:SP;

3 Check the unit states using the USI command.

Step example
ZUSI:STU;

Step result
LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

Commissioning Open MSS Cloud on OpenStack Completion of deployment

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
STU-0 000A WO-EX -
STU-1 000B SP-EX -

TOTAL OF 2 UNITS

COMMAND EXECUTED

9.7.4 Adding the CHU units

You can add the CHU units to the Open MSS Cloud using the USA command. After
adding the unit, change and check the unit state, then clear the INAC flag.

Procedure

1 Add the CHU units using the USA command.

w NOTICE: Create the CHU units in the following order:
a) CHU-0
b) CHU-1
c) CHU-1-0
d) CHU-1-1

Step example
ZUSA:CHU,0&&1;
ZUSA:CHU,1,0;
ZUSA:CHU,1,1;

2 Change the states of the CHU units using the USC command.

Step example
ZUSC:CHU,0,0:SE;
ZUSC:CHU,0,0:TE;
ZUSC:CHU,0,0:WO;
ZUSC:CHU,0,1:SE;
ZUSC:CHU,0,1:TE;
ZUSC:CHU,0,1:SP;
ZUSC:CHU,1,0:SE;
ZUSC:CHU,1,0:TE;

Completion of deployment Commissioning Open MSS Cloud on OpenStack

ZUSC:CHU,1,0:WO;
ZUSC:CHU,1,1:SE;
ZUSC:CHU,1,1:TE;
ZUSC:CHU,1,1:SP;

3 Check the unit states using the USI command.

Step example
ZUSI:CHU;

Step result
LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
CHU-0-0 0010 WO-EX INAC
CHU-0-1 0011 SP-EX INAC
CHU-1-0 0012 WO-EX INAC
CHU-1-1 0013 SP-EX INAC

TOTAL OF 4 UNITS

COMMAND EXECUTED

4 Clear the INAC flag from the CHU units.

For the exact procedure see Charging Handling Operate and Maintain document,
section Activating charging units.

9.7.5 Adding the VLRU units

You can add the VLRU units to the Open MSS Cloud using the USA command. After
adding the unit, change and check the unit state.

Purpose

g Note: In Open TRS Cloud the VLRU units are not used, so must not be created.

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Procedure

1 Add the VLRU units using the USA command.

w NOTICE: Create the VLRU units in the following order:
a) VLRU-0
b) VLRU-1
c) VLRU-1-0
d) VLRU-1-1
e) …
f) VLRU-5-1

Step example
ZUSA:VLRU,0&&1;
ZUSA:VLRU,1,0;
ZUSA:VLRU,1,1;
ZUSA:VLRU,2,0;
ZUSA:VLRU,2,1;
ZUSA:VLRU,3,0;
ZUSA:VLRU,3,1;
ZUSA:VLRU,4,0;
ZUSA:VLRU,4,1;
ZUSA:VLRU,5,0;
ZUSA:VLRU,5,1;

2 Change the states of the VLRU units using the USC command.

Step example
ZUSC:VLRU,0,0:SE;
ZUSC:VLRU,0,0:WO;
ZUSC:VLRU,0,1:SE;
ZUSC:VLRU,0,1:TE;
ZUSC:VLRU,0,1:SP;
ZUSC:VLRU,1,0:SE;
ZUSC:VLRU,1,0:WO;
ZUSC:VLRU,1,1:SE;
ZUSC:VLRU,1,1:TE;
ZUSC:VLRU,1,1:SP;
ZUSC:VLRU,2,0:SE;
ZUSC:VLRU,2,0:WO;
ZUSC:VLRU,2,1:SE;
ZUSC:VLRU,2,1:TE;
ZUSC:VLRU,2,1:SP;
ZUSC:VLRU,3,0:SE;
ZUSC:VLRU,3,0:WO;
ZUSC:VLRU,3,1:SE;
ZUSC:VLRU,3,1:TE;

Completion of deployment Commissioning Open MSS Cloud on OpenStack

ZUSC:VLRU,3,1:SP;
ZUSC:VLRU,4,0:SE;
ZUSC:VLRU,4,0:WO;
ZUSC:VLRU,4,1:SE;
ZUSC:VLRU,4,1:TE;
ZUSC:VLRU,4,1:SP;
ZUSC:VLRU,5,0:SE;
ZUSC:VLRU,5,0:WO;
ZUSC:VLRU,5,1:SE;
ZUSC:VLRU,5,1:TE;
ZUSC:VLRU,5,1:SP;

3 Check the unit states using the USI command.

Step example
ZUSI:VLRU;

Step result
LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

MSS MSS11
WORKING STATE OF UNITS
UNIT PHYS STATE INFO
VLRU-0-0 001A WO-EX -
VLRU-0-1 001B SP-EX -
VLRU-1-0 001C WO-EX -
VLRU-1-1 001D SP-EX -
VLRU-2-0 001E WO-EX -
VLRU-2-1 001F SP-EX -
VLRU-3-0 0020 WO-EX -
VLRU-3-1 0021 SP-EX -
VLRU-4-0 0022 WO-EX -
VLRU-4-1 0023 SP-EX -
VLRU-5-0 0024 WO-EX -
VLRU-5-1 0025 SP-EX -

TOTAL OF 12 UNITS

COMMAND EXECUTED

9.7.6 Adding the IPDU units

You can add the IPDU units to the Open MSS Cloud using the USA command. After
adding the unit, set the recovery group flag, then change and check the unit state.

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Procedure

1 Add the IPDU units using the USA command.

Step example
ZUSA:IPDU,0&&6;

2 Set recovery group 2 flags to the CP IPDU units using the UST command.

Step example
ZUST:IPDU,3:S-GRP2;
ZUST:IPDU,4:S-GRP2;
ZUST:IPDU,5:S-GRP2;
ZUST:IPDU,6:S-GRP2;

3 Change the states of the IPDU units using the USC command.

Step example
ZUSC:IPDU,0:SE;
ZUSC:IPDU,0:TE;
ZUSC:IPDU,0:SP;
ZUSC:IPDU,1:SE;
ZUSC:IPDU,1:TE;
ZUSC:IPDU,1:SP;
ZUSC:IPDU,2:SE;
ZUSC:IPDU,2:TE;
ZUSC:IPDU,2:SP;
ZUSC:IPDU,3:SE;
ZUSC:IPDU,3:TE;
ZUSC:IPDU,3:SP;
ZUSC:IPDU,4:SE;
ZUSC:IPDU,4:TE;
ZUSC:IPDU,4:SP;
ZUSC:IPDU,5:SE;
ZUSC:IPDU,5:TE;
ZUSC:IPDU,5:SP;
ZUSC:IPDU,6:SE;
ZUSC:IPDU,6:TE;
ZUSC:IPDU,6:SP;

4 Check the unit states using the USI command.

Step example
ZUSI:IPDU;

Completion of deployment Commissioning Open MSS Cloud on OpenStack

Step result
LOADING PROGRAM VERSION 1.18-0

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
IPDU-0 0070 SP-EX IDLE
IPDU-1 0071 SP-EX IDLE
IPDU-2 0072 SP-EX IDLE
IPDU-3 0073 SP-EX IDLE GRP2
IPDU-4 0074 SP-EX IDLE GRP2
IPDU-5 0075 SP-EX IDLE GRP2
IPDU-6 0076 SP-EX IDLE GRP2

TOTAL OF 7 UNITS
GROUP 2 OF N+1 REPLACEABLE 4

COMMAND EXECUTED

9.7.7 Adding the GISU units

You can add the GISU units to the Open MSS Cloud using the USA command. After
adding the unit, change and check the unit state.

Procedure

1 Add the GISU units using the USA command.

Step example
ZUSA:GISU,0&&30;

2 Change the states of the GISU units using the USC command.

Step example
ZUSC:GISU,0:SE;
ZUSC:GISU,0:TE;
ZUSC:GISU,0:SP;
ZUSC:GISU,1:SE;
ZUSC:GISU,1:TE;
ZUSC:GISU,1:SP;
ZUSC:GISU,2:SE;
ZUSC:GISU,2:TE;
ZUSC:GISU,2:SP;

Commissioning Open MSS Cloud on OpenStack Completion of deployment

ZUSC:GISU,3:SE;
ZUSC:GISU,3:TE;
ZUSC:GISU,3:SP;
ZUSC:GISU,4:SE;
ZUSC:GISU,4:TE;
ZUSC:GISU,4:SP;
ZUSC:GISU,5:SE;
ZUSC:GISU,5:TE;
ZUSC:GISU,5:SP;
ZUSC:GISU,6:SE;
ZUSC:GISU,6:TE;
ZUSC:GISU,6:SP;

3 Check the unit states using the USI command.

g Note: States of the GISUs change to WO-EX automatically just as you configure
the logical IPs of the GISUs. See the details in document
Site Connectivity Configuration for Open MSS Cloud on OpenStack.

Step example
ZUSI:GISU;

Step result
LOADING PROGRAM VERSION 1.18-0

MSS VSP - LAB

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
GISU-0 003A SP-EX IDLE
GISU-1 003B SP-EX IDLE
GISU-2 003C SP-EX IDLE
GISU-3 003D SP-EX IDLE
GISU-4 003E SP-EX IDLE
GISU-5 003F SP-EX IDLE
GISU-6 0040 SP-EX IDLE
GISU-7 0041 SE-NH -
GISU-8 0042 SE-NH -
GISU-9 0043 SE-NH -
GISU-10 0044 SE-NH -
GISU-11 0045 SE-NH -
GISU-12 0046 SE-NH -
GISU-13 0047 SE-NH -
GISU-14 0048 SE-NH -
GISU-15 0049 SE-NH -
GISU-16 004A SE-NH -
GISU-17 004B SE-NH -
GISU-18 004C SE-NH -

Completion of deployment Commissioning Open MSS Cloud on OpenStack

GISU-19 004D SE-NH -

GISU-20 004E SE-NH -
GISU-21 004F SE-NH -
GISU-22 0050 SE-NH -
GISU-23 0051 SE-NH -
GISU-24 0052 SE-NH -
GISU-25 0053 SE-NH -
GISU-26 0054 SE-NH -
GISU-27 0055 SE-NH -
GISU-28 0056 SE-NH -
GISU-29 0057 SE-NH -
GISU-30 0058 SE-NH -

TOTAL OF 31 UNITS

COMMAND EXECUTED

Other resources

References to other documents

Site Connectivity Configuration for Open MSS Cloud on OpenStack

9.8 Troubleshooting the DHCP service

Check if the DHCP is enabled on the OaM network in case the service does not provide
the default gateway.

Solution

Possible cause
OpenStack bug.

Troubleshooting procedure: Checking the DHCP and altering the host

routes.

Procedure

1 Check if the DHCP is enabled on the OaM network.

Step example
openstack subnet show MSS8_OaM_subnet

Commissioning Open MSS Cloud on OpenStack Completion of deployment

2 Alter the host routes on the OaM network.

g Note: The additional routes are not required in this subnet. This configuration is
only needed as a workaround. The DHCP server provides the correct default
gateway settings to the subnet, regardless from the configured additional routes.

Step example
openstack subnet update --host-route
destination=255.255.255.255/24,nexthop=192.0.2.65 MSS8_OaM_subnet

Step result
After both OMUs have physical IP addresses, no more DHCP queries are sent from
the OMU.

9.9 Troubleshoot for failed unit bringup

If a unit stuck in test or RP1 booting phase, Virtual Machine resetting is necessary.

Description and symptoms

During unit bringup when you check the unit states, if you find a unit stuck in test or RP1
booting phase (see example in the below table), you must reset the Virtual Machine (VM)
that contains the affected unit. Execute a hard reboot on the VM in the OpenStack
Dashboard (Horizon).

Table 13 Example for stuck unit in test phase

GISU-5 00C7 TE-EX RP 1 BYSY OBSE RCMD RUSR RSET

Solution

Troubleshooting procedure: Resetting a VM with OpenStack Dashboard

Procedure

1 Log in to the OpenStack dashboard and select the Project menu.

2 In the Project menu, select the Compute menu item.

Completion of deployment Commissioning Open MSS Cloud on OpenStack

3 In the Compute menu, select the Instances menu item.

4 In the Instances pane, search the VM to reset.

5 In the line of the needed VM, from the Actions drop-down list, select the Hard Reboot
Instance option.

Step example

Figure 60 Rebooting the VM

9.10 Checking the GRO setting on VXLAN interfaces

You must perform this procedure with root privileges on each compute node of the
OpenStack.

Commissioning Open MSS Cloud on OpenStack Completion of deployment

Procedure

1 Check the Generic Segmentation Offload (GRO) setting on the VXLAN interfaces with
the following command.

g Note: Execute this step on each compute node of the OpenStack.

Step example
ethtool -k vxlan_sys_4789

2 If generic-receive-offload is on, turn it off with the following command.

Step example
sudo ethtool -K vxlan_sys_4789 gro off

9.11 Troubleshooting predefined flavor use

During stack creation, the operator may encounter a CREATE_FAILED error message if
the environment.yaml file contains a non-existent predefined flavor.

Description and symptoms

During stack creation, after the operator gives the
$ heat stack-create -e environment.yaml -f heat_template.yaml --poll 5
predeftest
command, the following error message appears:
2018-02-21 06:12:08 [omu]: CREATE_FAILED resources.omu: Property error:
resources[1].properties.flavor: Error validating value 'MSS_82_2': The
Flavor ID (MSS_82_2) could not be found.

2018-02-21 06:12:10 [predeftest]: CREATE_FAILED Resource CREATE failed:

resources.omu: Property error: resources[1].properties.flavor: Error
validating value 'MSS_82_2': The Flavor ID (MSS_82_2) could not be
found.

Solution

Possible cause: The environment.yaml file contains a non-existent

predefined flavor.

Troubleshooting procedure: Edit the environment.yaml file.

Completion of deployment Commissioning Open MSS Cloud on OpenStack

• Give an existing predefined flavor in the environment.yaml file.

Step example
flavor_2_2: MSS_82_2 -> flavor_2_2: MSS_2_2

g Note: The flavors can be defined in the dashboard. See section
Creating predefined flavors.

9.12 NetAct registration of deployed MSS

NetAct registration depends on which tool you use for deploying the MSS. If you deploy
the MSS with Heat, integrate the MSS manually into NetAct. If you deploy the MSS with
CBAM, you can perform the NetAct registration in CBAM.

Purpose
When you deploy the MSS with Heat, you can integrate the Open MSS Cloud to NetAct
only manually. For manual instructions, see Integrating Open MSS Cloud to NetAct in the
NetAct documentation set.
After successful instantiation, you can integrate the Open MSS Cloud to NetAct via
CBAM.

Procedure

1 Prepare the MSS for integration.

Sub-steps

a) Check that there is at least one CMM unit in WO-EX state. Use the USI
command.

CMM unit is used in license interrogation during the automatic integration.

Step example
< ZUSI:CMM;

LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

MSS vMSS00 2018-03-20 13:11:34

Commissioning Open MSS Cloud on OpenStack Completion of deployment

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
CMM-0 0004 WO-EX -
CMM-1 0005 SP-EX -

TOTAL OF 2 UNITS

COMMAND EXECUTED

b) Prepare Transport Layer Security configuration if you plan to use XoHS protocol.

See subsection Configuring Transport Layer Security of section Integrating
OpenStack-based Open MSS Cloud to NetAct in documentation Integrating Open
MSS Cloud to NetAct. Find it in the NetAct documentation set.

2 Prepare NetAct for integration.

See subsection Preparing NetAct of section Integrating OpenStack-based Open
MSS Cloud to NetAct in documentation Integrating Open MSS Cloud to NetAct. Find
it in the NetAct documentation set.

3 Update the NetAct related parameters as described in section Modifying the VNF
attribute parameter values in CBAM.

Use the following parameters:
Table 14 NetAct related parameter descriptions
Extension parameter name Description Example
netact_address One of the IP addresses of the 0.0.0.0
NetAct VM where intgwas
services are running
netact_port Port of NetAct 22
netact_mrname NetAct Maintenance Region MRC-MSC/MR-MSS
name
netact_plmnname NetAct PLMN name PLMN-PLMN
netact_ne_type NetAct network element type MSC
netact_adaptation_release NetAct adaptation release MSSCloudCMCFP5
netact_xoh_securitymode Security mode of XOH interface 1
in NetAct
Set:
• 1 for HTTPS
• 0 for HTTP

Completion of deployment Commissioning Open MSS Cloud on OpenStack

Table 14 NetAct related parameter descriptions (Cont.)
Extension parameter name Description Example

g Note: Nokia recommends
to choose the secure
protocol HTTPS (XOHS)
instead of HTTP. Before
setting HTTPS, provide
that the TLS is configured
as described in chapter
Configuring Transport
Layer Security in
documentation Integrating
CBAM to NetAct.

netact_xoh_port Port of the XOH agent running on 443

network element
Set:
• 443 for HTTPS
• 80 for HTTP

netact_ftp_securitymode Security mode for FTP agent 1
Set:
• 1 for SFTP
• 0 for FTP

g Note: Nokia recommends
to choose the secure
protocol SFTP instead of
FTP.

netact_ftp_port Port of the FTP agent running on 22
network element
Set:
• 22 for SFTP
• 21 for FTP

netact_username User name in NetAct for the omc

integration
netact_mssadm_user User name in MSS for the MSSADM
integration
netact_password Password in NetAct for the
netact_username user
netact_mssadm_pass Password in MSS for the
netact_mssadm_user user

Commissioning Open MSS Cloud on OpenStack Completion of deployment

4 Initiate NetAct integration.

Sub-steps

a) In the Virtualized Network Functions pane, in the line of the created VNF, click

the three dot button, then select the Integrate with NetAct menu item.

b) In the pop-up window, confirm the action by clicking the OK button.

Figure 61 Integrate with NetAct

Related procedures
Modifying the VNF attribute parameter values in CBAM on page 88

Other resources

References to other documents

Integrating Open MSS Cloud to NetAct (in NetAct documentation set)
Integrating CBAM to NetAct (in NetAct documentation set)

9.13 Checking the operational status of the Open MSS

Cloud
For the correct operation of the VNF on OpenStack, all basic units must be in working
executing (WO-EX) or spare executing (SP-EX) state. This procedure is optional if you
use the CBAM and the Initialize operation on the instantiated VNF.

Before you start

The Open MSS deployment must be finished. You must bring up OMU and CMM units,
and they must be in operational state.

Completion of deployment Commissioning Open MSS Cloud on OpenStack

Procedure

1 Log in to the Man-Machine Interface (MMI) and check the EMB supervision timer with the
WOI command.

Step example
MAIN LEVEL COMMAND <___>
< ZWOI:9,193;

LOADING PROGRAM VERSION 9.5-0

EXECUTION STARTED

READING DATA FROM DATABASE, PLEASE WAIT ...

PARAMETER CLASS: 9 SYSTEM_SUPERVISION

IDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY

00193 EMB_SUPERV_MULTIPLIER 0008 YES

COMMAND EXECUTED

PARAMETER HANDLING COMMAND <WO_>

2 If the value of the EMB_SUPERV_MULTIPLIER parameter is lower than 8, increase it
with the WOC command.

Step example
< ZWOC:9,193,8;

LOADING PROGRAM VERSION 9.5-0

EXECUTION STARTED

CHANGE PARAMETER VALUE:

PARAMETER NAME NEW VALUE

EMB_SUPERV_MULTIPLIER 0008

COMMAND EXECUTED

PARAMETER HANDLING COMMAND <WO_>

Commissioning Open MSS Cloud on OpenStack Completion of deployment

3 After you have changed the parameter value, restart the system with the USS command.

Step example
< ZUSS:SYM:;

EXECUTION STARTED

SYSTEM RESTART WITH SYM UNIT REQUESTED

CONFIRM COMMAND EXECUTION: Y/N ? Y

SYSTEM RESTART ORDERED

END OF DIALOGUE SESSION

Connection closed

4 Check the unit states with the USI command.

The booting process takes approximately 5-10 minutes after starting the application.
After the process is finished, at least one Operation and Maintenance Unit (OMU)
must be in WO-EX state, and one Ethernet-based Message Bus (EMB) must be in
WO-EX state and one in SP-EX state.

Step example
ZUSI;

LOADING PROGRAM VERSION 1.13-0

EXECUTION STARTED

WORKING STATE OF UNITS

UNIT PHYS STATE INFO
OMU 0000 WO-EX -
CMM-0 0001 SP-EX -
CMM-1 0002 WO-EX -
EMB-0 WO-EX -
EMB-1 SP-EX -

TOTAL OF 3 UNITS

COMMAND EXECUTED

5 If some of the units are not in the correct state, check the unit operability by opening the
console of the unit in Horizon.

Completion of deployment Commissioning Open MSS Cloud on OpenStack

6 Reset the units from the MMI using the USU command and check the result in the
console.

g Note: You can also reset a unit from the console by selecting Hard Reboot
Instance from the Actions drop-down list for that unit. Select Console from the
list to check the result in the console.

g Note: Do not power off or switch on the Open MSS application VMs from
Horizon or on the controller node under any circumstances. Always use reset,
and only reset from Horizon.

Figure 62 Reset unit from dashboard

Commissioning Open MSS Cloud on OpenStack Appendix: Checklist for Open MSS Cloud deployment

Appendix: Checklist for Open MSS Cloud

deployment
Tasks to perform during the Open MSS Cloud deployment process.

Table 15 Checklist for Open MSS Cloud deployment
Step Input Output References Checked
1. Define the Open MSS Minimum number of See section [ ]
number of Capacity blades in a cluster Open MSS
blades. [______]k BHCA [____] capacity
requirements.
2. Define OpenStack Datastore See section [ ]
required capacity requirement Open MSS
storage. [300]GB capacity
requirements.
Open MSS storage
space requirements
to datastore
OMU W0 [100]GB
OMU W1 [100]GB
CHU 0 W0 [180]GB
CHU 0 W1 [180]GB
CHU 1 W0 [180]GB
CHU 1 W1 [180]GB

4. Customize the Open MSS can be See section [ ]

OpenStack. deployed. Customizing the
OpenStack on
HP platform.
5. Create a Project is created and See section [ ]
project and add tenant user is added. Creating the
the tenant user. tenant user.
6. Set the Quotas are set on See section [ ]
quotas. demand. Changing
quotas.
7. Create Provider networks See section [ ]
provider are created. Creating
networks. provider
networks.
8. Upload the iPXE image is See section [ ]
iPXE image. uploaded. Uploading the
iPXE image.
9. Upload the VSA image is See section [ ]
VSA image. uploaded. Uploading the
VSA image.
10. Create VSA VSA key pairs are See section [ ]
key pairs. created. Creating VSA
key pairs.

Appendix: Checklist for Open MSS Cloud deployment Commissioning Open MSS Cloud on OpenStack

Table 15 Checklist for Open MSS Cloud deployment (Cont.)
Step Input Output References Checked
11. Upload the The OMU disk is See section [ ]
OMU disk. created. Application
content
provisioning.
12. Create the The OMU disk is See section [ ]
OMU disk. created. Creating the
OMU disk
image.
13. Create the The CHU volumes See section [ ]
CHU volumes. are created. Creating CHU
volumes in
Cinder.
14. Upload the The name of the See section [ ]
Open MSS uploaded Open MSS Uploading the
template to Heat template in Heat or VNF template to
or CBAM. CBAM the controller
node for Heat
[________________ and Uploading
______] the VNFD
package to
CBAM Catalog
for CBAM.
15. Create new Username / Open MSS instance See section [ ]
Open MSS Password is created. Creating the
instance in case MSS VNF in
CBAM is used. Network CBAM.
mappings

16. Modify the The VNF parameters See section

VNF parameters are set. Application
in Heat or CBAM variables for
Heat and
Modifying the
VNF attribute
parameter
values in CBAM
for CBAM.
17. Deploy the Open MSS instance See section [ ]
new Open MSS is deployed. Creating the
instance in Heat Heat stack and
or CBAM. Open MSS
application for
Heat and
Instantiating the
MSS VNF in
CBAM for
CBAM.
18. Do the basic See section [ ]
health check on Completion of
the new Open deployment.
MSS instance.

Nokia Border Gateway Protocol SG v3.1.1
100% (1)
Nokia Border Gateway Protocol SG v3.1.1
464 pages
Nokia Border Gateway Protocol SG v3.1.1
100% (1)
Nokia Border Gateway Protocol SG v3.1.1
464 pages
CBIS OverCloud Deploy MOP
0% (1)
CBIS OverCloud Deploy MOP
37 pages
CMM Basis and Troubleshoting
No ratings yet
CMM Basis and Troubleshoting
56 pages
Ims-Lab (1 3a)
No ratings yet
Ims-Lab (1 3a)
56 pages
Nokia Full MMI Command With Detail
0% (1)
Nokia Full MMI Command With Detail
9 pages
Intra Circle Roaming: Vodafone - Idea Cellular
100% (1)
Intra Circle Roaming: Vodafone - Idea Cellular
28 pages
Sacc
No ratings yet
Sacc
54 pages
ZXUN USPP Theoretical Basic-Interface Protocol-Interfaces and Services
No ratings yet
ZXUN USPP Theoretical Basic-Interface Protocol-Interfaces and Services
61 pages
3he15239aaadtqzza01 - v1 - 7750 SR MG and CMG Cli Reference Guide r11.0.r7
No ratings yet
3he15239aaadtqzza01 - v1 - 7750 SR MG and CMG Cli Reference Guide r11.0.r7
2,142 pages
CBIS Overview
No ratings yet
CBIS Overview
25 pages
IR8831 LTE Roaming
100% (1)
IR8831 LTE Roaming
36 pages
IMS Signaling System Part 4 H.248 Megaco
No ratings yet
IMS Signaling System Part 4 H.248 Megaco
45 pages
1.SMS Interworking in Traditional Network 1.1.mobile Originated - SMS
No ratings yet
1.SMS Interworking in Traditional Network 1.1.mobile Originated - SMS
7 pages
Volte Roaming Testing 12 May 2021: This Is A Non-Binding Permanent Reference Document of The Gsma
No ratings yet
Volte Roaming Testing 12 May 2021: This Is A Non-Binding Permanent Reference Document of The Gsma
30 pages
One-Nds Brochure
50% (2)
One-Nds Brochure
2 pages
Nokia MSC HLR MML Commands
No ratings yet
Nokia MSC HLR MML Commands
9 pages
3GPP TS 24.301 V10.13.0 (2014-03)
No ratings yet
3GPP TS 24.301 V10.13.0 (2014-03)
327 pages
1 Data Sheet Nokia Cloud Mobile Gateway
No ratings yet
1 Data Sheet Nokia Cloud Mobile Gateway
8 pages
03 - CN37533EN10GLA0 - HW and SW - Doc PDF
No ratings yet
03 - CN37533EN10GLA0 - HW and SW - Doc PDF
110 pages
Vo LTE
100% (1)
Vo LTE
9 pages
vEPC Overview
100% (2)
vEPC Overview
121 pages
Basic Call Processing - Typical Packet Call: Home
No ratings yet
Basic Call Processing - Typical Packet Call: Home
30 pages
Map
No ratings yet
Map
40 pages
PCRF Triggers
100% (3)
PCRF Triggers
95 pages
Ericsson Nfvi Solution: Francois Lemarchand - Head of Nfvi Strategy Gerry Feeney - Telco Cloud Transformation Lead
100% (2)
Ericsson Nfvi Solution: Francois Lemarchand - Head of Nfvi Strategy Gerry Feeney - Telco Cloud Transformation Lead
21 pages
Nokia Cloudband Application Manager: Benefits
No ratings yet
Nokia Cloudband Application Manager: Benefits
4 pages
Cisco GX and PCRF
100% (2)
Cisco GX and PCRF
24 pages
Nokia Session Border Controller Data Sheet en
No ratings yet
Nokia Session Border Controller Data Sheet en
8 pages
MGW Boards
100% (1)
MGW Boards
10 pages
HSS9860 V900R008C20 Data Configuration and O&M
No ratings yet
HSS9860 V900R008C20 Data Configuration and O&M
93 pages
Camel PPS
100% (1)
Camel PPS
82 pages
MSS MGW MC Interface
No ratings yet
MSS MGW MC Interface
3 pages
Troubleshooting and Maintenace For CS Core
100% (3)
Troubleshooting and Maintenace For CS Core
29 pages
Presentations PDF
No ratings yet
Presentations PDF
187 pages
GSMA PRD IR.92-v5.0
No ratings yet
GSMA PRD IR.92-v5.0
30 pages
PGW Troubleshooting 01
No ratings yet
PGW Troubleshooting 01
530 pages
Nokia BSC S and MSC S Command List Nokia
No ratings yet
Nokia BSC S and MSC S Command List Nokia
44 pages
VoWiFi Related
No ratings yet
VoWiFi Related
66 pages
Admin Guide For Open
No ratings yet
Admin Guide For Open
369 pages
Diameter
No ratings yet
Diameter
40 pages
LTE-EPC Overview - Final
No ratings yet
LTE-EPC Overview - Final
52 pages
HSS Mop
No ratings yet
HSS Mop
9 pages
Emergency Call
No ratings yet
Emergency Call
6 pages
DNS Procedures Ts - 129303v100500p
No ratings yet
DNS Procedures Ts - 129303v100500p
59 pages
Diameter Protocol
No ratings yet
Diameter Protocol
122 pages
ZXWN EIR Technical Specification
No ratings yet
ZXWN EIR Technical Specification
35 pages
Pubate Satienpoch: SCCP: Signaling Connection Control Part
No ratings yet
Pubate Satienpoch: SCCP: Signaling Connection Control Part
23 pages
OpenStack PDF
100% (1)
OpenStack PDF
323 pages
CAMEL Feature1
100% (1)
CAMEL Feature1
34 pages
Design and Deployment of The ASR5500 PDF
No ratings yet
Design and Deployment of The ASR5500 PDF
51 pages
SGSN User Guide
100% (1)
SGSN User Guide
486 pages
Oran Chart
No ratings yet
Oran Chart
2 pages
(Full) The Impact of VoLTE On IP Backhaul Network
100% (2)
(Full) The Impact of VoLTE On IP Backhaul Network
44 pages
Nokia Commands
No ratings yet
Nokia Commands
9 pages
Diameter Protocol A Complete Guide
From Everand
Diameter Protocol A Complete Guide
Gerardus Blokdyk
No ratings yet
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
OpenStack Networking Essentials
From Everand
OpenStack Networking Essentials
James Denton
No ratings yet
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
Cloud Computing : Beginners And Intermediate User Guide
From Everand
Cloud Computing : Beginners And Intermediate User Guide
David comer
No ratings yet
FNS - (Mme - CBC) SBC Interface - 18.5
No ratings yet
FNS - (Mme - CBC) SBC Interface - 18.5
26 pages
CBIS - Acceptance Test Procedures - 12-2021
No ratings yet
CBIS - Acceptance Test Procedures - 12-2021
175 pages
Report Leave Management System 1
No ratings yet
Report Leave Management System 1
58 pages
Ssrs Interview Questions and Answers
No ratings yet
Ssrs Interview Questions and Answers
15 pages
cetol for solidworks
No ratings yet
cetol for solidworks
2 pages
Typing Trans Literate D Text in Macos X
No ratings yet
Typing Trans Literate D Text in Macos X
4 pages
How To Configure OCI Connection
No ratings yet
How To Configure OCI Connection
4 pages
Linking and Loading in Os
No ratings yet
Linking and Loading in Os
3 pages
为什么要在helpwriting net订购书籍？
100% (2)
为什么要在helpwriting net订购书籍？
8 pages
Access Control and Inheritance
No ratings yet
Access Control and Inheritance
5 pages
Manual Sundoo ST-20
No ratings yet
Manual Sundoo ST-20
10 pages
SM-A05X UM LTN UU Eng Rev.2.0 240213
No ratings yet
SM-A05X UM LTN UU Eng Rev.2.0 240213
125 pages
Blackbox Technologies: Presents Introduction To Gear Inspection Software (Gearsoft)
No ratings yet
Blackbox Technologies: Presents Introduction To Gear Inspection Software (Gearsoft)
25 pages
Paper Prototypes Still Our Favorite
No ratings yet
Paper Prototypes Still Our Favorite
4 pages
25 Must-Know Excel Interview Questions?
No ratings yet
25 Must-Know Excel Interview Questions?
13 pages
Types of Programming Languages
No ratings yet
Types of Programming Languages
12 pages
GoogleCloudPlatform Vs AWS
100% (1)
GoogleCloudPlatform Vs AWS
2 pages
Limbo Log
No ratings yet
Limbo Log
21 pages
Oci-Architect-Associate 2020
No ratings yet
Oci-Architect-Associate 2020
20 pages
U.A.E 5GEPC Project: EC 3.0 Deployment Via Bcat 5GEPC Basic Info
No ratings yet
U.A.E 5GEPC Project: EC 3.0 Deployment Via Bcat 5GEPC Basic Info
19 pages
InitData Java
No ratings yet
InitData Java
5 pages
MECM
No ratings yet
MECM
86 pages
Training Matrix
No ratings yet
Training Matrix
9 pages
VariCAD. Reference Manual
No ratings yet
VariCAD. Reference Manual
110 pages
Sap Hana Blog
No ratings yet
Sap Hana Blog
5 pages
Introduction To Asynchronous Programming: 1 The Models
No ratings yet
Introduction To Asynchronous Programming: 1 The Models
6 pages
20231213T195021 cdU2rcL4
No ratings yet
20231213T195021 cdU2rcL4
6 pages
Emx Gui Messages
No ratings yet
Emx Gui Messages
35 pages
Ict Skills Grade 10
No ratings yet
Ict Skills Grade 10
9 pages
Winter'24 Release Updates
No ratings yet
Winter'24 Release Updates
162 pages
Middle Ware Cot
No ratings yet
Middle Ware Cot
21 pages
Diagnostics Log
No ratings yet
Diagnostics Log
94 pages

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.