Forum Discussion
Hannes_Rapp
Oct 14, 2015Nimbostratus
Hello,
If relying purely on an iRule solution, you would have to use a workaround. I'm not aware of any iRule functions that would enable you to disable VIP entirely. To achieve exactly what you're asking for, by minimum, a combination of an iRule and an iCall script are required.
Perhaps a workaround is better for you?
While a VIP is disabled, F5 will respond to a new connection with a TCP/RST packet. The iRule below will help you simulate a similar behaviour as would occur if the VIP was disabled.
when CLIENT_ACCEPTED {
if { [active_members MyPoolName] < 3 }{
reject
log local0. "[IP::client_addr] - Client rejected. Active members of MyPoolName dropped below 3."
} else {
return
}
}
According to what you've said, all you want is to configure F5 so that any new connections are refused as the number of active members drops below 3. If there are other requirements, please specify.