Aviatrix Controller and Gateway Software Release Notes

8.0.0 Release Notes

Release Date: 19 May 2025

Release Notes Last Updated: 30 May 2025

Corrected Issues in Aviatrix Release 8.0.0

Issue

Description

AVX-51763

Improved the gateway keepalive handling to account for scenarios where the Controller instance hangs.

AVX-53207

Fixed an issue where an Azure Account could be deleted even though the Controller-deployed Azure VNET peerings were still active.

AVX-55661

Fixed an issue where gateway initialization could fail within 900 seconds due to misconfiguration and attempts to access external networks.

AVX-56050

Fixed an issue where Azure HA Gateway creation did not use the supplied HA_EIP in Terraform, resulting in the creation of a new EIP.

AVX-57450

Fixed an issue where WebGroups in firewall rules could not be used in conjunction with Custom SNAT configurations on a gateway.

AVX-58660

Corrected the Terraform import ID format for aviatrix_edge_platform_device_onboarding.

AVX-59226

Resolved an issue where applying a DNAT rule on a spoke gateway did not take effect, preventing access to workloads using the DNAT IP.

AVX-59416

Addressed an issue where resizing two Spoke VPCs with fast keepalive using CoPilot caused an extended traffic outage. This issue occurred during sequential resize operations on multiple spoke gateways.

AVX-60068

Changed the tunnel status email notification logic to be based on the combined status of tunnel endpoints. Previously, notifications were only sent when the updated statuses of the two endpoints differed, which could cause missed alerts. This change ensures more accurate notifications by reflecting the actual tunnel status.

AVX-60598

Addressed potential disk space issues caused by persistent log files from auditd.

AVX-60616

Corrected the tunnel source and destination in syslog messages and email notifications to avoid confusion and difficulty in matching Up and Down events.

AVX-60722

Resolved an issue where stale route entries in AWS TGW were not properly cleared after custom route advertisements were removed.

AVX-61070

When Aviatrix releases new gateway images for OCI Gov, there is typically a delay in publishing to the OCI Marketplace due to cloud service provider timelines. This means that 8.0 image will not be available right away in OCI Gov. Previously, after the image was published to the marketplace, a manual update was required to enable gateway launches with the new image. With this release, that manual step is no longer necessary—gateways can now automatically launch with the updated image once it becomes available in the OCI Marketplace. This is applicable for 7.2 images. Please note that the OCI Gov image publishing timeline itself remains unchanged.

AVX-61310

In an Aviatrix multi-transit design with Transit Peering, where one of the Transit Gateways has BGP S2C enabled and learns a default route (0.0.0.0/0), an issue occurs following a controller upgrade where incorrect metrics are applied to PeerS2c routes.

AVX-61396

Resolved an issue where Edge as a Spoke (EaS) did not install all ECMP routes for prefixes learned from an attached transit with an external connection.

AVX-61401

Resolved an issue where VPN connectivity using Okta integration failed post-upgrade due to signature verification errors. Signature verification now functions correctly.

AVX-61404

Resolved an issue where Aviatrix incorrectly added RFC1918 rules to all Spoke VCN Security Lists, including application subnets. RFC1918 rules are now only applied to gateway subnets.

AVX-61702

Resolved an issue where Azure gateway image upgrades failed when customer-provided public IPs were used. The Controller was expecting a specific naming convention (av-ip-[gateway-name]) and could not locate custom-named IPs, resulting in upgrade errors. The upgrade logic has been fixed to support any naming convention for public IPs.

AVX-61793

Resolved an issue where Transit Edge could not add a secondary IP and did not support removing the underlay configuration.

AVX-61803

Fixed an issue where the Controller did not correctly tag resources created through CFT and Lambda. It now tags all associated resources, including Lambda functions, Lambda roles, Launch Templates, Auto Scaling Groups, and SNS topics.

AVX-61981

When using RFC6598 Shared Address Space (100.64.0.0/10) in VPC/VNet CIDRs, traffic from these addresses to the public internet may have been incorrectly matched by the Public Internet security group. This could result in 100.64.0.0/10 being mistakenly classified as internet traffic. The 100.64.0.0/10 is commonly used for Kubernetes deployments. The Public Internet security group CIDR ranges have been updated to correctly exclude the shared address space. This enhancement improves the Kubernetes experience.

AVX-62067

The following issue has been fixed in this release.

