> ## 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.

# Aviatrix Controller and Gateway Software Release Notes 7.1

> Upgrade Options: This release version is available as an upgrade option only if you have already upgraded to the following:

## Important Notices for Upgrading to Aviatrix Release 7.1

**Upgrade Options:** This release version is available as an upgrade option only
if you have already upgraded to the following:

* 7.1.3956 or 7.1.4101 (older Linux OS)
* 7.1.3958, 7.1.4105, 7.1.4139, or 7.1.4183 (newer Linux OS)

**Disable Deprecated Controller-Logging Configurations:** You cannot upgrade
from any Controller 7.0 version to any Controller 7.1 or 7.2 version until you
have disabled the deprecated logging configurations for Elastic Filebeat, Splunk
Enterprise/Cloud, and Sumo Logic.

**Migrate Egress FQDN Filtering to Distributed Cloud Firewall:** As of
Controller 7.1.1710, Distributed Cloud Firewall (DCF) with WebGroups, configured
in CoPilot, is the recommended method for configuring and implementing Egress
Security.

## 7.1.4208 Release Notes

Release Date: 19 May 2025

### Corrected Issues in Aviatrix Release 7.1.4208

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-62067</td><td>Fixed an issue where Aviatrix Transit Gateways with large number of tunnels (>800) and running for a long time could encounter an unresponsive IPSec process leading to all IPsec tunnels going DOWN. This was caused by an internal counter reaching its maximum value and overflowing. The fix prevents this overflow condition.</td></tr>
  </tbody>
</table>

### Known Issues in Aviatrix Release 7.1.4208

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-61310</td><td>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.</td></tr>
    <tr><td>AVX-63334</td><td>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 use the full allocated disk space.<br /><br />**Workaround:**<br /><br />Customers running Aviatrix Edge Gateways on Equinix Edge or VMware environments with version 7.1.4191 should contact Aviatrix Support for assistance.</td></tr>
    <tr><td>AVX-63846</td><td>In the CoPilot UI, **Groups > SmartGroups** and **Groups > ExternalGroups** with multiple filters may not appear as originally configured after being saved. This occurs when creating groups with multiple sets of any resource type.<br /><br />**Workaround:**<br /><br />Avoid using multiple filter sets in a single group until the issue is resolved.</td></tr>
    <tr><td>AVX-64196</td><td>IPSec diagnostics in the Controller UI do not display logs for non-Equinix Edge Gateways (such as AEP or self-managed Edge Gateways).<br /><br />**Note:**<br /><br />This is a UI diagnostic issue only. IPSec tunnel functionality is not impacted.</td></tr>
    <tr><td>AVX-64213</td><td>When deploying Edge Gateways using images g3-202504251522 and g3-202504251525, the root disk may be incorrectly sized after the VM boots. Even if the VM is created with a 64GB disk, the root filesystem may be limited to only 12GB.<br /><br />**Workaround:**<br /><br />Manual resizing of the root partition and filesystem is required. Contact Aviatrix Support for assistance.</td></tr>
  </tbody>
</table>

## 7.1.4191 Release Notes

Release Date: 19 December 2024

### Corrected Issues in Aviatrix Release 7.1.4191

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-57922</td><td>**Security Notice:**<br /><br />CVE-2024-50603 has been permanently patched.</td></tr>
    <tr><td>AVX-58286</td><td>Fixed an issue where gateways using Legacy Egress FQDN filtering could experience traffic interruptions when processing very large data packets (approximately 4000 bytes or larger). This could result in halting all network traffic through the affected gateway.</td></tr>
    <tr><td>AVX-58757</td><td>Fixed an error condition whereby upon upgrading from 7.0 to 7.1, the Controller was not able to update gateway configuration, resulting in the affected gateway being flagged as not up-to-date.</td></tr>
    <tr><td>AVX-59149</td><td>Addressed a regression in 7.1 with TCP maximum segment size (MSS) clamping support, which is now supported on standalone gateways.</td></tr>
  </tbody>
</table>

### Known Issues in Aviatrix Release 7.1.4191

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-61310</td><td>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.</td></tr>
    <tr><td>AVX-63608</td><td>In earlier versions, gateway resize operations may fail with a KeyError: 'src' during the resize process. This occurred when peer tunnel data lacked the expected structure, blocking resize attempts.<br /><br />**Workaround:**<br /><br />If urgent, delete and recreate the gateway. Contact Aviatrix Support for assistance.</td></tr>
    <tr><td>AVX-65698</td><td>In earlier versions, gateways running Distributed Cloud Firewall (DCF) could reboot due to a memory leak in the Traffic Server (TS\_MAIN process). This occurred in environments with ThreatIQ external groups and a high number of DCF rules.<br /><br />**Workaround:**<br /><br />Reduce the number of active DCF threat rules where possible and monitor memory usage closely.</td></tr>
  </tbody>
</table>

## 7.1.4139 Release Notes

Release Date: 14 August 2024

