Mailing List Archive

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@micron21.com
> <mailto:james.braunegg@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@micron21.com
>> <mailto:james.braunegg@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@puck.nether.net] *On
>> Behalf Of *Youssef Bengelloun-Zahr
>> *Sent:* Friday, August 01, 2014 5:14 AM
>> *To:* Skylar MacMinn
>> *Cc:* foundry-nsp@puck.nether.net <mailto:foundry-nsp@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@crissic.net
>> <mailto:skylar@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@puck.nether.net
>> <mailto:foundry-nsp-bounces@puck.nether.net>] *On Behalf Of *Youssef
>> Bengelloun-Zahr
>> *Sent:* Friday, July 18, 2014 8:43 AM
>> *To:* Josh Galvez
>>
>>
>> *Cc:* foundry-nsp@puck.nether.net <mailto:foundry-nsp@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@zevlag.com
>> <mailto:josh@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@micron21.com <mailto:james.braunegg@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@micron21.com
>> <mailto:james.braunegg@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@puck.nether.net
>> <mailto:foundry-nsp-bounces@puck.nether.net>] *On Behalf Of
>> *Youssef Bengelloun-Zahr
>> *Sent:* Monday, May 26, 2014 6:48 PM
>>
>>
>> *To:* Wouter de Jong
>> *Cc:* <foundry-nsp@puck.nether.net
>> <mailto:foundry-nsp@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@widexs.nl
>> <mailto:wouter@widexs.nl>>:
>>
>> Hi Youssef,
>>
>> OK, that is the same date I received :)
>>
>> Regards,
>>
>> Wouter
>>
>>
>> > -----Original Message-----
>> > From: Youssef Bengelloun-Zahr [mailto:youssef@720.fr
>> <mailto:youssef@720.fr>]
>>
>> > Sent: Sunday, May 25, 2014 22:16
>> > To: Wouter de Jong
>> > Cc: <foundry-nsp@puck.nether.net
>> <mailto:foundry-nsp@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@720.fr <mailto:youssef@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@widexs.nl
>> <mailto:wouter@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@puck.nether.net
>> <mailto:foundry-nsp@puck.nether.net>
>> > >> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>>
>>
>>
>> --
>> Youssef BENGELLOUN-ZAHR
>>
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net>
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>>
>>
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net>
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>>
>>
>>
>> --
>> Youssef BENGELLOUN-ZAHR
>>
>>
>>
>>
>> --
>> Youssef BENGELLOUN-ZAHR
>>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@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@upenn.edu 215-898-9818
OpenPGP key ID: 0x155016CB

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@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@micron21.com
> > <mailto:james.braunegg@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@micron21.com
> >> <mailto:james.braunegg@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@puck.nether.net] *On
> >> Behalf Of *Youssef Bengelloun-Zahr
> >> *Sent:* Friday, August 01, 2014 5:14 AM
> >> *To:* Skylar MacMinn
> >> *Cc:* foundry-nsp@puck.nether.net <mailto:foundry-nsp@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@crissic.net
> >> <mailto:skylar@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@puck.nether.net
> >> <mailto:foundry-nsp-bounces@puck.nether.net>] *On Behalf Of *Youssef
> >> Bengelloun-Zahr
> >> *Sent:* Friday, July 18, 2014 8:43 AM
> >> *To:* Josh Galvez
> >>
> >>
> >> *Cc:* foundry-nsp@puck.nether.net <mailto:foundry-nsp@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@zevlag.com
> >> <mailto:josh@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@micron21.com <mailto:james.braunegg@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@micron21.com
> >> <mailto:james.braunegg@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@puck.nether.net
> >> <mailto:foundry-nsp-bounces@puck.nether.net>] *On Behalf Of
> >> *Youssef Bengelloun-Zahr
> >> *Sent:* Monday, May 26, 2014 6:48 PM
> >>
> >>
> >> *To:* Wouter de Jong
> >> *Cc:* <foundry-nsp@puck.nether.net
> >> <mailto:foundry-nsp@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@widexs.nl
> >> <mailto:wouter@widexs.nl>>:
> >>
> >> Hi Youssef,
> >>
> >> OK, that is the same date I received :)
> >>
> >> Regards,
> >>
> >> Wouter
> >>
> >>
> >> > -----Original Message-----
> >> > From: Youssef Bengelloun-Zahr [mailto:youssef@720.fr
> >> <mailto:youssef@720.fr>]
> >>
> >> > Sent: Sunday, May 25, 2014 22:16
> >> > To: Wouter de Jong
> >> > Cc: <foundry-nsp@puck.nether.net
> >> <mailto:foundry-nsp@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@720.fr <mailto:youssef@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@widexs.nl
> >> <mailto:wouter@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@puck.nether.net
> >> <mailto:foundry-nsp@puck.nether.net>
> >> > >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >>
> >>
> >>
> >> --
> >> Youssef BENGELLOUN-ZAHR
> >>
> >>
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net
> >
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net>
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >>
> >>
> >>
> >> --
> >> Youssef BENGELLOUN-ZAHR
> >>
> >>
> >>
> >>
> >> --
> >> Youssef BENGELLOUN-ZAHR
> >>
> >
> >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@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@upenn.edu 215-898-9818
> OpenPGP key ID: 0x155016CB
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

Hello Eldon,

Any news from BTAC ?

Best regards.



> Le 13 août 2014 à 23:29, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>
> We are running MLX and MLXe. Opening a ticket with Brocade is on my
> to-do list.
>
> --
> Eldon Koyle
> --
> Mathematics deals exclusively with the relations of concepts
> to each other without consideration of their relation to experience.
> -- Albert Einstein
>
>> On Aug 13 6:33+0200, Youssef Bengelloun-Zahr wrote:
>> Hi Eldon,
>>
>> On which platform did you notice this ? Did you open a case with BTAC ?
>>
>> Best regards.
>>
>>
>>
>>> Le 13 août 2014 à 00:50, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>
>>> I am seeing some invalid data from SNMP on 5.6d. 10G interfaces will
>>> periodically transfer at rates of multiple petabits per second and I am
>>> also seeing SNMP reporting 4G RX/TX discards on an interface that reports 0
>>> errors/discards on 'show stat' and 'show int'.
>>>
>>> --
>>> Eldon Koyle
>>> --
>>> Behold the warranty -- the bold print giveth and the fine print taketh away.
>>>
>>>> On Aug 12 10:25+0200, 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.
>>>>
>>>>
>>>>
>>>>> Le 1 août 2014 à 02:09, James Braunegg <james.braunegg@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@micron21.com | ABN: 12 109 977 666
>>>>> W: 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@puck.nether.net] On Behalf Of Youssef Bengelloun-Zahr
>>>>> Sent: Friday, August 01, 2014 5:14 AM
>>>>> To: Skylar MacMinn
>>>>> Cc: foundry-nsp@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@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
>>>>> Crissic Solutions, LLC
>>>>>
>>>>> From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of Youssef Bengelloun-Zahr
>>>>> Sent: Friday, July 18, 2014 8:43 AM
>>>>> To: Josh Galvez
>>>>>
>>>>> Cc: foundry-nsp@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@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@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@micron21.com | ABN: 12 109 977 666
>>>>> W: 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@puck.nether.net] On Behalf Of Youssef Bengelloun-Zahr
>>>>> Sent: Monday, May 26, 2014 6:48 PM
>>>>>
>>>>> To: Wouter de Jong
>>>>> Cc: <foundry-nsp@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@widexs.nl>:
>>>>> Hi Youssef,
>>>>>
>>>>> OK, that is the same date I received :)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Wouter
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Youssef Bengelloun-Zahr [mailto:youssef@720.fr]
>>>>>> Sent: Sunday, May 25, 2014 22:16
>>>>>> To: Wouter de Jong
>>>>>> Cc: <foundry-nsp@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@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@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@puck.nether.net
>>>>>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Youssef BENGELLOUN-ZAHR
>>>>>
>>>>> _______________________________________________
>>>>> foundry-nsp mailing list
>>>>> foundry-nsp@puck.nether.net
>>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> foundry-nsp mailing list
>>>>> foundry-nsp@puck.nether.net
>>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Youssef BENGELLOUN-ZAHR
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Youssef BENGELLOUN-ZAHR
>>>
>>>> _______________________________________________
>>>> foundry-nsp mailing list
>>>> foundry-nsp@puck.nether.net
>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

