v1.5.14 Bug Reports and Comments

[mayheart]

Expanding on the SFP issue.

I ran into this today. copper SFP on a 12 port AC switch.

I made a vlan change and the port went down. This was in the log until I manually shut the port down on the other side and brought it back up.

Code: Select all

Jun 24 15:55:44 SFP: I2C communication down to SFP 1, attempting to establish communications
Jun 24 15:56:32 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:56:32 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:56:42 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:56:42 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:02 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:02 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:12 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:12 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:22 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:22 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:32 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:32 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:42 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:57:42 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:58:22 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:58:22 Port: link state changed to 'up' (1G) on port 14
Jun 24 15:58:38 Port: link state changed to 'down' on port 14
Jun 24 15:58:41 Port: link state changed to 'up' (1G) on port 14


state down was me forcing it down on the other side.

[jdiggity]

Not sure this is related to this release but I have a problem with DHCP snooping. While it does work as normal when I first enable it on a port. If I disable it it still continues to block DHCP traffic until I reboot the switch.


WS-8-150-DC

[LingHunt]

What is the recommended Version for using a VLAN?

I see the note from [ sirhc ] on Apr 26,2022 saying the VLAN issue is still under investigation.

I'm getting asked why I have not upgraded those switches past 1.5.8

Thanks in Advance - John Martin

[slarner]

Ive been having issues when adding vlan's it seams to drop all the ports. Which is annoying for PPPoE as it then has to re establish all the sessions.

[gilky1]

I have lost comms to 3 switches in the last two weeks. All are running 14. When you go to power cycle the device it appears the port (or maybe entire) configuration is lost as the POE lights are out. I believe I will have to go into the field to attempt recovery of these switches.

[IntL-Daniel]

I have lost comms to 3 switches in the last two weeks. All are running 14. When you go to power cycle the device it appears the port (or maybe entire) configuration is lost as the POE lights are out. I believe I will have to go into the field to attempt recovery of these switches.

Is it possible that you remotely edit/save some settings changes via mobile device just before you lost config?

[KBrownConsulting]

What is the recommended Version for using a VLAN?

I see the note from [ sirhc ] on Apr 26,2022 saying the VLAN issue is still under investigation.

I'm getting asked why I have not upgraded those switches past 1.5.8

Thanks in Advance - John Martin

The only reported problem with VLANs that I'm aware of was related to QinQ and Double tagging which are the "Q" & "D" options on the VLANs page. If you don't use those options 1.5.14 is the recommended release.

I'll also mention that despite the fact that sirhc confirmed the issue with QinQ and Double tagging, I haven't been able to reproduce it... That's based on the consideration that the issue was reported as:

"QinQ and Double tagging on vlans seem to be missing on 1.5.12 ... I can only only select T, U and E on 1.5.12"

But I've checked on a few different model switches an I can still select & enable the Q & D VLAN options with 1.5.14. It's only possible if the port doesn't have an Untagged (U) VLAN assigned, which might be a bug itself, BUT that appears to be the way it has worked on older firmware versions as far back as 1.5.5 based on very limited testing I've done so this doesn't seem to be a new issue with 1.5.12. IMPORTANT: I don't actually use either the Q or D VLAN options so I can't comment on whether or not they actually work, but based on the original bug report about simply not being able to select them, I question what the actual issue is.


Long story short: If you don't use the Q or D VLAN options, then 1.5.14 is the recommended release, and even if you do use those features, you should probably try upgrading to 1.5.14 and see if it still works for you & then report back here.

[jpmoller]

I posted the original issue with the Q and D tagging not working. The option to apply those tags were simply missing when you went through the sequence of clicks.

I have had mixed results so far with the issue being present and not being present, but we have reverted to using 1.5.8 until the slew of issues have been fixed.

And on that note, I come bearing news I posted earlier somewhere between 1.5.11 - 1.5.14 posts about a potential memory leak I have encountered.

On advice from someone to look at disabling SNMP, I can confirm that when I disabled SNMP on the switch that demonstrated a potential memory leak, that available memory has remained high.

Below is an image of the trend showing a constant decline of available memory

Memory loss

Here is the switch memory after a fresh reboot and SNMP disabled. You can see uptime of switch is 1 minute

Switch reboot with SNMP disabled

And here we are almost 14 days later where the available memory is still the same as the day it was rebooted

Memory usage after 14 days

I have had SNMP enabled on the switch for less than 24 hours, and the available memory is again on the decline. I can currently observe this exact trend on about 5 different firmware versions dating all the way back to 1.4.9, all the way up to 1.5.11. And this issue isn't present on just one switch type. It is observed on the WS-8-150-DC, WS-12-250-DC, WS-26-500-DC and the WS-26-400-IDC. It's also observed on both older board revisions, as well as fresh out of the box revisions.

I'm happy to supply any diagnostic data if it will help get to the bottom of this.

[bipbaep]

Curious as to whether there is any development at Netonix?
Mysteriously quiet for a while now...

[KBrownConsulting]

While I agree it has seemed a little quieter than usual, they did just push out a new release candidate firmware for the WS3 switches 2 weeks ago...

viewtopic.php?f=17&t=7596