<div dir="ltr"><div>Hello,<br><br></div>For those interested, I had our SE open an RFE in order to request a new CAM profile : <span style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;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;display:inline;float:none">PRODRFE104462</span><div class="gmail_extra"><br></div><div class="gmail_extra">If you are intersted, I would highly suggest you push this with your local SE. We all know what the odds of this happening, but you never know.<br><br></div><div class="gmail_extra">Best regards.<br></div><div class="gmail_extra"><br><br><br><div class="gmail_quote">2017-06-14 10:05 GMT+02:00 Youssef Bengelloun-Zahr <span dir="ltr"><<a href="mailto:bengelly@gmail.com" target="_blank">bengelly@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Clement,<br><br>That is so very true. Still, that doesn't always work.<br><div><div><br>I also like the idea of threatening your favorite $$$$ vendor to throw away their gear on the curve, even if we all know that it won't help.<br><br></div><div>But that's another story, let's remain civilized and polite publically ;-)<br><br></div><div>Best regards.<br><br><br></div></div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-06-14 9:13 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">Hi Youssef,<br>
<br>
Sales peoples are like young kids: You have to raise them and let them<br>
understand what they can or cannot sell :). And if they'd still insist<br>
to sell L3VPN, they'll have to ask the management to buy you some brand<br>
new toys :-)<br>
<br>
Clément<br>
<div class="m_-8899003614209983172HOEnZb"><div class="m_-8899003614209983172h5"><br>
On Wed, 2017-06-14 at 09:01 +0200, Youssef Bengelloun-Zahr wrote:<br>
> Hi Clement :-)<br>
><br>
> Sur, I thought of that. But knowing sales guys in my company, someone at<br>
> some point will have the brilliant idea of selling an L3VPN and then I will<br>
> be sc*$€wed.<br>
><br>
> So, I'm trying to be creative here.... But I think my options are rather<br>
> limited.<br>
><br>
> BR.<br>
><br>
><br>
><br>
><br>
> 2017-06-14 8:08 GMT+02:00 Clement Cavadore <<a href="mailto:clement@cavadore.net" target="_blank">clement@cavadore.net</a>>:<br>
><br>
> > I'd rather change my management method and switch to ipv4-ipv6-2 :-)<br>
> ><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" target="_blank">daniel.schmidt@wyo.gov</a>> a<br>
> > écrit :<br>
> > > ><br>
> > > > No one really. My 2 cents:<br>
> > > ><br>
> > > > Use option #1, have each provider send you an additional default, and<br>
> > 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/asnbu<wbr>ilder</a><br>
> > > ><br>
> > > >> On Tue, Jun 13, 2017 at 3:07 PM, Youssef Bengelloun-Zahr <<br>
> > <a href="mailto:bengelly@gmail.com" target="_blank">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" target="_blank">bengelly@gmail.com</a>><br>
> > 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<br>
> > the following syslog error message on our MLXe gear :<br>
> > > >>><br>
> > > >>> Jun 13 07:51:02:A:CAM IPv6 partition warning: total 32768 (reserved<br>
> > 0), free 6, slot 2, ppcr 1<br>
> > > >>> Jun 13 07:51:02:A:CAM IPv6 partition warning: total 32768 (reserved<br>
> > 0), free 6, slot 2, ppcr 0<br>
> > > >>><br>
> > > >>> We receive full BGP feeds from multiple IP transit providers and<br>
> > 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<br>
> > Status Ports Starting MAC<br>
> > > >>> M1 (left ):BR-MLX-MR2-X Management Module<br>
> > Standby(Ready State)<br>
> > > >>> M2 (right):BR-MLX-MR2-X Management Module<br>
> > Active<br>
> > > >>> F1: NI-X-HSF Switch Fabric Module<br>
> > Active<br>
> > > >>> F2: NI-X-HSF Switch Fabric Module<br>
> > Active<br>
> > > >>> F3: NI-X-HSF Switch Fabric Module<br>
> > Active<br>
> > > >>> S1: BR-MLX-10Gx4-X 4-port 10GbE Module<br>
> > CARD_STATE_UP 4 0024.38a4.fb00<br>
> > > >>> S2: BR-MLX-10Gx4-X 4-port 10GbE Module<br>
> > CARD_STATE_UP 4 0024.38a4.fb30<br>
> > > >>> S3: BR-MLX-1GFx24-X 24-port 1GbE SFP Module<br>
> > CARD_STATE_UP 24 0024.38a4.fb60<br>
> > > >>> S4: BR-MLX-1GFx24-X 24-port 1GbE SFP Module<br>
> > CARD_STATE_UP 24 0024.38a4.fb90<br>
> > > >>><br>
> > > >>> For years, we have been using multi-service-4 CAM profil in order to<br>
> > provide pure IP connectivity and MPLS connectivity (mostly VPLS) to our<br>
> > clients.<br>
> > > >>><br>
> > > >>> After investigating with BTAC, they told us that our hardware<br>
> > couldn't handle much more 32k with this profil :<br>
> > > >>><br>
> > > >>> <a href="http://www.brocade.com/content/html/en/administration-guide/netiron-" rel="noreferrer" target="_blank">http://www.brocade.com/content<wbr>/html/en/administration-guide/<wbr>netiron-</a><br>
> > 05900-adminguide/GUID-F5A27733<wbr>-F4A2-4367-8F83-E8A4C3DE6F0E.<wbr>html<br>
> > > >>><br>
> > > >>> We only use MPLS VRF for management prurposes. So, we are left with<br>
> > either :<br>
> > > >>><br>
> > > >>> - Heavily filtering IPv6 bgp feeds + accepting a defaut route in<br>
> > order to get 1 MPLS VRF for management purposes,<br>
> > > >>><br>
> > > >>> - Accepting full IPv6 BGP feed by migrating to ipv4-ipv6-2 Profile,<br>
> > and loose MPLS VRF.<br>
> > > >>><br>
> > > >>> I seem to recall that someone on this list has been pushing Brocade<br>
> > to create a special profile to accomodate a very little number of MPLS<br>
> > VRFs. Did that happen ?<br>
> > > >>><br>
> > > >>> Other than that, how do you guys handle this ? Maybe a nifty trick<br>
> > 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" target="_blank">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/mailman<wbr>/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" target="_blank">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/mailman<wbr>/listinfo/foundry-nsp</a><br>
> ><br>
> ><br>
> ><br>
<br>
<br>
</div></div></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div>