Page 1 of 2
v1.5.15rc1 Bug Reports and Comments
Posted: Fri Oct 20, 2023 7:22 pm
by sirhc
Latest WS Release Candidate: v1.5.15rc1Click
HERE to download firmware v1.5.15rc1 - Released 10/20/2023
FIXED/CHANGED- Fixed SNMP init error (causing memory leaks)
- Fixed kernel page-cache failure
- Fixed watchdog memory leak
ENHANCEMENTSKNOWN ISSUES- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help
Released 10/20/2023
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Wed Oct 25, 2023 8:13 am
by IntL-Daniel
Good to see that NETONIX producs are not EOL and still live, thanks! I hope for another bugfixes within next RC relleases like this
SFP port flaps on any config change .
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Thu Oct 26, 2023 7:24 am
by mayheart
No issues to report other than the SFP port issues while applying changes.
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Thu Oct 26, 2023 2:51 pm
by sirhc
IntL-Daniel wrote:Good to see that NETONIX producs are not EOL and still live, thanks! I hope for another bugfixes within next RC relleases like this
SFP port flaps on any config change .
I do not see this, have you tried another module?
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Thu Oct 26, 2023 5:21 pm
by mayheart
sirhc wrote:IntL-Daniel wrote:Good to see that NETONIX producs are not EOL and still live, thanks! I hope for another bugfixes within next RC relleases like this
SFP port flaps on any config change .
I do not see this, have you tried another module?
We've had it happen with FS, Cisco and Juniper SFPs. This behavour started after 1.5.5.
Sometimes the port will bounce and come back fine, sometimes the only way to get back into it is a powercycle or have management built over a copper port and manually shut down/bring up the port.
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Thu Oct 26, 2023 5:52 pm
by Dave
we will investigate
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Thu Oct 26, 2023 5:59 pm
by jpmoller
This issue has been brought up a number of times in 1.5.14
I have an active switch at the moment that you can see ethernet flaps on the SPF port every time we make a vlan change to the switch. As others have mentioned, sometimes the switch will down the SFP port and not come back up without a reboot or having access via a copper port.
Oct 20 09:03:02 UI: VLAN 230 PortSettings: changed from 'EEEEEEEEEEEEEEEEEEEEEEETET' to 'EEEEEEEEEEEEEEEEEEEEEEEEET'
Oct 20 09:03:13 STP: msti 0 set port 7 to discarding
Oct 20 09:03:14 STP: msti 0 set port 24 to discarding
Oct 20 09:03:14 STP: msti 0 set port 26 to discarding
Oct 20 09:03:16 STP: msti 0 set port 26 to learning
Oct 20 09:03:16 STP: msti 0 set port 26 to forwarding
Oct 20 09:03:16 STP: msti 0 set port 24 to learning
Oct 20 09:03:16 STP: msti 0 set port 24 to forwarding
Oct 20 09:03:16 STP: msti 0 set port 7 to learning
Oct 20 09:03:16 STP: msti 0 set port 7 to forwarding
Oct 20 09:03:22 Port: link state changed to 'down' on port 26
Oct 20 09:03:22 STP: msti 0 set port 26 to discarding
Oct 20 09:03:26 Port: link state changed to 'up' (1G) on port 26
Oct 20 09:03:26 STP: msti 0 set port 26 to discarding
Oct 20 09:03:28 STP: msti 0 set port 26 to learning
Oct 20 09:03:28 STP: msti 0 set port 26 to forwarding
Another occurence:
Oct 20 11:39:39 UI: VLAN 231 PortSettings: changed from 'EEEEEEEEEEEEEEEEEEEEEEEEET' to 'EEEEEEEEEEEEEEEEEEEEEEETET'
Oct 20 11:39:54 STP: msti 0 set port 7 to discarding
Oct 20 11:39:55 STP: msti 0 set port 26 to discarding
Oct 20 11:39:57 STP: msti 0 set port 26 to learning
Oct 20 11:39:57 STP: msti 0 set port 26 to forwarding
Oct 20 11:39:57 STP: msti 0 set port 7 to learning
Oct 20 11:39:57 STP: msti 0 set port 7 to forwarding
Oct 20 11:40:03 Port: link state changed to 'up' (1G) on port 24
Oct 20 11:40:03 STP: msti 0 set port 24 to discarding
Oct 20 11:40:03 Port: link state changed to 'down' on port 26
Oct 20 11:40:03 STP: msti 0 set port 26 to discarding
Oct 20 11:40:05 STP: msti 0 set port 24 to learning
Oct 20 11:40:06 STP: msti 0 set port 24 to forwarding
Oct 20 11:40:06 Port: link state changed to 'up' (1G) on port 26
Oct 20 11:40:06 STP: msti 0 set port 26 to discarding
Oct 20 11:40:09 STP: msti 0 set port 26 to learning
Oct 20 11:40:09 STP: msti 0 set port 26 to forwarding
And another two back-to-back:
Oct 20 11:39:39 UI: VLAN 231 PortSettings: changed from 'EEEEEEEEEEEEEEEEEEEEEEEEET' to 'EEEEEEEEEEEEEEEEEEEEEEETET'
Oct 20 11:39:54 STP: msti 0 set port 7 to discarding
Oct 20 11:39:55 STP: msti 0 set port 26 to discarding
Oct 20 11:39:57 STP: msti 0 set port 26 to learning
Oct 20 11:39:57 STP: msti 0 set port 26 to forwarding
Oct 20 11:39:57 STP: msti 0 set port 7 to learning
Oct 20 11:39:57 STP: msti 0 set port 7 to forwarding
Oct 20 11:40:03 Port: link state changed to 'up' (1G) on port 24
Oct 20 11:40:03 STP: msti 0 set port 24 to discarding
Oct 20 11:40:03 Port: link state changed to 'down' on port 26
Oct 20 11:40:03 STP: msti 0 set port 26 to discarding
Oct 20 11:40:05 STP: msti 0 set port 24 to learning
Oct 20 11:40:06 STP: msti 0 set port 24 to forwarding
Oct 20 11:40:06 Port: link state changed to 'up' (1G) on port 26
Oct 20 11:40:06 STP: msti 0 set port 26 to discarding
Oct 20 11:40:09 STP: msti 0 set port 26 to learning
Oct 20 11:40:09 STP: msti 0 set port 26 to forwarding
Oct 20 11:43:06 UI: Configuration changed by root (::ffff:10.1.22.254)
Oct 20 11:43:06 UI: Port 7 Enable: changed from 'Enabled' to 'Disabled'
Oct 20 11:43:12 Port: link state changed to 'down' on port 7
Oct 20 11:43:12 STP: msti 0 set port 7 to discarding
Oct 20 11:43:26 UI: Configuration changed by root (::ffff:10.1.22.254)
Oct 20 11:43:26 UI: Config_Version: changed from '1446' to '1444'
Oct 20 11:43:26 UI: Port 7 Enable: changed from 'Disabled' to 'Enabled'
Oct 20 11:43:26 UI: VLAN 231 PortSettings: changed from 'EEEEEEEEEEEEEEEEEEEEEEETET' to 'EEEEEEEEEEEEEEEEEEEEEEEEET'
Oct 20 11:43:26 UI: VLAN 236 PortSettings: changed from 'EEEEEEEEEEEEEEEEEEEEEEEEET' to 'EEEEEEEEEEEETEEEEEEEEEEEET'
Oct 20 11:44:19 UI: Configuration changed by root (::ffff:10.1.22.254)
Oct 20 11:44:19 UI: VLAN 236 PortSettings: changed from 'EEEEEEEEEEEEEEEEEEEEEEEEET' to 'EEEEEEEEEEEEETEEEEEEEEEEET'
Oct 20 11:44:34 STP: msti 0 set port 24 to discarding
Oct 20 11:44:34 STP: msti 0 set port 26 to discarding
Oct 20 11:44:36 STP: msti 0 set port 26 to learning
Oct 20 11:44:36 STP: msti 0 set port 26 to forwarding
Oct 20 11:44:36 STP: msti 0 set port 24 to learning
Oct 20 11:44:36 STP: msti 0 set port 24 to forwarding
Oct 20 11:44:42 UI: Configuration changed by root (::ffff:10.1.22.254)
Oct 20 11:44:42 Port: link state changed to 'down' on port 26
Oct 20 11:44:42 STP: msti 0 set port 26 to discarding
Oct 20 11:44:43 UI: VLAN 236 PortSettings: changed from 'EEEEEEEEEEEEETEEEEEEEEEEET' to 'EEEEEEEEEEEEEEEEEEEEEEEEET'
Oct 20 11:44:45 Port: link state changed to 'up' (1G) on port 26
Oct 20 11:44:45 STP: msti 0 set port 26 to discarding
Oct 20 11:44:47 STP: msti 0 set port 26 to learning
Oct 20 11:44:47 STP: msti 0 set port 26 to forwarding
Oct 20 11:45:04 STP: msti 0 set port 24 to discarding
Oct 20 11:45:04 STP: msti 0 set port 26 to discarding
Oct 20 11:45:06 STP: msti 0 set port 26 to learning
Oct 20 11:45:06 STP: msti 0 set port 26 to forwarding
Oct 20 11:45:06 STP: msti 0 set port 24 to learning
Oct 20 11:45:06 STP: msti 0 set port 24 to forwarding
Oct 20 11:45:12 Port: link state changed to 'down' on port 26
Oct 20 11:45:12 STP: msti 0 set port 26 to discarding
Oct 20 11:45:15 Port: link state changed to 'up' (1G) on port 26
Oct 20 11:45:15 STP: msti 0 set port 26 to discarding
Oct 20 11:45:18 STP: msti 0 set port 26 to learning
Oct 20 11:45:18 STP: msti 0 set port 26 to forwarding
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Fri Oct 27, 2023 10:08 pm
by mayheart
I just had one here myself.
Oct 27 14:51:18 UI: VLAN 991 PortSettings: changed from 'ETTTUEUUUEUUTT' to 'ETTTUUUUUEUUTT'
Oct 27 14:51:18 UI: VLANs: removed ''
Oct 27 14:51:24 admin: removing lan (eth0.991) from firewall zone lan
Oct 27 14:51:27 admin: adding lan (eth0.991) to firewall zone lan
Oct 27 14:51:28 system: starting ntpclient
Oct 27 14:51:29 admin: removing lan (eth0.991) from firewall zone lan
Oct 27 14:51:34 admin: adding lan (eth0.991) to firewall zone lan
Oct 27 14:51:34 system: starting ntpclient
Oct 27 14:51:38 admin: adding lan (eth0.991) to firewall zone lan
Oct 27 14:51:45 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:45 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:45 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:46 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:46 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:47 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:47 Port: link state changed to 'up' (1G) on port 13
Oct 27 14:51:48 Port: link state changed to 'up' (1G) on port 13
I had to shut down the port on the far end for it to come back up. I'm using a FS GE-BX optic here. Speed is manually coded at this one switch to 1G. Far side is a Cisco NCS and requires that to be manually set.
I've also had this happen on auto negotiate connected to Cisco ASR920s and a Juniper MX5.
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Sun Oct 29, 2023 4:30 pm
by jpmoller
Unfortunately, the SNMP memory leak appears to still be present on the one host we have deployed the new firmware on.
Far right peak is the reboot with the new firmware applied. Rate of available memory depletion is the same as when it was on 1.5.14.
Re: v1.5.15rc1 Bug Reports and Comments
Posted: Mon Oct 30, 2023 11:43 am
by Dave
Actually, you will note the far right ramp starts with higher memory available then the previous two ramps.....memory usage will grow with use, but new code should limit that...would be good to see it further on..
but in the meantime can you share below:
- switch model
- your switch configuration
- which oids you are querying on snmp
- share /var/log/messages and your snmp log.