From: John D. Fellenbaum (john.d.fellenbaum@xxxxxxxx)
Date: Mon Dec 10 2001 - 21:39:00 GMT-3
Kris,
This command changes the next hop address of the matched packet(s). This
command is executed (assuming the match critera was satisfied) prior to ever
looking at the routing table. For example, if you fall through on your
route-map constructs, normal routing takes place. Use "debug ip policy" comman
d
along with "debug ip packet 101 detail", where "access-list 101 permit icmp any
any". Ping through the router, then check your debug output. If you try to pin
g
from the router, you will have to specify "ip local policy --- " to have router
generated packets policy routed.
HTH,
John
"Krake, Kris" wrote:
> I am curious to see what this command actually changes in a packet put on
> the wire (or if it changes that at all?). I am looking at ccbootcamp lab 1
> and have configured it and have it working but expected this to change the
> route table. The route table did not change. Next, I did a debug ip packet
> on the spoke routers to see if a header had changed and see that the source
> and destination of the packets is still in tact...again to my surprise. I
> now know that I'm completely off base as to what I thought the (ip next-hop)
> command actually does. I am considering putting a sniffer on the line and
> see what is actually changed but was wondering if someone who had more
> experience with this could give me the skinny instead so that I may save
> some valuable lab time.
>
> Much obliged...
> KK
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Kris A. Krake
> WAN Engineer
> AEGON Technology Services - NECS
> 502.560.2716
> kkrake@aegonusa.com
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:41 GMT-3