This solution applies to Barracuda Load Balancers in a Bridge-Path configuration, firmware verisons 2.0 and above.
To set up Bridge-Path, the following conditions must be met:
- The Real Servers must be physically isolated behind the Load Balancer. This means that each Real Server will no longer be visible on the network if the Barracuda Load Balancer goes down (a separate switch is absolutely required for models 440 and below).
- Each Real Server must be "one hop" away from the LAN port on the Barracuda Load Balancer. This means their switch must be directly connected into the LAN port of the Barracuda Load Balancer, or connected to a series of switches that eventually reach the LAN port of the Barracuda Load Balancer without going through any other machines.
- The LAN IP address of the Barracuda Load Balancer must not be specified in Bridge-Path mode (it must be left blank on the Basic > IP Configuration page).
- The Real Servers must be on the same subnet and logical network as the Barracuda Load Balancer, the Virtual IPs (VIPs), and the rest of the WAN, and they must specify the same gateway as the Barracuda Load Balancer.
- Lastly, the box must be in Bridge-Path mode on the Basic > IP Configuration page.
If Bridge-Path is the only deployment method that will work for your organization but you cannot support the Barracuda Load Balancer as a single point of failure, you can cluster two Barracuda Load Balancers together in High Availability mode for an active-passive failover configuration.
For more information on High Availability, see Solution #00001316.
Link to This Page: