10-18-2018 01:58 AM
Hi all,
every second i receive the following mstp events on both our cisco nexus (3064PQ) that are in a VPC domain
this port-channel agregates 2 40Gb links.
2018 Oct 18 08:35:16.278912 stp: mstp_cist_select_root(1253): port-channel1 selected peer-switch RP 2018 Oct 18 08:35:16.285768 stp: mstp_msti_select_root(963): port-channel1 selected peer-switch RP 2018 Oct 18 08:35:16.285924 stp: mstp_msti_select_root(963): port-channel1 selected peer-switch RP 2018 Oct 18 08:35:16.286022 stp: stp_get_stp_in_hitless_flag(138): stp_gbl_in_hitless_rc_flag:0x0
thanks for the attention,
Sincerely,
AM
10-19-2018 08:30 AM
Hey AM,
Are these constant syslogs or were you running debugs? Can you share the following:
show vpc role show run vpc show run spanning-tree show span vlan 1 show logging level spanning-tree
show span det | i ieee|occur|exec|from
show run int po1
show cdp neigh int po1
show logging log | i i stp | last 50
Thank you,
10-19-2018 09:26 AM
Hi Andrea,
The constant log only happens on "debug spanning-tree event"
SwitchCore02# show vpc role vPC Role status ---------------------------------------------------- vPC role : secondary Dual Active Detection Status : 0 vPC system-mac : 00:23:04:ee:be:0a vPC system-priority : 32667 vPC local system-mac : a4:93:4c:80:72:01 vPC local role-priority : 4000 vPC local config role-priority : 4000 vPC peer system-mac : a4:4c:11:b8:e6:41 vPC peer role-priority : 2000 vPC peer config role-priority : 2000
SwitchCore02# show run vpc !Command: show running-config vpc !Time: Fri Oct 19 15:41:20 2018 version 7.0(3)I7(4) feature vpc vpc domain 10 peer-switch role priority 4000 peer-keepalive destination 192.168.1.10 source 192.168.1.11 auto-recovery interface port-channel1 vpc peer-link interface port-channel12 vpc 12 interface port-channel15 vpc 10 interface port-channel20 vpc 20 interface port-channel21 vpc 21 interface port-channel22 vpc 22 interface port-channel23 vpc 23 interface port-channel24 vpc 24 interface port-channel25 vpc 25 interface port-channel26 vpc 26 interface port-channel27 vpc 27 interface port-channel28 vpc 28 interface port-channel29 vpc 29 interface port-channel30 vpc 30 interface port-channel31 vpc 31
SwitchCore02# sh run spanning-tree spanning-tree mode mst spanning-tree mst 0-1 priority 8192 spanning-tree mst configuration name region1 instance 1 vlan 1,20-21,25,30,110 interface port-channel1 spanning-tree port type network interface port-channel20 spanning-tree port type edge interface port-channel21 spanning-tree port type edge interface port-channel22 spanning-tree port type edge interface port-channel23 spanning-tree port type edge interface port-channel24 spanning-tree port type edge interface port-channel25 spanning-tree port type edge interface port-channel26 spanning-tree port type edge interface port-channel27 spanning-tree port type edge interface port-channel28 spanning-tree port type edge interface port-channel29 spanning-tree port type edge interface port-channel30 spanning-tree port type edge interface Ethernet1/14 spanning-tree port type edge spanning-tree guard root interface Ethernet1/25 spanning-tree port type edge interface Ethernet1/41 spanning-tree guard root interface Ethernet1/42 spanning-tree guard root interface Ethernet1/43 spanning-tree guard root interface Ethernet1/44 spanning-tree guard root
SwitchCore02# show span vlan 1 MST0001 Spanning tree enabled protocol mstp Root ID Priority 4097 Address 0023.04ee.be0a Cost 250 Port 4096 (port-channel1) Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Bridge ID Priority 8193 (priority 8192 sys-id-ext 1) Address 0023.04ee.be0a Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Po1 Root FWD 250 128.4096 (vPC peer-link) Network P2p Po12 Desg FWD 200 128.4107 (vPC) P2p Bound(STP) Po20 Desg FWD 200 128.4115 (vPC) Edge P2p Po21 Desg FWD 200 128.4116 (vPC) Edge P2p Po22 Desg FWD 200 128.4117 (vPC) Edge P2p Po24 Desg FWD 200 128.4119 (vPC) Edge P2p Po25 Desg FWD 200 128.4120 (vPC) Edge P2p Po28 Desg FWD 200 128.4123 (vPC) Edge P2p Po29 Desg FWD 200 128.4124 (vPC) P2p Po30 Desg FWD 200 128.4125 (vPC) P2p Po31 Desg BLK 200 128.4126 (vPC) P2p Eth1/9 Desg FWD 20000 128.9 P2p Eth1/14 Desg FWD 20000 128.14 P2p Eth1/25 Desg FWD 20000 128.25 Edge P2p Eth1/29 Desg FWD 20000 128.29 P2p Eth1/30 Desg FWD 20000 128.30 P2p Eth1/41 Desg FWD 20000 128.41 P2p Eth1/42 Desg FWD 20000 128.42 P2p Eth1/43 Desg FWD 2000 128.43 P2p Eth1/44 Desg FWD 20000 128.44 P2p
SwitchCore02# show logging level spanning-tree Facility Default Severity Current Session Severity -------- ---------------- ------------------------ stp 3 3 0(emergencies) 1(alerts) 2(critical) 3(errors) 4(warnings) 5(notifications) 6(information) 7(debugging)
SwitchCore02# show span det | i ieee|occur|exec|from MST0000 is executing the mstp compatible Spanning Tree protocol Number of topology changes 614 last change occurred 0:14:16 ago from Ethernet1/41 MST0001 is executing the mstp compatible Spanning Tree protocol Number of topology changes 617 last change occurred 0:14:16 ago from Ethernet1/41
SwitchCore02# show run int po1 !Command: show running-config interface port-channel1 !Time: Fri Oct 19 16:22:20 2018 version 7.0(3)I7(4) interface port-channel1 description 80G_UPLINK switchport mode trunk switchport trunk allowed vlan 1,20-21,25,30,45,110 spanning-tree port type network vpc peer-link
SwitchCore02# show cdp neigh int po1 Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge S - Switch, H - Host, I - IGMP, r - Repeater, V - VoIP-Phone, D - Remotely-Managed-Device, s - Supports-STP-Dispute Device-ID Local Intrfce Hldtme Capability Platform Port ID SwitchCore01.172.16.1.10(FOC1627R00P) Eth1/49 140 R S I s N3K-C3064PQ-1 Eth1/49 SwitchCore01.172.16.1.10(FOC1627R00P) Eth1/51 140 R S I s N3K-C3064PQ-1 Eth1/51 Total entries displayed: 2
SwitchCore02# show logging log | i i stp | last 50 2018 Oct 8 08:43:46 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:44:22 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:44:24 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:44:35 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:44:37 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:44:51 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:44:53 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:45:29 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:45:31 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:45:58 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:01 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:30 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:32 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:45 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:46 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:52 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 8 08:46:54 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 10 12:31:47 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/41 on MST0000. 2018 Oct 10 12:31:53 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/41 on MST0000. 2018 Oct 10 12:32:11 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/41 on MST0000. 2018 Oct 10 12:32:23 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/41 on MST0000. 2018 Oct 10 12:32:41 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/41 on MST0000. 2018 Oct 10 12:34:55 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/41 on MST0000. 2018 Oct 17 08:04:02 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 17 08:04:03 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 17 08:04:40 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/44 on MST0000. 2018 Oct 17 08:04:41 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/44 on MST0000. 2018 Oct 17 08:19:53 SwitchCore02 %STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard enabled on port Ethernet1/44. 2018 Oct 17 08:24:14 SwitchCore02 %STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard enabled on port Ethernet1/41. 2018 Oct 17 08:24:14 SwitchCore02 %STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard enabled on port Ethernet1/42. 2018 Oct 17 08:24:14 SwitchCore02 %STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard enabled on port Ethernet1/43. 2018 Oct 17 16:23:27 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/41 on MST0000. 2018 Oct 17 16:27:43 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/41 on MST0000. 2018 Oct 17 16:31:16 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/41 on MST0000. 2018 Oct 17 16:31:16 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/41 on MST0000. 2018 Oct 18 16:37:57 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 18 16:37:57 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/14 on MST0000. 2018 Oct 18 16:39:10 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 18 16:39:11 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/14 on MST0000. 2018 Oct 18 16:43:06 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 18 16:45:38 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 18 16:45:38 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/14 on MST0000. 2018 Oct 18 16:46:26 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 18 16:46:26 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/14 on MST0000. 2018 Oct 18 17:00:59 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 18 17:00:59 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/14 on MST0000. 2018 Oct 18 17:01:39 SwitchCore02 %STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard disabled on port Ethernet1/14. 2018 Oct 18 17:06:56 SwitchCore02 %STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard enabled on port Ethernet1/14. 2018 Oct 19 11:41:03 SwitchCore02 %STP-2-DISPUTE_DETECTED: Dispute detected on port Ethernet1/14 on MST0000. 2018 Oct 19 11:41:44 SwitchCore02 %STP-2-DISPUTE_CLEARED: Dispute resolved for port Ethernet1/14 on MST0000.
The last logs on Ethernet1/14 are tests on a test switch
Thanks for the attention.
Sincerely,
AM
10-22-2018 06:12 AM
Hey AM,
It looks like you have fairly constant STP Disputes on this switch which would explain the debugs regarding cist/msti root election. I would open a TAC case to have a Nexus engineer trace the source of the STP Disputes for you.
Spanning-tree Disputes are triggered when the BPDU received from our connecting device is inferior (worse) however it has the Designated role and state as Learning and/or Forwarding. In simpler terms, there's another switch in your network that is claiming to be the STP root even though it has a higher STP priority.
Hope that helps.
10-22-2018 07:42 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide