RE: Policy-map next-hop requires extra rib lookups

From: Laidlaw, Patrick A. (Patrick.Laidlaw@wwt.com)
Date: Tue Jun 12 2007 - 20:15:42 ART


Tarun,

I've been doing testing with setting the next hop for route-maps. I'm
having a problem with setting the next hop to the loopback of the device
that is has the destination network that I want to policy route.

IE. R1 <--> R2 <--> R3

R1 LAN 10.1.1.1/24
WAN 10.12.12.1/30
R2 WAN1 10.12.12.2/30
Wan2 10.13.13.1/30
R3 WAN 10.13.13.2/30
Loop 1 10.3.3.3/24
Loop 3 3.3.3.3

On R2 I have a route-map specifying anything from R1 LAN to R2 Loop3
next hop 10.3.3.3 all of the 10.x.x.x address space is being routed via
EIGRP. on R2 I have a default route to null 0 and populating it into
EIGRP so that R1 will send traffic its way for 3.3.3.3.

When pinging from R1 LAN to R3 Loop3 I see the packets matching my
route-map but they never make it to R3. If I change the next hop on R2
to the next wan hop 10.13.13.2 it works when I change it back to the
loop back address of 10.3.3.3 it does not.

My understanding is that the next hop does not have to be adjacent and
it should do a recursive lookup in the rib and send it out to R3 WAN.
If there is something wrong with this and its not possible please say so
but the link you sent says it should and Cisco docs say that the next
hop doesn't have to be adjacent.

Thanks

Patrick

________________________________

From: Tarun Pahuja [mailto:pahujat@gmail.com]
Sent: Saturday, June 09, 2007 6:09 AM
To: Laidlaw, Patrick A.
Cc: ccielab@groupstudy.com
Subject: Re: Policy-map next-hop requires extra rib lookups

Patrick,
               Policy based routing overrides information in the routing
table for the traffic matched by the route-map. Try to follow one of the
following examples to understand PBR concept.

http://www.netcraftsmen.net/welcher/papers/qos3.html#policyrouting
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/q
os_c/qcpart1/qcpolicy.htm

HTH,

Tarun Pahuja
CCIE#7707(R&S,Security,SP,Voice,Storage),CCSI



This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:48 ART