Any three of these: random, round robin, weighed round robin, least connection, least traffic, least latency, IP hash, URL hash, SDN adaptive.
Client-side load balancing: easy to implement and effective. Server-side load balancing: better able to guarantee load balancing; transparent to client; more secure; we can provide a message to client when all servers are down.
Load balancing and Failover.
The most likely cause is that I forgot to update the alias for the server pool to include the new server. Since the firewall rule to allow traffic to pass to the server pool uses this alias, it allows traffic to pass to every server except the new one.
(a) Yes; (b) no; (c) yes; (d) no.
No; we do not have to create a virtual IP for the PFSYNC interface because use it to pass synchronization data between firewalls; we don’t want any redundancy on this interface.
The firewall rule will get overwritten when data is synchronized with the master firewall.
Because, if the Advertising frequency is the same on two or more backup firewalls, if the master goes down, two or more backup firewalls will try to become master at the same time.
Use HAProxy and select Least Connections as the load balancing for Balance when configuring the backend.
Navigate to Status | CARP (failover) and click on the Enter Persistent CARP Maintenance Mode button.