### Corrected Issues in Aviatrix Release 7.1.4139

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-55256</td><td>Fixed an issue where running packet capture resulted in an error, preventing generation of packet captures for troubleshooting.</td></tr>
    <tr><td>AVX-55290</td><td>Fixed connectivity issues when custom DNS/NTP entries are configured in Cloud Service Provider DHCP options and those destinations are not reachable on the local VPC/VNet.</td></tr>
    <tr><td>AVX-55499</td><td>Fixed gateway PKI service issues during software rollback from 7.1.4105 (newer operating system) to 7.1.3956 or 7.1.4101 (older operating system) that caused lost communication between gateway and Controller.</td></tr>
  </tbody>
</table>

### Known Issues in Aviatrix Release 7.1.4139

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-62067</td><td>All Spoke, Transit peering, and external VPN tunnels on one Transit Gateway in a High Availability (HA) deployment pair may drop simultaneously when the 32-bit Netlink sequence counter overflows to 0 on Gateways running strongSwan versions earlier than 5.9.14.<br /><br />**Solutions:**<br /><br />Reboot the affected Gateway to re-establish tunnels, or upgrade Gateways to the latest version.</td></tr>
  </tbody>
</table>

## 7.1.4105 Release Notes

Release Date: 18 July 2024

### Corrected Issues in Aviatrix Release 7.1.4105

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-37706</td><td>**(GCP)** Resolved an issue that could cause gateway image upgrades to fail if Aviatrix Gateways were configured as Router Appliance spokes in the GCP Network Connectivity Center (NCC).</td></tr>
    <tr><td>AVX-37982</td><td>Fixed an issue where clearing bell notifications resulted in the error, "Command to execute is too long".</td></tr>
    <tr><td>AVX-42518</td><td>Resolved an issue where adding and deleting a large number of stateful firewalls increased memory usage to more than 80%.</td></tr>
    <tr><td>AVX-48386</td><td>**(OCI Gov)** Resolved an issue where gateway creation in OCI Gov failed.</td></tr>
    <tr><td>AVX-48707</td><td>**(AWS)** AWS configurable timeouts for security group connection tracking are now properly configured on gateway interfaces for Nitro-based instance types.</td></tr>
    <tr><td>AVX-48764</td><td>Corrected product telemetry for intra tunnels count.</td></tr>
    <tr><td>AVX-48903</td><td>Resolved an issue where upgrade could fail when upgrading an image for a non-HPE Transit Gateway that has a Site2Cloud GRE connection and Jumbo Frame.</td></tr>
    <tr><td>AVX-48917</td><td>Resolved an issue where traffic from the Spoke CIDR was incorrectly routed to FireNet, despite exclusion of the Spoke CIDR from the Inspection Policy.</td></tr>
    <tr><td>AVX-50194</td><td>**(GCP)** Resolved an issue with FireNet BGP over LAN on GCP by correcting the routing for the firewall\_rtb table.</td></tr>
    <tr><td>AVX-50640</td><td>Enhanced single IP HA Site2Cloud to avoid CSP underlay NAT issues during gateway failover.</td></tr>
    <tr><td>AVX-50752</td><td>Corrected product telemetry in private mode implementations.</td></tr>
    <tr><td>AVX-50897</td><td>Resolved an issue where the Controller did not restore peered tunnels that were deleted during the resizing process when HPE Gateway resizing failed due to CSP errors.</td></tr>
    <tr><td>AVX-50941</td><td>**(Azure)** When a new Azure HPE gateway is provisioned, the Controller now creates appropriate route tables that are properly cleaned up when the gateway is torn down.</td></tr>
    <tr><td>AVX-51027</td><td>The VPC Tracker Overlap Detection tool in Aviatrix CoPilot now works correctly with Edge devices.</td></tr>
    <tr><td>AVX-51147</td><td>Resolved an issue that could cause Site2Cloud connection disruptions by validating tunnel IPs prior to assignment to ensure they do not overlap with existing connections.</td></tr>
    <tr><td>AVX-51314</td><td>**(Azure)** Resolved an issue where Azure VNets created out-of-band (OOB) were not populating on the Controller when creating a Gateway.</td></tr>
    <tr><td>AVX-51407</td><td>Resolved an issue that caused disruptions in Site2Cloud tunnel configurations where the local IP address was incorrectly changed to the standby gateway IP after upgrading the image on the standby gateway.</td></tr>
    <tr><td>AVX-51703</td><td>Fixed an issue where an extra route table was created when a gateway without HPE was initially deployed, which was causing issues during gateway deletion.</td></tr>
    <tr><td>AVX-52360</td><td>Fixed dependency violation error when disabling Controller Security Group Management after a Controller image upgrade.</td></tr>
    <tr><td>AVX-52640</td><td>Resolved an issue where Security Group Orchestration incorrectly counted existing user security groups, leading to creation of new groups that could exceed the Security Group mapping limit.</td></tr>
    <tr><td>AVX-52808</td><td>Fixed an issue where the eth1 interface went down after upgrade to Controller 7.0.</td></tr>
    <tr><td>AVX-53450</td><td>Corrected an issue that sometimes resulted in receiving an email about an exception in export\_tf during migration (this did not affect the actual migration).</td></tr>
    <tr><td>AVX-54729</td><td>Resolved memory leak issue when deploying Layer 7 Distributed Cloud Firewall rules to a gateway.</td></tr>
  </tbody>
