Configuring Bsc Load Sharing (No Nat); Figure 14-20: Configuring Load Sharing On A Node - ADTRAN BlueSecure Controller Setup And Administration Manual

Chapter 14: Secure Mobility® MatriX
Mark the ID radio button that corresponds to the load sharing ID for the Load Sharing
4.
Node.
Specify the Load sharing method that is to be used: NAT enabled for Managed
5.
Interfaces or NAT disabled for Managed Interfaces.
Note: This procedure demonstrates configuration of the Single Subnet load sharing
method. See "Configuring BSC Load Sharing (No NAT)" on page 14-22 for
information about configuring the Multiple Subnet, No NAT load sharing method.
Click Save to store the Load Sharing settings to the BSC database.
6.
Restart the BSC so that its load sharing configuration takes effect.
7.

Configuring BSC Load Sharing (No NAT)

When running with NAT enabled, client traffic in and out traverses the assigned Load
Sharing BSC.
When NAT is disabled, each LSG node must be assigned a unique subnet or returning
traffic will only be routed through the Load Sharing Master. In addition to assigning
unique subnets, static routes for these subnets must be added to the local router.
Some sample settings for configuring Load Sharing with NAT disabled are provided
below. These samples show settings for the managed interface. Each VLAN interface must
be set up in the same way.
Address Settings
Consider the case where you wish to configure Load Sharing for a LSG with three
members across a managed subnet of 192.168.160.0/24.
First, configure the physical managed interface for each LSG BSC (under the Network
tab). These physical addresses are not subnetted.
192.168.160.1/24 (netmask=255.255.255.0)
1.
192.168.160.65/24 (netmask=255.255.255.0)
2.
3. 192.168.160.129/24 (netmask=255.255.255.0)
Next, configure the virtual addresses for each LSG BSC under the Load Share Nodes tab.
These addresses are subnetted.
192.168.160.2/26 (netmask=255.255.255.192)
1.
2. 192.168.160.66/26 (netmask=255.255.255.192)
192.168.160.130/26 (netmask=255.255.255.192)
3.
Note that the 192.168.160.192/26 subnet is not used.
14-22

Figure 14-20: Configuring Load Sharing on a Node