v2.0.9rc2 Bug Reports and Comments - WS3 Firmware

[Stephen]

Latest WS3 Release Candidate: v2.0.9rc2

Click HERE to download WS3 firmware v2.0.9rc2 - Released 3/14/2024

FIXED/CHANGED
- Fixed undefined behavior caused by dash characters in switch name - rc1
- STP/RSTP/MSTP Roles now correctly displayed in web UI and CLI - rc2
- Fixed STP/RSTP/MSTP instability handling Multicast Frames - rc2

NOTE:
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.

KNOWN ISSUES

- IPv6 has been disabled pending investigation
- IGMP Snooping has been found to cause instability with STP, it has been disabled pending investigation
- If you have an OCP on a port try using a different port see if bad port or problem follows the cable.


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

Released 3/14/2024

[jt.jofre]

Hello there,
I recently adquired a WS3 with 2.0.8 version. After sent to production i realized that the CPU was 99% all time.
After I upgraded to 2.0.9rc2 the CPU is still at 99% all the time.
this is top command output:

Code: Select all

 PID PPID USER STAT VSZ %VSZ %CPU COMMAND
 45 1 admin S 484m 196% 14% /usr/bin/switch_app
 6677 1 admin R 2448 1% 5% netonix_app -c
20782 1 admin R 2448 1% 5% netonix_app -c
 6703 1 admin R 2448 1% 4% netonix_app -c
 1592 1 admin R 2448 1% 4% netonix_app -c
 1658 1 admin R 2448 1% 4% netonix_app -c
10747 1 admin R 2448 1% 4% netonix_app -c
10780 1 admin R 2448 1% 4% netonix_app -c
14291 1 admin R 2448 1% 4% netonix_app -c
14324 1 admin R 2448 1% 4% netonix_app -c
20749 1 admin R 2448 1% 4% netonix_app -c
 6644 1 admin R 2448 1% 4% netonix_app -c
10813 1 admin R 2448 1% 4% netonix_app -c
14357 1 admin R 2448 1% 4% netonix_app -c
17666 1 admin R 2448 1% 4% netonix_app -c
17732 1 admin R 2448 1% 4% netonix_app -c
20716 1 admin R 2448 1% 4% netonix_app -c
17699 1 admin R 2448 1% 4% netonix_app -c
26170 25936 admin R 3260 1% 1% top
 

System: show status

Code: Select all

System
------
Current Time: 03/26/2024 01:43:14
Uptime: 959203.500000 seconds
CPU Usage: 99%
Memory Usage: 125.98 MB
MAC Address: --
IP Address: --
Firmware Version: 2.0.9rc2
Model: WS3-14-600-DC
Board Rev: D
Power
-----
Board 24V: 25.3 V
Board 3V: 3.3 V
Power Supply Input Voltage: 53.1 V
Power Supply Input Current: 0.5 A
Power Supply Output Voltage: 51.6 V
Thermal
-------
Board Temp: 37 C
CPU Temp: 47 C
PHY Temp: 59 C
Power Supply Board Temp: 30 C
Power Supply Heatsink #1 Temp: 23 C
Power Supply Heatsink #2 Temp: 23 C
Power Supply Controller Temp: 53 C
Cooling
-------
Fan 1 Speed: 2760 RPM
Fan 2 Speed: 2880 RPM
Fan 3 Speed: 2610 RPM


Is there something I can do lower CPU usage?
Thank you.

[Stephen]

By any chance are you using the Netonix Manager?

[jt.jofre]

Hi,
I have netonix manager for all my devices, but this WS3 is not added yet.

[Stephen]

Please take a look at this forum thread to see if any of the details mentioned may apply to your device setup and network.

[kblazk]

So i have a WS3 running the 2.0.9rc2 that I just deployed. Was replacing a really old WS-12-250A that was running 1.5.14 firmware. Here is what I have notice. The same total aggregate wattage displayed issue across all ports not showing correctly which was mentioned before in the 2.0.8 still exists.

But my biggest issue is I am getting falsing on the 48VH ports when trying to power an Aviat 80ghz radio that was running perfectly fine in the WS-12-250A. (power draw is 55.6 watts on this radio when fully booted up).

