zNetLaB › Guided labs › Enterprise
Multilayer switch routing 26 — three VLANs, no router
Enterprise Intermediate 4 devices 4 checked tasks 100 points Plan lab
Scenario — the Hubli office bought a multilayer switch and wants to retire its router. Create VLANs 85, 86, 87 (Marketing, Cameras, Research), put each PC on its VLAN (Fa0/1 – Fa0/3), give every VLAN an SVI gateway at .1 of 192.168.45.0/24, 192.168.46.0/24 and 192.168.47.0/24, enable IP routing and show the departments reach each other through the switch alone. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
the Hubli office bought a multilayer switch and wants to retire its router. Create VLANs 85, 86, 87 (Marketing, Cameras, Research), put each PC on its VLAN (Fa0/1 – Fa0/3), give every VLAN an SVI gateway at .1 of 192.168.45.0/24, 192.168.46.0/24 and 192.168.47.0/24, enable IP routing and show the departments reach each other through the switch alone.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 4 goals show as passed (100 points).
Network status
Devices: 1 switch, 3 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. Marketing-PC is a host with 192.168.45.11/24, gateway 192.168.45.1. Cameras-PC is a host with 192.168.46.11/24, gateway 192.168.46.1. Research-PC is a host with 192.168.47.11/24, gateway 192.168.47.1. L3-Hubli starts with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
VLANs 85, 86, 87 exist and each PC port is in its own (25 pts) IP routing is on and each SVI is the gateway of its subnet (35 pts) Marketing reaches Cameras (20 pts) Research reaches Marketing and Cameras (20 pts)
The activity, in order
VLANs 85, 86, 87 exist and each PC port is in its own Create VLAN 85 on L3-Hubli (vlan 85, then name it). On L3-Hubli, put FastEthernet0/1 in VLAN 85: interface FastEthernet0/1, switchport mode access, switchport access vlan 85. Create VLAN 86 on L3-Hubli (vlan 86, then name it). On L3-Hubli, put FastEthernet0/2 in VLAN 86: interface FastEthernet0/2, switchport mode access, switchport access vlan 86.Why: A port assigned to a VLAN that does not exist carries nothing. Verify with: show vlan brief IP routing is on and each SVI is the gateway of its subnet Make sure ip routing is on for L3-Hubli (it is by default on a router; on a multilayer switch, ip routing must be typed). The configuration of L3-Hubli must contain the line: interface Vlan85[^!]*ip address 192.168.45.1. Type it in the right mode (global, interface or line) and check it appears. The configuration of L3-Hubli must contain the line: interface Vlan86[^!]*ip address 192.168.46.1. Type it in the right mode (global, interface or line) and check it appears. The configuration of L3-Hubli must contain the line: interface Vlan87[^!]*ip address 192.168.47.1. Type it in the right mode (global, interface or line) and check it appears.Why: Without it the device only switches and never routes between subnets. Verify with: show running-config | include ip routing Marketing reaches Cameras From Marketing-PC, ping 192.168.46.11. If it fails, walk the path hop by hop: gateway, then each router’s routing table, then the way back.Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 192.168.46.11 Research reaches Marketing and Cameras From Research-PC, ping 192.168.45.11. If it fails, walk the path hop by hop: gateway, then each router’s routing table, then the way back. From Research-PC, ping 192.168.46.11. If it fails, walk the path hop by hop: gateway, then each router’s routing table, then the way back.Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 192.168.45.11
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Common mistake: Forgetting ip routing — SVIs exist but nothing is routed Common mistake: An SVI that stays down because no port is active in its VLAN Common mistake: Hosts pointing at the wrong gateway
Why this matters
A multilayer switch routes between VLANs in hardware: each VLAN gets a switched virtual interface (SVI) that acts as the gateway, and ip routing turns the switch into a router. No trunk to an external router, no hairpin.
What you will be able to do
Create VLANs and SVIs
Enable ip routing on a multilayer switch
Verify inter-VLAN reachability
The network
Catalyst 3560-24PS, PC — 4 devices in all, already cabled.
Fa0/1 Fa0 Fa0/2 Fa0 Fa0/3 Fa0 L3-Hubli Marketing-PC 192.168.45.11/24 · gw 192.168.45.1 Cameras-PC 192.168.46.11/24 · gw 192.168.46.1 Research-PC 192.168.47.11/24 · gw 192.168.47.1 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
L3-Hubli Catalyst 3560-24PS configure it
Marketing-PC PC 192.168.45.11 / 255.255.255.0 gw 192.168.45.1
Cameras-PC PC 192.168.46.11 / 255.255.255.0 gw 192.168.46.1
Research-PC PC 192.168.47.11 / 255.255.255.0 gw 192.168.47.1
Cabling
L3-Hubli Fa0/1 ↔ Marketing-PC Fa0
L3-Hubli Fa0/2 ↔ Cameras-PC Fa0
L3-Hubli Fa0/3 ↔ Research-PC Fa0
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 VLANs 85, 86, 87 exist and each PC port is in its own 25 On L3-Hubli: show vlan brief lists VLAN 85. and On L3-Hubli: show vlan brief — Fa0/1 is an access port in VLAN 85. and On L3-Hubli: show vlan brief lists VLAN 86. and On L3-Hubli: show vlan brief — Fa0/2 is an access port in VLAN 86. and On L3-Hubli: show vlan brief lists VLAN 87. and On L3-Hubli: show vlan brief — Fa0/3 is an access port in VLAN 87.
2 IP routing is on and each SVI is the gateway of its subnet 35 On L3-Hubli: show ip route works (routing is enabled). and On L3-Hubli: show running-config contains the line(s) matching interface Vlan85 … ip address 192\.168\.45\.1 . and On L3-Hubli: show running-config contains the line(s) matching interface Vlan86 … ip address 192\.168\.46\.1 . and On L3-Hubli: show running-config contains the line(s) matching interface Vlan87 … ip address 192\.168\.47\.1 .
3 Marketing reaches Cameras 20 On Marketing-PC: ping 192.168.46.11 must succeed.
4 Research reaches Marketing and Cameras 20 On Research-PC: ping 192.168.45.11 must succeed. and On Research-PC: ping 192.168.46.11 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Common mistakes
Forgetting ip routing — SVIs exist but nothing is routed
An SVI that stays down because no port is active in its VLAN
Hosts pointing at the wrong gateway
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
L3-Hubli ip routing
vlan 85
name MARKETING
exit
interface fa0/1
switchport mode access
switchport access vlan 85
exit
interface vlan 85
ip address 192.168.45.1 255.255.255.0
no shutdown
exit
vlan 86
name CAMERAS
exit
interface fa0/2
switchport mode access
switchport access vlan 86
exit
interface vlan 86
ip address 192.168.46.1 255.255.255.0
no shutdown
exit
vlan 87
name RESEARCH
exit
interface fa0/3
switchport mode access
switchport access vlan 87
exit
interface vlan 87
ip address 192.168.47.1 255.255.255.0
no shutdown
exit
Where this is examined
CCNA 2.0 inter-VLAN routing; CCNP ENCOR Layer 3 switching.
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.