v1.5.1rcX Bug Reports and Comments

[sirhc]

Erm... I see we are up to 1.5.1rc7, but the last change log I can find is for RC4. Can anyone point me to the 5, 6, & 7 change logs?

If you go to where you download the firmware which is the main place release notes are kept you will find this:
viewtopic.php?f=17&t=240#p848

FIXED/CHANGED
- Fixed voltage input calibration for the WS-8-150-DC - RC1
- Fixed services running on IPv6 - RC2
- Fixed being able to bypass console login by hitting CTRL-C - RC2
- Fixed MSTP setting instance forwarding state - RC2
- Fixed UI on ERPS tab to prevent footer from from being mangled - RC3
- Fixed ERPS MEPs issue that triggered a Signal Fail on a ring when port not in the ring is disconnected/disabled - RC3
- Fixed ERPS issue that prevented access to Management VLAN when added to the protected VLAN list - RC3
- Fixed ERPS protected VLANs would not forward packets outside of the ring - RC3
- Fixed SNMP (Broken in v1.5.1rc3) - RC4
- Fixed Access Controls for a confirmed security vulnerability - RC5 (for more details check this thread: viewtopic.php?f=12&t=4103 )
- Fixed UI bug in Access Control List - RC6
- Fixed DHCP failure when switch has a static ip assigned to a vlan - RC7
- Increased time buffer for warning voltage email trigger - RC7

ENHANCEMENTS

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed

RC1 Released 6/20/2018
RC2 Released 7/10/2018
RC3 Released 8/2/2018
RC4 Released 8/11/2018
RC5 Released 9/17/2018
RC6 Released 9/19/2018
RC7 Released 10/1/2018

[wtm]

Well, second time we have now had a problem with LAG's !
We are working on installing 2 additional AF11x links this next week, and I went into one of our WS-26-500-DC switches to see what ports were available to use. I decided to change a "Description" on one of the existing unused ports to assign it for one of the links to be installed this week. As soon as I hit "Apply" the entire network went down. I waited for a few minutes hoping that the switch would come back up as normal, but that did not happen.

I tried to re-log in again, to no avail. It would not respond to a ping either.

I then noticed that on Aircontrol that the 2 existing AF11x backhaul links that were currently "Lag'd" on that switch were still connected, but we were just not getting any through put to the switch.

I was able to log into the Netonix switch which was upstream from that one switch, and turn off the LAG on the 2 AF11x's. The network immediately came back up. Once it established, I was able to turn the LAG back on again. Everything seemed to be running as before the situation happened.

This switch is running the current 1.5.1rc6 on it. This was what we had problems with on the upstream switch, when we added more LAGs, and had to downgrade the firmware to 1.5.0 to get it to work!

We will be downgrading this switch to the 1.5.0 and will try this again. I have the feeling that we will find out that the current 1.5.1 firmware is the problem.

The BIG QUESTION is, why should any change on something as minor as a "Port Description" totally screw up the working LAGs ?

As we are continuing to expand our network, we will be installing more AF11x links, and will need to setup more LAG connections. We can't have this type of situation happen in the future !

[sirhc]

The BIG QUESTION is, why should any change on something as minor as a "Port Description" totally screw up the working LAGs ?

Several people have reported this or similar circumstance. It is on the list to figure out but does not happen all the time so hard to replicate. I think it has something to do with the fact that saving of something silly re-applies the VLAN Matrix or something else important which could interrupt traffic.

I suspect this is what caused your issue, meaning downgrading to v1.5.0 is not the fix but rather the random event from saving the config on a insignificant thing like Description reapplied the config to VLANs or something else. Again a random issue "I think" more than downgrading to v1.5.0 ?????

Sorry for the issue but if you can nail it down so we can look at it more closely.

[wtm]

Hoping to do more work on it within the next few days, as we need to get the new AF11x units up this week.

[Stephen]

v1.5.1rcX wrote:
FIXED/CHANGED
- Fixed voltage input calibration for the WS-8-150-DC - RC1
- Fixed services running on IPv6 - RC2
- Fixed being able to bypass console login by hitting CTRL-C - RC2
- Fixed MSTP setting instance forwarding state - RC2
- Fixed UI on ERPS tab to prevent footer from from being mangled - RC3
- Fixed ERPS MEPs issue that triggered a Signal Fail on a ring when port not in the ring is disconnected/disabled - RC3
- Fixed ERPS issue that prevented access to Management VLAN when added to the protected VLAN list - RC3
- Fixed ERPS protected VLANs would not forward packets outside of the ring - RC3
- Fixed SNMP (Broken in v1.5.1rc3) - RC4
- Fixed Access Controls for a confirmed security vulnerability - RC5 (for more details check this thread: viewtopic.php?f=12&t=4103 )
- Fixed UI bug in Access Control List - RC6
- Fixed DHCP failure when switch has a static ip assigned to a vlan - RC7
- Increased time buffer for warning voltage email trigger - RC7
- MAC Table search works using colons and dashes - RC8

ENHANCEMENTS

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed

RC1 Released 6/20/2018
RC2 Released 7/10/2018
RC3 Released 8/2/2018
RC4 Released 8/11/2018
RC5 Released 9/17/2018
RC6 Released 9/19/2018
RC7 Released 10/1/2018
RC8 Released 11/5/2018

[mark]

Yes I have the same issue
Last night started loosing a WS-12-150-DC running 1.5 fw at 12. 2 volts when the shut down is set to 11.5 volts
And the actual voltage of the batteries was 12.4 ,recorded by another volt meter I had connected
So replaced the switch with one on 1.5.7
So hope that sorts it
((( connected to batteries)))

