<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto">That's probably a reason, also the X2 card pricing is not so attractive. I also wonder when / if they will start a trade-in program for MLX to SLX, but seems they missed this opportunity with existing clients already. :(</p>
<p dir="auto">Additionally the SLX9850/9540 got its 1.5M route update late (March 2018?) and the SLX9640 is kind of being late to the party, too (but still a cool product!), so that we went for the SLX9540 for peering locations (and they needed 3 months to ship … ).</p>
<p dir="auto">For one point I thought that some kind of adapter card, that makes X2 cards work inside the SLX chassis, would protect a future investment and also running the power-pc based NetIron-OS inside the KVM hypervisor would be neat.</p>
<p dir="auto">I also think that marketing or product management of the former Brocade products are (purposely?) pretty weak and besides they are talking about inside architecture or visibility (SLX) platform, the hardware products are hardly visible or known at all. The last one-day sales presentation I have attended a year after the transition, they didn't even mention former "Brocade" products and talked about Extreme becoming THE "software / analytics vendor" for generic network devices… </p>
<p dir="auto">Well, what about being both? A software vendor and a hardware vendor (with touch control… )? The Brocade buy-out was such a steal and then they forgot to bring the customers into a safe harbor. Still to be mentioned that the whole Broadcom-Brocade-Qualcomm-US-Government disaster may had its own impact, too. </p>
<p dir="auto">So what they really need is a momentum shift. Bring the SLX-line out on the road where it matters and it can work, sponsor the right events, understand why people currently don't choose the products and work on this issues, show valid upgrade paths for current customers and develop a strategy for not loosing more customers to other vendors, advance the development (5 months for a critical bug?) and hand out the Brocade strategy behind 2020.</p>
<p dir="auto">Jörg</p>
<br><p dir="auto">On 28 Jan 2019, at 22:06, i3D.net - Martijn Schmidt wrote:</p>
</div>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div id="2714BD21-D57D-45F6-B997-E74CAED05A27">
I think everyone is phasing out their X-scalability hardware in anticipation of the global routing table growing larger than 786k IPv4 routes. These boxes don't have a long life ahead of them as a DFZ router, unless you only use X2-scalability cards in your
chassis.. and with operators essentially being forced to upgrade to a completely different platform (SLX or $other_vendor), Brextreme's advantage of being the incumbent vendor in the network is pretty much completely negated.<br>
<br>
Finally, as a BDA, let me tell you that being stabbed in the back when it comes to my certification record has not benefited my opinion of the new owner(s) of the Brocade diaspora. Why they decided to not only pull the plug on the entire Brocade education program,
but also delete the historical certification database from CertMetrics, is beyond me. It has become impossible to check the validity of years' worth of Brocade credentials.
<br>
<br>
Best regards,<br>
Martijn <br>
<br>
<div class="gmail_quote">On 28 January 2019 21:35:56 CET, Youssef Bengelloun-Zahr <bengelly@gmail.com> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Nope, just very little chatter.<br><br>BR.<br><br><br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Le 28 janv. 2019 à 20:32, joe mcguckin <joe@via.net> a écrit :<br><br>Is there a new list for Foundry/Brocade/Extreme?<br><br>Thanks,<br><br>joe<br><br><br>Joe McGuckin<br>ViaNet Communications<br><br>joe@via.net<br>650-207-0372 cell<br>650-213-1302 office<br>650-969-2124 fax<hr>foundry-nsp mailing list<br>foundry-nsp@puck.nether.net<br><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br></blockquote><hr>foundry-nsp mailing list<br>foundry-nsp@puck.nether.net<br><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br></pre>
</blockquote>
</div>
<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></blockquote>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">_______________________________________________<br>
foundry-nsp mailing list<br>
foundry-nsp@puck.nether.net<br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" style="color:#777">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></p>
</blockquote></div>
</div>
</body>
</html>