Applies To:

Show Versions Show Versions

Manual Chapter: Setting up a One-IP Network Topology
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

17 
Another configuration option you can use with the BIG-IP® system is a one-IP network topology. This differs from the typical two-network configuration in two ways:
Because there is only one physical network, this configuration does not require more than one interface on the BIG-IP system.
 
Clients need to be assigned SNATs to allow them to make connections to servers on the network in a load balancing pool.
The first task required to set up this implementation is to create a pool that contains the content servers that you want to load balance. Before creating the pool, verify that all content servers for the pool are in the network of VLAN external.
1.
On the Main tab of the navigation pane, expand Local Traffic, and click Pools.
The Pools screen opens.
2.
In the upper-right corner of the screen, click Create.
The New Pool screen opens.
Note: If the Create button is unavailable, this indicates that your user role does not grant you permission to create a pool.
3.
From the Configuration list, select Advanced.
4.
In the Name box, type a name for the pool, such as server_pool.
5.
For the Health Monitors setting, from the Available box select http, and click the Move button (<<) to move the monitor name to the Active box.
6.
For the Allow SNAT setting, verify that the value is Yes.
8.
In the Resources area of the screen, use the default values for the Load Balancing Method and Priority Group Activation settings.
9.
For the New Members setting, add the pool members:
a)
Click the New Address option.
b)
In the Address box, type the IP address of a server in the pool.
c)
In the Service Port box, type 80, or select HTTP.
d)
Click Add.
10.
Click Finished.
The second task required to set up this implementation is to create a virtual server that references the pool of servers that you want to load balance. The pool that the virtual server references is the pool you created in the previous task.
1.
On the Main tab of the navigation pane, expand Local Traffic, and click Virtual Servers.
The Virtual Servers screen opens.
2.
In the upper-right corner of the screen, click Create.
The New Virtual Server screen opens.
Note: If the Create button is unavailable, this indicates that your user role does not grant you permission to create a virtual server.
3.
In the Name box, type a name for the virtual server, such as vs_one_ip.
4.
For the Destination setting:
b)
In the Address box, type an IP address for the virtual server.
5.
In the Service Port box, type 80, or select HTTP from the list.
7.
From the HTTP Profile list, select http.
This assigns the default HTTP profile to the virtual server.
8.
In the Resources area of the screen, locate the Default Pool setting and select the name of the pool you created in the previous section (using our example, this would be server_pool).
9.
Click Finished.
Another task that you must perform to implement one-IP network load balancing is to define a default route for the VLAN external.
1.
On the Main tab of the navigation pane, expand Network and click Routes
The Routes screen opens.
2.
In the upper-right corner of the screen, click Add.
The New Route screen opens.
Note: If the Add button is unavailable, this indicates that your user role does not grant you permission to add a route.
3.
For the Type setting, verify that it is set to Default Gateway.
This disables the Destination and Netmask settings.
4.
For the Resource setting:
5.
Click Finished.
Note: If you are defining a default route for a route domain other than route domain 0 (the default route domain), the procedure varies slightly. For more information, see the TMOSTM Management Guide for BIG-IP® Systems.
Finally, configure the BIG-IP system to handle connections originating from the client. You must define a SNAT in order to change the source address on the packet to the SNAT external address, which is located on the BIG-IP system. Otherwise, if the source address of the returning packet is the IP address of the content server, the client does not recognize the packet because the client sent its packets to the IP address of the virtual server, not the content server.
If you do not define a SNAT, the server returns the packets directly to the client without giving the BIG-IP system the opportunity to translate the source address from the server address back to the virtual server. If this happens, the client might reject the packet as unrecognizable.
1.
On the Main tab of the navigation pane, expand Local Traffic, and click SNATs.
The SNATs screen opens.
2.
In the upper-right corner of the screen, click Create.
The New SNAT screen opens.
Note: If the Create button is unavailable, this indicates that your user role does not grant you permission to create a SNAT.
3.
In the Name box, type a name for the SNAT, such as snat_one_ip.
4.
In the Translation box, type an IP address that you want to use as a translation IP address.
5.
From the Origin list, select Address List.
This displays additional configuration settings.
6.
For the Address List setting:
a)
For the Type setting, verify that Host is enabled.
b)
In the Address box, type a client IP address.
c)
Click Add.
7.
From the VLAN Traffic list, select Enabled on.
8.
For the VLAN List setting, from the Available box select external, and click the Move button (<<) to move the VLAN name to the Active box.
9.
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)