<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1<br><br><br></div><div><br>Le 12 mai 2013 à 04:31, "David Unfried" <<a href="mailto:dunfried@linkline.com">dunfried@linkline.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We recently deployed our first CER in production. Our SE told us we needed a CER-RT with “Advanced Services Premium” to do both on the same box, which was a requirement. <o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We were steered away from the CES at the mention of full BGP routes and MPLS as requirements.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">“show ver” on our box indicates :</span> <span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">License: RT_SCALE, ADV_SVCS_PREM<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We are doing several full transit peers, a few down -stream customers, full internal mesh, and 80+ non-transit peers on this box and it doesn’t break a sweat.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My take is Brocade has crippled the CER/CES especially base versions as they don’t want to cannibalize MLXe sales. That is understandable, my concern is some of the documentation and pre-sales information was vague to confusing as to what supports what, and until you gain support access and dig into magic “system-max” options, some of the default limits out of the box are incredibly low, and might lead someone to worry the box won’t do what it was purchased to do.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> foundry-nsp [<a href="mailto:foundry-nsp-bounces@puck.nether.net">mailto:foundry-nsp-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Jon Maiman<br><b>Sent:</b> Saturday, May 11, 2013 5:14 PM<br><b>To:</b> Aaron Wendel<br><b>Cc:</b> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br><b>Subject:</b> Re: [f-nsp] mpls + bgp support on NI CES2K<o:p></o:p></span></p></div><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal">Nick, Matt, Aaron,<o:p></o:p></p></div><div><p class="MsoNormal">You can do both BGP and MPLS on a CES with the caveat that the FIB size is smaller (as expected). To do both on the CES, you need both the Layer 4 Premium and the Metro Edge Premium software upgrade licenses installed on the same switch. The CER licensing model is different.<o:p></o:p></p></div><div><p class="MsoNormal">Cheers,<o:p></o:p></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Jon (who works for Brocade)<br><br><o:p></o:p></p></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>foundry-nsp mailing list</span><br><span><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a></span><br><span><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></span></div></blockquote></body></html>