Verifying Your Load Sharing Configuration - ADTRAN BlueSecure Controller Setup And Administration Manual

You must allocate physical and virtual address carefully according to the subnets you
have chosen. Each node's assigned virtual address and physical address must be located
in the same subnet.
physical=192.168.160.1/24 virtual=192.168.160.2/26
1.
physical=192.168.160.65/24 virtual=192.168.160.66/26
2.
physical=192.168.160.129/24 virtual=192.168.160.130/26
3.
Note here we use the /24 subnet for all physical addresses and the /26 subnet for the
virtual addresses. The BSC DHCP server will give out subnet-masks based on the
configured virtual address, while the physical subnet is needed for failover.
Address Ranges
Do not use a DHCP range with Load Sharing. Instead, use the DHCP exclusion list. All
physical and virtual addresses assigned to the LSG BSCs are excluded automatically.
When configuring DHCP ranges, it's better to exclude the addresses you don't want. If
inclusion is the only option, be careful you don't overlap with the virtual or physical IPs. In
either case, you need to configure the exclusion/inclusion range on each BSC, in case
that BSC takes over as the primary BSC (i.e. the BSC running DHCP server). For more
information on address ranges, refer to "Networks" on page 4-1.

Verifying Your Load Sharing Configuration

Here is some additional information to help you verify that your load sharing
configuration is set up properly.
Network Interface Settings
After you have configured a BSC as a member of a Load Sharing Group, you will see its
virtual managed and protected addresses displayed as the currently used addresses
when you look at its physical interface settings.
Consider BSC2 from our sample set up. If we display its protected interface settings, we'll
see the configured virtual load sharing address displayed as its current protected
interface address as shown in Figure 14-21.
Active Connections
When you view the Status/Active Connections/All Connections page on a BSC that is a
member of a Load Sharing Group, you will see connections to all BSCs in the Load
Sharing Group listed. For example, if we view the active connections page on BSC2 in
our sample Load Sharing Group, we will also see the active connections to BSC1 and
BSC3 listed.
Load Sharing Status
You can view a BSC's load sharing status by displaying the Mobility MatriX/Load
Sharing Setup page.
For simplicity, we'll consider the example of a two-BSC Load Sharing Group. If we look at
the load sharing setup on the Load Sharing Master, we'll see a screen similar to this:
If we look at the load sharing setup on the Load Sharing Node, the screen might look as
shown in Figure 14-23.
Now if a load sharing failover event occurs at the Node, i.e. if its Managed, Protected or
Failover interface goes down, then the Load Sharing Master will reassign the Node's
virtual interfaces to another BSC in the group (in this case to itself). We can verify this by
looking at the Load Sharing Setup page on the Load Sharing Master as shown in Figure
14-24.
BlueSecure™ Controller Setup and Administration Guide
Load Sharing
14-23