Author Laszlo Szalay

Owner TypeNameHere
Organization TypeDepartmentOrFunctionHere
Approver TypeNameHere
Document ID TypeIDHere
Document location TypeDocLocationHere

Change History

Version Status Date Author Owner Reviewed by Reviewed Approver Approval Description of changes
date date
0.1 Draft 12-02-2018 Laszlo Szalay Document skeleton.

CMM Deployment Guide

Solution Integration Projects

11/3/2023 – TypeDocIDHere <insert security classification here> © 2017 Nokia

1 / 19
Contents
1 Scope of the Document............................................................................................................4
2 Prerequisites.............................................................................................................................5
2.1 Download the latest application software and documentation.................................................5
2.2 Study the documents before starting deployment....................................................................6
3 Cloud Preparation....................................................................................................................6
3.1 Create Tenant/Project/User for CMM......................................................................................6
3.1.1 Create Project...........................................................................................................................6
3.1.2 Create users and roles..............................................................................................................6
3.1.3 Create keysone file for your project.........................................................................................7
3.1.4 Source the new keystone file:..................................................................................................7
3.1.5 Upload the downloaded and converted RAW files to image repository..................................7
3.1.6 Make networks and subnets according to IP Plan....................................................................7
3.1.7 Set proper flavors according to the guide................................................................................9
3.1.8 Volume for backup storage......................................................................................................9
3.1.9 Create RSA Keypair for the VMs............................................................................................9
4 CBAM Template Preparation..................................................................................................9
4.1 Get Deployment artefacts for CMM........................................................................................9
4.1.1 Acquire sample template..........................................................................................................9
4.1.2 Fill the template with the local ENV parameters.....................................................................10
4.1.3 Create UUID file......................................................................................................................11
4.1.4 Generate CBAM template........................................................................................................13
4.1.5 Download the generated CBAM template...............................................................................14
5 Deploying the CMM................................................................................................................14
5.1 Upload Catalog........................................................................................................................14
5.2 Create VNF..............................................................................................................................14
5.3 Modify (optional for CMM) & Instantiate...............................................................................15
5.3.1 Instantiate VNF........................................................................................................................15
6 Check health of the newly created VNF’s...............................................................................16
6.1 NECC units are used for administration..................................................................................16
6.1.1 Log into NECC-1/2/3 for the first time....................................................................................16

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

2 / 19
6.1.2 Run the helth-check script........................................................................................................16
6.1.3 Make sure that all units can ping every other with jumbo packets..........................................16
6.1.4 Check that all the VIP addresses are assigned and reachable (169.254.65.x).........................17
7 Configuring the application.....................................................................................................18
7.1 Copy your configuration lines to the NECC with cmm user...................................................18

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

3 / 19
1 Scope of the Document
The purpose of this document to provide step by step installation manual for CMM v.18.0.
.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

4 / 19
2 Prerequisites
2.1 Download the latest application software and documentation

-Go to Alcatel-Lucent Order Management and OnLine Customer Support (OLCS) webpage:
https://market.alcatel-lucent.com

-Choose from the drop down list the products name CMM (Cloud Mobility Manager) and Submit.

-Choose the software version and select “Add to cart”

-See your cart

-Download the documentation and software package (for me it worked only with browser download, but
others may succeed with some more sophisticated ways Java issues may arise).

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

5 / 19
2.2 Study the documents before starting deployment

Go through at least the following documents:

 CMM18.0.0RL_V1_CMM Release Notes CMM18.0.0.pdf
 DN09131779CMM18_V1_IP Connectivity - CMM18.pdf
 DN09131801CMM18_V1_Lifecycle Management and Software Upgrade - CMM18.pdf
 DN09260888_V1_Cloud Mobility Manager Appliance Installation and Setup Guide.pdf

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

6 / 19
3 Cloud Preparation
3.1 Create Tenant/Project/User for CMM

3.1.1 Create Project

openstack project create cmm63

