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 <[email protected]> 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 <[email protected]> a
> >>> écrit :
> >>>
> >>> Who wants to test it….
> >>>
> >>> Kindest Regards
> >>>
> >>> James Braunegg
> >>> P: 1300 769 972 | M: 0488 997 207 | D: (03) 9751 7616
> >>> E: [email protected] | 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:[email protected]] On Behalf
> >>> Of Youssef Bengelloun-Zahr
> >>> Sent: Friday, August 01, 2014 5:14 AM
> >>> To: Skylar MacMinn
> >>> Cc: [email protected]
> >>> Subject: Re: [f-nsp] Netiron 5.6 feedbacks
> >>>
> >>> Hi all,
> >>>
> >>> 560d is out :-)
> >>>
> >>> Y.
> >>>
> >>>
> >>>
> >>> 2014-07-18 15:47 GMT+02:00 Skylar MacMinn <[email protected]>:
> >>> 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:[email protected]] On Behalf
> >>> Of Youssef Bengelloun-Zahr
> >>> Sent: Friday, July 18, 2014 8:43 AM
> >>> To: Josh Galvez
> >>>
> >>> Cc: [email protected]
> >>> 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 <[email protected]>:
> >>> 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
> >>> <[email protected]> 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: [email protected] | 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:[email protected]] On Behalf
> >>> Of Youssef Bengelloun-Zahr
> >>> Sent: Monday, May 26, 2014 6:48 PM
> >>>
> >>> To: Wouter de Jong
> >>> Cc: <[email protected]>
> >>> 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 <[email protected]>:
> >>> Hi Youssef,
> >>>
> >>> OK, that is the same date I received :)
> >>>
> >>> Regards,
> >>>
> >>> Wouter
> >>>
> >>>> -----Original Message-----
> >>>> From: Youssef Bengelloun-Zahr [mailto:[email protected]]
> >>>> Sent: Sunday, May 25, 2014 22:16
> >>>> To: Wouter de Jong
> >>>> Cc: <[email protected]>
> >>>> 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 <[email protected]> a
> >>>>>> écrit
> >>>>> :
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> Interesting... Did TAC give you 56d GA release date ?
> >>>>>
> >>>>> Y.
> >>>>>
> >>>>>
> >>>>>
> >>>>>> Le 25 mai 2014 à 12:57, Wouter de Jong <[email protected]> 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
> >>>>>> [email protected]
> >>>>>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>>
> >>>
> >>>
> >>> --
> >>> Youssef BENGELLOUN-ZAHR
> >>>
> >>> _______________________________________________
> >>> foundry-nsp mailing list
> >>> [email protected]
> >>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>>
> >>>
> >>> _______________________________________________
> >>> foundry-nsp mailing list
> >>> [email protected]
> >>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >>>
> >>>
> >>>
> >>> --
> >>> Youssef BENGELLOUN-ZAHR
> >>>
> >>>
> >>>
> >>> --
> >>> Youssef BENGELLOUN-ZAHR
> >
> >> _______________________________________________
> >> foundry-nsp mailing list
> >> [email protected]
> >> http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
>
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
