HCIA-Datacom lab 11 of 22
Inter-VLAN routing with sub-interfaces and VLANIF
Route between VLANs two ways. First a router-on-a-stick with dot1q termination sub-interfaces, then a migration of the internal VLANs to VLANIF gateways on the CloudEngine switch, without touching a single PC. The guest VLAN stays on the router, and a transit VLAN with static routes ties the two together.
Run this lab
It needs Lite: its 5 nodes are set to 6 vCPU and 7,168 MB in total. That fits the free demo too.
In your workspace: Shared, then HCIA-Datacom H12-811 guided labs, then 11 - Inter-VLAN routing with sub-interfaces and VLANIF
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Northwind has three VLANs on its office switch SW1: Finance (10), Sales (20) and Guest (30). Every PC's gateway is the .254 address of its subnet. Today you'll first route between the VLANs on the router R1 over a single trunk (a "router-on-a-stick"). Then, because the trunk to R1 is becoming a bottleneck, you'll move Finance and Sales routing onto the switch itself. Guests stay on R1, where internet policy will later be enforced.
| Device | Interface | Address |
|---|---|---|
| R1 | GE0/0/0 (trunk to SW1 GE1/0/1) | sub-interfaces, see the tasks |
| R1 | LoopBack0 | 8.8.8.8/32 (the "internet") |
| PC1 / PC2 / PC3 | SW1 GE1/0/10 / GE1/0/11 / GE1/0/12 | .10 in VLAN 10 / 20 / 30, gateway .254 |
| Transit (after Task 4) | VLAN 100 | R1 10.0.0.1/30, SW1 Vlanif100 10.0.0.2/30 |
What you’ll practise
- Configure dot1q termination sub-interfaces on an AR router (router-on-a-stick)
- Configure VLANIF interfaces on a switch for Layer 3 switching
- Migrate gateways between devices without changing host configuration
- Use a transit VLAN and static routes between a Layer 3 switch and a router
The tasks
- VLANs and access ports on SW1
- Router-on-a-stick
- Plan the migration
- Migrate Finance and Sales
- Prove the new design
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
- R1
GE0/0/0to SW1GE1/0/1 - SW1
GE1/0/10to PC1eth0 - SW1
GE1/0/11to PC2eth0 - SW1
GE1/0/12to PC3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| SW1 | Huawei CloudEngine CE6800 | huaweice6800-bundled | 2 vCPU, 2,048 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC3 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HCIA-Datacom H12-811 guided labs.Open
11 - Inter-VLAN routing with sub-interfaces and VLANIFand 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 HCIA-Datacom labs
Related labs in other courses
CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.