[c-nsp] 6500/7600 mls cef

[Sukumar Subburayan]

On Mon, 19 Feb 2007, vince anton wrote:

> Hi,
>
> from a post of a few weeks back (below) regarding  'mls cef error action
> freeze|reset'  it looks like using 'reset' rather than the default 'freeze'
> is the preferred way of operation - is that true also for current boxes
> SUP720-3BXL 12.2SFX7  ?  and is there a bug to watch for this item ?
>
>>>

The defaults being changed to 'reset' is being tracked via:

CSCse95283 (internal bug and hence not visible externally) for 7600. The 
7600 default change should be available as part of upcoming 7600 Release 
12.2(33)SRB.

CSCek68800 for 6500. The default change will be available in an upcoming 
release for Cat6k.

As you are aware, you can change it to 'reset' in configuration.

> **>>* This sounds to much better, and reset sounds better than freeze. Why
> *>>* on earth is freeze default?
> *
>> I agree it was a bad choice. But, it is being corrected to 'reset' as the
>> new default, in newer releases. Until then, you can use configuration
>> command to enable 'reset'.
>
>
> This post had actually started with a mention of:
>
>> * ip cef table consistency-check error-message
> *>* ip cef table consistency-check auto-repair*
>
>
> which is also disabled by default.   Is the cef consistency check something
> I want to be running in production - box is pushing abit less than 1 Gbps in
> and out.

I don't have much experience with enabling the above commands, but don't 
see any harm in enabling atleast the error messages.
BTW, Inconsistency check runs always.

> thanks,
>
> anton
> _______________________________________________
> 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/
>