zNetLaB › Guided labs › Enterprise
Triangle 21 — OSPF build
Enterprise Intermediate 6 devices 11 checked tasks 106 points Plan lab
Scenario — Raipur, Mangaluru and Jalandhar are cabled in a triangle, so every office has two ways to every other. Nothing is configured. The address plan: LANs Raipur 10.40.1.0/24, Mangaluru 10.40.2.0/24, Jalandhar 10.40.3.0/24; links Raipur–Mangaluru 172.20.20.0/30, Mangaluru–Jalandhar 172.20.20.4/30, Jalandhar–Raipur 172.20.20.8/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 OSPF 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
Raipur, Mangaluru and Jalandhar are cabled in a triangle, so every office has two ways to every other. Nothing is configured. The address plan: LANs Raipur 10.40.1.0/24, Mangaluru 10.40.2.0/24, Jalandhar 10.40.3.0/24; links Raipur–Mangaluru 172.20.20.0/30, Mangaluru–Jalandhar 172.20.20.4/30, Jalandhar–Raipur 172.20.20.8/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 OSPF carry the routes.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 11 goals show as passed (106 points).
Network status
Devices: 3 routers, 3 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. PC-Raipur is a host with 10.40.1.10/24, gateway 10.40.1.1. PC-Mangaluru is a host with 10.40.2.10/24, gateway 10.40.2.1. PC-Jalandhar is a host with 10.40.3.10/24, gateway 10.40.3.1. R-Raipur, R-Mangaluru, R-Jalandhar 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-Raipur: g0/0 10.40.1.1/24, g0/1 172.20.20.1/30, g0/2 172.20.20.10/30 (8 pts) Address R-Mangaluru: g0/0 10.40.2.1/24, g0/1 172.20.20.2/30, g0/2 172.20.20.5/30 (8 pts) Address R-Jalandhar: g0/0 10.40.3.1/24, g0/1 172.20.20.6/30, g0/2 172.20.20.9/30 (8 pts) R-Raipur has 2 OSPF neighbours in FULL (8 pts) R-Mangaluru has 2 OSPF neighbours in FULL (8 pts) R-Jalandhar has 2 OSPF neighbours in FULL (8 pts) OSPF process 61, area 0, with router-IDs 1.1.1.1 … 3.3.3.3 and passive LAN ports (12 pts) R-Raipur learns 10.40.3.0/24 from the protocol (10 pts) 10.40.1.10 (Raipur) reaches 10.40.3.10 (Jalandhar) (12 pts) 10.40.2.10 (Mangaluru) reaches 10.40.1.10 (Raipur) (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 OSPF 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: OSPF routes only flow over a FULL adjacency. If a neighbour is stuck in INIT or EXSTART, compare the two ends’ settings. Verify with: show ip ospf neighbor 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: A subnet mask instead of a wildcard mask in a network statement Common mistake: Different area numbers on the two ends of a link Common mistake: Leaving the LAN port active so hellos leak to hosts Why this matters
OSPF routers exchange link-state advertisements and each builds the same map of the area, so a new LAN is found everywhere without touching the other routers. Neighbours form only when area, subnet and timers agree.
What you will be able to do
Enable OSPF with a router-id and network statements
Read neighbour state and the learned routes
Find an area mismatch
The network
ISR 2911, PC — 6 devices in all, already cabled.
Fa0 Gi0/0 Fa0 Gi0/0 Fa0 Gi0/0 Gi0/1 Gi0/1 Gi0/2 Gi0/1 Gi0/2 Gi0/2 R-Raipur PC-Raipur 10.40.1.10/24 · gw 10.40.1.1 R-Mangaluru PC-Mangaluru 10.40.2.10/24 · gw 10.40.2.1 R-Jalandhar PC-Jalandhar 10.40.3.10/24 · gw 10.40.3.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R-Raipur ISR 2911 configure it PC-Raipur PC 10.40.1.10 / 255.255.255.0 gw 10.40.1.1 R-Mangaluru ISR 2911 configure it PC-Mangaluru PC 10.40.2.10 / 255.255.255.0 gw 10.40.2.1 R-Jalandhar ISR 2911 configure it PC-Jalandhar PC 10.40.3.10 / 255.255.255.0 gw 10.40.3.1
Cabling
PC-Raipur Fa0 ↔ R-Raipur Gi0/0 PC-Mangaluru Fa0 ↔ R-Mangaluru Gi0/0 PC-Jalandhar Fa0 ↔ R-Jalandhar Gi0/0 R-Raipur Gi0/1 ↔ R-Mangaluru Gi0/1 R-Mangaluru Gi0/2 ↔ R-Jalandhar Gi0/1 R-Jalandhar Gi0/2 ↔ R-Raipur Gi0/2
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-Raipur: g0/0 10.40.1.1/24, g0/1 172.20.20.1/30, g0/2 172.20.20.10/30 8 On R-Raipur: show ip interface brief — Gi0/0 has 10.40.1.1 and is up/up. and On R-Raipur: show ip interface brief — Gi0/1 has 172.20.20.1 and is up/up. and On R-Raipur: show ip interface brief — Gi0/2 has 172.20.20.10 and is up/up. 2 Address R-Mangaluru: g0/0 10.40.2.1/24, g0/1 172.20.20.2/30, g0/2 172.20.20.5/30 8 On R-Mangaluru: show ip interface brief — Gi0/0 has 10.40.2.1 and is up/up. and On R-Mangaluru: show ip interface brief — Gi0/1 has 172.20.20.2 and is up/up. and On R-Mangaluru: show ip interface brief — Gi0/2 has 172.20.20.5 and is up/up. 3 Address R-Jalandhar: g0/0 10.40.3.1/24, g0/1 172.20.20.6/30, g0/2 172.20.20.9/30 8 On R-Jalandhar: show ip interface brief — Gi0/0 has 10.40.3.1 and is up/up. and On R-Jalandhar: show ip interface brief — Gi0/1 has 172.20.20.6 and is up/up. and On R-Jalandhar: show ip interface brief — Gi0/2 has 172.20.20.9 and is up/up. 4 R-Raipur has 2 OSPF neighbours in FULL 8 On R-Raipur: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 5 R-Mangaluru has 2 OSPF neighbours in FULL 8 On R-Mangaluru: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 6 R-Jalandhar has 2 OSPF neighbours in FULL 8 On R-Jalandhar: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 7 OSPF process 61, area 0, with router-IDs 1.1.1.1 … 3.3.3.3 and passive LAN ports 12 On R-Raipur: show running-config contains the line(s) matching router ospf 61[\s\S]*router-id 1\.1\.1\.1. and On R-Mangaluru: show running-config contains the line(s) matching router ospf 61[\s\S]*router-id 2\.2\.2\.2. and On R-Jalandhar: show running-config contains the line(s) matching router ospf 61[\s\S]*router-id 3\.3\.3\.3. 8 R-Raipur learns 10.40.3.0/24 from the protocol 10 On R-Raipur: show ip route lists 10.40.3.0/24. 9 10.40.1.10 (Raipur) reaches 10.40.3.10 (Jalandhar) 12 On PC-Raipur: ping 10.40.3.10 must succeed. 10 10.40.2.10 (Mangaluru) reaches 10.40.1.10 (Raipur) 12 On PC-Mangaluru: ping 10.40.1.10 must succeed. 11 Every LAN reaches every other LAN 12 On PC-Raipur: ping 10.40.2.10 must succeed. and On PC-Raipur: ping 10.40.3.10 must succeed. and On PC-Mangaluru: ping 10.40.1.10 must succeed. and On PC-Mangaluru: ping 10.40.3.10 must succeed. and On PC-Jalandhar: ping 10.40.1.10 must succeed. and On PC-Jalandhar: ping 10.40.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
A subnet mask instead of a wildcard mask in a network statement
Different area numbers on the two ends of a link
Leaving the LAN port active so hellos leak to hosts
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-Raipur interface g0/0
ip address 10.40.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.20.20.1 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.20.20.10 255.255.255.252
no shutdown
exit
router ospf 61
router-id 1.1.1.1
network 10.40.1.0 0.0.0.255 area 0
network 172.20.20.0 0.0.0.3 area 0
network 172.20.20.8 0.0.0.3 area 0
passive-interface GigabitEthernet0/0
exit R-Mangaluru interface g0/0
ip address 10.40.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.20.20.2 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.20.20.5 255.255.255.252
no shutdown
exit
router ospf 61
router-id 2.2.2.2
network 10.40.2.0 0.0.0.255 area 0
network 172.20.20.0 0.0.0.3 area 0
network 172.20.20.4 0.0.0.3 area 0
passive-interface GigabitEthernet0/0
exit R-Jalandhar interface g0/0
ip address 10.40.3.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.20.20.6 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.20.20.9 255.255.255.252
no shutdown
exit
router ospf 61
router-id 3.3.3.3
network 10.40.3.0 0.0.0.255 area 0
network 172.20.20.4 0.0.0.3 area 0
network 172.20.20.8 0.0.0.3 area 0
passive-interface GigabitEthernet0/0
exit Where this is examined
CCNA 3.0 OSPFv2; CCNP ENARSI OSPF.
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.