v1.4.7rcX Bug Reports and Comments

[sirhc]

Please post comments and report bugs for v1.4.7rcX in this thread

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
- Fixed switch rebooting if multiple ports lose link too quickly - RC14
- Fixed multiple ports not turning off at the same time when they have the same shutdown voltage - RC14
- Fixed unexpected link change speed message - RC14
- Fixed port selection Tabs - RC14
- Fixed slight glitch in Input Current graph - RC16
- Fixed STP tab on 12 port models - RC18
- Fixes for WS-26-500-DC - RC21-RC22
- Fixed bulk editing Flow Control on Ports tab - RC22
- Fixed updating Watchdog description if port name is changed - RC22
- Fixed bulk editing on Power tab - RC22
- 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 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
- Added LLDP-MIB and CISCO-CDP-MIB to SNMP - RC 14
- Added option to change MAC aging time - RC14
- Added "Disable Power" action to watchdog - RC16

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
RC14 Released 3/7/2017
RC16 Released 4/4/2017
RC18 Released 4/7/2017
RC21 Released 5/2/2017
RC22 Released 5/3/2017

[mayheart]

Download link is busted.

[sirhc]

Download link is busted.

FIXED

[ict-plus]

We have the following error message on a Netonix switch (WS-6-MINI):

---
Jan 9 14:30:59 Port: link state changed to 'up' (1G) on port 3
Jan 9 14:44:14 switch[1330]: got excessive pause frames on port 2 (15105), count = 1
Jan 9 14:44:15 switch[1330]: got excessive pause frames on port 2 (15134), count = 2
Jan 9 14:44:16 switch[1330]: got excessive pause frames on port 2 (15123), count = 3
Jan 9 14:44:18 switch[1330]: got excessive pause frames on port 2 (15042), count = 1
Jan 9 14:44:19 switch[1330]: got excessive pause frames on port 2 (15121), count = 2
Jan 9 14:44:20 switch[1330]: got excessive pause frames on port 2 (15125), count = 3
Jan 9 14:44:21 switch[1330]: got excessive pause frames on port 2 (15131), count = 4
Jan 9 14:44:22 switch[1330]: got excessive pause frames on port 2 (15129), count = 5
Jan 9 14:44:23 switch[1330]: got excessive pause frames on port 2 (15113), count = 6
Jan 9 14:44:24 switch[1330]: got excessive pause frames on port 2 (15107), count = 7
Jan 9 14:44:25 switch[1330]: got excessive pause frames on port 2 (15110), count = 8
Jan 9 14:44:26 switch[1330]: got excessive pause frames on port 2 (15121), count = 9
Jan 9 14:50:01 switch[1330]: got excessive pause frames on port 2 (15051), count = 1
Jan 9 14:50:12 switch[1330]: got excessive pause frames on port 2 (15036), count = 1
Jan 9 14:50:13 switch[1330]: got excessive pause frames on port 2 (15055), count = 2
Jan 9 14:50:14 switch[1330]: got excessive pause frames on port 2 (15058), count = 3
Jan 9 14:50:15 switch[1330]: got excessive pause frames on port 2 (15057), count = 4
Jan 9 14:50:16 switch[1330]: got excessive pause frames on port 2 (15070), count = 5
Jan 9 14:50:17 switch[1330]: got excessive pause frames on port 2 (15065), count = 6
Jan 9 14:50:19 switch[1330]: got excessive pause frames on port 2 (15033), count = 1
Jan 9 14:50:20 switch[1330]: got excessive pause frames on port 2 (15044), count = 2
Jan 9 14:50:21 switch[1330]: got excessive pause frames on port 2 (15053), count = 3
Jan 9 14:50:22 switch[1330]: got excessive pause frames on port 2 (15045), count = 4
Jan 9 14:50:23 switch[1330]: got excessive pause frames on port 2 (15031), count = 5
Jan 9 14:50:24 switch[1330]: got excessive pause frames on port 2 (15038), count = 6
Jan 9 14:50:55 Port: link state changed to 'down' on port 3
---

The interesting thing is that on Port 2 no cable is connected. The device behind port 3 is also a Netonix switch (WS-6-MINI), which is connected over a 63m long Ethernet link, which goes down after 15 minutes of operation and does not come back.
The same problem already occurred with the release 1.4.6. The following has already been tested:
- The cable has been tested with a Cable Diagnostic Device and is ok
- The connected switch has already been exchanged
Thanks for any Help!

[Eric Stern]

Those log messages are actually referring to port 3, I forgot to add 1 to the port number (internally ports are numbered starting at 0).

[ict-plus]

And where do the pause frames come from?
Behind the Port is a Netonix switch, at which no devices are connected!
My problem is, that the port is shut down coming up for some seconds or minutes and shut down again.






