v1.4.7rcX Bug Reports and Comments

[Eric Stern]

v1.4.7rc6 and newer appear to break the trunk vlan checkbox (Access List) feature. Tested working with 1.4.6 1.4.7rc4. Not working in 1.4.7rc6, 1.4.7rc8.

CP

This will be fixed in 1.4.7rc9, which should be available soon.

[sirhc]

- Fixed QinQ - RC9
- Fixed VLAN trunking - RC9
- Allow QinQ and Double Tagging to be used with Trunk ports - RC9

NOTE: MSTP is still being tested so use MSTP at your own risk.

FIXED/CHANGED
- Fixed temp sensors showing crazy values in very cold environments - RC3
- Fixed getting "unexpected link change" messages due to port bounce, watchdogs, etc - RC3
- Fixed port bounce being 1 hour off after daylight savings time changes - RC3
- Fixed VLAN tab layout getting messed up when you delete a VLAN - RC3
- Fixed mac table refresh button causing entire page to reload - RC3
- Fixed problem with QinQ when using untagged VLANs - RC3
- Fixed fan control handling negative temperatures - RC4
- Fixed input voltage graph labels - RC4
- Fixed Apply/Save becoming active when looking at MSTP configuration even though nothing changed - RC6
- Fixed port number in log messages - RC6
- Fixed issue when importing config from a RevE board to a RevF with different POE port options. Affected WS-6 and WS-12 - RC6
- Fixed the support for WS-8-150-AC - RC7
- Fixed console login
- Fixed/Force powerdown/powerup limits on WS-8-150-DC to help prevent switch lock up when draining battery to 9V - RC8
- Fixed DC2DC-500 detection for WS-26-500-DC - RC8
- Fixed voltage range on dumb DC models - RC8
- Fixed QinQ - RC9
- Fixed VLAN trunking - RC9
- Allow QinQ and Double Tagging to be used with Trunk ports - RC9
- Changed UI layout on QOS tab - RC3
- Changed dumb DC models to temporarily disable POE when input voltage falls too low instead of disabling POE in the configuration - RC3
- Changed valid DC input voltage range to 9-72V in GUI for newer board revs - RC3
- Changed valid upper range for dc output voltage from 51V to 53V - RC3
- Changed input voltage graph to auto-scale - RC3
- Changed fan control to also use CPU and PHY temp - RC6
- Changed valid temp range on Status page meters - RC6

ENHANCEMENTS
- Added MSTP - RC3
- Automatically disable flow control on ports using QOS bandwidth limits to prevent packet locks - RC3
- Added restart timer to DC power supply to help in very cold environments with cold starts - RC3
- Added log message when time is set by NTP after boot is finished - RC3
- Added logging when STP selects new root port - RC3
- Added POE startup delay option on Power tab - RC3
- Added root path cost on STP tab - RC3
- Added portDuplex SNMP stat from CISCO-STACK-MIB - RC3
- Added ifAdminStatus to SNMP stats - RC3
- Added support for new WS-26 models - RC6
- Added Double Tagged to VLAN configuration - RC6

KNOWN ISSUES
- Some language templates need help - please contact us to help

RC3 Released 1/3/2017
RC4 Released 1/3/2017
RC6 Released 1/26/2017
RC7 Released 1/27/2017
RC8 Released 2/7/2017
RC9 Released 2/16/2017

[tma]

1) If the list of access subnets contains a subnet that matches the IP of the switch and the accessing PC, access is granted even if this subnet definition is disabled - as if the enable/disable option had no effect at all.

I just confirmed this one now. I'm looking at a switch that has several access subnets configured. These subnets are the source nets from several places where we manage our network from - so it doesn't really make sense to include a picture because I would have to "censor" all entries.

Only one subnet definition is set to "enabled", all other are disabled, and the one being enabled is NOT the one I'm currently using. I can access the switch GUI though as if the enabled/disabled option would have no effect at all.

[petecarlson]

What is the WS-26-500-DC and where can I get one? !!!

"- Fixed DC2DC-500 detection for WS-26-500-DC -
RC8"

[sirhc]

There are several new models coming out in Q2
24 copper 1G POE ports and 2 SFP 1G ports
(6) 48VH ports
(2) 24VH ports

WS-26-400-AC - Will replace WS-24-400A - MUCH SMALLER FORM FACTOR - 13.5" x 9.5" x 1.5"
WS-26-400-IDC - Will be a DC switch for NEGATIVE 48V sites like Telcos
WS-26-500-DC - Basically a bigger version of the WS-12-250-DC 9V - 72V DC in Smaller than (2) WS-12-250-DC and less than (2) WS-12-250-DC - 500 watts
WS-26-DC - Basically a bigger version of the WS-12-DC

[sirhc]

- Added IP Protocol to QoS rules - RC11
- Added CIDR notation in QoS Source IP rules - RC11
- Added option to log web and ssh logins - RC11
- Fixed Access Controls not honouring the Enable setting - RC11

NOTE: MSTP is still being tested so use MSTP at your own risk.

