TPVM Migration

With the introduction of the TPVM Configuration Persistence feature, the ability to persist TPVM configuration after TPVM upgrade was also introduced. The TPVM Migration feature now adds the ability to migrate the old configuration and store it automatically into SLX-OS running configuration.

This feature, introduced in SLX-OS version 20.3.2a, migrates some of the TPVM configurations made using the Privilege Execution Mode of the SLX-OS. These changes are now added to the SLX-OS's running configuration automatically.

This migration happens the first time the SLX device is upgraded to SLX-OS version 20.3.2a. This is a one time activity and this action will become obsolete in the next version.

Note

Note

No user action is required for this migration to happen.

The following table lists the various TPVM configurations and their migration status.

Configuration Migration State Notes
tpvm auto-boot Migrated
tpvm disk Not Migrated Disk configuration is not supported in the configuration mode, and therefore, not migrated.
tpvm password Migrated Only the old password is migrated. This is due to the password being encrypted and stored and it is not possible to know if the password was changed during the migration.
tpvm config ntp Migrated
tpvm config dns Migrated
tpvm config ldap Migrated Secure LDAP require certificates. It is assumed that certificates are already downloaded and installed. Certificates are not validated during this migration. A notification will be sent to the user to reconfigure LDAP certificate settings.
tpvm config hostname Migrated
tpvm config timezone Migrated
tpvm deploy <interface> allow-pwless Not Migrated This is the new default configuration and is not migrated.
tpvm deploy mgmt [ dhcp | static ] Migrated
tpvm deploy insight Not Migrated Insight interface configuration is not supported when configuring using the Privilege Execution Mode commands.
tpvm config ldap ca-cert Not Migrated
tpvm config trusted-peer Not Migrated All trusted-peer configurations are not migrated.
Note

Note

You must manually configure those parameters that were not migrated automatically to ensure that you TPVM's configuration is the same post migration.