BIG IP F5
“Continuity of service”, “always available”, “agreed level of operational performance”, “single point of failure” – We have come across these terms many times when high availability of website or application need to be considered. BIG IP F5 has mechanisms to maintain service availability during outages and hardware failures by use of redundant infrastructure.
Related- F5 Web Accelerator Module in BIG IP
BIG IP F5 High Availability Feature
High availability feature in BIG IP F5 consists of running redundant F5 chassis (load balancers). The failure of any one of these components does not interrupt the operation of the system.
BIG IP F5 HA has a majority of features which ensure application availability at all anytime, such as Network/connection mirroring, Configuration Synchronization, Network failure.
Related – F5 Big IP Load Balancing Methods
Connection Mirroring: – Connections and persistence information on the active traffic group F5 chassis are duplicated to the peer unit. In the event of a failover, the peer system can begin processing connections immediately without interruption.
Configuration Synchronization: – ConfigSync is a high availability process that collects the configuration files and directories from one unit of a redundant pair into an archive file, and then transmits and installs the shared configuration data on the peer.
Network Failover:- When BIG-IP redundant systems are configured to use network failover, the systems communicate over the configured failover addresses.
Related – Internet Connectivity Failover Scenario with Track
Let’s understand 2 member HA Clusters and their two operating modes; Active/Active and Active/Standby.
Active/ Standby: – In this mode, one unit is active and processes all traffic and the second unit is standby (Standby unit does not process traffic).
However, with the help of config sync feature the entire device configuration is typically synchronized between devices and connection persistence state data can also be mirrored.
If failure is detected on the active unit, all the traffic will be moved to the standby member since standby member is already having all the configuration and connections persistence state, standby become active.
Multiple traffic groups (Creating a virtual instance for your grouping of active-standby) cannot be created since only one unit is active at a time and processes all the connections.
Active/Active: – In this mode, both the units can be active at the same time. We can make full use of the hardware available.
This type of setup is majorly seen where we have limited hardware in the F5 units and the requirement of connection processes are more. Here we can create multiple traffic groups in order to distribute the traffic groups in different F5 devices and make 1st F5 unit as active for one f5 traffic group and 2nd F5 unit active for another traffic group.
Related- F5 LTM Interview Questions