3.1.2 Create users and roles

openstack user create cmm63 --project cmm63 --password cmm63

openstack role add admin --project cmm63 --user cmm63
openstack role add heat_stack_owner --project cmm63 --user cmm63

3.1.3 Create keysone file for your project

vi keysonerc_cmm63
export OS_NO_CACHE=True
export OS_CLOUDNAME=overcloud
export OS_AUTH_URL=https://10.94.237.6:13000/v2.0
export NOVA_VERSION=1.1
export COMPUTE_API_VERSION=1.1
export OS_USERNAME=cmm63
export OS_PASSWORD=cmm63
export no_proxy=,10.94.237.6
export OS_IMAGE_API_VERSION=1
export OS_TENANT_NAME=cmm63
export PS1='[\u@\h \W(cmm63)]\$ '

3.1.4 Source the new keystone file:

source keystonerc_cmm63

3.1.5 Upload the downloaded and converted RAW files to image repository

glance image-create --name CMM18.0.0-mme-cpps --is-public true --disk-format raw --container-format

bare --file CMM18.0.0-mme-cpps.raw --progress
glance image-create --name CMM18.0.0-mme-dbs --is-public true --disk-format raw --container-format bare
--file CMM18.0.0-mme-dbs.raw --progress

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

7 / 19
glance image-create --name CMM18.0.0-mme-necc --is-public true --disk-format raw --container-format
bare --file CMM18.0.0-mme-necc.raw --progress
glance image-create --name CMM18.0.0-mme-ipds --is-public true --disk-format raw --container-format bare
--file CMM18.0.0-mme-ipds.raw --progress

3.1.6 Make networks and subnets according to IP Plan

neutron net-create CMM63_OAM --provider:network_type vlan --provider:segmentation_id 460 --

provider:physical_network physnet0 --shared
neutron net-create CMM63_TCPUDP --provider:network_type vlan --provider:segmentation_id 461 --
provider:physical_network physnet0 --shared
neutron net-create CMM63_SCTP_PRI --provider:network_type vlan --provider:segmentation_id 462 --
provider:physical_network physnet0 --shared
neutron net-create CMM63_SCTP_SEC --provider:network_type vlan --provider:segmentation_id 463 --
provider:physical_network physnet0 --shared
neutron net-create CMM63_int

neutron subnet-create --name CMM63_OAM_SUNETV4 --allocation-pool

start=10.94.212.164,end=10.94.212.174 CMM63_OAM 10.94.212.160/28 --no-gateway --disable-dhcp
neutron subnet-create --name CMM63_TCPUDP_SUNETV4 --allocation-pool
start=10.94.212.180,end=10.94.212.190 CMM63_TCPUDP 10.94.212.176/28 --no-gateway --disable-dhcp
neutron subnet-create --name CMM63_SCTP_PRI_SUNETV4 --allocation-pool
start=10.94.212.132,end=10.94.212.142 CMM63_SCTP_PRI 10.94.212.128/28 --no-gateway --disable-dhcp
neutron subnet-create --name CMM63_SCTP_SEC_SUNETV4 --allocation-pool
start=10.94.212.148,end=10.94.212.158 CMM63_SCTP_SEC 10.94.212.144/28 --no-gateway --disable-
dhcp
neutron subnet-create --name CMM63_int_SUBNETV4 --allocation-pool
start=169.254.64.2,end=169.254.65.254 CMM63_int 169.254.64.0/23 --gateway 169.254.64.1 --disable-
dhcp

neutron subnet-create --name CMM63_TCPUDP_SUNETV6 --allocation-pool

