rule choose different pool if primary one is down

Question

Is there a way to have a rule automatically direct traffic to a different pool in the event that all the nodes in the primary pool fail? In this case my scenario is that the actual nodes are still up  but the networking infrastructure between them and the F5 is down. If I could have a rule that chooses an entirely different pool I could seamlessly reroute traffic to an alternate location and use SNAT (VIP bounce back) to overcome the asymmetric routing situation caused by doing this (which is why I need an entirely different pool to accomplish this since the primary pool would not have snat enabled). I know that pools have the failback host option but I would prefer not to redirect the name or ip address in the browser since the site is a sensitive one and customers might not trust the site if they do not see the domain name they are used to seeing. &nbsp;
&nbsp;thanks, Steve&nbsp;

deb_allen_18 · Answer

Hi Steve --&nbsp;
&nbsp;Unfortunately, v4 doesn't offer us much in the way of checking the status of the pool before sending traffic to it.  v9 is much more capable of handling this scenario.&nbsp;
&nbsp;The only way I can think to redirect traffic when the whole pool goes away while still keeping the same hostname would be to create another virtual server for the same name/IP, different port, then create a pool with the remote servers + SNAT &amp; set the fallback URL to reference the new virtual server:&nbsp;
&nbsp;Existing vitual server:  10.10.10.1:80
&nbsp;  Pool:  normal server pool
&nbsp;  Fallback:  http://10.10.10.1:81&nbsp;
&nbsp;Fallback vitual server:  10.10.10.1:81
&nbsp;  Pool:  remote fallback server(s) + SNAT&nbsp;
&nbsp;HTH
&nbsp;/deb

Forum Discussion

AppWorld Berlin iRules Contest!

F5 AppWorld 2026 Las Vegas - iRules Contest Winners!

Recent Discussions

VIP control across data centers - how to ensure only 1 VIP is up at a time?

FQDN Node Configuration

Logical Disk Full to Migrate rSeries

Priority Group Activation is not working

Changes to DO and AS3 GitHub - no longer monitored

Related Content

Use F5 Distributed Cloud to control Primary and Secondary DNS

Choosing an Instance for F5 BIG-IP in AWS

Choose Your Operator Wisely

is this script running on the primary blade?

Lightboard Lessons: Choosing Strong vs Weak Ciphers