Virtual Servers and Their Behavior with Different Profiles in BIG-IP
A Virtual Server in BIG-IP defines how traffic is processed for a specific service or application. Based on the profiles assigned to the virtual server, the behavior of the traffic flow, including handshakes and data exchange, can differ. Below, I’ll provide a detailed explanation of different virtual server configurations, highlighting the traffic flow and the handshakes involved, along with a text graph to illustrate the flow.
1. "Standard" Virtual Server with Only "TCP" Profile
When you configure a Standard Virtual Server with only a TCP Profile, the server will handle only the TCP-level interactions between the client and the server.
Behavior:
The virtual server waits for the 3-Way Handshake from the client-side.
Once the handshake is completed, the server immediately starts the 3-Way Handshake from the server-side.
Flow Description:
Client Side: The client initiates the TCP 3-Way Handshake with the server.
Virtual Server: The virtual server waits for the handshake from the client-side, then completes the handshake and forwards the connection to the server.
Server Side: The server receives the handshake, and the connection is established.
2. "Standard" Virtual Server with Both "TCP" and "Layer-7 Profile" like "HTTP"
When a Layer-7 Profile (e.g., HTTP profile) is added to the virtual server, it involves both TCP-level interaction and application-level processing.
Behavior:
The virtual server waits for both the 3-Way Handshake and application data (e.g., HTTP requests) from the client-side.
After receiving the 3-Way Handshake and application data, the server-side TCP Handshake is initiated.
Flow Description:
Client Side: The client initiates the TCP 3-Way Handshake, and during this process, it may also send HTTP Application Data (e.g., HTTP GET requests).
Virtual Server: The virtual server processes the TCP Handshake and expects the application data (HTTP).
Server Side: Once the handshake and application data are processed, the virtual server initiates the server-side TCP 3-Way Handshake, and the data is forwarded to the server.
3. "Standard" Virtual Server with Both "TCP" and "Layer-7 Profile" like "FTP"
When an FTP Profile is used, the virtual server only waits for the TCP 3-Way Handshake from the client, but it also requires the client to receive the FTP Greeting Banner before sending any data.
Behavior:
The virtual server waits for the 3-Way Handshake from the client-side.
After the 3-Way Handshake, it expects the client to receive the FTP Greeting Banner from the server before initiating any further data exchange.
Flow Description:
Client Side: The client initiates the TCP 3-Way Handshake.
Virtual Server: The virtual server waits for the handshake and sends the FTP Greeting Banner.
Server Side: The server completes the server-side handshake and sends the FTP Greeting Banner before further communication occurs.
Summary of Virtual Server Types
Virtual Server Type
Profile(s)
Handshake Process
TCP Profile Only
TCP Profile
Waits for Client-side 3-Way Handshake, then Server-side 3-Way Handshake
TCP + HTTP Profile
TCP Profile, HTTP Profile
Waits for Client-side 3-Way Handshake + HTTP Data, then Server-side 3-Way Handshake
TCP + FTP Profile
TCP Profile, FTP Profile
Waits for Client-side 3-Way Handshake, then immediately starts the Server-side handshake after the FTP Greeting Banner
Last updated