v1.5.1rcX Bug Reports and Comments

[Stephen]

VLAN Trunking on our switch is to allow the switch to accept tagged packets from VLANs other than ones explicitly configured on the VLAN page. Therefore including a VLAN on the trunk list whether it's defined or not by definition means that it won't be excluded. On that note, if you want to exclude a VLAN defined on the page, simply remove it from the trunk list and you can set the relevant port to 'E'.

[slowe]

In the past when we have been changing a VLAN to E and it’s in the trunk list was it still actually passing that vlan traffic on that port that had the E?

[Stephen]

Would you happen to know which version of code you are referring too? I can double check for you if you can tell me which one was doing this.

[sirhc]

FIXED/CHANGED
- Fixed voltage input calibration for the WS-8-150-DC - RC1
- Fixed services running on IPv6 - RC2
- Fixed being able to bypass console login by hitting CTRL-C - RC2
- Fixed MSTP setting instance forwarding state - RC2
- Fixed UI on ERPS tab to prevent footer from from being mangled - RC3
- Fixed ERPS MEPs issue that triggered a Signal Fail on a ring when port not in the ring is disconnected/disabled - RC3
- Fixed ERPS issue that prevented access to Management VLAN when added to the protected VLAN list - RC3
- Fixed ERPS protected VLANs would not forward packets outside of the ring - RC3

ENHANCEMENTS

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 6/20/2018
RC2 Released 7/10/2018
RC3 Released 8/2/2018

[surfermarty]

1.5.1rc3

Received a new WS-12-250-DC recently that requires FW > 1.5 according to the sheet of paper that accompanied it. We've put on 1.5.1rc3 and now find no response to any SNMP queries on either v1 or v2c. Internal network so no firewalls involved; nothing configured (intentionally) on the Netonix with regards to management restrictions. IP working fine - we can probe it remotely from across the network.

Anything I can try to see if we can get SNMP working again, or anything I need to provide to help debug it?

Thanks.

Marty

[surfermarty]

Ok, so after engaging my brain and remembering this is really unix under the hood - the daemon isn't running and when you try to run it by hand, it seg-faults

admin@NTX:/tmp/log# /usr/sbin/snmpd -Le -p /var/run/snmpd.conf -f
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (SNMPv2-SMI): At line 0 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 0 in (none)
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
Cannot find module (TUNNEL-MIB): At line 0 in (none)
Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)
Cannot find module (IPV6-ICMP-MIB): At line 0 in (none)
Cannot find module (IPV6-MIB): At line 0 in (none)
Cannot find module (IPV6-TCP-MIB): At line 0 in (none)
Cannot find module (IPV6-UDP-MIB): At line 0 in (none)
Segmentation fault

Known issue?

[Stephen]

Just to check the basics have you enabled snmp in your device configuration tab?

[dray]

SNMP broke for me on a WS-12-250-DC. Trying different versions and settings, and rebooting didnt help.

v1.5.1.rc3

[Stephen]

OK it does appear there is a problem here.
Stay tuned, working on a new update.

[surfermarty]

Yes - SNMP is enabled - tried both V1, V2c and then both - the fact the daemon isn't running and is seg faulting would seem to be the issue.