No, of course there are always 2 interfaces.
On the 5820 it is 1/0/24 and 2/0/24.
On the 5800 it is 1/0/13 and 1/0/14
On the 6000 it is 1/1/27 and 1/1/28
I also know that a trunk/lag/bag consists of at least two ports and the other ports are configured the same way.
On the Aruba 6000 I get the error message
sh lacp interfaces
State abbreviations :
A - Active P - Passive F - Aggregable I - Individual
S - Short-timeout L - Long-timeout N - InSync O - OutofSync
C - Collecting D - Distributing
X - State m/c expired E - Default neighbor state
Actor details of all interfaces:
----------------------------------------------------------------------------------
Intf Aggr Port Port State System-ID System Aggr Forwarding
Name Id Pri Pri Key State
----------------------------------------------------------------------------------
1/1/27 lag1 28 1 ALFOE ec:50:aa:81:b6:80 65534 1 lacp-block
1/1/28 lag1 29 1 ALFOE ec:50:aa:81:b6:80 65534 1 lacp-block
Partner details of all interfaces:
----------------------------------------------------------------------------------
Intf Aggr Port Port State System-ID System Aggr
Name Id Pri Pri Key
----------------------------------------------------------------------------------
1/1/27 lag1 0 0 PLFOEX 00:00:00:00:00:00 0 0
1/1/28 lag1 0 0 PLFOEX 00:00:00:00:00:00 0 0
Original Message:
Sent: Jun 07, 2023 03:49 PM
From: Davide Poletto
Subject: Trunk between Comware and Aruba OS-CX
It's not clear, are you trying to interlink a 5800 with ONE interface (member of a LAG with LACP) and an Aruba CX 6000 with TWO interfaces (members of LAG with LACP)? I expected a 2:2 LAGs (2 ports LAG with LACP to 2 ports LAG with LACP). Where is the second member port of Bridge-Aggregationx x logical interface if only one Ten-GigabitEthernet 1/0/24 is listed (or, at the end of your post, a GigabitEthernet 1/0/13 is listed). Then, starting with physical interfaces in their default states, the VLAN membership should be configured (imposed) only on the BAG (Bridge Aggregation Group) logical interface (that configuration propagates back to BAG member interfaces so you should not have mismatch between BAG and its member interfaces). Mismatch - at VLAN tagging level - between peer interfaces (5800 side and 6000 side) it's then another point BUT once you have the Native VLAN and the allowed VLAN list that are matching you should be good.
Original Message:
Sent: Jun 07, 2023 02:08 PM
From: Neonium
Subject: Trunk between Comware and Aruba OS-CX
I want to configure a trunk between a 5820/5800 and an Aruba 6000 switch.
Unfortunately this is my first Aruba OS-CX switch and I get my trunk configured between Comware and Aruba CX.
Just for information the 5800 is in a remote office where the Aruba 6000 should go. Here we have a 5820 where I wanted to test the Aruba 6000 first. Before I do not get the connection on site
Normally I configure the trunk under Comware like this
interface Ten-GigabitEthernet1/0/24
port link-mode bridge
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 200 240
port trunk pvid vlan 200
port link-aggregation group xx
dhcp-snooping trust
interface Bridge-Aggregationx x
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 200 240
port trunk pvid vlan 200
link-aggregation mode dynamic
dhcp-snooping trust
on the Aruba 6000 page I configured it like this
interface lag 1
description xxx
no shutdown
vlan trunk native 200
vlan trunk allowed 70,111,180,200,240
lacp mode active
dhcpv4-snooping trust
interface 1/1/27
no shutdown
lag 1
interface 1/1/28
no shutdown
lag 1
where is my mistake? except that the vlans do not fit
I have already configured the following on the 5800.
interface Bridge-Aggregation x
description xxx
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 70 180 200 240
port trunk pvid vlan 200
interface GigabitEthernet1/0/13
port link-mode bridge
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 70 111 180 200 240
port trunk pvid vlan 200
port link-aggregation group x