It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer

Step 5: How to Configure the Barracuda Load Balancer Network

  • Last updated on

Before configuring administrative settings, complete Step 4: How to Configure the Load Balancer Administrative Settings.

In this article:

Modify LAN and WAN IP Addresses

The BASIC > IP Configuration page contains the basic network configuration for your Barracuda Load Balancer. This page also contains the setting to specify whether this Barracuda Load Balancer operates in Route-Path or Bridge-Path mode. Finally, if the Barracuda Load Balancer is behind a proxy server, you can configure its location so that it can download firmware and Energize Updates

VLAN Support

The Barracuda Load Balancer supports Layer 2 VLANs to segment traffic. Use the ADVANCED > Advanced Networking page to identify VLANs on the Barracuda Load Balancer. You can then associate Services or Real Servers with VLANs.

In Bridge-Path mode, if VLANs are used, both the LAN and WAN ports must be on the same VLAN.

To associate a Real Server with a VLAN:

  1. On the ADVANCED > Advanced Networking page, create an entry for the VLAN using the VLAN Configuration table.
  2. Go to the Basic > Services page and add the Real Server.
  3. On the ADVANCED Advanced Networking page, in the Custom Virtual Interfaces table, create an interface for the Real Server.
  4. On the ADVANCED Advanced Networking page, add a static route to the Real Server if necessary.

To associate a Service with a VLAN:

  1. On the ADVANCED Advanced Networking page, create an entry for the VLAN using the VLAN Configuration table.
  2. Go to the BASIC > Services page and add the Service.
  3. On the ADVANCED > Advanced IP Config page, in the System Virtual Interfaces table, locate the entry for the Service. Select the VLAN from the Port list and save your changes.

Route to Multiple VLANs over an Interface

If any interface on the Barracuda Load Balancer has to route to multiple VLANs, it must be connected to the VLAN switch via a trunk (or hybrid) link, since multiple VLAN traffic can only be transported over trunk links. If the Real Servers are distributed across multiple VLANs, say 100, 105, and 111, then the LAN port must be connected to a trunk port on the VLAN switch. 

Make Services Accessible from the LAN/WAN

You can add virtual interface(s) to the physical port (WAN or LAN) used to communicate with the Services.

To make a Service accessible from the LAN:

  1. Go to the BASIC > Services page and add the Service.
  2. On the ADVANCED Advanced Networking page, in the System Virtual Interfaces table, locate the entry for the Service. Select LAN from the Port list and save your changes.

To access the Service from the WAN, create another Service with a different VIP but the same Real Servers.

Create Static Routes

You can create static routes to specify the exact route to a remote network.

To add a static route:

  1. On the ADVANCED Advanced Networking page, create an entry for the VLAN using the VLAN Configuration table, if necessary.
  2. On the same page, fill in the fields in the Static Routes table.

Allow Real Servers to Connect to the Internet

If the Real Servers are on a private network on the LAN side of the Barracuda Load Balancer and the WAN is on a public network, Real Servers are not allowed by default to connect to the Internet. You can override this behavior if, for example, the Real Servers need to get operating system or application updates. This option is available in both Route-Path and Bridge-Path mode.

To allow Real Servers to connect directly to the Internet:

  • On the ADVANCED Advanced Networking page, create a source network address translation (source NAT) rule to map the internal IP address of a Real Server to an external IP address or some other IP address on the WAN side of the Barracuda Load Balancer that is translated by the firewall to an external IP address.

See Specifying Source IP Address in a Clustered Environment for information about the source IP address of incoming traffic.