TCP reset when Multple irules applied

Hi,

When you have a TCL error message within an iRule the BIGIP send a reset to the client. So in your case you need to fix the issue you see to avoid this TCP reset.

the thing is that when all your pool members are disabled the BIGIP tries to:

redirect the user (first iRule) and then then a respond to the user. It definitely conflicts.

You should try the following:

if it's fine to merge both iRule:

when HTTP_REQUEST {
if {[active_members [LB::server pool]] == 0} {
    HTTP::redirect "http://maintenance.sitename.com/"
} else {
    HTTP::respond 301 Location "https://[getfield [HTTP::host] : 1][HTTP::uri]"
}
}

if you wish to use two different iRules:

when HTTP_REQUEST priority 1{
  if {[active_members [LB::server pool]] == 0} {
    HTTP::redirect "http://maintenance.sitename.com/"
    event disable all
}
}

event with the smallest priority will be applied first.

event disable all means that all other iRule will be disabled so that it won't be activated and conflicted

HTH

and

when HTTP_REQUEST {
HTTP::respond 301 Location "https://[getfield [HTTP::host] : 1][HTTP::uri]"
}