zNetLaB › Guided labs › Enterprise
Junction with a tail 11 — RIP build
Enterprise Intermediate 8 devices 10 checked tasks 101 points Plan lab
Scenario — Noida is a junction with no LAN: Lucknow, Panaji and the Nagpur–Mysuru tail all meet there. Nothing is configured. The address plan: LANs Lucknow 10.30.1.0/24, Panaji 10.30.2.0/24, Mysuru 10.30.3.0/24; links Lucknow–Noida 172.26.10.0/30, Noida–Panaji 172.26.10.4/30, Noida–Nagpur 172.26.10.8/30, Nagpur–Mysuru 172.26.10.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
Noida is a junction with no LAN: Lucknow, Panaji and the Nagpur–Mysuru tail all meet there. Nothing is configured. The address plan: LANs Lucknow 10.30.1.0/24, Panaji 10.30.2.0/24, Mysuru 10.30.3.0/24; links Lucknow–Noida 172.26.10.0/30, Noida–Panaji 172.26.10.4/30, Noida–Nagpur 172.26.10.8/30, Nagpur–Mysuru 172.26.10.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-Lucknow is a host with 10.30.1.10/24, gateway 10.30.1.1. PC-Panaji is a host with 10.30.2.10/24, gateway 10.30.2.1. PC-Mysuru is a host with 10.30.3.10/24, gateway 10.30.3.1. R-Lucknow, R-Noida, R-Panaji, R-Nagpur, R-Mysuru 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-Lucknow: g0/0 10.30.1.1/24, g0/1 172.26.10.1/30 (8 pts) Address R-Noida: g0/0 172.26.10.2/30, g0/1 172.26.10.5/30, g0/2 172.26.10.9/30 (8 pts) Address R-Panaji: g0/0 10.30.2.1/24, g0/1 172.26.10.6/30 (8 pts) Address R-Nagpur: g0/0 172.26.10.10/30, g0/1 172.26.10.13/30 (8 pts) Address R-Mysuru: g0/0 10.30.3.1/24, g0/1 172.26.10.14/30 (8 pts) RIP is version 2 with no auto-summary on all 5 routers (15 pts) R-Lucknow learns 10.30.3.0/24 from the protocol (10 pts) 10.30.1.10 (Lucknow) reaches 10.30.3.10 (Mysuru) (12 pts) 10.30.2.10 (Panaji) reaches 10.30.1.10 (Lucknow) (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-Lucknow PC-Lucknow 10.30.1.10/24 · gw 10.30.1.1 R-Noida R-Panaji PC-Panaji 10.30.2.10/24 · gw 10.30.2.1 R-Nagpur R-Mysuru PC-Mysuru 10.30.3.10/24 · gw 10.30.3.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R-Lucknow ISR 2911 configure it PC-Lucknow PC 10.30.1.10 / 255.255.255.0 gw 10.30.1.1 R-Noida ISR 2911 configure it R-Panaji ISR 2911 configure it PC-Panaji PC 10.30.2.10 / 255.255.255.0 gw 10.30.2.1 R-Nagpur ISR 2911 configure it R-Mysuru ISR 2911 configure it PC-Mysuru PC 10.30.3.10 / 255.255.255.0 gw 10.30.3.1
Cabling
PC-Lucknow Fa0 ↔ R-Lucknow Gi0/0 PC-Panaji Fa0 ↔ R-Panaji Gi0/0 PC-Mysuru Fa0 ↔ R-Mysuru Gi0/0 R-Lucknow Gi0/1 ↔ R-Noida Gi0/0 R-Noida Gi0/1 ↔ R-Panaji Gi0/1 R-Noida Gi0/2 ↔ R-Nagpur Gi0/0 R-Nagpur Gi0/1 ↔ R-Mysuru 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-Lucknow: g0/0 10.30.1.1/24, g0/1 172.26.10.1/30 8 On R-Lucknow: show ip interface brief — Gi0/0 has 10.30.1.1 and is up/up. and On R-Lucknow: show ip interface brief — Gi0/1 has 172.26.10.1 and is up/up. 2 Address R-Noida: g0/0 172.26.10.2/30, g0/1 172.26.10.5/30, g0/2 172.26.10.9/30 8 On R-Noida: show ip interface brief — Gi0/0 has 172.26.10.2 and is up/up. and On R-Noida: show ip interface brief — Gi0/1 has 172.26.10.5 and is up/up. and On R-Noida: show ip interface brief — Gi0/2 has 172.26.10.9 and is up/up. 3 Address R-Panaji: g0/0 10.30.2.1/24, g0/1 172.26.10.6/30 8 On R-Panaji: show ip interface brief — Gi0/0 has 10.30.2.1 and is up/up. and On R-Panaji: show ip interface brief — Gi0/1 has 172.26.10.6 and is up/up. 4 Address R-Nagpur: g0/0 172.26.10.10/30, g0/1 172.26.10.13/30 8 On R-Nagpur: show ip interface brief — Gi0/0 has 172.26.10.10 and is up/up. and On R-Nagpur: show ip interface brief — Gi0/1 has 172.26.10.13 and is up/up. 5 Address R-Mysuru: g0/0 10.30.3.1/24, g0/1 172.26.10.14/30 8 On R-Mysuru: show ip interface brief — Gi0/0 has 10.30.3.1 and is up/up. and On R-Mysuru: show ip interface brief — Gi0/1 has 172.26.10.14 and is up/up. 6 RIP is version 2 with no auto-summary on all 5 routers 15 On R-Lucknow: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Noida: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Panaji: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Nagpur: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. and On R-Mysuru: show running-config contains the line(s) matching router rip[\s\S]*version 2[\s\S]*no auto-summary. 7 R-Lucknow learns 10.30.3.0/24 from the protocol 10 On R-Lucknow: show ip route lists 10.30.3.0/24. 8 10.30.1.10 (Lucknow) reaches 10.30.3.10 (Mysuru) 12 On PC-Lucknow: ping 10.30.3.10 must succeed. 9 10.30.2.10 (Panaji) reaches 10.30.1.10 (Lucknow) 12 On PC-Panaji: ping 10.30.1.10 must succeed. 10 Every LAN reaches every other LAN 12 On PC-Lucknow: ping 10.30.2.10 must succeed. and On PC-Lucknow: ping 10.30.3.10 must succeed. and On PC-Panaji: ping 10.30.1.10 must succeed. and On PC-Panaji: ping 10.30.3.10 must succeed. and On PC-Mysuru: ping 10.30.1.10 must succeed. and On PC-Mysuru: ping 10.30.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-Lucknow interface g0/0
ip address 10.30.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.26.10.1 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.26.0.0
passive-interface GigabitEthernet0/0
exit R-Noida interface g0/0
ip address 172.26.10.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.26.10.5 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.26.10.9 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.26.0.0
exit R-Panaji interface g0/0
ip address 10.30.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.26.10.6 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.26.0.0
passive-interface GigabitEthernet0/0
exit R-Nagpur interface g0/0
ip address 172.26.10.10 255.255.255.252
no shutdown
exit
interface g0/1
ip address 172.26.10.13 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.26.0.0
exit R-Mysuru interface g0/0
ip address 10.30.3.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.26.10.14 255.255.255.252
no shutdown
exit
router rip
version 2
no auto-summary
network 10.0.0.0
network 172.26.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.