For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

JG_249184's avatar
JG_249184
Icon for Altocumulus rankAltocumulus
Nov 16, 2017

Killing active connections after a node is marked down

Hello guys,   Is there a way to kill all active connections immediately to the backend node, when the pool's HTTP keepalive marks it down? The problem we are seeing is the connection is still open...
application delivery
BIG-IP
LTM
Simon_Blakely's avatar
Simon_Blakely
Icon for Employee rankEmployee
Nov 16, 2017

The pool option Action on Service Down:

 

Specifies how the system should respond when the target pool member becomes unavailable. The default is None, meaning that the system takes no action to manage existing connections when a pool member becomes unavailable.

 

  • None: Specifies that the system maintains existing connections, but does not send new traffic to the member.

     

  • Reject: Specifies that, if there are no pool members available, the system resets and clears the active connections from the connection table and sends a reset (RST) or Internet Control Message Protocol (ICMP) message. If there are pool members available, the system resets and clears the active connections, but sends newly arriving connections to the available pool member and does not send RST or ICMP messages.

     

  • Drop: Specifies that the system simply cleans up the connection.

     

  • Reselect: Specifies that the system manages established client connections by moving them to an alternative pool member when monitors mark the original pool member down.

     

Please note - Reselect does not do what you think it does for TCP connections - it does not establish a new 3WHS to the newly selected pool member, it just send the packets. Unless the pool member is a transparent gateway, this will cause the new pool member to issue a reset.

 

K15095: Overview of the Action On Service Down feature