Forum Discussion

Miguel_Santos's avatar
Miguel_Santos
Icon for Nimbostratus rankNimbostratus
Oct 18, 2013

Persistence configuration - when node down all new connections permanently in the backup node, even if the previous one goes up again.

Hi,

 

I have the need to implement the following solution as follows:

 

The traffic can be balanced only for a member of the pool; If the member becomes Down the traffic must pass to another pool member; When the member who was down is again available, all the new and old sessions have to be keep in the other member;

 

Can anybody help me with this question?

 

Best Regards.

 

application delivery
availability
deployment
devops
iRules

3 Replies

Sort By
  • Miguel_Santos's avatar
    Miguel_Santos
    Icon for Nimbostratus rankNimbostratus
    Oct 18, 2013

    I think it could do the work! I'll have to try it first, anyway thanks for the help.

     

    I'll get back to you with the result.

     

  • Sam_Richman_263's avatar
    Sam_Richman_263
    Historic F5 Account
    Oct 18, 2013

    You could also configure the the pool to use priority group activation and the monitor on the pool to have the Manual Resume feature enabled. This would send all traffic to your designated primary pool member, and if that pool member goes down, the Manual Resume feature will prevent it from re-activating even if the service on that member comes back up.

     

    The downside of this technique is that you will have to manually reactivate the first pool member, but it gives you pretty solid control over which pool member is receiving traffic.