<div dir="ltr">John,<div><br></div><div>Is this only for particular line cards? Or are you seeing problems from all cards?</div><div><br></div><div>I've not actually done a stare and compare of CLI/SNMP/SFLOW on 5.6.0c, it just appeared to be right. (5.6.0b most definitely was not)</div>
<div><br></div><div>-Josh</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 14, 2014 at 7:01 PM, John W. O'Brien <span dir="ltr"><<a href="mailto:obrienjw@upenn.edu" target="_blank">obrienjw@upenn.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 8/12/14 4:25 AM, Youssef Bengelloun-Zahr wrote:<br>
> Hello,<br>
><br>
> Has anyone tried it yet ? I was planning to do so when I come back next<br>
> week but any early feedbacks will be appreciated.<br>
><br>
> Best regards.<br>
<br>
</div>This week we upgraded five MLXe-16 routers in our core from 5.4.00d* to<br>
5.6.00d. It looks like there is an sFlow export regression in this code<br>
that we didn't pick up during our lab validation. At least one obvious<br>
problem I've identified so far by looking at raw sFlow data is that the<br>
input and output packet counters are lower by about a factor of 3 than<br>
the corresponding counters in the CLI and in the SNMP ifXTable (which<br>
agree with each other). We've contacted Brocade and I would be glad to<br>
follow up here when we resolve the issue.<br>
<br>
I'm really hoping we can solve it without another hit-full code change.<br>
<br>
* Actually a CVR with a work-around for DEFECT000508412---the main<br>
reason we chose to upgrade---which is fixed in 5.6.00d.<br>
<br>
> Le 1 août 2014 à 02:09, James Braunegg <<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a><br>
> <mailto:<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a>>> a écrit :<br>
><br>
>> Who wants to test it….<br>
>><br>
>><br>
>><br>
>> Kindest Regards<br>
>><br>
>><br>
>><br>
>> *James Braunegg<br>
>> **P:* 1300 769 972 | *M:* 0488 997 207 | *D:* (03) 9751 7616<br>
>><br>
>> *E:* <a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a><br>
>> <mailto:<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a>> | *ABN:* <a href="tel:12%20109%20977%20666" value="+12109977666">12 109 977 666</a><br>
>> *W:* <a href="http://www.micron21.com/ddos-protection" target="_blank">www.micron21.com/ddos-protection</a><br>
>> <<a href="http://www.micron21.com/ddos-protection" target="_blank">http://www.micron21.com/ddos-protection</a>> *T:* @micron21<br>
<div class="">>><br>
>><br>
>><br>
>><br>
>> <image001.jpg><br>
>> This message is intended for the addressee named above. It may contain<br>
>> privileged or confidential information. If you are not the intended<br>
>> recipient of this message you must not use, copy, distribute or<br>
>> disclose it to anyone other than the addressee. If you have received<br>
>> this message in error please return the message to the sender by<br>
>> replying to it and then delete the message from your computer.<br>
>><br>
>><br>
>><br>
</div>>> *From:*foundry-nsp [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] *On<br>
>> Behalf Of *Youssef Bengelloun-Zahr<br>
>> *Sent:* Friday, August 01, 2014 5:14 AM<br>
>> *To:* Skylar MacMinn<br>
>> *Cc:* <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br>
>> *Subject:* Re: [f-nsp] Netiron 5.6 feedbacks<br>
<div class="">>><br>
>><br>
>><br>
>> Hi all,<br>
>><br>
>> 560d is out :-)<br>
>><br>
>> Y.<br>
>><br>
>><br>
>><br>
>> 2014-07-18 15:47 GMT+02:00 Skylar MacMinn <<a href="mailto:skylar@crissic.net">skylar@crissic.net</a><br>
</div>>> <mailto:<a href="mailto:skylar@crissic.net">skylar@crissic.net</a>>>:<br>
<div class="">>><br>
>> Thanks for that update J<br>
>><br>
>><br>
>><br>
>> We updated to 5.6.0.c and have been fine with sflow since. Thanks<br>
>> again to everyone who helped point out the issue J<br>
>><br>
>><br>
>><br>
>> Cordially Yours,<br>
>><br>
>><br>
>><br>
>> Skylar MacMinn<br>
>><br>
</div>>> <a href="http://www.crissic.net" target="_blank">www.crissic.net</a> <<a href="http://www.crissic.net" target="_blank">http://www.crissic.net</a>><br>
>> Crissic Solutions, LLC<br>
>><br>
>><br>
>><br>
>> *From:*foundry-nsp [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a><br>
>> <mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>>] *On Behalf Of *Youssef<br>
>> Bengelloun-Zahr<br>
>> *Sent:* Friday, July 18, 2014 8:43 AM<br>
>> *To:* Josh Galvez<br>
>><br>
>><br>
>> *Cc:* <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br>
>> *Subject:* Re: [f-nsp] Netiron 5.6 feedbacks<br>
<div class="">>><br>
>><br>
>><br>
>> Hi,<br>
>><br>
>> Little update as 56d GA was postponed until July 31st.<br>
>><br>
>> Best regards.<br>
>><br>
>><br>
>><br>
>> 2014-06-20 21:29 GMT+02:00 Josh Galvez <<a href="mailto:josh@zevlag.com">josh@zevlag.com</a><br>
</div>>> <mailto:<a href="mailto:josh@zevlag.com">josh@zevlag.com</a>>>:<br>
<div class="">>><br>
>> Just an FYI, I've ran in to two rather annoying bugs it the 5.6<br>
>> line of code, this on the XMR.<br>
>><br>
>><br>
>><br>
>> in 5.6b (but fixed in 5.6c):<br>
>><br>
>><br>
>><br>
>> Defect ID: DEFECT000502305<br>
>><br>
>> Technical Severity: Medium Probability: High<br>
>><br>
>> Product: Multi-Service IronWare Technology: Management<br>
>><br>
>> Reported In Release: NI 05.6.00 Technology Area: SFLOW<br>
>><br>
>> Closed In Release(s): NI 05.6.00c(Fixed)<br>
>><br>
>> Symptom: An incorrect raw packet header length in the sFlow<br>
>> protocol is observed.<br>
>><br>
>> Condition: Issue is seen while running L3 traffic along while<br>
>> enabling sFlow on an interface. sFlow enabled<br>
>><br>
>> interfaces send sFlow data packets to an sFlow collector. At the<br>
>> collector the raw packet header<br>
>><br>
>> length is less than what was originally sent.<br>
>><br>
>><br>
>><br>
>> In 5.6c (not in 5.6b, no fix yet):<br>
>><br>
>> Defect 505978<br>
>> BGPv6 neighborship not coming up over loopback interfaces as the<br>
>> ipv6 TCP cpnnection is in SYN-SENT state.<br>
>> It will occur if you peer using loopback address with /128 mask.<br>
>> It will be fixed in 5.6d which is not released yet.<br>
>> Current workaround would be to not use /128 mask or to downgrade<br>
>> your code.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Mon, May 26, 2014 at 7:48 AM, James Braunegg<br>
</div>>> <<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a> <mailto:<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a>>><br>
<div class="">>> wrote:<br>
>><br>
>> Will be interesting to hear your feedback in a few months !!<br>
>><br>
>><br>
>><br>
</div>>> Was about to upgrade to 5.5 but maybe it’s worth the wait to<br>
<div class="">>> see how 5.6d is !!<br>
>><br>
>><br>
>><br>
>> Kindest Regards<br>
>><br>
>><br>
>><br>
</div>>> *James Braunegg<br>
>> **P:* 1300 769 972 | *M:* 0488 997 207 | *D:* (03) 9751 7616<br>
>><br>
>> *E:* <a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a><br>
>> <mailto:<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a>> | *ABN:* 12 109 977<br>
>> 666 <tel:12%20109%20977%20666><br>
>> *W:* <a href="http://www.micron21.com/ddos-protection" target="_blank">www.micron21.com/ddos-protection</a><br>
>> <<a href="http://www.micron21.com/ddos-protection" target="_blank">http://www.micron21.com/ddos-protection</a>> *T:* @micron21<br>
<div class="">>><br>
>><br>
>><br>
>><br>
>> <image001.jpg><br>
>> This message is intended for the addressee named above. It may<br>
>> contain privileged or confidential information. If you are not<br>
>> the intended recipient of this message you must not use, copy,<br>
>> distribute or disclose it to anyone other than the addressee.<br>
>> If you have received this message in error please return the<br>
>> message to the sender by replying to it and then delete the<br>
>> message from your computer.<br>
>><br>
>><br>
>><br>
</div>>> *From:*foundry-nsp [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a><br>
>> <mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>>] *On Behalf Of<br>
>> *Youssef Bengelloun-Zahr<br>
>> *Sent:* Monday, May 26, 2014 6:48 PM<br>
>><br>
>><br>
>> *To:* Wouter de Jong<br>
>> *Cc:* <<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
>> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>>><br>
>> *Subject:* Re: [f-nsp] Netiron 5.6 feedbacks<br>
<div class="">>><br>
>><br>
>><br>
>> Hi,<br>
>><br>
>> I hope this one will be more mature and stable :-)<br>
>><br>
>> Y.<br>
>><br>
>><br>
>><br>
>> 2014-05-26 10:26 GMT+02:00 Wouter de Jong <<a href="mailto:wouter@widexs.nl">wouter@widexs.nl</a><br>
</div>>> <mailto:<a href="mailto:wouter@widexs.nl">wouter@widexs.nl</a>>>:<br>
<div class="">>><br>
>> Hi Youssef,<br>
>><br>
>> OK, that is the same date I received :)<br>
>><br>
>> Regards,<br>
>><br>
>> Wouter<br>
>><br>
>><br>
>> > -----Original Message-----<br>
>> > From: Youssef Bengelloun-Zahr [mailto:<a href="mailto:youssef@720.fr">youssef@720.fr</a><br>
>> <mailto:<a href="mailto:youssef@720.fr">youssef@720.fr</a>>]<br>
>><br>
>> > Sent: Sunday, May 25, 2014 22:16<br>
>> > To: Wouter de Jong<br>
>> > Cc: <<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
</div>>> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>>><br>
<div class="">>> > Subject: Re: [f-nsp] Netiron 5.6 feedbacks<br>
>> ><br>
>><br>
>> > Hi,<br>
>> ><br>
>> > Answering my own post. Just heard from my SE, 56d GA is<br>
>> targeted for<br>
>> > July 16th.<br>
>> ><br>
>> > Best regards.<br>
>> ><br>
>> ><br>
>> ><br>
>> > > Le 25 mai 2014 Ã 20:34, Youssef Bengelloun-Zahr<br>
</div>>> <<a href="mailto:youssef@720.fr">youssef@720.fr</a> <mailto:<a href="mailto:youssef@720.fr">youssef@720.fr</a>>> a écrit<br>
<div class="">>> > :<br>
>> > ><br>
>> > > Hi,<br>
>> > ><br>
>> > > Interesting... Did TAC give you 56d GA release date ?<br>
>> > ><br>
>> > > Y.<br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > >> Le 25 mai 2014 Ã 12:57, Wouter de Jong <<a href="mailto:wouter@widexs.nl">wouter@widexs.nl</a><br>
</div>>> <mailto:<a href="mailto:wouter@widexs.nl">wouter@widexs.nl</a>>> a écrit :<br>
<div><div class="h5">>> > >><br>
>> > >> Hi,<br>
>> > >><br>
>> > >> (Apologies for not quoting, etc as I don't have the<br>
>> original email in my<br>
>> > >> mailbox)<br>
>> > >><br>
>> > >> Too bad that 5.6 seems 'buggy' ... some of it's new<br>
>> features look nice,<br>
>> > and<br>
>> > >> I was planning to put it on a new box...<br>
>> > >> now I'm not so sure about that any longer...<br>
>> > >><br>
>> > >><br>
>> > >> Also interesting that you seem to run 5.5d without<br>
>> problems, as we<br>
>> > came<br>
>> > >> across a bug in 5.5 with regards<br>
>> > >> to the IPv6 route cache - DEFECT000500944<br>
>> > >><br>
>> > >> Due to it's characteristics, my guess would be that we<br>
>> really can't be<br>
>> > the<br>
>> > >> only one that faced that problem ? :)<br>
>> > >><br>
>> > >> The issue is that after a link between 2 MLXe's fails and<br>
>> the IGP selects a<br>
>> > >> different path ... it fails to update the IPv6 cache.<br>
>> > >> However, it updates the RIB, etc correctly .... so IPv6<br>
>> traffic transiting<br>
>> > >> through the router appears to keep working without issue and<br>
>> > >> everything _seems_ correctly (even from looking at CAM),<br>
>> only traffic<br>
>> > >> originated from the router itself (eg. loopback) is still<br>
>> pointing<br>
>> > >> to the wrong interface, which for example affected IPv6<br>
>> iBGP sessions<br>
>> > in our<br>
>> > >> case.<br>
>> > >><br>
>> > >> The provided method to resolve it is to manually clear<br>
>> the IPv6 cache<br>
>> > by<br>
>> > >> running "clear ipv6 cache"<br>
>> > >> (Note that 'cache' is hidden in the outout from "clear<br>
>> ipv6 ?" ...<br>
>> > >> DEFECT000503937)<br>
>> > >><br>
>> > >><br>
>> > >> According to TAC, this issue occurs in both 5.5.x and<br>
>> 5.6.x ... and both<br>
>> > >> with IS-IS and OSPF.<br>
>> > >> In our case, this was on MLXe-4's with 4x10G X-blades,<br>
>> running IS-IS, with<br>
>> > >> v5.5d and v5.5e<br>
>> > >> Fix should come in 5.6d .. not sure in what version 5.5<br>
>> will be fixed.<br>
>> > >><br>
>> > >><br>
>> > >> Just wondering if anyone else faced this as well ?<br>
>> > >><br>
>> > >><br>
>> > >> Best regards,<br>
>> > >><br>
>> > >> Wouter<br>
>> > >><br>
>> > >> _______________________________________________<br>
>> > >> foundry-nsp mailing list<br>
>> > >> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
</div></div>>> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br>
<div class="">>> > >> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Youssef BENGELLOUN-ZAHR<br>
>><br>
>><br>
>> _______________________________________________<br>
>> foundry-nsp mailing list<br>
</div>>> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br>
<div class="">>> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> foundry-nsp mailing list<br>
</div>>> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a> <mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br>
<div class="im HOEnZb">>> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Youssef BENGELLOUN-ZAHR<br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Youssef BENGELLOUN-ZAHR<br>
>><br>
><br>
><br>
</div><div class="HOEnZb"><div class="h5">> _______________________________________________<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" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
<br>
<br>
--<br>
</div></div><span class="HOEnZb"><font color="#888888">John W. O'Brien<br>
Senior Network Engineer<br>
Information Systems and Computing<br>
University of Pennsylvania<br>
<a href="mailto:obrienjw@upenn.edu">obrienjw@upenn.edu</a> <a href="tel:215-898-9818" value="+12158989818">215-898-9818</a><br>
OpenPGP key ID: 0x155016CB<br>
<br>
<br>
</font></span><br>_______________________________________________<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" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br></blockquote></div><br></div>