Forum Discussion
F5 GTM Persistence TTL - Is it an Idle Timeout?
- Aug 08, 2014
The expires time on the persistence record does not appear to increment with subsequent DNS requests, so I would say it is computed from the first time, not the most recent time.
Generally the larger problem than this is what happens when the client's LDNS changes in the middle of their session? Using Topology or Geo rules would seem a safer method to try and make sure they stay on the same LTM.
if persistence set on a wideip, when ever the first request from ldns or end workstation , it will add an entry in persistence table. and for all the request coming from same ldns or end workstation , it will give same record.if there is no request until timeout value the persistence record will expire.
for example : if we have 3600 sec ttl and gtm given a resolution for wideip. It stores the record in persistence table. Again if the request came from same ldns or end workstation at 3599 sec, persistence timeout will be again start from 0 to 3600
- Michael_WhiddenAug 08, 2014NimbostratusThank you for your detailed answer, but as I commented to mimlo, your answer conflicts with theirs. Can you clarify?
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