IPv6 support needed for failover of EIP's in Azure

[ksyednazir]

Do you already have an issue opened with F5 support?

F5 ticket opened C3534813. F5 engineer had asked to open github issue.

Description

1. We are using both IPv4 and IPv6 addresses today ion-prem on our F5 devices which are HA pair, and are required to migrate the application and F5 services to Azure.
2. We have a requirement to continue to support both IPv4 and IPv6 in Azure, and we would like to use CFE for high availability because we need fast failover times to meet our strict uptime SLA.
3. We have compliance enforced by a 3rd party so changing these requirements may be complex.
4. With an internet-facing deployment of F5 VE in Azure that supports IPv6 VIPs, we need the CFE to support failover of these VIPs. Can you suggest any workaround or timelines so we can plan for this? Many thanks.

Note: from https://clouddocs.f5.com/cloud/public/v1/azure_index.html
Currently, IPv6 does NOT support failover.

Environment information

For bugs, enter the following information:

• Cloud Failover Extension Version: Not validated
• BIG-IP version: 13.1.3.6
• Cloud provider: Azure

Severity Level

For bugs, enter the bug severity level. Do not set any labels.

Severity: 2

Severity level definitions:

1. Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
2. Severity 2 (High) : Defect is causing major obstruction of system operations.
3. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
4. Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
5. Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.

[shyawnkarim]

Thanks reporting this enhancement request. This is a known issue and we are currently tracking it with internal ID AUTOSDK-46.