This fix also requires an image upgrade of the Transit gateway.

Aviatrix Transit Gateways with large number of tunnels and running for a long time could encounter an issue where in the IPSec process becomes unresponsive leading to all IPsec tunnels going into a DOWN state. The cause of this is an internal counter reaching its maximum value and overflowing. To recover, the transit gateway needs to be rebooted.

While it is not possible to specify the exact number of tunnels and length of time it would take for the internal counter to overflow, the few customers who encountered this issue had greater than 800 ipsec tunnels on the transit gateway and took three to four months to encounter this issue. The number of ipsec tunnels on the gateway can be seen from Copilot UI under Diagnostics > Cloud Routes > Gateway Routes.

AVX-62269

Fixed an issue where GRPC traffic could be dropped when routed through Distributed Cloud Firewall (DCF) web filters using SNI-based web groups.

The fix improves support for HTTP/2-based traffic in scenarios where only H2 is present in the ALPN list, resolving a limitation in the Traffic Server tunneling logic.

AVX-62619

Fixed an issue where Aviatrix Gateways could experience memory buildup and restarts during prolonged Layer 7 (L7) traffic. The system now properly clears outdated web filter data to prevent excessive memory usage.

AVX-62795

Fixed an issue where rules using a SmartGroup were configured on both gateways when the SmartGroup included GCP cloud resources such as virtual machines with overlapping IP addresses. This caused unexpected policy enforcement on gateways where the rules should not apply.

Known Issues in Aviatrix Release 8.0.0

Issue

Description

AVX-58696

TCP MSS clamping is not supported on Standalone Gateways in Release 7.1 and later.

AVX-59376

When using Controller High Availability (HA) with Controllers version 8.0 and later, the standby Controller will fail to launch correctly. This is because the HA mechanism relies on a fixed software version specified in the Auto Scaling Group (ASG) launch template, but with Controllers version 8.0 and later now require the version to be passed dynamically through cloud-init during instance creation.

This issue occurs only in environments that use:

  • Controller HA for with Controllers version 8.0 and later

  • AWS Auto Scaling Group (ASG) launch templates

  • The default CloudFormation HA deployment method

Workaround: Use the new CloudFormation template to enable AWS Controller High Availability. This template supports dynamic version injection and restores compatibility with Controllers version 8.0 and later in supported regions. For versions 7.x and earlier, use the existing CloudFormation script (without the v3 suffix).

Note: This solution is not available in AWS regions that do not support Lambda Function URLs.

AVX-61355

Azure Standard_B1ms SNAT-enabled Egress Spoke Gateways may experience significant throughput drops under high connection loads. This limitation is caused by the Azure Standard_B1ms instance type, which has limited compute and network resources.

Affected Scenario:

  • SNAT-enabled Egress Spoke Gateways using Azure Standard_B1ms under high connection loads.

Workaround:

Upsize the Spoke Gateway to a larger Azure instance type for workloads that require more than 10K concurrent connections or consistent network throughput.

AVX-62011

Auto migration will not work from 7.2 to 8.0 when proxy is enabled. You must use a manual backup and restore process to perform the upgrade. Follow the steps below to back up and restore during the upgrade:

  1. If your Controller software version is 7.2.5012 or older, upgrade both the Controller and Gateways to the latest 7.2 build.

  2. Delete the proxy configuration from Controller UI > Settings > Advanced > Proxy.

  3. Back up the Controller from Controller UI > Settings > Maintenance > Backup & Restore > Backup.

  4. Shut down the old Controller.

  5. Launch the new 8.0 Controller and transfer the EIP.

  6. Once the 8.0 Controller is up, restore the Controller using the backup config from Controller UI > Settings > Maintenance > Backup & Restore > Restore.

  7. Add back the proxy configuration from Controller UI > Settings > Advanced > Proxy.

  8. Software upgrade the Gateways from version 7.2 to 8.0.

AVX-62147

The Controller auto-migration and Gateway upgrade features do not function properly when the Aviatrix Controller has proxy settings enabled. In such environments, migration may fail, and you must follow a manual backup and restore process instead of using the standard auto-migration workflow. This limitation is due to current backend behavior that does not support migration through proxy-enabled setups.

Affected Scenario:

  • Controller and Gateway upgrades using auto-migration in environments where proxy settings are enabled on the Aviatrix Controller

