Migrate XCO from a Single-Node to a Multi-Node Deployment using Interactive Mode

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

About this task

Follow this procedure to upgrade XCO from a single-node to a multi-node deployment using interactive mode.

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

To support dual stack IP mode, the XCO management Interface must have both IPv4 and IPv6 addresses configured. When creating a sub-interface, an IPv4 address is required and an IPv6 address is optional.

1. Download the image (*.tar.gz).
2. Verify the PGP signature as described in article 48172 on the Extreme Portal.
3. Untar the image.
   

   device# tar -xvzf efa-v3.x.x.tar.gz

4. Change to the XCO directory.
   

   device# cd efa

5. Run the deployment script.
   

   device# source deployment.sh

   The XCO Installer begins in a series of dialogs.

6. When prompted, select Multi-node deployment and OK.
   

   Tip

   Use arrow keys to move between options. Press the space bar to select an option.
7. When prompted, select the IP mode (IPv4 single stack, or Dual ip-stack). Then select OK.
   

   Tip

   • Use arrow keys to move between options. Press the space bar to select an option.
   • Depending on the IP stack selection, system will prompt you with appropriate IP address input.
8. When prompted, enter the peer IP address depending on the IP stack selected.
9. When prompted, enter the virtual IP address for the cluster.
10. 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.
11. 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.
12. When prompted to configure additional management IP networks, take one of the following steps.
    You can add only one management IP network during upgrade. After the upgrade, you can add more than one management IP network.

    • 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 4090.
      • 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.
13. When prompted to configure additional management IP network routes, take one of the following steps.
    • 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, including when deployment is complete.
14. Verify the upgrade.
    1. (If applicable) On the SLX device, run the show efa status command to see details of the installation and the state of services.
    2. From the XCO command line, run the sudo efactl status command to see the status of nodes, pods, and services.
    3. From the XCO command line, run the efa status command to ensure that all nodes are up.