Comware

I am replacing a 6120 blade switch with 6127XLG. With the 6120 I had bpdu filter configured for an uplink port so it drops bpdus sent on the uplink interface connected to a switch which has a bpduguard enabled. However, the 6127 does not have a bpdu filter option but instead it has bpdu drop, which I am assuming should do the same thing. In fact, it seems to keep forwading the bpdus up the port connected to the switch with the bpduguard enabled, since the port immediately transitions to Error Disabled. I ended up disabling the STP on the port to workaround this.
Anyone knows why it's not working and what else I can do with keeping stp enabled?

Is this community thing working? Not even views. How do we get support for these issues if no one is even looking at this?

I am replacing a 6120 blade switch with 6127XLG. With the 6120 I had bpdu filter configured for an uplink port so it drops bpdus sent on the uplink interface connected to a switch which has a bpduguard enabled. However, the 6127 does not have a bpdu filter option but instead it has bpdu drop, which I am assuming should do the same thing. In fact, it seems to keep forwading the bpdus up the port connected to the switch with the bpduguard enabled, since the port immediately transitions to Error Disabled. I ended up disabling the STP on the port to workaround this.
Anyone knows why it's not working and what else I can do with keeping stp enabled?

Hi Gedit

(Community members "do what they can", and sometimes they are not as reactive as a pro support team)

Anyway, 6127 is "HPE ProVision-based switches (formerly E-Series/ProCurve)", not comware ?

Why don't you just enable and configure spanning tree on both switches instead of trying to drop BPDUs ?

BPDU-drop works on "incoming" bpdus, not egress. Extract from doc : "A BPDU drop-enabled port does not receive any BPDUs "

The same for "bpdu-protection" function.

Maybe you are looking for "tc-restriction" function...

Is this community thing working? Not even views. How do we get support for these issues if no one is even looking at this?

I am replacing a 6120 blade switch with 6127XLG. With the 6120 I had bpdu filter configured for an uplink port so it drops bpdus sent on the uplink interface connected to a switch which has a bpduguard enabled. However, the 6127 does not have a bpdu filter option but instead it has bpdu drop, which I am assuming should do the same thing. In fact, it seems to keep forwading the bpdus up the port connected to the switch with the bpduguard enabled, since the port immediately transitions to Error Disabled. I ended up disabling the STP on the port to workaround this.
Anyone knows why it's not working and what else I can do with keeping stp enabled?

HI Frederic,
Thank you for your response. I did originally post this on the HPE community and was advised that the support for this switch has moved to this community.

I must say that documentation is a bit cryptic, since this type of switch is an edge that connects to ToR or other switch/router. So my understanding of this feature, that if the switch received BPDUs on the port it will drop them, OK so I guess if it receives them from the network going "downstream" to the end host connected to the switch, it will drop them? But a end host by definition doesn't receive or send BPDUs. On the port connected upstream (on which I've enabled BPDU drop), if it only drops BPDUs when received, why is it OK to send BPDUs to the upstream switch from which if received will drop them? In other words, this feature is really useless IMO.
To your question, both switches are configured for Spanning tree, however the upstream switch (which is a customer switch hence not in my control), is configured to not received BPDUs because the customer doesn't want this port to be impacted by STP calculation and having to shut down the port hence decided to disable STP on that port altogether..
Reading about tc-restriction, I will try it, but this sounds like what bpdu-drop should have done. If the port receives BPDUs it doesn't forward it to other ports, which sounds to me like " bpdu-drop".

Cheers!
Gedit

Hi Gedit

(Community members "do what they can", and sometimes they are not as reactive as a pro support team)

Anyway, 6127 is "HPE ProVision-based switches (formerly E-Series/ProCurve)", not comware ?

Why don't you just enable and configure spanning tree on both switches instead of trying to drop BPDUs ?

BPDU-drop works on "incoming" bpdus, not egress. Extract from doc : "A BPDU drop-enabled port does not receive any BPDUs "

The same for "bpdu-protection" function.

Maybe you are looking for "tc-restriction" function...

Is this community thing working? Not even views. How do we get support for these issues if no one is even looking at this?

I am replacing a 6120 blade switch with 6127XLG. With the 6120 I had bpdu filter configured for an uplink port so it drops bpdus sent on the uplink interface connected to a switch which has a bpduguard enabled. However, the 6127 does not have a bpdu filter option but instead it has bpdu drop, which I am assuming should do the same thing. In fact, it seems to keep forwading the bpdus up the port connected to the switch with the bpduguard enabled, since the port immediately transitions to Error Disabled. I ended up disabling the STP on the port to workaround this.
Anyone knows why it's not working and what else I can do with keeping stp enabled?