Netonix Forums

Hey there,

I've noticed this on a few switches running 1.5.9-RC1. This switch has spanning tree enabled, I've seen it happen on switches without spanning tree as well.

This is an example when I did a tag change and added a VLAN.

Code: Select all

Nov 25 16:04:39 UI: VLAN 991 PortSettings: changed from 'UEUUUUUEUUUUUUEEEEEEEEEEET' to 'UEUUUUUEUUUUEEEEEEEEEEEEET'
Nov 25 16:04:39 UI: VLANs: added 'OFFICE_MGMT'
Nov 25 16:04:49 STP: msti 0 set port 1 to discarding
Nov 25 16:04:49 STP: msti 0 set port 2 to discarding
Nov 25 16:04:49 STP: msti 0 set port 4 to discarding
Nov 25 16:04:49 STP: msti 0 set port 5 to discarding
Nov 25 16:04:49 STP: msti 0 set port 6 to discarding
Nov 25 16:04:49 STP: msti 0 set port 7 to discarding
Nov 25 16:04:49 STP: msti 0 set port 8 to discarding
Nov 25 16:04:49 STP: msti 0 set port 9 to discarding
Nov 25 16:04:49 STP: msti 0 set port 10 to discarding
Nov 25 16:04:49 STP: msti 0 set port 11 to discarding
Nov 25 16:04:49 STP: msti 0 set port 12 to discarding
Nov 25 16:04:49 STP: msti 0 set port 13 to discarding
Nov 25 16:04:49 STP: msti 0 set port 14 to discarding
Nov 25 16:04:50 STP: msti 0 set port 26 to discarding
Nov 25 16:04:52 STP: msti 0 set port 26 to learning
Nov 25 16:04:52 STP: msti 0 set port 26 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 14 to learning
Nov 25 16:04:52 STP: msti 0 set port 14 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 13 to learning
Nov 25 16:04:52 STP: msti 0 set port 13 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 12 to learning
Nov 25 16:04:52 STP: msti 0 set port 12 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 11 to learning
Nov 25 16:04:52 STP: msti 0 set port 11 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 10 to learning
Nov 25 16:04:52 STP: msti 0 set port 10 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 9 to learning
Nov 25 16:04:52 STP: msti 0 set port 9 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 8 to learning
Nov 25 16:04:52 STP: msti 0 set port 8 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 7 to learning
Nov 25 16:04:52 STP: msti 0 set port 7 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 6 to learning
Nov 25 16:04:52 STP: msti 0 set port 6 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 5 to learning
Nov 25 16:04:52 STP: msti 0 set port 5 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 4 to learning
Nov 25 16:04:52 STP: msti 0 set port 4 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 2 to learning
Nov 25 16:04:52 STP: msti 0 set port 2 to forwarding
Nov 25 16:04:52 STP: msti 0 set port 1 to learning
Nov 25 16:04:52 STP: msti 0 set port 1 to forwarding
Nov 25 16:04:56 Port: link state changed to 'down' on port 26
Nov 25 16:04:56 STP: msti 0 set port 26 to discarding
Nov 25 16:04:59 Port: link state changed to 'up' (1G) on port 26
Nov 25 16:04:59 STP: msti 0 set port 26 to discarding
Nov 25 16:05:02 STP: msti 0 set port 26 to learning
Nov 25 16:05:02 STP: msti 0 set port 26 to forwarding


Another switch with spanning-tree disabled.

Code: Select all

Nov 26 09:47:59 UI: VLAN 32 ID: changed from '32' to '1000'
Nov 26 09:48:16 Port: link state changed to 'down' on port 26
Nov 26 09:48:19 Port: link state changed to 'up' (1G) on port 26


Discovery is also disabled on all the switches.

on a 12 port unit running 1.5.9-RC1...

Code: Select all

Nov 26 12:16:03 UI: VLANs: added 'test'
Nov 26 12:16:09 Port: link state changed to 'down' on port 13
Nov 26 12:16:09 STP: msti 0 set port 13 to discarding
Nov 26 12:16:10 Port: link state changed to 'up' (1G) on port 13
Nov 26 12:16:10 STP: msti 0 set port 13 to discarding
Nov 26 12:16:12 STP: msti 0 set port 13 to learning
Nov 26 12:16:12 STP: msti 0 set port 13 to forwarding


Any update on this?

I've had to downgrade to 1.5.5 to prevent this from happening.

Bump.

Any traction on this?

Doing a vlan change and causing a temporarily network outage while the SFP bounces is pretty serve.

As my previous post, it looks something changed after 1.5.5.

And the same issue with any RSTP changes reported here. Any chance to fix at least this bug? Thanks!

We have stabilized on 1.5.5 as our stable release version for the time being -- that's how we've fixed this and many other issues.

Yeah, that was around the time I started noticing issues as well. Something changed in 1.5.6 and beyond.

mhoppes wrote:We have stabilized on 1.5.5 as our stable release version for the time being -- that's how we've fixed this and many other issues.

Can you please share what other issues you've noticed on recent versions that reverting to 1.5.5. fixed? A link to the forum post would work as well.

Cheers,

Wow I reported this almost 2 years ago...

Will this ever get fixed?