[Stephen]

FIXED/CHANGED
- Fixed voltage input calibration for the WS-8-150-DC - RC1
- Fixed services running on IPv6 - RC2
- Fixed being able to bypass console login by hitting CTRL-C - RC2
- Fixed MSTP setting instance forwarding state - RC2
- Fixed UI on ERPS tab to prevent footer from from being mangled - RC3
- Fixed ERPS MEPs issue that triggered a Signal Fail on a ring when port not in the ring is disconnected/disabled - RC3
- Fixed ERPS issue that prevented access to Management VLAN when added to the protected VLAN list - RC3
- Fixed ERPS protected VLANs would not forward packets outside of the ring - RC3
- Fixed SNMP (Broken in v1.5.1rc3) - RC4
- Fixed Access Controls for a confirmed security vulnerability - RC5 (for more details check this thread: viewtopic.php?f=12&t=4103 )
- Fixed UI bug in Access Control List - RC6
- Fixed DHCP failure when switch has a static ip assigned to a vlan - RC7
- Increased time buffer for warning voltage email trigger - RC7
- MAC Table search works using colons and dashes - RC8
- update for new fans - RC9

ENHANCEMENTS

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed

RC1 Released 6/20/2018
RC2 Released 7/10/2018
RC3 Released 8/2/2018
RC4 Released 8/11/2018
RC5 Released 9/17/2018
RC6 Released 9/19/2018
RC7 Released 10/1/2018
RC8 Released 11/5/2018
RC9 Released 12/23/2018

[Stephen]

FIXED/CHANGED
- Fixed voltage input calibration for the WS-8-150-DC - RC1
- Fixed services running on IPv6 - RC2
- Fixed being able to bypass console login by hitting CTRL-C - RC2
- Fixed MSTP setting instance forwarding state - RC2
- Fixed UI on ERPS tab to prevent footer from from being mangled - RC3
- Fixed ERPS MEPs issue that triggered a Signal Fail on a ring when port not in the ring is disconnected/disabled - RC3
- Fixed ERPS issue that prevented access to Management VLAN when added to the protected VLAN list - RC3
- Fixed ERPS protected VLANs would not forward packets outside of the ring - RC3
- Fixed SNMP (Broken in v1.5.1rc3) - RC4
- Fixed Access Controls for a confirmed security vulnerability - RC5 (for more details check this thread: viewtopic.php?f=12&t=4103 )
- Fixed UI bug in Access Control List - RC6
- Fixed DHCP failure when switch has a static ip assigned to a vlan - RC7
- Increased time buffer for warning voltage email trigger - RC7
- MAC Table search works using colons and dashes - RC8
- update for new fans - RC9/RC10

ENHANCEMENTS

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed

RC1 Released 6/20/2018
RC2 Released 7/10/2018
RC3 Released 8/2/2018
RC4 Released 8/11/2018
RC5 Released 9/17/2018
RC6 Released 9/19/2018
RC7 Released 10/1/2018
RC8 Released 11/5/2018
RC9 Released 12/23/2018
RC10 Released 12/25/2018

[leighton]

With RC9 & RC10 I see there have been updates to the fan control, apparently having the fan cycle on less frequently - great. I'm curious about the difference between what's labeled "Cooling Mode: New Fan Mode" and "Cooling Mode: Legacy Fan Mode." On one of my WS-8-150-DC board rev F, it now shows as the new fan mode, and another (also board rev F) as the legacy mode. What is the difference between the two modes, and what results in a switch getting the new mode or the legacy mode?

Thanks, Leighton

[sirhc]

With RC9 & RC10 I see there have been updates to the fan control, apparently having the fan cycle on less frequently - great. I'm curious about the difference between what's labeled "Cooling Mode: New Fan Mode" and "Cooling Mode: Legacy Fan Mode." On one of my WS-8-150-DC board rev F, it now shows as the new fan mode, and another (also board rev F) as the legacy mode. What is the difference between the two modes, and what results in a switch getting the new mode or the legacy mode?

Thanks, Leighton

I am going to make a detailed post on this soon but basically SUNON had discontinued the fan we used and their replacement was "supposed" to be a drop in replacement.

THEY LIED

Long story as to why we did not catch it as they worked but didn't work as a drop in replacement, again LONG post will be coming with more details.

So units we produced with a the following MFG dates used the NEW fans and should get the newer firmware to compensate for the new fan.
WS-8-150-AC MFG date of 10-13-2018 or newer
WS-8-150-DC MFG date of 09-12-2018 or newer
WS-12-250-AC MFG date of 10-06-2018 or newer
WS-12-250-DC MFG date of 10-06-2018 or newer
WS-26-400-IDC MFG date of 10-18-2018 or newer

YOU SHOULD UPGRADE THE FIRMWARE FOR THE ABOVE MODELS

Not upgrading the firmware will not "harm" the units but the fans do not operate as we intend them too.

The reason rc10 came out right after rc9 was we later found out we did not code the detection right for older EOL WS-24-400A and WS-24-400B. - OOPS

The reason rc11 came out right after rc9 was for WS-12-250A and WS-12-250B, again older EOL units we failed to properly deal with.

But do you know how borring it is to do testing on all models, since I did not have one in shop I skipped the test since all other models passed but later caught it when I upgraded my own WISP's switches as most of my switches in service are the original WS-24-400A units. They last a long time when you have your grounding right.