Mobility Hero Tutorials

Link Aggregation (LACP) on Aruba Controller - Jan 2014

Super Contributor II

Tutorial by Hendrik

Hi All

 

In a lot of instances your single 1Gb or even 10Gb (if your lucky) uplink from your Controller to your switching infrastructure would be sufficient, but as you grow and you add more APs and users this single link can become a problem regarding Bandwidth availability and reliability. Fortunately with LACP you can aggregate multiple links to act as a single uplink to provide you redundancy and greater bandwidth.

 

In the below example I will show you how to configure LACP from your controller and what will be required from your switching side.

 

Please note that during LACP configuration if BOTH the Switch and the Controllers Ports aren't configured with the same LACP config you will loose connectivity to the Controller - hence we 1st Configure the Controller, as and when the controller is configured with LACP and your switch is not the controller will disconnect. On the switch we will continue to configure the LACP which will complete the LACP configuration and the controller will become accessible. Of course if you have redundant Controllers setup you shouldn't experience any problems from the AP or User perspective as failover should occur on the controllers.

 

So lets Begin

 

  1. Login to your Controller, then select the "Configuration Tab" and select "Ports"
    Conf-Ports.jpg

  2. With your relevant port selected (remember to repeat these steps on all ports who should belong to the aggregated link), scroll down to the LACP section and set the following options:
    Group: 1                  <This is the ID of the Port Channel -- must be same for all ports in the same group>
    Mode: Active            <You can set the mode Active or Passive for the receiving and sending of LACPDU to and from the switch>
    Priority: 2                  <Priority of Port within the Group>
    Timeout: Short        <Period before the port will be disabled in the Group>
    LACP.JPG

    NOTE: With Mode I prefer to set all Links to Active (getting and making use of all available Link Bandwidth), however this largely depends on the switching infrastructure if it supports Active/Active links.

    Hit Apply for Changes to be saved

  3. Next select the "Port-Channel" tab at the top and Highlight all the ports that need to be included in the Group.
    PortChannel.jpg

  4. Ensure the Port-Channel ID is selected and set to the correct number - the same as you configured in step 2 under Group.
  5. Set all required VLAN, SPT and FW policies - this will override what is on the individual ports
  6. Hit Apply - you would likely have lost connectivity due to the switch not being configured.

Below are a few short examples of possible switch configurations you can consider

 

CISCO

interface Port-channel1
switchport
switchport access vlan 100
switchport mode access
no ip address
!
interface GigabitEthernet1/1
switchport
switchport access vlan 100
switchport mode access
no ip address
channel-group 1 mode on
!

VERIFY THAT IT WORKS

Switch# show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-dst-ip
mpls label-ip
EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address
MPLS: Label or IP

Switch# show etherchannel summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----------+--------------------------
1 Po1(SU) - Gi1/15(P) Gi1/16(P)
2 Po2(SU) - Gi1/1(P) Gi1/2(P)

Switch# show etherchannel protocol
Channel-group listing:
-----------------------
Group: 1
----------
Protocol: - (Mode ON)
Group: 2
----------
Protocol: - (Mode ON)

 

HP

ProCurve# conf
ProCurve# trunk 10-13 Trk1 Trunk

VERIFY THAT IT WORKED

ProCurve# show trunk
Load Balancing
Port | Name Type | Group Type
---- + --------- + ----- -----
10 | 100/1000T | Trk1 Trunk
11 | 100/1000T | Trk1 Trunk
12 | 100/1000T | Trk1 Trunk
13 | 100/1000T | Trk1 Trunk

 

 ARISTA

Arista#
Arista#configure terminal
Arista(config)#interface port-Channel 50
Arista(config-if-Po50)#exit
Arista(config)#interface ethernet 50 - 51
Arista(config-if-Et50-51)#channel-group 50 mode active
Arista(config-if-Et50-51)#exit

VERIFY THAT IT WORKED

Arista#show port-channel detailed
Port Channel Port-Channel50:
Active Ports:
Port            Time became active      Protocol      Mode
--------------- ---------------------- -------------- ------
Ethernet50      16:46:00                LACP          Active
Ethernet51      16:46:00                LACP          Active

 

Version history
Revision #:
1 of 1
Last update:
‎02-26-2014 08:10 AM
Updated by:
 
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.