[f-nsp] CER: IPv6 Route ADD: CAM entry creation FAILED

Derek dblabian at gmail.com
Wed Sep 6 15:43:37 EDT 2017


Yeah, you are right, profiles aren't supported on the CER series.  It still
seems your error is related to over-utilization, hence the fix with a
reboot.  Check the utilization.



On Wed, Sep 6, 2017 at 2:37 PM, Brian Rak <brak at gameservers.com> wrote:

> CER's don't have CAM profiles.  From the information I can find, they
> don't actually use TCAM anyway.
>
> On 9/6/2017 3:32 PM, Derek wrote:
>
> Did you check the CAM utilization?  It's probably full, perhaps you can
> partition it differently.
>
> On Wed, Sep 6, 2017 at 2:30 PM, Brian Rak <brak at gameservers.com> wrote:
>
>> Has anyone else seem problems with the CER's being unable to add routes
>> before?  We have multiple devices (all 2024C-4X) reporting one or both of
>> these messages:
>>
>> IPv6 Route ADD: CAM entry creation FAILED
>> IPv4 Network Route ADD: CAM entry creation FAILED
>>
>> They're learning a full v4+v6 table, but we are well below the limits
>> defined in `sh default values`.  From past experience, a reload seems to be
>> the only thing that will actually correct this, but that is a pretty
>> annoying thing to have to do.
>>
>> Any ideas for what may be causing this?  We're on 5.6.0m right now.
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
>
>
> --
> Be Well,
>
> Derek Labian
>
>
>


-- 
Be Well,

Derek Labian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20170906/1a5e2b42/attachment.html>


More information about the foundry-nsp mailing list