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