v1.5.12 Bug Reports and Comments

[coreinput]

Upgraded from 1.5.8 running since September 2021 and everything went smooth (and no POE loss). Hats off to the team including beta testers for making this release happen. Thanks!

[mayheart]

I ran into an issue upgrading some 1.5.3 units to 1.5.12.

Only a few ports appear under STP tab instead of all 14 or 26.

It also causes packet loss to the switch and this appears in the log files:

Mar 18 09:43:02 monitor: restarting vtss_appl
Mar 18 09:43:16 monitor: restarting vtss_appl
Mar 18 09:43:30 monitor: restarting vtss_appl
Mar 18 09:43:44 monitor: restarting vtss_appl
Mar 18 09:43:57 monitor: restarting vtss_appl
Mar 18 09:44:10 monitor: restarting vtss_appl
Mar 18 09:44:11 monitor: restarting snmpd
Mar 18 09:44:25 monitor: restarting vtss_appl
Mar 18 09:44:25 monitor: restarting snmpd
Mar 18 09:44:39 monitor: restarting vtss_appl
Mar 18 09:44:39 monitor: restarting snmpd
Mar 18 09:44:53 monitor: restarting vtss_appl

I do have a backed up config from these units before they were factory defaulted if you need a copy. I suspect there might be some garbage that I can't see in either the port or vlan labels.

[sirhc]

I ran into an issue upgrading some 1.5.3 units to 1.5.12.

Only a few ports appear under STP tab instead of all 14 or 26.

It also causes packet loss to the switch and this appears in the log files:

Mar 18 09:43:02 monitor: restarting vtss_appl
Mar 18 09:43:16 monitor: restarting vtss_appl
Mar 18 09:43:30 monitor: restarting vtss_appl
Mar 18 09:43:44 monitor: restarting vtss_appl
Mar 18 09:43:57 monitor: restarting vtss_appl
Mar 18 09:44:10 monitor: restarting vtss_appl
Mar 18 09:44:11 monitor: restarting snmpd
Mar 18 09:44:25 monitor: restarting vtss_appl
Mar 18 09:44:25 monitor: restarting snmpd
Mar 18 09:44:39 monitor: restarting vtss_appl
Mar 18 09:44:39 monitor: restarting snmpd
Mar 18 09:44:53 monitor: restarting vtss_appl

I do have a backed up config from these units before they were factory defaulted if you need a copy. I suspect there might be some garbage that I can't see in either the port or vlan labels.

When you factory defaulted them and then MANUALLY set them back up did they work fine?

[mayheart]

Yes, it was fine after factory defaulting and re-entering all the data.

[TomO]

QinQ and Double tagging on vlans seem to be missing on 1.5.12. Just checked all three of my switches on 1.5.11 and they are working there.

I can only only select T, U and E on 1.5.12
(

I did verify your report, you are correct. I can get this fixed in the next release.

Hi team,

Do we have an ETA for the next release? I am looking forward to being able to log in to our switches on my preferred browser AND use double tagging :)

Thanks!

Tom.

[Dawizman]

May have found a bug. Not sure how to reproduce though.

I just had three switches on different network segments reboot at roughly the same time. The only thing these switches have in common is that I pushed a mass upgrade from netonix manager to 1.5.12 on them at the same time, so they would have had the same uptime.

Not sure what other info would be beneficial here.

[sakita]

Did they reboot immediately after the update push? A reboot is normal as part of the update process so if they were pushed at the same time they would reboot at the same time... or are you saying that they were updated then all rebooted later but at the same time?

[IntL-Daniel]

May have found a bug. Not sure how to reproduce though.

I just had three switches on different network segments reboot at roughly the same time. The only thing these switches have in common is that I pushed a mass upgrade from netonix manager to 1.5.12 on them at the same time, so they would have had the same uptime.

Not sure what other info would be beneficial here.

If you do not mean the reboot just after the upgrade, maybe you are facing to RSTP/loop issue mentioned here.

[Dawizman]

Did they reboot immediately after the update push? A reboot is normal as part of the update process so if they were pushed at the same time they would reboot at the same time... or are you saying that they were updated then all rebooted later but at the same time?

I should have been more clear. The update was ~10days prior to the unexplained reboot.

[Dawizman]

Well on third glance, it may actually be an issue with Netonix manager. One switch definitely rebooted, however the other switched that I thought rebooted at the same time did not actually reboot. Netonix manager is just showing a short uptime, and it happened to line up with when the one switch did reboot.

What's odd to me is that the same switches that I thought rebooted now show a very short (5 hour) uptime in netonix manager, but in the GUI of the switch they are ~20days correlating to the 1.5.12 update.