You can upgrade a multi-node deployment
of XCO on TPVM (Third-Party Virtual Machine).
Before you begin
Ensure that the
XCO tar file is available on the
/efaboot
partition of the SLX device.
About this task
XCO on TPVM is supported only on
the platforms described in Supported Platforms and Deployment Models for Fabric Skill. By default, XCO is installed in secure
mode.
Installing XCO on a TPVM in a two-node deployment takes approximately 20 minutes.
Procedure
-
Enter SLX Linux mode.
device# start-shell
# cd /efaboot
-
Copy the XCO tar file to the SLX device.
# scp efa-x.x.x.tar.gz
Note
From SLX version 20.4.1 and above, a new
install or upgrade of
XCO on TPVM in a multi-node
deployment displays the following warning
banner:
*****************************************************************
* ! ! ! WARNING ! ! ! *
* Proceeding with Extreme Fabric Automation deployment *
* 1. Do not reboot device(s) or TPVM(s) *
* 2. Do not toggle management port on device(s) or TPVM(s) *
* 3. Avoid CTRL+C on the installer window *
**********************************************************************
-
Deploy XCO on TPVM from the SLX
command line.
device# efa deploy
Starting "efa deploy", DO NOT hit CTRL+C
Step 1: Checking if TPVM is deployed ...
Step 2: Get IP Addressed assigned to TPVM to deploy EFA
IP Address of the TPVM 10.x.x.x
Step 3: Checking for EFA packages in /efaboot directory
Step 4: Deploying EFA package efa-2.x.x.tar.gz on 10.x.x.x
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. Press 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 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 IPv4 or IPv6 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.
- An IPv6 address is optional, but an IPv4 address is
mandatory.
- 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.
Note
XCO management Interface must have both IPv4 and IPv6 address configured.
Adding IPv6 address is optional while IPv4 is mandatory during sub
interface creation.
- 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.
As the installation proceeds,
messages display showing the installation progress.
-
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 sudo efactl
status command to see the status of nodes, pods, and
services.
-
From the XCO command line, run the efa status
command for concise status information.