GTM sorry server/last resort best practices
Is there an article that outlines the best practices or guidelines for implementing a GTM sorry server?
The problem I am facing is that we currently use an iRule to reselect the sorry server pool (just webservers displaying an outage page) in the event of an LTM service failing. This is used in preference to a fallback host as it allows the client to maintain the original URL.
However if this iRule is used in virtuals for GTM services, the virtuals are enever marked as failed as the iRule ensures that the sorry server page is still served.
For a GTM service using a global availability algorithm this means that the GTM service fails to fail over to a remote site if the first virtual in the GTM pool fails.
I can forgo the use of a LTM iRule for a sorry server, however this means using a last resort pool in the wideip configuration. The problem then becomes that as our organisation uses a combination of private and public services, both a public and private sorry server GTM pool is required. Additionally, both a HTTP and HTTP service are required for each public and private sorry server as the services are a mixture.
Is there any way in which to simplify the configuration of a GTM sorry server or fallback host?