Active Active HA FO 1 NIC - fadlytabrani/f5-azure-ha-fo GitHub Wiki

Topology

This is a progression from Active Standby HA FO 1 NIC. There are no changes to the topology, just configuration settings.

Deployment

Modify the virtual address(1.1.1.1) object disable ARP and enable spanning.

This instructs all members of the failover group to listen on that VIP, even on standby. At this point, if you have 2 devices, only the active device will respond as it is still in standby state; the cloud_lb_probe_listener virtual server is still indicating to the upstream Azure load balancer that it is in standby. Traffic groups will used to change this behaviour.

Create a traffic group for each of the devices in the failover group. Assign each device as the preferred device in failover order of their respective traffic groups. The screenshot below shows how the assignment should take place.

To explain further, the following are sample settings configured for a 3 device cluster.

Traffic Group	Preferred Order
traffic-group-1	bigip0.azurelabs
traffic-group-2	bigip1.azurelabs
traffic-group-3	bigip2.azurelabs

Once you have assigned the traffic groups, all the BIG-IP devices in the device group will transition to an active state. The upstream Azure load balancer will now route packets to every BIG-IP device in the group in a round-robin fashion. This is now a good time to re-configure the Azure load balancer with persistence settings.

How Does it Work?

TODO

Where Do You Go From Here?

TODO