From: Rex Dayes (nerker@xxxxxxx)
Date: Fri Sep 15 2000 - 09:55:33 GMT-3
Title: ip route-cache
One reason to turn off route-cache:
If you want to do the dreaded "debug ip packet" in the middle of the
day, you can utilize it with an access-list so that you don't bring
your router to its knees.
"debug ip packet 151" for instance, will only display ip packets that
match access-list 151.
The main problem is that if packets are not process switched and are
using cached information on what interface to route to, you will only
catch the first packet with the debug as the processor does its first
lookup.
By turning off any cacheing, every packet goes to the processor, and
the debug will pick them up. This way you can verify a particular
host, host:port, etc., is transiting your router's interface, and can
timestamp (service timestamp debug datetime msec) them in and out of
your router.
I've used this on a busy 7507 taking it from 40% processor utilization
to just over 60%, and certainly no where as dangerous as a "debug ip
packet"!!!
***** When done, turn off debug and turn route-cache back on *****
Your router will love you for it!
----- Original Message -----
From: Price, Jamie
To: ccielab@groupstudy.com
Sent: Wednesday, September 13, 2000 6:05 PM
Subject: ip route-cache
Hi,
Can anyone help me out here?
I've been wondering about the aforementioned command. I realize,
after looking at the docs that "ip route-cache" enables fast switch
processing but I'm curious about the parameters and the ability to
disable it.
Can anyone provide me with some solid, factual, reasons as to why
you would want to turn fast switching off or turn autonomous
switching on, etc? Also why can you use it on a Vlan interface in
a switch - this one sort of has me at the moment?
If this is something basic that I'm overlooking.......well....I was
going to apologize but we all have to take a trip back to the
basics sometime dont we.....so I wont :)
Thanks
Jamie
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:56 GMT-3