Hi Steve,
I don't think that's fully accurate. If you have an iRule enabled on a virtual server that's marked down because the default pool is down, the iRule should still be triggered. Here's a quick test on 11.3:
HTTP request to the VS marked down gets a response:
curl -I 10.1.0.120
HTTP/1.0 200 OK
a_header_name: a_header_value
Server: BigIP
Connection: Keep-Alive
Content-Length: 109
VS shows down because default pool is marked down:
[root@ve11d:Active:Changes Pending] config tmsh show ltm virtual ve11_10.1.0.120_http_vs
------------------------------------------------------------------
Ltm::Virtual Server: ve11_10.1.0.120_http_vs
------------------------------------------------------------------
Status
Availability : offline
State : enabled
Reason : The children pool member(s) are down
CMP : enabled
CMP Mode : all-cpus
Destination : 10.1.0.120:80
List of virtual definition:
[root@ve11d:Active:Changes Pending] config tmsh list ltm virtual ve11_10.1.0.120_http_vs
ltm virtual ve11_10.1.0.120_http_vs {
destination 10.1.0.120:http
ip-protocol tcp
mask 255.255.255.255
pool ubuntu_1ip_port80_pool
profiles {
a_tag_html { }
http { }
oneconnect { }
tcp-lan-optimized { }
}
rules {
http_response_by_uri_rule
}
security-log-profiles {
"Log illegal requests"
}
source 0.0.0.0/0
source-address-translation {
type automap
}
vlans-disabled
}
Aaron