Check Whether You Are Affected:

  • In Controller UI: Go to Settings > Advanced > Proxy

  • In CoPilot UI: Go to Settings > Configuration > Private Mode > Proxy Servers

If proxy configurations are present in either location, your deployment is affected.

Workaround:

Follow the manual backup and restore steps below to upgrade the Aviatrix Controller and Gateways:

  1. If the Controller is running version 7.2.5012 or earlier, upgrade to the latest 7.2 build first.

  2. Delete the proxy configuration in the Controller UI.

  3. Back up the Controller from Settings > Maintenance > Backup & Restore > Backup in the CoPilot UI.

  4. Shut down the old Controller.

  5. Launch a new Controller with version 8.0 and reassign the EIP.

  6. Restore the backup in the new Controller.

  7. Reconfigure the proxy settings.

  8. Upgrade the Gateways from version 7.2 to 8.0.

    A maintenance window is recommended for this manual upgrade, as it involves Controller downtime and multiple steps.

AVX-62230

When upgrading Aviatrix Gateways from version 7.2.x to 8.0.0 with TLS decryption enabled in Distributed Cloud Firewall (DCF), the Gateway automatically regenerates its TLS decryption certificate authority (CA). Because each Gateway maintains its own unique CA for security, the regenerated CA no longer matches the CA previously trusted by clients.

As a result, you may experience the following issues after the upgrade:

  • Failed TLS connections for decrypted traffic

  • Certificate trust errors in browsers or applications

  • Traffic disruption for services that rely on TLS inspection

Affected Scenario:

  • Gateways with TLS decryption enabled in DCF being upgraded from 7.2.x to 8.0.0

Workaround:

  1. Before the Gateway upgrade, export the existing TLS decryption CA certificate from the Gateway.

  2. After the Gateway upgrade, re-import the new CA certificate into client trust stores to restore trust and resume decrypted connections.

AVX-62299

When upgrading from Controller version 7.1 to 7.2 or 8.0, Spoke Gateways with routing through a Public Subnet Filtering (PSF) Gateway may fail to upgrade and become unreachable if the PSF Gateway has not been upgraded first. This issue affects AWS environments where Spoke Gateway route tables are configured to point to a PSF Gateway.

To avoid this issue, follow the correct upgrade sequence:

  1. Upgrade the PSF Gateway first.

  2. Wait for the PSF Gateway upgrade to complete successfully.

  3. Then upgrade the dependent Spoke Gateways.

AVX-62506

During a gateway software upgrade, traffic matching DCF WebGroup rules may be briefly dropped during the upgrade. This impacts both Layer 7 (HTTP/HTTPS) and Layer 4 traffic and occurs across all supported cloud providers (AWS, Azure, and GCP). The disruption typically lasts a few seconds but may vary depending on gateway load and policy complexity.

Workaround:

None

Recommendations:

  • Schedule gateway upgrades during maintenance windows or low-traffic periods.

  • Use HA deployments and upgrade gateways one at a time in HA pairs.

  • Monitor logs for “Failed to load policy” messages to confirm when policies are reloaded.

AVX-62542

In environments where Distributed Cloud Firewall (DCF) and customized SNAT are used together, DCF rules may fail to match traffic correctly when the same SmartGroups are specified in both the source and destination fields. This is because the system does not account for the translated source address during rule evaluation.

As a result, traffic may be unintentionally blocked by the DefaultDenyAll rule, and policies may not apply as expected—particularly in cross-cloud or cross-region scenarios.

Affected Configurations:

  • Customized SNAT (not Single IP SNAT) configured on gateways

  • DCF rules with overlapping SmartGroups in source and destination

  • Environments involving SNAT-translated traffic

Workaround:

In earlier versions, avoid using 0.0.0.0/0 as the destination in SNAT rules. Instead, specify only the required destination CIDRs.

AVX-62636

Distributed Cloud Firewall (DCF) is not officially supported on Edge gateways. Although DCF rules may appear to be deployed to Edge gateways, they are not fully validated and may not function correctly, especially in environments using NAT for overlapping IP address spaces.

DCF rules pushed to Edge gateways may not account for NAT translations, leading to incorrect rule behavior and potential traffic filtering issues.

Affected Deployments:

  • Edge gateways with DCF rules applied

  • Environments using NAT to manage overlapping IP address spaces

  • Traffic flows between cloud resources and Edge sites with DCF enforcement

