Netonix Forums

v1.4.7 wrote:NOTE: MSTP is still being tested so use MSTP at your own risk.

FIXED/CHANGED
- Fixed temp sensors showing crazy values in very cold environments
- Fixed getting "unexpected link change" messages due to port bounce, watchdogs, etc
- Fixed port bounce being 1 hour off after daylight savings time changes
- Fixed VLAN tab layout getting messed up when you delete a VLAN
- Fixed mac table refresh button causing entire page to reload
- Fixed problem with QinQ when using untagged VLANs
- Fixed fan control handling negative temperatures
- Fixed input voltage graph labels
- Fixed Apply/Save becoming active when looking at MSTP configuration even though nothing changed
- Fixed port number in log messages
- Fixed issue when importing config from a RevE board to a RevF with different POE port options. Affected WS-6 and WS-12
- Fixed the support for WS-8-150-AC
- Fixed console login
- Fixed/Force powerdown/powerup limits on WS-8-150-DC to help prevent switch lock up when draining battery to 9V
- Fixed DC2DC-500 detection for WS-26-500-DC
- Fixed voltage range on dumb DC models
- Fixed QinQ
- Fixed VLAN trunking
- Fixed Access Controls not honouring the Enable setting
- Fixed switch rebooting if multiple ports lose link too quickly
- Fixed multiple ports not turning off at the same time when they have the same shutdown voltage
- Fixed unexpected link change speed message
- Fixed port selection Tabs
- Fixed slight glitch in Input Current graph
- Fixed STP tab on 12 port models
- Fixes for WS-26-500-DC
- Fixed bulk editing Flow Control on Ports tab
- Fixed updating Watchdog description if port name is changed
- Fixed bulk editing on Power tab
- Allow QinQ and Double Tagging to be used with Trunk ports
- Changed UI layout on QOS tab
- Changed dumb DC models to temporarily disable POE when input voltage falls too low instead of disabling POE in the configuration
- Changed valid DC input voltage range to 9-72V in GUI for newer board revs
- Changed valid upper range for dc output voltage from 51V to 53V
- Changed input voltage graph to auto-scale
- Changed fan control to also use CPU and PHY temp
- Changed valid temp range on Status page meters
- Changed input voltage threshold where it forgets the configured Wake up voltage and defaults to 10V Wake up on WS-12-250-DC

ENHANCEMENTS
- Added MSTP
- Automatically disable flow control on ports using QOS bandwidth limits to prevent packet locks
- Added restart timer to DC power supply to help in very cold environments with cold starts
- Added log message when time is set by NTP after boot is finished
- Added logging when STP selects new root port
- Added POE startup delay option on Power tab
- Added root path cost on STP tab
- Added portDuplex SNMP stat from CISCO-STACK-MIB
- Added ifAdminStatus to SNMP stats
- Added support for new WS-26 models
- Added Double Tagged to VLAN configuration
- Added IP Protocol to QoS rules
- Added CIDR notation in QoS Source IP rules
- Added option to log web and ssh logins
- Added LLDP-MIB and CISCO-CDP-MIB to SNMP
- Added option to change MAC aging time
- Added "Disable Power" action to watchdog

KNOWN ISSUES
- Some language templates need help - please private message Eric Stern to help

Released 5/7/2017

giannici wrote:Hi!

Today I have found another bug with SFP ports: I disabled an SFP port (Port 14), then I have gone to the "Status" tab and port was actually shown as disabled and no traffic was flowing, but then I returned to the "Ports" tab and... the port appeared as enabled!

Firmware 1.4.7 release.

I have to say that I wasn't able to reproduce it anymore, but fortunately I have immediately taken photos so I'm sure it wasn't an hallucination! I don't remember exactly but perhaps between the switch to the two tabs, maybe I removed and inserted the SFP module, but again it's only a possibility, actually I don't remember.

jonwang wrote:I'm not sure it this is a 1.4.7 issue or HW, but I had a switch out of the blue fail on me today. WS-12-250-AC only a few month's old fed by an AF24 (but using PoE brick). It then feeds several Ethernet switches via copper and fiber.

I first tried physically rebooting the switch several times before I yanked it. Wasn't hot, no weird power issues, no storms or water, and only a hard reset as it was powering back up brought it back.