v1.5.1rcX Bug Reports and Comments

[lligetfa]

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

What would happen if we replace the old fans with the new ones on these legacy models? If the code only looks at the model revision how would it know the version of fan?

I ask cuz my fans are in need of replacing but have been contemplating putting in lower CFM fans so they don't short cycle as much.

[sirhc]

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

What would happen if we replace the old fans with the new ones on these legacy models? If the code only looks at the model revision how would it know the version of fan?

I ask cuz my fans are in need of replacing but have been contemplating putting in lower CFM fans so they don't short cycle as much.

The software detects which fan it is on boot up.

[sirhc]

Well be careful which fan you use.

Our old fans: 4 armature 100Hz low speed 3K +/-
Our new fans: 2 armature 25KHz low speed 4K +/-

There are several other flavors of 24V fans with differnt Hz

Now technically any 24V Tach (3 wire) fan will work but will default to MIXED mode if not compatible with our 100Hz or 25Kz which will then be either ON or OFF full speed then the Hz does not matter as it is just straight 24V to achieve this with no pulse modulation.

[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/RC11

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
RC11 Released 12/27/2018

[nneiwert@wildwisp.com]

Hello Netonix,

Any chance of a new FW stable release coming out soon? I get the RC mode of operation that you have been in for a while and appreciate the benefit of some recent releases but it would be nice to see a well tested stable version that is not RC come out again now that you have solved a lot of issues.
Maybe time for a 1.5.2 release?
Thanks.

[wtm]

Still can't run LAGs on this version without the switch getting "touchy" to reboots ? Don't have the problem on 1.5.0

[sirhc]

Still can't run LAGs on this version without the switch getting "touchy" to reboots ? Don't have the problem on 1.5.0

Your going to have to be more specific.

I am running LACP LAGs with v1.5.1rc11 between 2 Netonix WS-24-400A and several others with no issues

I am running STATIC LAGs with v1.5.1rc11 between Netonix and Cisco routers with no issues.

I need to finalize v1.5.1 as it is needed to fix issue with newer units with the new model of fans.

[wtm]

For what ever reason, when we had 1.5.1 rc in it, and we tried to change "anything" on switch B, it would become inaccesible, and we had to go into the switch A, on the remote end, un-lag our backhauls, then switch B would come back up and be accessible again. Then we could re-establish the lags.

Don't have that problem on 1.5.0

Not sure what changed between the 2 firmwares?

[sirhc]

For what ever reason, when we had 1.5.1 rc in it, and we tried to change "anything" on switch B, it would become inaccesible, and we had to go into the switch A, on the remote end, un-lag our backhauls, then switch B would come back up and be accessible again. Then we could re-establish the lags.

Don't have that problem on 1.5.0

Not sure what changed between the 2 firmwares?

So in the picture below you can see LACP is linked up between 2 switches.
One switch is running v1.5.0 and the other v1.5.1rc11

Now to be fair both were originally v1.5.0 linked up then about 21 days ago I upgraded both to v1.5.1rc11 one at a time as I was doing so remotely and I saw no issues.

They both had been working fine at v1.5.1rc11 for 21 days.

Now today I downgraded NL-WS1 to v1.5.0 and the LACP failed to come up. I then rebooted the switch and it came up. Which was ODD I give you that. I think it was more the fact that the SFP modules I have in these switches act weird from time to time?

I then proceeded to upgrade and downgrade them a couple times with no issues?

CLICK IMAGE BELOW TO VIEW FULL SIZE

[sirhc]

For what ever reason, when we had 1.5.1 rc in it, and we tried to change "anything" on switch B, it would become inaccesible, and we had to go into the switch A, on the remote end, un-lag our backhauls, then switch B would come back up and be accessible again. Then we could re-establish the lags.

Don't have that problem on 1.5.0

Not sure what changed between the 2 firmwares?

After some further testing I think I am able to recreate this in v1.5.1rc11. Making some obscure change(s) does seem to sometimes (randomly) stop the LACP LAG. If I then disable the ports and re-enable the ports in the LAG it brings the LAG backup.

I need to confirm this does NOT happen in v1.5.0 then go from there.