Forum Discussion

EdH_135054's avatar
EdH_135054
Icon for Nimbostratus rankNimbostratus
Jan 16, 2014

Setting pool member priority on the fly

This is a temporary solution to provide high availability of two apache load balancers which eventually will be decommissioned once we get F5 to perform the way we want and it will take over the LB responsibilities.

 

Currently, F5 LTM is acting as a load balancer for two apache web servers of which only one is active. The idea is to use F5 to provide HA capability to the two apache load balancers who are in turn are load balancing a group of servers. Only one is active, the other passive. This is done by making one server have a higher priority thereby forcing all requests to that member.

 

In the event of a failure of the active, F5 switches requests over to the passive member. When the failed member (with higher priority) comes back online, it resumes as the primary.

 

The real question. Is there a way, to change the priority of the once passive server (now active) to be the priority server, so that when the failed server comes back online, it in fact becomes the passive?

 

1 Reply

  • I don't believe there is. My only thought is that you use the Manual Resume feature so a failed Pool Member can only come back online if a manual intervention is made - far from ideal.

     

    Does Persistence not prevent issues when the failed server comes back?