zNetLaB › Guided labs › Enterprise
Junction with a tail 38 — RIP build
Enterprise Intermediate 8 devices 10 checked tasks 101 points Plan lab
Scenario — Jalandhar is a junction with no LAN: Mangaluru, Kochi and the Gurugram–Ajmer tail all meet there. Nothing is configured. The address plan: LANs Mangaluru 10.57.1.0/24, Kochi 10.57.2.0/24, Ajmer 10.57.3.0/24; links Mangaluru–Jalandhar 172.21.37.0/30, Jalandhar–Kochi 172.21.37.4/30, Jalandhar–Gurugram 172.21.37.8/30, Gurugram–Ajmer 172.21.37.12/30. Give every router interface its address (the router takes .1 of its LAN, the first address of a /30 goes to the lower-numbered router), then make RIPv2 carry the routes. 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
Jalandhar is a junction with no LAN: Mangaluru, Kochi and the Gurugram–Ajmer tail all meet there. Nothing is configured. The address plan: LANs Mangaluru 10.57.1.0/24, Kochi 10.57.2.0/24, Ajmer 10.57.3.0/24; links Mangaluru–Jalandhar 172.21.37.0/30, Jalandhar–Kochi 172.21.37.4/30, Jalandhar–Gurugram 172.21.37.8/30, Gurugram–Ajmer 172.21.37.12/30. Give every router interface its address (the router takes .1 of its LAN, the first address of a /30 goes to the lower-numbered router), then make RIPv2 carry the routes.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 10 goals show as passed (101 points).
Network status
Devices: 5 routers, 3 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. PC-Mangaluru is a host with 10.57.1.10/24, gateway 10.57.1.1. PC-Kochi is a host with 10.57.2.10/24, gateway 10.57.2.1. PC-Ajmer is a host with 10.57.3.10/24, gateway 10.57.3.1. R-Mangaluru, R-Jalandhar, R-Kochi, R-Gurugram, R-Ajmer start with an empty configuration. Known problems
None: nothing is misconfigured. The routers are simply not finished: the goals list what has to be built. Goals
Address R-Mangaluru: g0/0 10.57.1.1/24, g0/1 172.21.37.1/30 (8 pts) Address R-Jalandhar: g0/0 172.21.37.2/30, g0/1 172.21.37.5/30, g0/2 172.21.37.9/30 (8 pts) Address R-Kochi: g0/0 10.57.2.1/24, g0/1 172.21.37.6/30 (8 pts) Address R-Gurugram: g0/0 172.21.37.10/30, g0/1 172.21.37.13/30 (8 pts) Address R-Ajmer: g0/0 10.57.3.1/24, g0/1 172.21.37.14/30 (8 pts) RIP is version 2 with no auto-summary on all 5 routers (15 pts) R-Mangaluru learns 10.57.3.0/24 from the protocol (10 pts) 10.57.1.10 (Mangaluru) reaches 10.57.3.10 (Ajmer) (12 pts) 10.57.2.10 (Kochi) reaches 10.57.1.10 (Mangaluru) (12 pts) Every LAN reaches every other LAN (12 pts) The activity, in order
Address every interface from the plan: each router task lists its ports and addresses. 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 Enable RIPv2 on each router and advertise its LAN and links; keep LAN ports passive. 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 Read the routing table of every router and compare it with the plan. 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 Ping from each LAN to every other LAN, in both directions. 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 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 Fa0 Gi0/0 Fa0 Gi0/0 Gi0/1 Gi0/0 Gi0/1 Gi0/1 Gi0/2 Gi0/0 Gi0/1 Gi0/1 R-Mangaluru PC-Mangaluru 10.57.1.10/24 · gw 10.57.1.1 R-Jalandhar R-Kochi PC-Kochi 10.57.2.10/24 · gw 10.57.2.1 R-Gurugram R-Ajmer PC-Ajmer 10.57.3.10/24 · gw 10.57.3.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R-Mangaluru ISR 2911 configure it PC-Mangaluru PC 10.57.1.10 / 255.255.255.0 gw 10.57.1.1 R-Jalandhar ISR 2911 configure it R-Kochi ISR 2911 configure it PC-Kochi PC 10.57.2.10 / 255.255.255.0 gw 10.57.2.1 R-Gurugram ISR 2911 configure it R-Ajmer ISR 2911 configure it PC-Ajmer PC 10.57.3.10 / 255.255.255.0 gw 10.57.3.1
Cabling
PC-Mangaluru Fa0 ↔ R-Mangaluru Gi0/0 PC-Kochi Fa0 ↔ R-Kochi Gi0/0 PC-Ajmer Fa0 ↔ R-Ajmer Gi0/0 R-Mangaluru Gi0/1 ↔ R-Jalandhar Gi0/0 R-Jalandhar Gi0/1 ↔ R-Kochi Gi0/1 R-Jalandhar Gi0/2 ↔ R-Gurugram Gi0/0 R-Gurugram Gi0/1 ↔ R-Ajmer Gi0/1
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 Address R-Mangaluru: g0/0 10.57.1.1/24, g0/1 172.21.37.1/30 8 On R-Mangaluru: show ip interface brief — Gi0/0 has 10.57.1.1 and is up/up. and On R-Mangaluru: show ip interface brief — Gi0/1 has 172.21.37.1 and is up/up. 2 Address R-Jalandhar: g0/0 172.21.37.2/30, g0/1 172.21.37.5/30, g0/2 172.21.37.9/30 8 On R-Jalandhar: show ip interface brief — Gi0/0 has 172.21.37.2 and is up/up. and On R-Jalandhar: show ip interface brief — Gi0/1 has 172.21.37.5 and is up/up. and On R-Jalandhar: show ip interface brief — Gi0/2 has 172.21.37.9 and is up/up. 3 Address R-Kochi: g0/0 10.57.2.1/24, g0/1 172.21.37.6/30 8 On R-Kochi: show ip interface brief — Gi0/0 has 10.57.2.1 and is up/up. and On R-Kochi: show ip interface brief — Gi0/1 has 172.21.37.6 and is up/up. 4 Address R-Gurugram: g0/0 172.21.37.10/30, g0/1 172.21.37.13/30 8 On R-Gurugram: show ip interface brief — Gi0/0 has 172.21.37.10 and is up/up. and On R-Gurugram: show ip interface brief — Gi0/1 has 172.21.37.13 and is up/up. 5 Address R-Ajmer: g0/0 10.57.3.1/24, g0/1 172.21.37.14/30 8 On R-Ajmer: show ip interface brief — Gi0/0 has 10.57.3.1 and is up/up. and On R-Ajmer: show ip interface brief — Gi0/1 has 172.21.37.14 and is up/up. 6 RIP is version 2 with no auto-summary on all 5 routers 15 On R-Mangaluru: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Jalandhar: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Kochi: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Gurugram: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Ajmer: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. 7 R-Mangaluru learns 10.57.3.0/24 from the protocol 10 On R-Mangaluru: show ip route lists 10.57.3.0/24. 8 10.57.1.10 (Mangaluru) reaches 10.57.3.10 (Ajmer) 12 On PC-Mangaluru: ping 10.57.3.10 must succeed. 9 10.57.2.10 (Kochi) reaches 10.57.1.10 (Mangaluru) 12 On PC-Kochi: ping 10.57.1.10 must succeed. 10 Every LAN reaches every other LAN 12 On PC-Mangaluru: ping 10.57.2.10 must succeed. and On PC-Mangaluru: ping 10.57.3.10 must succeed. and On PC-Kochi: ping 10.57.1.10 must succeed. and On PC-Kochi: ping 10.57.3.10 must succeed. and On PC-Ajmer: ping 10.57.1.10 must succeed. and On PC-Ajmer: ping 10.57.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
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-Mangaluru interface g0/0
ip address 10.57.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.21.37.1 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.21.0.0
passive-interface GigabitEthernet0/0
exit R-Jalandhar interface g0/0
ip address 172.21.37.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.21.37.5 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.21.37.9 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.21.0.0
exit R-Kochi interface g0/0
ip address 10.57.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.21.37.6 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.21.0.0
passive-interface GigabitEthernet0/0
exit R-Gurugram interface g0/0
ip address 172.21.37.10 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.21.37.13 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.21.0.0
exit R-Ajmer interface g0/0
ip address 10.57.3.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.21.37.14 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.21.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.