NimbostratusThe problem is you are checking the node and not the pool member. Change LB::status node x.x.x.x to LB::status pool pool_name member x.x.x.x port for better results. For example:
if { [LB::status pool ssloffload_pool member 172.16.20.1 443] eq "session_disabled" } {
....
} elseif { [LB::status pool ssloffload_pool member 172.16.20.1 443] eq "down" } {
....
}Important! session_disabled is returned only if the pool member is manually disabled (not forced offline). If you force the pool member offline, the the LB::status command returns down rather than session disabled, same as what it does if a monitor marks the pool member down. In other words, with LB::status, there is no way to differentiate between the two causes: "down manually by an administrator" or "down by a monitor."
NimbostratusThank you for the fast reply and good explanation.
I adjusted the iRule, but still only the "down" page is showing.
The node in the pool is really down at the moment, so the Down page is as expected.
When i set the node to Disabled, i expect the maintenance page.
But still the down page is showing. (also tried with incognito browser, cache disabled)
---------------------------------------------------------------------------
Okay,
Replied to fast.
I was disabling the node itself instead of the member of the pool.
Down page and Maintenance page is working now.
If i disable the member of the pool, the maintenance page is showed. Great!
If i disconnect the LAN interface from the webserver, the down page is showed. Great!
But...
I disabled the member of the pool, the maintenance page is showed.
Then i restart the member of the pool for example because of windows updates, for the F5 the member is down instead of disabled and the maintenance page is replaced by the down page.
How can i manage this small problem?