DescriptionType
Like a Forwarding (Layer 2) virtual server. A Forwarding (IP) virtual server has no pool
members to load balance. The virtual server simply forwards a packet directly to the
Forwarding (IP)
congured destination IP address, based on what's dened in the BIG-IP system's routing
table. The virtual server destination address can be either a node address or a network
address. With a forwarding (IP) virtual server, address translation is disabled. An example
of a Forwarding (IP) virtual server is one that accepts all trafc on an external VLAN
and forwards it to the virtual server destination IP address.
A Performance (HTTP) virtual server is a virtual server with which you associate a Fast
HTTP prole. Together, the virtual server and prole increase the speed at which the
virtual server processes HTTP requests.
Performance
(HTTP)
A Performance (Layer 4) virtual server is a virtual server with which you associate a
Fast L4 prole. Together, the virtual server and prole increase the speed at which the
virtual server processes Layer 4 requests.
Performance
(Layer 4)
A stateless virtual server prevents the BIG-IP system from putting connections into the
connection table for wildcard and forwarding destination IP addresses. When creating
Stateless
a stateless virtual server, you cannot congure SNAT automap, iRules, or port translation,
and you must congure a default load balancing pool. Note that this type of virtual server
applies to UDP trafc only.
A Reject virtual server species that the BIG-IP system rejects any trafc destined for
the virtual server IP address.
Reject
A DHCP virtual server relays Dynamic Host Control Protocol (DHCP) messages between
clients and servers residing on different IP networks. Known as a DHCP relay agent, a
DHCP
BIG-IP system with a DHCP type of virtual server listens for DHCP client messages
being broadcast on the subnet and then relays those messages to the DHCP server. The
DHCP server then uses the BIG-IP system to send the responses back to the DHCP client.
Conguring a DHCP virtual server on the BIG-IP system relieves you of the tasks of
installing and running a separate DHCP server on each subnet.
An internal virtual server is one that can send trafc to an intermediary server for
specialized processing before the standard virtual server sends the trafc to its nal
Internal
destination. For example, if you want the BIG-IP system to perform content adaptation
on HTTP requests or responses, you can create an internal virtual server that load balances
those requests or responses to a pool of ICAP servers before sending the trafc back to
the standard virtual server. An internal virtual server supports both TCP and UDP trafc.
Creating a virtual server
Before creating a virtual server, verify that you have created the pool to which you want this virtual server
to send trafc.
When you create a virtual server, you specify a destination IP address and service port. All other settings
on the virtual server have default values. You can change the default values of any settings to suit your
needs.
1.
On the Main tab, click Local Trafc > Virtual Servers.
The Virtual Server List screen opens.
2.
Click the Create button.
The New Virtual Server screen opens.
3.
In the Name eld, type a unique name for the virtual server.
4.
In the Destination Address eld, type the IP address in CIDR format.
12
About Virtual Servers