v1.4.7rcX Bug Reports and Comments

[petecarlson]

When you tag D for a vlan on a port, it still lets you set another vlan on the same port to T but it still double tags it. It would be awesome if it didn't.

This way we could run management over the same port instead of having to run another cable.

You could also have a setup like Netonx -> wireless link -> any switch where you could manage the wireless link, switch, etc while still putting customer vlans inside a service vlan.

i.e port 6 D500, T5
So something with a VLAN 5 tag would ingress/egress through port 6 with out getting a second tag added/removed but anything else would get a second 500 tag added/removed.

This would make me very very happy. I'll drive up to PA just to buy Chris a beer if thats what it takes.

Short of that, I think the ability to set T on a port should be removed when you set a vlan on the port to D just like it is for Q.

[Eric Stern]

The switch core only allows you to set the tagging options per port (not per port/vlan), so there is nothing I can about this.

[petecarlson]

Makes sense but it was worth a shot. Can you remove the option to T a second vlan on a port that has D set on a vlan like you do with Q? Doesn't make sense to leave it as an option if it isn't doing anything.

[bradg]

Just upgraded a brand new WS-8-150-AC from 1.4.2 (out of the box) with a very basic config (basic IP and config info, 6 VLAN's) to 1.4.7rc6 with no joy. Config was working as expected on 1.4.2, upgrade went fine, after reboot I get the login screen, login, and main.html just reloads over and over with no displayable content. Will do some searching to see what it takes to downgrade - SSH CLI still works at least.

Update - I should have added that I set ports 3, 4, 5, 6 to 24V PoE, and on reboot after upgrade, port 5 had a red LED lit (left) and green (right). I did a firmware downgrade from the CLI, and on reboot, none of the PoE settings were preserved - although it appeared that everything else was still intact. I re-setup the ports for 24V PoE, finally switched my management VLAN, and all seems good now back on 1.4.6.

FYI

[sirhc]

Personally I would factory default it - thinking config files is possibly corrupt.
Upgrade to v1.4.7rc6 then manually set it back up

Hundreds of people are using b1.4.7rc6 with no issues including me.

[sirhc]

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
- 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

[IntL-Daniel]

I did play now with FlowControl option per port and I have found that on ports connected to AirFiber24 (1000 Mbps Full) when I select FC to "Generate" only then the port shows Flow Control Off at all (the same result like None option). If I do the same on ports connectet to RocketM5 (100 Mbit Full) then it works correctly. I am still on 1.4.6 but not sure if this is an issue or not and if so, then is this an issue of AirFiber or Netonix?

[sirhc]

There is NO KNOWN ISSUE with Netonix with Flow Control.

I did not ask you to play with [Obey] or [Generate] or [Obey+Generate], I simply asked you to try Disabling Flow Control on all ports and see what happens.

Not all devices deal with all possible options of Flow Control Options and only work with ON or OFF.

There are KNOWN Bugs with Flow Control on UBNT devices which has been discussed many times on BOTH forums:
viewtopic.php?f=17&t=2375&p=17220&hilit=+Flow+Control#p17220

I have also asked for Screen Grabs of the Port Status on each port so I can examine the Stats and get a better idea of your issue.

Since there are now over 30,000 WISP Switches out there sold over the past 3 years and no one is having this issue I would assume it is something with your setup /environment?

I am trying to help but I need the information I asked for.

Let the switch run awhile and generate stats then post the info I need please.

[IntL-Daniel]

Chris I did not write that there is an issue with Netonix...I am not sure. I have just found suspicious behaviour of "Generate" option only. As I wrote above the symbols of flow control on ports connected to AirFiber24 in Nenonix main page is like this:
option selected to Both - two arrows
option selected to Obey - one arrow
option selected to Generate - no arrows
option selected to None - no arrows

I believe you have some AF24 on your switch so you could try as well. I do no know if this is correct or not...you have to decide :-)

BTW there is an update from UBNT side here https://community.ubnt.com/t5/airFiber-Beta/Updated-When-AF-Slave-goes-offline-Master-side-router-locks-up/m-p/1817562/highlight/true#M4930 if you care.

[sirhc]

Chris I did not write that there is an issue with Netonix...I am not sure. I have just found suspicious behaviour of "Generate" option only. As I wrote above the symbols of flow control on ports connected to AirFiber24 in Nenonix main page is like this:
option selected to Both - two arrows
option selected to Obey - one arrow
option selected to Generate - no arrows
option selected to None - no arrows

I believe you have some AF24 on your switch so you could try as well. I do no know if this is correct or not...you have to decide :-)

BTW there is an update from UBNT side here https://community.ubnt.com/t5/airFiber-Beta/Updated-When-AF-Slave-goes-offline-Master-side-router-locks-up/m-p/1817562/highlight/true#M4930 if you care.

I will experiment with this some evening with my AF24 radios in service as you suggest.
I will also experiment in the same manner between two Netonix switches and between Netonix and another Brand like Cisco to see if it works as intended.
Will let you know what I find but might be a couple days.