Jan 14 15:37:44 Port: link state changed to 'up' (1G) on port 2
Jan 14 15:37:50 Port: link state changed to 'down' on port 2
Jan 14 15:37:54 Port: link state changed to 'up' (1G) on port 2
Jan 14 15:42:17 Port: link state changed to 'down' on port 2
Jan 14 20:20:38 Port: link state changed to 'up' (1G) on port 2
Jan 14 20:20:44 Port: link state changed to 'down' on port 2
Jan 14 20:20:47 Port: link state changed to 'up' (1G) on port 2
Jan 14 20:21:17 Port: link state changed to 'down' on port 2
Jan 15 08:41:27 Port: link state changed to 'up' (1G) on port 2
Jan 15 08:41:31 Port: link state changed to 'down' on port 2
Jan 15 08:41:33 Port: link state changed to 'up' (1G) on port 2
Jan 15 08:42:16 Port: link state changed to 'down' on port 2
Jan 15 14:05:32 Port: link state changed to 'up' (1G) on port 2
Jan 15 14:05:39 Port: link state changed to 'down' on port 2
Jan 15 14:05:41 Port: link state changed to 'up' (1G) on port 2
Jan 15 14:06:12 Port: link state changed to 'down' on port 2

[Eric Stern]

You can try disabling STP on that port.

[sirhc]

And where do the pause frames come from?
Behind the Port is a Netonix switch, at which no devices are connected!
My problem is, that the port is shut down coming up for some seconds or minutes and shut down again.

Jan 14 15:37:44 Port: link state changed to 'up' (1G) on port 2
Jan 14 15:37:50 Port: link state changed to 'down' on port 2
Jan 14 15:37:54 Port: link state changed to 'up' (1G) on port 2
Jan 14 15:42:17 Port: link state changed to 'down' on port 2
Jan 14 20:20:38 Port: link state changed to 'up' (1G) on port 2
Jan 14 20:20:44 Port: link state changed to 'down' on port 2
Jan 14 20:20:47 Port: link state changed to 'up' (1G) on port 2
Jan 14 20:21:17 Port: link state changed to 'down' on port 2
Jan 15 08:41:27 Port: link state changed to 'up' (1G) on port 2
Jan 15 08:41:31 Port: link state changed to 'down' on port 2
Jan 15 08:41:33 Port: link state changed to 'up' (1G) on port 2
Jan 15 08:42:16 Port: link state changed to 'down' on port 2
Jan 15 14:05:32 Port: link state changed to 'up' (1G) on port 2
Jan 15 14:05:39 Port: link state changed to 'down' on port 2
Jan 15 14:05:41 Port: link state changed to 'up' (1G) on port 2
Jan 15 14:06:12 Port: link state changed to 'down' on port 2

How Pause Frames received on one port can affect another port.

Say you have Port 1 feed by your router and ports 2 goes to a backhaul to another tower and ports 3 through 6 feed local APs:

Now say a user with a poor wireless connection on an AP on port 4 requests something from the internet. That data will come flying into the switch as fast as it can get it from the router on port 1 but when the packets try to go out Port 4 and hits the SLOW / POOR wireless connection the packets get backed up as the radio on Port 4 is sending Tx Pause frames to the switch Port 4 so it tries to hold the packets in its buffers but soon the buffers fill up. Since switches use shared buffer memory for all ports and the switch is now out of memory so these packets can not move out port 4 and since the switch has no more buffers the switch will start sending Tx Pause Frames out all other ports including Port 1 which is the source for all other APs creating a packet lock as not all ports are sending out Tx Pause Frames.

Now some radios are known to have Flow Control bugs like UBNT AirFIBER and airMAX AC radios. If you are running up to date firmware on the WISP Switch it should detect these Pause Frames Storms and disable Flow Control on the offending port receiving the Pause Frame Storm. Make sure you do NOT disable Pause Frame Storm protection on the Device/Configuration Tab or disable FLow Control on any port connected to AF or AC radios.

As far as your port 2 going up and down make sure you are not hard coding port speed to 1G, leave it set to Auto and set to Auto on the Device otherwise if there is any blip at all on port 2 and it can not maintain 1G communications it will drop and then renegotiate which is what I see above in your logs. Another cause for a port going up and down is a bad wire or crimp and you are getting intermittent connection on either pair 1 or pair 2.

[cwachs]

So we are no longer disabling flow control on ports feeding AF radios with 1.4.7?

[sirhc]

So we are no longer disabling flow control on ports feeding AF radios with 1.4.7?

We did not have a Flow Control Bug UBNT did.

Some users still report a Pause Frame Storm issue with UBNT AF and airMAX AC radios.

1.4.7rc4 will protect you from a Pause Frame Storm if it occurs if Pause Frame Storm Protection is enabled.

READ: viewtopic.php?f=17&t=2375&start=20#p17034