Forum Discussion

breizho35_11667's avatar
breizho35_11667
Icon for Nimbostratus rankNimbostratus
Aug 02, 2016

How to configure manual resume for the second failover only (rollback)

Hello,

 

I would like to know how to custom my configuration to answer to the following need:

 

I currently use a pool with 2 nodes. I have configured some monitors to monitor the nodes states ( my nodes works as activ / passiv state).

 

Currently, If node1 become down, we have a failover (F1) of services from node1 to node2. The Monitors check that node1 is down and the network traffic is automaticaly forwarded only to node2. In case of a new failover (F2) (if node2 become down and node1 become up) the network traffic is forwarded to node1.This case works perfectly in my basic configuration.

 

My need is following: Regarding the second failover (F2), when node1 became up again with service up, I wish to proceed to a manual resume before forward the traffic from node2 to node1.

 

I have tested the "manual resume" option on my monitors but It seems to not answer to my need. Indeed, when I configure "manual resume" option as Yes on my monitors, the first failover is not an automatic process, I have to proceed to a manual resume.

 

I would like to configure the first failover (F1) as automatic and the second failover (rollback) (F2) as "manual resume".

 

Can you advise me to how to configure this need ?

 

Thanks you by advance.

 

Breizho

 

LTM
security

1 Reply

Sort By
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Aug 02, 2016

    breizho35, do you not need to just enable "manual resume" on the node1 monitor (i assume you have two monitors, a different one per node)?

     

    This way if node1 fails, node 2 takes the traffic. if node1 comes back up then it needs manual intervention?

     

    You could probably improve this with Priority Group Activation (if you haven't already). If node1 has a higher priority then once you manually resume that pool member all traffic should then be served by it, independent on node2 availability. See Priority-based member activation

     

    Hope this helps. If not then an anonymised config of you pool setup may help.

     

    N