MSTP between HP Procurve and Cisco problem.

[dmbnex]

Hi guys,

This should be a quite easy deployment to accomplish.

I struggle to make the Procurve the root for all vlans without the cisco blocking its uplink(trunk) to the procurve.

there is created mst region with same name and revision on both procurve and cisco switches, default instance.(all vlans are members as of default)

there is no routing to these just an L2 trunk in between.

when lowering procurves mst 0 priority lower then the cisco' the cisco block as it look random vlans on it trunk port.

after raising it again and cisco becomes the root all is fine..

the cisco is an access switch and I would really like the procurve to be the root of the stp in the region.

procurve has more uplinks to other switches but it does not block anything when it is acting as root..

[procurve]-----vlan-trunk----X->[cisco]

gi0/1 is the trunk to the procurve

vlan13 is the management

fa0/6 is edge.

here is the log:

*Jul  2 09:38:39.560: %SPANTREE-2-PVSTSIM_FAIL: Blocking root port Gi0/1: Inconsitent inferior PVST BPDU received on VLAN 11, claiming root 32779:000f.23e7.69c0

*Jul  2 09:38:39.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan13, changed state to down

sw02(config)#

*Jul  2 09:38:39.619: %SPANTREE-2-PVSTSIM_FAIL: Blocking designated port Fa0/6: Inconsitent superior PVST BPDU received on VLAN 14, claiming root 32768:0026.55d7.bbf2

MST Instance           Root ID          Cost    Time  Age Dly  Root Port

---------------- -------------------- --------- ----- --- ---  ------------

MST0              4096 ec30.91b6.a900         0    2   20  15

MST0

  Root ID    Priority    4096

             Address     ec30.91b6.a900

             This bridge is the root

             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

sw02(config)#spanning-tree mst 0 priority 4096

*Jul  2 09:37:20.640: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan13, changed state to up

*Jul  2 09:37:39.565: %SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port GigabitEthernet0/1.

sw02(config)#spanning-tree mst 0 priority 45056

sw02(config)#

*Jul  2 09:38:39.560: %SPANTREE-2-PVSTSIM_FAIL: Blocking root port Gi0/1: Inconsitent inferior PVST BPDU received on VLAN 11, claiming root 32779:000f.23e7.69c0

*Jul  2 09:38:39.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan13, changed state to down

sw02(config)#

*Jul  2 09:38:39.619: %SPANTREE-2-PVSTSIM_FAIL: Blocking designated port Fa0/6: Inconsitent superior PVST BPDU received on VLAN 14, claiming root 32768:0026.55d7.bbf2

sw02(config)#spanning-tree mst 0 priority 4096

*Jul  2 09:39:39.622: %SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port FastEthernet0/6.

sw02(config)#

*Jul  2 09:40:10.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan13, changed state to up

what may be done to make the procuve root for the mst region?

any help is appreciated,

regards, Dan.

[Rolf Fischer · Accepted solution]

Dan,

it looks like you have other Cisco switches running a per-VLAN STP mode connected to the ProCurve switch.

The problem could be that the ProCurve does not understand the Cisco proprietary so-called Shared-STP BPDUs (per-VLAN) and treats them as normal multicast, that is flooding them over all interfaces, including the uplink to the MSTP access-switch.

Many years ago I had exactly the same problem. Unfortunately I don't remember the ProCurve command, but you can suppress the SSTP MAC address. Other discussion:

https://supportforums.cisco.com/discussion/11896731/native-vlan-mismatch-between-cisco-and-non-cisco-switches

Perhaps you could elaborate a bit what your layer-2 topology looks like and what protocols are running.

HTH
Rolf

[VNi]

just wondering, if we were to configure bpdu filter between HP and Cisco that would solve the problem?

of course in that scenario we would have two root bridges for the same vlan but we would be able to extend broadcast domain across two switches without problem.