zNetLaB › Guided labs › Enterprise
Junction with a tail 36 — RIP routing
Enterprise Intermediate 8 devices 4 checked tasks 49 points Plan lab
Scenario — Dhanbad is a junction with no LAN: Salem, Bhopal and the Thane–Kohima tail all meet there. Every interface is already addressed. Your job is the routing: use RIPv2 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
Dhanbad is a junction with no LAN: Salem, Bhopal and the Thane–Kohima tail all meet there. Every interface is already addressed. Your job is the routing: use RIPv2 so every office can reach every other.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 4 goals show as passed (49 points).
Network status
Devices: 5 routers, 3 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R-Salem starts with addresses (G0/0 10.55.1.1/24, G0/1 172.19.35.1/30). PC-Salem is a host with 10.55.1.10/24, gateway 10.55.1.1. R-Dhanbad starts with addresses (G0/0 172.19.35.2/30, G0/1 172.19.35.5/30, G0/2 172.19.35.9/30). R-Bhopal starts with addresses (G0/0 10.55.2.1/24, G0/1 172.19.35.6/30). PC-Bhopal is a host with 10.55.2.10/24, gateway 10.55.2.1. R-Thane starts with addresses (G0/0 172.19.35.10/30, G0/1 172.19.35.13/30). R-Kohima starts with addresses (G0/0 10.55.3.1/24, G0/1 172.19.35.14/30). PC-Kohima is a host with 10.55.3.10/24, gateway 10.55.3.1. Known problems
None: nothing is misconfigured. The routers are simply not finished: the goals list what has to be built. Goals
RIP is version 2 with no auto-summary on all 5 routers (15 pts) R-Salem learns 10.55.3.0/24 from the protocol (10 pts) 10.55.1.10 (Salem) reaches 10.55.3.10 (Kohima) (12 pts) 10.55.2.10 (Bhopal) reaches 10.55.1.10 (Salem) (12 pts) The activity, in order
Enable RIPv2 on each router and advertise its LAN and links; keep LAN ports passive. Why: This is the task that checks your configuration directly: the line must really be there, not just look right. Verify with: show running-config Read the routing table of every router and compare it with the plan. 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 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.55.3.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: Staying on version 1 (no masks) Common mistake: Forgetting no auto-summary Common mistake: Advertising only one of the classful networks in use Why this matters
RIP counts hops and repeats its whole table every thirty seconds. It is simple and old, and still examined because it shows distance-vector behaviour in its plainest form; version 2 carries masks, version 1 does not.
What you will be able to do
Enable RIPv2 with classful network statements
Turn off automatic summarisation
Spot a link network that is not advertised
The network
ISR 2911, PC — 8 devices in all, already cabled.
Fa0 Gi0/0 10.55.1.1/24 Fa0 Gi0/0 10.55.2.1/24 Fa0 Gi0/0 10.55.3.1/24 Gi0/1 172.19.35.1/30 Gi0/0 172.19.35.2/30 Gi0/1 172.19.35.5/30 Gi0/1 172.19.35.6/30 Gi0/2 172.19.35.9/30 Gi0/0 172.19.35.10/30 Gi0/1 172.19.35.13/30 Gi0/1 172.19.35.14/30 R-Salem PC-Salem 10.55.1.10/24 · gw 10.55.1.1 R-Dhanbad R-Bhopal PC-Bhopal 10.55.2.10/24 · gw 10.55.2.1 R-Thane R-Kohima PC-Kohima 10.55.3.10/24 · gw 10.55.3.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R-Salem ISR 2911 configure it PC-Salem PC 10.55.1.10 / 255.255.255.0 gw 10.55.1.1 R-Dhanbad ISR 2911 configure it R-Bhopal ISR 2911 configure it PC-Bhopal PC 10.55.2.10 / 255.255.255.0 gw 10.55.2.1 R-Thane ISR 2911 configure it R-Kohima ISR 2911 configure it PC-Kohima PC 10.55.3.10 / 255.255.255.0 gw 10.55.3.1
Cabling
PC-Salem Fa0 ↔ R-Salem Gi0/0 PC-Bhopal Fa0 ↔ R-Bhopal Gi0/0 PC-Kohima Fa0 ↔ R-Kohima Gi0/0 R-Salem Gi0/1 ↔ R-Dhanbad Gi0/0 R-Dhanbad Gi0/1 ↔ R-Bhopal Gi0/1 R-Dhanbad Gi0/2 ↔ R-Thane Gi0/0 R-Thane Gi0/1 ↔ R-Kohima 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-Salem interface g0/0
ip address 10.55.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.19.35.1 255.255.255.252
no shutdown
exit R-Dhanbad interface g0/0
ip address 172.19.35.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.19.35.5 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.19.35.9 255.255.255.252
no shutdown
exit R-Bhopal interface g0/0
ip address 10.55.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.19.35.6 255.255.255.252
no shutdown
exit R-Thane interface g0/0
ip address 172.19.35.10 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.19.35.13 255.255.255.252
no shutdown
exit R-Kohima interface g0/0
ip address 10.55.3.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.19.35.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 RIP is version 2 with no auto-summary on all 5 routers 15 On R-Salem: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Dhanbad: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Bhopal: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Thane: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Kohima: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. 2 R-Salem learns 10.55.3.0/24 from the protocol 10 On R-Salem: show ip route lists 10.55.3.0/24. 3 10.55.1.10 (Salem) reaches 10.55.3.10 (Kohima) 12 On PC-Salem: ping 10.55.3.10 must succeed. 4 10.55.2.10 (Bhopal) reaches 10.55.1.10 (Salem) 12 On PC-Bhopal: ping 10.55.1.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
Staying on version 1 (no masks)
Forgetting no auto-summary
Advertising only one of the classful networks in use
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-Salem router rip
version 2
no auto-summary
network 10.0.0.0
network 172.19.0.0
passive-interface GigabitEthernet0/0
exit R-Dhanbad router rip
version 2
no auto-summary
network 10.0.0.0
network 172.19.0.0
exit R-Bhopal router rip
version 2
no auto-summary
network 10.0.0.0
network 172.19.0.0
passive-interface GigabitEthernet0/0
exit R-Thane router rip
version 2
no auto-summary
network 10.0.0.0
network 172.19.0.0
exit R-Kohima router rip
version 2
no auto-summary
network 10.0.0.0
network 172.19.0.0
passive-interface GigabitEthernet0/0
exit Where this is examined
CCNA 3.0 routing fundamentals; Network+ 2.1 dynamic 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.