My gut kind of thought that the problem described in viewtopic.php?p=33160#p33160 was what we were experiencing. We rely on RSTP, so disabling it isn't an option. But the observation that this is a new problem in 1.5.5 and 1.5.6 led me to downgrade. I suppose I could try upgrading to 1.5.4 and see if the problem comes back. Then upgrade to 1.5.5 and see if the problem comes back, and so on and so forth to confirm which version has the code change causing our problem.
Storing at some of the logs in a permanent place would be most helpful in knowing what the switch was "thinking" before it crashed/blocked ports/became inaccessible.
Dave
v1.5.6 Bug Reports and Comments
-
david.sovereen@mercury.net - Member
- Posts: 33
- Joined: Tue Sep 29, 2015 6:17 pm
- Location: Midland, MI
- Has thanked: 0 time
- Been thanked: 2 times
-
Stephen - Employee
- Posts: 1057
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 90 times
- Been thanked: 192 times
Re: v1.5.6 Bug Reports and Comments
If your situation is the same as mayheart's then your best option would be to try and use MSTP as we concluded that for mayheart the problem was being caused because RSTP is not VLAN aware. But if you are experiencing issue's on one firmware version and not another it must be a (potentially related) bug in the firmware itself.
Permanent logging will hopefully be available soon. In the mean time you can also use a syslog server if you don't want to wait for that feature to become available.
Permanent logging will hopefully be available soon. In the mean time you can also use a syslog server if you don't want to wait for that feature to become available.
-
JustJoe - Experienced Member
- Posts: 266
- Joined: Sat Aug 02, 2014 11:33 pm
- Has thanked: 94 times
- Been thanked: 59 times
Re: v1.5.6 Bug Reports and Comments
To be honest, I only tested this other MSTP bug:
viewtopic.php?f=17&t=6787
on v1.5.6 because that is where I started using it. But since I provided a copy of the failing config, Stephen could easily test on a previous release to see if it occurred there.
The suspicious part is that it is such a low level basic bug, I'm scratching my head why no one reported it before?
viewtopic.php?f=17&t=6787
on v1.5.6 because that is where I started using it. But since I provided a copy of the failing config, Stephen could easily test on a previous release to see if it occurred there.
The suspicious part is that it is such a low level basic bug, I'm scratching my head why no one reported it before?
-
tpnorris@velocityonline.net - Member
- Posts: 2
- Joined: Tue Oct 27, 2015 12:14 pm
- Location: Tallahassee, FL
- Has thanked: 0 time
- Been thanked: 0 time
Re: v1.5.6 Bug Reports and Comments
Hi all, we have a few ws-12-250A switches in the field. All are hidden from the world so we never upgraded firmware due to everything working well. I have two I need to upgrade, one is on 1.3.1, one is on 1.5.0. Can I upgrade from these to 1.5.6 or do I need to upgrade to a different version before going to 1.5.6?
Thanks in advance.
Thanks in advance.
-
Stephen - Employee
- Posts: 1057
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 90 times
- Been thanked: 192 times
Re: v1.5.6 Bug Reports and Comments
In this case I would highly recommend first backing up the config for both switches. Then download 1.3.1 and 1.5.0 firmware from here:
firmware/archive/
Then take both of those switches out of production and then proceed to upgrade them to 1.5.6, test them in the lab before putting them back into production.
If you're upgrade is successful the old configs will no longer be relevant so you will need to rebuild it from the CLI of web UI before putting it back in operation.
But if it fails, you can put them back on their original firmware versions and just apply the old config.
Upgrading 1.5.0 to 1.5.6 will likely be OK. I believe I've seen older upgrades succeed.
But I've never heard of someone upgrading from 1.3.1 so I very highly recommend following that procedure for at least that switch.
firmware/archive/
Then take both of those switches out of production and then proceed to upgrade them to 1.5.6, test them in the lab before putting them back into production.
If you're upgrade is successful the old configs will no longer be relevant so you will need to rebuild it from the CLI of web UI before putting it back in operation.
But if it fails, you can put them back on their original firmware versions and just apply the old config.
Upgrading 1.5.0 to 1.5.6 will likely be OK. I believe I've seen older upgrades succeed.
But I've never heard of someone upgrading from 1.3.1 so I very highly recommend following that procedure for at least that switch.
-
tpnorris@velocityonline.net - Member
- Posts: 2
- Joined: Tue Oct 27, 2015 12:14 pm
- Location: Tallahassee, FL
- Has thanked: 0 time
- Been thanked: 0 time
- coreinput
- Member
- Posts: 17
- Joined: Tue Dec 27, 2016 1:59 pm
- Has thanked: 2 times
- Been thanked: 14 times
Re: v1.5.6 Bug Reports and Comments
Upgraded from 1.5.5 running since February 2020 and everything went smooth (and no POE loss). Hats off to the team including beta testers for making this release happen. Thanks!
-
mayheart - Experienced Member
- Posts: 177
- Joined: Thu Jan 15, 2015 1:42 pm
- Location: Canada
- Has thanked: 44 times
- Been thanked: 49 times
Re: v1.5.6 Bug Reports and Comments
Hey Stephen,
I had one site where we lost management access only to the Netonix, the unit was power cycled then it would drop packets every 8 pings. Disabling spanning tree completely fixed it. Re-enabling spanning tree causes the packet loss and these system logs to return.
Port 4 is a wireless uplink to another tower which connects to a Cisco router
port 7 is a end client with only one device plugged in
port 10 is a UPS.
I had one site where we lost management access only to the Netonix, the unit was power cycled then it would drop packets every 8 pings. Disabling spanning tree completely fixed it. Re-enabling spanning tree causes the packet loss and these system logs to return.
Port 4 is a wireless uplink to another tower which connects to a Cisco router
port 7 is a end client with only one device plugged in
port 10 is a UPS.
- Code: Select all
Mar 5 12:54:06 monitor: restarting vtss_appl
Mar 5 12:54:07 STP: msti 0 set port 4 to discarding
Mar 5 12:54:07 STP: msti 0 set port 7 to discarding
Mar 5 12:54:07 STP: msti 0 set port 10 to discarding
Mar 5 12:54:10 STP: msti 0 set port 10 to learning
Mar 5 12:54:10 STP: msti 0 set port 10 to forwarding
Mar 5 12:54:10 STP: msti 0 set port 7 to learning
Mar 5 12:54:10 STP: msti 0 set port 7 to forwarding
Mar 5 12:54:10 STP: msti 0 set port 4 to learning
Mar 5 12:54:10 STP: msti 0 set port 4 to forwarding
Mar 5 12:54:20 monitor: restarting vtss_appl
Mar 5 12:54:21 STP: msti 0 set port 4 to discarding
Mar 5 12:54:21 STP: msti 0 set port 7 to discarding
Mar 5 12:54:21 STP: msti 0 set port 10 to discarding
Mar 5 12:54:24 STP: msti 0 set port 10 to learning
Mar 5 12:54:24 STP: msti 0 set port 10 to forwarding
Mar 5 12:54:24 STP: msti 0 set port 7 to learning
Mar 5 12:54:24 STP: msti 0 set port 7 to forwarding
Mar 5 12:54:24 STP: msti 0 set port 4 to learning
Mar 5 12:54:24 STP: msti 0 set port 4 to forwarding
Mar 5 12:54:33 monitor: restarting vtss_appl
Mar 5 12:54:34 STP: msti 0 set port 4 to discarding
Mar 5 12:54:34 STP: msti 0 set port 7 to discarding
Mar 5 12:54:34 STP: msti 0 set port 10 to discarding
Mar 5 12:54:37 STP: msti 0 set port 10 to learning
Mar 5 12:54:37 STP: msti 0 set port 10 to forwarding
Mar 5 12:54:37 STP: msti 0 set port 7 to learning
Mar 5 12:54:37 STP: msti 0 set port 7 to forwarding
Mar 5 12:54:37 STP: msti 0 set port 4 to learning
Mar 5 12:54:37 STP: msti 0 set port 4 to forwarding
Mar 5 12:54:47 monitor: restarting vtss_appl
Mar 5 12:54:48 STP: msti 0 set port 4 to discarding
Mar 5 12:54:48 STP: msti 0 set port 7 to discarding
Mar 5 12:54:48 STP: msti 0 set port 10 to discarding
Mar 5 12:54:51 STP: msti 0 set port 10 to learning
Mar 5 12:54:51 STP: msti 0 set port 10 to forwarding
Mar 5 12:54:51 STP: msti 0 set port 7 to learning
Mar 5 12:54:51 STP: msti 0 set port 7 to forwarding
Mar 5 12:54:51 STP: msti 0 set port 4 to learning
Mar 5 12:54:51 STP: msti 0 set port 4 to forwarding
Mar 5 12:55:01 monitor: restarting vtss_appl
Mar 5 12:55:01 STP: msti 0 set port 4 to discarding
Mar 5 12:55:01 STP: msti 0 set port 7 to discarding
Mar 5 12:55:01 STP: msti 0 set port 10 to discarding
Mar 5 12:55:04 STP: msti 0 set port 10 to learning
Mar 5 12:55:04 STP: msti 0 set port 10 to forwarding
Mar 5 12:55:04 STP: msti 0 set port 7 to learning
Mar 5 12:55:04 STP: msti 0 set port 7 to forwarding
Mar 5 12:55:04 STP: msti 0 set port 4 to learning
Mar 5 12:55:04 STP: msti 0 set port 4 to forwarding
Mar 5 12:55:14 monitor: restarting vtss_appl
Mar 5 12:55:15 STP: msti 0 set port 4 to discarding
Mar 5 12:55:15 STP: msti 0 set port 7 to discarding
Mar 5 12:55:15 STP: msti 0 set port 10 to discarding
Mar 5 12:55:18 STP: msti 0 set port 10 to learning
Mar 5 12:55:18 STP: msti 0 set port 10 to forwarding
Mar 5 12:55:18 STP: msti 0 set port 7 to learning
Mar 5 12:55:18 STP: msti 0 set port 7 to forwarding
Mar 5 12:55:18 STP: msti 0 set port 4 to learning
Mar 5 12:55:18 STP: msti 0 set port 4 to forwarding
Mar 5 12:55:28 monitor: restarting vtss_appl
Mar 5 12:55:28 STP: msti 0 set port 4 to discarding
Mar 5 12:55:28 STP: msti 0 set port 7 to discarding
Mar 5 12:55:28 STP: msti 0 set port 10 to discarding
Mar 5 12:55:31 STP: msti 0 set port 10 to learning
Mar 5 12:55:31 STP: msti 0 set port 10 to forwarding
Mar 5 12:55:31 STP: msti 0 set port 7 to learning
Mar 5 12:55:31 STP: msti 0 set port 7 to forwarding
Mar 5 12:55:31 STP: msti 0 set port 4 to learning
Mar 5 12:55:31 STP: msti 0 set port 4 to forwarding
Mar 5 12:55:41 monitor: restarting vtss_appl
Mar 5 12:55:42 STP: msti 0 set port 4 to discarding
Mar 5 12:55:42 STP: msti 0 set port 7 to discarding
Mar 5 12:55:42 STP: msti 0 set port 10 to discarding
Mar 5 12:55:45 STP: msti 0 set port 10 to learning
Mar 5 12:55:45 STP: msti 0 set port 10 to forwarding
Mar 5 12:55:45 STP: msti 0 set port 7 to learning
Mar 5 12:55:45 STP: msti 0 set port 7 to forwarding
Mar 5 12:55:45 STP: msti 0 set port 4 to learning
Mar 5 12:55:45 STP: msti 0 set port 4 to forwarding
Mar 5 12:55:55 monitor: restarting vtss_appl
Mar 5 12:55:56 STP: msti 0 set port 4 to discarding
Mar 5 12:55:56 STP: msti 0 set port 7 to discarding
Mar 5 12:55:56 STP: msti 0 set port 10 to discarding
Mar 5 12:55:58 STP: msti 0 set port 10 to learning
Mar 5 12:55:58 STP: msti 0 set port 10 to forwarding
Mar 5 12:55:58 STP: msti 0 set port 7 to learning
Mar 5 12:55:58 STP: msti 0 set port 7 to forwarding
Mar 5 12:55:58 STP: msti 0 set port 4 to learning
Mar 5 12:55:58 STP: msti 0 set port 4 to forwarding
Mar 5 12:56:08 monitor: restarting vtss_appl
Mar 5 12:56:09 STP: msti 0 set port 4 to discarding
Mar 5 12:56:09 STP: msti 0 set port 7 to discarding
Mar 5 12:56:09 STP: msti 0 set port 10 to discarding
Mar 5 12:56:12 STP: msti 0 set port 10 to learning
Mar 5 12:56:12 STP: msti 0 set port 10 to forwarding
Mar 5 12:56:12 STP: msti 0 set port 7 to learning
Mar 5 12:56:12 STP: msti 0 set port 7 to forwarding
Mar 5 12:56:12 STP: msti 0 set port 4 to learning
Mar 5 12:56:12 STP: msti 0 set port 4 to forwarding
Mar 5 12:56:22 monitor: restarting vtss_appl
Mar 5 12:56:23 STP: msti 0 set port 4 to discarding
Mar 5 12:56:23 STP: msti 0 set port 7 to discarding
Mar 5 12:56:23 STP: msti 0 set port 10 to discarding
Mar 5 12:56:26 STP: msti 0 set port 10 to learning
Mar 5 12:56:26 STP: msti 0 set port 10 to forwarding
Mar 5 12:56:26 STP: msti 0 set port 7 to learning
Mar 5 12:56:26 STP: msti 0 set port 7 to forwarding
Mar 5 12:56:26 STP: msti 0 set port 4 to learning
Mar 5 12:56:26 STP: msti 0 set port 4 to forwarding
Mar 5 12:56:36 monitor: restarting vtss_appl
Mar 5 12:56:36 STP: msti 0 set port 4 to discarding
Mar 5 12:56:36 STP: msti 0 set port 7 to discarding
Mar 5 12:56:36 STP: msti 0 set port 10 to discarding
Mar 5 12:56:39 STP: msti 0 set port 10 to learning
Mar 5 12:56:39 STP: msti 0 set port 10 to forwarding
Mar 5 12:56:39 STP: msti 0 set port 7 to learning
Mar 5 12:56:39 STP: msti 0 set port 7 to forwarding
Mar 5 12:56:39 STP: msti 0 set port 4 to learning
Mar 5 12:56:39 STP: msti 0 set port 4 to forwarding
Mar 5 12:56:49 monitor: restarting vtss_appl
Mar 5 12:56:50 STP: msti 0 set port 4 to discarding
Mar 5 12:56:50 STP: msti 0 set port 7 to discarding
Mar 5 12:56:50 STP: msti 0 set port 10 to discarding
Mar 5 12:56:53 STP: msti 0 set port 10 to learning
Mar 5 12:56:53 STP: msti 0 set port 10 to forwarding
Mar 5 12:56:53 STP: msti 0 set port 7 to learning
Mar 5 12:56:53 STP: msti 0 set port 7 to forwarding
Mar 5 12:56:53 STP: msti 0 set port 4 to learning
Mar 5 12:56:53 STP: msti 0 set port 4 to forwarding
Mar 5 12:57:03 monitor: restarting vtss_appl
Mar 5 12:57:03 STP: msti 0 set port 4 to discarding
Mar 5 12:57:03 STP: msti 0 set port 7 to discarding
Mar 5 12:57:03 STP: msti 0 set port 10 to discarding
Mar 5 12:57:06 STP: msti 0 set port 10 to learning
Mar 5 12:57:06 STP: msti 0 set port 10 to forwarding
Mar 5 12:57:06 STP: msti 0 set port 7 to learning
Mar 5 12:57:06 STP: msti 0 set port 7 to forwarding
Mar 5 12:57:06 STP: msti 0 set port 4 to learning
Mar 5 12:57:06 STP: msti 0 set port 4 to forwarding
Mar 5 12:57:16 monitor: restarting vtss_appl
Mar 5 12:57:17 STP: msti 0 set port 4 to discarding
Mar 5 12:57:17 STP: msti 0 set port 7 to discarding
Mar 5 12:57:17 STP: msti 0 set port 10 to discarding
Mar 5 12:57:20 STP: msti 0 set port 10 to learning
Mar 5 12:57:20 STP: msti 0 set port 10 to forwarding
Mar 5 12:57:20 STP: msti 0 set port 7 to learning
Mar 5 12:57:20 STP: msti 0 set port 7 to forwarding
Mar 5 12:57:20 STP: msti 0 set port 4 to learning
Mar 5 12:57:20 STP: msti 0 set port 4 to forwarding
Mar 5 12:57:30 monitor: restarting vtss_appl
Mar 5 12:57:30 STP: msti 0 set port 4 to discarding
Mar 5 12:57:30 STP: msti 0 set port 7 to discarding
Mar 5 12:57:31 STP: msti 0 set port 10 to discarding
Mar 5 12:57:33 STP: msti 0 set port 10 to learning
Mar 5 12:57:33 STP: msti 0 set port 10 to forwarding
Mar 5 12:57:33 STP: msti 0 set port 7 to learning
Mar 5 12:57:33 STP: msti 0 set port 7 to forwarding
Mar 5 12:57:33 STP: msti 0 set port 4 to learning
Mar 5 12:57:33 STP: msti 0 set port 4 to forwarding
Mar 5 12:57:43 monitor: restarting vtss_appl
Mar 5 12:57:44 STP: msti 0 set port 4 to discarding
Mar 5 12:57:44 STP: msti 0 set port 7 to discarding
Mar 5 12:57:44 STP: msti 0 set port 10 to discarding
Mar 5 12:57:47 STP: msti 0 set port 10 to learning
Mar 5 12:57:47 STP: msti 0 set port 10 to forwarding
Mar 5 12:57:47 STP: msti 0 set port 7 to learning
Mar 5 12:57:47 STP: msti 0 set port 7 to forwarding
Mar 5 12:57:47 STP: msti 0 set port 4 to learning
Mar 5 12:57:47 STP: msti 0 set port 4 to forwarding
etc...
-
Stephen - Employee
- Posts: 1057
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 90 times
- Been thanked: 192 times
Re: v1.5.6 Bug Reports and Comments
Hey mayheart, do you mind sharing the Status, Ports, VLAN and Device->Config tabs?
Who is online
Users browsing this forum: No registered users and 11 guests