Forum Discussion
Best way for iRule to adapt to offline Virtual?
We have some test backend servers that are regularly offline for prolonged periods of time. However, automated monitoring traffic continues to come in, and causes TCL Errors like this:
01220001:3: TCL error: - Operation not supported (line 😎 invoked from within "HTTP::header sanitize $preserve_headers"
This is normally caused by attempting to manipulate HTTP headers after an HTTP::redirect, but there is no redirect in this case... I think the backend being offline has the same effect in blocking HTTP:: manipulations.
What's the normal way of dealing with this? Is there a call you can make to check if the backend is offline so that iRules can stop processing before trying to make these changes? Is there a way to tell the F5 not to invoke iRules when the backend server is offline?
Any pointers appreciated.
1 Reply
LB::status could help. depends a little on how many servers you have in your pool.
https://devcentral.f5.com/wiki/iRules.LB__status.ashx
i don't quite get why the above would happen if the pool is fully down and the virtual server still gets request. are these monitor software request very specific or such?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com