zNetLaB › Guided labs › Enterprise
Two-site 47 — static routes routing
Enterprise Beginner 4 devices 3 checked tasks 36 points Free lab
Scenario — Rajkot and Delhi are two offices joined by a single leased line. Every interface is already addressed. Your job is the routing: use static routes so every office can reach every other. 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
Rajkot and Delhi are two offices joined by a single leased line. Every interface is already addressed. Your job is the routing: use static routes so every office can reach every other.
Your role: a network engineer on the enterprise team. Level: Beginner Done when: all 3 goals show as passed (36 points).
Network status
Devices: 2 routers, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R-Rajkot starts with addresses (G0/0 10.66.1.1/24, G0/1 172.30.46.1/30). PC-Rajkot is a host with 10.66.1.10/24, gateway 10.66.1.1. R-Delhi starts with addresses (G0/0 10.66.2.1/24, G0/1 172.30.46.2/30). PC-Delhi is a host with 10.66.2.10/24, gateway 10.66.2.1. Known problems
None: nothing is misconfigured. The routers are simply not finished: the goals list what has to be built. Goals
R-Rajkot: a route — 10.66.2.0/24 via 172.30.46.2 (8 pts) R-Delhi: a route — 10.66.1.0/24 via 172.30.46.1 (8 pts) 10.66.1.10 (Rajkot) reaches 10.66.2.10 (Delhi) (20 pts) The activity, in order
On each router write a route for every network it does not touch, using its own neighbour as next hop. Why: The next hop must be an address on a directly connected subnet, or the route never enters the table. Verify with: show ip route Read the routing table of every router and compare it with the plan. Why: The next hop must be an address on a directly connected subnet, or the route never enters the table. Verify with: show ip route Ping from each LAN to every other LAN, in both directions. Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.66.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. Common mistake: Adding the route only one way — the ping leaves and never returns Common mistake: Using the far router’s address instead of the directly connected neighbour as next hop Common mistake: Forgetting a transit router in the middle of the chain Why this matters
A router only knows its connected networks. With static routes you write every other network in by hand — one next hop per destination — and the same must be done in the opposite direction or the reply is lost.
What you will be able to do
Work out the next hop toward each remote LAN from a diagram
Write ip route statements with the right prefix, mask and next hop
Explain why every router on the path needs the route
The network
ISR 2911, PC — 4 devices in all, already cabled.
Fa0 Gi0/0 10.66.1.1/24 Fa0 Gi0/0 10.66.2.1/24 Gi0/1 172.30.46.1/30 Gi0/1 172.30.46.2/30 R-Rajkot PC-Rajkot 10.66.1.10/24 · gw 10.66.1.1 R-Delhi PC-Delhi 10.66.2.10/24 · gw 10.66.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R-Rajkot ISR 2911 configure it PC-Rajkot PC 10.66.1.10 / 255.255.255.0 gw 10.66.1.1 R-Delhi ISR 2911 configure it PC-Delhi PC 10.66.2.10 / 255.255.255.0 gw 10.66.2.1
Cabling
PC-Rajkot Fa0 ↔ R-Rajkot Gi0/0 PC-Delhi Fa0 ↔ R-Delhi Gi0/0 R-Rajkot Gi0/1 ↔ R-Delhi Gi0/1
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
R-Rajkot interface g0/0
ip address 10.66.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.30.46.1 255.255.255.252
no shutdown
exit R-Delhi interface g0/0
ip address 10.66.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.30.46.2 255.255.255.252
no shutdown
exit 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 R-Rajkot: a route — 10.66.2.0/24 via 172.30.46.2 8 On R-Rajkot: show ip route 10.66.2.0 shows next hop 172.30.46.2. 2 R-Delhi: a route — 10.66.1.0/24 via 172.30.46.1 8 On R-Delhi: show ip route 10.66.1.0 shows next hop 172.30.46.1. 3 10.66.1.10 (Rajkot) reaches 10.66.2.10 (Delhi) 20 On PC-Rajkot: ping 10.66.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
Common mistakes
Adding the route only one way — the ping leaves and never returns
Using the far router’s address instead of the directly connected neighbour as next hop
Forgetting a transit router in the middle of the chain
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:
R-Rajkot ip route 10.66.2.0 255.255.255.0 172.30.46.2 R-Delhi ip route 10.66.1.0 255.255.255.0 172.30.46.1 Where this is examined
CCNA 3.0 static routing; Network+ 2.1 routing technologies.
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.