Request Feedback v1.1.0 - PLEASE

[adairw]

Chris, if yer still up,
the WS-12-250A that's running in my Data Center with 1.0.8 on it. should it be good to take straight to RC19 or should I do intermediate upgrades?

[sirhc]

Chris, if yer still up,
the WS-12-250A that's running in my Data Center with 1.0.8 on it. should it be good to take straight to RC19 or should I do intermediate upgrades?

Yes

[adairw]

I just got a FAN 2 is failing on my switch I just upgraded. thought that was fixed?

[sirhc]

I just got a FAN 2 is failing on my switch I just upgraded. thought that was fixed?

No, read a couple posts up
It is also listed as known issues with rc19

yep. 7 minutes until 12 midnight here.

sendgrid.com is just a smtp outbound mail service we use so we don't have to run our own smtp server in house. we were having trouble getting mail delivered to people with yahoo, hotmail and att.net email addresses and it fixed that.

I'm getting the false fan alert emails on the RC18 switch.

Yea Eric is looking into that issue. I think it is because we poll the fans one at a time and when we spin them up it takes a couple seconds for the second and or 3rd fan to register tach but we are checking rpm as soon as we apply power to the fans so during spin up 1 fan is showing RPM and the second and or third shows 0 until we mux shift to read the next fan and so the system thinks a fan is stopped. Just a simple logic over sight fans are fine.

CLICK HERE TO DOWNLOAD FIRMWARE v1.1.0rc19 - Released 2/4/2015
This version has all the new feature sets.
CURRENTLY UNDER FINAL TESTING FOR FINAL RELEASE.

FIXES
- fixed LACP and STP special packets "leaking" to other ports under rare circumstances and unique configurations

EXPLANATION
We have identified an issue with firmware version 1.1.0rc18. This issue specifically affects LACP and STP, or rather the BPDU packets that both protocols use to communicate with other bridges on the network. The symptoms of this bug are BPDU packets traversing the switch and being forwarded out other ports. This could cause LACP and STP to be unable to function properly, causing intermittent loops even when the switches were provisioned properly.

In my testing the only time that this downtime even would occur was when multiple Netonix switches were used in a ring topology with at least two LACP connections between the device, and while using STP for fault tolerance. This bug has been resolved in 1.1.0rc19.

KNOWN ISSUES OR REPORTED BUGS
- We still have FALSE positive fan failure messages in the switch log and if you have SMTP enable you will get FALSE email alert.
This is a FALSE positive and has been an issue for several releases but was forgotten about, we will address in the next release. - NON CRITICAL

Read down through this thread for firmware version details.

[adairw]

ah ok, missed that.

The WS-12 just completed it's upgrade from 1.0.8 to 1.1.0RC19.
It's up and running.
Mostly acting as a mid-span for 3 exalt G2 links and one AF24. There are also three RM5's trunked back through a single port to the router. No FC on this switch. MC is enabled. Also using SMTP, NTP & SNMP.
Passing 250Mb and all's well.

[tfadgen]

I just upgraded from rc18 to rc19 with no issues.

[WisTech]

I upgraded a brand new unit from 10/27/14 running I believe 1.0.1 straight to rc19, no problem!

[iggy05]

Thanks chris for the reply. That would probably be the case. Sick at home today but that has to be the issue. In that case everything seems to work fine! :)

[mayheart]

Running r19 on a switch stuck up a tower with fiber ran to it. No problems.

[LRL]

Chris,

Looks like I'm the only naysayer, Sorry.

When the switch is configured without STP or LAG enabled the switch doesn't handle BPDU packets correctly.
Specifically in the case where I'm noticing this we run RSTP through the switch. We don't want the switch participating in spanning tree and so far have kept STP disabled on it. I'm running RC19. I upgraded it from stable because we were seeing some leakage of BPDUs between VLANs and noticed the notation about the fix. I have MC enabled on all ports.

I haven't been able to wire shark it to be sure about what's happening but it appears the switch is acting as the root bridge even though STP is turned off. To boot with stp turned off in the switch and it acting as root all other bridges don't see the correct topology causing a loop.

PS, I was up till 5am upgrading and total forgot to hit submit.