Hi all,
@Brad: Thank you for the suggestion. At the moment the default is handled by associated pool. If the iRule is not matched, then it goes through the pool rules. I have tested this on a virtual F5s by specifying different IP addresses in the iRule, to the ones from the pool, and I get expected results.
What is very strange is the fact, that there is no difference (on the virtual F5) to behavior between the iRule with the "status" variable and "status_vs". No errors generated with both. However on the physical F5 it's failing. I haven't tested the status_vs on the physical GTMs yet.
My virtual F5 has both LTM and GTM enabled in on one instance, while the physical appliances are separate. Is that what can affect the behavior? I am really confused by this. Probably the best way is to apply it on the physical and test it, but it's still interesting what's the difference.