David_Saw_24368
Nimbostratus
Sep 15, 2018Pool Member disable/forced offline behaviour
Hi Guys, I have a scenario as below:
- Client tries to connect to Outlook and get a password prompt
- Found out the pool member health monitor is showing UP but actual server services (running MS Exch 2016 is down) hence the password prompt.
- Disabled the problematic pool member on F5
- Client clicks Reconnect from Outlook and from F5 sys conn table showing it hitting the pool member
- Did a delete sys conn cs-client-addr in F5 and still showing it hitting the pool member
- Forced offline the problematic pool member on F5and and from F5 sys conn table showing it hitting the pool member
- Remove the problematic pool member from the pool and from F5 sys conn table showing it hitting other pool members. User click Reconnect and no more prompt.
I would like to understand the below:
- When pool member is set to Disabled/Forced offline, any new connection requests will be RST. Any existing active/persistent connections will remain connected until time out? If so, the timeout will be from client or F5 perspective?
- By manually purging the sys connection "delete sys connection cs-client-addr ", does it entirely help to kill off all active/existing connection too? Does it really work and is it a clean way to purge?
- Another way to purge the active/existing connection would be to close the Outlook app and reopen. Then it will hit the F5 VIP and gets served to other working pool members.
Is my understanding correct on the above? I believe this is the way TCP/IP behaves.
Thanks.
David Saw