[c-nsp] Dot1q Interface detect switchport failure

[Rodney Dunn]

The problem he is trying to solve is to know when the
next hop is actually down.

We developed something called object tracking and
started hooking other protocols in to it.
ie: PBR, static routes, etc.
One of the main goals was to solve the DSL dial backup
problem.  Since then it's been used in a lot of corner
case scenarios.

Go to CCO and search on "object tracking static route".

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5413/products_feature_guide09186a00801d862d.html

It hasn't been ported to a code train that runs on the
76xx.  The feature was developed originally for lowend
systems.

There is no other way than a routing protocol to accomplish
what you need.

You would write an offline script that does it for you.
Every 30 seconds telnet in and ping the next hop.
If the next hop doesn't respond add the backup route.
Repeat it and when the next hop comes back add the
route back.

Rodney





On Tue, Aug 31, 2004 at 09:56:40PM -0400, James Hampton wrote:
> Try using a floating static route, basically you have two static
> routes, one of them gets a slightly higher administrative distance
> than the other. When the first route is not reachable and dropped from
> the table, the second one, with the lower A.D. takes over.
> 
> James
> 
> On Wed, 1 Sep 2004 01:54:47 +0800, Tay Chee Yong <tcy at pacific.net.sg> wrote:
> > Hi all,
> > 
> > I have a 7600 connecting to a Catalyst 3550, via a GE Trunk.
> > 
> > As i know that the sub-interface on any router will always be up, irregardless of the port status on the switch. I would like to find out if the dot1q interface on a 7600 is capable of detecting an outage on the switchport of the catalyst 3550, as i need fullfill some kind of backup routing using static routing, so that when the FE port on the switch is down, the router is capable of re-routing traffic to a secondary link. BGP is not an option here. My scenario doesn't allow me to connect the FE directly to the router also, due to the network setup.
> > 
> > Any advise is greatly appreciated.
> > 
> > Regards,
> > Cheeyong
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/