<div dir="ltr"><div><div><div>Hi Clement :-)<br><br>Sur, I thought of that. But knowing sales guys in my company, someone at some point will have the brilliant idea of selling an L3VPN and then I will be sc*$€wed.<br></div><br></div>So, I'm trying to be creative here.... But I think my options are rather limited.<br><br></div>BR.<br><br><br><div><div><div> <br><div class="gmail_extra"><br><div class="gmail_quote">2017-06-14 8:08 GMT+02:00 Clement Cavadore <span dir="ltr"><<a href="mailto:clement@cavadore.net" target="_blank">clement@cavadore.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'd rather change my management method and switch to ipv4-ipv6-2 :-)<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, 2017-06-14 at 01:02 +0200, Youssef Bengelloun-Zahr wrote:<br>
> Dear Daniel,<br>
><br>
> Is this really the only option ?<br>
><br>
> Either shrinking the DFZ or upgrade to newer LPs ?<br>
><br>
> Thank you.<br>
><br>
><br>
><br>
> > Le 14 juin 2017 à 00:37, Daniel Schmidt <<a href="mailto:daniel.schmidt@wyo.gov">daniel.schmidt@wyo.gov</a>> a écrit :<br>
> ><br>
> > No one really. My 2 cents:<br>
> ><br>
> > Use option #1, have each provider send you an additional default, and do an ASN filter list with a little help from this:<br>
> > <a href="https://github.com/ipcjk/asnbuilder" rel="noreferrer" target="_blank">https://github.com/ipcjk/<wbr>asnbuilder</a><br>
> ><br>
> >> On Tue, Jun 13, 2017 at 3:07 PM, Youssef Bengelloun-Zahr <<a href="mailto:bengelly@gmail.com">bengelly@gmail.com</a>> wrote:<br>
> >> No one ? Really ?!?<br>
> >><br>
> >> Y.<br>
> >><br>
> >><br>
> >><br>
> >>> Le 13 juin 2017 à 10:05, Youssef Bengelloun-Zahr <<a href="mailto:bengelly@gmail.com">bengelly@gmail.com</a>> a écrit :<br>
> >>><br>
> >>> Dear Foundry community,<br>
> >>><br>
> >>> I'm about to revive an old trolly thread, but boy are they fun.<br>
> >>><br>
> >>> 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>
> >>> We receive full BGP feeds from multiple IP transit providers and YES, we DO filter prefixes over a /48 size.<br>
> >>><br>
> >>> 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>
> >>> 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>
> >>> 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" rel="noreferrer" target="_blank">http://www.brocade.com/<wbr>content/html/en/<wbr>administration-guide/netiron-<wbr>05900-adminguide/GUID-<wbr>F5A27733-F4A2-4367-8F83-<wbr>E8A4C3DE6F0E.html</a><br>
> >>><br>
> >>> We only use MPLS VRF for management prurposes. So, we are left with either :<br>
> >>><br>
> >>> - Heavily filtering IPv6 bgp feeds + accepting a defaut route in order to get 1 MPLS VRF for management purposes,<br>
> >>><br>
> >>> - Accepting full IPv6 BGP feed by migrating to ipv4-ipv6-2 Profile, and loose MPLS VRF.<br>
> >>><br>
> >>> 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>
> >>> Other than that, how do you guys handle this ? Maybe a nifty trick I'm not aware of ?<br>
> >>><br>
> >>> Thank you for your wisdom.<br>
> >>><br>
> >>> Best regards.<br>
> >><br>
> >> ______________________________<wbr>_________________<br>
> >> foundry-nsp mailing list<br>
> >> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> >> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/<wbr>mailman/listinfo/foundry-nsp</a><br>
> ><br>
> ><br>
> ><br>
> > E-Mail to and from me, in connection with the transaction<br>
> > of public business, is subject to the Wyoming Public Records<br>
> > Act and may be disclosed to third parties.<br>
> ______________________________<wbr>_________________<br>
> foundry-nsp mailing list<br>
> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/<wbr>mailman/listinfo/foundry-nsp</a><br>
<br>
<br>
</div></div></blockquote></div><br></div></div></div></div></div>