Forum Discussion

steven_forti_83's avatar
steven_forti_83
Icon for Nimbostratus rankNimbostratus
May 27, 2006

rule choose different pool if primary one is down

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.

 

 

thanks, Steve

 

  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    Hi Steve --

     

     

    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.

     

     

    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 & set the fallback URL to reference the new virtual server:

     

     

    Existing vitual server: 10.10.10.1:80

     

    Pool: normal server pool

     

    Fallback: http://10.10.10.1:81

     

     

    Fallback vitual server: 10.10.10.1:81

     

    Pool: remote fallback server(s) + SNAT

     

     

    HTH

     

    /deb