zNetLaB › Guided labs › Enterprise
Triangle 49 — OSPF routing
Enterprise Beginner 6 devices 7 checked tasks 70 points Free lab
Scenario — Kolhapur, Kolkata and Shimla are cabled in a triangle, so every office has two ways to every other. Every interface is already addressed. Your job is the routing: use OSPF 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 is a free lab: it stays open on the free plan. It needs an account, which keeps your progress.
The scenario
Kolhapur, Kolkata and Shimla are cabled in a triangle, so every office has two ways to every other. Every interface is already addressed. Your job is the routing: use OSPF so every office can reach every other.
Your role: a network engineer on the enterprise team. Level: Beginner Done when: all 7 goals show as passed (70 points).
Network status
Devices: 3 routers, 3 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R-Kolhapur starts with addresses (G0/0 10.68.1.1/24, G0/1 172.16.48.1/30, G0/2 172.16.48.10/30). PC-Kolhapur is a host with 10.68.1.10/24, gateway 10.68.1.1. R-Kolkata starts with addresses (G0/0 10.68.2.1/24, G0/1 172.16.48.2/30, G0/2 172.16.48.5/30). PC-Kolkata is a host with 10.68.2.10/24, gateway 10.68.2.1. R-Shimla starts with addresses (G0/0 10.68.3.1/24, G0/1 172.16.48.6/30, G0/2 172.16.48.9/30). PC-Shimla is a host with 10.68.3.10/24, gateway 10.68.3.1. Known problems
None: nothing is misconfigured. The routers are simply not finished: the goals list what has to be built. Goals
R-Kolhapur has 2 OSPF neighbours in FULL (8 pts) R-Kolkata has 2 OSPF neighbours in FULL (8 pts) R-Shimla has 2 OSPF neighbours in FULL (8 pts) OSPF process 55, area 0, with router-IDs 1.1.1.1 … 3.3.3.3 and passive LAN ports (12 pts) R-Kolhapur learns 10.68.3.0/24 from the protocol (10 pts) 10.68.1.10 (Kolhapur) reaches 10.68.3.10 (Shimla) (12 pts) 10.68.2.10 (Kolkata) reaches 10.68.1.10 (Kolhapur) (12 pts) The activity, in order
Enable OSPF on each router and advertise its LAN and links; keep LAN ports passive. 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 Read the routing table of every router and compare it with the plan. 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 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 10.68.1.1/24 Fa0 Gi0/0 10.68.2.1/24 Fa0 Gi0/0 10.68.3.1/24 Gi0/1 172.16.48.1/30 Gi0/1 172.16.48.2/30 Gi0/2 172.16.48.5/30 Gi0/1 172.16.48.6/30 Gi0/2 172.16.48.9/30 Gi0/2 172.16.48.10/30 R-Kolhapur PC-Kolhapur 10.68.1.10/24 · gw 10.68.1.1 R-Kolkata PC-Kolkata 10.68.2.10/24 · gw 10.68.2.1 R-Shimla PC-Shimla 10.68.3.10/24 · gw 10.68.3.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R-Kolhapur ISR 2911 configure it PC-Kolhapur PC 10.68.1.10 / 255.255.255.0 gw 10.68.1.1 R-Kolkata ISR 2911 configure it PC-Kolkata PC 10.68.2.10 / 255.255.255.0 gw 10.68.2.1 R-Shimla ISR 2911 configure it PC-Shimla PC 10.68.3.10 / 255.255.255.0 gw 10.68.3.1
Cabling
PC-Kolhapur Fa0 ↔ R-Kolhapur Gi0/0 PC-Kolkata Fa0 ↔ R-Kolkata Gi0/0 PC-Shimla Fa0 ↔ R-Shimla Gi0/0 R-Kolhapur Gi0/1 ↔ R-Kolkata Gi0/1 R-Kolkata Gi0/2 ↔ R-Shimla Gi0/1 R-Shimla Gi0/2 ↔ R-Kolhapur Gi0/2
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-Kolhapur interface g0/0
ip address 10.68.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.16.48.1 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.16.48.10 255.255.255.252
no shutdown
exit R-Kolkata interface g0/0
ip address 10.68.2.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.16.48.2 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.16.48.5 255.255.255.252
no shutdown
exit R-Shimla interface g0/0
ip address 10.68.3.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 172.16.48.6 255.255.255.252
no shutdown
exit
interface g0/2
ip address 172.16.48.9 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 R-Kolhapur has 2 OSPF neighbours in FULL 8 On R-Kolhapur: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 2 R-Kolkata has 2 OSPF neighbours in FULL 8 On R-Kolkata: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 3 R-Shimla has 2 OSPF neighbours in FULL 8 On R-Shimla: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 4 OSPF process 55, area 0, with router-IDs 1.1.1.1 … 3.3.3.3 and passive LAN ports 12 On R-Kolhapur: show running-config contains the line(s) matching router ospf 55[\s\S]*router-id 1\.1\.1\.1. and On R-Kolkata: show running-config contains the line(s) matching router ospf 55[\s\S]*router-id 2\.2\.2\.2. and On R-Shimla: show running-config contains the line(s) matching router ospf 55[\s\S]*router-id 3\.3\.3\.3. 5 R-Kolhapur learns 10.68.3.0/24 from the protocol 10 On R-Kolhapur: show ip route lists 10.68.3.0/24. 6 10.68.1.10 (Kolhapur) reaches 10.68.3.10 (Shimla) 12 On PC-Kolhapur: ping 10.68.3.10 must succeed. 7 10.68.2.10 (Kolkata) reaches 10.68.1.10 (Kolhapur) 12 On PC-Kolkata: ping 10.68.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
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-Kolhapur router ospf 55
router-id 1.1.1.1
network 10.68.1.0 0.0.0.255 area 0
network 172.16.48.0 0.0.0.3 area 0
network 172.16.48.8 0.0.0.3 area 0
passive-interface GigabitEthernet0/0
exit R-Kolkata router ospf 55
router-id 2.2.2.2
network 10.68.2.0 0.0.0.255 area 0
network 172.16.48.0 0.0.0.3 area 0
network 172.16.48.4 0.0.0.3 area 0
passive-interface GigabitEthernet0/0
exit R-Shimla router ospf 55
router-id 3.3.3.3
network 10.68.3.0 0.0.0.255 area 0
network 172.16.48.4 0.0.0.3 area 0
network 172.16.48.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.