Upgrade XCO in a Multi-Node Deployment using Single CLI

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

Before you begin

If you need additional management addresses, use the interactive migration path.
Ensure that the multi-node is running EFA 2.5.5 or later.
Ensure that you have completed the high-availability prerequisites in High-Availability Requirements.

About this task

Follow this procedure to upgrade XCO from a Single-Node to a Multi-Node deployment or Multi-Node to Multi-Node deployment using single CLI.

The upgrade process takes approximately 20 - 25 minutes. During the upgrade process, XCO services remain down.

The upgrade process backs up the XCO system to recover data if the upgrade fails.

Note

XCO management Interface must have both IPv4 and IPv6 addresses configured for XCO to support dual stack IP Mode. Adding IPv6 address is optional while IPv4 is mandatory during sub interface creation.

Procedure

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
```
Change to the XCO directory.
```
device# cd efa
```

Run the deployment script in non interactive mode, and insert the arguments as needed.

The following example shows two hosts sharing the virtual IP 10.25.101.100 when deploying fabric skill with no additional IP addresses:

device# source deployment.sh -I --deploy-suite fabric --deploy-type multi-node --deploy-ipmode ipv4  --virtual-ipv4 10.25.101.100 --peer-node-ip 10.25.101.102 
    Checking for EFA Stack...
    Network configuration supports ipv6. Input IP Mode will be ignored and system will be upgraded to Dual IP Mode.
    Deployment mode is upgrade
    Verifying connectivity to 10.25.101.102...
    10.25.101.102 server is reachable...
    You have entered:
    - to redeploy EFA at version 3.3.0 build 44
    - from single-node to multi-node
    - with peer 10.25.101.102
    - and with VIP 10.25.101.100
    - with IP Stack dual
    - with suites: Fabric Automation
    Verifying if monitor service is running on 10.25.101.101 10.25.101.102...
    Checking system configuration on 10.25.101.101 10.25.101.102...
    Ensuring machine clocks are in sync
    Verifying clocks are approximately in sync
    Checking default gateway reachability on all nodes...
    Completed verification of default gateway reachability on all nodes
    Ensuring peer hostnames are unique
    Verifying unique hostname between nodes
    Hostnames are unique
    Ensuring compatible OS version
    Verifying Operating System between nodes
    Operating system of all nodes are same
    Making backup

Verify the upgrade.
1. From the XCO command line, run the sudo efactl status command to see the status of nodes, pods, and services.
2. From the XCO command line, run the efa status command to ensure that status of all the nodes are up.