FIXED/CHANGED
- Fixed temp sensors showing crazy values in very cold environments - RC3
- Fixed getting "unexpected link change" messages due to port bounce, watchdogs, etc - RC3
- Fixed port bounce being 1 hour off after daylight savings time changes - RC3
- Fixed VLAN tab layout getting messed up when you delete a VLAN - RC3
- Fixed mac table refresh button causing entire page to reload - RC3
- Fixed problem with QinQ when using untagged VLANs - RC3
- Fixed fan control handling negative temperatures - RC4
- Fixed input voltage graph labels - RC4
- Fixed Apply/Save becoming active when looking at MSTP configuration even though nothing changed - RC6
- Fixed port number in log messages - RC6
- Fixed issue when importing config from a RevE board to a RevF with different POE port options. Affected WS-6 and WS-12 - RC6
- Fixed the support for WS-8-150-AC - RC7
- Fixed console login
- Fixed/Force powerdown/powerup limits on WS-8-150-DC to help prevent switch lock up when draining battery to 9V - RC8
- Fixed DC2DC-500 detection for WS-26-500-DC - RC8
- Fixed voltage range on dumb DC models - RC8
- Fixed QinQ - RC9
- Fixed VLAN trunking - RC9
- Fixed Access Controls not honouring the Enable setting - RC11
- Allow QinQ and Double Tagging to be used with Trunk ports - RC9
- Changed UI layout on QOS tab - RC3
- Changed dumb DC models to temporarily disable POE when input voltage falls too low instead of disabling POE in the configuration - RC3
- Changed valid DC input voltage range to 9-72V in GUI for newer board revs - RC3
- Changed valid upper range for dc output voltage from 51V to 53V - RC3
- Changed input voltage graph to auto-scale - RC3
- Changed fan control to also use CPU and PHY temp - RC6
- Changed valid temp range on Status page meters - RC6
- Changed the input voltage threshold where it forgets the configured Wake up voltage and defaults to 10V Wake up on WS-12-250-DC - RC10

ENHANCEMENTS
- Added MSTP - RC3
- Automatically disable flow control on ports using QOS bandwidth limits to prevent packet locks - RC3
- Added restart timer to DC power supply to help in very cold environments with cold starts - RC3
- Added log message when time is set by NTP after boot is finished - RC3
- Added logging when STP selects new root port - RC3
- Added POE startup delay option on Power tab - RC3
- Added root path cost on STP tab - RC3
- Added portDuplex SNMP stat from CISCO-STACK-MIB - RC3
- Added ifAdminStatus to SNMP stats - RC3
- Added support for new WS-26 models - RC6
- Added Double Tagged to VLAN configuration - RC6
- Added IP Protocol to QoS rules - RC11
- Added CIDR notation in QoS Source IP rules - RC11
- Added option to log web and ssh logins - RC11

KNOWN ISSUES
- Some language templates need help - please contact us to help

RC3 Released 1/3/2017
RC4 Released 1/3/2017
RC6 Released 1/26/2017
RC7 Released 1/27/2017
RC8 Released 2/7/2017
RC9 Released 2/16/2017
RC10 Released 2/20/2017
RC11 Released 2/22/2017

[IntL-Daniel]

I would like to report very strange thing...I have WS-12-250-AC on 1.4.7rc7. Today we have excessive flow control pause frames report in the log and the flow control was automaticaly disabled on AF24 port. It was typical situation where the AF24 link was broken (because of opposite side stop responding) and AF24 started to send unsolicited pauseframes. OK, we have to live with this.

BUT "exactly at the moment" when the switch detected pause frame storm and disabled flow control three devices on other Netonix ports were independently restarted at the same moment. These are 3 units powered by 48V POE. I believe that there was broken 48V power for a while at the moment of disabling FlowControl or during the pause frame storm? I have set ping watchdog for these ports but there was no report of any missend ping or power cycle in the log. So I am just trying to describe the situation where something strange and unexpected happend. Maybe it is hidden long time ongoing issue? Unfortunately I have no chance to simullate the sitaution again because it is our main switch of the wireless network.

[sirhc]

Well for one you should upgrade to v1.4.7rc10 but that is not the issue just poking you to stay updated.

I doubt the POE was interrupted. More than anything the Pause Frame Storm basically caused a packet lock in the switch which has been discussed many times on the forums.

Think of it as a vapor lock. Once Flow Control was disabled on the AF24 port by our protection routine it resets the Ethernet link on the port dumping all the packets held in memory and traffic resumes.

Basically switches uses SHARED memory for buffering so when the memory fills up from a Pause Frame Storm it can cause all ports to stop passing traffic.

Now if you have watchdogs setup to reboot radios this could be what happened as the radios would fail their ping watchdog and reboot or if a watchdog rule in the switch the switch reboots it.

I believe UBNT recently released a new version of firmware to finally fix the Pause Frame Storm Bug?

[IntL-Daniel]

Now if you have watchdogs setup to reboot radios this could be what happened as the radios would fail their ping watchdog and reboot or if a watchdog rule in the switch the switch reboots it.

I believe UBNT recently released a new version of firmware to finally fix the Pause Frame Storm Bug?

But I believe that if the restart was caused by watchdog then I would find some report in the Netonix log? But there were only messages of disconnected/connected lan cable on these three ports .

No there is not any fix UBNT for pause frame storms. They are still sending tons of pauseframes at the moment of their full buffer even when the link is down.

[sirhc]

If the radios rebooted there should be record in the switch log of the port going down and back up (twice), is there?

Did you log into the radios and confirm they rebooted? (up time)?

Do you have a watchdog set up in the radios themselves?

I have AF radios all over the place and I see the Flow Control turned OFF all the time and have never seen this behavior on any of my switches so my opinion is there is something else a foot here.