topic RE: X670 15.3.2.11 stops forwarding random traffic in ExtremeSwitching (EXOS/Switch Engine)

X670 15.3.2.11 stops forwarding random traffic

Dawid_Chrzan — Fri, 09 Jan 2015 21:05:00 GMT

Hi,
X670 with XOS 15.3.2.11 - started to act quite weird.
It stopped to forward some packets from some mac addresses.
We use port mirroring - and i heard that sometimes - xos starts to lose random traffic when using old firmware.
We rebooted - and all worked OK.
But today we have similar problem.

We have been sugested to upgrade to 15.6.1.4 or 15.5.3.4 patch1-2. Is it a good idea ?
Any info about stability of these versions?

RE: X670 15.3.2.11 stops forwarding random traffic

Bill_Stritzinge — Fri, 09 Jan 2015 21:52:00 GMT

There were some issues using mirroring on some of the early releases of 15.3.2 - If you want to stay on that build level, the latest version is 15.3.4.6-patch1-2 - It is a very stable release. Please let me know if you have any other questions or need anything else. If you continue to have issues, if you haven't already I would open a case with GTAC just to track and provide support if necessary.

Bill

RE: X670 15.3.2.11 stops forwarding random traffic

PARTHIBAN_CHINN — Fri, 09 Jan 2015 22:39:00 GMT

This is a known issue.
you should upgrade to fix the problem

RE: X670 15.3.2.11 stops forwarding random traffic

Dawid_Chrzan — Sat, 10 Jan 2015 05:05:00 GMT

Thanks.
I will try 15.3.4.6-patch1-10 that i received.
Is multicast routing (PIM-SM) and VMAN stable in that realease ?

RE: X670 15.3.2.11 stops forwarding random traffic

Johan_Lehto — Thu, 05 Feb 2015 20:00:00 GMT

"This is a known issue." - do you have any references for this statement?

RE: X670 15.3.2.11 stops forwarding random traffic

BrandonC — Thu, 05 Feb 2015 23:54:00 GMT

I believe the known issue Parthiban is referring to is PD4-4490184741. This is documented in the EXOS 15.3.1.4-patch1-36 release notes, as this was the first release that included the fix for this issue.

RE: X670 15.3.2.11 stops forwarding random traffic

Dawid_Chrzan — Sun, 08 Feb 2015 02:43:00 GMT

15.3.4.6-patch1-10 solved the issue