Upgrade EFA from a Single-Node to a Multi-Node Deployment

You can upgrade a single-node deployment of EFA to a multi-node deployment.

Before you begin

Ensure the single node is running EFA 2.3.0 or later. Upgrade if necessary. For more information, see Upgrade EFA in a Single-node Deployment.

Ensure you have completed the high-availability prerequisites in EFA Requirements.

About this task

Expect the upgrade process to take approximately 15 minutes, during which EFA services are down but users or automated systems can continue to make calls into EFA.

The upgrade process backs up the EFA system, so that you can easily recover data if the upgrade fails. For more information, see Recover from an Upgrade Failure.

By default, EFA is installed in secure mode. For more information about the modes, see EFA Installation Modes.

Procedure

Download the image (*.tar.gz) to a new sub-folder.
Untar the image.
```
device# tar -xfz efa-v2.x.x.tar.gz
```
Verify the PGP signature as described in article 48172 on the Extreme Portal.
Change to the EFA directory.
```
device# cd efa
```
Run the deployment script.
```
device# source deployment.sh
```
The EFA Installer begins in a series of dialogs.
When prompted, select Multi-node deployment and OK.

Tip
Use arrow keys to move between options and the space bar to select an option.
When prompted, enter the peer IP address or FQDN of the other node in the cluster.
When prompted, enter the virtual IP address for the cluster.
When prompted, enter the virtual IPv6 address for the cluster.
- Select Yes and then provide the virtual IPv6 addresses.
- Select No to ignore this optional step.
When prompted to configure additional IP addresses for a health check, take one of the following steps.
- Select Yes and then provide the IP addresses.
- Select No to ignore this optional step.
When prompted to configure additional management IP networks, take one of the following steps.
- Select Yes and then provide the following information when prompted. Repeat as often as necessary.
  - Sub-interface name, which is a unique name that contains no more than 11 characters, no white space, and no % or / characters.
  - ID of the VLAN that the management network uses to tag traffic. Valid values range from 2 through 4093.
  - IP subnet address in CIDR format. The subnet must not overlap with any IP subnet that you have already provided.
- Select No to ignore this optional step or when you have finished entering network information.
When prompted to configure additional management IP network routes, take one of the following steps.
- Select Yes and then provide the following information when prompted. Repeat as often as necessary.
  - Target network IP address in CIDR format
  - Source IP address for outbound traffic
  - Next-hop or gateway IP address through which access to the destination network is provided
- Select No to ignore this optional step or when you have finished entering route information.
The installation proceeds. Messages summarize your selections, describe the progress, and indicate when EFA is deployed.
Verify the upgrade.
1. On the SLX device, run the show efa status command to see details of the installation and the state of services.
2. From the EFA command line, run the efactl status command to see the status of nodes, pods, and services.
3. From the EFA command line, run the efa status command for concise status information.