Testing it by unplugging the connection from the Internet source would simulate a true problem on that Internet connection. And because you can't do this during times when the CC terminal is being used, try the test after hours. You should see it automatically fail over.
First - the concept is that when you balance, you can specify either specific protocols or specific hosts to be bound to a particular WAN port - if that port fails, all traffic is supposed to be routed via the other WAN port - I have tested this with protocol bindings, but not host bindings.
Second - WAN port failure detection - this is done either through a DNS lookup or by pinging a server of your choice and it will take roughly TWO MINUTES to detect and fail over - IF IT ACTUALLY FAILS OVER - choose the server carefully - failover will only occur IF the link failure is between the WAN port and the server you have chosen - if the failure occurs "upstream" from that server, it will not be detected.
Last but not least - EVERY "back up" plan needs to be tested - it's the only way to guarantee that it works - it also needs to be tested at periodic intervals to ensure functionality.
this is done either through a DNS lookup or by pinging a server of your choice and it will take roughly TWO MINUTES to detect and fail over - IF IT ACTUALLY FAILS OVER
Wow, does it really take this long on the Netgear multiwans? The Cisco rv series is pretty quick to enable failover, but you can adjust the number of timeouts before the wan is disabled, so setting it to 3 5s failed pings will fail over the connection in 15s. I'm really shocked to hear you say it takes two minutes.
