Hi Team, We noticed a strange issue in our Enviornment. Currently we enabled the default persistence as cookie. When we tried to access the application from different browser all the request are sending to only App server. Pasting below the jsession ID and cookie information. i could see the cookie information is same for all browser, Why it so? Finally I want to know when F5 will send the request to second APP server, does it require clearing cache on browser or F5 cookie? IE: mda_JSESSIONID=mOKmvioojyuMCkbprmyd698G; BIGipServerSAAS_MDA_POOL=3730919434.63530.0000 Chrome: mda_JSESSIONID=YU4G9p8bcy0ZAZCL1KQA0cI3; BIGipServerSAAS_MDA_POOL=3730919434.63530.0000 Firefox: BIGipServerSAAS_MDA_POOL=3730919434.63530.0000; mda_JSESSIONID=0Ddk1aKwg1CMNMXBlt-oMiiW Thanks, Akhi

Can anybody update on this. -Akhilesh

Hi Akhilesh, You confirm you persitance profil is set to cookie persistance. Can tell us what do you see in pool statistics ? Do you all request going to the same server or do you see stuffs to the second app server ? What is your Load Balancing method ? Take care Matt

Yes, if i tried accessing application from different client IP then another APP server will start serving request. But when i access from different browser from same client IP then request are going to only one App server and pool statistics will show traffic to only one APP box. i cleared my browser cache and accessed again and still the same app server is processing traffic. I tried after one hour and again same app server is serving request. a) Why F5 cookie information is same for all browser? thanks, Akhi

Load balancing method- Round Robin Default persistance- Cookie Fall back persistance- Source address

Cookie value is the same because the member selected by LTM is the same. Pleas try to : - clear all cookies in your browsers - check you LB methods (Round robin for ie) - Check your persistance profiles (cookie insert par ie) And make a test. Try without any persitance profile to test if load balancing methods works as well. There is something in your configuration forcing all connections to server 1.

Cookie persistance | DevCentral

17 Replies

Akhilesh_128432
Nimbostratus
Jul 23, 2013
Can anybody update on this.

-Akhilesh
Matt_Dierick
Employee
Jul 23, 2013
Hi Akhilesh,

You confirm you persitance profil is set to cookie persistance. Can tell us what do you see in pool statistics ? Do you all request going to the same server or do you see stuffs to the second app server ?

What is your Load Balancing method ?

Take care

Matt
Akhilesh_128432
Nimbostratus
Jul 23, 2013
Yes, if i tried accessing application from different client IP then another APP server will start serving request.

But when i access from different browser from same client IP then request are going to only one App server and pool statistics will show traffic to only one APP box. i cleared my browser cache and accessed again and still the same app server is processing traffic. I tried after one hour and again same app server is serving request.

a) Why F5 cookie information is same for all browser?

thanks,

Akhi
Akhilesh_128432
Nimbostratus
Jul 23, 2013
Load balancing method- Round Robin

Default persistance- Cookie

Fall back persistance- Source address
Matt_Dierick
Employee
Jul 23, 2013
Cookie value is the same because the member selected by LTM is the same.

Pleas try to :

- clear all cookies in your browsers

- check you LB methods (Round robin for ie)

- Check your persistance profiles (cookie insert par ie)

And make a test. Try without any persitance profile to test if load balancing methods works as well.

There is something in your configuration forcing all connections to server 1.
Matt_Dierick
Employee
Jul 23, 2013
Disable the fallback persistance profile as well. It is the root cause I think.
nitass
Employee
Jul 23, 2013
is this helpful?

i could see the cookie information is same for all browser, Why it so?
sol6917: Overview of BIG-IP persistence cookie encoding

http://support.f5.com/kb/en-us/solu...l6917.html
Akhilesh_128432
Nimbostratus
Jul 23, 2013
Matt,

i just disabled fallback persistence profile and could see second app server start processing traffic. so My question why we need fallback persistence then? thanks for your help.

Also As I mentioned why cookie information is same for all browser from same client machine? how long will it keep this cookie information. currently i didn't mentioned any time out value in my Virtual server configuration

-Akhi
Akhilesh_128432
Nimbostratus
Jul 23, 2013
Seems after disabling fallback persistence again the traffic are processed by one App server. please help me.
What_Lies_Bene1
Cirrostratus
Jul 23, 2013
Can you post your Pool and Cookie persistence configurations please? tmsh list ltm pool 'name' and tmsh list ltm profiles persistence...