CloudLabBox
Try the free demo

Aruba CX lab 3 of 16

Link aggregation with static LAG and LACP

Join two AOS-CX switches with two cables safely: build a static LAG, convert it to LACP, tune the LACP rate and hash, and prove that a member failure doesn't interrupt traffic.

Run this lab

It needs Lite: its 4 nodes are set to 6 vCPU and 7,168 MB in total. That fits the free demo too.

In your workspace: Shared, then HPE Aruba Networking CX switching guided labs, then 03 - Link aggregation with static LAG and LACP

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Beginner
Time
About 45 minutes
Nodes need
6 vCPU, 7,168 MB
Smallest plan
Lite

The scenario

The two server-room switches at Northwind Logistics are joined by two cables to get 2 Gb/s and a spare path. Nobody has configured the links yet (they're still down). Your job: aggregate them so both carry traffic and either can fail, first with a static LAG, then with LACP, which is what you'd run in production.

DevicePortsPurpose
sw1, sw21/1/1, 1/1/2lag1, layer 2 trunk carrying VLAN 10
sw1, sw21/1/4h1 / h2, access VLAN 10 (already configured)
h1 / h2eth010.10.10.1/24 · 10.10.10.2/24

What you’ll practise

  • Explain why parallel layer 2 links need a LAG (or spanning tree) and why AOS-CX needs care here
  • Configure a static LAG and verify it with show lag
  • Convert it to LACP, read actor and partner state in show lacp interfaces
  • Change the LACP rate and the load-sharing hash
  • Test member-link failure

The tasks

  1. Why not just enable both cables?
  2. A static LAG
  3. Convert to LACP
  4. Tune the LAG
  5. Fail a member

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Link aggregation with static LAG and LACP4 nodes, 4 links. Every link is listed as text below the diagram.sw1sw2h1h21/1/4eth01/1/4eth01/1/11/1/11/1/21/1/2
4 nodes, with the interface names each link uses.
Every link, as text
  • sw1 1/1/1 to sw2 1/1/1
  • sw1 1/1/2 to sw2 1/1/2
  • sw1 1/1/4 to h1 eth0
  • sw2 1/1/4 to h2 eth0
Nodes in Link aggregation with static LAG and LACP, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
sw1Aruba AOS-CX virtual switcharubacx-10.142 vCPU, 3,072 MB
sw2Aruba AOS-CX virtual switcharubacx-10.142 vCPU, 3,072 MB
h1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder HPE Aruba Networking CX switching guided labs.

  3. Open 03 - Link aggregation with static LAG and LACP and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Aruba CX labs

All Aruba CX labs

Related labs in other courses

CloudLabBox is independent of Hewlett Packard Enterprise. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.