TPVM Configuration Persistence

TPVM (Guest OS) instance on Bare-Metal SLX, also can be deployed using the config tpvm mode.

All the TPVM related configurations, including config deploy (this process installs and then starts a TPVM instance) is persisted in the SLX database and becomes a part of the SLX running-configuration. These persisted configuration values are then used while upgrading the installed TPVM or while RMA of the SLX device. The persisted TPVM configurations are not applied when the TPVM reboots due to reboot or power-cycle of the SLX-OS. Since these configurations are a part of the saved running configuration, they are automatically applied for the above events.

The TPVM snapshot feature allows you to take the snapshot of the TPVM instance when the TPVM is not running (STOP state). Only one snapshot can be taken at any point of time. The TPVM snapshot can be used later to revert any failure in installing TPVM or to reinstall an old version of TPVM. The snapshot image is stored at the on the SLX device folder /support/snapshots/TPVM/auto .

When upgrading an existing TPVM instance, the new TPVM image is first downloaded and installed. If TPVM configuration is persisted, it is applied on the installed TPVM. As a backup measure, a snapshot of the previous TPVM installation is taken and stored on the SLX device. The new TPVM image (debian package file) is downloaded from the following local folder /tftpboot/SWBD2900.

For TPVM Configuration Persistence, the following configurations must be applied before executing the config deploy, as these three configurations are applied to the TPVM before it is deployed.