Mandatory YAML files

The configuration process requires the following YAML files:

YAML file Node types

tsn-vmpool-config.yaml

TSN

snmp-config.yaml

TSN, MAG, ShCM, MMT GSM, and SMO

routing-config.yaml

TSN, MAG, ShCM, MMT GSM, and SMO

system-config.yaml

TSN, MAG, ShCM, MMT GSM, and SMO

mag-vmpool-config.yaml

MAG

bsf-config.yaml

MAG

naf-filter-config.yaml

MAG

common-config.yaml

MAG, ShCM, MMT GSM, and SMO

home-network-config.yaml

MAG, MMT GSM, and SMO

number-analysis-config.yaml

MAG and MMT GSM

sas-config.yaml

MAG, ShCM, MMT GSM, and SMO

shcm-vmpool-config.yaml

ShCM

shcm-service-config.yaml

ShCM

mmt-gsm-vmpool-config.yaml

MMT GSM

sentinel-volte-gsm-config.yaml

MMT GSM

hlr-config.yaml

MMT GSM and SMO

icscf-config.yaml

MMT GSM and SMO

smo-vmpool-config.yaml

SMO

sgc-config.yaml

SMO

sentinel-ipsmgw-config.yaml

SMO

Optional YAML files

The example files included here are "empty", showing a file which has the minimum content to make it syntactically correct, but not actually adding any configuration. If the file is not in use, you can either upload the empty example file to CDS, or simply not include the file at all in the upload.

Note
Low-level Rhino configuration override files

The files ending in *-overrides.yaml contain low-level Rhino configuration. They allow resolution of errors in the configuration generated from the other YAML files, and nonstandard behaviours. Use these files only when advised to do so by your Customer Care Representative.
YAML file Node types

mag-overrides.yaml

MAG

mag-nginx-config.yaml

MAG

shcm-overrides.yaml

ShCM

mmt-gsm-overrides.yaml

MMT GSM

smo-overrides.yaml

SMO
Previous page Next page
Rhino VoLTE TAS VMs Version 4.2