zNetLaB › Guided labs › Enterprise
CCNP — EIGRP and OSPF domains joined by redistribution
Enterprise Advanced 6 devices 6 checked tasks 100 points Plan lab
An EIGRP branch and an OSPF campus meet on one border router. Redistribute both ways, then read the EIGRP topology table to find the feasible successor. 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
An EIGRP branch and an OSPF campus meet on one border router. Redistribute both ways, then read the EIGRP topology table to find the feasible successor.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 6 goals show as passed (100 points).
Network status
Devices: 2 PCs, 4 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. Branch-PC is a host with 10.1.10.10/24, gateway 10.1.10.1. BR1 starts with addresses (G0/0 10.1.10.1/24, G0/1 10.1.12.1/30, G0/2 10.1.99.1/30) and EIGRP 100 already configured. BR2 starts with addresses (G0/1 10.1.13.1/30, G0/2 10.1.99.2/30) and EIGRP 100 already configured. CAMPUS starts with addresses (G0/0 10.2.30.2/30, G0/1 10.2.20.1/24) and OSPF 1 already configured. Campus-PC is a host with 10.2.20.10/24, gateway 10.2.20.1. BORDER starts with an empty configuration. 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
BORDER interfaces addressed and up on all three links (15 pts) BORDER forms two EIGRP adjacencies into the branch (20 pts) BORDER forms an OSPF adjacency with CAMPUS (15 pts) Mutual redistribution — branch prefixes appear in the OSPF domain (20 pts) Campus prefixes appear in the EIGRP branch (15 pts) Branch-PC reaches Campus-PC end to end (15 pts) The activity, in order
BORDER interfaces addressed and up on all three links 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 BORDER forms two EIGRP adjacencies into the branch Why: EIGRP shares routes only with neighbours; a mismatched AS number simply never forms one. Verify with: show ip eigrp neighbors BORDER forms an OSPF adjacency with CAMPUS 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 Mutual redistribution — branch prefixes appear in the OSPF domain Why: If the prefix is not in the routing table, the router drops packets for it, whatever else is configured. Verify with: show ip route Campus prefixes appear in the EIGRP branch Why: If the prefix is not in the routing table, the router drops packets for it, whatever else is configured. Verify with: show ip route Branch-PC reaches Campus-PC end to end 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.2.20.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. Why this matters
An EIGRP branch and an OSPF campus meet on one border router. Redistribute both ways, then read the EIGRP topology table to find the feasible successor.
What you will be able to do
BORDER interfaces addressed and up on all three links
BORDER forms two EIGRP adjacencies into the branch
BORDER forms an OSPF adjacency with CAMPUS
Mutual redistribution — branch prefixes appear in the OSPF domain
The network
PC, ISR 2911, ISR 4331 — 6 devices in all, already cabled.
Fa0 Gi0/0 10.1.10.1/24 Gi0/1 10.1.12.1/30 Gi0/0/0 Gi0/2 10.1.99.1/30 Gi0/2 10.1.99.2/30 Gi0/1 10.1.13.1/30 Gi0/0/1 Gi0/0/2 Gi0/0 10.2.30.2/30 Gi0/1 10.2.20.1/24 Fa0 Branch-PC 10.1.10.10/24 · gw 10.1.10.1 BR1 BR2 BORDER CAMPUS Campus-PC 10.2.20.10/24 · gw 10.2.20.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
Branch-PC PC 10.1.10.10 / 255.255.255.0 gw 10.1.10.1 BR1 ISR 2911 configure it BR2 ISR 2911 configure it BORDER ISR 4331 configure it CAMPUS ISR 2911 configure it Campus-PC PC 10.2.20.10 / 255.255.255.0 gw 10.2.20.1
Cabling
Branch-PC Fa0 ↔ BR1 Gi0/0 BR1 Gi0/1 ↔ BORDER Gi0/0/0 BR1 Gi0/2 ↔ BR2 Gi0/2 BR2 Gi0/1 ↔ BORDER Gi0/0/1 BORDER Gi0/0/2 ↔ CAMPUS Gi0/0 CAMPUS Gi0/1 ↔ Campus-PC Fa0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
BR1 interface g0/0
ip address 10.1.10.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 10.1.12.1 255.255.255.252
no shutdown
exit
interface g0/2
ip address 10.1.99.1 255.255.255.252
no shutdown
exit
router eigrp 100
network 10.0.0.0
no auto-summary BR2 interface g0/1
ip address 10.1.13.1 255.255.255.252
no shutdown
exit
interface g0/2
ip address 10.1.99.2 255.255.255.252
no shutdown
exit
router eigrp 100
network 10.0.0.0
no auto-summary CAMPUS interface g0/0
ip address 10.2.30.2 255.255.255.252
no shutdown
exit
interface g0/1
ip address 10.2.20.1 255.255.255.0
no shutdown
exit
router ospf 1
router-id 5.5.5.5
network 10.2.30.0 0.0.0.3 area 0
network 10.2.20.0 0.0.0.255 area 0 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 BORDER interfaces addressed and up on all three links 15 On BORDER: show ip interface brief — Gi0/0/0 has 10.1.12.2 and is up/up. and On BORDER: show ip interface brief — Gi0/0/1 has 10.1.13.2 and is up/up. and On BORDER: show ip interface brief — Gi0/0/2 has 10.2.30.1 and is up/up. 2 BORDER forms two EIGRP adjacencies into the branch 20 On BORDER: show ip eigrp neighbors shows at least 2 neighbour(s). 3 BORDER forms an OSPF adjacency with CAMPUS 15 On BORDER: show ip ospf neighbor shows at least 1 neighbour(s) in FULL. 4 Mutual redistribution — branch prefixes appear in the OSPF domain 20 On CAMPUS: show ip route lists 10.1.10.0/24. 5 Campus prefixes appear in the EIGRP branch 15 On BR1: show ip route lists 10.2.20.0/24. 6 Branch-PC reaches Campus-PC end to end 15 On Branch-PC: ping 10.2.20.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
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:
BORDER interface g0/0/0
ip address 10.1.12.2 255.255.255.252
no shutdown
exit
interface g0/0/1
ip address 10.1.13.2 255.255.255.252
no shutdown
exit
interface g0/0/2
ip address 10.2.30.1 255.255.255.252
no shutdown
exit
router eigrp 100
network 10.1.0.0 0.0.255.255
no auto-summary
redistribute ospf 1 metric 100000 100 255 1 1500
exit
router ospf 1
router-id 4.4.4.4
network 10.2.30.0 0.0.0.3 area 0
redistribute eigrp 100 subnets metric 30 Where this is examined
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.