For any application or website that has been deployed, it is important to have load balancing and high availability implemented to sustain high traffic and failover in case your primary infrastructure goes down.
The load balancer is the key component that ensures high availability and intelligently routes client requests to the right server. This in turn maximizes performance and capacity utilization while sending requests only to servers that are online.
High availability (HA) makes sure that the server pool is ready for user requests in situations when your primary load balancer is down and you can redirect that traffic to your backup/secondary load balancer with very minimal downtime which is not noticeable by users.
F5 load balancer ensures seamless failover in cases where a server is down or overloaded and redirect the traffic to other servers that could handle the load.
HA deployment consists of two BIG-IP (like other load balancers) systems synchronized with the same configuration.
The goal of such redundant pairing is to provide users with seamless, uninterrupted service in the event of failure on one device.
If the active system is taken offline or fails to connect, the standby system immediately takes over, to avoid processing traffic. Typically, the newly active system remains active until an event requires the first BIG-IP system to become active again or until you manually force that system into standby.
The sensor automatically detects the HA Peer configuration when one of these devices is added to sensor as part of “addagentless”. Also, during automation, the certificate is synced to both the HA devices based on the F5 configuration. Hence, you are not required to add both the IPs as separate agentless.
Sensor supports the following configurations when adding an F5 for automation: