Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

LACP on 6100 vs 2930F

This thread has been viewed 67 times
  • 1.  LACP on 6100 vs 2930F

    Posted Jul 17, 2022 11:45 AM
    I have had a long time love for HPE/Aruba switches and found their CLI to be easy to understand and use. Just got a 6100 to see what the CX CLI was all about and found it in general very 'Ciscoy'. So - with that, I am confused on getting a Windows Server 2016+ configured with an LACP Team and the 6100.

    On the 2930, I simply:
    trunk 8,10 trk1 lacp

    interface 8
    name " VM NIC2"
    untagged vlan 1
    trunk trk1 lacp
    exit

    interface 10
    name "VM NIC1"
    untagged vlan 1
    trunk trk1 lacp
    exit

    interface Trk1
    tagged vlan 212,280,525,532,534,564,568,572,596
    untagged vlan 1
    spanning-tree priority 4
    exit

    I can then go into Windows and Create a Trunk, LACP, Hyper-V and it all works.

    On the 6100 I created a LAG:
    interface lag 1
    description Hyper-V
    no shutdown
    vlan trunk native 1
    vlan trunk allowed 212,280,525,532,534,564,568,572,596
    lacp mode active

    interface 1/1/3
    no shutdown
    lag 1

    interface 1/1/4
    no shutdown
    lag 1

    But in Windows, the trunk refuses to connect and switch reports "State information : Disabled by LACP or LAG"

    What magic needs to be done to get this to work?

    Appreciate the help -

    ------------------------------
    Brian Ricks
    ------------------------------


  • 2.  RE: LACP on 6100 vs 2930F

    MVP GURU
    Posted Jul 17, 2022 02:45 PM
    Hi! I would suggest you to add the native (untagged in HP jargon) VLAN Id to the vlan trunk allowed's VLAN Id(s) list.

    LAG configuration seems quite OK, are member interface administratively enabled? is the lag interface in no shut? was MTU set to 9198?


  • 3.  RE: LACP on 6100 vs 2930F

    Posted Jul 18, 2022 10:01 AM
    Thanks - all enabled and no, I hadn't set an MYU value - but I did on the member interfaces to see if that made a difference, it did not (is it a requirement for the CX?).

    ------------------------------
    Brian Ricks
    ------------------------------