zNetLaB › Guided labs › Enterprise
Diamond, two paths 47 — default routes routing
Enterprise Intermediate 6 devices 5 checked tasks 52 points Plan lab
Scenario — Rajkot and Mangaluru are joined by two paths, one through Delhi and one through Raipur. Every interface is already addressed. Your job is the routing: use a default route design (default toward the head-end, specific routes only where needed) 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 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
Rajkot and Mangaluru are joined by two paths, one through Delhi and one through Raipur. Every interface is already addressed. Your job is the routing: use a default route design (default toward the head-end, specific routes only where needed) so every office can reach every other.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 5 goals show as passed (52 points).
Network status
Devices: 4 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, G0/2 172.30.46.5/30). PC-Rajkot is a host with 10.66.1.10/24, gateway 10.66.1.1. R-Delhi starts with addresses (G0/0 172.30.46.2/30, G0/1 172.30.46.9/30). R-Raipur starts with addresses (G0/0 172.30.46.6/30, G0/1 172.30.46.13/30). R-Mangaluru starts with addresses (G0/0 10.66.2.1/24, G0/1 172.30.46.10/30, G0/2 172.30.46.14/30). PC-Mangaluru 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: 2 routes — default via 172.30.46.1; 10.66.2.0/24 via 172.30.46.10 (8 pts) R-Raipur: 2 routes — default via 172.30.46.5; 10.66.2.0/24 via 172.30.46.14 (8 pts) R-Mangaluru: a route — default via 172.30.46.9 (8 pts) 10.66.1.10 (Rajkot) reaches 10.66.2.10 (Mangaluru) (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: The next hop must be an address on a directly connected subnet, or the route never enters the table. Verify with: show ip route 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: Pointing the default route at the wrong neighbour address Common mistake: Forgetting the head-end needs specific routes back to every branch Common mistake: Leaving a transit router without the routes to LANs beyond it Why this matters
A branch does not need to know every network. A default route toward the head-end handles everything unknown, while the head-end carries the specific routes — the standard hub-and-spoke design for small sites.
What you will be able to do
Choose between a default route and specific routes
Point a default route at the correct neighbour
Read the gateway of last resort in show ip route
The network
ISR 2911, PC — 6 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/0 172.30.46.2/30 Gi0/2 172.30.46.5/30 Gi0/0 172.30.46.6/30 Gi0/1 172.30.46.9/30 Gi0/1 172.30.46.10/30 Gi0/1 172.30.46.13/30 Gi0/2 172.30.46.14/30 R-Rajkot PC-Rajkot 10.66.1.10/24 · gw 10.66.1.1 R-Delhi R-Raipur R-Mangaluru PC-Mangaluru 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 R-Raipur ISR 2911 configure it R-Mangaluru ISR 2911 configure it PC-Mangaluru PC 10.66.2.10 / 255.255.255.0 gw 10.66.2.1
Cabling
PC-Rajkot Fa0 ↔ R-Rajkot Gi0/0 PC-Mangaluru Fa0 ↔ R-Mangaluru Gi0/0 R-Rajkot Gi0/1 ↔ R-Delhi Gi0/0 R-Rajkot Gi0/2 ↔ R-Raipur Gi0/0 R-Delhi Gi0/1 ↔ R-Mangaluru Gi0/1 R-Raipur Gi0/1 ↔ R-Mangaluru Gi0/2
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
interface g0/2
ip address 172.30.46.5 255.255.255.252
no shutdown
exit R-Delhi interface g0/0
ip address 172.30.46.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.30.46.9 255.255.255.252
no shutdown
exit R-Raipur interface g0/0
ip address 172.30.46.6 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.30.46.13 255.255.255.252
no shutdown
exit R-Mangaluru interface g0/0
ip address 10.66.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.30.46.10 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.30.46.14 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: 2 routes — default via 172.30.46.1; 10.66.2.0/24 via 172.30.46.10 8 On R-Delhi: show ip route 0.0.0.0 shows next hop 172.30.46.1. and On R-Delhi: show ip route 10.66.2.0 shows next hop 172.30.46.10. 3 R-Raipur: 2 routes — default via 172.30.46.5; 10.66.2.0/24 via 172.30.46.14 8 On R-Raipur: show ip route 0.0.0.0 shows next hop 172.30.46.5. and On R-Raipur: show ip route 10.66.2.0 shows next hop 172.30.46.14. 4 R-Mangaluru: a route — default via 172.30.46.9 8 On R-Mangaluru: show ip route 0.0.0.0 shows next hop 172.30.46.9. 5 10.66.1.10 (Rajkot) reaches 10.66.2.10 (Mangaluru) 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
Pointing the default route at the wrong neighbour address
Forgetting the head-end needs specific routes back to every branch
Leaving a transit router without the routes to LANs beyond it
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 0.0.0.0 0.0.0.0 172.30.46.1
ip route 10.66.2.0 255.255.255.0 172.30.46.10 R-Raipur ip route 0.0.0.0 0.0.0.0 172.30.46.5
ip route 10.66.2.0 255.255.255.0 172.30.46.14 R-Mangaluru ip route 0.0.0.0 0.0.0.0 172.30.46.9 Where this is examined
CCNA 3.0 default routing; CCNP ENARSI static routing.
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.