I am powering a AF24 just fine on Port #3. Trying to Power the Aviat on Port 4 and it never starts drawing power. Log shows: "Port 4 cable check results: Abnormal termination, Abnormal termination, Abnormal termination, Abnormal termination". I have moved it to ports 2,3,6 and it does the same thing. I tried disabled Smart POE and it still does nothing. If I try to power it with 48v (non-H) it will power up. (these Aviats take like 5+ minutes before they fully power up so the power draw is minimal 20-25 watts initially so powering with non-H is ok as long as i don't let it go past 5 minutes that way).

One time i was able to get it to power up i flipped it with the AF24 that was on port 3 and it powered up. After it did I rebooted the WS3 and it went back to what it was doing before. I feel like its not the radio because it powers fine on the older Netonix Switch. My WS3 is revision D if that matters.

[sirhc]

What is the MAC address?

Did you have POE Smart disabled on the old switch?
IF THIS IS YES

You said you turned POE Smart off on the port in the WS3 and that did not help, correct?
IF THIS IS YES

If you use an AF24 POE brick does it power up fine then plug it into the switch port with POE OFF on that port.
IF THIS YES

IF ALL 3 ABOVE YES THEN THERE MAY BE A BUG IN THE WS3 FIRMWARE ON THE POE Smart DISABLE OPTION.

There was another radio years ago that had to have POE Smart DISABLED for the radio to work which is why the option was created. This option may not be working correctly in the WS3 due to the AOCP.

[backtick]

Looks like emails are not working with 2.0.9rc2. Test button is missing so cannot test functionality. WS line is flawless with email outs, can this be fixed?

[klosey]

We have purchased several WS3-14-600-DC to start upgrading some of our existing WS-12-250-DC but so far have not found the WS3-14-600-DC to be a usable product for us. The GUI is very slow/laggy and CPU usage often shows close to maxed out. This is a problem we remember from older versions of firmware in years past on netonix products but looks like it's back with the WS3-14-600-DC running 2.0.9rc2.

Our biggest problem so far is "OCP" We have found on powering up Ubiquiti radios, OCP will often not allow the port to power up, we will move the radio to different ports on the switch and eventually find a port that will power up the radio, to then put the radio back to the original port and then it will work, sometimes. All these radio's and cables have worked fine for years on the WS-12-250-DC but not when plugged into the WS3-14-600-DC. We have switched back to WS-12-250-DC and it works great, WS-12-250-DC is a great stable switch.

We are hoping for some fixes in newer firmware for the WS3-14-600-DC soon as it appears others are seeing similar issues?

MAC address of last WS3-14-600-DC we were testing with these issues is ec:13:b2:89:02:26

Thanks,
Ken

[sirhc]

We have purchased several WS3-14-600-DC to start upgrading some of our existing WS-12-250-DC but so far have not found the WS3-14-600-DC to be a usable product for us. The GUI is very slow/laggy and CPU usage often shows close to maxed out. This is a problem we remember from older versions of firmware in years past on netonix products but looks like it's back with the WS3-14-600-DC running 2.0.9rc2.

Our biggest problem so far is "OCP" We have found on powering up Ubiquiti radios, OCP will often not allow the port to power up, we will move the radio to different ports on the switch and eventually find a port that will power up the radio, to then put the radio back to the original port and then it will work, sometimes. All these radio's and cables have worked fine for years on the WS-12-250-DC but not when plugged into the WS3-14-600-DC. We have switched back to WS-12-250-DC and it works great, WS-12-250-DC is a great stable switch.

We are hoping for some fixes in newer firmware for the WS3-14-600-DC soon as it appears others are seeing similar issues?

MAC address of last WS3-14-600-DC we were testing with these issues is ec:13:b2:89:02:26

Thanks,
Ken

This unit was purchased 09/22/2023 by MBSI WAV LP. They placed restock on that unit 4/12/2024 so you would have had to have had that unit for a year?
It is out of warranty but you can send to Julian at julian.lorah@wisprepairs.us for repair or diagnostics. I doubt this is firmware related but we will have new firmware in a couple months.

Grasping at straws.
Are you using any type of Ethernet surge protection? If so try removing them, they are useless to protect against ground current which is 99% of damage seen in this environment and surge protectors do nothing to prevent AC ground current but could mess with OCP.