Workaround:

  • Avoid applying DCF rules to Edge gateways in environments with NAT or overlapping IP ranges.

  • Explicitly exclude Edge from DCF deployment by using the following Provider Deployment API:

POST /v2.5/api/microseg/deploy-policy
{
  "providers": ["AWS", "AZURE", "GCP"]  // Include all desired cloud providers EXCEPT "EDGE"
}

AVX-62712

When recreating a policy-based Site-to-Cloud (S2C) VPN connection after deleting a previous one with the same remote CIDR, the system may incorrectly report a CIDR overlap error, even though the original connection has been removed. This occurs because the system does not fully clean up the remote CIDR information, causing it to believe the CIDR is still in use.

Affected Scenario:

  • Recreating a policy-based Site-to-Cloud VPN connection using the same remote CIDR after deletion, in either of the following cases:

    • The deleted connection was a route-based S2C connection on a gateway that still has other S2C connections.

    • The deleted connection was a policy-based S2C connection.

Workaround:

Contact Aviatrix Support to manually clear the cached CIDR information.

AVX-62719

The Distributed Cloud Firewall (DCF) policy writer writes approximately 40KB of data per gateway during each configuration snapshot, regardless of whether there are policy changes. In large deployments, this results in frequent and unnecessary write operations to the controller database.

Affected Scenario: - DCF enabled across many gateways - Frequent configuration snapshots (triggered automatically or during updates)

Impact: Increased system load and database write activity, which may affect controller performance and stability in large-scale environments.

Workaround:

There is no direct workaround at this time. Users operating at scale should monitor controller resource usage closely. Aviatrix is actively working to reduce unnecessary write operations in a future update. If performance issues are observed, contact Aviatrix Support for evaluation and potential tuning options.

AVX-63175

In Aviatrix Controller version 8.0, Edge Gateway version numbers may be incorrectly updated in the Controller UI after the gateway comes back online from a down state. This occurs even when no new software installation has taken place.

Instead of preserving the actual version running on the Edge Gateway, the Controller may incorrectly overwrite it with its own version. This can lead to confusion during troubleshooting, upgrade planning, or compliance checks.

Affected Environments:

  • All Edge Gateway platforms, including Equinix Network Edge, AEP appliances, and other supported Edge deployments

  • The issue occurs whenever an Edge Gateway transitions from a "down" to "up" state for any reason other than initial installation (for example, reboot, network disruption, or manual restart)

Workaround:

  • Maintain a separate record of installed Gateway versions outside the Controller

  • Use the Edge Gateway’s local console or logs to verify the current version when planning upgrades or diagnosing issues

Note:

This issue only affects Edge Gateways. Cloud provider (CSP) Gateways in AWS, Azure, GCP, or OCI are not affected.

AVX-63224

In Controller release 8.0, gateway software upgrades take longer to complete compared to earlier versions. On average, the upgrade rate drops from approximately 14 gateways per minute in version 7.2 to approximately 11 gateways per minute in 8.0, which is an increase of about 20% in execution time.

Affected Scenarios:

  • Upgrading from version 7.2.x to 8.0.x

  • Upgrading between 8.0.x versions

Impact:

Only the upgrade duration is affected. Gateway functionality remains unaffected after a successful upgrade.

Recommendations:

  • Allocate approximately 20% more time for gateway upgrades.

  • For large environments (for example, 1,000+ gateways), plan for 90–120 minutes of upgrade time.

  • Schedule upgrades during maintenance windows to accommodate the longer duration.

AVX-63334

Aviatrix Edge Gateways deployed on Equinix Network Edge and certain VMware environments may experience issues with root disk resizing during initial setup. The root filesystem might not expand to utilize the full allocated disk space. This can prevent essential cloud-init modules from executing properly.

Affected Versions:

  • Aviatrix Controller 7.1.4191 with Edge Gateway image avx-gateway-avx-g3-202407091338

  • All Edge deployments on Equinix Network Edge and specific VMware configurations

Workaround:

Customers running Aviatrix Edge Gateways on Equinix Edge or VMware environments with version 7.1.4191 should contact Aviatrix Support for assistance.

AVX-63816

In versions prior to 8.0.0, the Public Internet SmartGroup includes the RFC6598 Shared Address Space (100.64.0.0/10). Starting in version 8.0.0, this range is excluded from new installations to improve Layer 7 (L7) traffic inspection and policy enforcement.

