CloudLabBox
Try the free demo

Network+ lab 6 of 27

Inter-VLAN routing: router-on-a-stick and SVIs

Route between VLANs two ways in one design: switched virtual interfaces on a layer 3 switch for the staff VLANs, and router-on-a-stick subinterfaces on the edge router for the guest VLAN. You join them with a transit VLAN and static routes and trace the paths.

Run this lab

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

In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 06 - Inter-VLAN routing - router-on-a-stick and SVIs

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 50 minutes
Nodes need
5 vCPU, 4,352 MB
Smallest plan
Lite

The scenario

The head-office VLANs from lab 05 work, but Sales and Accounts can't reach each other, the guest kiosk can't reach anything, and nobody can reach the internet. The design team has decided:

  • Staff VLANs (10 Sales, 20 Accounts) are routed by the layer 3 switch SW1, close to the users and fast.
  • The guest VLAN (30) is routed by the edge router R1, where security policy will later be applied. R1 uses router-on-a-stick: one physical trunk with a subinterface per VLAN.
  • SW1 and R1 exchange traffic over a small transit VLAN 100 on the same trunk.
DeviceInterfaceAddressNotes
SW1Vlan1010.10.10.1/24Sales gateway
SW1Vlan2010.10.20.1/24Accounts gateway
SW1Vlan10010.0.100.2/30transit to R1
R1Gi0/0.3010.10.30.1/24Guest gateway, VLAN 30
R1Gi0/0.10010.0.100.1/30transit to SW1, VLAN 100
R1Loopback0203.0.113.1/32"internet"
PC1 / PC2 / PC3eth0.10 / .20 / .30 in VLAN 10 / 20 / 30gateways are .1

What you’ll practise

  • Explain why VLANs need a layer 3 device to talk to each other
  • Configure 802.1Q subinterfaces on a router (router-on-a-stick)
  • Enable IP routing on a layer 3 switch and route with SVIs
  • Join two routing points with a transit VLAN, a default route and static routes
  • Compare the hop counts and trade-offs of each method

The tasks

  1. See why VLANs need routing
  2. Route the guest VLAN with router-on-a-stick
  3. Route the staff VLANs with SVIs
  4. Join the two routing points
  5. Trace and compare

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 Inter-VLAN routing - router-on-a-stick and SVIs5 nodes, 4 links. Every link is listed as text below the diagram.R1SW1PC1PC2PC3Gi0/0Gi0/0Gi0/2eth0Gi0/1eth0Gi0/3eth0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 Gi0/0 to SW1 Gi0/0
  • SW1 Gi0/1 to PC1 eth0
  • SW1 Gi0/2 to PC2 eth0
  • SW1 Gi0/3 to PC3 eth0
Nodes in Inter-VLAN routing: router-on-a-stick and SVIs, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
SW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 768 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC3VPCS 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 CompTIA Network Plus N10-009 guided labs.

  3. Open 06 - Inter-VLAN routing - router-on-a-stick and SVIs 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 Network+ labs

All Network+ labs

Related labs in other courses

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