Upgrade your Controller and Gateways to the Latest Aviatrix Supported Images (AWS and Azure Only)

This auto-upgrade process only applies to AWS and Azure. Contact Aviatrix Support if your Controller and Gateways are deployed on other cloud service provides.

For single-version Controller and Gateway upgrade, see Single-Version Upgrade for Controller and Gateways

For multi-version Controller and Gateway upgrade, see Multiple-Version Upgrade for Controller and Gateways.

This documentation aims at providing steps on upgrading your Controller and Gateways to the latest Aviatrix images.

During the upgrade, we transfer all settings from the old Controller to the new Controller, which keeps the same public IP (Elastic IP) but gets a new private IP. This change helps to maintain seamless service during the transition. After the upgrade is complete, the old Controller is stopped. Aviatrix recommends terminating the old Controller to avoid unnecessary costs.

Major Upgrade Paths for Controller and Gateways

The following table lists the upgrade paths for Controller and Gateways to the latest v7.1 of Controller and gateway release. To upgrade to v7.2 of Controller and gateway release, see Upgrade your Controller and Gateway to the latest v7.2 of software Controller and gateway release.
Controller CSP Current Version End Version Upgrade Path 3

AWS

7.0.x 1

7.1.4183 (latest image version)

7.0.x → 7.0.2239 → 7.1.4101 → 7.1.4183

  1. Perform a software upgrade from 7.0.x to 7.0.2239 of the Controller and all the gateways.

  2. Perform a software upgrade from 7.0.2239 to 7.1.4101 of the Controller and all the gateways.

  3. Perform an image upgrade from 7.1.4101 to 7.1.4183 of the Controller and all the gateways.

AWS

7.1.x 2

7.1.4183 (latest image version)

7.1.x → 7.1.4101 → 7.1.4183

  1. Perform a software upgrade from 7.1.x to 7.1.4101 of the Controller and all the gateways.

  2. Perform an image upgrade from 7.1.4101 to 7.1.4183 of the Controller and all the gateways.

AWS

7.1.3956

7.1.4183 (latest image version)

7.1.3956 → 7.1.4183

  1. Perform an image upgrade from 7.1.3956 to 7.1.4183 of the Controller and all the gateways.

AWS

7.1.3958

7.1.4183 (latest image version)

7.1.3958 → 7.1.4183

  1. Perform a software upgrade from 7.1.3958 to 7.1.4183 of the Controller and all the gateways.

AWS

7.1.4105

7.1.4183 (latest image version)

7.1.4105 → 7.1.4183

  1. Perform a software upgrade from 7.1.4105 to 7.1.4183 of the Controller and all the gateways.

Azure

7.0.x 1

7.1.4183 (latest image version)

7.0.x → 7.0.2239 → 7.1.4101 → 7.1.4183

  1. Perform a software upgrade from 7.0.x to 7.0.2239 of the Controller and all the gateways.

  2. Perform a software upgrade from 7.0.2239 to 7.1.4101 of the Controller and all the gateways.

  3. Perform an image upgrade from 7.1.4101 to 7.1.4183 of the Controller and all the gateways.

Azure

7.1.x 2

7.1.4183 (latest image version)

7.1.x → 7.1.4101 → 7.1.4183

  1. Perform a software upgrade from 7.1.x to 7.1.4101 of the Controller and all the gateways.

  2. Perform an image upgrade from 7.1.4101 to 7.1.4183 of the Controller and all the gateways.

Azure

7.1.4105

7.1.4183 (latest image version)

7.1.4105 → 7.1.4183

  1. Perform a software upgrade from 7.1.4105 to 7.1.4183 of the Controller and all the gateways.

1 7.0.x refers to any 7.0 release earlier than 7.0.2239.

2 7.1.x refers to any 7.1 release earlier than 7.1.4101.

3 The upgrade path applies to both the Controller and Gateways. Upgrade the Controller first to the desired release version. Once the Controller upgrade is successful, proceed with upgrading the Gateways.

4 If you are using a private marketplace in Azure, you must subscribe to the gateway image offer in Azure marketplace first. See Subscribing Gateway Offers to Azure Private Marketplace for Aviatrix Deployments.

Major Upgrade Steps

Aviatrix recommends performing all platform software lifecycle management tasks on the CoPilot UI. If you are not currently using CoPilot, please deploy it before proceeding with any procedures in this documentation.

The following steps summarize the major upgrade process:

  1. Perform a software upgrade of your Controller and gateways to 7.1.4101. See Upgrade of your Controller and gateways to 7.1.4101.

  1. Back up your Controller data. See Back up your Controller data.

  2. Perform a Controller Image Upgrade Dry Run to check for potential errors.

  3. Resolve any potential errors according to the provided solutions.

  4. Perform an Image Upgrade of your Controller to the latest Aviatrix supported image. See Image Upgrade of your Controller to 7.1.4183.

    If your Controller has been upgraded to 7.1.3958 or later, you can perform a software upgrade to 7.1.4183 for the latest software version.

  5. Verify your Controller Upgrade Status.

  6. Perform an Image Upgrade of all your gateways to the latest Aviatrix supported image. See Image Upgrade of your Gateways to 7.1.4183.

    If your gateways have been upgraded to 7.1.3958 or later, you can perform a software upgrade to 7.1.4183 for the latest software version.

  7. Verify your Gateway Upgrade Status.

