v1.5.0 Bug reports and Comments

[sirhc]

Please post bug reports and comments on v1.5.0 ONLY in this thread.

FIXED/CHANGED
- Fixed I2C service to deal with errors better to prevent reboots with WS-12-250-DC and WS-26-500-DC
- Fixed sending CDP frames tagged with VID 1 if the management VLAN is not VID 1
- Fixed SNMP walk failing if VLANs are not in numerical order
- Fixed using hash mark in SMTP password
- Fixed using hash mark in RADIUS password
- Fixed issues with Loop Protection on SFP ports
- Fixed intermittent telemetry error on Device/Status TAB mostly seen with WS-26-500-DC
- Fixed power TAB shutdown time set to 12 AM would turn off poe on that port]
- Fixed ST/RSTP bridge priority change would not update properly
- Fixed cli on WS-8-150-DC model's allowing one to set the power restart/shutoff from cli
- Fixed scheduled portbounce to no longer trigger unexpected link status change email
- Fixed SNMP broken in v1.5.0rc5 due to a build mistake
- Fixed SNMP handling longer firmware version
- Extended length for URL resource for SMTP recipient address

ENHANCEMENTS
- Optimized code to reduce CPU utilization especially needed for the WS-26-500-DC
- Changed watchdog waits + Interval seconds before checking again after watchdog is triggered
- Added log entry to report if the switch rebooted due to watchdog timer
- Added lldpRemPortId, lldpRemPortIdSubtype, and lldpRemPortDesc to LLDP-MIB
- Added cdpCacheDevicePort to CISCO-CDP-MIB
- Added popover for POE enabled ports on 'Watts' column to show power usage on each pair for VH ports
- Added root bridge id to STP log message
- Added Low Voltage notification for DC model's to contain the threshold and the present value in the log/email
- SNMP Contact and Location character limit increased from 26 to 255 characters
- Improved ability to deal with loops while loop protection, flow control, and STP disabled to not reboot
- Added checkbox to SYSLOG Configuration called "Log Name" which appends the switch name to messages
- Added Calling-Station-Id to RADIUS attributes to allow freeradius to log ip address of client

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help
- IGMP snooping over VLANS, MSTP, and ERPS are still being developed

Released 6/4/2018

[aaron@futuretk.com]

Chris,
Updating to 1.5.0 seems to power cycle all connected PoE devices at the end of the update. I don't believe I've seen that behavior before. I just applied it to a WS-26-500-DC in our lab environment, and it appears to have powercycle a connected CCR1009 once at the end of the update, and a second during the reboot it performs just after the update.

Is this expected behavior?

[sirhc]

Sometimes a firmware upgrade will cause a cold boot, this is not intended but can happen in frequently.

This is not new to v1.5.0 as we have seen this in previous versions and have no idea why.

I upgraded 12 switches the other day and 1 did a cold reboot power cycling the POE the other 11 rebooted properly leaving the POE ON.

Not sure why it happens every so often but sometimes it does.

[coreinput]

Upgraded from 1.4.8 after 202 days uptime and everything went smooth (and no POE loss).
Hats off to Eric and team including the beta testers for making this a good release.
Thanks!

[slimey]

Upgrading from 1.5.0rc3 to 1.5.0 I noticed this error during the upgrade process...


Do not turn off power while upgrade is in progress!
Uploading firmware file ...
Unpacking firmware ...
/usr/bin/firmware_upgrade: line 164: //: Permission denied
Running preflash script ...
Unlocking /dev/mtd8 ...
Writing from redboot_recovery_config to /dev/mtd8 ...
Unlocking linux ...
Writing from kernel.img to linux ...


Upgrade seems to work fine, though...

[Eric Stern]

Upgrading from 1.5.0rc3 to 1.5.0 I noticed this error during the upgrade process...


Do not turn off power while upgrade is in progress!
Uploading firmware file ...
Unpacking firmware ...
/usr/bin/firmware_upgrade: line 164: //: Permission denied
Running preflash script ...
Unlocking /dev/mtd8 ...
Writing from redboot_recovery_config to /dev/mtd8 ...
Unlocking linux ...
Writing from kernel.img to linux ...


Upgrade seems to work fine, though...

Just a small typo in the upgrade script, won't affect anything.

[mhoppes]

Small typo? Gulp. What’s that line suppose to do?

[sporkman]

Perhaps it's a shell script, and someone used a PHP comment (//) instead of a (#). The system tries to "execute" //, which isn't happening (and would be harmless).

[sirhc]

Upgrading from 1.5.0rc3 to 1.5.0 I noticed this error during the upgrade process...

/usr/bin/firmware_upgrade: line 164: //: Permission denied

Reported

Just a small typo in the upgrade script, won't affect anything.

Answered

Small typo? Gulp. What’s that line suppose to do?

If it was harmful in anyway we would tell you, Eric told you above that it was a small typo and was harmless.

Perhaps it's a shell script, and someone used a PHP comment (//) instead of a (#). The system tries to "execute" //, which isn't happening (and would be harmless).

Sporkman nailed it.

This was copied from our internal Skype conversation:

I mistakenly used // for a comment instead of #
Will not hurt anything other than report an erroneous error message
Fixed it and replaced v1.5.0 in the download section

[LRL]

Tonight I upgraded several switches to 1.5.0 and all except one went off without issues.

The problem child is a ws-12-250-dc was running 1.4.9. Upon upgrade the switch went as normal but never came back up after. Upon arriving on site I found the switch to have no lights except a few green lights internally on what appear to be on the power supply board. Removing DC from the terminals for a few seconds and reconnecting brought the switch back to life.

The status page shows:

Firmware Version 1.5.0
Board Rev F
Power Supply Firmware Version 70
Power Supply Board Rev B
I'm curious to know if there was a PS Firmware change here too and if it should be running 70?