Forum Discussion
Martin_Renneke_
May 29, 2017Nimbostratus
Thank you Piotr,
Regarding your questions: The selected option is "cookie insert" We do have Agents established on the member, which are logging every http request at the test system. The behavior is inline with your second post, BUT additional HTTP requests for a member which is not marked down are arriving at the wrong member. We wonder how we can find out, why the F5 seems to send the requests to a wrong member? Is there any option to increase the log level for specific events?
Thank you again. Martin.
- dragonflymrMay 29, 2017Cirrostratus
Hi,
I really don't know what options and behavior is in v10.x - it's quite old. I am dealing mostly with 11.x, 12.x, 13.x
Can you confirm situation:
- First request send to member 1 (according to cookie value)
- Second request with the same cookie value is send to member 2 - even if member 1 is still up
Is that the case?
If so there is either kind of bug or:
- You have OneConnect profile attached to VS and second request is containing cookie value pointing to member 2 - that is exactly as expected - OneConnect is doing LB on per HTTP request base, not per TCP connection base. Easiest way to check is if you can log headers on members, see if BIG-IP cookie is the same in request send to member 1 and member 2. If you can't log headers run tcpdump on BIG-IP or members and see what headers are in request
- Client is sending request with BIG-IP cookie and without it (this is as well only relevant when OneConnect is used). Request with cookie will be send to member according to cookie value, without to any new member selected by LB decision.
- There is some iRule, traffic class or something else causing this behavior
- You have monitor flapping - member goes down/up in rapid succession - should be visible in logs.
Piotr