Spaning Tree MST P2p Dispute
hi
i have a pair of C3750X running IOS 15.2(1)E
they are connected over througt a WAN (Layer2 VPLS 802.1Q) connection.
the port on the Root Bridge is in a block state because there is a P2p Dispute. anyone got a clue to why this i happening
below is the port configuration, spanning tree configuration i have attached debug output from the Root Switch
Root Switch
spanning-tree mode mst
spanning-tree logging
spanning-tree extend system-id
spanning-tree mst 0 priority 4096
interface GigabitEthernet1/0/1
description ** xxxxxxx **
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 276-281
switchport mode trunk
storm-control broadcast level 2.00
2nd switch
spanning-tree mode mst
spanning-tree logging
spanning-tree extend system-id
spanning-tree mst 0 priority 28672
interface GigabitEthernet1/0/1
description ** xxxxx **
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 276-281
switchport mode trunk
Hi,
The problem can be caused by STP or EtherChannel misconfiguration, or by an uni-directional link.
1- You can check the bi-directional functionality of the link or MST configuration?
2- if you configured "vlan dot1q tag native" , remove it.
Houtan
Similar Messages
-
Spaning tree Not working On L2 Links
Hi,
I am facing problem in spaning tree over L2 links between my core switch in braanch to data centre switch, please find my network digram for your understanding,
1) we have two 4500 switches in my HO as a core there are two links are connected between them & configured as a port channel.
2) We have some server which are co locate in nearest DATA center to access that server from HO we have two L2 link between Ho & DATA center
3) but we are facing issue in spanning tree at the end of HO switch port stat is showing forwarding state in Active switch as well standby switch & in DATA center we are facing the same problem,
is there any challenges for spanning tree over L2 links?
Re
SuhasDuplicate posts. :P
Go here: https://supportforums.cisco.com/discussion/12136526/proble-spanning-tree-over-l2-inks -
Spanning Tree MST per Vlan, best practice
Hi Community.
I did the following MST Spanning Tree Config
spanning-tree mst configuration
name xxxxxxx
revision1
instance 1 vlan 1, 10-20, 25, 30
So I added every Vlan to the config which we use. But every time when I add one more vlan to the config the whole network get a little outage.
I see lots of MAC Flaps on ports with two Server links and the outage is for some seconds.
Is it a better practice to add all possible Vlans to the config. So I do the config like that:
instance 1 vlan 1-4096
What you think.
Best Regards patrickHi,
So I added every Vlan to the config which we use. But every time when I add one more vlan to the config the whole network get a little outage.
Correct, that is normal behavior with MST.
I would just add "instance 1 vlan 1-4094" this way there is no outage when you bring up a new vlan.
HTH -
Spaning Tree and StackPort Bloking
Hello
i have this issue:
On Switch Stack of six switch C2960X Spaning tree showme this errors:
with inconsistent peer vlan id 27 on StackPort2 VLAN25. (Stack6-2)
Oct 21 15:22:57.160: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0027. Port consistency restored. (Stack6-3)
Oct 21 15:22:57.824: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort3 on VLAN0035. Inconsistent peer vlan. (Stack6-3)
Oct 21 15:22:58.258: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 30 on StackPort3 VLAN29. (Stack6-3)
Oct 21 15:22:58.258: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort3 on VLAN0029. Inconsistent local vlan. (Stack6-3)
Oct 21 15:22:59.177: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0034. Port consistency restored. (Stack6-3)
Oct 21 15:23:05.741: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsisten
Stack6>t peer vlan id 203 on StackPort3 VLAN34. (Stack6-3)
Oct 21 15:23:05.741: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort3 on VLAN0203. Inconsistent peer vlan. (Stack6-3)
Oct 21 15:23:05.741: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort3 on VLAN0034. Inconsistent local vlan. (Stack6-3)
Oct 21 15:23:08.121: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0025. Port consistency restored. (Stack6-3)
Oct 21 15:23:08.121: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0013. Port consistency restored. (Stack6-3)
Oct 21 15:23:59.687: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort1 on VLAN0038. Inconsistent local vlan. (Stack6-1)
Oct 21 15:24:01.242: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0028. Port consistency restored. (Stack6-1)
Oct 21 15:24:01.256: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0026. Port consistency restored. (Stack6-1)
Oct 21 15:24:01.522: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 31 on StackPort1 VLAN37. (Stack6-1)
Oct 21 15:24:01.522: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort1 on VLAN0037. Inconsistent local vlan. (Stack6-1)
Oct 21 15:24:01.976: %SPANTREE-2-BLOCK_PVI
Oct 21 15:28:41.348: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort2 on VLAN0025. Inconsistent local vlan. (Stack6-2)
Oct 21 15:28:43.487: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort2 on VLAN0026. Inconsistent peer vlan. (Stack6-2)
Oct 21 15:28:47.444: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort2 on VLAN0037. Port consistency restored. (Stack6-2)
Oct 21 15:28:54.169: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort2 on VLAN0031. Port consistency restored. (Stack6-2)
Oct 21 15:28:55.738: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort2 on VLAN0013. Port consistency restored. (Stack6-2)
Oct 21 15:23:12.183: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 38 on StackPort3 VLAN25. (Stack6-3)
Oct 21 15:23:12.183: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort3 on VLAN0025. Inconsistent local vlan. (Stack6-3)
Oct 21 15:23:12.462: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0032. Port consistency restored. (Stack6-3)
Oct 21 15:23:15.003: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0012. Port consistency restored. (Stack6-3)
Oct 21 15:23:20.145: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 203 on StackPort3 VLAN27. (Stack6-3)
Oct 21 15:24:06.995: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0010. Port consistency restored. (Stack6-1)
Oct 21 15:24:09.701: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0034. Port consistency restored. (Stack6-1)
Oct 21 15:24:09.701: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0033. Port consistency restored. (Stack6-1)
Oct 21 15:24:13.958: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort1 on VLAN0010. Inconsistent peer vlan. (Stack6-1)
Oct 21 15:24:15.059: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0035. Port consistency restored. (Stack6-1)
Oct 21 15:28:59.216: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort2 on VLAN0033. Port consistency restored. (Stack6-2)
Oct 21 15:28:59.807: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 13 on StackPort2 VLAN203. (Stack6-2)
Oct 21 15:28:59.807: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort2 on VLAN0013. Inconsistent peer vlan. (Stack6-2)
Oct 21 15:28:59.807: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort2 on VLAN0203. Inconsistent local vlan. (Stack6-2)
Oct 21 15:29:00.209: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 38 on StackPort2 VLAN31. (Stack6-2)
Oct 21 15:29:00.209: %SPANTREE-2-BLOCK_PVI
Oct 21 15:23:20.145: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort3 on VLAN0027. Inconsistent local vlan. (Stack6-3)
Oct 21 15:23:20.218: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0030. Port consistency restored. (Stack6-3)
Oct 21 15:23:22.861: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0026. Port consistency restored. (Stack6-3)
Oct 21 15:23:23.147: %SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on StackPort3 VLAN11. (Stack6-3)
Oct 21 15:23:24.500: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0016. Port consistency restored. (Stack6-3)
Oct 21 15:23:24.843: %SPANTREE-2-BLOCK_PVID_PEER: B
Oct 21 15:23:25.161: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 203 on StackPort3 VLAN13. (Stack6-3)
Oct 21 15:23:25.161: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort3 on VLAN0013. Inconsistent local vlan. (Stack6-3)
Oct 21 15:23:26.859: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0035. Port consistency restored. (Stack6-3)
Oct 21 15:23:27.282: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort3 on VLAN0029. Port consistency restored. (Stack6-3)
Oct 21 15:23:27.859: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 203 on StackPort3 VLAN35. (Stack6-3)
Oct 21 15:24:16.740: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 32 on StackPort1 VLAN33. (Stack6-1)
Oct 21 15:24:16.740: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort1 on VLAN0032. Inconsistent peer vlan. (Stack6-1)
Oct 21 15:24:16.740: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort1 on VLAN0033. Inconsistent local vlan. (Stack6-1)
Oct 21 15:24:16.751: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort1 on VLAN0034. Inconsistent peer vlan. (Stack6-1)
Oct 21 15:24:16.978: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0030. Port consistency restored. (Stack6-1)
Oct 21 15:24:26.502: %SPANTREE-2-RECV_PVID_ERR: Receiv
Oct 21 15:24:26.502: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort1 on VLAN0028. Inconsistent peer vlan. (Stack6-1)
Oct 21 15:24:26.502: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort1 on VLAN0011. Inconsistent local vlan. (Stack6-1)
Oct 21 15:24:26.712: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0038. Port consistency restored. (Stack6-1)
Oct 21 15:24:28.960: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0010. Port consistency restored. (Stack6-1)
Oct 21 15:24:28.960: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort1 on VLAN0026. Port consistency restored. (Stack6-1)
Oct 21 15:29:00.230: %SPANTREE-2-BLOCK_PVID_PEER: Blocking StackPort2 on VLAN0033. Inconsistent peer vlan. (Stack6-2)
Oct 21 15:29:07.517: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort2 on VLAN0030. Port consistency restored. (Stack6-2)
Oct 21 15:29:07.591: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 31 on StackPort2 VLAN37. (Stack6-2)
Oct 21 15:29:07.591: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking StackPort2 on VLAN0037. Inconsistent local vlan. (Stack6-2)
Oct 21 15:29:09.527: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking StackPort2
Of course, i lost stack connection
RegardsDuplicate post.
Go HERE. -
Why does the command "spanning-tree mst simulate pvst disable" exist
That's all really. Why would you turn it off? What is the advantage. If you're not receiving PVST BPDUs, you don't need it, but why turn it off?
When you use the spanning-tree mst simulate pvst disable command, specified MST interfaces that receive a Rapid PVST+ (SSTP) bridge protocol data unit (BPDU) move into the STP blocking state. Those interfaces remain in the inconsistent state until the port stops receiving Rapid PVST+ BPDUs, and then the port resumes the normal STP transition process.
OK, that's what it does, but why? the only effect it has is blocking your ports. -
Hi,
we have the following configuration on our switches
spanning-tree mode mst
spanning-tree extend system-id
spanning-tree mst configuration
name test
spanning-tree mst forward-time 4
when we have a failover convergence time was about 8-10 seconds outage is there anything on the above config that suggest's this could be causing the delay? i thought MST was fast convergence times?
Thanksi will try and you this later on. Not sure it was already in place what are the difference's between them both i thought MST can have multiple vlans per region so better design. Is RSTP not the same as PVST? not done much spanning tree as of yet. so not had chance to look at the differences?
Thanks -
Nexus 4001i and MST tons of log errors
Went looking through my Nexus 4001i logs today, and started noticing a bunch of STP role and port change messages:
2013 Jul 5 14:40:31 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/1 instance MST0000 role changed to designated
2013 Jul 5 14:40:31 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port port-channel2 instance MST0000 role changed to alternate
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port port-channel1 instance MST0000 role changed to root
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/14 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/14 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/13 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/13 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/12 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/12 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/11 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/11 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/10 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/10 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/9 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/9 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/8 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/8 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/7 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/7 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/6 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/6 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/5 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/5 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/4 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/4 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/3 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/3 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/2 removed as MST Boundary port
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-PORT_ROLE: Port Ethernet1/2 instance MST0000 role changed to designated
2013 Jul 5 14:40:32 N4k-SLOT7-SW1 %STP-6-MST_PORT_BOUNDARY: Port Ethernet1/1 removed as MST Boundary port
After going through a variety of configuration validations, spanning-tree root and priority validations as well as making sure the instances and revisions between the various MST speaking switches (all of the Nexus gear including Nexus 5596 which are vPC peers, 4001i's which connect via vPC's to the 5596's, and Catalyst 3110X's which also use MST, but only have one uplink at this time to the 5596's not in a vPC setup).
None of the other devices appear to be experiencing this problem.
I am quite confused as to what is going on, and cannot figure out why the 4001i is wigging out like this.
A quick output of MST::
N4k-SLOT7-SW1# show spanning-tree mst
##### MST0 vlans mapped: 801-3109,3111-4094
Bridge address 6073.5c8d.7e82 priority 24576 (24576 sysid 0)
Root address 0023.04ee.be03 priority 16384 (16384 sysid 0)
port Po1 path cost 0
Regional Root address 0023.04ee.be03 priority 16384 (16384 sysid 0)
internal cost 500 rem hops 19
Operational hello time 2 , forward delay 15, max age 20, txholdcount 6
Configured hello time 2 , forward delay 15, max age 20, max hops 20
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 32.4096 P2p
Po2 Altn BLK 1000 64.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
##### MST1 vlans mapped: 2-499,600-800,3110
Bridge address 6073.5c8d.7e82 priority 24577 (24576 sysid 1)
Root address 0023.04ee.be03 priority 16385 (16384 sysid 1)
port Po1 cost 500 rem hops 19
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 128.4096 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
##### MST2 vlans mapped: 1,500-599
Bridge address 6073.5c8d.7e82 priority 24578 (24576 sysid 2)
Root address 0023.04ee.be03 priority 16386 (16384 sysid 2)
port Po2 cost 1000 rem hops 19
Interface Role Sts Cost Prio.Nbr Type
Po2 Root FWD 1000 128.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
N4k-SLOT7-SW1# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:09 ago
from port-channel1
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:07 ago
from port-channel1
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3:48:07 ago
from port-channel2
(topology change was due to testing rapid-PVST for this switch, and then putting it back, the previous change occured 555 hours ago).
N4k-SLOT9-SW2# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID Priority 16384
Address 0023.04ee.be03
Cost 0
Port 4096 (port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24576 (priority 24576 sys-id-ext 0)
Address 2c54.2ded.b704
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 128.4096 P2p
Po2 Altn BLK 1000 128.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID Priority 16385
Address 0023.04ee.be03
Cost 500
Port 4096 (port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24577 (priority 24576 sys-id-ext 1)
Address 2c54.2ded.b704
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Root FWD 500 128.4096 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
MST0002
Spanning tree enabled protocol mstp
Root ID Priority 16386
Address 0023.04ee.be03
Cost 1000
Port 4097 (port-channel2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24578 (priority 24576 sys-id-ext 2)
Address 2c54.2ded.b704
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po2 Root FWD 1000 128.4097 P2p
Eth1/1 Desg FWD 2000 128.129 Edge P2p
Eth1/2 Desg FWD 2000 128.130 Edge P2p
Eth1/3 Desg FWD 2000 128.131 Edge P2p
Eth1/4 Desg FWD 2000 128.132 Edge P2p
Eth1/5 Desg FWD 2000 128.133 Edge P2p
Eth1/6 Desg FWD 2000 128.134 Edge P2p
Eth1/7 Desg FWD 2000 128.135 Edge P2p
Eth1/8 Desg FWD 2000 128.136 Edge P2p
Eth1/9 Desg FWD 2000 128.137 Edge P2p
Eth1/10 Desg FWD 2000 128.138 Edge P2p
Eth1/11 Desg FWD 2000 128.139 Edge P2p
Eth1/12 Desg FWD 2000 128.140 Edge P2p
Eth1/13 Desg FWD 2000 128.141 Edge P2p
Eth1/14 Desg FWD 2000 128.142 Edge P2p
N4k-SLOT9-SW2# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 18758 last change occurred 4:01:03 ago
from port-channel1
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 45742 last change occurred 4:01:02 ago
from port-channel1
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 21007 last change occurred 599:47:47 ago
from port-channel2
N4k-SLOT9-SW2#
N5596-DC-SW1# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID Priority 16384
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16384 (priority 16384 sys-id-ext 0)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Desg FWD 1000 128.4195 (vPC peer-link) Network P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID Priority 16385
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16385 (priority 16384 sys-id-ext 1)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Desg FWD 1000 128.4195 (vPC peer-link) Network P2p
MST0002
Spanning tree enabled protocol mstp
Root ID Priority 16386
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16386 (priority 16384 sys-id-ext 2)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
N5596-DC-SW1# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 44578 last change occurred 4:11:57 ago
from port-channel2
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 98707 last change occurred 4:11:55 ago
from port-channel2
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 4 last change occurred 4:11:55 ago
from port-channel1
N5596-DC-SW2# show spanning-tree
MST0000
Spanning tree enabled protocol mstp
Root ID Priority 16384
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16384 (priority 16384 sys-id-ext 0)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Root FWD 1000 128.4195 (vPC peer-link) Network P2p
Eth1/9 Desg FWD 20000 128.137 P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
MST0001
Spanning tree enabled protocol mstp
Root ID Priority 16385
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16385 (priority 16384 sys-id-ext 1)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po2 Desg FWD 200 128.4097 (vPC) P2p
Po3 Desg FWD 200 128.4098 (vPC) P2p
Po57 Desg FWD 200 128.4152 (vPC) P2p
Po100 Root FWD 1000 128.4195 (vPC peer-link) Network P2p
Eth1/9 Desg FWD 20000 128.137 P2p
MST0002
Spanning tree enabled protocol mstp
Root ID Priority 16386
Address 0023.04ee.be03
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 16386 (priority 16384 sys-id-ext 2)
Address 0023.04ee.be03
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Po1 Desg FWD 1000 128.4096 P2p
Eth1/9 Desg FWD 20000 128.137 P2p
Eth1/15 Desg FWD 2000 128.143 Edge P2p
Eth1/16 Desg FWD 2000 128.144 Edge P2p
N5596-DC-SW2# show spanning-tree | i occur|from|exec
N5596-DC-SW2# show spanning-tree detail | i occur|from|exec
MST0000 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 44234 last change occurred 4:12:45 ago
from port-channel100
MST0001 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 97804 last change occurred 4:12:43 ago
from port-channel100
MST0002 is executing the mstp compatible Spanning Tree protocol
Number of topology changes 49801 last change occurred 599:58:06 ago
from Ethernet1/9
Except from MST configs:
Nexus 4001i switches:
vlan 1,301-499
vlan 500
fip-snooping enable
vlan 600-800
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 24576
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
Nexus 5596 switches:
N5596-DC-SW1
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 16384
spanning-tree pseudo-information
mst 0-2 root priority 16384
mst 0-2 designated priority 16384
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
N5596-DC-SW2
spanning-tree mode mst
spanning-tree pathcost method long
spanning-tree mst 0-2 priority 16384
spanning-tree vlan 3110 priority 24576
spanning-tree pseudo-information
mst 0-1 designated priority 20480
mst 2 designated priority 16384
vlan 1-499,501,600-800 designated priority 20480
spanning-tree mst configuration
revision 1
instance 1 vlan 2-499,600-800,3110
instance 2 vlan 1,500-599
5596's vPC configs
N5596-DC-SW1
vpc domain 3
peer-switch
role priority 100
peer-keepalive destination 192.168.92.223 source 192.168.92.222
auto-recovery
N5596-DC-SW2
vpc domain 3
peer-switch
role priority 200
peer-keepalive destination 192.168.92.222 source 192.168.92.223
auto-recovery
Quick rundown of connections between devices:
Nexus 4001's connect to Nexus 5596's for ethernet data via twinax cables in a four port vPC between both Nexus 5596's.
Nexus 4001's connect to one Nexus 5596 a piece for FCoE two port LACP port channel. (hence the two instances, and vlan 1,500-599 in the same instance)
Catalyst 3110X connects via one Fiber-Optic connection to the N5596-DC-SW2, eventually will have two in a port-channel
Also keep in mind I corrected a priority conflict between the 3110X and Nexus 5596's earlier last month, which would explain all of the topology changes.
I can provide any other information if it is useful. I am just confused!I identified the problem.
Refer to
http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/interfaces/configuration/guide/if_vPC.html
for more information.
The problem I encountered was self-inflicted.
Using the spanning-tree pseudo-information command creates a psuedo priority setup that if implemented after the global spanning-tree commands sits alongside the spanning-tree priority and vlan definitions. This is intended to allow for non-vPC VLANs to have their own spanning-tree definitions separate of the spanning-tree environment for the vPC vlans. I am not sure the best way to describe it, but if you are not running a hybrid vPC setup (where you have vPC member VLANs and non-vPC VLANS with a separate link between the 5596's for the non-vPC VLANs) this setup would help you ensure you have a stable spanning-tree and prevent unnecessary blocking.
When I enabled this command, I applied it to the vPC VLAN's as well, and that caused the Nexus 4001i's vPC links to constantly change port role, and update all of the edge ports subsequently. While I didn't see a performance impact to end hosts (not much traffic is on the Nexus DataCenter environment yet), I did get a torrent of logs as shown above.
Once I removed the spanning-tree pseudo-information, the switches quieted down and spanning-tree stabilized on the Nexus 4001i's.
I will revisit the configuration though for trunks not using vPC if it is needed. -
I have enabled MST on a access layer switch
here is the MST config
spanning-tree mode mst
spanning-tree portfast bpduguard default
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree mst configuration
name building1
revision 1
instance 2 vlan 12
instance 6 vlan 16
Now look at this output fro show sho span tree
How come the switch thinks it's the root switch for MST02 & MST06 and at the same time be blocking ports
ASW12#show spanning-tree
MST00
Spanning tree enabled protocol mstp
Root ID Priority 32768
Address 000a.f49a.b080
Cost 200000
Port 1 (FastEthernet0/1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32768 (priority 32768 sys-id-ext 0)
Address 0013.8038.5fc0
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Fa0/1 Root FWD 200000 128.1 P2p Bound(RSTP)
Fa0/2 Altn BLK 200000 128.2 P2p Bound(RSTP)
Fa0/3 Desg FWD 2000000 128.3 Edge Shr
MST02
Spanning tree enabled protocol mstp
Root ID Priority 32770
Address 0013.8038.5fc0
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32770 (priority 32768 sys-id-ext 2)
Address 0013.8038.5fc0
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Fa0/1 Boun FWD 200000 128.1 P2p Bound(RSTP)
Fa0/2 Boun BLK 200000 128.2 P2p Bound(RSTP)
MST06
Spanning tree enabled protocol mstp
Root ID Priority 32774
Address 0013.8038.5fc0
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32774 (priority 32768 sys-id-ext 6)
Address 0013.8038.5fc0
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
Fa0/1 Boun FWD 200000 128.1 P2p Bound(RSTP)
Fa0/2 Boun BLK 200000 128.2 P2p Bound(RSTP)
Also I have an upstream switch with this mst config
spanning-tree mode mst
spanning-tree extend system-id
spanning-tree vlan 1,12-13 priority 8192
spanning-tree mst configuration
name building1
revision 1
instance 1 vlan 11
instance 2 vlan 12
instance 3 vlan 13
instance 5 vlan 15
instance 6 vlan 16
instance 7 vlan 17
spanning-tree mst 1,3,6 priority 8192
spanning-tree mst 2,5,7 priority 4096
We cant even control which which port becomes the root port on out acces layer switch
In fact is doing the total opposite that we have requested
cheersYou need to have a little bit more understanding of what MST is, which is not obvious for engineers very used to PVST.
In MST, there is a dependency between instances: basically, all MST Instances (id > 0) depend on the CIST (id 0). MST Instances have a scope restricted to an MST region, ie, a group of switch sharing the exact same MST configuration. At the boundary of a region, all MST Instances follow the state of the CIST.
In your example, the port you mention is at the boundary of the switch's region (its neighbor is not in the same region). As a result, all the MST Instances follow the state of the CIST for this port: as F0/2 is blocking for instance 0, it will be blocking for all the instances.
The bridge is root for the MST Instances, because it has the best root ID for these instances in the region (again, the instances only exist within the region).
Regards,
Francois -
Cisco Switches and HP Interoperability with Spanning-Tree (RSTP)
Hello All.
I read a lot of information from this forum about Spaning-Tree interoperability between HP Switches and Cisco Switches.
Rather than having questions I would like to post that I manage to configure successfully HP and Cisco using RSTP (802.1w).
SWPADRAO]display stp root
MSTID Root Bridge ID ExtPathCost IntPathCost Root Port
0 32768.cc3e-5f3a-2939 0 0
[SWPADRAO]display stp brief
MSTID Port Role STP State Protection
0 GigabitEthernet1/0/47 DESI FORWARDING NONE
0 GigabitEthernet1/0/48 DESI FORWARDING NONE
[SWPADRAO]display stp instance 0
-------[CIST Global Info][Mode RSTP]-------
CIST Bridge :32768.cc3e-5f3a-2939
Bridge Times :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
CIST Root/ERPC :32768.cc3e-5f3a-2939 / 0
CIST RegRoot/IRPC :32768.cc3e-5f3a-2939 / 0
CIST RootPortId :0.0
BPDU-Protection :enabled
Bridge Config-
Digest-Snooping :disabled
TC or TCN received :17
Time since last TC :0 days 0h:1m:52s
SWNHAM17#show spanning-tree VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32768
Address cc3e.5f3a.2939
Cost 4
Port 26 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Bridge ID Priority 61441 (priority 61440 sys-id-ext 1)
Address 001b.54db.7200
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 Interface Role Sts Cost Prio.Nbr Type
Gi0/1 Altn BLK 4 128.25 P2p
Gi0/2 Root FWD 4 128.26 P2p
SWNHAM18#show spanning-tree VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32768
Address cc3e.5f3a.2939
Cost 4
Port 26 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Bridge ID Priority 61441 (priority 61440 sys-id-ext 1)
Address 001b.0cbc.4300
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 Interface Role Sts Cost Prio.Nbr Type
Gi0/1 Desg FWD 4 128.25 P2p
Gi0/2 Root FWD 4 128.26 P2pHello, David.
Your command doesn't work because it's made only for tha ports that has command "spanning-tree portfast" in them. Try change spanning tree mode at the HP switch to MSTP if this is possible. -
I am running a 6509 (IOS ver s3223-ipbasek9-mz.122-18.SXF3)with dual sup32's in SSO redundancy mode. I am also running Multiple Spanning-tree (MST). During testing I have found that when a switchover of the active supervisor occurs (due to physical remove), MST forces all active ports on the switch to go through spanning-tree again, resulting in an outage (approx 10 secs) to the attached devices. If I perform this same test when using PVST, this outage does not occur. Is this a limitation of MST?
If you are only using one MST instance, then indeed this will not be more complex that PVST. You basically don't have to touch the MST config at all;-)
I don't think of any reason why MST should behave differently than rapid-pvst in that conditions. Could you be a little bit more specific as to what you mean by "ports go through STP"? Do you see the port role change, or is it just designated ports to go to a blocking state. If you can afford to play around with your setup, could you enable some simple and focus on a single port that you see getting blocked?
Something like:
remote login switch (the MST debugs are on the supervisor, not on the msfc)
debug condition interface
debug spanning-tree mst role
debug spanning-tree mst sync
Enable this on the redundant supervisor, and we should see what's happening to this particular port when the switchover happens.
If you don't want to enable debugs, just doing some show span mst during the problem should already help.
Regards,
Francois -
Hello,
There are two N7Ks connected with peer-link (Po1). There will be some other L2 switches connected to those N7Ks with vPC. Also, there is a separate, dedicated L2 link (Po9) between N7Ks to carry VLANs for orphan ports connected on both N7Ks. Here is configuration:
N7K-1:
spanning-tree mst configuration
name test
revision 3
instance 1 vlan 1-9,12-14,16-1005
instance 2 vlan 10,11,15
spanning-tree mode mst
spanning-tree mst 0-2 priority 4096
spanning-tree pseudo-information
mst 0-2 designated priority 4096
mst 0-2 root priority 4096
vpc domain 1
peer-keepalive destination 1.1.1.2 source 1.1.1.1 vrf peer-keepalive
system-priority 1000
role priority 1
auto-recovery reload-delay 240
peer-gateway
peer-switch
graceful consistency-check
ip arp synchronize
delay restore 30
delay restore interface-vlan 40
interface port-channel 1
vpc peer-link
switchport trunk allowed vlan remove 10,11,15
interface port-channel 9
switchport trunk allowed vlan 10,11,15
spanning-tree mst 2 cost 100
N7K-2:
spanning-tree mst configuration
name test
revision 3
instance 1 vlan 1-9,12-14,16-1005
instance 2 vlan 10,11,15
spanning-tree mode mst
spanning-tree mst 0-2 priority 4096
spanning-tree pseudo-information
mst 0-2 designated priority 8192
mst 0-2 root priority 8192
vpc domain 1
peer-keepalive destination 1.1.1.1 source 1.1.1.2 vrf peer-keepalive
system-priority 1000
role priority 1
auto-recovery reload-delay 240
peer-gateway
peer-switch
graceful consistency-check
ip arp synchronize
delay restore 30
delay restore interface-vlan 40
interface port-channel 1
vpc peer-link
switchport trunk allowed vlan remove 10,11,15
interface port-channel 9
switchport trunk allowed vlan 10,11,15
spanning-tree mst 2 cost 100
In theory, for vPC VLANs, that is those carried over peer-link, global STP configuration should be used. And, because peer-switch is used, both N7Ks will generate the same BPDU (the same Bridge ID with priority 4096), both becomming root. And, for other VLANs, carried over dedicated L2 link, the pseudo-information should be used. That is, N7K-1 should become root, and Po9 should be Designated. The N7K-2 should be backup root and Po9 should be Root port.
Unfortunately, it's not how it works. Maybe I am missing something, but BPDUs sent over dedicated L2 Po9 are exactly the same as for VPC VLANs. N7K-1 becomes root and its Po9 becomes Designated. But, N7K-2 is also a root, and since it sees the same BPDU as it generates by itself, it treats Po9 as an alternate way to itself and places that port in Alternate/Blocking state.
So, am I doing something wrong, or dedicated L2 link cannot co-exist with peer-link? I had no chance to test it, but it may work if I remove peer-switch feature (although it is recommended to have it)
Best regards,
KrzysztofWe have filed
CSCuc41076
vPC Peer Switch Hybrid Topology MST blocking in non vPC Peer Link -
Hi,
I have 6 x 3560 switches all connected in a redundant ring topology and interconnected using fibre.
I have enabled the fibre ports as trunk ports with dot1q encapsulation.
I have created 6 VLANS and defined ports on each device as members of the configured VLANS, and also defined a VTP root switch (all VLAN info appears to be propagating correctly between all switches).
I have enabled MST on all the devices and created an instance 1 with a name and revision number on all of the switches which are identical.
I have also used the root and secondary mst commands to define a root and secondary switch.
E.G:-
spanning-tree mode mst
spanning-tree extend system-id
spanning-tree mst configuration
name ABC
revision 1
instance 1 vlan 1-200
The problem I am seeing is that if I remove the fibre from the ROOT port from the ROOT switch, the comms fail and I see a time out of approx 8-10 seconds before the link is re-established using the redundant path (second fibre port. I see the port swap the MST01 from DESG to ROOT, when the previous ROOT port goes down (cable removed).
Ive reduced the forward time to the minimum 4 seconds, which has improved the recovery time, but still not <1 second which I need.
Im confused as to why when I setup a device on 1 switch to ping a device on the adjacent switch (ie next device in the fibre), but is on the same VLAN, that the layer 2 comms should be affected by the removal of the Root switch link (physicaly not even connected to the 2 devices which need to talk).
I can see if the root switch is totally removed from circuit, that the secondary takes over fine.
Im also not doing any layer 3, inter-vlan routing.
Can anyone help?If tuning the forward delay timer had any effect, it means that your network is not taking advantage of the MST protocol. Reconvergence is achieved with no use of the forward delay timer in your scenario. Check that all the links in your ring are seen as point-to-point by the STP. You can also adjust the max-hop parameter to a value closer to the size of your ring (assuming that your MST network is only this ring, you could tune it down to 8 for instance). Also, you may want to upgrade your software release if it's an old one, as the response to agreement have been optimized (it may save some few seconds). At last, if you are only using one instance, the simplest and the most efficient is to keep the default configuration, where all the vlans are mapped to instance 0 (but I guess your network is more complex than what you exposed).
MST uses a sync mechanism that explains that the communication between your edge switch could be affected by a failure on the root. That should be short though.
Regards,
Francois -
Dear All,
I have a query regarding MST, I have attached the topology, i am suing 4500 switches as the CORE in the LAn network and many 2960,3850 as access switches, am also using Nexus switches. I would like to use Multiple spanning tree(MST) in the network. My plan was to make the 4500 VSS core as the root switch. However am confused as to how many regions and instances do i create. Please give ur valuable views on this as to how do i go about and apply MST on the networkHi,
Usually you don't need more than one region and one instance unless you have a lots of vlans and you want to load balance traffic. Multiple regions with multiple instance can make things complicated and hard to manage.
For switches to participate in multiple spanning-tree (MST) instances, you must consistently configure the switches with the same MST configuration information. A collection of interconnected switches that have the same MST configuration comprises an MST region as shown in Figure 19-1.
The MST configuration controls to which MST region each switch belongs. The configuration includes the name of the region, the revision number, and the MST VLAN-to-instance assignment map. You configure the switch for a region by using the spanning-tree mst configuration global configuration command, after which the switch enters the MST configuration mode. From this mode, you can map VLANs to an MST instance by using the instance MST configuration command, specify the region name by using the name MST configuration command, and set the revision number by using the revision MST configuration command.
A region can have one or multiple members with the same MST configuration. Each member must be capable of processing RSTP bridge protocol data units (BPDUs). There is no limit to the number of MST regions in a network, but each region can support up to 65 spanning-tree instances. Instances can be identified by any number in the range from 0 to 4094. You can assign a VLAN to only one spanning-tree instance at a time.
link:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/swmstp.html
HTH -
What is the command to check the changes in the spanning-tree topology?
What is the command to check the changes in the spanning-tree topology?
Hi,
Few commands which would help are:
1- Show spanning-tree detail
2-show spanning-tree detail | in ieee|from|occur|is exec >> This will give from were the changes occuring- Ex:
C6K1#show spanning-tree detail | in ieee|from|occur|is exec
VLAN0001 is executing the rstp compatible Spanning Tree protocol
Number of topology changes 9536 last change occurred 00:00:29 ago
from GigabitEthernet4/6
3- show spanning-tree active *& show spanning-tree root >> Will give you the root information.
4- show spanning-tree inconsistentports >> If there are any port which are inconsistent state due to STP features.
STP running MST:
===============
show spanning-tree mst configuration >> Need to check and match the same outputs with the other switches running in the same MST domain/region.
show spanning-tree mst detail
show spanning-tree mst <name of the region>
Debug on STP:
============
debug spanning-tree events/bpdu >> would be good but to be run with more cautious.
HTH
Inayath
*Plz rate if this info is usefull. -
Nexus spanning tree pseudo configuration
Hi
I am trying to understand the pseudo configuration commands in a Nexus hybrid topology.
I have vlans a, b and c only in the vPC side of the topology. I have peer switch configured and the same stp priority on both switches.
In the standard Spaning-tree topology I have completely seperate vlans x, y and z.
What should I be configuring in the pseudo config section ? Do I define a pseudo root priority for all vlans a, b, c and x, y, z or just for the standard spanning tree vlans x, y and z. I need to avoid and, even short, spanning tree outages if I take one Nexus out of service for a short time.
My thinking is that if one Nexus is out of service the physical mac will be used and potentially reduce the root priority of the vPC vlans causing a TCN and STP recalculation in vlans a, b and c. This can be avoided by configuring a pseudo root priority for all Vlans lower than the current spanning tree priority shared by the vPC peers. Is this correct ? However, since I have a shared priority of 8192 on current vPC vlans will configuring, for example, a pseudo root priority of 4096 on those vPC vlans won't this also cause the TCN and recalculation I am trying to avoid ? Is the benefit of the pseudo root config only obtained if it is configured at the start when the vPC is formed and prior to the peer switch command being issued ?
Thanks, Stuart.Hi Ajay,
It is recommended that switch-to-switch links are configured with the spanning-tree port type normalcommand. The one exception is the vPC peer-link which is recommended to configure with the spanning-tree port type network command.
Take a read of the Best Practices for Spanning Tree Protocol Interoperability from page 56 of the vPC Best Practice Design Guide for further information on this.
Regards
Maybe you are looking for
-
How to check upload progress when using Azure Node.js SDK createBlockBlobFromLocalFile
We are building our cloud application using node.js. The "createBlockBlobFromLocalFile" API can be used to upload a local file to a container. However, is there any feedback event being fired so that I know how many bytes have been uploaded so far?
-
I have had this range expander for approximately 4 years now. It works, I mean blue lights and all and I can connect to it, but I could never access the web utility. I tried to plug it into the router, results in a lost connection. Tried changing t
-
WBS element withot Billing element
Hi Is it possible to create sales order with account assinment ' WBS element w/o Billing element' ?
-
Nodemanager Broken in WLS 12.1.2 (Bug)
I discovered the following issue with the latest WLS 12.1.2 release: WebLogic 12.1.2 Nodemanager Bug Any suggestions? Is anybody else bothered? Does it work with the per machine NM? Same problem in earlier versions of WLS or just 12.1.2? (I haven't n
-
Trying to find a new way of expressing the constant crashing of Safari 3.0.4. I'm using a G4 Powerbook running 10.4.11, and a MacBookPro running Leopard 10.5.1, both at home and at work, both on airport. They both crash frequently usually when going