Re: [Astlinux-devel] Forcing WAN Failover

[Michael K. <mic...@ip...>]

Thanks Lonnie for your response.

Could we have a checkbox on the failover tab with something like 'Force Failover to Secondary' and a button to trigger it.
In failover mode, this parameter could be checked and so the secondary does not fail back.
To return to Primary you uncheck the parameter and trigger again.
What do you think?

I could possibly also do this myself in the wan-failover.script I suspect.

Regards
Michael Knill

On 25/9/19, 1:23 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    
    > On Sep 23, 2019, at 3:18 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi Devs
    >  
    > There have been a number of times where I have an intermittently faulty link and I want to force a WAN Failover and keep it there until the problem is restored.
    > The service failover test triggers a failover but its not permanent.
    > Any ideas?
    
    Setting Secondary Delay: to a higher number would keep the switchover to Failover longer.
    
    Unless you are looking for a CLI command like
    --
    service failover force
    --
    but somehow this would need to be reset back to primary.  And the secondary link could also fail while the primary is OK again.
    
    Other than setting Secondary Delay: to 30 minutes or so for notably bad primary links, I'm not not sure of a true answer.
    
    I suppose we could keep track of the time between switches and increase the effective Secondary Delay if there are a lot of failover switches, but that can get complicated.
    
    
    > It would also be really nice to be able to change an ‘External Failover Destination Route’ without having to reboot the system. There have been a number of times where I have just wanted to move the VoIP traffic over to the Secondary link.
    
    Currently your best option is to manually define routes using "ip route add ..."
    
    
    > Thanks all. Failover is great.
    
    Great to hear, I use it all the time but the good news is my primary link is very robust (knock on wood) and the failover is seldom triggered.
    
    Lonnie
    
    
    >  
    > Regards
    > Michael Knill
    > _______________________________________________
    > Astlinux-devel mailing list
    > Ast...@li...
    > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel