Aruba CX lab 11 of 16
Troubleshooting a campus with five planted faults
A branch was rebuilt over the weekend and nothing works properly: half the LAG is missing, one VLAN can't reach its gateway, the access switch can't be managed and nobody reaches the application server. Find and fix five planted faults on AOS-CX with a bottom-up method.
Run this lab
It needs Standard: its 5 nodes are set to 8 vCPU and 10,240 MB in total.
In your workspace: Shared, then HPE Aruba Networking CX switching guided labs, then 11 - Troubleshooting a campus with five planted faults
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 8 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Northwind's Leeds depot was re-cabled and re-configured over the weekend from a design that was correct. On Monday:
- staff PCs (VLAN 10, h10) can't reach their gateway or the application server 10.99.99.1;
- scanners (VLAN 20, h20) can't reach their gateway;
- the monitoring system can't reach acc1 on 10.0.99.2 and reports the uplink LAG as degraded.
There are five faults. Find each with evidence, fix it with the smallest change, and verify.
| Design item | Value |
|---|---|
| core1–acc1 | lag1 = 1/1/1 + 1/1/2 on both, LACP active, trunk native VLAN 1, allowed VLANs 10, 20, 99 |
| Gateways (core1) | vlan 10 10.10.10.1/24 · vlan 20 10.10.20.1/24 · vlan 99 10.0.99.1/24 |
| acc1 management | vlan 99 10.0.99.2/24, default route via 10.0.99.1 |
| core1–wan1 | 1/1/3 10.0.0.1/30 – wan1 1/1/1 10.0.0.2/30, OSPF area 0, point-to-point |
| wan1 | application server loopback 10.99.99.1/32 in OSPF |
| Hosts | h10 10.10.10.11/24 via 10.10.10.1 · h20 10.10.20.11/24 via 10.10.20.1 |
What you’ll practise
- Troubleshoot bottom-up: physical and LAG, VLANs and trunks, IP addressing, routing
- Use show lag, show lacp interfaces, show vlan, show interface and show ip ospf neighbors to localise faults
- Recognise VLAN, native VLAN and IP mismatches from their symptoms
- Write a remediation plan and verify each fix
The tasks
- Reproduce
- Links and the LAG
- VLANs and the trunk
- IP addressing
- Routing
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 acc11/1/2 - core1
1/1/3to wan11/1/1 - acc1
1/1/3to h10eth0 - acc1
1/1/4to h20eth0
| 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 |
| wan1 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| h10 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h20 | 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
11 - Troubleshooting a campus with five planted faultsand 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.