Prepare for Upgrading your Controller and Gateways to the Latest Aviatrix Supported Images

If you plan to deploy a new Controller from the AWS marketplace or Azure marketplace before performing the upgrade, make sure to select the correct Controller version. We recommend using only 7.1.4183 as it uses the latest operating system image.

For AWS

  • To deploy Controller version 7.1.4183:

    1. From the AWS Marketplace, sign up for the Aviatrix Cloud Network License Service if you do not have an Aviatrix license.

    2. Subscribe to Aviatrix Cloud Network Controller.

    3. Select g3-202407091338 as the version.

  • To deploy Controller version 7.1.4101:

    1. From the AWS Marketplace, sign up for the Aviatrix Cloud Network License Service if you do not have an Aviatrix license.

    2. Subscribe to Aviatrix Cloud Network Controller.

    3. Select 05302023 as the version from the drop list.

For Azure

  • To deploy Controller version 7.1.4183:

    1. From the Azure Marketplace, sign up for the Aviatrix Cloud Network License Service if you do not have an Aviatrix license.

    2. Subscribe to Aviatrix Cloud Network Controller.

  • To deploy Controller version 7.1.4101 :

    1. From the Azure Marketplace, sign up for the Aviatrix Cloud Network License Service if you do not have an Aviatrix license.

    2. Subscribe to Aviatrix Secure Networking Platform BYOL.

Check the following prerequisites before upgrading your Controller.

  • Make sure your Controller and CoPilot are deployed on AWS or Azure. For deployments on other cloud service providers, contact Aviatrix Support to help you perform the upgrade.

  • Check your Controller version to ensure it meets the version requirements. Perform a software upgrade of your Controller to make sure the Controller version is 7.1.4101. See Upgrade your Controller to 7.1.4101 for more details.

  • Ensure that your gateways are in 7.1.4101 version. Upgrade any gateways that are not in 7.1.4101 to 7.1.4101. See Upgrade your Gateways to 7.1.4101 for details.

  • Make sure you have installed the latest CoPilot version (>=4.11.1). See Deploy CoPilot.

  • Make sure that you have subscribed to the Required Aviatrix License and Marketplace Offers and have a valid customer id (license) issued by the Aviatrix Cloud Network License Service. For legacy licenses/listings below, contact Aviatrix Support for the upgrade assitance.

    • Aviatrix Secure Networking Platform - Enterprise Subscription

    • Aviatrix Secure Networking Platform Metered 2208 - Copilot & 24x7 Support

    • Aviatrix Secure Networking Platform PAYG - Metered

  • Make sure no CloudN gateways are attached to your Controller. If there are any CloudN gateways attached to your Controller, you will first need to migrate to Aviatrix Edge. Please contact Aviatrix Support.

  • Make sure you have not enabled Private Mode. If you are using the private mode, contact Aviatrix Support for the other upgrade options.

  • For Controller that is configured in HA mode, please disable HA before the Controller upgrade. You will then need to enable HA mode after the Controller upgrade. See Controller High Availability in AWS for details.

Before your Controller and Gateway Upgrade

Ensure you complete the following before starting your Controller upgrade.

Check the General Controller and Gateway Upgrade Guidance

  • Check the General Controller and Gateways Upgrade Guidance.

  • Before proceeding with the upgrade in the production environment, perform the upgrade in a testing environment.

  • It is important to upgrade the Controller first, ensuring it is at the desired release version.

  • Once the Controller is successfully upgraded, proceed to upgrade the Gateways.

Go through Checklist of the Controller and Gateway Upgrade

  1. Go through the checklist of Controller and Gateway upgrade. See details in Upgrade Checklist of the Controller and Gateway Upgrade.

  2. Make sure you have performed all the pre-upgrade tasks of the Controller and Gateway Upgrade.

Upgrade Controller and Gateways to the Latest Aviatrix Supported Images(AWS and Azure Only)

To upgrade Controller and gateways for the latest Aviatrix Supported Images:

  1. Upgrade your Controller for the latest Aviatrix Supported Images (AWS and Azure Only)

  2. Upgrade your Gateways for the latest Aviatrix Supported Images (AWS and Azure Only)

Troubleshooting your Controller and Gateway Upgrade

If the upgrade of your Controller fails, we will revert the Controller to its previous state.

See Troubleshooting Controller and Gateway Upgrades for the detailed troubleshooting solutions.