<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>No one ? Really ?!?</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Y.<br><br><br></div><div><br>Le 13 juin 2017 à 10:05, Youssef Bengelloun-Zahr <<a href="mailto:bengelly@gmail.com">bengelly@gmail.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div>Dear Foundry community,<br><br></div>I'm about to revive an old trolly thread, but boy are they fun.<br><br></div>With the growth of IPv6 DFZ over 32K entries, we have been receiving the following syslog error message on our MLXe gear :<br><br>Jun 13 07:51:02:A:CAM IPv6 partition warning: total 32768 (reserved 0), free 6, slot 2, ppcr 1<br>Jun 13 07:51:02:A:CAM IPv6 partition warning: total 32768 (reserved 0), free 6, slot 2, ppcr 0<br><br></div><div>We receive full BGP feeds from multiple IP transit providers and YES, we DO filter prefixes over a /48 size.<br></div><div><br></div>Our MLXe act as MPLS PEs and run the following hardware on NI58g :<br><br>Module Status Ports Starting MAC <br>M1 (left ):BR-MLX-MR2-X Management Module Standby(Ready State)<br>M2 (right):BR-MLX-MR2-X Management Module Active <br>F1: NI-X-HSF Switch Fabric Module Active <br>F2: NI-X-HSF Switch Fabric Module Active <br>F3: NI-X-HSF Switch Fabric Module Active <br>S1: BR-MLX-10Gx4-X 4-port 10GbE Module CARD_STATE_UP 4 0024.38a4.fb00<br>S2: BR-MLX-10Gx4-X 4-port 10GbE Module CARD_STATE_UP 4 0024.38a4.fb30<br>S3: BR-MLX-1GFx24-X 24-port 1GbE SFP Module CARD_STATE_UP 24 0024.38a4.fb60<br>S4: BR-MLX-1GFx24-X 24-port 1GbE SFP Module CARD_STATE_UP 24 0024.38a4.fb90<br><br></div>For years, we have been using multi-service-4 CAM profil in order to provide pure IP connectivity and MPLS connectivity (mostly VPLS) to our clients.<br><br></div>After investigating with BTAC, they told us that our hardware couldn't handle much more 32k with this profil :<br><br><a href="http://www.brocade.com/content/html/en/administration-guide/netiron-05900-adminguide/GUID-F5A27733-F4A2-4367-8F83-E8A4C3DE6F0E.html" style="font-family:Calibri;font-size:14.6667px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><font color="#0563C1"><u>http://www.brocade.com/content/html/en/administration-guide/netiron-05900-adminguide/GUID-F5A27733-F4A2-4367-8F83-E8A4C3DE6F0E.html</u></font></a><br><br></div>We only use MPLS VRF for management prurposes. So, we are left with either :<br><br></div>- Heavily filtering IPv6 bgp feeds + accepting a defaut route in order to get 1 MPLS VRF for management purposes,<br><br></div>- Accepting full IPv6 BGP feed by migrating to ipv4-ipv6-2 Profile, and loose MPLS VRF.<br><br></div>I seem to recall that someone on this list has been pushing Brocade to create a special profile to accomodate a very little number of MPLS VRFs. Did that happen ?<br><br></div>Other than that, how do you guys handle this ? Maybe a nifty trick I'm not aware of ?<br><br></div>Thank you for your wisdom.<br><br></div>Best regards.<br></div>
</div></blockquote></body></html>