-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Do you already have an issue opened with F5 support?
Github Issues are consistently monitored by F5 staff, but should be considered as best effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open an case with F5 if this is a critical issue.
Description
How to Setup HA (CFE) in Azure where our BIG-IP F5 is already running on Single NIC in Azure
Environment information
For bugs, enter the following information:
- Cloud Failover Extension Version:
- BIG-IP version:
- Cloud provider:
Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: <Fill in level: 1 through 5>
Severity level definitions:
- Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
- Severity 2 (High) : Defect is causing major obstruction of system operations.
- Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
- Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
- Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.
How to setup this in Azure CFE Prerequisites
1:- Virtual addresses created in a floating traffic group and matching addresses (secondary) on the IP configurations of the instance NICs serving application traffic
2:- We have single NIC in our existing F5 VMs, So can you please explain bit more step by step how to configure CFE in existing running BIG IP F5