Netonix Forums

Please post bug reports and comments on v1.4.9 ONLY in this thread.

v1.4.9 wrote:NOTE: IGMP snooping over VLANS, MSTP, and ERPS are still being developed so use these features at your own risk.

FIXED/CHANGED
- Fixed ubiquiti Discovery TAB with new ubiquiti firmware; not sure if this fixes where some have reported issues when doing a UBNT Discovery from a UBNT router causing issues with the Netonix switches?

- Fixed changing VLAN List in MSTP configuration
- Fixed MSTP root message
- Fixed to only show OCP controls if board has OCP

ENHANCEMENTS
- Added ifHighSpeed from IF-MIB
- Added option to enable both SNMP v1 and v2c

KNOWN ISSUES
- Loop Protection broken on SFP ports
- CPU utilization too high on WS-26-500-DC can cause reboots - will release v1.5.0rcX soon to fix this
- UI issues when not at 100% Zoom on browser.
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed

Released 12/27/2017

Please take a look at this lab config. We are testing ERPS functionality before put it in production, but no resuts.

4 Netonix in ring topology, erps control seems to work fine, but vlans declared in vlan monitor field appears to be blocked for all switch ports, in all ERPS working modes. If somebody have a working config please let us know, thanks

drbaker wrote:Please take a look at this lab config. We are testing ERPS functionality before put it in production, but no resuts.

4 Netonix in ring topology, erps control seems to work fine, but vlans declared in vlan monitor field appears to be blocked for all switch ports, in all ERPS working modes. If somebody have a working config please let us know, thanks

mike99 and Eric are testing/developing this feature which is still being developed and classified as use at own risk.

Eric is on vacation for 10 days and mike99 has a day job so whenever he gets a chance.

I have test the feature and reported what seem a wrong behavior to Dave and Eric. I'm waiting for a new firmware to test.

I found a bug After the update I can not turn on a port ie enable it from OFF to 24 in the registered one but the switch does not power the port

Please post up screen grabs of these TABs

Status
Ports
VLANs

I'm on my second ws-6-mini at a site that had been stable for at least a year. I'm now seeing the switch just randomly stop passing traffic until it's power-cycled. It continues to power everything attached to it. Two things that changed are adding a radio (metrolinq 2.5-60-19) and upgrading from 1.4.8 to 1.4.9. I'm normally not someone that is an early adopter and prefer to let others find bugs, but I think I was here asking a question and just noticed 1.4.9 was out so I put it on two switches.

I know this is super broad and vague, but anyone else seeing this? I suspected hardware (hence the swap), but after a day and a half, another lockup. I'm going to downgrade to 1.4.8 and give it a few days. If that fixes it, anything I can provide?

Are there any plans in the future to carry logs across reboots?

sirhc wrote:Please post up screen grabs of these TABs

Status
Ports
VLANs

Hi, here's the picture you asked me

jg0007 wrote:I found a bug After the update I can not turn on a port ie enable it from OFF to 24 in the registered one but the switch does not power the port

You have red arrows pointing to port 2 and port 3 in your original post picture.

Port 2 has an X on it because it is disabled on the Ports TAB

sporkman wrote:I'm on my second ws-6-mini at a site that had been stable for at least a year. I'm now seeing the switch just randomly stop passing traffic until it's power-cycled. It continues to power everything attached to it. Two things that changed are adding a radio (metrolinq 2.5-60-19) and upgrading from 1.4.8 to 1.4.9. I'm normally not someone that is an early adopter and prefer to let others find bugs, but I think I was here asking a question and just noticed 1.4.9 was out so I put it on two switches.

I know this is super broad and vague, but anyone else seeing this? I suspected hardware (hence the swap), but after a day and a half, another lockup. I'm going to downgrade to 1.4.8 and give it a few days. If that fixes it, anything I can provide?

Are there any plans in the future to carry logs across reboots?

Tell me any device that keeps a log after reboot?
This is why we support a syslog server.
viewtopic.php?f=17&t=1497&p=11096&hilit=+log+reboot+syslog#p11096

I highly doubt the switch "locked" up but rather this is a Pause Frame Packet Lock. There are TONS of posts discussing this on this forums and UBNT Forum. This is not a bug on our end but rather how wireless devices handle Pause Frames.
viewtopic.php?f=17&t=671&start=110#p22252

Search and read post on the forum about Flow Control. You can try disabling Flow Control on all ports if the problem persists to determine if that is your issue.