As with any routing protocol, the goal is to populate the IP routing table with routes to remote networks and the best paths to reaching those networks. As with IPv4, it is important to examine the IPv6 routing table and determine whether it is populated with the correct routes.
The IPv6 routing table is examined using the show ipv6 route command. EIGRP for IPv6 routes are denoted in the routing table with a D, similar to its counterpart for IPv4.
Figure 1 shows that R1 has installed three EIGRP routes to remote IPv6 networks in its IPv6 routing table:
- 2001:DB8:CAFE:2::/64 via R3 (FE80::3) using its Serial 0/0/1 interface
- 2001:DB8:CAFE:3::/64 via R3 (FE80::3) using its Serial 0/0/1 interface
- 2001:DB8:CAFE:A002::/64 via R3 (FE80::3) using its Serial 0/0/1 interface
All three routes are using router R3 as the next-hop router (successor). Notice that the routing table uses the link-local address as the next-hop address. Because each router has had all its interfaces configured with a unique and distinguishable link-local address, it is easy to recognize that the next-hop router via FE80::3 is router R3.
Figure 2 displays the IPv6 routing table for R2.
Figure 3 displays the routing table for R3. Notice that R3 has two equal cost paths to the 2001:DB8:CAFE:A001::/64. One path is via R1 at FE80::1 and the other path is via R2 at FE80::2.