Forum Discussion
Alan_G__3009
Nimbostratus
NimbostratusPersistence without Persistence Profile?
Hi all,
Please forgive me if this is a repost. I'm trying to determine if there is any type of persistence in place by default within a pool if none is explicitly setup and assigned. During our testing, there are some times where it does appear that persistence is setup for just a few seconds by source IP address, but we don't have a profile attached to a pool. In our case, our pool consists of LDAP servers (tcp ports 389 and 636). Right now our testing hasn't been rigorous enough to track down the issue definitively, but I wanted to ask anyway.
Anyone else seen anything like this? If so, anything we can do to eliminate it?
Thanks for the help.
- Chris_Miller
Altostratus
Besides a persistence table, LTM also has a "connection table" on both its client-to-virtual server side and its LTM-to-Pool Member side. This cuts down on the number of 3-way handshakes that have to take place.
Are you trying to eliminate persistence? 
Alan_G__3009Well, I think if we can understand it, we may not need to eliminate it. In our scenarios, we have customized LDAP health monitors, running every 5 seconds to see if an LDAP server is down. After the 16 second Timeout, the LDAP server is removed from the pool, until its health is restored. However, during that 16 second time period, a client request may come in and be routed to the down server.
We're trying to understand if that re-connection to a down server is more likely for a client LDAP request that just came in 5 seconds ago (and failed), than a brand new LDAP request from a new client.
Does that make sense?
