In this video we talk about address persistence feature of F5 appliance using profiles. When you configure session persistence, Local Traffic Manager tracks and stores session data, such as the specific pool member that serviced a client request. The primary reason for tracking and storing session data is to ensure that client requests are directed to the same pool member throughout the life of a session or during subsequent sessions. A persistence profile is a pre-configured object that automatically enables persistence when you assign the profile to a virtual server.
The video has two parts, each part has the concept understanding, implementation and verification. The two sections are:
1. Source Address Persistence: Also known as simple persistence, source address affinity persistence supports TCP and UDP protocols, and directs session requests to the same server based solely on the source IP address of a packet.
2. Destination Address Persistence: Also known as sticky persistence, destination address affinity persistence supports TCP and UDP protocols, and directs session requests to the same server based solely on the destination IP address of a packet.
BIG IP F5 version: 14.0.0.3
Client: Cisco Router 3725 and Windows 7
Servers: Cisco Router 3725
To learn F5 LTM online: https://bluemap.co/courses/course-det...
Website: https://www.bluemap.co
LinkedIn: / omar-memon