You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer observed an issue where they had deployed the across-az CFT template and deployed secondary IPs to the ENIs. When the BIG-IP system was rebooted they observe that the secondary IPs are removed by CFE.
To avoid this issue the customer had to manually disable CFE. Ideally there should be an option for CFE to not disassociate private IPs. This is somewhat similar to #64
In this instance the customer did not need CFE for their requirements (they were using DNS to point to the private IPs in each AZ), but ideally this could be a configurable option to disable removing private IPs unless a customer is working with a same-az deployment.
Environment information
For bugs, enter the following information:
Cloud Failover Extension Version: 1.8.0
BIG-IP version: 14.1
Cloud provider: AWS
Severity Level
Severity: 3
The text was updated successfully, but these errors were encountered:
Description
Customer observed an issue where they had deployed the across-az CFT template and deployed secondary IPs to the ENIs. When the BIG-IP system was rebooted they observe that the secondary IPs are removed by CFE.
To avoid this issue the customer had to manually disable CFE. Ideally there should be an option for CFE to not disassociate private IPs. This is somewhat similar to #64
In this instance the customer did not need CFE for their requirements (they were using DNS to point to the private IPs in each AZ), but ideally this could be a configurable option to disable removing private IPs unless a customer is working with a same-az deployment.
Environment information
For bugs, enter the following information:
Severity Level
Severity: 3
The text was updated successfully, but these errors were encountered: