Forum Discussion
Persistence source addr (Source Address Affinity type)
Persistence – source_addr (default setting) Time out – 180 sec Protocol – TCP Ideal Timeout – 300sec Question – If a user had a persistence record and the user session was ideal for some time .User tried to access the resource (2nd try) just say 10 sec before the persistence record expire - 1.Will the user persistence entry gets updated to 180sec after the existing persistence timer expires? 2. Will the LTM starts counting the TCP ideal timeout(300sec) from the starting of the second try?
1 Reply
- StephanManthey
Nacreous
Hi Joe,
I just gave it a try in under v11.5.1 (virtual server in standard mode with http-profile and source address affinity. And I was a bit surprised to see the persistence records to be reset to 0 with each new request in a keep-alive connection. Same result in performanceL4 mode. By now I was convinced persistence records will be updated with new connections only and after connection close. This used to be the case in the past. But according to AskF5 solution 11109 this was changed. To monitor the persistence table you can run the following on CLI:watch -n 1 -d 'tmsh show ltm persist persist-records'You can add the "all-properties" parameter and limit the output by setting additional properties.
Thanks, Stephan
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com