Persistence

don't you see the bigip cookie in response?

don't you see the bigip cookie in response?

why it is failing as there are lot of source address peresistence reords

i understand fallback persistence record will always be created.

why it is failing as there are lot of source address peresistence reords

i understand fallback persistence record will always be created.

Will this impact performance?

if you concern about bigip's resource, you may reduce source address persistence timeout.

Will this impact performance?

if you concern about bigip's resource, you may reduce source address persistence timeout.

Is there way to configure fall back source if persistence only on demand?

I'm not sure that would make sense. If you waited to enable source IP persistence until you needed it, there would be nothing in the persistence table to match on. A fallback mechanism continually tracks the persistence information, but does not use it until it's needed. Are you observing that the clients are following source address persistence instead of cookie (assuming they aren't pointing to the same server), or is it just that you see lots of source address persistence records in the table?

Well, as Nitass' alludes, even though source address persistence isn't being used, it still has to gather the data for when it is needed. If it weren't storing that data, then it wouldn't much use. The question then becomes, what is driving you to use source address as a fallback, or really any fallback with cookie as the primary. HTTP cookie persistence is, for any purely browser-based application, the most stable method of all of them. There are certainly edge cases where a fallback would make sense, like when a browser spawns separate agents to separate URLs, but that's not a typical sort of thing.