topic Re: Erro:STP.InBPDU.Drop since replacing a Cisco switch for Extreme in ExtremeSwitching (EXOS/Switch Engine)

Erro:STP.InBPDU.Drop since replacing a Cisco switch for Extreme

Keith9 — Sat, 13 Feb 2021 05:46:18 GMT

In our core we have 2 X690 stacks running VRRP between them and we also MLAG between them to uplink to other closets.

We just replaced a stack of Cisco 3750x switches in a 3rd floor network closet with two Extreme 5520 running EXOS 31.1.1.3.

Connected to them is a 10gbps fiber optic uplink to port 1:57 and port 2:57.

Down where all links converge our two X690 stacks are called PurpleCore and YellowCore (appropriate colored cables going to each). Port 1:2 on PurpleCore goes to 5520 switch port 1:57. Port 1:2 on YellowCore goes to 5520 swich port 2:57.

There is no connectivity issue at all between the datacenter and 3rd floor network closet. Not a single complaint, and everything seems to be working.

I was just in some switches today and noticed in PurpleCore X690 I’m seeing a lot of these log messages

02/12/2021 16:41:26.22 <Erro:STP.InBPDU.Drop> Slot-1: Port=1:2: STP Port is disabled!
02/12/2021 16:38:32.08 <Erro:STP.InBPDU.Drop> Slot-1: Previous message repeated 87 additional times in the last 172 second(s)

Nothings changed except the switch in the 3rd floor closet. These messages were non-existant when Cisco swiches were up there. Here’s how the port is configured at the core:
enable sharing 1:2 grouping 1:2 algorithm address-based L3_L4 lacp
enable mlag port 1:2 peer "YELLOW" id 102
1:2 Untagged 1
Tagged 3, 5, 172, 200

And at the 5520 switch stack
enable sharing 1:57 grouping 1:57,2:57 algorithm address-based L3_L4 lacp
1:57 Untagged 1
Tagged 3, 5, 172, 200

the sh log on that access switch does not show anything in regards to <Erro:STP.InBPDU.Drop>

Any idea why just switching out the access switch brand causes this log on one of our core’s? Is it cosmetic only? Nobody is reporting any issues.

Re: Erro:STP.InBPDU.Drop since replacing a Cisco switch for Extreme

Keith9 — Sat, 13 Feb 2021 06:03:39 GMT

I noticed on our core switch we have some of these statements on any ports that are dual uplinked to other area’s via the mlag.

disable stpd s0 ports 1:1
disable stpd s0 ports 1:2
disable stpd s0 ports 1:3
disable stpd s0 ports 1:9
disable stpd s0 ports 1:45
disable stpd s0 ports 2:1
disable stpd s0 ports 2:7
disable stpd s0 ports 2:27

So on the new 5520 switch in the 3rd floor closet I put

disable stpd s0 ports 1:57

Then on the PurpleCore X690 with this repeaded log spam, I disable port 1:2 enable port 1:2

Now the log shows this. A few minutes later and it still doesn't says its down.

02/12/2021 16:56:33.33 <Info:LACP.AddPortToAggr> Slot-1: Add port 1:2 to aggregator
02/12/2021 16:56:31.32 <Info:vlan.msgs.portLinkStateUp> Slot-1: Port 1:2 link UP at speed 10 Gbps and full-duplex
02/12/2021 16:56:28.46 <Info:LACP.RemPortFromAggr> Slot-1: Remove port 1:2 from aggregator
02/12/2021 16:56:28.46 <Info:vlan.dbg.info> Slot-1: Port 1:2 is Down, remove from aggregator 1:2
02/12/2021 16:56:28.46 <Info:vlan.msgs.portLinkStateDown> Slot-1: Port 1:2 link down
02/12/2021 16:55:16.79 <Erro:STP.InBPDU.Drop> Slot-1: Port=1:2: STP Port is disabled!

This was the config of the uplink port on the cisco switch that the 5520 replaced:

interface Port-channel3
description To Extreme Core
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,3,5,172,200
switchport mode trunk
ip arp inspection trust
spanning-tree bpdufilter enable
ip dhcp snooping trust

interface TenGigabitEthernet3/1/1
description Uplink to Purple-Core 1:2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,3,5,172,200
switchport mode trunk
ip arp inspection trust
channel-group 3 mode active
spanning-tree portfast
spanning-tree bpdufilter enable
ip dhcp snooping trust

interface TenGigabitEthernet3/1/2
description Uplink to Yellow-Core 1:2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,3,5,172,200
switchport mode trunk
ip arp inspection trust
channel-group 3 mode active
spanning-tree portfast
spanning-tree bpdufilter enable
ip dhcp snooping trust

Re: Erro:STP.InBPDU.Drop since replacing a Cisco switch for Extreme

Miguel-Angel_RO — Sat, 13 Feb 2021 19:10:19 GMT

Keith,

Could oyu share a show stpd s0 ports?

Mig

Re: Erro:STP.InBPDU.Drop since replacing a Cisco switch for Extreme

PeterK — Sat, 13 Feb 2021 19:39:57 GMT

you see this messages because you’ve disabled stp on that ports, but the 5520 has stp enabled on the uplinks

disable stp on the uplink of the 5520

“Erro:STP.InBPDU.Drop” does not mean, that port is in blocking… it is in forwarding. It’s a “Warning” that you receive bpdu’s on a stp-disabled port.

In cases where you have no access to the other switch you can filter bpdu-pakets with a ACL

Re: Erro:STP.InBPDU.Drop since replacing a Cisco switch for Extreme

Keith9 — Tue, 16 Feb 2021 04:16:04 GMT

I think I have it stopped now. On the new switch in our 3rd floor closet, I ran this on the master port of that load sharing link

disable stpd s0 ports 1:57
That port now shows like this in sh stpd s0 ports

1:57* 802.1D FORWARDING 1800 d-------- 128 8039 00:00:00:00:00:00:00:00

Downstairs at the core where it’s plugged in here is the first core (part of an mlag)
1:2* 802.1D FORWARDING 2000 d-------- 128 8002 00:00:00:00:00:00:00:00

And in the other core switch (mlag peer)
1:2* 802.1D FORWARDING 2000 d-------- 128 8002 00:00:00:00:00:00:00:00

Not showing any logspam anymore.

Think this one is solved.
I guess disable stpd s0 ports X:XX is equivelant to Cisco’s commands:
spanning-tree portfast
spanning-tree bpdufilter enable

That were on the uplink ports of the switch stack that we replaced?