</table>

### Known Issues in Aviatrix Release 7.1.4105

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-54874</td><td>**(Azure)** The message "Agent status: Not ready" might display in the Azure portal when viewing the Aviatrix Controller. This is by design and does not affect Controller functionality.</td></tr>
    <tr><td>AVX-55256</td><td>Running packet capture may result in an error, preventing generation of packet captures for troubleshooting. Contact Aviatrix Support if you encounter this issue.</td></tr>
    <tr><td>AVX-55290</td><td>If custom DNS/NTP entries are configured in Cloud Service Provider DHCP options and those destinations are not reachable on the local VPC/VNet, traffic to those destinations might be blocked.</td></tr>
    <tr><td>AVX-55499</td><td>Software rollback from 7.1.4105 (newer OS) to 7.1.3956 or 7.1.4101 (older OS) causes gateway PKI service to go down, resulting in lost communication between gateway and Controller. Contact Aviatrix Support for assistance.</td></tr>
  </tbody>
</table>

## 7.1.483 Release Notes

Release Date: 15 October 2024

### Corrected Issues in Aviatrix Release 7.1.483

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-52626</td><td>Fixed an issue when modifying the remote subnet CIDR range of an existing Site2Cloud (S2C) connection using Terraform provider version 3.1.4 where the change was incorrectly applied to the local subnet CIDR range instead of the remote subnet.</td></tr>
    <tr><td>AVX-53986</td><td>Fixed an issue where the Aviatrix Controller was using excessive memory when managing large numbers of access accounts.</td></tr>
    <tr><td>AVX-54732</td><td>Fixed an issue where Aviatrix Edge Platform (AEP) Gateway upgrade status displayed incorrectly after a successful image upgrade.</td></tr>
    <tr><td>AVX-55012</td><td>Fixed an issue where certain SNAT IP addresses were not properly advertised to connected networks when manual connection summaries were configured after upgrading to version 7.1.</td></tr>
    <tr><td>AVX-55434</td><td>Resolved an issue where attaching a virtual network with both IPv4 and IPv6 address spaces could cause invalid routes to be added to the network, losing management connectivity.</td></tr>
    <tr><td>AVX-56022</td><td>Fixed an issue that resulted in loss of expected network connectivity between VNets when an Aviatrix Gateway originating the default route experienced a disruption.</td></tr>
    <tr><td>AVX-56032</td><td>Fixed an issue where Security Group Orchestration was not functioning as expected in some Azure environments with multiple instances in the same virtual network.</td></tr>
    <tr><td>AVX-56466</td><td>Resolved an issue affecting Azure Transit Gateways where upgrading to 7.1.4139 resulted in additional routes being added to the Gateways' secondary network interfaces.</td></tr>
    <tr><td>AVX-56779</td><td>Fixed an issue where restore from backup fails during controller image upgrades.</td></tr>
    <tr><td>AVX-56921</td><td>Resolved an issue where, during Azure service outages, resource handling incorrectly deleted all Azure resources from its database.</td></tr>
  </tbody>
</table>

### Known Issues in Aviatrix Release 7.1.483

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-45480</td><td>Distributed Cloud Firewall rules are not properly applied to non-encrypted (non-TLS), non-web (non-HTTP) traffic when processed by Gateways with High Performance Encryption (HPE) enabled.<br /><br />**Workaround:**<br /><br />Configure DCF rules for non-TLS/non-HTTP traffic with higher priority to ensure proper handling.</td></tr>
    <tr><td>AVX-51456</td><td>Destination network address translation (DNAT) rules cannot be configured on Aviatrix Gateways using Terraform provider version 3.1.4.<br /><br />**Workaround:**<br /><br />Configure DNAT rules through the Aviatrix CoPilot interface.</td></tr>
    <tr><td>AVX-53179</td><td>When the "Ensure TLS" setting on a Distributed Cloud Firewall rule is enabled, non-encrypted HTTP traffic is incorrectly passed to the next rule instead of being dropped.</td></tr>
    <tr><td>AVX-55015</td><td>An issue can occur in handling Site2Cloud Mapped NAT connections when the local CIDR is set to 0.0.0.0/0. When a user edits or deletes a connection mapped to this CIDR, the corresponding IP table rule is not properly removed.</td></tr>
    <tr><td>AVX-56811</td><td>After restoring a Controller configuration, restarting Gateways that were offline could fail re-attestation.<br /><br />**Solution:**<br /><br />Ensure that all Gateways are up before restoring a Controller configuration.</td></tr>
    <tr><td>AVX-60731</td><td>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.<br /><br />**Workaround:**<br /><br />Add a route-map on the upstream sender to strip or reject AS-SET entries.</td></tr>
  </tbody>
</table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.