Rhino VoLTE TAS VMs 4.1 :: RVT VM Install Guide (GSM)

RVT service groups

Note that whilst SDFs include all VNFCs in the deployment, this section only covers the Rhino VoLTE TAS VMs (TSN, MAG, ShCM, MMT GSM, and SMO).

Define one service group for each RVT node type (tsn, mag, shcm, mmt-gsm, or smo).

Networks for RVT service groups

See Subnets and traffic schemes.

SSH configuration

SSH authentication

See Logging in through SSH.

SIMPL VM SSH private key

For validation tests (csar validate) to succeed, you must also add a secret ID of an SSH key that SIMPL VM can use to access the VM, under the field private-key-id within the SSH section. It is not necessary to also add the public half of this key to the authorized-keys list; rvtconfig will ensure the VM is configured with the public key.

The SSH key must be in PEM format; it must not be an OpenSSH formatted key (the default format of keys created by ssh-keygen). You can create a PEM formatted SSH key pair using the command ssh-keygen -b 4096 -m PEM.

To minimize the risk of this key being compromised, we recommend making the SIMPL VM create this key for you. See Auto-creating SSH keys in the SIMPL VM Documentation for instructions on how to do this.

SSH configuration example

An example SSH section for a VNFC is shown below:

vnfcs:
- name: mag
  cluster-configuration:
    count: 3
    instances:
    - name: my-mag-1
      ssh:
        authorized-keys:
        - ssh-rsa AAAA... Bob's key
        private-key-id: simpl-vm-access-private-key-id
    ...

Product options for RVT service groups

The following is a list of RVT-specific product options in the SDF. All listed product options must be included in a product-options: → <node type> section, for example:

product-options:
  tsn:
    cds-addresses:
      - 1.2.3.4
    etc.

cds-addresses : Required by all node types. This element lists all the CDS addresses. Must be set to all the signaling IPs of the TSN nodes. These are the TSN nodes in the deployment.
secrets-private-key-id : Required by all node types. A secret ID referencing an encryption key to encrypt/decrypt passwords generated for configuration. The rvtconfig tool should be used to generate this key. More details can be found in the rvtconfig page. The same key must be used for all VMs in a deployment.
primary-user-password-id: Required for all node types. A secret ID referencing the password used to authenticate the primary user on the VMs. This password must be at least 8 characters. The corresponding entry in the secrets file should be surrounded by single quotes (''), to ensure any special characters are properly handled.
ims-domain-name : Required by MMT, SMO, MAG, and ShCM nodes. The IMS SRV domain name, for example mnc001.mcc001.3gppnetwork.org.
mmt-vnf : Required by MMT nodes. Host part of the FQDN of the MMT virtual network function, e.g. the mmt in mmt.mnc001.mcc001.3gppnetwork.org. The full FQDN consists of the mmt-vnf and ims-domain-name, This will correspond to an SRV record which resolves to the MMT nodes providing the function to the site.
atu-sti-hostname : Required by MMT nodes. The Access Transfer Update - Session Transfer Identifier (ATU-STI) hostname. See Access transfer in the Configuration and Management Guide for more details.
smo-vnf : Required by SMO node. Host part of the FQDN of the SMO virtual network function, e.g. the smo in smo.mnc001.mcc001.3gppnetwork.org. The full FQDN consists of the smo-vnf and ims-domain-name, and corresponds to an SRV record which resolves to the SMO nodes providing the function to the site.
shcm-vnf : Required by MMT, SMO, MAG, and ShCM nodes. Host part of the FQDN of the Sh Cache Microservice virtual network function, e.g. the shcm in shcm.mnc001.mcc001.3gppnetwork.org. The full FQDN consists of the shcm-vnf and ims-domain-name, and will correspond to an SRV record which resolves to the ShCM nodes providing the microservice to the site.

Previous page Next page