Netonix Forums

v1.5.5 wrote:FIXED/CHANGED
- WS-12-400-AC would not display port 5 and port 6 monitored power correctly for VH (This bug has been present since before 1.4.9)
- Added Firmware Version to page footer
- DCDC Bootloader Version and DCDC Board Rev display correctly if i2c link to Power Supply is broken on boot up
- vtss_appl is now SIGNIFICANTLY more stable than it was. This was probably the root of many other issue's experienced by users.
- SFP module interaction has improved SIGNIFICANTLY, rebooting, and general operation should no longer cause failure's. It's possible more module's are compatible as well (this requires further testing)
- Boot up now performs a gratuitous ARP broadcast, which prevents the scenario where upon a warm or cold boot (aka firmware upgrade, etc) where loss of connectivity
to the switch's management site or ssh access occurs even if sometimes otherwise the switch is operating.
- Fixed issue, upon boot or config changes, PoE wattage values would disappear on smart DC switches if i2c to the Power Supply failed.
- vtss_appl should no longer crash when Management VLAN ID is changed from default or if IP addresses are assigned to any other VLANs, and overall stability has been increased beyond rc2
- IPv6 address's will no longer be assigned to interfaces via SLAAC when IPv6 is disabled which caused a security concern, instead it is now a configurable option
- fixed vtss_appl crash loop caused by having >8 IP address's assigned to a VLAN

ENHANCEMENTS
- "Stats" checkbox in ports tab when disabled now removes excessive logging for the associated port
- IPv6 "SLAAC" is a separate option in the Device Config Tab under IPv6 as well as the CLI
- New command in CLI "web_conf_check" which will detect and repair web config corruption that can prevent access to the web UI.
- At bootup, switch runs web config check to prevent faulty web UI config


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

Released 10/15/2019

Banana Jack wrote:Thanks for the new release! Should I be worried that the gratuitous ARP broadcast at boot up could cause packet storms on a large flat network in the same way that Ubiquiti Discovery packets do?

Code: Select all

2019-10-17T04:05:53-06:00 100.96.109.2 UI: Firmware upgrade by admin (::ffff:74.50.218.133)
2019-10-17T04:07:35-06:00 100.96.109.2 Port: link state changed to 'down' on port 13
2019-10-17T04:07:35-06:00 100.96.109.2 Port: link state changed to 'down' on port 14
2019-10-17T04:07:35-06:00 100.96.109.2 Port: link state changed to 'down' on port 7
2019-10-17T04:07:35-06:00 100.96.109.2 STP: msti 0 set port 13 to discarding
2019-10-17T04:07:35-06:00 100.96.109.2 STP: msti 0 set port 14 to discarding
2019-10-17T04:07:35-06:00 100.96.109.2 STP: msti 0 set port 7 to discarding
2019-10-17T04:07:36-06:00 100.96.109.2 Port: link state changed to 'down' on port 12
2019-10-17T04:07:36-06:00 100.96.109.2 STP: msti 0 set port 12 to discarding
2019-10-17T04:07:37-06:00 100.96.109.2 Port: link state changed to 'down' on port 6
2019-10-17T04:07:37-06:00 100.96.109.2 STP: msti 0 set port 6 to discarding
2019-10-17T04:07:38-06:00 100.96.109.2 Port: link state changed to 'down' on port 5
2019-10-17T04:07:38-06:00 100.96.109.2 Port: link state changed to 'up' (100M-F) on port 12
2019-10-17T04:07:38-06:00 100.96.109.2 Port: link state changed to 'up' (100M-F) on port 13
2019-10-17T04:07:38-06:00 100.96.109.2 Port: link state changed to 'up' (100M-F) on port 14
2019-10-17T04:07:38-06:00 100.96.109.2 Port: link state changed to 'up' (100M-F) on port 7
2019-10-17T04:07:38-06:00 100.96.109.2 STP: msti 0 set port 12 to discarding
2019-10-17T04:07:38-06:00 100.96.109.2 STP: msti 0 set port 13 to discarding
2019-10-17T04:07:38-06:00 100.96.109.2 STP: msti 0 set port 14 to discarding
2019-10-17T04:07:38-06:00 100.96.109.2 STP: msti 0 set port 5 to discarding
2019-10-17T04:07:38-06:00 100.96.109.2 STP: msti 0 set port 7 to discarding
2019-10-17T04:07:39-06:00 100.96.109.2 Port: link state changed to 'up' (100M-F) on port 6
2019-10-17T04:07:39-06:00 100.96.109.2 STP: msti 0 set port 6 to discarding
2019-10-17T04:07:39-06:00 100.96.109.2 switch[1693]: !unexpected link change on port 7 (AP AC NLRN3) from 1G to 100M-F
2019-10-17T04:07:40-06:00 100.96.109.2 Port: link state changed to 'up' (100M-F) on port 5
2019-10-17T04:07:40-06:00 100.96.109.2 STP: msti 0 set port 14 to forwarding
2019-10-17T04:07:40-06:00 100.96.109.2 STP: msti 0 set port 14 to learning
2019-10-17T04:07:40-06:00 100.96.109.2 STP: msti 0 set port 5 to discarding
2019-10-17T04:07:41-06:00 100.96.109.2 switch[1701]: !unexpected link change on port 13 (AP AC NLRW2) from 1G to 100M-F
2019-10-17T04:11:33-06:00 100.96.109.2 init: starting pid 2108, tty '': '/etc/init.d/rcS K stop'
2019-10-17T04:16:05-06:00 100.96.109.2 kernel: SQUASHFS error: lzma returned unexpected result 0x1


Code: Select all

switch -? !unexpected link change on port 13 (AP AC NLRW2) from 1G to 100M-F