[f-nsp] Does VRF still take CAM resources from 'ipv4 vpn' in later MLXe code?

[David Hubbard]

Hey all, in 2014 I ran into an issue where I converted an MLXe to the ipv4-ipv6-2 profile to get maximum routes for both.  When I did that, I lost management access because I use management VRF’s, and those require resources from the ‘IPv4 VPN’ segment of CAM.  The ipv4-ipv6-2 profile sets that to zero.  So, I switched to multi-service-4 as a workaround since it still had enough room.

Fast forward two years and IPv6 adoption has increased to the point where an MLXe with –X cards is just about out of CAM if it’s acting as an internet router and using the multi-service-4 profile.  Starting to see these alerts:

Aug 31 11:51:10:A:CAM IPv6 partition warning: total 32768 (reserved 0), free 1602, slot 3, ppcr 1

because internet routers are seeing roughly 31,000 IPv6 advertisements now and multi-service-4 only has room for 32k.

At the time, there was no way to configure custom CAM values, such as my desired goal of 768k minus 1 ipv4, 64k ipv6, 1 IPv4 VPN to facilitate one VRF.  I didn’t want to use ipv4-ipv6-2 either since I like having the VRF.

Is there any workaround for this issue in later code releases?

Thanks,

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20160831/2fdd8374/attachment.html>