start=2a00:8a00:4000:65ef:ffff:ffff:ffff:A674,end=2a00:8a00:4000:65ef:ffff:ffff:ffff:A67E
CMM63_TCPUDP 2a00:8a00:4000:65ef:ffff:ffff:ffff:a670/124 --no-gateway --disable-dhcp --ip_version 6
neutron subnet-create --name CMM63_SCTP_PRI_SUNETV6 --allocation-pool
start=2a00:8a00:4000:65ef:ffff:ffff:ffff:A644,end=2a00:8a00:4000:65ef:ffff:ffff:ffff:A64E
CMM63_SCTP_PRI 2a00:8a00:4000:65ef:ffff:ffff:ffff:a640/124 --no-gateway --disable-dhcp --ip_version 6
neutron subnet-create --name CMM63_SCTP_SEC_SUNETV6 --allocation-pool
start=2a00:8a00:4000:65ef:ffff:ffff:ffff:A654,end=2a00:8a00:4000:65ef:ffff:ffff:ffff:A65E
CMM63_SCTP_SEC 2a00:8a00:4000:65ef:ffff:ffff:ffff:a650/124 --no-gateway --disable-dhcp --ip_version 6

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

8 / 19
3.1.7 Set proper flavors according to the guide

openstack flavor create cmm_necc_8_32_20 --id auto --vcpus 8 --ram 32768 --disk 20
openstack flavor create cmm_dbs_8_24_10 --id auto --vcpus 8 --ram 24576 --disk 10
openstack flavor create cmm_cpps_8_24_10 --id auto --vcpus 8 --ram 24576 --disk 10
openstack flavor create cmm_ipds_10_24_10 --id auto --vcpus 10 --ram 24576 --disk 10

3.1.8 Volume for backup storage

cinder create --name cmm63_ext_drive --metadata readonly=False attached_mode=rw --availability-zone

nova 200

3.1.9 Create RSA Keypair for the VMs

openstack keypair create CtrlKey > CtrlKey

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

9 / 19
4 CBAM Template Preparation
4.1 Get Deployment artefacts for CMM

4.1.1 Acquire sample template

Download the appropriate sample template from the following intranet page:
http://cmm3ls.labs.ca.alcatel-lucent.com:1000/

This shall lead us to a list of samples that is based on the specific cloud underneath (OC/VM) or NW
virtualization (OVS/SRIOV…), etc. The highlighted one is usually used on NON PeV environments.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

10 / 19
.

4.1.2 Fill the template with the local ENV parameters.

Necessary to modify:
- NWs, GWs, subnet addresses for all networks.
- IP addresses for all nodes.
- Allowed address ranges to allow communication between nodes.
- availability_zone
- ne_key_name: here you need to add the created RSA key for the CMM
- security_group (other than default)

Do not change:
- Internal IP ranges
- Images (later you need to create them anway)

The attached result is the filled in template for CBAM template generation on CMM63.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

11 / 19
4.1.3 Create UUID file

On the following place generate uuid file from the filled “yaml”
http://cmm3ls.labs.ca.alcatel-lucent.com:4000/

Use
- thesample filled in the previous point
- correct version as written on the page
- CMM Type: MME or TA (MME + SGSN)
- CMM naming always classic except Verizon
- Template type: choose CBAM for CBAM deployment.
Execute the “Generate UUID File!” script.

If the syntax and semantics are correct then the script generates a UUID file similar to the following:
# small-cmm63
# resource GUIDs for CBAM

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

12 / 19
volumes:
cinder_id: "fill GUID of cinder volume here, please"

net_id:
om0: "fill GUID of om0 network here, please"
om0_ipv4: "fill GUID of ipv4 subnet of om0 network here, please"
int0: "fill GUID of int0 network here, please"
int0_ipv4: "fill GUID of ipv4 subnet of int0 network here, please"
ext_tcp_udp: "fill GUID of ext_tcp_udp network here, please"
ext_tcp_udp_ipv4: "fill GUID of ipv4 subnet of ext_tcp_udp network here, please"
ext_tcp_udp_ipv6: "fill GUID of ipv6 subnet of ext_tcp_udp network here, please"
ext_sctp_pri: "fill GUID of ext_sctp_pri network here, please"
ext_sctp_pri_ipv4: "fill GUID of ipv4 subnet of ext_sctp_pri network here, please"
ext_sctp_pri_ipv6: "fill GUID of ipv6 subnet of ext_sctp_pri network here, please"
ext_sctp_sec: "fill GUID of ext_sctp_sec network here, please"
ext_sctp_sec_ipv4: "fill GUID of ipv4 subnet of ext_sctp_sec network here, please"
ext_sctp_sec_ipv6: "fill GUID of ipv6 subnet of ext_sctp_sec network here, please"