On 8/15/14 4:26 PM, Josh Galvez wrote:
> 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)

It seems to affect all line cards. I spent some time today sifting
through a packet trace of the sFlow output from one of our routers
during an interval when Arbor Peakflow shows a ridiculously large
(~1Pb/s when our usual peaks are <10Gb/s) output traffic spike across
multiple interfaces. In the time I spent, I didn't see anything
obviously wrong in the sFlow data packet-by-packet, so I think I would
have to bring some automation to bear to explore and summarize the data
en masse. In fact, I wasn't even able to reproduce the previous example
of incorrect packet counter samples. My guess is that most sFlow records
are fine, and from time to time there are some that are corrupted somehow.

> On Thu, Aug 14, 2014 at 7:01 PM, John W. O'Brien <obrienjw@upenn.edu
> <mailto:obrienjw@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@micron21.com <mailto:james.braunegg@micron21.com>
> > <mailto:james.braunegg@micron21.com
> <mailto:james.braunegg@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@micron21.com
> <mailto:james.braunegg@micron21.com>
> >> <mailto:james.braunegg@micron21.com
> <mailto:james.braunegg@micron21.com>> | *ABN:* 12 109 977 666
> <tel:12%20109%20977%20666>
> >> *W:* www.micron21.com/ddos-protection
> <http://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@puck.nether.net
> <mailto:foundry-nsp-bounces@puck.nether.net>] *On
> >> Behalf Of *Youssef Bengelloun-Zahr
> >> *Sent:* Friday, August 01, 2014 5:14 AM
> >> *To:* Skylar MacMinn
> >> *Cc:* foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@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@crissic.net
> <mailto:skylar@crissic.net>
> >> <mailto:skylar@crissic.net <mailto:skylar@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> <http://www.crissic.net>
> >> Crissic Solutions, LLC
> >>
> >>
> >>
> >> *From:*foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net
> <mailto:foundry-nsp-bounces@puck.nether.net>
> >> <mailto:foundry-nsp-bounces@puck.nether.net
> <mailto:foundry-nsp-bounces@puck.nether.net>>] *On Behalf Of *Youssef
> >> Bengelloun-Zahr
> >> *Sent:* Friday, July 18, 2014 8:43 AM
> >> *To:* Josh Galvez
> >>
> >>
> >> *Cc:* foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@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@zevlag.com
> <mailto:josh@zevlag.com>
> >> <mailto:josh@zevlag.com <mailto:josh@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@micron21.com
> <mailto:james.braunegg@micron21.com>
> <mailto:james.braunegg@micron21.com
> <mailto:james.braunegg@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@micron21.com
> <mailto:james.braunegg@micron21.com>
> >> <mailto:james.braunegg@micron21.com
> <mailto:james.braunegg@micron21.com>> | *ABN:* 12 109 977
> >> 666 <tel:12%20109%20977%20666>
> >> *W:* www.micron21.com/ddos-protection
> <http://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@puck.nether.net
> <mailto:foundry-nsp-bounces@puck.nether.net>
> >> <mailto:foundry-nsp-bounces@puck.nether.net
> <mailto:foundry-nsp-bounces@puck.nether.net>>] *On Behalf Of
> >> *Youssef Bengelloun-Zahr
> >> *Sent:* Monday, May 26, 2014 6:48 PM
> >>
> >>
> >> *To:* Wouter de Jong
> >> *Cc:* <foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> >> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@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@widexs.nl <mailto:wouter@widexs.nl>
> >> <mailto:wouter@widexs.nl <mailto:wouter@widexs.nl>>>:
> >>
> >> Hi Youssef,
> >>
> >> OK, that is the same date I received :)
> >>
> >> Regards,
> >>
> >> Wouter
> >>
> >>
> >> > -----Original Message-----
> >> > From: Youssef Bengelloun-Zahr [mailto:youssef@720.fr
> <mailto:youssef@720.fr>
> >> <mailto:youssef@720.fr <mailto:youssef@720.fr>>]
> >>
> >> > Sent: Sunday, May 25, 2014 22:16
> >> > To: Wouter de Jong
> >> > Cc: <foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> >> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@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@720.fr <mailto:youssef@720.fr>
> <mailto:youssef@720.fr <mailto:youssef@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@widexs.nl <mailto:wouter@widexs.nl>
> >> <mailto:wouter@widexs.nl <mailto:wouter@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@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> >> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>>
> >> > >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >>
> >>
> >>
> >> --
> >> Youssef BENGELLOUN-ZAHR
> >>
> >>
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>>
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>
> <mailto:foundry-nsp@puck.nether.net
> <mailto:foundry-nsp@puck.nether.net>>
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >>
> >>
> >>
> >> --
> >> Youssef BENGELLOUN-ZAHR
> >>
> >>
> >>
> >>
> >> --
> >> Youssef BENGELLOUN-ZAHR
> >>
> >
> >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@puck.nether.net <mailto:foundry-nsp@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@upenn.edu <mailto:obrienjw@upenn.edu> 215-898-9818
> <tel:215-898-9818>
> OpenPGP key ID: 0x155016CB
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net>
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@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@upenn.edu 215-898-9818
OpenPGP key ID: 0x155016CB

Hello Eldon,

Any news from BTAC ?

Best regards.



> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>
> Hello Eldon,
>
> Any news from BTAC ?
>
> Best regards.

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

I finally heard back today, not sure how long it will take them to fix
it:

DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling

I thought saw something about SNMP caching in the changelog... I'm
wondering if they did something wrong there.

--
Eldon Koyle
Information Technology
Utah State University

