v1.4.5rcX Bug Reports and Comments

[sirhc]

Please post comments and report bugs for v1.4.5rcX in this thread

FIXED[b]/CHANGED[/b]
- Fixed voltage fluctuation that affected a small percentage of WS-6-MINI, WS-8-150-AC, WS-8-150-DC - rc1
- Updated SSH daemon to get more modern key exchange algorithm - rc1
- Watchdog no longer checks for link on port to be bounced - rc1
- Ignore the SFP ports when checking Priority values - rc4
- Changed throttle limits between switch core and CPU - rc4
- Fixed web UI login only using the first 8 characters of the password - rc4
- Removed Address from MODBUS configuration - rc4
- Fixed reset button on WS-6-MINI broken since v1.4.1 - rc6
- Fixed web UI display for mobile devices - rc8

ENHANCEMENTS
- Added option to bounce link instead of POE for watchdog rules - rc1
- Added support for 1000BASE-BX SFP modules (including Fiberstore SFP-GE-BX) - rc2
- Added ability to configure QoS based on packet headers (MAC, IP, TCP ports, etc) - rc6
- Added support for Mikrotik S-RJ01 SFP module - rc6
- Show the SFP model number in UI - rc6
- Skip PoE watchdog if PoE is not turned on for a port - rc7
- Changed default Revert Timer value from 60 to 180 seconds - rc7
- Added range for DSCP and PCP values in QoS rules - rc7
- Removed DSCP and PCP mappings from QoS config - rc7

KNOWN ISSUES
- Some language templates need help - please contact us to help - rc1

Released 10/31/2016 - rc8
Released 10/21/2016 - rc7
Released 10/18/2016 - rc6
Released 10/10/2016 - rc4
Released 9/21/2016 - rc2
Released 9/19/2016 - rc1

[IntL-Daniel]

Fix - Watchdog no longer checks for link on port to be bounced - rc1

Do I understand correctly that current 1.4.4 final and Watchdog does not work at all?

[sirhc]

Fix - Watchdog no longer checks for link on port to be bounced - rc1

Do I understand correctly that current 1.4.4 final and Watchdog does not work at all?

No, read what it says and think about what it is saying.

Currently in v1.4.4 and older if you defined a watchdog rule to ping a device and on failure of this ping port 5 is to be bounced by cycling POE power but if port 5 has no Ethernet link it ignores the rule thinking there is no point to bounce POE power on port 5 since it does not detect an Ethernet link on port 5.

This check was removed in v1.4.5rc1

99.999% of the times when a device locks up and no longer responds to pings it still has a physical link the device just will not respond to pings so you reboot it.

[IntL-Daniel]

OK thanks for explanation!

[sirhc]

v1.4.5rc2 is now available for download.

- Added support for 1000BASE-BX SFP modules (including Fiberstore SFP-GE-BX) - rc2

[Fisher]

I just upgraded.

*fingers crossed*

[jakematic]

Installed a brand new WS-8-150-AC this week that had never connected to another switch/device - just an AGW-Pro powered by the switch and a Chromebox.
This morning the 48V & 24V were bouncing around.

Upgraded to v1.4.5rc2 and the fluctuations have disappeared, will continue to monitor.

[IntL-Daniel]

Which version bouncing?

[sirhc]

Which version bouncing?

We have an issue that affect about 1% +/- of the following models:
WS-6-MINI
WS-8-150-AC
WS-8-150-DC

Where the software will report the voltages bouncing around if you have most of the Ethernet ports used but normally goes away with just one or a couple ports active.

This is due to +/- tolerances of components that mess up our 3.3V reading and since the 3.3V reading is used as a reference for the readings of the 24V and 48V they all 3 bounce.

v1.4.5.rc2 will correct for the +/- component tolerance and stabilize the voltage readings as the voltage is actually not fluctuating. Well that is not 100% true, voltages always fluctuate a little but acceptable fluctuations are expected and called ripple. At worst 300 millivolts can be observed on our voltages under load with a good enough piece of equipment to measure it.

All of the above mentioned models with a manufactured date of 9/9/2016 or later now have a higher cost component to remove this +/- tolerance issue.

Just upgrade to v1.4.5rc2 and you should be good.

There are other reasons to upgrade to v1.4.5rc2 anyway as it has bugs fixed that were found in v1.4.4 and it also has new security patches.

If your switch is on a public IP you definitely want to upgrade to v1.4.5rc2 and you should also use the Access COntrol List to limit who can access your switch from the web.

[Fisher]

I'm still getting Out of Range log messages. A couple a day. This is an improvement over 1.4.4 where I could get a couple an hour.

Sep 22 12:09:29 switch[1322]: 24V is out of range (22.7V)
Sep 23 00:57:57 switch[1322]: 24V is out of range (22.7V)
Sep 23 03:36:48 switch[1322]: 24V is out of range (22.7V)
Sep 23 20:02:41 switch[1322]: 24V is out of range (22.7V)
Sep 24 08:39:19 switch[1322]: 24V is out of range (22.8V)
Sep 24 14:16:32 switch[1322]: 24V is out of range (22.7V)
Sep 25 19:11:11 switch[1322]: 24V is out of range (22.7V)
Sep 25 22:39:09 switch[1322]: 24V is out of range (22.8V)
Sep 26 07:51:31 switch[1322]: 24V is out of range (22.8V)