[c-nsp] 6500/7600 TCAM Usage

Chris Welti chris.welti at switch.ch
Thu Jun 2 11:30:34 EDT 2016


On 01/06/16 16:28, Marian Ďurkovič wrote:
> On Wed, Jun 01, 2016 at 11:03:05AM +0200, Chris Welti wrote:
>> On 01/06/16 10:24, Mikael Abrahamsson wrote:
>>> On Tue, 31 May 2016, Pete Templin wrote:
>>>
>>>> +1 on what Gert said. You'll get log entries at the 90% threshold within
>>>> a region, but the badness only happens when you tickle the 100%
>>>> threshold.
>>>
>>> In my 5 year old experience, the badness would continue even if you
>>> removed some routes and TCAM usage dropped to (let's say) 95% again. The
>>> problem would only be solved by reboot. Is this still the case?
>>>
>>
>> Yes, even on the latest releases. Once you reach "FIB exception state =
>> TRUE",
>> no more new prefix installations possible in the TCAM until a reboot.
>> That also applies to Sup2T btw.
>
> Hmm, in quite old SXF16 we've received the following message a few times:
>
> Jan 12 16:44:53.087: %CONST_V6-SP-5-FIB_EXCEP_OFF: Protocol IPv6 recovered from FIB exception
>
> Is this no longer working?
>
>
>    Thanks,
>
>        M.
>

Interesting. I guess that would call for a new evaluation in the lab...
I guess that is Sup720?

Chris



More information about the cisco-nsp mailing list