On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> Hello Eldon,
>
> Any news from BTAC ?
>
> Best regards.
>
>
>
> > Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
> >
> > Hello Eldon,
> >
> > Any news from BTAC ?
> >
> > Best regards.
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Hi,

This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?

I will ask my SE to look it up.

Thanks for the feedback.

Best regards.



> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>
> I finally heard back today, not sure how long it will take them to fix
> it:
>
> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
>
> I thought saw something about SNMP caching in the changelog... I'm
> wondering if they did something wrong there.
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
>
>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
>> Hello Eldon,
>>
>> Any news from BTAC ?
>>
>> Best regards.
>>
>>
>>
>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>>>
>>> Hello Eldon,
>>>
>>> Any news from BTAC ?
>>>
>>> Best regards.
>>

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

I don't have any more information than that, sorry. They didn't need my
help to reproduce it, so I suspect others have reported the same issue.
FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
as extensively.

--
Eldon Koyle
Information Technology
Utah State University
--
For certain people, after fifty, litigation takes the place of sex.
-- Gore Vidal

On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> Hi,
>
> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
>
> I will ask my SE to look it up.
>
> Thanks for the feedback.
>
> Best regards.
>
>
>
> > Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >
> > I finally heard back today, not sure how long it will take them to fix
> > it:
> >
> > DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
> >
> > I thought saw something about SNMP caching in the changelog... I'm
> > wondering if they did something wrong there.
> >
> > --
> > Eldon Koyle
> > Information Technology
> > Utah State University
> >
> >> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> >> Hello Eldon,
> >>
> >> Any news from BTAC ?
> >>
> >> Best regards.
> >>
> >>
> >>
> >>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
> >>>
> >>> Hello Eldon,
> >>>
> >>> Any news from BTAC ?
> >>>
> >>> Best regards.
> >>
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Hello Eldon,

Any feedbacks from BTAC regarding that SNMP defect ?

Best regards.



> Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>
> I don't have any more information than that, sorry. They didn't need my
> help to reproduce it, so I suspect others have reported the same issue.
> FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
> as extensively.
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> For certain people, after fifty, litigation takes the place of sex.
> -- Gore Vidal
>
>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
>> Hi,
>>
>> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
>>
>> I will ask my SE to look it up.
>>
>> Thanks for the feedback.
>>
>> Best regards.
>>
>>
>>
>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>
>>> I finally heard back today, not sure how long it will take them to fix
>>> it:
>>>
>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
>>>
>>> I thought saw something about SNMP caching in the changelog... I'm
>>> wondering if they did something wrong there.
>>>
>>> --
>>> Eldon Koyle
>>> Information Technology
>>> Utah State University
>>>
>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
>>>> Hello Eldon,
>>>>
>>>> Any news from BTAC ?
>>>>
>>>> Best regards.
>>>>
>>>>
>>>>
>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>>>>>
>>>>> Hello Eldon,
>>>>>
>>>>> Any news from BTAC ?
>>>>>
>>>>> Best regards.
>>

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

My SE says that defect was caused by using 32bit counters. So I'm rolling it out now.

First one looks ok.

/Tias


> 28 sep 2014 kl. 10:48 skrev Youssef Bengelloun-Zahr <youssef@720.fr>:
>
> Hello Eldon,
>
> Any feedbacks from BTAC regarding that SNMP defect ?
>
> Best regards.
>
>
>
>> Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>
>> I don't have any more information than that, sorry. They didn't need my
>> help to reproduce it, so I suspect others have reported the same issue.
>> FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
>> as extensively.
>>
>> --
>> Eldon Koyle
>> Information Technology
>> Utah State University
>> --
>> For certain people, after fifty, litigation takes the place of sex.
>> -- Gore Vidal
>>
>>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
>>> Hi,
>>>
>>> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
>>>
>>> I will ask my SE to look it up.
>>>
>>> Thanks for the feedback.
>>>
>>> Best regards.
>>>
>>>
>>>
>>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>>
>>>> I finally heard back today, not sure how long it will take them to fix
>>>> it:
>>>>
>>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
>>>>
>>>> I thought saw something about SNMP caching in the changelog... I'm
>>>> wondering if they did something wrong there.
>>>>
>>>> --
>>>> Eldon Koyle
>>>> Information Technology
>>>> Utah State University
>>>>
>>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
>>>>> Hello Eldon,
>>>>>
>>>>> Any news from BTAC ?
>>>>>
>>>>> Best regards.
>>>>>
>>>>>
>>>>>
>>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>>>>>>
>>>>>> Hello Eldon,
>>>>>>
>>>>>> Any news from BTAC ?
>>>>>>
>>>>>> Best regards.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

I gave up waiting on them. They claimed it was something with 32-bit
counters, but do they even have 64-bit error counters?

I ended up disabling SNMP caching (snmp-server cache disable), which has
eliminated the symptoms for us. I'm not sure what the other
ramifications of that change will be.

--
Eldon Koyle
Information Technology
Utah State University
--
BOFH excuse #192:
runaway cat on system.

On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
> Hello Eldon,
>
> Any feedbacks from BTAC regarding that SNMP defect ?
>
> Best regards.
>
>
>
> > Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >
> > I don't have any more information than that, sorry. They didn't need my
> > help to reproduce it, so I suspect others have reported the same issue.
> > FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
> > as extensively.
> >
> > --
> > Eldon Koyle
> > Information Technology
> > Utah State University
> > --
> > For certain people, after fifty, litigation takes the place of sex.
> > -- Gore Vidal
> >
> >> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> >> Hi,
> >>
> >> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
> >>
> >> I will ask my SE to look it up.
> >>
> >> Thanks for the feedback.
> >>
> >> Best regards.
> >>
> >>
> >>
> >>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >>>
> >>> I finally heard back today, not sure how long it will take them to fix
> >>> it:
> >>>
> >>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
> >>>
> >>> I thought saw something about SNMP caching in the changelog... I'm
> >>> wondering if they did something wrong there.
> >>>
> >>> --
> >>> Eldon Koyle
> >>> Information Technology
> >>> Utah State University
> >>>
> >>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> >>>> Hello Eldon,
> >>>>
> >>>> Any news from BTAC ?
> >>>>
> >>>> Best regards.
> >>>>
> >>>>
> >>>>
> >>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
> >>>>>
> >>>>> Hello Eldon,
> >>>>>
> >>>>> Any news from BTAC ?
> >>>>>
> >>>>> Best regards.
> >>
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

In other news, I just had ssh stop working on 5 MLX routers, all running
5.6d:

$ ssh myrouter
invalid public DH value (1/1024)
Disconnecting: bad server public DH value
$

When will Brocade get their act together on their SSH implementation?
Does this really have to happen on every third firmware release?

--
Eldon Koyle
Information Technology
Utah State University
--
It is much easier to suggest solutions when you know nothing about the problem.

