[c-nsp] Policy based routing and redndancy

[Ashe Canvar]

Thans Mark, Arturo and Kristofer.

My issue is what happens if the BG session goes down but the ext hop
stays in the routing table because the interface is directly conected
to it. In such a case the seconf route in the OR route map will never
kick in.

I do not know much about VRF's at all. I will look into it.

Finally, I read the cisco docs before posting but my 6509 running
12.2.SXD(5) did not have the interface tracking fully implemented. I
TACed the issue and they said tat basically they have no pland of
implementing this on the 6500 platform.

Anyway, thanks much fr all your input. i really appreciate it.

-ashe


On 8/13/05, Arturo Servin <aservin at remoteconfig.net> wrote:
> Kristofer Sigurdsson wrote:
> 
> >Hi,
> >
> >On Sun, 2005-08-07 at 12:02 -0700, Ashe Canvar wrote:
> >
> >
> >>Hi All,
> >>
> >>I currently use policy based routing to set the next hop for traffic
> >>originating from certain subnets. This works great until the next hop
> >>fails or goes down.
> >>
> >>What are some of the stratergies I might employ to create a "standby"
> >>next hop that takes over if the primary one fails (I have 3 ISPs
> >>connected to the same 6509) ?
> >>
> >>
> >
> >Is putting this subnet in a seperate VRF (either through interface
> >config or policy) an option?  In that case, you could customize the
> >routing table of that VRF according to your needs, eg. via routing
> >protocols or route metrics...
> >
> >
> >
> 
>  A couple of links.
> 
> http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800c75d2.html#wp1000904
> http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps5207/products_feature_guide09186a00801d1e95.html
> 
> Hope it helps.
> 
> -as
> 
> 
> --
> 
> Remote Config, The Remote Configuration Company
> http://www.remoteconfig.net
> Global Service Offices
> contact at remoteconfig.net
> 
> 
> _______________________________________________
> 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/
>