Aruba CX lab 2 of 16
VLANs and trunks with the native VLAN and LLDP
Split a flat network into VLANs on two AOS-CX switches, carry them over an 802.1Q trunk with a deliberate native VLAN, document the cabling with LLDP and read the MAC address table.
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 02 - VLANs and trunks with the native VLAN and LLDP
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 6 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Northwind Logistics' warehouse office is a single flat network. You'll introduce VLANs: users in VLAN 10, label printers in VLAN 20, and switch management in VLAN 99. The access switch acc1 connects to core1 with one cable that must carry all three VLANs, with management travelling untagged as the trunk's native VLAN. Routing between VLANs comes in lab 5; today is pure layer 2.
| Device | Port | Mode | VLANs | Connects to |
|---|---|---|---|---|
| core1 | 1/1/1 | trunk | native 99, allowed 10, 20, 99 | acc1 1/1/1 |
| core1 | 1/1/2 | access | 10 | h11 (10.10.10.11/24) |
| acc1 | 1/1/1 | trunk | native 99, allowed 10, 20, 99 | core1 1/1/1 |
| acc1 | 1/1/2 | access | 10 | h10 (10.10.10.10/24) |
| acc1 | 1/1/3 | access | 20 | (printer, not connected) |
| core1 / acc1 | VLAN 99 interface | – | 10.0.99.1/24 / 10.0.99.2/24 | – |
What you’ll practise
- Explain why AOS-CX ports may be routed by default and turn them into layer 2 ports
- Create named VLANs and assign access ports
- Build a trunk with a native VLAN and an allowed-VLAN list
- Manage a switch through a VLAN interface in the management VLAN
- Read LLDP neighbours, the VLAN table and the MAC address table
The tasks
- Look before you change: LLDP and port state
- Create the VLANs
- Access ports
- The trunk
- Management in VLAN 99
- Hosts and the MAC address table
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.
Every link, as text
- core1
1/1/1to acc11/1/1 - core1
1/1/2to h11eth0 - acc1
1/1/2to h10eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| core1 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| acc1 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| h11 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h10 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HPE Aruba Networking CX switching guided labs.Open
02 - VLANs and trunks with the native VLAN and LLDPand 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
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.