Netonix MSTP fail

DOWNLOAD THE LATEST FIRMWARE HERE
maturrin
Member
 
Posts: 12
Joined: Thu Jul 11, 2019 12:32 pm
Has thanked: 0 time
Been thanked: 0 time

Netonix MSTP fail

Thu Aug 08, 2019 2:50 pm

Netonix MSTP failTwo Netonix model WS-12-250-DC with, 1.5.3 firmware are used in the laboratory


Netonix-R20 Netonix-R35

MSTP - Enable Name:R3 Revision:3 MSTP - Enable Name:R3 Revision:3

Priority:32768 Priority:28672
Bridge ID:32768-EC-13-B2-82-65-0E Bridge ID: ID:28672-EC-13-B2-83-1A-12
Root Bridge ID:28672-EC-13-B2-83-1A-12 Root Bridge ID:28672-EC-13-B2-83-1A-12

E1------------ Vlan1 ---PC ---- 172.20.20.1/24 E1---------Vlan1--PC----172.20.35.2/24
Vlan3410 ------ 192.168.10.2/24 Vlan3410 ----192.168.10.1/24
Vlan3411--------192.168.11.2/24 Vlan3411-----192.168.11.1/24

E2-------------------------------------------------------------------------------------------------------E2
Vlan3410 - MST-Instance1-Root Vlan3410 - MST-Instance1-Designated
Vlan3411 - MST-Instance2-Alternate Vlan3411 - MST-Instance2-Designated


E3-------------------------------------------------------------------------------------------------------E3
Vlan3410 - MST-Instance1-Alternate Vlan3410 - MST-Instance1-Designated
Vlan3411 - MST-Instance2-Root Vlan3411 - MST-Instance2-Designated



- Under normal operating conditions, traffic from the Vlan3410 flows through E2 between both Netonix devices.
Example: Ping from 192.168.10.1 to 192.168.10.2

- Under conditions of connection failure in E2, traffic from the Vlan3410 flows through E3 between both Netonix devices.
Example: Ping from 192.168.10.1 to 192.168.10.2

- Under normal operating conditions, traffic from the Vlan3411 flows through E3 between both Netonix devices.
Example: Ping from 192.168.11.1 to 192.168.11.2

- Under conditions of connection failure in E3, traffic from Vlan3411 flows through E2 between both Netonix devices.
Example: Ping from 192.168.11.1 to 192.168.11.2


Fail A:
- Under normal conditions, traffic from 192.168.10.1 to 192.168.10.2 flows through E2.

- Action: Break the connection between E3, wait 1 second, then resume the connection between E3.

- Failure: Traffic between 192.168.10.1 and 192.168.10.2 stops flowing.



Failure B:
- Under normal conditions, traffic from 192.168.11.1 to 192.168.11.2 flows through E3.

- Action: Break the connection between E2, wait 1 second, then resume the connection between E2.

- Failure: Traffic between 192.168.11.1 and 192.168.11.2 stops flowing.




Image




Image




Image





Image




Image




Image




Image




Image




Image




Image

User avatar
Stephen
Employee
Employee
 
Posts: 1033
Joined: Sun Dec 24, 2017 8:56 pm
Has thanked: 85 times
Been thanked: 181 times

Re: Netonix MSTP fail

Thu Aug 08, 2019 6:22 pm

Thank you for the thorough description.

[quote="maturrin"]
- Action: Break the connection between E3, wait 1 second, then resume the connection between E3.
...
- Action: Break the connection between E2, wait 1 second, then resume the connection between E2.
[/quote]

If you are still setup to do this. Could you clear the logs on the switches and then perform these action's again and post the log results here? That should give us an idea of what is going on with the STP state machines on each of the relevant VLANs.

maturrin
Member
 
Posts: 12
Joined: Thu Jul 11, 2019 12:32 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Netonix MSTP fail

Fri Aug 09, 2019 5:57 pm

Netonix-R20

