Applies To:

Show Versions Show Versions

Manual Chapter: Configuring a Basic Link Controller
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

2
The BIG-IP® Link Controller provides a variety of methods for managing the traffic flowing in and out of a network. This basic implementation guides you through configuring the Link Controller to help manage DNS traffic into and out of your network.
For this implementation, consider the fictional company SiteRequest. This company has two internet connections using two different ISPs. SiteRequest has purchased a Link Controller system to manage the inbound and outbound internet traffic to and from their network.
Perform initial set up, including licensing the system and running the Setup utility to perform the initial load balancing configuration
You can use either the liquid crystal display (LCD) panel on the device, or access the system command line to set the management interface IP address and route for the system.
1.
Press the X button on the LCD panel.
The LCD goes into Menu mode, and the arrow buttons become functional.
2.
Use the arrow buttons to select the System menu, and the Management option.
3.
Type the management interface IP address.
For this example, use the preferred management interface IP address 192.168.1.245.
4.
Select the Mgmt Mask option.
5.
Type the netmask for the management interface IP address.
For this example, use the default netmask 255.255.255.0.
6.
Select the Mgmt Gateway option.
8.
Select the Commit option to save your changes.
1.
2.
At the prompt, enter: config customization/
3.
Follow the F5 Management Port Setup utility prompts to set the management interface IP address, subnet and default route.
Now that you have set the management interface IP address and default route, you can license the system, and then access the Configuration utility and run the Setup utility.
2.
3.
To create a dossier, at the prompt type the following command sequence, replacing <regkey> with your registration key:
Copy only the section that begins on the line after the command you typed in step 3, and ends just before the next command prompt.
6.
Follow the instructions to submit your dossier.
The web site returns your product license.
8.
From the BIG-IP system command line, to use a vi text editor to open the file /config/bigip.license, type the following command sequence:
12.
To save the bigip.license file and exit vi, enter the following command sequence:
Important: Even if you typically use the command line to configure a system, you must run the Setup utility from the browser-based Configuration utility before you begin.
3.
At the logon prompt, type admin for the user name, and admin for the password.
The Configuration utility opens displaying the Welcome screen.
Tip: As you proceed through the Setup utility, click the Help tab on the navigation pane for information about the settings on each screen.
1.
On the Welcome screen, click Run the Setup Utility.
3.
Because you have already entered the management interface IP address, netmask and default route using the LCD, accept the values for these options.
Select Use Management Port IP Address to associate the host name with the IP address of the management interface.
This is the default setting.
Select Custom Host IP Address and type a different IP address.
6.
Select a time zone.
The system uses the time zone for the date and time of events recorded in logs.
If you change the time zone, F5 Networks recommends that you reboot the system to ensure that all of the services are in sync. If you do not reboot, it does not affect traffic or management functionality, but there is a possibility that some timestamps might be logged or displayed incorrectly, depending on which service has been restarted and which has not.
7.
In the Password box, type the password for the root account.
8.
In the Confirm box, retype the password that you typed in the Password box.
9.
In the Password box, type the password for the account, admin.
The admin account provides only browser access to the system.
10.
In the Confirm box, retype the password that you typed in the Password box.
11.
Select Enabled from the SSH access list.
12.
Select *All Addresses, to grant unrestricted SSH access to all IP addresses.
Select Specify Range, and then type an address range in the box, to restrict SSH access to a block of IP addresses.
For example, to restrict access to only systems on the 192.168.0.0 network, type 192.168.*.*.
Now that you have set up the system, you can set the setup.run db key to prevent the Link Controller from starting the Setup utility each time a user accesses the Configuration utility.
2.
Type tmsh to access the Traffic Management Shell.
4.
Type quit to exit tmsh.
The next task you perform is to provision the system. Provisioning and licensing work together to make sure that software modules are accessible and appropriately provided with system CPU, memory, and disk space.
Warning: You must provision the Link Controller before you configure it; otherwise, when you provision the module, you lose the configuration.
2.
On the Main tab of the navigation pane, click System, and then click Resource Provisioning.
3.
Select Nominal for the Link Controller setting in the Resource Provisioning (Licensed Modules) area.
The system allocates CPU, memory, and disk space to the Link Controller.
The modules listed in the Resource Provisioning (Unlicensed Modules) area should not be provisioned. That is, the value in those fields must be set to None (Disabled).
4.
Click Update.
Now that you have provisioned the system, the next task is to configure a host name and set up the user accounts for the Link Controller system.
1.
On the Main tab of the navigation pane, expand System, and then click Platform.
2.
In the Host Name box, type the host name for the system.
For this example, type www.siterequest.com.
3.
For the Root Account, type a new password, and then confirm the password. (This account provides access to only the command line interface.)
4.
For the Admin Account, type a new password, and then confirm the password. (This account provides access to only the Configuration utility.)
5.
Click Update to save your changes.
The next task in this implementation is to set up three VLANs that encompass the IP addresses associated with the Link Controller and the other network components that help manage DNS traffic. For this example, create three VLANs using the information in Table 2.1.
VLAN Name
communication between the Link Controller 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 internal.
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 first VLAN.
For this example, type isp1.
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 first VLAN.
For this example, type isp2.
4.
For the Interfaces setting, use the Move buttons to assign the interface 1.3 to the Untagged list.
5.
Click Finished.
After you configure the links, the next task is to create the default gateway pool that load balances the outbound traffic across the links.
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 pool.
For this example, type default_gateway_pool.
4.
For the New Members setting, add the IP addresses associated with each link:
5.
Click Finished.
After you create a default gateway pool, you must instruct the Link Controller to use the pool as the default gateway connection between the internal network and the Internet.
1.
2.
Click Add.
3.
From the Type list, select Default Gateway.
4.
From the Resource list, select Use Pool.
5.
From the Pool list, select default_gateway_pool.
6.
Click Finished.
After you create the VLANs, the next task is to define the physical connections to the Internet. To do this, you create links using the IP addresses of one or more routers on the network that provide a path to the Internet. For this example, create the links using the information in Table 2.2.
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 a name for the link that represents one of the ISPs.
For this example, type ISP1.
4.
In the Router Address box, type the IP address of the router associated with the ISP.
For this example, type 192.168.5.5.
5.
In the Uplink Address box, type the IP address of the ISP.
For this example, type 192.168.5.6.
6.
In the Service Provider box, type the name of the ISP.
For this example, type ISP1.
7.
For the Health Monitors setting, use the Move buttons to add the bigip_link and gateway_icmp monitors to the Enabled list.
The bigip_link monitor uses iQuery to provide the status of the link. The gateway_icmp monitor provides the status of the gateway.
8.
Click Create.
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 a name for the link that represents one of the ISPs.
For this example, type ISP2.
4.
In the Router Address box, type the IP address of the router associated with the ISP.
For this example, type 192.168.10.5.
5.
In the Uplink Address box, type the IP address of the ISP.
For this example, type 192.168.10.6.
6.
In the Service Provider box, type the name of the ISP.
For this example, type ISP2.
7.
For the Health Monitors setting, use the Move buttons to add the bigip_link and gateway_icmp monitors to the Enabled list.
The bigip_link monitor uses iQuery to provide the status of the link. The gateway_icmp monitor provides the status of the gateway.
8.
Click Create.
The next task in this implementation is to configure two listeners, one that detects DNS traffic bound for SiteRequest from each of the ISPs.
1.
On the Main tab of the navigation pane, expand Link Controller and click Listeners.
2.
Click Create.
3.
In the Destination box, type the self IP address on which the Link Controller listens for traffic from ISP 1.
For this example, type 10.10.10.1.
4.
Click Finished.
1.
On the Main tab of the navigation pane, expand Link Controller and click Listeners.
2.
Click Create.
3.
In the Destination box, type the self IP address on which the Link Controller listens for traffic from ISP 1.
For this example, type 10.20.10.1.
4.
Click Finished.
The next task in this implementation is to configure a load balancing pool to process the inbound traffic from the Internet through the ISPs to SiteRequest. The Link Controller system sends client requests to any of the servers that are members of that pool.
1.
On the Main tab of the navigation pane, expand Local Traffic and then click Pools.
2.
Click Create.
3.
From the Configuration list, select Advanced.
4.
In the Name box, type a name for the pool.
For this example, type www-pool.
5.
For the Health Monitors setting, use the Move buttons to move selected monitors to the Active list.
For this example, move the http monitor to the Available list.
6.
Click Finished.
After you create the load balancing pool, the next task is to configure virtual servers, one for each link, to load balance inbound connections across the servers on the network. You also configure one wildcard virtual server to load balance outbound connections across the routers.
1.
On the Main tab of the navigation pane, expand Local Traffic and then click Virtual Servers.
2.
Click Create.
3.
In the Name box type a name for the virtual server.
For this example, type vs for ISP1.
4.
For the Destination setting, select Host, and type the self IP address in the Address box.
For this example, type 10.10.10.80.
5.
In the Service Port box, type 80.
6.
Click Finished.
1.
On the Main tab of the navigation pane, expand Local Traffic and then click Virtual Servers.
2.
Click Create.
3.
In the Name box type a name for the virtual server.
For this example, type vs for ISP2.
4.
For the Destination setting, select Host, and type the self IP address in the Address box.
For this example, type 10.20.20.80.
5.
In the Service Port box, type 80.
6.
Click Finished.
1.
On the Main tab of the navigation pane, expand Local Traffic and then click Virtual Servers.
2.
Click Create.
3.
In the Name box, type a name for the virtual server.
For this example, type forward_outbound.
4.
For the Destination setting, select Network, and type a self IP address in the Address box, and a netmask in the Mask box.
For this example, in both the Address and Mask boxes, type 0.0.0.0.
5.
In the Service Port box, type 0.
Port 0 defines a wildcard virtual server that handles all types of services. If you specify a port number, you create a port-specific wildcard virtual server. In that case, the wildcard virtual server handles traffic only for the specified port.
6.
In the Resources area, from the Default Pool list, select default_gateway_pool.
7.
Click Finished.
1.
On the Main tab of the navigation pane, expand Link Controller and then click Inbound Wide IPs.
2.
Click Create.
3.
In the Name box, type the URL of the wide IP.
For this example, type www.siterequest.com.
4.
For the Members List setting, add the virtual servers that you created in the previous task. For this example, from the Virtual Server list, select:
10.10.10.80, and then click Add.
10.20.20.80, and then click Add.
5.
Click Finished.
Table of Contents   |   << Previous Chapter   |   Next 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)