Aviatrix Controller and Gateway Software Release Notes 7.2

​

7.2.5097 Release Notes

Release Date: 19 May 2025

​

Corrected Issues in Aviatrix Release 7.2.5097

Issue	Description
AVX-63522	Resolved an issue where customers using Azure accounts with a high number of Network Security Groups might experience a delay during gateway creation while the Controller validates the subscription’s quota. This process has been optimized to reduce delays during gateway deployment.
AVX-63608	Fixed gateway resize operations that could fail with a KeyError: ‘src’ during the resize process. This occurred when peer tunnel data lacked the expected structure, blocking resize attempts, including those used for recovery from config_fail states.
AVX-64741	Fixed an issue where Datadog metrics could stop sending after a gateway software upgrade. This occurred when the Datadog agent configuration was not properly preserved during the upgrade process.

​

Known Issues in Aviatrix Release 7.2.5097

Issue	Description
AVX-65901	In environments with ThreatIQ enabled and high traffic volumes to threat IPs, gateways running Distributed Cloud Firewall may experience gradual memory consumption leading to potential reboots. This affects gateways with a large number of DCF rules processing continuous threat traffic. Workaround: Monitor memory usage closely and consider reducing the number of active threat rules where possible.
AVX-75944	When migrating an existing Controller to a new Controller VM, a database migration issue can cause configuration changes to be applied to gateways too early during the migration process. Impact: Gateways with NAT configured may experience a temporary datapath disruption during Controller migration. Workaround: There is no workaround. Upgrade to a version that includes the fix (8.0.60, 8.1.30, 8.2.10, or 9.0.0). Contact Aviatrix Support for assistance.
AVX-79521	On Controller versions prior to 10.1.0, it is possible to onboard multiple Aviatrix access accounts that map to the same underlying cloud service provider (CSP) account. Because several Controller features assume a one-to-one relationship between an Aviatrix access account and a CSP account, duplicate access accounts can lead to unpredictable configuration and operational behavior. Duplicate is defined per CSP as follows: AWS (including AWS GovCloud and AWS China): same account number, for both IAM role and access/secret key authentication. Azure (including Azure Government and Azure China): same subscription. GCP: same project. OCI (including OCI Government): same tenancy and compartment combination. Alibaba: same account number. Starting in Controller 10.1.0, the Controller blocks new onboarding of duplicate access accounts across all supported CSPs. Existing duplicate access accounts continue to operate as-is and are not automatically removed. Impact: New duplicate access accounts can still be onboarded on Controller versions prior to 10.1.0. Environments that already have duplicate access accounts may see inconsistent behavior in features that assume a unique CSP account per Aviatrix access account. Workaround: Onboard only one Aviatrix access account per underlying CSP account. If duplicate access accounts have already been onboarded and are causing issues, contact Aviatrix Support for assistance with identifying and removing the duplicates.
AVX-80983	When Azure Security Group Management reads the current state of a security group rule before adding a new gateway’s IP address to it during gateway launch, an Azure API throttling response on that read can be misinterpreted as the rule not existing. In that case, the existing rule is deleted and a new rule is created instead of the existing rule being updated. Impact: Azure security group rules can be unexpectedly deleted and recreated during gateway launch when the Azure API throttles the read call. The delete-and-recreate sequence can result in a brief gap in security group coverage for the affected rule, or in duplicate rules if the sequence does not fully complete. Workaround: Contact Aviatrix Support if you observe unexpected security group rule changes on gateway launch in an Azure environment.

​

7.2.5090 Release Notes

Release Date: 15 April 2025

​

Corrected Issues in Aviatrix Release 7.2.5090

Issue	Description
AVX-63334	Fixed root disk resizing issues on Aviatrix Edge Gateways deployed on Equinix Network Edge and certain VMware environments. The root filesystem now properly expands to use the full allocated disk space during initial setup.
AVX-63846	Resolved display issues in CoPilot UI where SmartGroups and ExternalGroups with multiple filters would not appear as originally configured after being saved. The UI now correctly displays all configured filter sets.
AVX-64196	Fixed IPSec diagnostics in the Controller UI for non-Equinix Edge Gateways. Diagnostic logs are now properly displayed for AEP and self-managed Edge Gateways.

​

Known Issues in Aviatrix Release 7.2.5090

Issue	Description
AVX-65012	BGP route propagation may experience delays in environments with Transit Gateways having more than 1000 learned routes. This affects large-scale deployments with extensive route tables. Workaround: Consider route summarization to reduce the number of individual routes being processed.
AVX-80983	When Azure Security Group Management reads the current state of a security group rule before adding a new gateway’s IP address to it during gateway launch, an Azure API throttling response on that read can be misinterpreted as the rule not existing. In that case, the existing rule is deleted and a new rule is created instead of the existing rule being updated. Impact: Azure security group rules can be unexpectedly deleted and recreated during gateway launch when the Azure API throttles the read call. The delete-and-recreate sequence can result in a brief gap in security group coverage for the affected rule, or in duplicate rules if the sequence does not fully complete. Workaround: Contact Aviatrix Support if you observe unexpected security group rule changes on gateway launch in an Azure environment.

