TPVM Upgrade Workflow Dependencies

Before you start the TPVM upgrade, review the TPVM configuration and registration dependencies.

TPVM Configuration Persistence

The TPVM running configuration and operational data (including the TPVM image version and TPVM IP address) from the SLX device continue to exist in the XCO DB. The following table describes the TPVM configurations present in the XCO DB.

TPVM Config SLX Command Execution Stage Type Value Description
auto-boot Install only Boolean Exists or does not exist Must always be enabled for an XCO TPVM.
password Pre-start only String An encoded non-clear text password string. If does not exist then default is “password”. Extreme user password is not a clear-text in the running-config. The encoded password string will still configure the SLX TPVM properly. If no password is set then default “password” is used.

Interface management

  • ip
  • gw
 Pre-start only String
  • DHCP or IPv4 address
  • IPv4 address
 If configured as DHCP, the XCO must still fetch the existing management IP and Gateway IP to validate that the TPVM IP remains the same after the upgrade or node replacement.

Interface insight

  • ipv4
  • gw

 Pre-start only String
  • DHCP or IPv4 address
  • IPv4 address
Hostname Post-start String hostname
Timezone Post-start String timezone
DNS server Post-start String FQDN or IPv4 address
NTP server Post-start String FQDN or IPv4 address

LDAP

  • Host
  • Port
  • Secure
  • basedn
  • rootdn
  • Password
 Post-start
  • FQDN or IPv4 address or IPv6 address
  • 0-65535
  • Exists or not exists
  • Base domain name
  • Root domain name
  • Root domain name password

ldap ca-cert

  • protocol
  • user
  • password
  • host
  • directory
  • filename
 Post-start String
  • scp
  • Username
  • Password
  • IPv4 address
  • Directory
  • Filename
 The ca-cert for LDAP must be stored on the firmware-host and for XCO to support the node replacement. The ca-cert can also have IPv6 address.

trusted-peer

  • ip
  • password
  • sudo-user
 Post-start String
  • IPv4 address
  • Sudo user password
  • Sudo username
 Trusted-peer config exists on one of the XCO nodes. Push this config to the correct node after the upgrade.
deploy Install Boolean
  • Exist
  • Does not exist
 Installs, starts, and applies the configurations to the TPVM instance.

Device Registration Enhancements

The TPVM config information already exist in the XCO DB when a device is registered or during the initial device registration. The TPVM running-config information is read and stored during the device discovery so that user visible device registration times are not impacted. The TPVM config is fetched and stored only during initial device registration and not during subsequent device updates.

Timer-based TPVM Config Updates

A timer is set to poll daily data for any TPVM config changes for XCO HA peer managed devices.

9037728-00 RevAB