Unsolved
This post is more than 5 years old
1 Rookie
•
108 Posts
0
58519
March 8th, 2013 10:00
spanning tree protocol and isolated switch
Hi,
We have a network with two 6248s, two M6220s and four M8024s, a few PowerEdge blade/rack servers and a few EqualLogic iSCSI arrays.
There are few redundant paths in the network topology, but that shouldn't be an issue, since the switches are running by default the rapid spanning tree protocol.
But yesterday we hit an big issue.
After reloading one of the M8024s, it got completely isolated from the network!
The M8024 in question (switch-c1) is connected to another M8024 (switch-b1) and to a 6248 (switch2).
It appears that the spanning tree protocol instance on the latter two switches is blocking the ports connected to the switch in question, see the diagnostic output and the logs below.
And being isolated from the network, the switch in question is running its own spanning tree protcol instance.
Before the reload, the switch was apparently working just fine within the network.
We would expect that only one of the two switches connect to it would block the connection to it to prevent a loop in the network, but not both of them at the same time!
The switch has now been isolated from the network for more than a day, a new STP log entry is created on each of the two switches connected to it every two seconds.
It looks like the issue is not going to resolve automatically.
The 6248s are running firmware version 3.3.5.5.
The M6220s and M8024s are running firmware version 5.0.1.3.
What's wrong with our setup?
Thanks.
P.S.: The MAC addresses and the IP addresses in this message are masked.
switch2#show spanning-tree blockedports
Spanning tree Enabled (BPDU flooding : Disabled) mode rstp
CST Regional Root: 80:00:00:19:B9:11:11:11
Regional Root Path Cost: 0
###### MST 0 Vlan Mapped: 1, 10, 31-46, 150
ROOT ID
Address 00:19:B9:11:11:11
This Switch is the Root.
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec
Interfaces
Name State Prio.Nbr Cost Sts Role PortFast RestrictedPort
------ -------- --------- ---------- ---- ----- -------- -------
1/xg4 Enabled 128.52 2000 DSC Desg No No
switch2# show logging
<189> MAR 08 18:19:18 111.111.111.111-1 TRAPMGR[152561184]: traputil.c(611) 54331 %% 1/0/52 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> MAR 08 18:19:20 111.111.111.111-1 TRAPMGR[152561184]: traputil.c(611) 54332 %% 1/0/52 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> MAR 08 18:19:22 111.111.111.111-1 TRAPMGR[152561184]: traputil.c(611) 54333 %% 1/0/52 is transitioned from the Forwarding state to the Blocking state in instance 0
switch-b1#show spanning-tree blockedports
Spanning tree Enabled (BPDU flooding : Disabled) mode rstp
CST Regional Root: 80:00:A4:BA:DB:22:22:22
Regional Root Path Cost: 0
###### MST 0 Vlan Mapped: 1, 10, 31-45, 150
ROOT ID
Priority 32768
Address 0019.B911.1111
Path Cost 3000
Root Port Te1/1/4
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec
Bridge ID
Priority 32768
Address A4BA.DB22.2222
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec
Interfaces
Name State Prio.Nbr Cost Sts Role RestrictedPort
------ -------- --------- --------- ---- ----- --------------
Te1/1/3 Enabled 128.19 2000 DSC Desg No
switch-b1#show logging
<189> MAR 08 18:08:11 222.222.222.222-1 TRAPMGR[199127520]: traputil.c(637) 57162 %% Te1/1/3 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> MAR 08 18:08:09 222.222.222.222-1 TRAPMGR[199127520]: traputil.c(637) 57161 %% Te1/1/3 is transitioned from the Forwarding state to the Blocking state in instance 0
<189> MAR 08 18:08:07 222.222.222.222-1 TRAPMGR[199127520]: traputil.c(637) 57160 %% Te1/1/3 is transitioned from the Forwarding state to the Blocking state in instance 0
switch-c1#show spanning-tree blockedports
Spanning tree Enabled (BPDU flooding : Disabled) mode rstp
CST Regional Root: 80:00:5C:26:0A:33:33:33
Regional Root Path Cost: 0
###### MST 0 Vlan Mapped: 1, 10, 31-45, 150
ROOT ID
Priority 32768
Address 5C26.0A33.3333
This Switch is the Root.
Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec
Interfaces
Name State Prio.Nbr Cost Sts Role RestrictedPort
------ -------- --------- --------- ---- ----- --------------
pzero
1 Rookie
•
108 Posts
0
March 24th, 2013 14:00
Also, it shouldn't matter if you are using either general mode or trunk mode, as long as you have the two connected ports in the same mode (which we have), since VLAN 1 should pass over the connection anyway, respectively tagged or untagged, without problems.
Thanks.
DELL-Willy M
802 Posts
0
March 25th, 2013 18:00
The different switch models have different firmware levels. Based on that the switchport modes can have slightly different behavior. Theoretically you are correct about having the same modes on both ends and it should pass VLAN 1.
Because of the behavior of the spanning tree protocol in this instance we are wanting to set a trunk on the 8024 models to see it we can get the best response.
If you feel that it is a firmware issue that is the cause. You do have the option to call in a get the scenario documented and then submitted for firmware revision.
The documentation for the M8024 states:
Trunk — Trunk-mode ports are intended for switch-to-switch links. Trunk ports can receive both tagged and untagged packets. Tagged packets received on a trunk port are forwarded on the VLAN contained in the tag. Untagged packets received on a trunk port are forwarded on the native VLAN. Packets received on another interface belonging to the native
VLAN are transmitted untagged on a trunk port.
pzero
1 Rookie
•
108 Posts
0
March 26th, 2013 13:00
Hi Willy,
As per your request, we've configured port Te1/1/3 on switch-b1 and the same port on switch-c1 to use trunk mode, now the only configuration for that ports is the following:
interface Te1/1/3
mtu 9216
switchport mode trunk
exit
But switch-c1 is still isolated from the network.
Also, the received BPDUs are still 0.
Please see below the details for the interfaces in question.
What can we do next?
Thanks.
switch-b1#show interfaces detail Te1/1/3
Port Name Duplex Speed Neg MTU Admin Link
State State
--------- --------------------------- ------ ------- ---- ----- ----- -----
Te1/1/3 Full 10000 Off 9216 Up Up
Port Description
-------- ----------------------------------------------------------------------
Te1/1/3
Flow Control:Enabled
Port: Te1/1/3
VLAN Membership mode:Trunk Mode
Operating parameters:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Default Priority: 0
GVRP status:Disabled
Protected:Disabled
Port Te1/1/3 is member in:
VLAN Name Egress rule Type
---- --------------------------------- ----------- --------
1 default Untagged Default
10 VLAN0010 Tagged Static
31 VLAN0031 Tagged Static
32 VLAN0032 Tagged Static
33 VLAN0033 Tagged Static
34 VLAN0034 Tagged Static
35 VLAN0035 Tagged Static
36 VLAN0036 Tagged Static
37 VLAN0037 Tagged Static
38 VLAN0038 Tagged Static
39 VLAN0039 Tagged Static
40 VLAN0040 Tagged Static
41 VLAN0041 Tagged Static
42 VLAN0042 Tagged Static
43 VLAN0043 Tagged Static
44 VLAN0044 Tagged Static
45 VLAN0045 Tagged Static
150 VLAN0150 Tagged Static
Static configuration:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Port Te1/1/3 is statically configured to:
VLAN Name Egress rule
---- --------------------------------- -----------
10 VLAN0010 Tagged
31 VLAN0031 Tagged
32 VLAN0032 Tagged
33 VLAN0033 Tagged
34 VLAN0034 Tagged
35 VLAN0035 Tagged
36 VLAN0036 Tagged
37 VLAN0037 Tagged
38 VLAN0038 Tagged
39 VLAN0039 Tagged
40 VLAN0040 Tagged
41 VLAN0041 Tagged
42 VLAN0042 Tagged
43 VLAN0043 Tagged
44 VLAN0044 Tagged
45 VLAN0045 Tagged
150 VLAN0150 Tagged
Forbidden VLANS:
VLAN Name
---- ---------------------------------
Port Te1/1/3 Enabled
State: Discarding Role: Designated
Port id: 128.19 Port Cost: 2000
Port Fast: No (Configured: no ) Root Protection: No
Designated bridge Priority: 32768 Address: A4BA.DB22.2222
Designated port id: 128.19 Designated path cost: 3000
CST Regional Root: 80:00:A4:BA:DB:22:22:22 CST Port Cost: 0
BPDU: sent 827790, received 82777
switch-c1#show interfaces detail Te1/1/3
Port Name Duplex Speed Neg MTU Admin Link
State State
--------- --------------------------- ------ ------- ---- ----- ----- -----
Te1/1/3 Full 10000 Off 9216 Up Up
Port Description
-------- ----------------------------------------------------------------------
Te1/1/3
Flow Control:Enabled
Port: Te1/1/3
VLAN Membership mode:Trunk Mode
Operating parameters:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Default Priority: 0
GVRP status:Disabled
Protected:Disabled
Port Te1/1/3 is member in:
VLAN Name Egress rule Type
---- --------------------------------- ----------- --------
1 default Untagged Default
10 VLAN0010 Tagged Static
31 VLAN0031 Tagged Static
32 VLAN0032 Tagged Static
33 VLAN0033 Tagged Static
34 VLAN0034 Tagged Static
35 VLAN0035 Tagged Static
36 VLAN0036 Tagged Static
37 VLAN0037 Tagged Static
38 VLAN0038 Tagged Static
39 VLAN0039 Tagged Static
40 VLAN0040 Tagged Static
41 VLAN0041 Tagged Static
42 VLAN0042 Tagged Static
43 VLAN0043 Tagged Static
44 VLAN0044 Tagged Static
45 VLAN0045 Tagged Static
150 VLAN0150 Tagged Static
Static configuration:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Port Te1/1/3 is statically configured to:
VLAN Name Egress rule
---- --------------------------------- -----------
10 VLAN0010 Tagged
31 VLAN0031 Tagged
32 VLAN0032 Tagged
33 VLAN0033 Tagged
34 VLAN0034 Tagged
35 VLAN0035 Tagged
36 VLAN0036 Tagged
37 VLAN0037 Tagged
38 VLAN0038 Tagged
39 VLAN0039 Tagged
40 VLAN0040 Tagged
41 VLAN0041 Tagged
42 VLAN0042 Tagged
43 VLAN0043 Tagged
44 VLAN0044 Tagged
45 VLAN0045 Tagged
150 VLAN0150 Tagged
Forbidden VLANS:
VLAN Name
---- ---------------------------------
Port Te1/1/3 Enabled
State: Forwarding Role: Designated
Port id: 128.19 Port Cost: 2000
Port Fast: No (Configured: no ) Root Protection: No
Designated bridge Priority: 32768 Address: 5C26.0A33.3333
Designated port id: 128.19 Designated path cost: 0
CST Regional Root: 80:00:5C:26:0A:33:33:33 CST Port Cost: 0
BPDU: sent 827606, received 0
DELL-Willy M
802 Posts
1
March 27th, 2013 11:00
I sent you an email with information on how we can work together offline to get a proper resolution.
thanks