07-18-2018 04:16 AM - edited 03-08-2019 03:43 PM
Setup:
We have couple of N3K connected back to back on a trunk link, dual home Internet feed terminating on each of them.
We have single multihomed L2 (transparent) circuit wiz capable of transporting multi-tag frame and L2 protocol between these N3K and Remote CPE switch 3850 (stack of 6).
N3K--------- N3K
| |
| |
L2 Crkt1 L2 Crkt2 (Crkt1 & 2 are from different carrier)
| |
| |
3850-Stack-of-6
Problem statement:
Observing STP loop if enable both the circuit. STP roots are elected differently for both the end of LAN segment.
STP counters for Interfaces connected between N3Ks and 3850, increment only for "sent bpdu" however the counter remains 0 for "receive bpdu".
Other interfaces of the switches doesn't show such kind of STP malfunctioning issue.
Diagnose:
Circuits are bidirectional as Udld aggressive works good.
Circuit transport L2 protocols, since cdp works fine.
Able to ping connected subnet, If enable any single circuit.
Packet captured at both the end of circuit which shows BPDU received on the wire however the interface seems not processing it and the counter still remains 0 for "receive bpdu" on both the side of the interfaces.
Default the interfaces and re configure the ports however no luck.
Logs:
N3K1 & N3K2 are identical
N3K2# sh spanning-tree interface Eth1/49 deta
Port 177 (Ethernet1/49) of VLAN0500 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.177
Designated root has priority 33268, address 707d.xxxx.737c
Designated bridge has priority 33268, address 707d.xxxx.7601
Designated port id is 128.177, designated path cost 4
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 2
Link type is point-to-point by default
BPDU: sent 164140, received 0
!
interface Ethernet1/49
switchport mode trunk
switchport trunk allowed vlan 500
speed 1000
udld aggressive
========================================================
Output for tenGigabitEthernet 1/1/2 & tenGigabitEthernet 2/1/2 are identical
3850-Stack-of-6#show spanning-tree interface tenGigabitEthernet 1/1/2 det
Port 54 (TenGigabitEthernet1/1/2) of VLAN0500 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.54.
Designated root has priority 500, address 00e1.xxx.6580
Designated bridge has priority 500, address 00e1.xxxx.6580
Designated port id is 128.54, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
Loop guard is enabled on the port
BPDU: sent 26, received 0
!
interface TenGigabitEthernet2/1/2
description xxxxxx
switchport trunk allowed vlan 500
switchport mode trunk
udld port
spanning-tree guard loop
end
03-17-2020 09:38 AM
We are having a very similar issue here. We are running MST on our network for a carrier ethernet service provider configuration. Seems that double tagged 802.1ad/802.1q carrier ports are not able to receive BPDUs on an ISR 4451-X. If I change the interfaces to single 802.1q tagging the spanning tree process works fine, and the root bridge info is populated. BPDU counter goes up.
We have the core ports configured as such:
Core Router: ASR 920
interface GigabitEthernet0/0/0
no ip address
media-type rj45
negotiation auto
spanning-tree link-type point-to-point
ethernet dot1ad nni
service instance 10 ethernet
encapsulation dot1ad 10 dot1q 10
rewrite ingress tag pop 2 symmetric
bridge-domain 10
Edge Router: ISR 4451-X
interface GigabitEthernet0/0/0
no ip address
media-type rj45
negotiation auto
spanning-tree link-type point-to-point
service instance 10 ethernet
encapsulation dot1ad 10 dot1q 10
rewrite ingress tag pop 2 symmetric
bridge-domain 10
Spanning Tree output:
Port 7 (GigabitEthernet0/0/0) of MST10 is root forwarding
Port path cost 20000, Port priority is 128, Port Identifier 128.7,
Designated root has priority 10, address cc70.xxxx.e33d
Designated bridge has priority 32778, address 00fd.xxxx.fe3d
Designated port id is 128.7, designated path cost 40000
Timers: message age 0, forward delay 14, hold 0
Number of transitions to forwarding state: 0
Link type is point-to-point, Internal
Loop guard is enabled by default on this port
BPDU: sent 1139, received 0
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