Forum Discussion
NimbostratusCookie persistence when node goes offline
We have issue on our F5 LTM that we are struggling understand and to find a solution for. The version we are on is 11.3.0 Build 3117.0 HF 5
We are using standard cookie persistence on the virtual server, but when a node goes offline in the pool the users are not being directed to the active node for up to 30 seconds.
The Pool has two members and is set up with an action on service down of ‘reselect’. We have also tried Drop and Reject but they made no difference. The monitor we use is an HTTP monitor, this is set up with an interval of 5 seconds and a timeout of 16 seconds, so we would expect a node to be marked down after 16 seconds and for sessions to be moved to the active node at that time.
Is there something special within cookie persistence that prevents node reselection ?
many thanks for any help
Bill
3 Replies
What_Lies_Bene1Cirrostratus
I don't think there's anything special about cookie persistence. What do you mean by 'standard cookie persistence'.
Despite not knowing what the real issue is I can say with some confidence that enabling OneConnect will no doubt improve the situation.
StephanMantheyNacreous
I would monitor the LTM log file:
tail -f /var/log/ltmNow send a request to see, how it´s handled.
You may also want to use an LB_FAILED event with a log statement.
LB_FAILED should be triggered in this case.- Bill_McCreath_9
Many thanks guys, will investigate oneconnect and capture some more log events.
