<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">I suspect you may need to use multi-service-4 to give cam resources for IPv4 VPN (or whatever profile fits your needs that contains IPv4/6 VPN). The ipv4-ipv6-2 has no
IPv4 VPN or IPv6 VPN resources allocated in it. See if that works.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">-Vinny</span><o:p></o:p></p>
<p>---Original Message-----<br>
From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of David Hubbard<br>
Sent: Thursday, August 7, 2014 3:04 PM<br>
To: foundry-nsp@puck.nether.net<br>
Subject: Re: [f-nsp] CAM IP partition warning - Error Help MLXe X 1 million routes<br>
<br>
Would a cam profile change affect layer 3 services in a VRF? :-) <br>
<br>
I just switched a test router to ipv4-ipv6-2 from default and lost my management access via network. I have a management vrf defined with a gig port member since the management port can't be in a management vrf in the code version I'm running. After the reload,
the router still responds to arp requests but won't talk ssh, snmp or ntp, which are the only services I have enabled, or respond to ping. All the normal stuff not in the vrf came up fine (bgp & ospf).<br>
<br>
-----Original Message-----<br>
From: James Cornman [mailto:james@atlanticmetro.net]<br>
Sent: Thursday, August 07, 2014 1:21 PM<br>
To: David Hubbard<br>
Cc: foundry-nsp@puck.nether.net<br>
Subject: Re: [f-nsp] CAM IP partition warning - Error Help MLXe X 1 million routes<br>
<br>
David,<br>
<br>
I think ipv4-ipv6 is there really to preserve prior deployments that may justify any adjustments to the cam-profile. I haven't found anyone who uses that for any new deployments, unless its just for testing or just very basic layer3.
<br>
<br>
In most cases ipv4-ipv6-2 or multi-service-4 (or whatever its called) seem the most attractive in comparison. This is all in reference to XMR/MLXe. MLX itself (with or with out -X cards), is a different story.<br>
<br>
Also, I think the cards state that they support 1million routes, but I don't think there is a cam profile for exactly 1million routes for IPv4..the rest of the capabilities get spread across ipv4/mpls/mac address/acl's, etc.
<br>
<br>
SSH@router#show mod | inc S2<br>
S2: BR-MLX-10Gx4-X 4-port 10GbE Module<br>
CARD_STATE_UP <br>
SSH@router#show cam-partition usage slot 2<br>
<br>
CAM partitioning profile: ipv4-ipv6-2<br>
<br>
Slot 2 XPP20SP 0:<br>
[IP] 786432(size), 282381(free), 064.09%(used)<br>
<br>
-James<br>
<br>
<br>
On Thu, Aug 7, 2014 at 12:39 PM, David Hubbard wrote:<br>
<br>
<br>
Is there a table that shows the values that are used for -X cards with<br>
the ipv4-ipv6 and ipv4-ipv6-2 profiles? Only one I could find seems to<br>
be for the normal cards<br>
<br>
http://www.brocade.com/downloads/documents/html_product_manuals/NI_05600<br>
<br>
_ADMIN/wwhelp/wwhimpl/common/html/wwhelp.htm#href=CAM_part.11.2.html&sin<br>
gle=true<br>
0<br>
_ADMIN/wwhelp/wwhimpl/common/html/wwhelp.htm#href=CAM_part.11.2.html&sin<br>
gle=true> <br>
<br>
Trying to understand when you'd want to use ipv4-ipv6 vs<br>
ipv4-ipv6-2<br>
<br>
Thanks,<br>
<br>
David<br>
<br>
-----Original Message-----<br>
From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net]<br>
On Behalf<br>
Of Mike Tindle<br>
Sent: Wednesday, August 06, 2014 11:01 PM<br>
To: James B; foundry-nsp@puck.nether.net<br>
Subject: Re: [f-nsp] CAM IP partition warning - Error Help MLXe X 1<br>
million routes<br>
<br>
James,<br>
<br>
Did you also change the cam-partiion profile you are using?<br>
<br>
router#sh cam-part | i profile<br>
CAM partitioning profile: ipv4-ipv6-2<br>
<br>
If you're using the default profile, it will still have the tcam carved<br>
for 512k IPv4 routes.<br>
<br>
Also, updating the cam profile takes a reload.<br>
<br>
Regards,<br>
Mike<br>
<br>
On Aug 6, 2014, at 7:23 PM, James B wrote:<br>
<br>
<br>
<br>
Hi All<br>
<br>
We are using both 5.3d and 5.4d on different devices and getting<br>
the same errors on different MLXe X platform, which should support 1<br>
million routes.<br>
<br>
CAM IP partition warning: total 524288 (reserved 0), free 26214,<br>
slot 3, ppcr 1<br>
<br>
However we have increased the ip-route and ip-cache cam to<br>
maximum:<br>
<br>
System Parameters Default Maximum Current<br>
Actual<br>
Bootup Revertible<br>
mac 131072 2097152 131072<br>
131072<br>
131072 Yes<br>
vlan 512 4095 1024<br>
1024<br>
1024 No<br>
spanning-tree 32 128 32<br>
32<br>
32 No<br>
rstp 32 128 32<br>
32<br>
32 No<br>
ip-arp 8192 65536 8192<br>
8192<br>
8192 No<br>
ip-cache 204800 1048576 1048576<br>
1048576 1048576 Yes<br>
ip-route 204800 1048576 1048576<br>
1048576 1048576 Yes<br>
<br>
<br>
Whilst the error is for 500k routes the maximum is set to 1<br>
million routes, what could be causing these errors ?<br>
<br>
Thanks<br>
<br>
James<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
foundry-nsp@puck.nether.net<br>
http://puck.nether.net/mailman/listinfo/foundry-nsp<br>
<br>
<br>
*----------- H U R R I C A N E - E L E C T R I C ---------->><br>
| Mike Tindle | Senior Network Engineer | mtindle@he.net ASN<br>
6939 |<br>
| http://www.he.net | 510-580-4126<br>
*--------------------------------------------------->><br>
<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
foundry-nsp@puck.nether.net<br>
http://puck.nether.net/mailman/listinfo/foundry-nsp<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
<br>
<br>
James Cornman<br>
<br>
Chief Technology Officer<br>
jcornman@atlanticmetro.net <br>
212.792.9950 - ext 101<br>
<br>
Atlantic Metro Communications, Inc.<br>
<br>
4 Century Drive, Parsippany NJ 07054<br>
<br>
<br>
Data Centers * Managed Hosting * Internet Access * Cloud Computing Follow @atlanticmetro on Twitter to learn more about daily specials.<br>
www.atlanticmetro.net <br>
<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
foundry-nsp@puck.nether.net<br>
http://puck.nether.net/mailman/listinfo/foundry-nsp<o:p></o:p></p>
</div>
</body>
</html>