Upgrade EFA in a Single-node Deployment
Expect the upgrade process to take approximately 8 to10 minutes, during which EFA services are down.
About this task
The upgrade process automatically 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.
- Download the image (*.tar.gz).
- Verify the PGP signature as described in article 48172 on the Extreme Portal.
Untar the image.
device # tar -xvzf efa-v3.x.x.tar.gz ~/builds/3.1.0/tmp $ tar -xfz efa-3.1.0-58.tar.gz tar: z: Cannot open: No such file or directory tar: Error is not recoverable: exiting now sbr@sbr-virtual-machine ~/builds/3.1.0/tmp $
Change to the EFA directory.
device# cd efa
Run the following deployment
script without any optional parameters.
device# source deployment.sh
- When prompted, select Upgrade or Redeploy.
When prompted to configure
additional management IP networks, take one of the following steps.
The upgrade proceeds. Messages summarize your selections, describe the progress, and indicate when EFA is deployed.
- Select Yes and
then provide the following information when prompted. Repeat as often as
- 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.
- An IPv6 address is optional, but an IPv4 address is mandatory.
- Select No to ignore this optional step or when you have finished entering sub-interface information.
- Select Yes and then provide the following information when prompted. Repeat as often as necessary.
Verify the upgrade.
- From the EFA command line, run the sudo efactl status command to see the status of nodes, pods, and services.
- Run the efa status command for concise status information.