zNetLaB › Guided labs › Enterprise
Static routing between two LANs
Enterprise Beginner 6 devices 5 checked tasks 70 points Free lab
Two routers, two switches, two PCs. Address the links, add static routes, prove reachability. 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 is a free lab: it stays open on the free plan. It needs an account, which keeps your progress.
The scenario
Two routers, two switches, two PCs. Address the links, add static routes, prove reachability.
Your role: a network engineer on the enterprise team. Level: Beginner Done when: all 5 goals show as passed (70 points).
Network status
Devices: 2 PCs, 2 switchs, 2 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. PC0 is a host with 192.168.1.10/24, gateway 192.168.1.1. PC1 is a host with 192.168.2.10/24, gateway 192.168.2.1. Switch0, Router0, Router1, Switch1 start 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
Router0 g0/0 = 192.168.1.1/24, up (10 pts) Router0 g0/1 = 10.0.0.1/30, up (10 pts) Router1 both interfaces addressed and up (15 pts) A route on each router to the far LAN (15 pts) PC0 can ping PC1 (20 pts) The activity, in order
Router0 g0/0 = 192.168.1.1/24, up Why: A router interface routes nothing until it has an address and is up. Every other task builds on this one. Verify with: show ip interface brief Router0 g0/1 = 10.0.0.1/30, up Why: A router interface routes nothing until it has an address and is up. Every other task builds on this one. Verify with: show ip interface brief Router1 both interfaces addressed and up Why: A router interface routes nothing until it has an address and is up. Every other task builds on this one. Verify with: show ip interface brief A route on each router to the far LAN Why: If the prefix is not in the routing table, the router drops packets for it, whatever else is configured. Verify with: show ip route PC0 can ping PC1 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.2.10 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. Why this matters
Two routers, two switches, two PCs. Address the links, add static routes, prove reachability.
What you will be able to do
Router0 g0/0 = 192.168.1.1/24, up
Router0 g0/1 = 10.0.0.1/30, up
Router1 both interfaces addressed and up
A route on each router to the far LAN
The network
PC, Switch 8-port, ISR 2911 — 6 devices in all, already cabled.
Fa0 Fa0/1 Fa0/2 Gi0/0 Gi0/1 Gi0/1 Gi0/0 Fa0/1 Fa0/2 Fa0 PC0 192.168.1.10/24 · gw 192.168.1.1 Switch0 Router0 Router1 Switch1 PC1 192.168.2.10/24 · gw 192.168.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
PC0 PC 192.168.1.10 / 255.255.255.0 gw 192.168.1.1 Switch0 Switch 8-port configure it Router0 ISR 2911 configure it Router1 ISR 2911 configure it Switch1 Switch 8-port configure it PC1 PC 192.168.2.10 / 255.255.255.0 gw 192.168.2.1
Cabling
PC0 Fa0 ↔ Switch0 Fa0/1 Switch0 Fa0/2 ↔ Router0 Gi0/0 Router0 Gi0/1 ↔ Router1 Gi0/1 Router1 Gi0/0 ↔ Switch1 Fa0/1 Switch1 Fa0/2 ↔ PC1 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 Router0 g0/0 = 192.168.1.1/24, up 10 On Router0: show ip interface brief — Gi0/0 has 192.168.1.1 and is up/up. 2 Router0 g0/1 = 10.0.0.1/30, up 10 On Router0: show ip interface brief — Gi0/1 has 10.0.0.1 and is up/up. 3 Router1 both interfaces addressed and up 15 On Router1: show ip interface brief — Gi0/1 has 10.0.0.2 and is up/up. and On Router1: show ip interface brief — Gi0/0 has 192.168.2.1 and is up/up. 4 A route on each router to the far LAN 15 On Router0: show ip route lists 192.168.2.0/24. and On Router1: show ip route lists 192.168.1.0/24. 5 PC0 can ping PC1 20 On PC0: ping 192.168.2.10 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
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:
Router0 interface g0/0
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 10.0.0.1 255.255.255.252
no shutdown
exit
ip route 192.168.2.0 255.255.255.0 10.0.0.2 Router1 interface g0/1
ip address 10.0.0.2 255.255.255.252
no shutdown
exit
interface g0/0
ip address 192.168.2.1 255.255.255.0
no shutdown
exit
ip route 192.168.1.0 255.255.255.0 10.0.0.1 Where this is examined
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.