Forum Discussion
Comex_17260
Nimbostratus
Nimbostratusmonitor vs persistence
Hello folks,
Let me describe my situation first.
I have a continuous incoming one-way UDP traffic, in which every connection may be alive for a few days or minutes, and btw there are lots of data coming through each connection.
I enabled source addr persistence which time-outs in 3600 seconds for my storage convention.
My problem is:
when a member is marked as down by a monitor, and the connection does not die for a long time, F5 does not direct the active traffic to the member which is up.
It may be waiting for the connection to die and then load balance the new connection which, makes sense, but persistence is a necessity for my case and I wonder if there is a solution for my problem.
Cannot F5 kill the connection when the member is marked as down?
Thanks in advance,
Cx
hoolioCirrostratus
Hi Cx,
You can set the 'action on service down' setting to reject on the pool to have LTM send a TCP reset or ICMP unreachable message to the client and server when a pool member is marked down.
Aaron
HamishCirrocumulus
Or if it's on-way UDP, and you just want to make sure the traffic gets to a poolmember (i.e. There's no connection), you could set it to ReSelect.
H- Comex_17260
Cheers mates, that should do it.