# EOF

Fill in all the required IDs, based on the created networks and subnets created in point…..
Example of CMM63:
# small-cmm63
# resource GUIDs for CBAM

volumes:
cinder_id: "2983c009-99f4-4a22-b728-990654cea956"

net_id:
om0: "c2753a0d-6a89-46cf-9d0b-91e0f3d6175f"
om0_ipv4: "c96e3f21-726b-46c8-823a-47c8f3dbda9b"
int0: "2d45a0b0-806a-4679-a979-55b2bd8cc2bd"
int0_ipv4: "b3f6e877-bf94-4514-a82e-83c0654e155f"
ext_tcp_udp: "419b1dd9-ac3d-44bc-b8cb-7a7f593691b1"
ext_tcp_udp_ipv4: "26876179-c794-4154-918b-19477826e629"
ext_tcp_udp_ipv6: "b952dfde-3eb2-4fbb-9cd4-3d782ad52be7"
ext_sctp_pri: "6bf58a3a-71e7-45a7-b93b-de8ef62e5c27"
ext_sctp_pri_ipv4: "2c6f51e7-5006-4472-ae89-6d2401e5b70d"
ext_sctp_pri_ipv6: "f96959df-787c-4ba2-9f91-3a80710fbdbd"
ext_sctp_sec: "a5babc80-f14c-4a69-96a2-7af67704cea5"
ext_sctp_sec_ipv4: "a6676bff-cefe-4184-94ee-81dac6a3153f"
ext_sctp_sec_ipv6: "8e3d48bd-4c0b-4f23-8ab0-2d80235241ac"

# EOF

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

13 / 19
4.1.4 Generate CBAM template

Once we have the sample template from point 4.1.2 and the UUID file from point 4.1.3 the CBAM template
can be generated on the intranet page:
http://cmm3ls.labs.ca.alcatel-lucent.com:2001/

4.1.5 Download the generated CBAM template

5 Deploying the CMM

5.1 Upload Catalog

Go to CBAM and upload CBAM template downloaded in 4.1.5 package to Catalog.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

14 / 19
5.2 Create VNF

Create the VNF from the template/catalog uploaded in the previous point.

5.3 Modify (optional for CMM) & Instantiate

5.3.1 Instantiate VNF

Use the <cmm-name >.json file generated together with the CBAM template based on your sample.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

15 / 19
If CBAM says completed you can go deeper into APP layer.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

16 / 19
6 Check health of the newly created VNF’s
6.1 NECC units are used for administration.

6.1.1 Log into NECC-1/2/3 for the first time.

It may be that the ansible did not run completely in those cases passwords may differ from well known ones,
and from default ones as well. If “new” lines does not work, then the “old” lines shall be used.
remote_cmmuse_old: "2pe1qlP4zjXt"
remote_cmmuse_new: "MMEmme@1234"

If old is used t login, change is required, please change to the new one. (simple passwords were not
accepted)

The cmm user can execute cmm configuration troubleshooting commands.

The root user can make general administration of the nodes, but no cmm commands.

6.1.2 Run the helth-check script

[cmm@csr-cmm63-necc1 ~]$ su -

Password: root12

[root@csr-cmm63-necc1 app]# cmm_monitor

CMM level health check summary:

Result ........................................................................OK

Individual checks:
REMcli Status .................................................................OK
Mariadb Health Status .........................................................OK
Host Name Status ..............................................................OK
Run FNS Monitor ...............................................................OK
Mariadb Data Status ...........................................................OK

