Netonix Forums

Please post comments and report bugs with v1.4.4 in this thread

v1.4.4 wrote:FIXED
- Fixed shell exit
- Fixed missing field on scheduled port bounces created in CLI which would cause a config file to become corrupt - URGENT
- Fixed occasional invalid statistics reported to the UI
- Fixed clearing of stats on SFP ports
- Removed disabling poe if port has link while turning on power
- Changed SNMP ifName/ifDescr/ifAlias
- Fixed console login when using passwords with special characters
- Fix power budget on WS-8-150-DC
- Fix CDP and LLDP on SFP ports on 12 port models
- Fixed SMTP so it send emails in a background process, could have caused UI to become unresponsive if there was an issue with server
- Fixed reboot command to properly do warm boot
- New fix for IGMP snooping on VLANs
- Fixed incorrect port number on LACP notification
- Fixed color of 100M links on SFP ports

ENHANCEMENTS
- Reduce resource usage of ubiquiti discovery
- Increased Pause Frame Storm Threshold from 10K unsolicited Pause Frames per second for 5 seconds to 15K unsolicited Pause Frames per second for 10 seconds
- Added pause frame count logging when Pause Frame Storm Protection trips
- Add graphic to firmware update
- Added BRIDGE-MIB to SNMP
- Added port name to email
- Added configurable email alerts so you can select which messages are sent via SMTP
- Added ifType to SNMP
- Moved email alerts config to a dialog
- Unexpected link change message now indicates speed
- Added button to flush mac table
- Added America/Creston timezone
- Added QOS Tab
- Added Serial Proxy for SCADA devices

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

Released 9/5/2016

OK sorry about v1.4.3 having SNMP broken so here is v1.4.4

Updated some switches that are about 2,000 miles away from me with 1.4.4. It seems like as soon as I updated them they've disappeared from my Ubiquiti scan. I can't login to them. They seem to show up and disappear on and off. Yet the cameras plugged into them are working. I did notice information on the log of one of them that I got in and was able to roll back to 1.4.3rc7. It said detected loop from port 1 to port 1 and disabled port 1.

alex.frisbie wrote:Updated some switches that are about 2,000 miles away from me with 1.4.4. It seems like as soon as I updated them they've disappeared from my Ubiquiti scan. I can't login to them. They seem to show up and disappear on and off. Yet the cameras plugged into them are working. I did notice information on the log of one of them that I got in and was able to roll back to 1.4.3rc7. It said detected loop from port 1 to port 1 and disabled port 1.

I am sorry for your issue Alex but Loop detection can detect a loop on a port to itself, this might not be a bug, we have to investigate.

How loop Detection works is it sends out a BPDU packet on every port every second. If that BPDU packet gets back to any port on the switch that sent it even the port it was sent from Loop Detection will disable the sending port. So it is possible to get a Loop Detection from Port 1 to Port 1.

Sometimes if you are running RSTP and Loop Detection together when a switch reboots and RSTP paths change a stray packet might get back and trigger a false loop detection. If you run a large flat segment you might only want to use 1 or the other method.

This can happen if there is a loop further out on your network on a single port or possibly a leaky VLAN.

You could Disable Loop Protection on the Device/Configuration Tab.

I do not believe there were any changes to how Loop Protection Works for several versions and definitely not between v1.4.3rc7 and v1.4.4 but we will investigate it today.

As far as installing a new version of firmware on switches 2,000 miles away I would not suggest doing that when first testing a new firmware release. Whereas I appreciate your confidence in us there really is no way to test 100% that every feature will work for every persons network topology and other equipment used in their network which is why every equipment manufacturer I know of has to continuously fix bugs as found.

When I roll out new firmware at my WISP I upgrade some easy to access switches first then slowing roll out to easiest to access first until I feel comfortable then push to the masses which is why we have the warning below where you download firmware.

As always be careful to roll out new versions, upgrade switches that are easily accessible until you verify that the new firmware works with your network design and desired feature set. We try to test as much as possible but it is impossible to test every possible network configuration.

