v1.4.0rc19 - rc25 Bug Reports and Comments

[sirhc]

I now have rc22 running on many various switches, ntp seems to take over an hour to update, whereas earlier versions time was correct as it came back up. Discovery used to show many devices Ubnt and Netonix on same vlan, now only seem to see netonix on lldp connected directly to its ports or via radio link.

The Discovery was just fixed in rc19 to actually be able to see all devices on all ports and VLANs. However it does not detect uniFi and airCAM stuff yet, next release.

If a device is set to be discovered via multiple protocols like the Netonix switch can respond on UDP, CDP, and LLDP if enabled to do so the switch will only report the FIRST one it sees. So if it see the Netonix Switch on LLDP first it will not show it on UDP or CDP.

We chose to do this to prevent the list from getting too large and showing the same devices on multiple discovery protocols.

Maybe we could say a device was discovered and on which protocols?

CLICK IMAGE TO VIEW FULL SIZE

[sirhc]

v1.4.0rc25 is released.

This version has Pause Frame Storm Protection which some people are experiencing with AF radios. Ubiquiti has identified the bug and plans to release a fix as soon as possible.

If the switch detects a Pause Frame storm on a port it will automatically disable Flow Control on that port and send an SMTP alert if you have SMTP setup properly in the switch. This will prevent the switch from appearing to lock up because of a never ending storm of Pause Frames.

The Pause Frame Storm can occur of the AF modulates down due to interference or rain fade and the capacity of the link becomes less then the amount of traffic you are trying to send over it. You can chose to disable this feature on the Device/Configuration Tab

The other option is to simply DISABLE Flow Control on the AF radio or on the switch port powering the AF radio.

It also allows you to configure Flow Control to Obey/Generate/Both on a per port basis on the Ports Tab.

To download the firmware click HERE

[Banana Jack]

There's an issue in 1.3.9 where if you change the switch name, the new name isn't picked up by airControl (i.e. the Netonix Ubiquiti Discovery I guess) until the WISP Switch is rebooted. It's just a niggle but it would be great if this were to be fixed in 1.4 as it would save a one-off short period of corrective downtime whenever we reconfigure the device name!

Thanks
Glenn

[sirhc]

There's an issue in 1.3.9 where if you change the switch name, the new name isn't picked up by airControl (i.e. the Netonix Ubiquiti Discovery I guess) until the WISP Switch is rebooted. It's just a niggle but it would be great if this were to be fixed in 1.4 as it would save a one-off short period of corrective downtime whenever we reconfigure the device name!

It has already been fixed in v1.4.0rcXX

[ryanm]

WS-6-Mini
upgraded to 1.4.0rc25

I tried enabling Discovery (it was not enabled previously to the upgrade).
The Discovery tool just gives me this: "Enable discovery in the device configuration."

I tried selecting a single discovery method (UBNT) as well as rebooting the switch.

[sirhc]

WS-6-Mini
upgraded to 1.4.0rc25

I tried enabling Discovery (it was not enabled previously to the upgrade).
The Discovery tool just gives me this: "Enable discovery in the device configuration."

I tried selecting a single discovery method (UBNT) as well as rebooting the switch.

The current version does not detect airCAMs and mFi but the next release will.

CLICK IMAGE TO VIEW FULL SIZE

[ryanm]

WS-6-Mini
upgraded to 1.4.0rc25

I tried enabling Discovery (it was not enabled previously to the upgrade).
The Discovery tool just gives me this: "Enable discovery in the device configuration."

I tried selecting a single discovery method (UBNT) as well as rebooting the switch.

The current version does not detect airCAMs and mFi but the next release will.

CLICK IMAGE TO VIEW FULL SIZE

avatar.jpg

Well, I sure missed that one. Thanks!