CloudLabBox
Try the free demo

CCNA lab 14 of 46

EtherChannel with LACP: Layer 2 and Layer 3

Stop spanning tree wasting a second uplink by bundling it into a Layer 2 LACP port channel, break the bundle on purpose and read why, then build a routed Layer 3 port channel between two distribution switches.

Run this lab

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

In your workspace: Shared, then CCNA 200-301 guided labs, then 14 - EtherChannel with LACP - Layer 2 and Layer 3

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
Intermediate
Time
About 55 minutes
Nodes need
4 vCPU, 4,096 MB
Smallest plan
Lite

The scenario

Brookfield Data's access switch (ASW1) has two cables to the distribution switch (DSW1), but users still see the bandwidth of one, and DSW1 has two cables to the second distribution switch (DSW2) that the network team wants to route over. You'll bundle each pair into an EtherChannel with LACP: a Layer 2 trunk bundle at the access layer and a routed bundle between the distribution switches.

DeviceInterfacesRole / address
ASW1Gi0/0, Gi0/1uplinks to DSW1 → Port-channel1 (Layer 2 trunk)
ASW1Gi1/0PC1, VLAN 10
DSW1Gi0/0, Gi0/1downlinks to ASW1 → Port-channel1
DSW1Gi0/2, Gi0/3to DSW2 → Port-channel2, 10.0.12.1/30 (routed)
DSW1SVI VLAN 1010.14.10.1/24 (PC1's gateway)
DSW2Gi0/2, Gi0/3to DSW1 → Port-channel2, 10.0.12.2/30 (routed)
DSW2Loopback010.255.255.2/32 (server)
PC1eth010.14.10.10/24

What you’ll practise

  • Explain why parallel links need EtherChannel
  • Build a Layer 2 LACP port channel and configure the trunk on the port-channel interface
  • Diagnose a member that won't bundle from show etherchannel summary and the logs
  • Choose a load-balancing method and explain how traffic is spread
  • Build a Layer 3 LACP port channel with an IP address

The tasks

  1. See why parallel links need EtherChannel
  2. Build the Layer 2 bundle with LACP
  3. Break a member on purpose and read the evidence
  4. Choose how traffic is shared
  5. Build the Layer 3 bundle
  6. Compare the protocols

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 EtherChannel with LACP - Layer 2 and Layer 34 nodes, 5 links. Every link is listed as text below the diagram.ASW1DSW1DSW2PC1Gi1/0eth0Gi0/2Gi0/2Gi0/3Gi0/3Gi0/0Gi0/0Gi0/1Gi0/1
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • ASW1 Gi0/0 to DSW1 Gi0/0
  • ASW1 Gi0/1 to DSW1 Gi0/1
  • DSW1 Gi0/2 to DSW2 Gi0/2
  • DSW1 Gi0/3 to DSW2 Gi0/3
  • ASW1 Gi1/0 to PC1 eth0
Nodes in EtherChannel with LACP: Layer 2 and Layer 3, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
ASW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 1,024 MB
DSW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 1,024 MB
DSW2Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 1,024 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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 CCNA 200-301 guided labs.

  3. Open 14 - EtherChannel with LACP - Layer 2 and Layer 3 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 CCNA labs

All CCNA labs

Related labs in other courses

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