Tom_51318
Nov 01, 2012Nimbostratus
LTM logging of persistence and load-balancing algorithm results
Hi there,
this is my first post to DevCentral, so I hope it's not a stupid question!
I have an HTTPS virtual server
- default persistence is cookie insert
- fallback persistence is source IP
Although I can verify the presence of the LTM-created cookie, in the response to the client browser, I am concerned that there are still source IP persistence records being created in the LTM.
Now, I can change the fallback persistence to None, and then no source IP persistence records appear.
But I would really like concrete answers as to why these persistence records get created in the first place.
My browser
- is accepting the cookies
- can be stuck to another server, by maniulating the cookie content
This proves to me that the cookie-insert persistence is obeyed.
Is/are there (a) logfile(s) that record why the LTM took the action it did.
For example:
- received request from client with IP A for virtual server with IP W and port X
- no persistence cookie found in request
- no source IP persistence record found where source IP = A
- virtual server W:X uses least-connection(member) load-balance algorithm to pool Y
- pool Y member connection counts:
- pool member D: 100
- pool member E: 106
- pool member F: 96
- client balanced to pool member F with least connections
Cheers,
Tom.