Applies To:
Show VersionsBIG-IP versions 1.x - 4.x
- 4.5.14, 4.5.13, 4.5.12, 4.5.11, 4.5.10
7
A Simple Intranet Configuration
Working with a simple intranet configuration
The simple intranet solution described in this chapter is commonly found in a corporate intranet (see Figure 7.1 ). In this scenario, the BIG-IP system performs load balancing for several different types of connection requests:
- HTTP connections to the company's intranet web site. The BIG-IP system load balances the two web servers that host the corporate intranet web site, Corporate.main.net.
- HTTP connections to Internet content. These are handled through a pair of cache servers that are also load balanced by the BIG-IP system.
- Non-HTTP connections to the Internet.
Figure 7.1 A simple intranet configuration
As Figure 7.1 shows, the non-intranet connections are handled by wildcard virtual servers, that is, servers with the IP address 0.0.0.0 (or * or "any"). The wildcard virtual server handling traffic to the cache servers is port specific, specifying port 80 for HTTP requests. This way all HTTP requests not matching an IP address on the intranet are directed to the cache server. The wildcard virtual server handling non-HTTP requests is a default wildcard server. A default wildcard virtual server is one that uses only port 0 (or any or * or "" [blank string]). This makes it a catch-all match for outgoing traffic that does not match any standard virtual server or any port-specific wildcard virtual server.
Creating the simple intranet configuration
To create this configuration, you need to complete the following tasks in order:
- Create load balancing pools
Create pools for the intranet servers you want to load balance and one for the cache server. - Create virtual servers
Create the virtual servers for each pool and for the non-HTTP requests.
Defining the pools
The first step in a basic configuration is to define the two load balancing pools, a pool for the intranet content servers and a pool for the Internet cache servers.
To create pools using the Configuration utility
- In the navigation pane, click Pools.
The Pools screen opens. - Click the Add button.
The Add Pool screen opens. - For each pool, enter the pool name and member addresses in the Add Pool screen. (For additional information about configuring a pool, click the Help button.)
Configuration notes
For the example in Figure 7.1 , create the pool http_pool containing members 192.168.100.10:80 and 192.168.100.11:80.
Create the pool specificport_pool containing members 192.168.100.20:80 and 192.168.100.21:80.
To create the pools from the command line
To define a pool from the command line, use the following syntax:
b pool <pool_name> { member <member_definition> ... member <member_definition>}
To create the pools http_pool and specificport_pool from the command line, you type the following commands:
b pool http_pool { \
member 192.168.100.10:80 \
member 192.168.100.11:80 }
b pool specificport_pool { \
member 192.168.100.20:80 \
member 192.168.100.21:80 }
Defining the virtual servers
The next step in a basic configuration is to define the virtual servers that reference http_pool and specificport_pool, respectively, as well as the forwarding server (no pool) for remaining Internet traffic.
To define the virtual servers using the Configuration utility
- In the navigation pane, click Virtual Servers.
The Virtual Servers screen opens. - Click the Add button.
The Add Virtual Server screen opens. - For each virtual server, enter the virtual server address and pool name. (For additional information about configuring a virtual server, click the Help button.)
Configuration notes
For the example in Figure 7.1 :
Create virtual server 192.168.200.30:80 using http_pool
Create virtual server 0.0.0.0:80 using specificport_pool
Create virtual server 0.0.0.0:0 as forwarding server (no pool)
To define the virtual servers from the command line
To define a virtual server from the command line, use the following syntax:
b virtual <virt IP>:<port> use pool <pool_name>
You can use standard service names in place of port numbers. If you have DNS configured, you can also use host names in place of IP addresses.
The following commands define virtual servers that map to the pools http_pool and specificport_pool, respectively, and a forwarding virtual server:
b virtual 192.168.200.30:80 use pool http_pool
b virtual 0.0.0.0:80 use pool specificport_pool
b virtual 0.0.0.0:0 forward
Additional configuration options
Whenever you configure a BIG-IP system, you have a number of options:
- You have the option in all configurations to configure a BIG-IP redundant system for fail-over. Refer to Chapter 13, Configuring a Redundant System , in the BIG-IP Reference Guide.
- All configurations have health monitoring options. Refer to Chapter 11, Monitors , in the BIG-IP Reference Guide.
- When you create a pool, there is an option to set up persistence and a choice of load balancing methods. Refer to Chapter 4, Pools , in the BIG-IP Reference Guide.