Wired Intelligent Edge

Hi, I have 2 Aruba 2930F switches, configured as VSF (Switch 1 Commander, Switch 2 Standby).
I want to configure dynamic LACP trunk groups distributed between both. For example, a dynamic LACP trunk group of 4 physical ports formed by ports 1 and 2 in switch 1 and ports 1 and 2 in switch 2.
Is it possible to do this? Could someone tell me how?

 

This is my current configuration and list of ports:

hostname "Core-HV-Commander"
vsf
enable domain 9000
member 1
type "JL259A" mac-address 9cdc71-37da40
priority 255
link 1 1/23
link 1 name "I-Link1_1"
link 2 1/24
link 2 name "I-Link1_2"
exit
member 2
type "JL259A" mac-address 9cdc71-362fe0
priority 128
link 1 2/23
link 1 name "I-Link2_1"
link 2 2/24
link 2 name "I-Link2_2"
exit
port-speed 1g
exit
aruba-central disable
include-credentials
password manager user-name "manager" sha1
"6f2f6aad0e3d08acaa56fcae9ead3eb7ad259ed6"
time timezone -3
snmp-server community "public" unrestricted
snmpv3 engineid "00:00:00:0b:00:00:9c:dc:71:37:da:43"
vlan 1
name "DEFAULT_VLAN"
untagged 1/1-1/22,1/25-1/28,2/1-2/22,2/25-2/28
ip address 10.250.250.16 255.255.255.0
exit
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update

Flow Bcast
Port Total Bytes Total Frames Errors Rx Drops Tx Ctrl Limit
------------ -------------- -------------- --------- --------- ---- -----
1/1 8,448,200 8285 0 0 off 0
1/2 0 0 0 0 off 0
1/3 0 0 0 0 off 0
1/4 0 0 0 0 off 0
1/5 0 0 0 0 off 0
1/6 0 0 0 0 off 0
1/7 0 0 0 0 off 0
1/8 0 0 0 0 off 0
1/9 0 0 0 0 off 0
1/10 0 0 0 0 off 0
1/11 0 0 0 0 off 0
1/12 0 0 0 0 off 0
1/13 0 0 0 0 off 0
1/14 0 0 0 0 off 0
1/15 0 0 0 0 off 0
1/16 0 0 0 0 off 0
1/17 0 0 0 0 off 0
1/18 0 0 0 0 off 0
1/19 0 0 0 0 off 0
1/20 0 0 0 0 off 0
1/21 0 0 0 0 off 0
1/22 0 0 0 0 off 0
1/23 0 0 0 0 off 0
1/24 2,197,780,855 167,829,705 0 0 off 0
1/25 0 0 0 0 off 0
1/26 0 0 0 0 off 0
1/27 0 0 0 0 off 0
1/28 0 0 0 0 off 0
2/1 0 0 0 0 off 0
2/2 0 0 0 0 off 0
2/3 0 0 0 0 off 0
2/4 0 0 0 0 off 0
2/5 0 0 0 0 off 0
2/6 0 0 0 0 off 0
2/7 0 0 0 0 off 0
2/8 0 0 0 0 off 0
2/9 0 0 0 0 off 0
2/10 0 0 0 0 off 0
2/11 0 0 0 0 off 0
2/12 0 0 0 0 off 0
2/13 0 0 0 0 off 0
2/14 0 0 0 0 off 0
2/15 0 0 0 0 off 0
2/16 0 0 0 0 off 0
2/17 0 0 0 0 off 0
2/18 0 0 0 0 off 0
2/19 0 0 0 0 off 0
2/20 0 0 0 0 off 0
2/21 0 0 0 0 off 0
2/22 0 0 0 0 off 0
2/23 0 0 0 0 off 0
2/24 2,211,441,065 168,042,248 0 0 off 0
2/25 0 0 0 0 off 0
2/26 0 0 0 0 off 0
2/27 0 0 0 0 off 0
2/28 0 0 0 0 off 0

 

Thanks in advance

Gabriel

Cheers, what's the purpose of using Dynamic LACP versus Static LACP Port Trunking?

Pay attention to restrictions related to using Dynamic LACP (e.g. VLAN 1 untagged, becoming untagged member of other - non default - VLAN requires GVRP) versus Static LACP.

Anyway...if you really want to go down the Dynamic LACP route...commands below should suffice:

interface 1/1 lacp active
interface 1/2 lacp active
interface 2/1 lacp active
interface 2/2 lacp active

If instead you reconsider Static LACP and want to deploy it...use:

trunk 1/1,1/2,2/1,2/2 trkX lacp

where X is the (free) logical trunk port number to assign within your VSF. Then you can, if needed, change trkX untagged VLAN membership with a simple command inside the vlan Y context: trkX untagged (and trkX will become untagged member of VLAN Y).

Thanks @parnassus for response.

In my case I don't use VLANS. At the other end I have Hyper-V Server 2016 servers with NIC Teamings already configured as LACP Dynamic.
I noticed that it is necessary also after the configuration you mention, to specify the operational key to form the groups.
I add this information for future references:

# interface 1/1 lacp key 100
# interface 1/2 lacp key 100
# interface 2/1 lacp key 100
# interface 2/2 lacp key 100

The key value ranges from 0 to 65535.

 

Thanks again.

Gabriel

Personally, I setup few dozens of Static LACP Port Trunks (HP, HPE and Aruba) mainly used to form uplinks to Switches and Servers and never - repeat: never - it was necessary or required to manually change or assign Port Group Operational Key (even if that can be managed)...simply because the trunk command used to setup Ststic LACP trunks takes care about that...so my suggestion is still to give it a try and avoid Dynamic LACP if there isn't a valid reason to stick with it.

Ok, maybe I didn't see the operational key when I ran show lacp because I hadn't connected the ports yet. After connected they would have been assigned automatically. Or maybe by assigning them manually it shows them to me even when the ports are disconnected.
Regarding static trunk, I haven't used it before, because I understand that it is more prone to failures.
I could test them as well, configuring my NIC Teamings in static LACP and configuring my switches as you mentioned: trunk 1/1,1/2,2/1,2/2 trkX lacp
Do you think this would be enough?
Thank you very much
Gabriel

---

@neok wrote: Regarding static trunk, I haven't used it before, because I understand that it is more prone to failures.

Hi Gabriel, could you explain me what are pros/cons of using Dynamic LACP versus Static LACP (considering Dynamic/Static LACP as implemented on ArubaOS-Switch or HP ProVision NOS)?

 

Generally I see peers (Vendors) supporting simply LACP IEEE 802.3ad and the additional term Dynamic paired with LACP just means LACP as opposed to referring to Static (NON LACP...so without a Protocol)...but the fact that a vendor uses the Dynamic term this doesn't actually mean that it should be paired with an (Aruba/HP) Dynamic LACP implementation...at least this is my opinion.

---

@neok wrote:

Do you think this would be enough?

---

Yes, I think.