None of the cam-partition commands are even supported on the CER, so I'm
not sure how to even begin to look at utilization. The only real
commands related to this are 'show cam l4 SLOT/PORT', which doesn't
really tell me a whole lot.
I've checked that our route counts are below what we have defined in
system-max... if there's another limit here it's not well documented.
On 9/6/2017 3:43 PM, Derek wrote:
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 <[email protected]
<mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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
[email protected] <mailto:[email protected]>
http://puck.nether.net/mailman/listinfo/foundry-nsp
<http://puck.nether.net/mailman/listinfo/foundry-nsp>
--
Be Well,
Derek Labian
--
Be Well,
Derek Labian
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