On Sep 29 11:40-0600, Eldon Koyle wrote:
> I gave up waiting on them. They claimed it was something with 32-bit
> counters, but do they even have 64-bit error counters?
>
> I ended up disabling SNMP caching (snmp-server cache disable), which has
> eliminated the symptoms for us. I'm not sure what the other
> ramifications of that change will be.
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> BOFH excuse #192:
> runaway cat on system.
>
> On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
> > Hello Eldon,
> >
> > Any feedbacks from BTAC regarding that SNMP defect ?
> >
> > Best regards.
> >
> >
> >
> > > Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> > >
> > > I don't have any more information than that, sorry. They didn't need my
> > > help to reproduce it, so I suspect others have reported the same issue.
> > > FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
> > > as extensively.
> > >
> > > --
> > > Eldon Koyle
> > > Information Technology
> > > Utah State University
> > > --
> > > For certain people, after fifty, litigation takes the place of sex.
> > > -- Gore Vidal
> > >
> > >> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> > >> Hi,
> > >>
> > >> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
> > >>
> > >> I will ask my SE to look it up.
> > >>
> > >> Thanks for the feedback.
> > >>
> > >> Best regards.
> > >>
> > >>
> > >>
> > >>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> > >>>
> > >>> I finally heard back today, not sure how long it will take them to fix
> > >>> it:
> > >>>
> > >>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
> > >>>
> > >>> I thought saw something about SNMP caching in the changelog... I'm
> > >>> wondering if they did something wrong there.
> > >>>
> > >>> --
> > >>> Eldon Koyle
> > >>> Information Technology
> > >>> Utah State University
> > >>>
> > >>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> > >>>> Hello Eldon,
> > >>>>
> > >>>> Any news from BTAC ?
> > >>>>
> > >>>> Best regards.
> > >>>>
> > >>>>
> > >>>>
> > >>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
> > >>>>>
> > >>>>> Hello Eldon,
> > >>>>>
> > >>>>> Any news from BTAC ?
> > >>>>>
> > >>>>> Best regards.
> > >>
> >
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Are theese MLX or MLXe routers ? What kind of MPs running ?

Other unusual behavior ?

Best regards.

Y.



> Le 1 oct. 2014 à 00:42, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>
> In other news, I just had ssh stop working on 5 MLX routers, all running
> 5.6d:
>
> $ ssh myrouter
> invalid public DH value (1/1024)
> Disconnecting: bad server public DH value
> $
>
> When will Brocade get their act together on their SSH implementation?
> Does this really have to happen on every third firmware release?
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> It is much easier to suggest solutions when you know nothing about the problem.
>
>> On Sep 29 11:40-0600, Eldon Koyle wrote:
>> I gave up waiting on them. They claimed it was something with 32-bit
>> counters, but do they even have 64-bit error counters?
>>
>> I ended up disabling SNMP caching (snmp-server cache disable), which has
>> eliminated the symptoms for us. I'm not sure what the other
>> ramifications of that change will be.
>>
>> --
>> Eldon Koyle
>> Information Technology
>> Utah State University
>> --
>> BOFH excuse #192:
>> runaway cat on system.
>>
>>> On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
>>> Hello Eldon,
>>>
>>> Any feedbacks from BTAC regarding that SNMP defect ?
>>>
>>> Best regards.
>>>
>>>
>>>
>>>> Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>>
>>>> I don't have any more information than that, sorry. They didn't need my
>>>> help to reproduce it, so I suspect others have reported the same issue.
>>>> FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
>>>> as extensively.
>>>>
>>>> --
>>>> Eldon Koyle
>>>> Information Technology
>>>> Utah State University
>>>> --
>>>> For certain people, after fifty, litigation takes the place of sex.
>>>> -- Gore Vidal
>>>>
>>>>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
>>>>> Hi,
>>>>>
>>>>> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
>>>>>
>>>>> I will ask my SE to look it up.
>>>>>
>>>>> Thanks for the feedback.
>>>>>
>>>>> Best regards.
>>>>>
>>>>>
>>>>>
>>>>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>>>>
>>>>>> I finally heard back today, not sure how long it will take them to fix
>>>>>> it:
>>>>>>
>>>>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
>>>>>>
>>>>>> I thought saw something about SNMP caching in the changelog... I'm
>>>>>> wondering if they did something wrong there.
>>>>>>
>>>>>> --
>>>>>> Eldon Koyle
>>>>>> Information Technology
>>>>>> Utah State University
>>>>>>
>>>>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
>>>>>>> Hello Eldon,
>>>>>>>
>>>>>>> Any news from BTAC ?
>>>>>>>
>>>>>>> Best regards.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>>>>>>>>
>>>>>>>> Hello Eldon,
>>>>>>>>
>>>>>>>> Any news from BTAC ?
>>>>>>>>
>>>>>>>> Best regards.
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

All are MLX-4 with single NI-MLX-MR management modules. I haven't
noticed other unusual behavior associated with this as of yet.

--
Eldon Koyle
Information Technology
Utah State University
--
BOFH excuse #195:
We only support a 28000 bps connection.

On Oct 01 1:07+0200, Youssef Bengelloun-Zahr wrote:
> Are theese MLX or MLXe routers ? What kind of MPs running ?
>
> Other unusual behavior ?
>
> Best regards.
>
> Y.
>
>
>
> > Le 1 oct. 2014 à 00:42, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >
> > In other news, I just had ssh stop working on 5 MLX routers, all running
> > 5.6d:
> >
> > $ ssh myrouter
> > invalid public DH value (1/1024)
> > Disconnecting: bad server public DH value
> > $
> >
> > When will Brocade get their act together on their SSH implementation?
> > Does this really have to happen on every third firmware release?
> >
> > --
> > Eldon Koyle
> > Information Technology
> > Utah State University
> > --
> > It is much easier to suggest solutions when you know nothing about the problem.
> >
> >> On Sep 29 11:40-0600, Eldon Koyle wrote:
> >> I gave up waiting on them. They claimed it was something with 32-bit
> >> counters, but do they even have 64-bit error counters?
> >>
> >> I ended up disabling SNMP caching (snmp-server cache disable), which has
> >> eliminated the symptoms for us. I'm not sure what the other
> >> ramifications of that change will be.
> >>
> >> --
> >> Eldon Koyle
> >> Information Technology
> >> Utah State University
> >> --
> >> BOFH excuse #192:
> >> runaway cat on system.
> >>
> >>> On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
> >>> Hello Eldon,
> >>>
> >>> Any feedbacks from BTAC regarding that SNMP defect ?
> >>>
> >>> Best regards.
> >>>
> >>>
> >>>
> >>>> Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >>>>
> >>>> I don't have any more information than that, sorry. They didn't need my
> >>>> help to reproduce it, so I suspect others have reported the same issue.
> >>>> FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
> >>>> as extensively.
> >>>>
> >>>> --
> >>>> Eldon Koyle
> >>>> Information Technology
> >>>> Utah State University
> >>>> --
> >>>> For certain people, after fifty, litigation takes the place of sex.
> >>>> -- Gore Vidal
> >>>>
> >>>>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> >>>>> Hi,
> >>>>>
> >>>>> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
> >>>>>
> >>>>> I will ask my SE to look it up.
> >>>>>
> >>>>> Thanks for the feedback.
> >>>>>
> >>>>> Best regards.
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >>>>>>
> >>>>>> I finally heard back today, not sure how long it will take them to fix
> >>>>>> it:
> >>>>>>
> >>>>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
> >>>>>>
> >>>>>> I thought saw something about SNMP caching in the changelog... I'm
> >>>>>> wondering if they did something wrong there.
> >>>>>>
> >>>>>> --
> >>>>>> Eldon Koyle
> >>>>>> Information Technology
> >>>>>> Utah State University
> >>>>>>
> >>>>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> >>>>>>> Hello Eldon,
> >>>>>>>
> >>>>>>> Any news from BTAC ?
> >>>>>>>
> >>>>>>> Best regards.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
> >>>>>>>>
> >>>>>>>> Hello Eldon,
> >>>>>>>>
> >>>>>>>> Any news from BTAC ?
> >>>>>>>>
> >>>>>>>> Best regards.
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp@puck.nether.net
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

