With EFA 2.3.0 and later, you can upgrade
EFA in a multi-node, high-availability deployment.
About this task
Expect the upgrade process to take approximately 10 minutes, during which EFA services are
down but users or automated systems can continue to make calls into EFA.
The upgrade process also backs up the EFA database, so that you can easily recover
data if the upgrade fails.
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.
-
Run the deployment script.
device# source deployment.sh
The EFA Installer begins in a series of dialogs.
-
When prompted, select Upgrade or Redeploy.
-
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
sub-interface information.
The upgrade proceeds. Messages
describe the progress and indicate when EFA is deployed.
-
Verify the upgrade.
-
On the SLX device, run
the show efa
status command to see details of the installation and the
state of services.
-
From the EFA command
line, run the efactl status command to see the status of nodes, pods,
and services.
-
From the EFA command
line, run the efa status command for concise status information.