Figure 1 shows that R1’s GigabitEthernet 0/1 interface has now been configured with the 10.10.10.1/24 address and is active.
R1 and R3 still have their neighbor adjacency, but a ping test from the R3 router to a R1’s G0/1 interface of 10.10.10.1 is unsuccessful. Figure 2 shows a failed connectivity test from R3 to the destination network of 10.10.10.0/24.
In Figure 3, using the show ip protocols on the R1 router shows that the network 10.10.10.0/24 is not advertised to EIGRP neighbors.
As shown in Figure 4, R1’s EIGRP process is configured to include the advertisement of the 10.10.10.0/24 network.
Figure 5 shows that there is now a route in R3’s routing table for the 10.10.10.0/24 network and reachability is verified by pinging R1’s GigabitEthernet 0/1 interface.
EIGRP for IPv6
Similar commands and troubleshooting criteria also apply to EIGRP for IPv6.
The following are the equivalent commands used with EIGRP for IPv6:
- Router# show ipv6 protocols
- Router# show ipv6 route
- Router(config-rtr)# network ipv6-prefix/prefix-length
Note: Another form of missing route may result from the router filtering inbound or outbound routing updates. ACLs provide filtering for different protocols, and these ACLs may affect the exchange of the routing protocol messages that cause routes to be absent from the routing table. The show ip protocols command shows whether there are any ACLs that are applied to EIGRP.