On Tue, 30 Sep 2014, Eldon Koyle wrote:

> In other news, I just had ssh stop working on 5 MLX routers, all running
> 5.6d:
>
> $ ssh myrouter
> invalid public DH value (1/1024)
> Disconnecting: bad server public DH value

I've got a ICX6610 running 07.3.00aT7f3 that's doing that. I've tried
zero'ing and recreating the key on the switch. Maybe a reboot will fix
it, but I don't plan to find out anytime soon. It's still switching
packets well enough.

Another rant that came up today. Why doesn't NetIron/XMR sort bgp
communities on routes? Leaving them in "as added" order makes writing
extended community-lists to match on multiple community strings
interesting.

----------------------------------------------------------------------
Jon Lewis, MCP :) | I route
| therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

We had this happen on an ICX6610. I think TAC's response was upgrade to
8.0. That did fix it for us.


--
Brian Loveland
Director, Infrastructure Operations
Aereo, Inc.

On Tue, Sep 30, 2014 at 8:08 PM, Jon Lewis <jlewis@lewis.org> wrote:

> On Tue, 30 Sep 2014, Eldon Koyle wrote:
>
> In other news, I just had ssh stop working on 5 MLX routers, all running
>> 5.6d:
>>
>> $ ssh myrouter
>> invalid public DH value (1/1024)
>> Disconnecting: bad server public DH value
>>
>
> I've got a ICX6610 running 07.3.00aT7f3 that's doing that. I've tried
> zero'ing and recreating the key on the switch. Maybe a reboot will fix it,
> but I don't plan to find out anytime soon. It's still switching packets
> well enough.
>
> Another rant that came up today. Why doesn't NetIron/XMR sort bgp
> communities on routes? Leaving them in "as added" order makes writing
> extended community-lists to match on multiple community strings interesting.
>
> ----------------------------------------------------------------------
> Jon Lewis, MCP :) | I route
> | therefore you are
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

Also seen in 5.7 and most likely in 5.7a. I think this happens after about 70 SSH logins.

I've been through the TAC and told it will be fixed in the next patch release for 5.6 and 5.7.

Zeroing out the key and recreating seems to work sometimes and/or briefly. Telnet is unaffected if you can get to the serial console to enable it :)

Mitchell

_____

From: Eldon Koyle [mailto:esk-puck.nether.net@esk.cs.usu.edu]
To: foundry-nsp@puck.nether.net [mailto:foundry-nsp@puck.nether.net]
Sent: Wed, 01 Oct 2014 08:42:49 +1000
Subject: Re: [f-nsp] Netiron 5.6 feedbacks

In other news, I just had ssh stop working on 5 MLX routers, all running
5.6d:

$ ssh myrouter
invalid public DH value (1/1024)
Disconnecting: bad server public DH value
$

When will Brocade get their act together on their SSH implementation?
Does this really have to happen on every third firmware release?

--
Eldon Koyle
Information Technology
Utah State University
--
It is much easier to suggest solutions when you know nothing about the problem.

On Sep 29 11:40-0600, Eldon Koyle wrote:
> I gave up waiting on them. They claimed it was something with 32-bit
> counters, but do they even have 64-bit error counters?
>
> I ended up disabling SNMP caching (snmp-server cache disable), which has
> eliminated the symptoms for us. I'm not sure what the other
> ramifications of that change will be.
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> BOFH excuse #192:
> runaway cat on system.
>
> On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
> > Hello Eldon,
> >
> > Any feedbacks from BTAC regarding that SNMP defect ?
> >
> > Best regards.
> >
> >
> >
> > > Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> > >
> > > I don't have any more information than that, sorry. They didn't need my
> > > help to reproduce it, so I suspect others have reported the same issue.
> > > FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
> > > as extensively.
> > >
> > > --
> > > Eldon Koyle
> > > Information Technology
> > > Utah State University
> > > --
> > > For certain people, after fifty, litigation takes the place of sex.
> > > -- Gore Vidal
> > >
> > >> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> > >> Hi,
> > >>
> > >> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
> > >>
> > >> I will ask my SE to look it up.
> > >>
> > >> Thanks for the feedback.
> > >>
> > >> Best regards.
> > >>
> > >>
> > >>
> > >>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> > >>>
> > >>> I finally heard back today, not sure how long it will take them to fix
> > >>> it:
> > >>>
> > >>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
> > >>>
> > >>> I thought saw something about SNMP caching in the changelog... I'm
> > >>> wondering if they did something wrong there.
> > >>>
> > >>> --
> > >>> Eldon Koyle
> > >>> Information Technology
> > >>> Utah State University
> > >>>
> > >>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> > >>>> Hello Eldon,
> > >>>>
> > >>>> Any news from BTAC ?
> > >>>>
> > >>>> Best regards.
> > >>>>
> > >>>>
> > >>>>
> > >>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
> > >>>>>
> > >>>>> Hello Eldon,
> > >>>>>
> > >>>>> Any news from BTAC ?
> > >>>>>
> > >>>>> Best regards.
> > >>
> >
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

On 01/10/2014 01:08, Jon Lewis wrote:
> On Tue, 30 Sep 2014, Eldon Koyle wrote:
>> $ ssh myrouter
>> invalid public DH value (1/1024)
>> Disconnecting: bad server public DH value
>
> I've got a ICX6610 running 07.3.00aT7f3 that's doing that. I've tried
> zero'ing and recreating the key on the switch. Maybe a reboot will fix it,
> but I don't plan to find out anytime soon. It's still switching packets
> well enough.

that's probably DEFECT000408284 which is fixed in 7.3.00e / 7.4.00c.
Release train 8 is probably a better long term bet for the icx platform
though.

Nick

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

This bug keeps being forked back into newer releases. We've seen this
exact bug pop up somewhere since 5.2x or 5.3x



