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

JimRiley_106607's avatar
JimRiley_106607
Icon for Nimbostratus rankNimbostratus
Jan 18, 2012

persistant connection

An active in-use node has two health monitors. One health monitor fails and the F5 properly sets the node to RED diamond / inactive state. However, the F5 still sends data to the node. The data i...
application delivery
dev
devops
iRules
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Jan 19, 2012
Reselect only works for these cases:

 

 

 

http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-concepts-11-1-0/ltm_pools.html

 

 

You should configure the system to select a different node in certain cases only, such as:

 

•When the relevant virtual server is a Performance (Layer 4) virtual server with address translation disabled.

 

•When the relevant virtual servers Protocol setting is set to UDP.

 

•When the pool is a gateway pool (that is, a pool or routers)

 

 

 

And yes, I meant reject which sends a reset for TCP connections. Drop would potentially work as it removes the LTM connection table entry and causes LTM to send a reset to the client and pool member on the next packet from either side. Reject just works quicker to get to the same point. No matter which option you select, LTM will start selecting the pool member again for new connections once it's marked up by the monitor(s).

 

 

Aaron