Best Practice - Maintenance Pages when LB_Failed
Hey Guys, Historically we have provided our users with the below iRule to through up a maintenance page when the pool/members fail. We have been caught out just recently when a dozen sites got updated pools but due to user/admin error no one updated the maintenance page iRule. The servers in the old pools got decommissioned and an error page was thrown.
when HTTP_REQUEST {
if {[active_members Pool-old-pool-name] < 1 } {
HTTP::respond 200 content "
I have been investigating a better method to do this without direct referencing the pool name. I was looking at and testing in our PreProduction enviornment the event LB_FAILED but ran into truncated responses and was given this reference article via F5 support ( http://support.f5.com/kb/en-us/solutions/public/9000/400/sol9456.html ). So that means that avenue is closed.
What is the best practise for error pages without directly refercing the pool name.
Thanks