[c-nsp] ip route-cache

[Rodney Dunn]

CEF should be on by default in that code and the
only way 'no ip route-cache' should show up would
be if someone manually put it in.  It should
never be done unless you have found it as a workaround
for a bug in the switching path and as soon as you
can get a fix you should turn it back on as Gert suggested.

Rodney


On Thu, Oct 14, 2004 at 10:37:05AM -0700, Brian Vowell wrote:
> Config:
> 
> 7204 w/ 128MB
> C7200-I/O
> PA-CT3
> PA-FE
> PA-FE
> IOS 12.3(11)T
> 
> 
> 
> Gert Doering wrote:
> 
> >hi,
> >
> >On Thu, Oct 14, 2004 at 09:54:52AM -0700, Brian Vowell wrote:
> >  
> >
> >>What about "ip route-cache flow" 
> >>
> >>I've never used NetFlow, and am not very familiar with it.  I thought it 
> >>was mostly for reporting, but some of the CCO docs make it sound more 
> >>than that.  Is there any benefit on a single static route?
> >>    
> >>
> >
> >The switching paths available differ between IOS releases.  At some time
> >in the past, netflow was an actual switching path, while in recent IOS
> >releases, it's only used for reporting (except on 6500s with some SUPs, if
> >I understood that correctly).
> >
> >What sort of box do you have, and which IOS version?
> >
> >Generally speaking, "ip cef" (global) and "ip route-cache cef" (on each
> >interface) is what you really want.  If your IOS is oldish, CEF might have
> >weird bugs.  In that case you definitely want "ip route-cache".
> >
> >"no ip route-cache" is only necessary in very special conditions, usually
> >related to IOS bugs or debugging things.
> >
> >gert
> >
> >  
> >
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/