Re: 6500 Static Route

From: Jeff Andiorio (jandiorio@gmail.com)
Date: Thu Mar 05 2009 - 09:28:13 ARST


Another option in this case would be to add an exit interface
parameter to the static route.

ip route 1.1.1.0 255.255.255.0 vlanX 10.1.1.254

This syntax will specify the next hop ip address and the exit
interface avoiding the recursive lookup issue. When the interface is
down the route will be removed from the routing table.

Jeff

On Thu, Mar 5, 2009 at 6:03 AM, paul cosgrove <paul.cosgrove@gmail.com> wrote:
> The router is probably performing a recursive lookup for 10.1.1.254, and
> believes that it can reach that address via another available path. It may
> be that you have a default route, and that is being used to validate your
> static.
>
> You could setup an ip sla instance, and have your static route track the
> status of that.
>
> Paul.
>
> On Thu, Mar 5, 2009 at 10:35 AM, Rookie Ccie <rookie.ccie@gmail.com> wrote:
>
>> Dear Experts,
>>
>> Recently I noticed that when I configure a static route pointing to a vlan
>> interface next hop IP, the route does not get removed even when the vlan
>> interface is down.
>>
>> ex. ip route 1.1.1.0 255.255.255.0 10.1.1.254
>>
>> When the vlan interface is down due to a physical interface failure, the
>> static route is still in the routing table. On routers the route
>> gets removed from the routing table when the nexthop interface is down. How
>> can I make the static route disapear when next hop interface is down on a
>> 6500 switch.
>>
>>
>> Rgds
>>
>> Rookie
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:04 ART