v1.3.9 FINAL bug reports and comments

[sirhc]

Please post comments and reports bugs with v1.3.9 FINAL in this thread

This version fixed a LOT of issues (see below) so we strongly suggested upgrading your switches.

If you try this version and still have issues try the latest RC version as this version is FINAL and no development is being done in it.

FIXED
- Fixed clear log
- Fixed SNMP using 100% CPU
- Fixed config revert not working
- Fixed per-port graphs that were broken if switch was up less than 1 hour
- Fixed condition where DC2DC power supply failed to wake up switch from hibernation mode
- Fixed where unresolvable hostname could hang syslog server
- Fixed DC power supply voltage range
- Fixed UBNT Discovery name
- Fixed Watchdog, now disabled if port is disabled
- Fixed so now retains log if log daemon is restarted
- Fixed so CLI no longer saves config unless something was changed
- Fixed Log file formatting
- Fixed UBNT Discovery - FINALLY
- Fixed Linux log
- Fixed Loop protection log entry refers to wrong port number
- Fixed Broadcast storm when using LACP and RSTP
- Fixed Unable to change RSTP path cost for LAGs
- Fixed MAC table eating up CPU time when you have hundreds and hundreds of MAC entries.
- Fixed SNMP, Changed from mini-snmpd to net-snmp, a more common and well tested snmp daemon.

ENHANCEMENTS
- Added enable/disable VLAN to CLI
- Added "clear log" CLI command
- Added LLDP Discovery
- Added changing of Safe Mode Timer and ability to disable Safe Mode
- Added ability to reset counters per port instead of all
- Added Enhancement for MAC table
- Added clear stats command to CLI
- Added HTTP watchdog - Customer can now create a watchdog event based on an HTTP URL
- Allow up to 253 character RADIUS secret - USER REQUESTED
- Delay I2C init in SMART DC power supply firmware to fix random RJ45 POE light on a cold boot - COSMETIC FIX ONLY

KNOWN ISSUES
- SNMP reported up time is incorrect
Released 1/30/2016

[menacers]

after applying the new firmware i have a message:

Jan 30 12:58:10 switch[1488]: Detected warm boot
Jan 30 13:00:40 switch[1433]: Warning: expected 2 fans but found 1
Jan 30 13:02:11 switch[1433]: Fan 2 is failing (0 RPM, cooling level 255, board temp 54 C)

the system appears be running warm, 80C. Although I'm not suggesting the firmware broke the fan, in fact I remember the switch being noisy. I may have never noticed the fan was broken but I see now because there is a red exclamation on devices tab in this new firmware.

Let me know if there is anything I should do to troubleshoot. If the fan is in fact broken, how do I proceed with RMA? This a rev C board, 12 port switch AC.

Thanks

[sirhc]

after applying the new firmware i have a message:

Jan 30 12:58:10 switch[1488]: Detected warm boot
Jan 30 13:00:40 switch[1433]: Warning: expected 2 fans but found 1
Jan 30 13:02:11 switch[1433]: Fan 2 is failing (0 RPM, cooling level 255, board temp 54 C)

the system appears be running warm, 80C. Although I'm not suggesting the firmware broke the fan, in fact I remember the switch being noisy. I may have never noticed the fan was broken but I see now because there is a red exclamation on devices tab in this new firmware.

Let me know if there is anything I should do to troubleshoot. If the fan is in fact broken, how do I proceed with RMA? This a rev C board, 12 port switch AC.

Thanks

Yes this newer firmware now makes things very apparent that are not correct which was the idea.

I am "guessing" this is a WS-12-250A or B model as you failed to report the model?

If you observe the fan is it spinning?

If the fan is making noise sometimes the 2 screws that hold it in are too tight and warp the fan chassis. I have seen fans that hard held from moving because the user cranked them as tight as they could and warped the plastic fan chassis so it would not turn.

Try loosening each one a quarter turn and see if the noise stops.

[adairw]

I've upgraded two 8 ports at home. will slowly roll out to other switches in the network over the next few days and report any trouble.

[adairw]

I've upgraded about 30 switches to 1.3.9 with no issues.
I didn't realize how much 1.2.0, 1.3.3 and 1.3.8 was out there.

[sbyrd]

Not sure if a bug or if I am reading the wrong OID, but OID 1.3.6.1.2.1.1.3.0 reads as system uptime, but the value on my recently rebooted switch reads 429d 04:30:04.8. I have not even had the switch for that long.

[sirhc]

Not sure if a bug or if I am reading the wrong OID, but OID 1.3.6.1.2.1.1.3.0 reads as system uptime, but the value on my recently rebooted switch reads 429d 04:30:04.8. I have not even had the switch for that long.

I am not see that on my units. Maybe it is a weird glitch, please reboot the unit again and see if it goes away?

[sbyrd]

I will give it a try off hours later tonight. So far I have 3 WS-Minis on 1.39 or 1.39rc15 and they all report uptimes of 429 days. I have another WS-MIni on 1.33 with a SNMP uptime of 117 days and GUI uptime of 118 days. My WS-12s and WS-8 (running much older FW) are reporting uptimes correctly.

I will work on upgrading all my switches to 1.39 (including my WS-12s and WS-8) and report back.

If it matters I am using The Dude for SNMP and pulled these values using SNMP walk.

[sirhc]

I will give it a try off hours later tonight. So far I have 3 WS-Minis on 1.39 or 1.39rc15 and they all report uptimes of 429 days. I have another WS-MIni on 1.33 with a SNMP uptime of 117 days and GUI uptime of 118 days. My WS-12s and WS-8 (running much older FW) are reporting uptimes correctly.

I will work on upgrading all my switches to 1.39 (including my WS-12s and WS-8) and report back.

If it matters I am using The Dude for SNMP and pulled these values using SNMP walk.

OH, My bad I did not read your post correctly, I thought you were referring to the UI report of uptime.

Yes upgrade them to v1.3.9 and report back as there were MAJOR changes to SNMP in v1.3.9

There may be a bug on the SNMP reported up time so yes please upgrade and review the release notes.

Also note that you now must use our new MIB file located HERE

[sirhc]

Also now v1.3.9 will bring switch damage more into focus.

Our switches are built pretty tough and will continue to function even when damaged but unless people paid close attention to things like voltages, current, temperatures and such may be un-aware that their switch took damage such as surge or ground potential shift damage in the past.

Now any thing out of range will be very apparent with bold indicators that something is wrong.

Normally current sensor damage would go un-noticed and sometimes current sensor damage can cause other telemetry to be off as they share the same I2C bus.

Biggest reason for damage to these sensors if from poor grounding systems. Many people do not properly bond tower grounding systems to electrical service grounds and then the bond to these 2 different ground potentials is the Ethernet cable.

People really should review these 2 posts on proper ground practices:
viewtopic.php?f=30&t=188
viewtopic.php?f=30&t=1429

Blown current sensors are not covered under warranty so people really should start beefing up their grounding systems.

We are experimenting with a new design concept to hopefully better protect the current sensors on newer models but this is only masking a weak grounding system.