Multiple-Version Upgrade for Controller and Gateways
The multiple-version upgrade refers to:
Upgrade Controller and Gateways from one version to another, where there are multiple intermediate versions between the current version and the target version.
When upgrading from one minor version of a major release to another or from one major release to another, it is necessary to follow a sequential upgrade process and cannot skip over intermediate release versions.
For single-version Controller and Gateway upgrade, see Single-Version Upgrade for Controller and Gateways
For upgrading Controller and Gateways for the latest Aviatrix supported images, see Upgrade your Controller and Gateways to the Latest Aviatrix Supported Images (AWS and Azure Only)
Before Upgrade
Before you upgrade your Controller and Gateways, it is highly recommend to 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.
Perform the Pre-upgrade Tasks
Check and perform all the pre-upgrade tasks. See details in Pre-upgrade Tasks for Controller and Gateways.
Check the Upgrade Checklist
Perform all the items listed in the upgrade checklist. See details in Upgrade Checklist of the Controller and Gateway Upgrade
Check your Controller Version and Determine the Upgrade Path
You need to identify your current Controller release version and the major release version that you want to upgrade to.
Determine the Controller version you are running:
-
On CoPilot UI, click the caret (^) symbol on the top left.
-
Look for the version number under Aviatrix Controller.
If you are currently using Aviatrix Controller version 6.5 or earlier, it is strongly recommended to open a ticket with Aviatrix Support before proceeding with any upgrade. This is necessary to ensure a thorough review and redesign of your network architecture to align with the latest best practices and supported versions. |
Determine your Controller License and Image
Log into your cloud provider to check your license information and Controller image information.
-
If your Controller is not using the Bring Your Own License (BYOL) license or your Controller image is 2021 or earlier:
-
Perform Controller Migration to use the latest BYOL Controller image.
-
If your Controller did not have a fixed EIP, go to Controller UI > SETTINGS > CoPilot Association to update your CoPilot Association to point to the new EIP of the Controller.
-
-
If your Controller is already using a BYOL license but does not have an ABUP (Aviatrix Billing and Usage Platform) customer ID:
-
Subscribe to the correct Aviatrix license:
-
In AWS, subscribe to the Aviatrix Cloud Network License Service subscription offer license.
-
In Azure, GCP, and OCI, subscribe to the Aviatrix Secure Networking Platform 2208-Universal 24x7 Support subscription offer license.
-
-
Apply your new Customer ID on the Controller UI > SETTINGS > License page.
-
Upgrade Controller and Gateways
Follow the outlined steps below to upgrade your Controller and Gateways basing on your start version and end version.
For the detailed upgrade procedure for a single-version upgrade, see Single-Version Upgrade for Controller and Gateways.
Multiple-Version Upgrade Starting from Version 6.5
Upgrade Start Version | Upgrade End Version | Upgrade Steps |
---|---|---|
6.5 |
6.8 |
|
6.9 |
|
|
7.0 |
|
|
7.1 |
|
|
Gateway Images that Do not Require Additional Image Upgrade
The following table lists the images that do not require for additional image upgrade. If you have one of the gateway images listed in the following table, you do not need to perform an additional image upgrade.
Upgrade-to Version | AWS | Azure | GCP | OCI | Alibaba |
---|---|---|---|---|---|
6.6 |
hvm-cloudx-aws-031222 |
aviatrix-companion-gateway-v8 |
gw-base-04102021 |
aviatrix_gateway_54_1042_20210426_patched_v2 |
hvm-cloudx-aliyun-122520 |
6.7 |
hvm-cloudx-aws-031722 |
aviatrix-companion-gateway-v10u |
gw-base-04092022 |
aviatrix_gateway_54_20220323 |
hvm-cloudx-aliyun-042322 |
6.8 |
hvm-cloudx-aws-080322 |
aviatrix-companion-gateway-v13u |
gw-base-08032022 |
aviatrix_gateway_54_20220323 |
hvm-cloudx-aliyun-062422 |
6.9 |
hvm-cloudx-aws-030923 |
aviatrix-companion-gateway-v15u-6-9 |
gw-base-08032022 |
aviatrix_gateway_54_20220323 |
hvm-cloudx-aliyun-062422 |
7.0 |
hvm-cloudx-aws-061023 |
aviatrix-companion-gateway-v16u |
gw-base-06062023 |
avx-gateway-oci-20230607 |
hvm-cloudx-aliyun-020623 |
7.1 |
hvm-cloudx-aws-061023 |
aviatrix-companion-gateway-v16u |
gw-base-06062023 |
avx-gateway-oci-20230607 |
hvm-cloudx-aliyun-021623 |
Multiple-Version Upgrade Starting from Version 6.6
Upgrade Start Version | Upgrade End Version | Upgrade Steps |
---|---|---|
6.6 |
6.8 |
|
6.9 |
|
|
7.0 |
|
|
7.1 |
|
|
Multiple-Version Upgrade Starting from Version 6.7
Upgrade Start Version | Upgrade End Version | Upgrade Steps |
---|---|---|
6.7 |
6.8 |
|
6.9 |
|
|
7.0 |
|
|
7.1 |
|
|
Multiple-Version Upgrade Starting from Version 6.8
Upgrade Start Version | Upgrade End Version | Upgrade Steps |
---|---|---|
6.8 |
6.9 |
|
7.0 |
|
|
7.1 |
|
|
Multiple-Version Upgrade Starting from Version 6.9
Upgrade Start Version | Upgrade End Version | Upgrade Steps |
---|---|---|
6.9 |
7.0 |
|
7.1 |
|
|
Multiple-Version Upgrade Starting from Version 7.0
Upgrade Start Version | Upgrade End Version | Upgrade Steps |
---|---|---|
7.0 |
7.1 |
|
|
Verify your Upgrade
After performing an upgrade, it is important to verify your upgrade status.