On 01/10/14 10:35, Mitchell Warden wrote:
> Also seen in 5.7 and most likely in 5.7a. I think this happens after
> about 70 SSH logins.
>
> I've been through the TAC and told it will be fixed in the next patch
> release for 5.6 and 5.7.
>
> Zeroing out the key and recreating seems to work sometimes and/or
> briefly. Telnet is unaffected if you can get to the serial console to
> enable it :)
>
> Mitchell
>
> ------------------------------------------------------------------------
> *From:* Eldon Koyle [mailto:esk-puck.nether.net@esk.cs.usu.edu]
> *To:* foundry-nsp@puck.nether.net [mailto:foundry-nsp@puck.nether.net]
> *Sent:* Wed, 01 Oct 2014 08:42:49 +1000
> *Subject:* Re: [f-nsp] Netiron 5.6 feedbacks
>
> In other news, I just had ssh stop working on 5 MLX routers, all
> running
> 5.6d:
>
> $ ssh myrouter
> invalid public DH value (1/1024)
> Disconnecting: bad server public DH value
> $
>
> When will Brocade get their act together on their SSH implementation?
> Does this really have to happen on every third firmware release?
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> It is much easier to suggest solutions when you know nothing about
> the problem.
>
> On Sep 29 11:40-0600, Eldon Koyle wrote:
> > I gave up waiting on them. They claimed it was something with 32-bit
> > counters, but do they even have 64-bit error counters?
> >
> > I ended up disabling SNMP caching (snmp-server cache disable),
> which has
> > eliminated the symptoms for us. I'm not sure what the other
> > ramifications of that change will be.
> >
> > --
> > Eldon Koyle
> > Information Technology
> > Utah State University
> > --
> > BOFH excuse #192:
> > runaway cat on system.
> >
> > On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
> > > Hello Eldon,
> > >
> > > Any feedbacks from BTAC regarding that SNMP defect ?
> > >
> > > Best regards.
> > >
> > >
> > >
> > > > Le 8 sept. 2014 à 06:54, Eldon Koyle
> <esk-puck.nether.net@esk.cs.usu.edu
> <mailto:esk-puck.nether.net@esk.cs.usu.edu>> a écrit :
> > > >
> > > > I don't have any more information than that, sorry. They
> didn't need my
> > > > help to reproduce it, so I suspect others have reported the
> same issue.
> > > > FWIW, I didn't notice this with 5.6c, but we didn't deploy
> that version
> > > > as extensively.
> > > >
> > > > --
> > > > Eldon Koyle
> > > > Information Technology
> > > > Utah State University
> > > > --
> > > > For certain people, after fifty, litigation takes the place
> of sex.
> > > > -- Gore Vidal
> > > >
> > > >> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> > > >> Hi,
> > > >>
> > > >> This DEFECT isn't listed in the official Brocade KB. Can
> you tell us a little bit more about it (affected versions, etc.) ?
> > > >>
> > > >> I will ask my SE to look it up.
> > > >>
> > > >> Thanks for the feedback.
> > > >>
> > > >> Best regards.
> > > >>
> > > >>
> > > >>
> > > >>> Le 5 sept. 2014 à 21:08, Eldon Koyle
> <esk-puck.nether.net@esk.cs.usu.edu
> <mailto:esk-puck.nether.net@esk.cs.usu.edu>> a écrit :
> > > >>>
> > > >>> I finally heard back today, not sure how long it will take
> them to fix
> > > >>> it:
> > > >>>
> > > >>> DEFECT000527089: 000527089 Seeing unexpected traffic
> spikes/dips during SNMP IfInOctets Polling
> > > >>>
> > > >>> I thought saw something about SNMP caching in the
> changelog... I'm
> > > >>> wondering if they did something wrong there.
> > > >>>
> > > >>> --
> > > >>> Eldon Koyle
> > > >>> Information Technology
> > > >>> Utah State University
> > > >>>
> > > >>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> > > >>>> Hello Eldon,
> > > >>>>
> > > >>>> Any news from BTAC ?
> > > >>>>
> > > >>>> Best regards.
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr
> <youssef@720.fr <mailto:youssef@720.fr>> a écrit :
> > > >>>>>
> > > >>>>> Hello Eldon,
> > > >>>>>
> > > >>>>> Any news from BTAC ?
> > > >>>>>
> > > >>>>> Best regards.
> > > >>
> > >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net>
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net <mailto:foundry-nsp@puck.nether.net>
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp


--

Jeroen Wunnink
IP NOC Manager - Hibernia Networks
Main numbers (Ext: 1011): USA +1.908.516.4200 | UK +44.1704.322.300
Netherlands +31.208.200.622 | 24/7 IP NOC Phone: +31.20.82.00.623
jeroen.wunnink@hibernianetworks.com
www.hibernianetworks.com

Dell - Internal Use - Confidential
I seriously don't think Brocade thoroughly tests their SSH implementations on their gear. Evidenced by this, and past experience. I remember one 5.x release that would NOT let me upgrade to a newer version via SSH giving some erroneous error during the copy of just one of the files. I forget which. Oddly, it worked if you were trying it via telnet and this bug was fixed in the release I was trying to upgrade to. It was a known bug that TAC told me about... unfortunately they told me after they insisted the file copied properly and to reboot the device despite the reload check failing. Naturally this caused the line card to fail to boot properly. Fortunately I was able to recover easily enough but it was very annoying. Other routers I used telnet (after turning it on) and the upgrade process went smoothly.

From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of Mitchell Warden
Sent: Wednesday, October 01, 2014 4:35 AM
To: Eldon Koyle; foundry-nsp@puck.nether.net
Subject: Re: [f-nsp] Netiron 5.6 feedbacks

Also seen in 5.7 and most likely in 5.7a. I think this happens after about 70 SSH logins.

I've been through the TAC and told it will be fixed in the next patch release for 5.6 and 5.7.

Zeroing out the key and recreating seems to work sometimes and/or briefly. Telnet is unaffected if you can get to the serial console to enable it :)

Mitchell
________________________________
From: Eldon Koyle [mailto:esk-puck.nether.net@esk.cs.usu.edu]
To: foundry-nsp@puck.nether.net<mailto:foundry-nsp@puck.nether.net> [mailto:foundry-nsp@puck.nether.net]
Sent: Wed, 01 Oct 2014 08:42:49 +1000
Subject: Re: [f-nsp] Netiron 5.6 feedbacks

In other news, I just had ssh stop working on 5 MLX routers, all running
5.6d:

$ ssh myrouter
invalid public DH value (1/1024)
Disconnecting: bad server public DH value
$

When will Brocade get their act together on their SSH implementation?
Does this really have to happen on every third firmware release?

--
Eldon Koyle
Information Technology
Utah State University
--
It is much easier to suggest solutions when you know nothing about the problem.

