v1.2.0 FINAL bug reports and comments

[sirhc]

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

Version 1.2.0 FINAL is the same as v1.2.0rc12

FIXES

- Fixed scrolling on status page
- Fixed DHCP when changing the management VLAN ID
- Fixed SNMP stats for new models
- Fixed stats for new models in CLI
- Fix to ensure flashing 48VH PoE LED remains on during reboot
- Fixed problem with SFP ports not showing correct STP state on 12 port models

- Fixed problem configuring STP Priority
- Fixed MAC table sometimes showing filtered entries

- Fixed saving config in human readable format when configuring with CLI

- Fixed fan thresholds
- Fixed CLI configuration allowing Untagged port on multiple VLANs
- Fixed conflict between STP and loop protection

ENHANCEMENTS
- Added fallback to static IP configuration if DHCP fails

- Added DHCP Snooping
- Added Ubiquiti Discovery
- Added Cisco Discovery
- Added TFTP auto backup for config
- Added buttons to reorder VLANs
- Added support for WS-6-MINI, WS-8-250-AC and WS-8-250-DC
- Added Power tab for DC models
- Added current ratings to PoE settings in UI
- Added CLI command to show vlans
- Added CLI command to change ID of VLANs
- Added ability to use port range when configuring VLANs
- Added showing IP address of management VLAN to "show vlan" CLI command
- Added tarpit functionality to SSH server

- Added paging to "show config" CLI command


KNOWN ISSUES
- Ubiquiti Discovery Protocol is still a little flaky

[JustJoe]

On a WS-8-250-AC-white, did the easy one, upgraded from v1.2.0rc12 to v1.2.0 Final. All is well.

Will try a second switch tomorrow taking it from v1.1.0 to v1.2.0 .

[JustJoe]

On a WS-8-250-AC-white #2, upgraded from v1.1.0 to v1.2.0 Final. All is well.

[WisTech]

Non special-edition 8 port to 1.2.0 final this morning, no problem. Deployed it successfully powering a 5X, and 5 other radios.

[sirhc]

On a WS-8-250-AC-white #2, upgraded from v1.1.0 to v1.2.0 Final. All is well.

Did you tell it to reboot 1 more time after upgrade as instructed?

[JustJoe]

On a WS-8-250-AC-white #2, upgraded from v1.1.0 to v1.2.0 Final. All is well.

Did you tell it to reboot 1 more time after upgrade as instructed?

First after upgrade, tested simple management connectivity over a couple of different ports and connectivity through the switch to a couple of other radios. Then rebooted. Then set to factory defaults. Then power cycled. Then manually loaded a simple new config. No glitches at all. :)

The only strangeness I saw at all was v1.1.8 to 1.2.0rc12 on WS-8-250-AC-white #1 back here:

viewtopic.php?f=17&t=674&start=10

That after I reported the Discovery flakiness and was trying ssh access. Since the low level factory reset, it has been solid. :)

[sbyrd]

Upgraded to 1.2.0 today and I can still do an SNMP walk using any community string. Not sure if this is an issue with the Switch or my SNMP monitoring tool (Mikrotik The Dude), but I do know my other devices in the dude fail SNMP walk if the wrong community string is used.

[Eric Stern]

Upgraded to 1.2.0 today and I can still do an SNMP walk using any community string. Not sure if this is an issue with the Switch or my SNMP monitoring tool (Mikrotik The Dude), but I do know my other devices in the dude fail SNMP walk if the wrong community string is used.

The SNMP daemon doesn't support authentication when using SNMPv1.

1.2.1 will have SNMPv1 disabled so this won't be an issue.

[yoder]

Updated a WS-12-250A (the one I got in the forum contest!) this morning from 1.1.0rc18 and all is good. This is the first time I restarted it since I put in in service almost 4 months ago. As far as I could tell I didn't miss a ping on the update and the subsequent (2nd) reboot. Not sure how you do that but it does make updates a lot easier to do.

This switch is in a location with good power and good UPS + batteries, so we never had many problems with power. I just ordered some MINIs and I will be putting these in some more difficult locations as far and the power grid is concerned. I am hopeful your power supply is better than the standard POEs we have now. I am also exited to be able to have one battery bank for 48V and 24V.

Keith

[SBB-DJ]

I have upgraded a WS-24-400A to 1.2.0 and I am having some problems. I was hoping that someone on the forums might be able to help me. The upgrade process itself went fine, and we did the required reboot after the upgrade. However since the upgrade to 1.2.0 two of our switches have been acting weird.

The first problem is that the switch seems to soft reset itself every few hours. Originally I thought maybe the hardware itself was the issue so I swapped it with a new one that had been upgraded to 1.2.0 and I am now seeing the same problem. Before I tried to downgrade (if I can?) I wanted to give someone from Netonix an opportunity to look at the problem since no one else has reported the issue. When this reset condition happens power is not lost to any devices being POE powered from the switch but it does drop ethernet link and stops switching for a few seconds.

Along with that same problem I am also having a reporting issue where the temperature, power and cooling fan speed are not report either at all, or properly in the UI. I have confirmed that even though the fans in the web page say they are spinning at 10,000+ RPM, they are not actually spinning at all in real life.





Any help or suggestions would be greatly appreciated. I will most likely also open a support ticket with Netonix as well to see if they have any suggestions on the issue.