zNetLaB › Guided labs › Enterprise
RIPv2 — distance-vector routing across three routers
Enterprise Beginner 5 devices 4 checked tasks 100 points Free lab
Three routers in a row, a LAN at each end, and no routes. Turn on RIP version 2, advertise the connected networks, switch off automatic summarisation so the /24s are not collapsed into a classful block, and watch the far LAN appear with a hop count. 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
Three routers in a row, a LAN at each end, and no routes. Turn on RIP version 2, advertise the connected networks, switch off automatic summarisation so the /24s are not collapsed into a classful block, and watch the far LAN appear with a hop count.
Your role: a network engineer on the enterprise team. Level: Beginner Done when: all 4 goals show as passed (100 points).
Network status
Devices: 3 routers, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with addresses (G0/0 10.1.0.1/24, G0/1 10.0.12.1/30). R2 starts with addresses (G0/0 10.0.12.2/30, G0/1 10.0.23.1/30). R3 starts with addresses (G0/0 10.0.23.2/30, G0/1 10.3.0.1/24). PC-West is a host with 10.1.0.10/24, gateway 10.1.0.1. PC-East is a host with 10.3.0.10/24, gateway 10.3.0.1. 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
RIP version 2 is running on all three routers (25 pts) Automatic summarisation is off (15 pts) R1 learns the east LAN 10.3.0.0/24 by RIP (30 pts) PC-West reaches PC-East (30 pts) The activity, in order
RIP version 2 is running on all three routers 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 Automatic summarisation is off 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 R1 learns the east LAN 10.3.0.0/24 by RIP Why: The code tells you HOW a route was learned, which tells you which process to look at if it is wrong. Verify with: show ip route PC-West reaches PC-East 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.3.0.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: Leaving version 1 on (no masks) Common mistake: A network statement that does not match the interface Common mistake: Expecting convergence in milliseconds — RIP is slow Why this matters
RIP is the simplest distance-vector protocol: hop count and periodic updates. Version 2 carries masks, so networks need not be classful — if automatic summarisation is turned off.
What you will be able to do
Enable RIPv2 and advertise connected networks
Turn off automatic summarisation
Read the RIP routes and hop counts
The network
ISR 2911, PC — 5 devices in all, already cabled.
Gi0/1 10.0.12.1/30 Gi0/0 10.0.12.2/30 Gi0/1 10.0.23.1/30 Gi0/0 10.0.23.2/30 Fa0 Gi0/0 10.1.0.1/24 Fa0 Gi0/1 10.3.0.1/24 R1 R2 R3 PC-West 10.1.0.10/24 · gw 10.1.0.1 PC-East 10.3.0.10/24 · gw 10.3.0.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R1 ISR 2911 configure it R2 ISR 2911 configure it R3 ISR 2911 configure it PC-West PC 10.1.0.10 / 255.255.255.0 gw 10.1.0.1 PC-East PC 10.3.0.10 / 255.255.255.0 gw 10.3.0.1
Cabling
R1 Gi0/1 ↔ R2 Gi0/0 R2 Gi0/1 ↔ R3 Gi0/0 PC-West Fa0 ↔ R1 Gi0/0 PC-East Fa0 ↔ R3 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:
R1 interface g0/0
ip address 10.1.0.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 10.0.12.1 255.255.255.252
no shutdown
exit R2 interface g0/0
ip address 10.0.12.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 10.0.23.1 255.255.255.252
no shutdown
exit R3 interface g0/0
ip address 10.0.23.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 10.3.0.1 255.255.255.0
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 version 2 is running on all three routers 25 On R1: show running-config contains the line(s) matching router rip[\s\S]*version 2. and On R2: show running-config contains the line(s) matching router rip[\s\S]*version 2. and On R3: show running-config contains the line(s) matching router rip[\s\S]*version 2. 2 Automatic summarisation is off 15 On R1: show running-config contains the line(s) matching no auto-summary. 3 R1 learns the east LAN 10.3.0.0/24 by RIP 30 On R1: show ip route lists 10.3.0.0/24 with code R. 4 PC-West reaches PC-East 30 On PC-West: ping 10.3.0.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
Leaving version 1 on (no masks)
A network statement that does not match the interface
Expecting convergence in milliseconds — RIP is slow
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:
R1 router rip
version 2
network 10.0.0.0
no auto-summary
exit R2 router rip
version 2
network 10.0.0.0
no auto-summary
exit R3 router rip
version 2
network 10.0.0.0
no auto-summary
exit Where this is examined
CCNA (routing basics), Network+ (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.