v2.0.9rc1 Bug Reports and Comments - WS3 Firmware

[Stephen]

Latest WS3 Release Candidate: v2.0.9rc1

Click HERE to download WS3 firmware v2.0.9rc1 - Released 11/15/2023

FIXED/CHANGED
- Fixed undefined behavior caused by dash characters in switch name - rc1

NOTE:
This fix directly applies to changing the switch name to something like "switch-test-1", doing this caused severe delay's applying config's, switch lock-up, and unexpected behavior after reboots.
Due to the nature of the error, components of what was needed to fix this specific issue may have been responsible for other types of config changes causing similar error's. We will need feedback to verify if this is the case or not. During testing, we are now unable to replicate the behavior's described.
With any luck, this might solve the majority of stability issue's we're seeing on the WS3.

Some people have reported needing to default switch after upgrade to RC1. Probably more needed if you had a dash in the switch name.


Please let us know in this thread what you find when trying this firmware.

ENHANCEMENTS

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help

Released 11/15/2023

[backtick]

I can confirm everything that did not work now does work! The GUI seems snappier too, great stuff

Only problem that does not seem to go away is the OCP. 1,6,7 48VH ports allocated always need a Reset, whether or not there's a cable connected. Once its reset there is never a problem and cable diagnostics are clean. Port 1 has never powered a radio and the others see max 40W so I am stumped to as why its happening after every reboot. Any advice? Thanks

ps. the switch is on the bench; the entries are chronological

Nov 16 03:41:11 switch[45]: Disabling PoE power on port 6 (48VH-AF5XHD-) due to Over Current Protection
Nov 16 03:41:11 switch[45]: Disabling PoE power on port 7 (48VH-TO-SW06) due to Over Current Protection
Nov 15 22:43:52 switch[45]: Resetting over current protection on port 7
Nov 15 22:43:57 switch[45]: Port 7 cable check results: Open, Open, Open, Open
Nov 15 22:43:57 switch[45]: Port 7 passed PoE Smart cable check, turning on power
Nov 15 22:44:07 switch[45]: Resetting over current protection on port 6
Nov 15 22:44:11 switch[45]: Port 6 cable check results: Open, Open, Open, Open
Nov 15 22:44:11 switch[45]: Port 6 passed PoE Smart cable check, turning on power

[Stephen]

Glad to hear it helped, OCP issue might be a problem with init logic. Will investigate. If you don't mind, can you post your config for the ws3 that is doing this? It may assist with debugging.

[backtick]

Thanks, Sent you the file. I did a default and now the problems have disappeared. Ill keep you posted

edit: After resting for 5min and after cold boot still see the same ports giving OCP error

[Stephen]

Hello backtick,

Been looking into this one. Actually I can't seem to reproduce.
- tried with provided config after modifying slightly (password hash, ip's to work on my network, removed dropbear sshkey, etc) then did coldboot and software reboot
- set all available ports to 24V, 24VH, 48V, 48VH, software reboot and cold boot
- plugged in load within parameters and did coldboot/software boot

I have a few questions that might help us get some answers:
- my current model under test is a WS3-14-600-DC, is yours an AC?
- have these ports been used already and perhaps shorted at any point?
- do you have another WS3 you can check to see if you see the same issue's?

[sirhc]

Thanks, Sent you the file. I did a default and now the problems have disappeared. Ill keep you posted

edit: After resting for 5min and after cold boot still see the same ports giving OCP error

It could be a damaged or defective port. I would suggest RMA