This will work if the interface goes down. On fiber connection, most of the time connectivity to the switch will be up but there could be failure/cut after the switch. The best way is check availability of the noc router through the primary link (you can use icmp ping tracking) and failover to secondary link if availability is not there. -----Original Message----- From: skunkworks-bounces@lists.my.co.ke [mailto:skunkworks-bounces@lists.my.co.ke] On Behalf Of Hugo Lombaard Sent: Thursday, September 15, 2011 12:32 PM To: Skunkworks Mailing List Subject: Re: [Skunkworks] Auto Switching of Links and Aggregation On Thu, Sep 15, 2011 at 12:20:50PM +0300, Edwin Ngige wrote:
Hi Hugo Lombard,
All links terminate on one router at end user side and the same at NOC side.
Let's say CustomerA terminates on the NOC router on FastEthernet2 and Serial2, and has been assigned the subnet 10.20.0.0/16. On CustomerA's router, the fiber terminates on FastEthernet0, and the serial on Serial0. There's a default route to the NOC. Then, at the NOC router, you might try: ip route 10.20.0.0 255.255.0.0 FastEthernet2 ip route 10.20.0.0 255.255.0.0 Serial2 100 On the customer router: ip route 0.0.0.0 0.0.0.0 FastEthernet0 ip route 0.0.0.0 0.0.0.0 Serial0 100 Note that this assumes the NOC router and CustomerA's router senses a DOWN on their respective FastEthernet interfaces in case of issues on the fiber. Once that happens, it will fall back to the route over the Serial interfaces, until the FastEthernet comes up again. Beware, this advice is based on a lot of assumptions. You should make sure you understand the consequences of applying this to your network, if you choose to do so. -- Hugo Lombard _______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke