v1.5.0rc3 and newer Bug Reports and Comments.

[sirhc]

Please post bug reports and comments on v1.5.0rc3 and newer ONLY in this thread.
We started a new thread for v1.5.0rc3 because v1.5.0rc1 did reduce CPU utilization which was GOOD but did not fix issues it was intended to fix.

Next v1.5.0rc2 was a blunder on our part and the use of that firmware could actually cause worse issues and could possibly brick a WS-8-250-DC or WS-12-250-DC or WS-26-500-DC unit (all other units it would not harm).

We spent about 1 week testing v1.5.0rc3 so we feel much more confident we achieved our goal?

FIXED/CHANGED
- Fixed I2C service to deal with errors better to prevent reboots with WS-12-250-DC and WS-26-500-DC - RC2 & RC3
Note: The attempt to fix I2C in RC2 was a failure and caused worse issues.
It was rushed out too fast with not enough testing.
If you downloaded v1.5.0rc2 DELETE IT AND NEVER USE IT AGAIN
We spent almost a week testing the I2C in RC3 and feel we got it right this time.

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

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

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

RC1 Released 3/19/2018
RC2 Released 3/22/2018
RC3 Released 4/3/2018
RC4 Released 4/30/2018
RC5 Released 5/25/2018 - BROKE SNMP Confirmed 5/31/2018
RC6 Released 6/2/2018

[aaron@futuretk.com]

One of my WS-26-500-DC switches is showing Error on most of the power supply graphs after upgrading from 1.5.0rc1. Image attached.

Thank you
-Aaron

[sirhc]

One of my WS-26-500-DC switches is showing Error on most of the power supply graphs after upgrading from 1.5.0rc1. Image attached.

Thank you
-Aaron

That is why we have v1.5.0rc3, this thread is ONLY for v1.5.0rc3 or newer which is the current firmware version we are working on.

v1.5.0rc1 is fine that you installed but install v1.5.0rc3

If you downloaded v1.5.0rc2 DELETE IT AND NEVER USE IT AS IT "COULD" BRICK THE FOLLOWING SMART DC SWITCHES

WS-8-250-DC - OLD DISCONTINUED UNIT NOT TO BE CONFUSED WITH WS-8-150-DC WHICH IT WILL NOT HURT
WS-12-250-DC
WS-26-500-DC

[Julian]

One of my WS-26-500-DC switches is showing Error on most of the power supply graphs after upgrading from 1.5.0rc1. Image attached.

Thank you
-Aaron

Aaron - this can happen. Sometimes a warm reboot will fix this, but most of the time it needs a hard reset (power cycle) to clear.

Thanks!

[lligetfa]

v1.5.0rc1 is fine that you installed but install v1.5.0rc3

Chris, if you look closely at the screenshot you will see that it is in fact rc3. Might that be one of the units that should have the wire harness rerouted?

[sirhc]

v1.5.0rc1 is fine that you installed but install v1.5.0rc3

Chris, if you look closely at the screenshot you will see that it is in fact rc3. Might that be one of the units that should have the wire harness rerouted?

Fixing the I2C cable (if needed) is always a good idea but with rc3 it is not so much needed.

The I2C cable is not what causes this issue, it just happens once and a blue moon and we have no idea why but a power cycle fixes it.

I have rebooted switches hundreds of times trying to recreate it so we could trouble shoot it but with no luck and when customers encounter it they just want it gone so a power cycle clears it.

The odds in it happen has to be something like 1 in thousands of reboots.

[rwineteer]

I have a WS-26-500-DC unit running rc3 that's still rebooting, though it hasn't had the wiring adjusted internally. After it was upgraded to rc3 a lot of the sensors were reporting error. It's had a warm reboot after upgrading, which never cleared the errors.

[sirhc]

I have a WS-26-500-DC unit running rc3 that's still rebooting, though it hasn't had the wiring adjusted internally. After it was upgraded to rc3 a lot of the sensors were reporting error. It's had a warm reboot after upgrading, which never cleared the errors.

You need to do a power cycle. Since your there doing the power cycle you could also check the I2C cable.

[IntL-Daniel]

I have more often cold (watchdog) reboot detected on our WS-12-250-AC running 1.5.0rc3 :-( I can see the message in the log then:

Code: Select all

 Jan 1 01:00:28 switch[783]: Detected cold (watchdog) boot

Last reboot was after 1 week uptime only. We saw unexpected reboots already on 1.4.8 on this switch...but if I remember NEVER up to fw 1.4.7. We have another 5 WS-10-250-AC without any reboot on 1.5.0rc3. Is I2C cabling issue related to WS-12-250-AC model as well?

[sirhc]

I have more often cold (watchdog) reboot detected on our WS-12-250-AC running 1.5.0rc3 :-( I can see the message in the log then:

Code: Select all

 Jan 1 01:00:28 switch[783]: Detected cold (watchdog) boot

Last reboot was after 1 week uptime only. We saw unexpected reboots already on 1.4.8 on this switch...but if I remember NEVER up to fw 1.4.7. We have another 5 WS-10-250-AC without any reboot on 1.5.0rc3. Is I2C cabling issue related to WS-12-250-AC model as well?

No there is no I2C communication on any of our "AC" models.

The only switches with an I2C communications between switch and SMART DC power supplies are WS-8-250-DC (Discontinued), WS-12-250-DC, and WS-26-500-DC.

If you are seeing "Cold reboots" something else is afoot. Power disruptions or possibly a defective unit. I would look at power issue.

You could also swap the suspect unit out with a spare and if the replacement does the same thing you can bet it is probably not the switch.