--> The basic concept behind Persistence is the request from same client should go to the same server.
--> This feature most commonly used if the application which we are using is stateful.
--> The persistence feature is used to change the load balancing behavior of a virtual server.
--> New clients will be load balanced based on the load balancing method configured in the pool.
--> All subsequent connection requests from the same client are direct back to the same pool member if they occur prior to the persistence record time out.
--> Once the initial connection is established then F5 LTM will track and store session data in persistence record.
--> The persistence record contains information like client characteristics and the pool member that accepted the client request.
--> This information is used to identify a returning client and get it back to the same pool member that initially accepted the client request.
--> This feature most commonly used if the application which we are using is stateful.
--> The persistence feature is used to change the load balancing behavior of a virtual server.
--> New clients will be load balanced based on the load balancing method configured in the pool.
--> All subsequent connection requests from the same client are direct back to the same pool member if they occur prior to the persistence record time out.
--> Once the initial connection is established then F5 LTM will track and store session data in persistence record.
--> The persistence record contains information like client characteristics and the pool member that accepted the client request.
--> This information is used to identify a returning client and get it back to the same pool member that initially accepted the client request.
Types of Persistence
1) Simple Persistence --- Persistence record is created based upon client ip address.
2) Cookie Persistence --- Persistence record is created by inserting the cookie when sending the packet to the client.
3) SSL Session ID Persistence --- Persistence record is created based upon Session ID.
4) Universal Persistence--- Persistence record is created based upon any piece of data such as ( network, application protocol , data ) to persist a session.
5) Hash Persistence --- Hash persistence is the use of multiple values within a request to enable persistence.
6) SIP, WTS, Username Persistence ---Session Initiation Protocol (SIP) and Windows Terminal Server (WTS) persistence are application-specific persistence techniques that use data unique to a session to persist connections. Username persistence is a similar technique designed to address the needs of VDI - specifically VMware View solutions - in which sessions are persisted (as one might expect) based on username.
Reference : F5
Very very good explanations
ReplyDeleteHii mahmadd,
ReplyDeleteCan you explain about in real case study in your environtment that when we must using cookies persistence, source address affinity persistence, and destination source address affinity persistence ??? I know that web application server is suitable using cookies persistence. But i dont really know about while we using each type persistence like source address affinity, destination affinity etc. Please give me an example in case study to understand about that implementation of type of persistence. Thanks so much mahhmadd ..
Destination persistence in case of the traffic is going to multiple destinations ( Internet via proxy load balancing)
ReplyDeleteSource address persistence is common in case of TCP application ( not web application)