Planning for the procedure
Background knowledge
This procedure assumes that:
-
you are installing into an existing VMware vSphere deployment which has pre-configured networks and VLANs; this procedure does not cover setting up a VMware vSphere deployment from scratch
-
you have deployed a SIMPL VM, unpacked the CSAR, and prepared an SDF.
Reserve maintenance period
This procedure does not require a maintenance period. However, if you are integrating into a live network, we recommend that you implement measures to mitigate any unforeseen events.
Tools and access
You must have access to the SIMPL VM, and the SIMPL VM must have the right permissions on the VMware vSphere deployment.
Determine Parameter Values
In the below steps, replace parameters marked with angle brackets (such as <deployment ID>)
with values as follows.
(Replace the angle brackets as well, so that they are not included in the final command to be run.)
-
<path to SDF>: The path to the SDF file on SIMPL VM. For example,/home/admin/current-config/sdf-rvt.yaml. -
<yaml-config-file-directory>: The path to the directory file where config is located on SIMPL VM. For example,/home/admin/current-config/ -
<vm version>: The version of the VM that is deployed. For example,4.2-8-1.0.0. -
<CDS address>: The management IP address of the first TSN node. -
<CDS auth args>(authentication arguments): If your CDS has Cassandra authentication enabled, replace this with the parameters-u <username> -k <secret ID>to specify the configured Cassandra username and the secret ID of a secret containing the password for that Cassandra user. For example,./rvtconfig -c 1.2.3.4 -u cassandra-user -k cassandra-password-secret-id ….If your CDS is not using Cassandra authentication, omit these arguments.
-
<deployment ID>: The deployment ID. You can find this at the top of the SDF. -
<site ID>: A number for the site in the formDC1throughDC32. You can find this at the top of the SDF. -
<site name>: The name of the site managed by a csar command. This is required by somecsarcommands when there are multiple sites defined by a single SDF file:deploy,delete,update, andredeploy. When this optional parameter is skipped, the csar command is applied to VMs from all the sites defined on the SDF file. -
<any TSN IP>: The management IP address of any TSN node.
Method of procedure
|
Refer to the SIMPL VM Documentation for details on the commands mentioned in the procedure. |
Step 1 - Validate MMT GSM RVT configuration
Validate the configuration for the MMT GSM nodes to ensure that each MMT GSM node can properly self-configure.
To validate the configuration after creating the YAML files, run
rvtconfig validate -t mmt-gsm -i <yaml-config-file-directory>
on the SIMPL VM from the resources subdirectory of the MMT GSM CSAR.
Step 2 - Upload MMT GSM RVT configuration
Upload the configuration for the MMT GSM nodes to the CDS. This will enable each MMT GSM node to self-configure when they are deployed in the next step.
To upload configuration after creating the YAML files and validating them as described above, run
rvtconfig upload-config -c <CDS address> <CDS auth args> -t mmt-gsm -i <yaml-config-file-directory> (--vm-version-source this-rvtconfig | --vm-version <vm version>)
on the SIMPL VM from the resources subdirectory of the MMT GSM CSAR.
See Example configuration YAML files for example configuration files.
An in-depth description of RVT YAML configuration can be found in the Rhino VoLTE TAS Configuration and Management Guide.
Step 3 - Deploy the OVA
Run csar deploy --vnf mmt-gsm --sdf <path to SDF> --sites <site name>.
This will validate the SDF, and generate the terraform template. After successful validation, this will upload the image, and deploy the number of MMT GSM nodes specified in the SDF.
|
Only one node type should be deployed at the same time. I.e. when deploying these MMT GSM nodes, don’t deploy other node types at the same time in parallel. |
Backout procedure
To delete the deployed VMs, run
csar delete --vnf mmt-gsm --sdf <path to SDF> --sites <site name>.
You must also delete the MDM state for each VM. To do this, you must first SSH into one of the MDM VMs.
-
Get the instance IDs by running:
mdmhelper instance list --concise. That will provide the <VM instance ID> of each VM that is in the deployment. -
Then for each MMT GSM VM, run the following command:
mdm-remove-vnfcis <VM instance ID>. Repeat using the instance ID of each managed VM that has been destroyed. -
Run the following command to verify that the configuration has been removed from MDM’s database, specifying the destroyed VM’s instance ID:
mdmhelper instance get <VM instance ID>. This should returnInstance with id <VM instance ID> not found. -
Run the following command to verify that the VMs have been removed from MDM:
mdmhelper instance list --concise. Verify that the VMs you deleted are no longer listed. -
You may now log out of the MDM VM.
You must also delete state for this node type and version from the CDS prior to deploying the VMs again.
To delete the state, run
rvtconfig delete-node-type-version --cassandra-contact-point <any TSN IP> --deployment-id <deployment ID>.
--site-id <site ID> --t mmt-gsm (--ssh-key SSH_KEY | --ssh-key-secret-id SSH_KEY_SECRET_ID)
(--vm-version-source [this-vm | this-rvtconfig] | --vm-version <vm version>)
