Policy-map next-hop requires extra rib lookups

From: Laidlaw, Patrick A. (Patrick.Laidlaw@wwt.com)
Date: Fri Jun 08 2007 - 20:31:44 ART


Group,
When using route-maps for PBR on an incoming interface it should
override any routing information for those packets that match a mapping.
"someone say yeah or nay now"
If I have three routers R1----R2---R3. R3 with a loopback 1.1.1.1 and
10.1.1.1 the others just setup for 10.x.x.x links full eigrp routing for
10 address space. R2 has a default route to null 0 and redistributes
that out through eigrp. If I try to ping to 1.1.1.1 from R1 the traffic
should go into the bit bucket with no answer.
If I then have a route-map on the incoming interface of R2 from R1 that
specifies traffic from R1 going anywhere should be sent to R3's loopback
reachable via eigrp, and I then try to ping 1.1.1.1 it should work
correct?
My logic for this scenario is as follows:
R1 Trys to ping 1.1.1.1
Looks up in its table sees default route to R2
R2 receives traffic from R1 It hits the route-map
Route-map sees ACL matching traffic from R1 to anywhere
Sets next hop to 10.1.1.1
Looks up in rib table for 10.1.1.1
Sees 10.1.1.1 is on R3
Sends traffic destined to 1.1.1.1 to R3
Someone tell me if my logic is skewed because I'm getting unreachable
when trying to ping 1.1.1.1 and before I go digging through my config
wanted to make sure this logic works.
Patrick Laidlaw - Deployment Engineer
t: 907 770 8300
f: 907 770 8329
m: 907 382 1150
E: patrick.laidlaw@wwt.com
w: www.wwt.com



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