> ## Documentation Index > Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt > Use this file to discover all available pages before exploring further. # 8.0.0 Release Notes > Release Date: 19 May 2025 Release Notes Last Updated: 25 September 2025 **Release Date:** 19 May 2025\ **Release Notes Last Updated:** 25 September 2025 ## Corrected Issues in Aviatrix Release 8.0.0 | Issue ID | 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. 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. | | AVX-66162 | Fixed an issue where DNAT and SNAT configuration updates failed on gateways with policy-based Site2Cloud tunnels. The NAT validation logic has been corrected to properly resolve interfaces, ensuring DNAT and SNAT rules can now be created, modified, or deleted through the Controller UI without errors. | ## Known Issues in Aviatrix Release 8.0.0 | Issue ID | Description | | - | - | | AVX-58696 | TCP MSS clamping is not supported on Standalone Gateways in Release 7.1 and later. | | AVX-59298 | In Aviatrix Controller 8.0 versions, when deploying Edge Spoke or Edge Transit Gateways in Megaport Virtual Edge (MVE), less than 5 VNICs can result in the gateway failing to initialize. This issue occurs because the cloud-init expects 5 interfaces.

**Workaround:** To ensure the successful deployment of Edge Spoke or Edge Transit Gateways in MVE, configure the MVE with 5 VNICs. | | 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 Gov Cloud regions. | | AVX-60731 | BGP Event Monitor on gateways may crash when receiving BGP route updates containing AS-SET or AS\_CONFED\_SET values in the AS-PATH attribute (such as \{13908,17063,...}). This occurs because the system attempts to parse AS-SET entries as individual integers, resulting in a ValueError and causing the BGP monitoring process to exit.

**Workaround:** Add a route-map on the upstream sender to strip or reject AS-SET entries. Alternatively, configure the Aviatrix gateway to reject AS-SET-containing routes manually if applicable.

**Impact:** BGP monitoring service crash. Affected routes are not processed or sent to the Controller. No BGP routes appear in /avx-northbound-v1/best\_routes in etcd. Systemd logs may show "avx-bgpd-event-mon.service: Main process exited, code=exited, status=1/FAILURE".

**Resolution:** Fixed in version 8.0.10 and later. | | 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-62003 | Azure gateway image upgrades may fail when the Controller does not have the required Azure image subscription access. During the upgrade, the system deletes the existing gateway before validating subscription availability, which can result in gateway deletion without a replacement being created. This leaves dangling gateways in the Controller and can cause potential service outages.

**Impact:** Existing gateways may be deleted during image upgrade. Replacement gateway creation fails due to missing subscription. Customers may experience connectivity loss and dangling gateway entries in the Controller. Manual intervention required, leading to support escalations.

**Workaround:** None. To avoid outages, ensure the Controller subscription includes access to the required Azure image before attempting upgrades. | | 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: If your Controller software version is 7.2.5012 or older, upgrade both the Controller and Gateways to the latest 7.2 build. Delete the proxy configuration from Controller UI > Settings > Advanced > Proxy. Back up the Controller from Controller UI > Settings > Maintenance > Backup & Restore > Backup. Shut down the old Controller. Launch the new 8.0 Controller and transfer the EIP. Once the 8.0 Controller is up, restore the Controller using the backup config from Controller UI > Settings > Maintenance > Backup & Restore > Restore. Add back the proxy configuration from Controller UI > Settings > Advanced > Proxy. Software upgrade the Gateways 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 to upgrade the Aviatrix Controller and Gateways. | | 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:** If you have imported your own proxy CA and key, you can re-import the same certificate and key after the Gateway upgrade to maintain trust continuity. If you rely on the Aviatrix-generated CA: After the Gateway upgrade, export the new CA certificate from the Gateway and distribute it to clients. | | 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. | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.