
Chapter 4: Configuring the High-Level Network
4-22
The BIG-IP tracks information about individual persistent connections, and
keeps the information only for a given period of time. The way in which
persistent connections are identified depends on the type of persistence.
Types of persistence
The types of persistence are:
◆ Simple persistence
Simple persistence supports TCP and UDP protocols, and tracks
connections based only on the client IP address.
◆ HTTP cookie persistence
HTTP cookie persistence uses an HTTP cookie stored on a client’s
computer to allow the client to reconnect to the same server previously
visited at a web site.
◆ SSL persistence
SSL persistence is a type of persistence that tracks SSL connections
using the SSL session ID. Even when the client’s IP address changes, the
BIG-IP still recognizes the connection as being persistent based on the
session ID.
◆ SIP Call-ID persistence
SIP persistence is a type of persistence used for proxy servers that
receive Session Initiation Protocol (SIP) messages sent through UDP.
SIP is a protocol that enables real-time messaging, voice, data, and video.
◆ Destination address affinity (sticky persistence)
Destination address affinity directs requests for a certain destination to
the same proxy server, regardless of which client the request comes from.
◆ WTS persistence
Windows Terminal Server (WTS) persistence tracks and load balances
connections between WTS client-server configurations.
Note
All persistence methods are properties of pools.
Persistence options
When setting up persistence, you can enable either of the following two
options:
◆ Persistence across virtual servers with the same address
Persistence across virtual servers with the same address causes the
BIG-IP to maintain persistence only when the virtual server hosting the
connection has the same virtual address as the virtual server hosting the
initial persistent connection.
◆ Persistence across all virtual servers
Persistence across all virtual servers causes the BIG-IP to maintain
persistence for all connections requested by the same client, regardless of
which virtual server hosts each individual connection initiated by the
client.
Comentarios a estos manuales