From: Marvin Greenlee (marvingreenlee@yahoo.com)
Date: Tue Sep 21 2004 - 13:31:16 GMT-3
'Debug IP routing' can be an excellent tool to use for
checking the stability of a lab topology. It will
show you if routes are flapping due to distance
issues. It can also be used with an access-list if
you want to just check a certain route (or group of
routes).
access-list x permit y.y.y.y
debug ip routing x
If you think you have redistribution configured
properly in a test scenario, turn on debug ip routing
and then clear your routing table with a 'clear ip
route *'. If there are flapping routes, you will know
very quickly.
If you have a recursive routing issue with a tunnel,
debug ip routing will show you the route for the
tunnel destination being overwritten by the route
learned through the tunnel (as well as the
administrative distance for both).
As always, use caution when using debug commands in a
production environment.
- Marvin Greenlee, CCIE#12237
Network Learning Inc
marvin@ccbootcamp.com
www.ccbootcamp.com (Cisco Training)
--- ccie2be <ccie2be@nyc.rr.com> wrote:
> Hi guys,
>
> In the documentation for above command, it says this
> command can used to see
> what routes rip adds, modifies, or deletes in the
> route table.
>
> It seems to me, this isn't completely true in that
> it doesn't need to be RIP
> which is changing the route table.
>
> In any case, I'm wondering if this command can be
> used in all circumstances to
> see the changes being made to the route table.
>
> Thanks, Tim
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:47 GMT-3