On Sep 29 11:40-0600, Eldon Koyle wrote:
> I gave up waiting on them. They claimed it was something with 32-bit
> counters, but do they even have 64-bit error counters?
>
> I ended up disabling SNMP caching (snmp-server cache disable), which has
> eliminated the symptoms for us. I'm not sure what the other
> ramifications of that change will be.
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> BOFH excuse #192:
> runaway cat on system.
>
> On Sep 28 10:48+0200, Youssef Bengelloun-Zahr wrote:
> > Hello Eldon,
> >
> > Any feedbacks from BTAC regarding that SNMP defect ?
> >
> > Best regards.
> >
> >
> >
> > > Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu<mailto:esk-puck.nether.net@esk.cs.usu.edu>> a écrit :
> > >
> > > I don't have any more information than that, sorry. They didn't need my
> > > help to reproduce it, so I suspect others have reported the same issue.
> > > FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
> > > as extensively.
> > >
> > > --
> > > Eldon Koyle
> > > Information Technology
> > > Utah State University
> > > --
> > > For certain people, after fifty, litigation takes the place of sex.
> > > -- Gore Vidal
> > >
> > >> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> > >> Hi,
> > >>
> > >> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
> > >>
> > >> I will ask my SE to look it up.
> > >>
> > >> Thanks for the feedback.
> > >>
> > >> Best regards.
> > >>
> > >>
> > >>
> > >>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu<mailto:esk-puck.nether.net@esk.cs.usu.edu>> a écrit :
> > >>>
> > >>> I finally heard back today, not sure how long it will take them to fix
> > >>> it:
> > >>>
> > >>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
> > >>>
> > >>> I thought saw something about SNMP caching in the changelog... I'm
> > >>> wondering if they did something wrong there.
> > >>>
> > >>> --
> > >>> Eldon Koyle
> > >>> Information Technology
> > >>> Utah State University
> > >>>
> > >>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> > >>>> Hello Eldon,
> > >>>>
> > >>>> Any news from BTAC ?
> > >>>>
> > >>>> Best regards.
> > >>>>
> > >>>>
> > >>>>
> > >>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr<mailto:youssef@720.fr>> a écrit :
> > >>>>>
> > >>>>> Hello Eldon,
> > >>>>>
> > >>>>> Any news from BTAC ?
> > >>>>>
> > >>>>> Best regards.
> > >>
> >
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net<mailto:foundry-nsp@puck.nether.net>
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net<mailto:foundry-nsp@puck.nether.net>
http://puck.nether.net/mailman/listinfo/foundry-nsp

On 8/14/14 9:01 PM, John W. O'Brien 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.

We've finally made progress on this issue, with the help of our flow
collector vendor. It seems likely that this is a regression in the SNMP
IF-MIB, not in the sFlow emitter. The flow collector would use the SNMP
counters to scale the sampled flows, so if the counters report bad data,
the scaling is all wrong. We've disable the SNMP scaling as a
work-around, and are continuing to work the case with Brocade.

Here's an example of what to look for, in case your flow collector or
NMS reports funky results.

Arrival Time: Sep 26, 2014 06:24:42.342790184 EDT
IF-MIB::ifHCOutOctets.970 (1.3.6.1.2.1.31.1.1.1.10.970): 0
--
Arrival Time: Sep 26, 2014 06:29:42.342692072 EDT
IF-MIB::ifHCOutOctets.970 (1.3.6.1.2.1.31.1.1.1.10.970): 0
--
Arrival Time: Sep 26, 2014 06:34:42.366492840 EDT
IF-MIB::ifHCOutOctets.970 (1.3.6.1.2.1.31.1.1.1.10.970): 0
--
Arrival Time: Sep 26, 2014 06:39:42.340412560 EDT
IF-MIB::ifHCOutOctets.970 (1.3.6.1.2.1.31.1.1.1.10.970):
6607961528840748800

IF-MIB::ifOperStatus.970 (1.3.6.1.2.1.2.2.1.8.970): down (2)
IF-MIB::ifName.970 (1.3.6.1.2.1.31.1.1.1.1.970): ethernet16/10


--
John W. O'Brien
Senior Network Engineer
Information Systems and Computing
University of Pennsylvania
obrienjw@upenn.edu 215-898-9818
OpenPGP key ID: 0x155016CB

> -----Original Message-----
> From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On
> Behalf Of Eldon Koyle
> Sent: Wednesday, 1 October 2014 8:43 AM
> To: foundry-nsp@puck.nether.net
> Subject: Re: [f-nsp] Netiron 5.6 feedbacks
>
> In other news, I just had ssh stop working on 5 MLX routers, all running
> 5.6d:
>
> $ ssh myrouter
> invalid public DH value (1/1024)
> Disconnecting: bad server public DH value
> $
>
> When will Brocade get their act together on their SSH implementation?
> Does this really have to happen on every third firmware release?
>
> --
> Eldon Koyle
> Information Technology
> Utah State University

From what I've read up it would appear to be a library linking order problem (which is why it might reoccur).

In saying that: I've done a lot of testing on 5.6d in the lab and this hasn't popped up for us.

I just checked in on a script I've left running and it's up to about 2700 ssh login/logouts of which every few hundred logins it varies between a show run and a show tech.

Just curious, what is your memory usage like and uptime?

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Hi

On 9/29/14 11:15 AM, Mathias Wolkert wrote:
> My SE says that defect was caused by using 32bit counters. So I'm rolling it out now.
>
> First one looks ok.

I was wrong andso was my SE. snmp counters are borked and disabling snmp
cache is a workaround.

Apart from that 5.6d seems ok.

/Tias

>
> /Tias
>
>
>> 28 sep 2014 kl. 10:48 skrev Youssef Bengelloun-Zahr <youssef@720.fr>:
>>
>> Hello Eldon,
>>
>> Any feedbacks from BTAC regarding that SNMP defect ?
>>
>> Best regards.
>>
>>
>>
>>> Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>
>>> I don't have any more information than that, sorry. They didn't need my
>>> help to reproduce it, so I suspect others have reported the same issue.
>>> FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
>>> as extensively.
>>>
>>> --
>>> Eldon Koyle
>>> Information Technology
>>> Utah State University
>>> --
>>> For certain people, after fifty, litigation takes the place of sex.
>>> -- Gore Vidal
>>>
>>>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
>>>> Hi,
>>>>
>>>> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
>>>>
>>>> I will ask my SE to look it up.
>>>>
>>>> Thanks for the feedback.
>>>>
>>>> Best regards.
>>>>
>>>>
>>>>
>>>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>>>
>>>>> I finally heard back today, not sure how long it will take them to fix
>>>>> it:
>>>>>
>>>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
>>>>>
>>>>> I thought saw something about SNMP caching in the changelog... I'm
>>>>> wondering if they did something wrong there.
>>>>>
>>>>> --
>>>>> Eldon Koyle
>>>>> Information Technology
>>>>> Utah State University
>>>>>
>>>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
>>>>>> Hello Eldon,
>>>>>>
>>>>>> Any news from BTAC ?
>>>>>>
>>>>>> Best regards.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>>>>>>>
>>>>>>> Hello Eldon,
>>>>>>>
>>>>>>> Any news from BTAC ?
>>>>>>>
>>>>>>> Best regards.
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Hi Mathias,

Has it been validated by BTAC ? Any ETA on a defentive correction ?

Best regards.



