HP A5500 LACP and "bpdu-drop any"

[JanGierveld]

Hi all,

We are trying to configure a 20Gbps bridge-aggregation between 2 HPE A5500 switches in an IRF Stack and 2 Aruba 2930F switches in VSF mode. The HPE A500 IRF Stack is the STP root bridge for all switches on this specific location. The Aruba 2930 Stack is part of a different spanning-tree domain/instance (City fiber ring) so we don't want STP BPDU's to be transferred between the 2 stacks and thus different spanning-tree domains/instances. On the Aruba 2930 we have the following configuration;

#
trunk 1/28,2/28 trk1 lacp
#
interface 1/28
name "Trunk LACP Core_switch_BRK"
untagged vlan 1
trunk trk1 lacp
exit
#
interface 2/28
name "Trunk LACP Core_switch_BRK"
untagged vlan 1
trunk trk1 lacp
exit
#
interface Trk1
tagged vlan 10,24,31,56,70,118,120,124,140,160,168,200,208,240,330,400,809,811,1018,1020,2012
untagged vlan 1
spanning-tree priority 4 bpdu-filter
exit
#

On the HPE 5500 switch we are using the following configuration;

#
interface Bridge-Aggregation8
description Uplink Ring-Core8
port link-type trunk
port trunk permit vlan 1 10 24 31 56 70 118 120 124 140
port trunk permit vlan 160 168 200 208 240 330 400 809 811 1018
port trunk permit vlan 1020 2012
link-aggregation mode dynamic
#
interface Ten-GigabitEthernet1/0/30
port link-mode bridge
description Uplink Ring-Core8
port link-type trunk
port trunk permit vlan 1 10 24 31 56 70 118 120 124 140
port trunk permit vlan 160 168 200 208 240 330 400 809 811 1018
port trunk permit vlan 1020 2012
bpdu-drop any
port link-aggregation group 8
#
interface Ten-GigabitEthernet2/0/29
port link-mode bridge
description Uplink Ring-Core8
port link-type trunk
port trunk permit vlan 1 10 24 31 56 70 118 120 124 140
port trunk permit vlan 160 168 200 208 240 330 400 809 811 1018
port trunk permit vlan 1020 2012
bpdu-drop any
port link-aggregation group 8
#

The status of the LACP trunk on the HPE A5500 is as follows;

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired

Aggregation Interface: Bridge-Aggregation8
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, 4431-9270-31bf
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
XGE1/0/30 S 32768 2 {ACDEFG}
XGE2/0/29 U 32768 2 {ACG}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
XGE1/0/30 0 32768 0 0x8000, 0000-0000-0000 {DEF}
XGE2/0/29 0 32768 0 0x8000, 0000-0000-0000 {DEF}

As it turns out, the LACP trunk won't establish because te setting 'bpdu-drop any' is configured on the 2 interfaces. If i remove these settings, the LACP trunk wil establish succesfully. However this is not a desired configuration, because we want to make sure no BPDU's will be processed bij the bridge-aggregation 8 interface on the HPE 5500.

The question now is, how can we filter/drop the STP BDPU's on the bridge-aggregation interface on the HPE 5500 IRF Stack? There is no command on the bridge-aggregation interface on the HPE 5500 to do so; on the Aruba side however this is possible by setting the command "spanning-tree priority 4 bpdu-filter"

I would greatly appriciate an answer or a possible solution from you in this matter.