[c-nsp] static route across LACP link

[Oliver Boehmer (oboehmer)]

cisco-nsp-bounces at puck.nether.net <> wrote on Saturday, October 07, 2006
7:10 AM:

> Quoth A. Li:
> 
>> A - I assume this is happening because I don't have an L3 interface
>> for vlan20 on the 3650. So although I do have a default route, it is
>> pointing to an address that I do not now how to get to. However, if
>> this is the case, I'm not sure how to get around it. This is a /30,
>> and the other IP address belongs to my ISP.
>> 
>> B - If this is the case, I am not sure why?
> 
> All next-hop routes must, by definition, be directly connected.
> 
> Directly connected = same subnet = same L2 broadcast domain.
> 
> If you configure a route via a next hop that doesn't meet this
> requirement, IOS won't install it in the routing table.  That is
> exactly what you are seeing. 

Well, the requirement is that the route must *resolve* to a reachable
next-hop. So if you do

 ip route <network> <mask> <next-hop> 

where <next-hop> is not known via directly connected, but there is
another route which resolves next-hop to something directly connected,
it'll work. IOS recurses multiple levels down, so something like this
will work

ip route 1.1.1.1 255.255.255.255 1.1.1.2
ip route 1.1.1.2 255.255.255.255 1.1.1.3
ip route 1.1.1.3 255.255.255.255 1.1.1.4
ip route 1.1.1.4 255.255.255.255 Serial0

all the FIB/CEF entries will point to Serial0

A.Li: You should just point the default route on the new 3650 to the
first switch's address of the LACP channel, instead of to 192.158.1.2.
Or you can add a routing protocol between the switches so the new 3650
will know how to reach 192.168.1.2, but then you can also advertise the
default route from the first one..

	oli