Current connections not dropped when using command:discard

Most certainly NOT an elegant solution, but I think you could try this kludgy idea, which does not involve an irule....

 

 

For each member of your pool, create a monitor associated with that IP's destination specified. Apply all the monitors to the pool, with an "Availability Requirement" of 2 and set the "Action On Service Down" to either drop or reject....

 

 

For example... via the CLI...

 

 

tmsh

 

ltm

 

create monitor http http-192.168.0.1-80 destination 192.168.0.1:80 defaults-from http

 

create monitor http http-192.168.0.2-80 destination 192.168.0.2:80 defaults-from http

 

create monitor http http-192.168.0.3-80 destination 192.168.0.3:80 defaults-from http

 

create pool testpool members add {192.168.0.1:80 192.168.0.2:80 192.168.0.3:80} monitor min 2 of { http-192.168.0.1-80 http-192.168.0.2-80 http-192.168.0.3-80} service-down-action reset

 

 

You may want to replace 'reset' with 'drop' depending on whether or not you actually want to send resets or just kill the connection.