The diagnostics from all the VMs should be collected. To do this, follow instructions from RVT Diagnostics Gatherer. After generating the diagnostics, transfer it from the VMs to a local machine.
If not already done, transfer the CSAR EFIX patches onto the SIMPL VM. For each CSAR EFIX patch, run:
csar efix <node type>/<version> <path to CSAR EFIX>
<path to CSAR EFIX> is the full path to the CSAR EFIX patch.
<node type>/<version> is the downlevel unpacked CSAR located at
For example, if a ShCM CSAR is being patched by a CSAR EFIX patch called
csar efix shcm/4.0.0-14-1.0.0 my_patch.tar
If you are not sure of the exact version string to use, run
This will apply the efix patch to the the downlevel CSAR.
|The new patched CSAR is now the uplevel CSAR referenced in the following steps.|
Don’t apply the same CSAR EFIX patch to the same CSAR target more than once.
If a previous attempt to run the csar efix command failed, be sure to remove the created CSAR before re-attempting, as the
If the CSAR EFIX patch uplevel SDF was not created on the SIMPL VM, transfer the previously written CSAR EFIX patch uplevel SDF onto the SIMPL VM.
Upload the uplevel configuration for all of the node types to the CDS. This is required for the rolling upgrade using CSAR EFIX patch to complete.
|As configuration is stored against a specific version, you need to re-upload the uplevel configuration even if it is identical to the downlevel configuration.|
The uplevel version for a CSAR EFIX patch is the format
4.0.0-14-1.0.0 is the downlevel version and
patch123 is the patch version.
An in-depth description of RVT YAML configuration can be found in the Rhino VoLTE TAS Configuration and Management Guide.