Forum Discussion
Thomas_Gobet_91
Dec 03, 2013Cirrostratus
Hi.
Firstly you don't need your failover server, you can do that with a HTTP profile. There's "Fallback Host" in it, and when all pool members are unavailable it will send the request to this host (your failover server).
Regarding the difference between "all pool members unavailable" and "overloaded", LTM makes the difference.
You will have a red diamond if all members are down, and a yellow triangle if the connection limit is reached. If the connection limit is reached, the BIG-IP will send a TCP RST.To avoid that you have to use your own iRule to make a connection limit :
when RULE_INIT {
set ::max_connections 100
set static ::active_connections 0
}
when HTTP_REQUEST {
if {$::active_connections > $::max_connections} then {
HTTP::redirect "Your_newest_URL"
TCP::close
incr ::active_connections 1
}
}
when CLIENT_CLOSED {
incr ::active_connections -1
}
- third_eye_13875Dec 03, 2013NimbostratusHi, thanks for the response. What worries me a bit is "If the connection limit is reached, the BIG-IP will send a TCP RST". I thought that when I set a conneciton limit on a pool node base (not VIP base) then the BIG-IP will try to connect to the next available pool node (of the same priority). So it does always send a TCP RST? The problem with the counting of current connections in the iRule is that the amount of our "worker" nodes can change all the time (virtual ones) and for changing an iRule (to change the amount of max connections) I need to create a ticket in our datacenter (which could take some time worst case).