[c-nsp] 7600 cef confusion

Saku Ytti saku+cisco-nsp at ytti.fi
Wed Jan 31 13:05:56 EST 2007


On (2007-01-31 09:36 -0800), Sukumar Subburayan wrote:
 
> When you have 'mls cef error action freeze' which is default in many 
> releases ( but is being changed to 'reset' in upcoming releases), what is 
> supposed to happen is, we free the HW-tables, so that no new entries are 
> added. However, we are also supposed to disable HW-switching and punt 
> everything to software. So, the leaking you are talking about is not 
> possible, as all traffic is being punted to software and software has 
> accurate copy.

In practice this hasn't happened to me not once, but I've seen 
only 3 MLS frozen events.

> However, I do know that there were some bugs, where HW-switching was not 
> getting disabled correctly and hence packets were still being HW-switched. 
> But, that is a bug and not the intended behavior.

Good to hear, much more saner approach (well, will bring box to it's
knees and possibly requiring local access to reload).

> This is what recover is supposed to do:
> 
> 1. Try to reload the fib entries to HW again and unfreeze
> 2. If after a certain number of attempts we still cannot recover
>    we reset the system

This sounds to much better, and reset sounds better than freeze. Why
on earth is freeze default?
What kind of problems could I expect to have with recover? Is it deemed
that it's quite unlikely that system could recover so clean reset
right away on average outperforms recover?

Thank you very much for responding,
-- 
  ++ytti


More information about the cisco-nsp mailing list