> Le 5 oct. 2014 à 15:26, Mathias Wolkert <tias@netnod.se> a écrit :
>
> Hi
>
>> On 9/29/14 11:15 AM, Mathias Wolkert wrote:
>> My SE says that defect was caused by using 32bit counters. So I'm rolling it out now.
>>
>> First one looks ok.
>
> I was wrong andso was my SE. snmp counters are borked and disabling snmp
> cache is a workaround.
>
> Apart from that 5.6d seems ok.
>
> /Tias
>
>>
>> /Tias
>>
>>
>>> 28 sep 2014 kl. 10:48 skrev Youssef Bengelloun-Zahr <youssef@720.fr>:
>>>
>>> Hello Eldon,
>>>
>>> Any feedbacks from BTAC regarding that SNMP defect ?
>>>
>>> Best regards.
>>>
>>>
>>>
>>>> Le 8 sept. 2014 à 06:54, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>>
>>>> I don't have any more information than that, sorry. They didn't need my
>>>> help to reproduce it, so I suspect others have reported the same issue.
>>>> FWIW, I didn't notice this with 5.6c, but we didn't deploy that version
>>>> as extensively.
>>>>
>>>> --
>>>> Eldon Koyle
>>>> Information Technology
>>>> Utah State University
>>>> --
>>>> For certain people, after fifty, litigation takes the place of sex.
>>>> -- Gore Vidal
>>>>
>>>>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
>>>>> Hi,
>>>>>
>>>>> This DEFECT isn't listed in the official Brocade KB. Can you tell us a little bit more about it (affected versions, etc.) ?
>>>>>
>>>>> I will ask my SE to look it up.
>>>>>
>>>>> Thanks for the feedback.
>>>>>
>>>>> Best regards.
>>>>>
>>>>>
>>>>>
>>>>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <esk-puck.nether.net@esk.cs.usu.edu> a écrit :
>>>>>>
>>>>>> I finally heard back today, not sure how long it will take them to fix
>>>>>> it:
>>>>>>
>>>>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips during SNMP IfInOctets Polling
>>>>>>
>>>>>> I thought saw something about SNMP caching in the changelog... I'm
>>>>>> wondering if they did something wrong there.
>>>>>>
>>>>>> --
>>>>>> Eldon Koyle
>>>>>> Information Technology
>>>>>> Utah State University
>>>>>>
>>>>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
>>>>>>> Hello Eldon,
>>>>>>>
>>>>>>> Any news from BTAC ?
>>>>>>>
>>>>>>> Best regards.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr> a écrit :
>>>>>>>>
>>>>>>>> Hello Eldon,
>>>>>>>>
>>>>>>>> Any news from BTAC ?
>>>>>>>>
>>>>>>>> Best regards.
>>>
>>> _______________________________________________
>>> foundry-nsp mailing list
>>> foundry-nsp@puck.nether.net
>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>>
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

Dear All,

I just got yesterday from my SE the details of NI 5.6e patch release (GA
targeted for 12/16) and the DEFECTs that will be corrected, and there are
quite a lot of them.

Among them, there is that SNMP (reported by Mathias W) defect and the one
related to the mac adresses flapping messages on CER-RT (reported by
Clement C) corrected.

You can all read about it here :

http://freepdfhosting.com/34b6a9eb39.pdf

HTH.

Y.



2014-10-05 17:17 GMT+02:00 Youssef Bengelloun-Zahr <youssef@720.fr>:

> Hi Mathias,
>
> Has it been validated by BTAC ? Any ETA on a defentive correction ?
>
> Best regards.
>
>
>
> > Le 5 oct. 2014 à 15:26, Mathias Wolkert <tias@netnod.se> a écrit :
> >
> > Hi
> >
> >> On 9/29/14 11:15 AM, Mathias Wolkert wrote:
> >> My SE says that defect was caused by using 32bit counters. So I'm
> rolling it out now.
> >>
> >> First one looks ok.
> >
> > I was wrong andso was my SE. snmp counters are borked and disabling snmp
> > cache is a workaround.
> >
> > Apart from that 5.6d seems ok.
> >
> > /Tias
> >
> >>
> >> /Tias
> >>
> >>
> >>> 28 sep 2014 kl. 10:48 skrev Youssef Bengelloun-Zahr <youssef@720.fr>:
> >>>
> >>> Hello Eldon,
> >>>
> >>> Any feedbacks from BTAC regarding that SNMP defect ?
> >>>
> >>> Best regards.
> >>>
> >>>
> >>>
> >>>> Le 8 sept. 2014 à 06:54, Eldon Koyle <
> esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >>>>
> >>>> I don't have any more information than that, sorry. They didn't need
> my
> >>>> help to reproduce it, so I suspect others have reported the same
> issue.
> >>>> FWIW, I didn't notice this with 5.6c, but we didn't deploy that
> version
> >>>> as extensively.
> >>>>
> >>>> --
> >>>> Eldon Koyle
> >>>> Information Technology
> >>>> Utah State University
> >>>> --
> >>>> For certain people, after fifty, litigation takes the place of sex.
> >>>> -- Gore Vidal
> >>>>
> >>>>> On Sep 05 21:18+0200, Youssef Bengelloun-Zahr wrote:
> >>>>> Hi,
> >>>>>
> >>>>> This DEFECT isn't listed in the official Brocade KB. Can you tell us
> a little bit more about it (affected versions, etc.) ?
> >>>>>
> >>>>> I will ask my SE to look it up.
> >>>>>
> >>>>> Thanks for the feedback.
> >>>>>
> >>>>> Best regards.
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Le 5 sept. 2014 à 21:08, Eldon Koyle <
> esk-puck.nether.net@esk.cs.usu.edu> a écrit :
> >>>>>>
> >>>>>> I finally heard back today, not sure how long it will take them to
> fix
> >>>>>> it:
> >>>>>>
> >>>>>> DEFECT000527089: 000527089 Seeing unexpected traffic spikes/dips
> during SNMP IfInOctets Polling
> >>>>>>
> >>>>>> I thought saw something about SNMP caching in the changelog... I'm
> >>>>>> wondering if they did something wrong there.
> >>>>>>
> >>>>>> --
> >>>>>> Eldon Koyle
> >>>>>> Information Technology
> >>>>>> Utah State University
> >>>>>>
> >>>>>>> On Sep 04 21:14+0200, Youssef Bengelloun-Zahr wrote:
> >>>>>>> Hello Eldon,
> >>>>>>>
> >>>>>>> Any news from BTAC ?
> >>>>>>>
> >>>>>>> Best regards.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Le 18 août 2014 à 21:00, Youssef Bengelloun-Zahr <youssef@720.fr>
> a écrit :
> >>>>>>>>
> >>>>>>>> Hello Eldon,
> >>>>>>>>
> >>>>>>>> Any news from BTAC ?
> >>>>>>>>
> >>>>>>>> Best regards.
> >>>
> >>> _______________________________________________
> >>> foundry-nsp mailing list
> >>> foundry-nsp@puck.nether.net
> >>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> foundry-nsp@puck.nether.net
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
>



--
Youssef BENGELLOUN-ZAHR