F Standard virtual server【DOC精选】.docVIP

The BIG-IP LTM TMOS operating system implements a full proxy architecture for virtual servers configured with a TCP profile. By assigning a custom TCP profile to the virtual server, you can configure the BIG-IP LTM to maintain compatibility to disparate server operating systems in the data center. At the same time, the BIG-IP LTM can leverage it’s TCP/IP stack on the client side of the connection to provide independent and optimized TCP connections to client systems.In a full proxy architecture, the BIG-IP LTM appears as a TCP peer to both the client and the server by associating two independent TCP connections with the end-to-end session. Although certain client information such as the source IP address, or source TCP port may be re-used on the server-side of the connection, the BIG-IP LTM manages the two sessions independently, making itself transparent to the client and server.The Standard virtual server requires a TCP or UDP profile, and may optionally be configured with HTTP, FTP or SSL, profiles if Layer 7 or SSL processing is required.The TCP connection set-up behavior for a Standard virtual server varies depending on whether a TCP profile or a TCP and Layer 7 profile such as HTTP, is associated with the virtual server. Standard virtual server with TCP profile The TCP connection set-up behavior for a Standard virtual server operates as follows: the three-way TCP handshake occurs on the client side of the connection before the BIG-IP LTM initiates the TCP handshake on the server side of the connection.A Standard virtual server processes connections using the full proxy architecture. The following TCP flow diagram illustrates the TCP handshake for a Standard virtual server with TCP profile:  Standard virtual server with Layer 7 functionality If a Standard virtual server is configured with Layer 7 functionality, such as an HTTP profile, the client must send at least one data packet before the server-side connection can be initiated by the BIG-IP LTM