<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On the CER, the equivalent of "show cam-partition usage" is "show
resource". I believe the IP entries include both IPv4 & IPv6.<br>
<br>
"show default values" is also useful because you can see if your
"system-max ipv6-route" is high enough - the default is only 8192
and your IPv6 DFZ table obviously won't fit if your system-max is
set to such a low value. We tend to run it at 262144 because
system-max is a fairly pointless feature anyway, it doesn't carve up
your CAM, just restricts certain features from over-consuming
resources that are shared with different features.<br>
<br>
And, of course, after messing around with system-max you're going to
have to reload the device to apply the new settings.<br>
<br>
Best regards,<br>
Martijn<br>
<br>
<div class="moz-cite-prefix">On 06-09-17 21:53, Brian Rak wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f168d2ac-cb47-a02f-684f-1a81db0b1be8@gameservers.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>What sort of resource limits are you running into here? Did
you find any sort of workaround, or are you just reloading all
the time?<br>
</p>
<br>
<div class="moz-cite-prefix">On 9/6/2017 3:45 PM, Youssef
Bengelloun-Zahr wrote:<br>
</div>
<blockquote type="cite"
cite="mid:10A476D2-1EE9-4F74-A047-B324A1DA43D1@gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<div>Been there, suffer from it everyday.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">They might not have CAM profiles
ala MLXe, but they still have CAMs... so they have limited and
counted ressources.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Best regards.<br>
<br>
<br>
</div>
<div><br>
Le 6 sept. 2017 à 21:37, Brian Rak <<a
href="mailto:brak@gameservers.com" moz-do-not-send="true">brak@gameservers.com</a>>
a écrit :<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p>CER's don't have CAM profiles. From the information I
can find, they don't actually use TCAM anyway.<br>
</p>
<br>
<div class="moz-cite-prefix">On 9/6/2017 3:32 PM, Derek
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGKcJgBt4yw7Xin2i6zQMpxLcGz2NusjDxrR67xEXjoPXyJc7Q@mail.gmail.com">
<div dir="ltr">Did you check the CAM utilization? It's
probably full, perhaps you can partition it differently.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Sep 6, 2017 at 2:30 PM,
Brian Rak <span dir="ltr"><<a
href="mailto:brak@gameservers.com" target="_blank"
moz-do-not-send="true">brak@gameservers.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">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:<br>
<br>
IPv6 Route ADD: CAM entry creation FAILED<br>
IPv4 Network Route ADD: CAM entry creation FAILED<br>
<br>
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.<br>
<br>
Any ideas for what may be causing this? We're on
5.6.0m right now.<br>
<br>
______________________________<wbr>_________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net"
target="_blank" moz-do-not-send="true">foundry-nsp@puck.nether.net</a><br>
<a
href="http://puck.nether.net/mailman/listinfo/foundry-nsp"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://puck.nether.net/mailman<wbr>/listinfo/foundry-nsp</a></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">Be Well,
<div><br>
</div>
<div>Derek Labian</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>foundry-nsp mailing list</span><br>
<span><a href="mailto:foundry-nsp@puck.nether.net"
moz-do-not-send="true">foundry-nsp@puck.nether.net</a></span><br>
<span><a
href="http://puck.nether.net/mailman/listinfo/foundry-nsp"
moz-do-not-send="true">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></span></div>
</blockquote>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
foundry-nsp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div style="font-family: arial; font-size: 12px; vertical-align:
text-top;">Met vriendelijke groet / Kindest regards,
<br>
Martijn Schmidt</div>
<br>
<br>
<table height="185" width="600">
<tbody>
<tr>
<td>
<img
src="http://static.i3d.net/assets/images/i3Dlogo-email.png"
alt="i3D.net performance hosting" height="138"
width="251">
</td>
<td>
<div style="font-family: arial; font-size: 12px;
vertical-align: text-top;">
<b style="font-size: 18px;">Martijn Schmidt | Network
Architect</b><br>
Email: <a href="mailto://martijnschmidt@i3d.net">martijnschmidt@i3d.net</a>
| Tel: +31 10 8900070<br>
<br>
<b>i3D.net B.V. | Global Backbone AS49544</b><br>
Rivium 1e Straat 1, 2909 LE Capelle aan den IJssel, The
Netherlands<br>
VAT: NL 8202.63.886.B01<br>
<br>
<a class="one"
href="http://www.i3d.net/?utm_source=emailsignature&utm_medium=email&utm_campaign=home">Website</a>
|
<a class="one"
href="http://www.i3d.net/partners/?utm_source=emailsignature&utm_medium=email&utm_campaign=case-studies">Case
Studies</a> |
<a class="one"
href="https://www.linkedin.com/company/i3d-net">LinkedIn</a>
</div>
</td>
<td valign="top">
<br>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>