zNetLaB › Guided labs › Enterprise
EIGRP for IPv6 — the process that starts shut down
Enterprise Intermediate 4 devices 5 checked tasks 100 points Plan lab
Configure EIGRP for IPv6 on two routers and nothing happens. Everything looks right: the interfaces are in the process, the addresses are correct, the router-ids are set. One line is missing, and it is the same line every time. 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
Configure EIGRP for IPv6 on two routers and nothing happens. Everything looks right: the interfaces are in the process, the addresses are correct, the router-ids are set. One line is missing, and it is the same line every time.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 5 goals show as passed (100 points).
Network status
Devices: 2 routers, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with addresses (L0 1.1.1.1/32, G0/0 2001:db8:1::1/64, G0/1 2001:db8:12::1/64). R2 starts with addresses (L0 2.2.2.2/32, G0/0 2001:db8:2::1/64, G0/1 2001:db8:12::2/64). 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
Both interfaces on each router are in EIGRP AS 100 (20 pts) The process is out of shutdown on BOTH routers (30 pts) The adjacency comes up (25 pts) Each router learns the other’s LAN by EIGRP (15 pts) The two hosts reach each other (10 pts) The activity, in order
Both interfaces on each router are in EIGRP AS 100 Why: An administratively down port forwards nothing, and a routing protocol cannot form a neighbour over it. Verify with: show ip interface brief The process is out of shutdown on BOTH routers Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The adjacency comes up Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Each router learns the other’s LAN by EIGRP Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The two hosts reach each other Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 2001:db8:2::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
Configure EIGRP for IPv6 on two routers and nothing happens. Everything looks right: the interfaces are in the process, the addresses are correct, the router-ids are set. One line is missing, and it is the same line every time.
What you will be able to do
Both interfaces on each router are in EIGRP AS 100
The process is out of shutdown on BOTH routers
The adjacency comes up
Each router learns the other’s LAN by EIGRP
The network
ISR 2921, PC — 4 devices in all, already cabled.
Gi0/1 2001:db8:12::1/64 Gi0/1 2001:db8:12::2/64 Gi0/0 2001:db8:1::1/64 Fa0 Gi0/0 2001:db8:2::1/64 Fa0 R1 R2 H1 H2 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R1 ISR 2921 configure it R2 ISR 2921 configure it H1 PC configure it H2 PC configure it
Cabling
R1 Gi0/1 ↔ R2 Gi0/1 R1 Gi0/0 ↔ H1 Fa0 R2 Gi0/0 ↔ H2 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:
R1 ipv6 unicast-routing
interface Loopback0
ip address 1.1.1.1 255.255.255.255
exit
interface GigabitEthernet0/0
ipv6 address 2001:db8:1::1/64
no shutdown
exit
interface GigabitEthernet0/1
ipv6 address 2001:db8:12::1/64
no shutdown
exit R2 ipv6 unicast-routing
interface Loopback0
ip address 2.2.2.2 255.255.255.255
exit
interface GigabitEthernet0/0
ipv6 address 2001:db8:2::1/64
no shutdown
exit
interface GigabitEthernet0/1
ipv6 address 2001:db8:12::2/64
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 Both interfaces on each router are in EIGRP AS 100 20 On R1: show ip interface brief — Gi0/1 is up/up. and On R2: show ip interface brief — Gi0/1 is up/up. 2 The process is out of shutdown on BOTH routers 30 Checked automatically against the device’s live state (eigrp6Up). and Checked automatically against the device’s live state (eigrp6Up). 3 The adjacency comes up 25 Checked automatically against the device’s live state (eigrp6Nbrs). and Checked automatically against the device’s live state (eigrp6Nbrs). 4 Each router learns the other’s LAN by EIGRP 15 Checked automatically against the device’s live state (route6Type). and Checked automatically against the device’s live state (route6Type). 5 The two hosts reach each other 10 On H1: ping 2001:db8: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
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:
R1 interface GigabitEthernet0/0
ipv6 eigrp 100
exit
interface GigabitEthernet0/1
ipv6 eigrp 100
exit
ipv6 router eigrp 100
eigrp router-id 1.1.1.1
no shutdown R2 interface GigabitEthernet0/0
ipv6 eigrp 100
exit
interface GigabitEthernet0/1
ipv6 eigrp 100
exit
ipv6 router eigrp 100
eigrp router-id 2.2.2.2
no shutdown 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.