Dec 31 19:28:45 syslogd started: BusyBox v1.19.4
Dec 31 19:28:45 UI: Log cleared by admin (::ffff:172.20.20.250)
Dec 31 19:29:11 Port: link state changed to 'down' on port 3
Dec 31 19:29:11 STP: MSTI2: New root on port 2, root path cost is 0, root bridge id is 0.00-00-00-00-00-00
Dec 31 19:29:11 STP: msti 2 set port 3 to discarding
Dec 31 19:29:11 STP: msti 2 set port 2 to learning
Dec 31 19:29:11 STP: msti 2 set port 2 to forwarding
Dec 31 19:29:13 Port: link state changed to 'up' (100M-F) on port 3
Dec 31 19:29:13 STP: msti 0 set port 3 to discarding
Dec 31 19:29:13 STP: msti 1 set port 3 to discarding
Dec 31 19:29:13 STP: msti 2 set port 3 to discarding
Dec 31 19:29:13 STP: MSTI2: New root on port 3, root path cost is 0, root bridge id is 0.00-00-00-00-00-00
Dec 31 19:29:13 STP: msti 2 set port 2 to discarding
Dec 31 19:29:13 STP: msti 2 set port 3 to learning
Dec 31 19:29:13 STP: msti 2 set port 3 to forwarding
Dec 31 19:29:32 Port: link state changed to 'down' on port 2
Dec 31 19:29:32 STP: MSTI0: New root on port 3, root path cost is 0, root bridge id is 28672.EC-13-B2-83-1A-12
Dec 31 19:29:32 STP: msti 0 set port 2 to discarding
Dec 31 19:29:32 STP: MSTI1: New root on port 3, root path cost is 0, root bridge id is 0.00-00-00-00-00-00
Dec 31 19:29:32 STP: msti 1 set port 2 to discarding
Dec 31 19:29:32 STP: msti 0 set port 3 to learning
Dec 31 19:29:32 STP: msti 0 set port 3 to forwarding
Dec 31 19:29:32 STP: msti 1 set port 3 to learning
Dec 31 19:29:32 STP: msti 1 set port 3 to forwarding
Dec 31 19:29:35 Port: link state changed to 'up' (100M-F) on port 2
Dec 31 19:29:35 STP: msti 0 set port 2 to discarding
Dec 31 19:29:35 STP: msti 1 set port 2 to discarding
Dec 31 19:29:35 STP: msti 2 set port 2 to discarding
Dec 31 19:29:35 STP: MSTI0: New root on port 2, root path cost is 0, root bridge id is 28672.EC-13-B2-83-1A-12
Dec 31 19:29:35 STP: msti 0 set port 3 to discarding
Dec 31 19:29:35 STP: MSTI1: New root on port 2, root path cost is 0, root bridge id is 0.00-00-00-00-00-00
Dec 31 19:29:35 STP: msti 1 set port 3 to discarding
Dec 31 19:29:35 STP: msti 0 set port 2 to learning
Dec 31 19:29:35 STP: msti 0 set port 2 to forwarding
Dec 31 19:29:35 STP: msti 1 set port 2 to learning
Dec 31 19:29:35 STP: msti 1 set port 2 to forwarding
Copyright 2014-2019 Netonix



Netonix-R35

Dec 31 19:25:36 syslogd started: BusyBox v1.19.4
Dec 31 19:25:36 UI: Log cleared by admin (::ffff:172.20.35.250)
Dec 31 19:25:39 Port: link state changed to 'down' on port 3
Dec 31 19:25:39 STP: msti 0 set port 3 to discarding
Dec 31 19:25:39 STP: msti 1 set port 3 to discarding
Dec 31 19:25:39 STP: msti 2 set port 3 to discarding
Dec 31 19:25:43 Port: link state changed to 'up' (100M-F) on port 3
Dec 31 19:25:43 STP: msti 0 set port 3 to discarding
Dec 31 19:25:43 STP: msti 1 set port 3 to discarding
Dec 31 19:25:43 STP: msti 2 set port 3 to discarding
Dec 31 19:25:44 STP: msti 0 set port 3 to learning
Dec 31 19:25:44 STP: msti 0 set port 3 to forwarding
Dec 31 19:25:44 STP: msti 1 set port 3 to learning
Dec 31 19:25:44 STP: msti 1 set port 3 to forwarding
Dec 31 19:25:44 STP: msti 2 set port 3 to learning
Dec 31 19:25:44 STP: msti 2 set port 3 to forwarding
Dec 31 19:25:55 Port: link state changed to 'down' on port 2
Dec 31 19:25:55 STP: msti 0 set port 2 to discarding
Dec 31 19:25:55 STP: msti 1 set port 2 to discarding
Dec 31 19:25:55 STP: msti 2 set port 2 to discarding
Dec 31 19:25:59 Port: link state changed to 'up' (100M-F) on port 2
Dec 31 19:25:59 STP: msti 0 set port 2 to discarding
Dec 31 19:25:59 STP: msti 1 set port 2 to discarding
Dec 31 19:25:59 STP: msti 2 set port 2 to discarding
Dec 31 19:26:00 STP: msti 0 set port 2 to learning
Dec 31 19:26:00 STP: msti 0 set port 2 to forwarding
Dec 31 19:26:00 STP: msti 1 set port 2 to learning
Dec 31 19:26:00 STP: msti 1 set port 2 to forwarding
Dec 31 19:26:00 STP: msti 2 set port 2 to learning
Dec 31 19:26:00 STP: msti 2 set port 2 to forwarding
Copyright 2014-2019 Netonix

maturrin
Member
 
Posts: 12
Joined: Thu Jul 11, 2019 12:32 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Netonix MSTP fail

Tue Aug 13, 2019 9:02 am

Is the information useful?

Return to Hardware and software issues

Who is online

Users browsing this forum: No registered users and 70 guests