Upgrade EFA, SLX-OS, and TPVM Option 2

Use this upgrade option if the latest version of EFA is supported on your version of TPVM.

About this task

For more information about supported versions, see Supported Platforms and Deployment Models.

In the following procedure, SLX1 refers to the active EFA node (TPVM1). SLX2 refers to the standby EFA node (TPVM2).

Procedure

Upgrade EFA to the latest version.
1. Back up EFA.
```
efa system backup
```
2. SCP the backup file to a location outside of TPVM, such as the /efaboot partition of SLX-OS where the EFA image is kept.
3. Copy the EFA 2.5.x image to the /efaboot directory on SLX1.
4. Deploy EFA on SLX1.
```
efa deploy
```
5. When prompted, select Multi Node Build Upgrade.
Upgrade SLX-OS to the latest version.

An SLX-OS upgrade from 20.2.3x to 20.3.2x needs a full install. The procedure performs fabric-wide firmware download by staging the devices in multiple groups with no traffic disruption. Complete the following steps to download firmware on all the devices in the fabric.
1. From the EFA command line on TPVM1 (the active node), upgrade SLX2 to the latest SLX-OS version.
```
efa inventory firmware-host register --ip <fw-host-ip> 
--protocol scp --username <username> --password <password>
```
2. From the EFA command line on SLX1, upgrade SLX-OS from 20.2.3f to 20.3.2b.
```
efa inventory device firmware-download prepare add --fabric <fabric name> 
--firmware-host <fw-host-ip> --firmware-directory <fw-path>

efa inventory device firmware-download prepare list --fabric <fabric name>

efa inventory device firmware-download execute --fabric <fabric name> 

efa inventory device firmware-download show --fabric <fabric name>
```
Upgrade TPVM2 to the latest version.
Upgrade TPVM2 first, because it is in the standby node.
Note
- With SLX-OS 20.3.2a and later, TPVM configuration is persisted in subsequent SLX-OS upgrades, so you do not need to configure TPVM in these upgrades. When an SLX device that hosts TPVM is upgraded to 20.3.2a, the existing TPVM continues to run, and all TPVM parameters that were configured with the tpvm config command are converted to TPVM config block commands.
  For information on TPVM configuration block and migration details, see the Extreme SLX-OS Management Configuration Guide.
- If you deployed TPVM using SLX configuration mode (by copying a default configuration or remote configuration without TPVM config block into the SLX startup config), a reboot of the device clears the running TPVM, and the TPVM is removed from the device. To preserve the running TPVM, you must add the TPVM configuration block into the configuration file.
1. On SLX2, run the following commands.
```
device# tpvm stop
device# tpvm uninstall force
```
2. Copy the new TPVM build (replace tpvm-4.2.4.deb with tpvm-4.2.5.deb) to the /tftpboot/SWBD2900/ directory.
3. Set all TPVM2-related parameters in SLX2 config mode.
```
device# no deploy
device# auto-boot
device# ntp <ip-add>
device# hostname <unique-hostname>
device# trusted-peer ip <peer-ip> password  <password>
device# interface management ip <ip-add>/<subnet-mask> gw <gw-IP>
device# deploy
```
4. Copy the EFA 2.5.x image to the /efaboot directory on SLX1.
5. Deploy EFA on SLX1.
```
efa deploy
```
6. When prompted, select Multi Node Build Upgrade with Node Replacement.
Upgrade TPVM1 to the latest version.
1. On SLX1, run the following commands.
```
device# tpvm stop
device# tpvm uninstall force
```
2. Copy the new TPVM build (replace tpvm-4.2.4.deb with tpvm-4.2.5.deb) to the /tftpboot/SWBD2900/ directory.
3. Set all the TPVM1-related parameters in SLX1 config mode.
4. Perform a fresh installation of TPVM.
```
device# no deploy
device# auto-boot
device# ntp <ip-add>
device# hostname <unique-hostname>
device# trusted-peer ip <peer-ip> password  <password>
device# interface management ip <ip-add>/<subnet-mask> gw <gw-IP>
device# deploy
```
5. Copy the EFA 2.5.x image to the /efaboot directory on SLX2.
6. Deploy EFA on SLX2.
```
efa deploy
```
7. When prompted, select Multi Node Build Upgrade with Node Replacement.