Wired Intelligent Edge

 View Only
last person joined: 17 hours ago 

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

2930f LACP vs 6200f LACP

This thread has been viewed 17 times
  • 1.  2930f LACP vs 6200f LACP

    Posted May 12, 2023 05:44 PM
    I am setting up my new network that consists of two 8325 VSX cores with MC-LAGs (LACP mode active) going to 6200f access layer stacks.  I also have several stacks of 2930f switches that I need to configure LACP on as well.  Given the 6200f config below, what would be the equivalent or best way to configure my 2930f stacks in Aruba OS?  I will be using ports 1/49 and 2/49 on my 3920f stacks.
    6200f Access Layer config:
    interface lag 35
        no shutdown
        no routing
        vlan trunk native 1
        vlan trunk allowed all
        lacp mode active
    interface 1/1/49
        description -- VLAN 35 lag to 8325-CORE-1 Port 1/1/47
        no shutdown
        mtu 9100
        lag 35
    interface 2/1/49
        description -- VLAN 35 lag to 8325-CORE-2 Port 1/1/47
        no shutdown
        mtu 9100
        lag 35

  • 2.  RE: 2930f LACP vs 6200f LACP

    Posted May 12, 2023 05:58 PM
    Hi! a simple trunk 1/47,2/47 trk<trunk-id> lacp should suffice.

    VLAN tagging of logical interface <trunk-id> (to match the Aruba 6200's posted configuration) and Jumbo frame settings should be configured as required, set as you  usually do on ArubaOS-Switch.

  • 3.  RE: 2930f LACP vs 6200f LACP

    Posted May 12, 2023 06:18 PM
    Would the VLAN tagging be done within each VLAN interface or would each VLAN be tagged within the Trk1 interface?

    VLAN 35
        tagged Trk1

    VLAN 36
        tagged Trk1


        tagged vlan 35-36

    Wm. Wayne DuBose
    Network Administrator

      (936) 633-5330
      3500 S 1st Street 
          Lufkin, TX 75904

    Confidentiality Notice: This e-mail message is confidential communication intended only for the named addressee, is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521, and is legally privileged. It may not be disclosed, republished or seen by anyone not the addressee. Unauthorized review, use, disclosure, distribution, or storage is strictly prohibited. If you are not the intended recipient, copying or forwarding of this communication is strictly prohibited, and you must delete this message and any copy of it (in any form) without disclosing it and contact the sender.  Angelina College accepts no liability for damage caused by any virus transmitted by this E-mail. Unless expressly stated in this e-mail, nothing in this message should be construed as a digital or electronic signature. *Consider the environment before printing.*

  • 4.  RE: 2930f LACP vs 6200f LACP

    Posted May 13, 2023 04:44 AM
    It's the same.

    I personally prefer the latter way only when I have to (un)configure a list of tagged VLAN Ids on a specific interface. The former way it's faster when you have to (un)configure the very same VLAN Id (tagged or untagged) on different interfaces (logical, physical, range, list). As you know the ProCurve heritage let us to deal with VLAN membership looking at it from two different point of views...AOS-CX is instead more interface centric with that regard.

  • 5.  RE: 2930f LACP vs 6200f LACP

    Posted May 15, 2023 03:05 PM

    So I would get the same result with it configured either way?

  • 6.  RE: 2930f LACP vs 6200f LACP

    Posted May 15, 2023 03:17 PM

    Try both ways and check each way output with:

    show vlans port ethernet Trk1 detail (as example)

    The VLAN tagging membership of the logical interface Trk1 shall be the same whatever configuration method you will apply.