However, during upgrades to 8.0.0, the existing configuration is retained, and the 100.64.0.0/10 range is not automatically removed.

Impact:

  • Traffic from 100.64.0.0/10 (commonly used by Kubernetes) may bypass L7 inspection

  • Firewall traffic statistics may be incomplete

  • Distributed Cloud Firewall (DCF) policy enforcement may not behave as expected

Workaround:

  • Clone the existing Public Internet SmartGroup

  • Remove 100.64.0.0/10 from the cloned group

  • Update your policies to use the custom SmartGroup

Recommendation:

After upgrading to version 8.0.0, review your SmartGroup configuration if your deployment uses the 100.64.0.0/10 range in DCF rules.

AVX-63846

In the CoPilot UI, Groups > SmartGroups and Groups > ExternalGroups with multiple filters may not appear as originally configured after being saved. This issue occurs when creating groups with multiple sets of any resource type. While policy enforcement is correct, the UI may display missing or merged filter sets, leading to ambiguity and confusion during review or editing.

Affected Scenario:

  • Creating or editing SmartGroups or ExternalGroups with multiple filters applied

Workaround:

There is no workaround at this time. If possible, avoid using multiple filter sets in a single group until the issue is resolved.

AVX-63883

In Aviatrix Controller version 8.0.0, you may encounter a problem when creating or modifying Distributed Cloud Firewall (DCF) rules using either the CoPilot UI or Terraform. In the CoPilot UI, the ruleset may not display correctly and the "Commit" button may be non-functional. When using Terraform, an error may occur indicating that the DCF policy API is unavailable.

This issue prevents you from applying new or updated DCF rules, impacting network security policy management.

Affected Scenario:

  • Creating or modifying DCF rules using the CoPilot UI or Terraform

  • DCF-enabled environments where no rules are currently visible or editable

Workaround:

Contact Aviatrix Support. They can run a script to restore the missing policy list without requiring a full upgrade.

AVX-64015

Jumbo Frame support cannot be enabled on BGPoLAN (BGP over LAN) connections for AWS HPE gateways. Attempts to enable this feature may result in an error indicating that Jumbo Frames are not supported.

This affects environments where high-throughput performance is critical, such as large-scale or latency-sensitive deployments.

Affected Scenario:

  • BGPoLAN connections on AWS HPE gateways

  • Use cases that rely on Jumbo Frame support for performance optimization

Limitation:

In version 8.0.0, Jumbo Frame support can only be enabled when creating a new BGPoLAN connection on AWS HPE gateways. Editing an existing connection to enable Jumbo Frames is not supported.

Workaround:

None.

To enable Jumbo Frame support, delete the existing connection and recreate it with the setting enabled.

AVX-64196

IPSec diagnostics in the Controller UI do not display logs for non-Equinix Edge Gateways (such as AEP or self-managed Edge Gateways). When accessing the diagnostics page for these gateways, the IPSec log section may appear empty, even if IPSec tunnels are operating correctly.

This issue affects visibility into tunnel-level logs and may complicate troubleshooting efforts.

Affected Scenario:

  • Viewing IPSec diagnostic logs in the Controller UI for AEP or self-managed Edge Gateways

  • IPSec tunnels are active, but logs are not shown

Workaround:

Use tunnel status and statistics to verify IPSec operation.

Note:

This is a UI diagnostic issue only. IPSec tunnel functionality is not impacted.

AVX-64213

When deploying Edge Gateways using images g3-202504251522 and g3-202504251525, the root disk may be incorrectly sized after the VM boots and the ZTP (Zero Touch Provisioning) process runs. Even if the VM is created with a 64GB disk, the root filesystem may be limited to only 12GB.

This may lead to insufficient storage for certain workloads or during upgrades.

Affected Scenario:

  • Edge Gateway deployments using image versions g3-202504251522 or g3-202504251525

  • Environments requiring full disk capacity for normal operations or upgrades

Workaround:

Manual resizing of the root partition and filesystem is required. Please contact Aviatrix Support for assistance, as this step cannot be performed independently.

AVX-64483

Creating a Secondary or HA Transit/Spoke Edge Gateway on a Dell appliance currently fails due to a backend issue.

Workaround:

Aviatrix is actively working on a fix for this issue, which is expected to be included in a future release. In the meantime, if you need to create a Secondary or HA Transit/Spoke Edge Gateway on a Dell appliance, please contact Aviatrix Support for assistance.