Changes

Jump to: navigation, search

Load balancing

5 bytes removed, 12:44, 26 March 2012
no edit summary
=== Layer 3 (redirects) ===
Layer 3 load balancing is implemented as a firewall port forward, which is very efficient, and therefore gives layer 3 load balancing a performance advantage over layer 4+. Because of its implementation, it '''requires the firewall to be started''' (simply check if there are any firewall rules in the configuration). Also because if this, it's normally not necessary to add any additional firewall rules. Further, it's necessary that the load balancer is the default route (gateway) of the servers being load balanced, since the source packets of the incoming traffic is maintained. In order words, the topology would look something like:
Internet -> Halon -> Switch -> Server1
# Just give it a name, listen address (the external virtual IP), listen port, forward pool (the pool you created in step 3) and then click "Apply"
# Click the "Cancel" button, then click the newly added redirect in the table, and watch the health check status
 
=== Layer 4+ (relays) ===
Unlike redirects, relays doesn't require the firewall to be enabled, nor that the load balancer is the servers' default route (gateway). In fact, the most common scenario is to perform layer 4 load balancing with the firewall disabled (removing the <tt>firewall</tt> configuration) and to not use the load balancer as a router. Please keep in mind that if the firewall is enabled (simply check if there are any firewall rules in the configuration), you most likely have to add rules on your own allowing traffic to the relay. The topology would look something like:
Internet -> Router -> Switch <-> Halon

Navigation menu