From: Brant I. Stevens (branto@branto.com)
Date: Mon Apr 18 2005 - 23:12:51 GMT-3
You might want to disable CEF when issuing debugs, and you want traffic to
be process-switched.
On 04/18/2005 08:28 PM, "Richard Gallagher" <rgallagh@cisco.com> wrote:
> Mark,
>
> There are no real reasons that you want to disable CEF unless you were
> running into a bug where's it causing problems.
>
> You might find the following doc intersting, it answers some of your
> questions:
>
> -
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fswtch
> _c/swprt1/xcfcef.htm
>
> HTH, Rich
>
> --
>
> * Rich Gallagher - Cisco Systems TAC
> * CCIE #7211 - R&S, C&S
>
> Mark Lasarko wrote:
>
>> Just thinking - as much real world as the lab I suppose...
>> Are there *any* situations where 'ip cef' would not be desirable?
>> (aside from the obvious "do not issue the command ip cef")
>>
>> I can only think of two myself... and I am not sure if both apply??
>>
>> The first is proxy-arp, 'cause this can cause a routing loop
>>
>> The second is if you wanted to load-balance by the routing protocol
>> then you would not want cef
>> The logic being that cef would assume the load balancing functions over
>> the routing protocol once populated.
>>
>> and while I have the burning smell inside my brain...
>> I recall reading that arp populates cef.
>> I also recall reading that when arp times out cef entries will do the
>> same
>> are these two perceptions correct?
>> and with cef enabled (and populated) how does this impact arp activity
>> - if at all?
>>
>> Thoughts?
>> ~M
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:55:00 GMT-3