​

7.2.5012 Release Notes

Release Date: 20 March 2025

​

Corrected Issues in Aviatrix Release 7.2.5012

Issue	Description
AVX-62067	Fixed an issue where Transit Gateways with a large number of tunnels (typically >800) could encounter IPSec process unresponsiveness after running for 3-4 months. This was caused by an internal counter overflow. The fix prevents this overflow condition.
AVX-64213	Resolved root disk sizing issues with Edge Gateways using images g3-202504251522 and g3-202504251525. The root filesystem now properly utilizes the full 64GB disk allocation instead of being limited to 12GB.

​

Known Issues in Aviatrix Release 7.2.5012

Issue	Description
AVX-61310	In multi-transit designs with Transit Peering where one Transit Gateway has BGP S2C enabled and learns a default route (0.0.0.0/0), incorrect metrics may be applied to PeerS2c routes following a controller upgrade. Impact: Route metrics may not be applied as expected, potentially affecting traffic path selection.
AVX-80983	When Azure Security Group Management reads the current state of a security group rule before adding a new gateway’s IP address to it during gateway launch, an Azure API throttling response on that read can be misinterpreted as the rule not existing. In that case, the existing rule is deleted and a new rule is created instead of the existing rule being updated. Impact: Azure security group rules can be unexpectedly deleted and recreated during gateway launch when the Azure API throttles the read call. The delete-and-recreate sequence can result in a brief gap in security group coverage for the affected rule, or in duplicate rules if the sequence does not fully complete. Workaround: Contact Aviatrix Support if you observe unexpected security group rule changes on gateway launch in an Azure environment.

​

7.2.4996 Release Notes

Release Date: 18 February 2025

​

Corrected Issues in Aviatrix Release 7.2.4996

Issue	Description
AVX-63001	Fixed Site2Cloud connection stability issues that could occur during gateway failover scenarios in HA configurations. Connections now maintain proper state during transitions.

​

Known Issues in Aviatrix Release 7.2.4996

Issue	Description
AVX-64501	Controller backup operations may take longer than expected in environments with a large number of Site2Cloud connections (>500). The backup process validates all connection configurations which extends completion time. Impact: Extended backup duration but no impact on network operations during backup.
AVX-80983	When Azure Security Group Management reads the current state of a security group rule before adding a new gateway’s IP address to it during gateway launch, an Azure API throttling response on that read can be misinterpreted as the rule not existing. In that case, the existing rule is deleted and a new rule is created instead of the existing rule being updated. Impact: Azure security group rules can be unexpectedly deleted and recreated during gateway launch when the Azure API throttles the read call. The delete-and-recreate sequence can result in a brief gap in security group coverage for the affected rule, or in duplicate rules if the sequence does not fully complete. Workaround: Contact Aviatrix Support if you observe unexpected security group rule changes on gateway launch in an Azure environment.

​

7.2.4820 Release Notes

Release Date: 28 January 2025

​

Important Upgrade Notice

Distributed Cloud Firewall Migration: As of Controller 7.2.4820, Distributed Cloud Firewall (DCF) with WebGroups, configured in CoPilot, is the recommended method for configuring and implementing Egress Security. Aviatrix strongly recommends migrating from Egress FQDN Filtering (Legacy) to Distributed Cloud Firewall to enforce Egress network security policy.

​

Corrected Issues in Aviatrix Release 7.2.4820

Issue	Description
AVX-62891	Fixed memory leak in gateway FQDN filtering that could occur over extended periods with high DNS query volumes. Memory usage now properly stabilizes during normal operations.
AVX-63112	Resolved Controller UI responsiveness issues that could occur when managing deployments with a large number of gateways (>200). The UI now loads and responds more efficiently.
AVX-63203	Fixed an issue where gateway status updates could be delayed in the Controller UI during periods of high network activity. Status information now updates more reliably.

​

Known Issues in Aviatrix Release 7.2.4820

Issue	Description
AVX-63890	Gateway image upgrades on Azure may experience extended completion times in regions with high resource demand. This is due to CSP-level resource allocation delays. Workaround: Schedule upgrades during off-peak hours when possible.
AVX-64001	CoPilot dashboards may show intermittent data gaps for gateway metrics during the first 24 hours after a Controller software upgrade. Data collection normalizes after this period. Impact: Temporary metrics display issue with no functional impact.
AVX-80983	When Azure Security Group Management reads the current state of a security group rule before adding a new gateway’s IP address to it during gateway launch, an Azure API throttling response on that read can be misinterpreted as the rule not existing. In that case, the existing rule is deleted and a new rule is created instead of the existing rule being updated. Impact: Azure security group rules can be unexpectedly deleted and recreated during gateway launch when the Azure API throttles the read call. The delete-and-recreate sequence can result in a brief gap in security group coverage for the affected rule, or in duplicate rules if the sequence does not fully complete. Workaround: Contact Aviatrix Support if you observe unexpected security group rule changes on gateway launch in an Azure environment.