Check it on all units, that result is OK state. (In our case it often failed wit Kafka related issues, but it
does not necessary influence functionality, only statistics.)

6.1.3 Make sure that all units can ping every other with jumbo packets.

[root@csr-cmm63-necc1 app]# ping ipds0.local -s 9000

PING csr-cmm63-ipds0.local (169.254.64.60) 9000(9028) bytes of data.
9008 bytes from csr-cmm63-ipds0.local (169.254.64.60): icmp_seq=1 ttl=64 time=1.67 ms
9008 bytes from csr-cmm63-ipds0.local (169.254.64.60): icmp_seq=2 ttl=64 time=0.872 ms

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

17 / 19
If not, then probably MTU issue (lower size ok) or Port Security issues (no ping possible at all between
units) exist.

6.1.4 Check that all the VIP addresses are assigned and reachable (169.254.65.x)

[cmm@csr-cmm63-necc1 ~]$ ip a
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether fa:16:3e:1a:eb:13 brd ff:ff:ff:ff:ff:ff
inet 169.254.64.31/23 scope global eth0
valid_lft forever preferred_lft forever
inet 169.254.65.30/23 scope global secondary eth0
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe1a:eb13/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether fa:16:3e:3d:9e:5a brd ff:ff:ff:ff:ff:ff
inet 10.94.212.165/28 scope global eth1
valid_lft forever preferred_lft forever
inet 10.94.212.167/28 brd 10.94.212.175 scope global secondary eth1
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe3d:9e5a/64 scope link
valid_lft forever preferred_lft forever

7 Configuring the application

7.1 Copy your configuration lines to the NECC with cmm user

Example initial config for CMM63:

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

18 / 19
8 Check interfaces
Check the interfaces with cmm user:

[cmm@csr-cmm63-necc1 ~]$ cmm multiLink list --linkInterfaceType sgs

+-----------+-------------------+-----------+----------------+--------------------+------------+---------------+---------------+

| multiLink | linkInterfaceType | linkIndex | linkAdminState | linkOperationState | alarmState | remoteIp1 | remoteIp2 |

+-----------+-------------------+-----------+----------------+--------------------+------------+---------------+---------------+

| sgs | sgs | 1 | unlocked | enabled | none | 10.94.211.236 | 10.94.211.212 |

+-----------+-------------------+-----------+----------------+--------------------+------------+---------------+---------------+

[cmm@csr-cmm63-necc1 ~]$ cmm multiLink list --linkInterfaceType s6ad

+-----------+-------------------+-----------+----------------+--------------------+------------+---------------+---------------+

| multiLink | linkInterfaceType | linkIndex | linkAdminState | linkOperationState | alarmState | remoteIp1 | remoteIp2 |

+-----------+-------------------+-----------+----------------+--------------------+------------+---------------+---------------+

| s6ad | s6ad | 0 | unlocked | enabled | none | 10.94.211.110 | 10.94.211.102 |

+-----------+-------------------+-----------+----------------+--------------------+------------+---------------+---------------+

[cmm@csr-cmm63-necc1 ~]$ cmm multiLink list --linkInterfaceType s1mme

+-----------+-------------------+-----------+----------------+--------------------+------------+--------------+-----------+

| multiLink | linkInterfaceType | linkIndex | linkAdminState | linkOperationState | alarmState | remoteIp1 | remoteIp2 |

+-----------+-------------------+-----------+----------------+--------------------+------------+--------------+-----------+

| s1mme | s1mme | 1 | unlocked | enabled | none | 10.95.80.220 | 0.0.0.0 |

+-----------+-------------------+-----------+----------------+--------------------+------------+--------------+-----------+

Check logs from /var/log/app/ directory if something is not as planned, or increase log level with logCtrl if
necessary.

11/3/2023 – TypeDocIDHere Nokia Internal Use © 2017 Nokia

19 / 19