I want to help here Alex but I need more information.

Were you able to roll out v1.4.4 on other switches without issue and if so what might be different with this installation?

Are you running both RSTP and Loop Protection?

You "should" be able to disable Loop Protection and then upgrade to v1.4.4 if it was Loop Protection that was Disabling the Port 1

The question is why did v1.4.4 give you grief and as you said v1.4.3rc7 did not, this is going to have to be investigated and determine if we are at fault and if so fix it for you.

@Alex

I have been testing Loop Protection here with daisy chained Netonix Switches and do not see any issue.

Could you post up the Config Tabs of the switch that was giving you the issue and maybe explain the network topography around that switch.

Is it part of a larger flat Layer 2 segment or routed?

Do you have a lot of VLANs? (a screen shot of your VLAN tab would help)

sirhc wrote:@Alex

I have been testing Loop Protection here with daisy chained Netonix Switches and do not see any issue.

Could you post up the Config Tabs of the switch that was giving you the issue and maybe explain the network topography around that switch.

Is it part of a larger flat Layer 2 segment or routed?

Do you have a lot of VLANs? (a screen shot of your VLAN tab would help)

Chris,

We don't really use anything on the Switches at all besides PoE, haha. It looks like in this scenario, loop protection was enabled for some reason on certain switches. Normally, we don't use loop protection. However, with that being said, loop protection on these switches was enabled and they were running 1.4.2rc4, I believe. I upgraded them all to 1.4.4 and it seemed they started to throw fits. All of the loop protection detections were on ports running Ubiquiti Antennas that were setup on a PtMP network. The only thing plugged into the majority of the switches that gave me problems is one camera and one Ubiquiti antenna. I ended up rolling back to 1.3.7rc6 on 6 of them at this location.. the other 3 I haven't been able to get into yet. It seems they're still passing data, as I have camera footage at the locations the switches are at, but I can't find them in a Ubiquiti scan nor can I login to them.

Also, out of curiosity, did you guys ever find a problem with Flow Control? I've been disabling flow control on switches we've been putting out. There definitely was a problem on the initial 1.4.2. After I disabled Flow Control everything was fine on the switch I had a problem with prior. Once again, that switch was only sending camera data to a Ubiquiti antenna back to a centralized location.

P.S. There's no VLANs setup there at all.

This is a configuration from one of the switches that I rolled back to 1.3.7rc6.

upgraded from 1.4.3 to 1.4.4 and now I have some:

1: "undefined" issues under Flow Control options. (not sure if this is expected)
2: Missing options under Device -> Configuration. no ssh, no https, no syslog, no storm control, no snmp server, no credentials

What version of IE are you using?

If you use Chrome what happens?

I am running v1.4.4 and I do not have this issue?

IE version: 11.0.9600.18426
Update version: 11.0.34

alex.frisbie wrote:
Also, out of curiosity, did you guys ever find a problem with Flow Control? I've been disabling flow control on switches we've been putting out. There definitely was a problem on the initial 1.4.2. After I disabled Flow Control everything was fine on the switch I had a problem with prior. Once again, that switch was only sending camera data to a Ubiquiti antenna back to a centralized location.

There is nothing wrong with our Flow Control no but UBNT acknowledge a Flow Control iss with AF radios. SOme people have reported the Flow Control issue on airMAX AC radios.

Also it has been reported by one person that there "could" be a Flow Control issue with epmp 2000 radios, similar but not quite the same as AF radio but was not determined for sure if it was epmp radio or possibly MT router or a combination of the 2 or even the 3.

There is a new feature in v1.4.2 and above which is Pause Frame Storm Protection which will detect a storm and automatically Disable FC on that port. This feature protects against the UBNT issue but not known if it will protect against epmp 2000 issue yet.

Alex your going to have to do some detective work on your end and give us something to work on. Or you could simply disable Loop Protection but you either need to narrow it down for something for us to fix or just disable Loop Protection as you really do not want to be running such old code.