Applies To:

Show Versions Show Versions

Manual Chapter: Setting Up a Link Controller Redundant System Configuration
Manual Chapter
Table of Contents   |   << Previous Chapter

One standard implementation of BIG-IP® Link Controller systems is a redundant system configuration, which is a set of two Link Controllers: one operating as the active unit, the other operating as the standby unit. If the active unit goes offline, the standby unit immediately assumes responsibility for managing traffic. The new active unit remains active until another event occurs that would cause the unit to go offline, or you manually reset the status of each unit.
This implementation uses and example based on the fictional company, SiteRequest. The following tables detail the network characteristics at SiteRequest.
Table 5.1 outlines the basic characteristics of each Link Controller at SiteRequest.
Self IP address 10.1.1.20 on link1 VLAN
Self IP address 10.1.2.20 on link2 VLAN
Self IP address 172.168.1.20 on internal VLAN
Floating IP address 10.1.1.50 on link1 VLAN
Floating IP address 10.1.2.50 on link2 VLAN
Floating IP address 172.168.1.50 on internal VLAN
Self IP address 10.1.1.21 on link1 VLAN
Self IP address 10.1.2.21 on link2 VLAN
Self IP address 172.168.1.20 on internal VLAN
Floating IP address 10.1.1.50 on link1 VLAN
Floating IP address 10.1.2.50 on link2 VLAN
Floating IP address 172.168.1.50 on internal VLAN
Table 5.2 describes the links that SiteRequest uses.
IP address: 10.1.1.5
IP address: 10.1.2.5
Table 5.3 describes the VLANs you will set up for SiteRequest.
Assigned interfaces: 1.1 (untagged)
Assigned interfaces: 1.2 (untagged)
Assigned interfaces: 1.3 (untagged)
IP address: 10.1.1.100
IP address: 192.168.5.15
Table 5.4 describes several other network characteristics that play an important role in a redundant system configuration for SiteRequest.
IP address: 192.168.5.15
Name: gw_pool
IP addresses: 10.1.1.5 and 10.1.2.5
SiteRequest wants to create a Link Controller redundant system configuration. They have installed two Link Controller systems on the network, and can access each system from the management port.
The first task in creating a redundant system configuration with two Link Controllers is to define each Link Controller as part of a redundant system.
1.
2.
From the High Availability list, select Redundant Pair.
3.
From the Unit ID list, select 1.
4.
Click Update.
1.
2.
From the High Availability list, select Redundant Pair.
3.
From the Unit ID list, select 2.
4.
Click Update.
The next task in this implementation is to set up several VLANs. These VLANs encompass the IP addresses associated with the Link Controllers and the other network components that help manage DNS traffic.
link1
For traffic between the Link Controllers and the Link1 router.
link2
For traffic between the Link Controllers and the Link2 router
internal
For communication between the two Link Controllers and the rest of the internal network
1.
2.
Click Create.
3.
In the Name box, type the name of the first VLAN.
For this example, type link1.
4.
For the Interfaces setting, use the Move buttons to assign the interface 1.1 to the Untagged list.
5.
Click Finished.
1.
2.
Click Create.
3.
In the Name box, type the name of the second VLAN.
For this example, type link2.
4.
For the Interfaces setting, use the Move buttons to assign the interface 1.2 to the Untagged list.
5.
Click Finished.
1.
2.
Click Create.
3.
In the Name box, type the name of the internal VLAN.
For this example, type internal.
4.
For the Interfaces setting, use the Move buttons to assign the interface 1.3 to the Untagged list.
5.
Click Finished.
With a VLAN in place, assign self IP addresses to each Link Controller. These self IP addresses identify the Link Controller on a per VLAN basis.
1.
On the Main tab of the navigation pane, expand Network and then click Self IPs.
2.
Click Create.
3.
In the IP address box, type the self IP address for the system that applies to the VLAN.
For this example, type one of the following:
If you are configuring lc1.siterequest.com, type 10.1.1.20
If you are configuring lc2.siterequest.com, type 10.1.1.21
4.
In the Netmask box, type the subnet mask that applies to this IP address.
For this example, type 255.255.255.0.
5.
From the VLAN list, select the appropriate VLAN.
In this example, select link1.
6.
Click Finished.
1.
On the Main tab of the navigation pane, expand Network and then click Self IPs.
2.
Click Create.
3.
In the IP address box, type the self IP address for the system that applies to the VLAN.
For this example, type one of the following:
If you are configuring lc1.siterequest.com, type 10.1.2.20
If you are configuring lc2.siterequest.com, type 10.1.2.21
4.
In the Netmask box, type the subnet mask that applies to this IP address.
For this example, type 255.255.255.0.
5.
From the VLAN list, select the appropriate VLAN.
In this example, select link2.
6.
Click Finished.
1.
On the Main tab of the navigation pane, expand Network and then click Self IPs.
2.
Click Create.
3.
In the IP address box, type the self IP address for the system that applies to the VLAN.
For this example, type one of the following:
If you are configuring lc1.siterequest.com, type 172.168.1.20
If you are configuring lc2.siterequest.com, type 172.168.1.21
4.
In the Netmask box, type the subnet mask that applies to this IP address.
For this example, type 255.255.255.0.
5.
From the VLAN list, select the appropriate VLAN.
In this example, select internal.
6.
Click Finished.
In a redundant system configuration, both Link Controllers share common IP addresses called floating IP addresses. To the rest of the network, this floating IP address represents the active Link Controller. If the primary unit goes offline, the secondary unit takes over traffic destined for the floating IP address. This setup ensures that network traffic flows smoothly in the event a failover occurs.
Typically, each unit in a redundant system configuration shares a floating IP address for each VLAN on which the redundant system operates. In this implementation, you need to create three floating IP addresses. These IP addresses represent the two Link Controllers on the link1, link2, and internal VLANs.
Important: For this task, configure only the active system. The settings you configure on this system are transferred to the standby system during a synchronization that you initiate later in this implementation.
1.
On the Main tab of the navigation pane, expand Network and then click Self IPs.
2.
Click Create.
3.
In the IP address box, type the floating IP address that is shared between both units.
In this example, type 10.1.1.50.
4.
In the Netmask box, type the subnet mask that applies to the floating IP address.
For this example, type 255.255.255.0.
5.
Check the Floating IP box.
6.
Click Finished.
1.
On the Main tab of the navigation pane, expand Network and then click Self IPs.
2.
Click Create.
3.
In the IP address box, type the floating IP address that is shared between both units.
In this example, type 10.1.2.50.
4.
In the Netmask box, type the subnet mask that applies to the floating IP address.
For this example, type 255.255.255.0.
5.
Check the Floating IP box.
6.
Click Finished.
1.
On the Main tab of the navigation pane, expand Network and then click Self IPs.
2.
Click Create.
3.
In the IP address box, type the floating IP address that is shared between both units.
For this example, type 172.168.1.50.
4.
In the Netmask box, type the subnet mask that applies to the floating IP address.
In this example, type 255.255.255.0.
5.
Check the Floating IP box.
6.
Click Finished.
The options associated with creating a redundant system configuration include the IP addresses of each system, the type of redundant system, and other options.
1.
On the Main tab of the navigation pane, expand System and then click High Availability.
2.
On the menu bar, click Network Failover.
3.
Click the Network Failover box.
4.
In the Peer Management Address box, delete the colons (::) and type the management IP address of the peer unit.
For this example, type 192.168.1.1.
a)
In the Configuration Identifier box, type a unique name for the unicast entry.
For this example, type Link Controller.
b)
In the Local Address box, type the self IP address associated with the failover VLAN you created on the unit you are configuring.
For this example, type 172.168.1.20.
c)
In the Remote Address box, type the self IP address associated with the failover VLAN you created on the peer unit.
In this example, type 172.168.1.21.
d)
Click Add.
Important: In this example, for the lc2.siterequest.com system, use 192.168.1.2 for the Peer Management Address, and reverse the values of the Local Address and Remote Address settings.
Optionally, define a set of secondary failover IP addresses. In this example, the secondary failover addresses can be the self IP addresses the Link Controllers use to communicate with link1 or link2.
The next task of this implementation requires defining an NTP server that both Link Controllers use during synchronization options. This task is important because it determines a common time value for both systems. During file synchronizations, the systems use this time value to see if any newer configuration files exist.
1.
On the Main tab of the navigation pane, expand System and then click Configuration.
3.
In the Address box, type the IP address of the NTP server you want to use.
For this example, type 192.168.5.15.
4.
Click Add.
5.
Click Update.
The next task is to define the default gateway for network traffic. (In this example, the default gateway is a pool containing the IP addresses that correspond to the link1 and link2 links.) Once you create this pool, you can create a default route within the Link Controllers.
1.
On the Main tab of the navigation pane, expand Local Traffic and then click Pools.
2.
Click Create.
3.
In the Name box, type the name of the default gateway pool.
For this example, type gw_pool.
4.
For the Health Monitors setting, use the Move buttons to add gateway_icmp to the Active list.
5.
From the Load Balancing Method list, select Dynamic Ratio (node).
6.
For the New Members setting, add the IP address of each link.
For this example type the following:
IP address 10.1.1.5, selecting All Services from the Service Port list. This IP address represents the link1 link.
IP Address 10.1.2.5, selecting All Services from the Service Port list. This IP address represents the link2 link.
7.
Click Add.
8.
Click Finished.
1.
2.
Click Add.
3.
From the Type list, select Default Gateway.
4.
From the Resource list, select Use Pool and then select the name of the default gateway pool.
In this example, select gw_pool from the list.
5.
Click Finished.
The Link Controller employs a listener to identify the traffic for which it is responsible. In this example, create a listener that corresponds to the floating IP address shared between the two systems.
Important: For this task, configure only the active system. The settings you establish on this system are transferred to the standby system during a synchronization that you initiate later in this process.
1.
On the Main tab in the navigation pane, expand Link Controller and then click Listeners.
2.
Click Create.
3.
In the Destination box, type the IP address on which the system listens for network traffic.
For this example type 10.1.1.50.
4.
From the VLAN Traffic list, select All VLANs.
5.
Click Finished.
For a redundant system configuration, you must employ an additional synchronization option to share the self IP address, default route, and other information you configured on both the active and standby systems.
1.
On the Main tab of the navigation pane, expand System and then click High Availability.
2.
3.
Click Synchronize TO Peer.
The system synchronize settings to the standby Link Controller; in this example, lc2.siterequest.com.
4.
Important: For this task, configure only the active system. The settings you establish on this system are transferred to the standby system during a synchronization that you initiate later in this process.
1.
On the Main tab of the navigation pane, expand System and then click Configuration.
3.
Check the Synchronization check box.
4.
Check the Synchronize DNS Zone Files check box.
5.
In the Synchronization Group Name box, type the name of the synchronization group.
For this example, type Link Controller Group A.
6.
Click Update.
The next task is to add the links that represent the two Internet connections. Each Link Controller configuration must contain at least two links for the system to load balance network traffic.
Important: For this task, configure only the active system. The settings you establish on this system are transferred to the standby system during a synchronization that you initiate later in this process.
1.
On the Main tab of the navigation pane, expand Link Controller, and then click Links.
2.
Click Create.
3.
In the Name box, type the name of the link.
For this example, type link1.
4.
In the Router Address box, type the IP address of the link.
In this example, type 10.1.1.5.
5.
For the Health Monitors setting, use the Move buttons to add the bigip_link monitor to the Enabled list.
6.
Click Finished.
Repeat the procedure to define the second link. In this example, the second link on the Link Controller, uses the name link2 and the router address 10.1.2.5.
Lastly, you need to have the two units share the same configuration. For this implementation, that means you need to have the standby Link Controller acquire the configurations established on the active Link Controller. You must do this before you attempt to synchronize these systems; otherwise, you run the risk of having the new Link Controller, which is unconfigured, replace the configuration of older systems. To acquire the configuration files, you run the gtm_add script.
Important: Run the gtm_add script from the unconfigured Link Controller.
1.
Log on to the standby system.
In this example, log on to lc2.siterequest.com.
3.
Press the y key to start the gtm_add script.
4.
Type the IP address of the active system.
For this example, type 172.168.1.20.
5.
Press Enter.
The gtm_add process begins, acquiring configuration data from the active Link Controller (in this example lc1.sitequrest.com). Once the process completes, you have successfully created a redundant system configuration consisting of two Link Controllers.
Table of Contents   |   << Previous Chapter

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)