Northbound IPv6 support

EFA 3.1.0 supports IPv6 via an additional virtual IP that is assigned during EFA installation or upgrade. Clients can make REST API calls to XCO via either an IPv4 or an IPv6 address. An IPv6 address is optional, but an IPv4 address is mandatory.

You can configure the API gateway with IPv4 and IPv6 addresses.

Note

Dual mode or IPv4 only mode is supported. TPVM does not support assigning an IPv6 address via the SLX CLI.
(Optional) Upgrades from earlier releases or from single-node to multi-node and fresh install require an IPv6 address configuration.
Single-node installation supports IP address change for both IPv4 and IPv6 addresses.
API gateway supports IPv6 virtual IP address for multi-node and single-node installation.

All the northbound CLIs, which support dual IP mode, validate IP address according to the derived mode.

For information about commands and supported parameters to configure IPv6, see ExtremeCloud Orchestrator Command Reference, 3.2.0 .

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 XCO command line, run the efactl status command to see the status of nodes, pods, and services.
Run the efa status command for concise status information.

Note

For information about upgrading XCO, see the ExtremeCloud Orchestrator Deployment Guide, 3.2.0 .

Verify the IPv6 Address

During fresh installation or upgrade, ensure that you have specified a valid IPv6 address.

When prompted, select Yes to assign an IPv6 address as a virtual IP for cluster.
Specify the virtual IPv6 address. The system validates the IPv6 address to ensure that it is not in use. If it is already in use, change the IPv6 address.