The Case of the Failed IPv6 Ping – Part 2: The Solution
Put your detective hat on your head and your Network Detective badge on your lapel. It is time to SOLVE for the Case of the Failed IPv6 Ping.
Review the Facts and Clues Again
Let’s review where we left off in our Part 1 of this case — “Case of the Failed IPv6 Ping – Part1: Facts and Clues“. At the end of Part 1…..we were ON R1 and unable to ping the IPv6 address of our directly connected interface gig0/0/3, 2001:db8:14:1::1.
As you recall the facts were as below. Interface up/up, OSPFv3 configured properly, proper IPv6 address configured on interface gig0/0/3. Still, we cannot ping R1’s directly connected IPv6 address from anywhere including from R1 itself.
Totally confused. Time to just stare at the list above, absorb the oddness, and think.
Wait one second!!!! “No valid route for destination” ??? Even the ping from R1 said that?
“That can’t be true“, I think to myself while I type show ipv6 route connected.
What the????….. Why don’t I have R1’s gig0/0/3 interface in the routing table? It is up/up and with the proper IPv6 address configured. Now Continue reading




David Goeckeler is now GM of the Networking and Security Business Group at Cisco.