[f-nsp] CAM IP partition warning - Error Help MLXe X 1 million routes

Thu Aug 7 15:56:26 EDT 2014

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.

-Vinny

---Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of David Hubbard
Sent: Thursday, August 7, 2014 3:04 PM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] CAM IP partition warning - Error Help MLXe X 1 million routes

Would a cam profile change affect layer 3 services in a VRF? :-)

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).

-----Original Message-----
From: James Cornman [mailto:james at atlanticmetro.net]
Sent: Thursday, August 07, 2014 1:21 PM
To: David Hubbard
Cc: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] CAM IP partition warning - Error Help MLXe X 1 million routes

David,

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.

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.

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.

SSH at router#show mod | inc S2
S2: BR-MLX-10Gx4-X 4-port 10GbE Module
CARD_STATE_UP
SSH at router#show cam-partition usage slot 2

CAM partitioning profile: ipv4-ipv6-2

Slot 2 XPP20SP 0:
[IP] 786432(size), 282381(free), 064.09%(used)

-James

On Thu, Aug 7, 2014 at 12:39 PM, David Hubbard wrote:

Is there a table that shows the values that are used for -X cards with
the ipv4-ipv6 and ipv4-ipv6-2 profiles? Only one I could find seems to
be for the normal cards

http://www.brocade.com/downloads/documents/html_product_manuals/NI_05600

_ADMIN/wwhelp/wwhimpl/common/html/wwhelp.htm#href=CAM_part.11.2.html&sin
gle=true
0
_ADMIN/wwhelp/wwhimpl/common/html/wwhelp.htm#href=CAM_part.11.2.html&sin
gle=true>

Trying to understand when you'd want to use ipv4-ipv6 vs
ipv4-ipv6-2

Thanks,

David

-----Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net]
On Behalf
Of Mike Tindle
Sent: Wednesday, August 06, 2014 11:01 PM
To: James B; foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] CAM IP partition warning - Error Help MLXe X 1
million routes

James,

Did you also change the cam-partiion profile you are using?

router#sh cam-part | i profile
CAM partitioning profile: ipv4-ipv6-2

If you're using the default profile, it will still have the tcam carved
for 512k IPv4 routes.

Also, updating the cam profile takes a reload.

Regards,
Mike

On Aug 6, 2014, at 7:23 PM, James B wrote:

Hi All

We are using both 5.3d and 5.4d on different devices and getting
the same errors on different MLXe X platform, which should support 1
million routes.

CAM IP partition warning: total 524288 (reserved 0), free 26214,
slot 3, ppcr 1

However we have increased the ip-route and ip-cache cam to
maximum:

System Parameters Default Maximum Current
Actual
Bootup Revertible
mac 131072 2097152 131072
131072
131072 Yes
vlan 512 4095 1024
1024
1024 No
spanning-tree 32 128 32
32
32 No
rstp 32 128 32
32
32 No
ip-arp 8192 65536 8192
8192
8192 No
ip-cache 204800 1048576 1048576
1048576 1048576 Yes
ip-route 204800 1048576 1048576
1048576 1048576 Yes

Whilst the error is for 500k routes the maximum is set to 1
million routes, what could be causing these errors ?

Thanks

James

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

*----------- H U R R I C A N E - E L E C T R I C ---------->>
| Mike Tindle | Senior Network Engineer | mtindle at he.net ASN
6939 |
| http://www.he.net | 510-580-4126
*--------------------------------------------------->>

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

--

James Cornman

Chief Technology Officer
jcornman at atlanticmetro.net
212.792.9950 - ext 101

Atlantic Metro Communications, Inc.

4 Century Drive, Parsippany NJ 07054

Data Centers * Managed Hosting * Internet Access * Cloud Computing Follow @atlanticmetro on Twitter to learn more about daily specials.
www.atlanticmetro.net

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20140807/fba13f2a/attachment.html>