Forcing down a pool member on a GTM

Actually, you shouldn't need an iRule to accomplish any of your goals...

 

 

I have a requirement to send all traffic to the production site as long as it is available, and automatically fail all traffic over to the DR site if the production site is not available.For this, use "Global Availability" as the WIP LB mode, numbering each pool/member in the order in which you'd like them to be handed out, 1 being the most preferred.

 

 

We do not want traffic to automatically fail back to the production site from the DR site when the production site comes back on line.As claretian mentioned, GTM's "Manual resume" feature enabled on at least the primary DC pool member should do the trick (Global Traffic / Pools / / Configuration / Advanced).

 

 

Is there a way to automatically force a pool member down on the GTM if the monitor (which checks to see if a page is returned from the VIP on the LTM) shows that it is unavailable?All you should have to do there is apply an appropriate monitor to the pool members. Make sure you have a Receive string defined, or any response, even a 404 Not Found error, will cause the pool member to be marked UP. If the expected response is not received, the pool member will be marked DOWN after the timeout expires, and if Manual Resume is configured, should stay DOWN until manually re-enabled.

 

 

If you use an LTM monitor to mark the real servers down, but no content monitor on GTM looking for a specific response string, the LTM-generated DOWN status will propagate to GTM via iQuery, but then I don't believe Manual Resume on GTM would work as expected since GTM didn't explicitly mark the node down.

 

 

If you are seeing behavior that doesn't match what I've described, I'd open a Support case and review your observations and configuration with them.

 

 

HTH

 

/deb