session persistence issue

Robert,

 

 

"dest_addr" persistence will persist all traffic, independent of src client, to the same pool member when the dest ip is the same. So, if there's only one dest ip then all connections will be served by the same pool member. What's the mask on the "dest_addr" profile? I think by default it's 255.255.255.255. If destination persistence is what you're after I'd double check this. However, should you be thinking of using source address persistence? Without knowing more of your setup I'm unsure whether this is relevant info.

 

 

Hope it helps!

 

 

N

Destination address persistence uses the client's destination IP address, so it's only really useful for network virtuals. As Nathan said, try source address persistence.

 

 

Aaron

Thanks. What do you need to know about our setup to know if source address persistence is what I should be using?

 

 

The mask is "None" because I'm using the default profile.

 

Is this HTTPS traffic? Do your clients support cookies? If yes to both of those I'd suggest using cookie insert persistence with a OneConnect profile. This should give more granular load balancing across pool members compared with source address persistence.

 

 

Aaron

The traffic is HTTPS to the Big-IP LTM and then the SLL if offloaded by the Big-IP LTM and the traffic is then HTTP to the servers. Cookies... no because they aren't required but we do use cookie-less sessions though.

nathan, if I use source address persistence can I use the default source address profile or do I need to change anything? Thanks.

Robert,

 

 

The only two settings i've tended to modify in the default profile are Mask - do you want individual clients to source persist or are you happy to persist a subnet and Timeout - in the past I've had to increase the default setting.

 

 

N

Resolved! I changed it to source address and had to really bump the timeout up! Thanks!!!