Specifications

Load Balancing Concepts 21
If you need to remotely administer your Real Servers individually then you should create new
Services, each of which only load balances a single Real Server. Each Real Server must list the LAN
IP address of the Barracuda Load Balancer as its gateway IP address.
Note that Real Servers in the Route-Path deployment cannot access their own VIPs, or any other VIPs
on their own Barracuda Load Balancer.
If you choose this mode of deployment, make sure that the Operating Mode of the Barracuda Load
Balancer is set to Route-Path on the
Basic>IP Configuration page.
Bridge-Path
Bridge-Path provides an easy configuration scenario. Place the Barracuda Load Balancer inline with
your existing IP infrastructure and it can load-balance servers without changing IP addresses. With
Bridge-Path deployment, the WAN and LAN interfaces must be on physically separate networks. The
LAN interface must be on the same logical switch as the servers being load-balanced.
Despite its simple configuration, Bridge-Path deployment is not recommended for most situations.
The following table describes the advantages and disadvantages of deploying your Barracuda Load
Balancer in Bridge-Path mode.
Advantages Disadvantages
Minimal network changes since the existing IP
infrastructure is reused
Slow High Availability failover - longer than 30 seconds.
Real Servers keep their existing IP addresses Separate physical networks required for downstream
Real Servers
Less resilient to network misconfigurations
Sensitive to broadcast storms and other errors related to
loops in a Spanning Tree protocol
Improper configuration of a Bridge-Path network may
result in a broadcast storm, resulting in network outages
Session Directory Integration is not available in Bridge-
Path mode