Bouter E^shu* ip pigrp topology Active
IP-EIÛRP Topology Table for Aâ(1)/ID(1Û>1.5.2) J 10.1.5.0^4
The output for show ip eigrp topology active didn't show anything for Router E. This indicates that, as far as Router E is concerned, there are no routes in active state. Now you should Telnet back to Router D to double-check whether the router is still in the active state for route 22.214.171.124/24. Telnetting back to Router D shows that Router D is still in active state for route 126.96.36.199/24, but Router E doesn't have any routes in active state. What's going on?
To summarize what has been going on so far, the chain of event is as follows:
1. Router A went active for route 188.8.131.52/24 and is waiting for Router B to reply to the query.
2. Router B can't reply because it is waiting for Router D's query response.
3. Router D can't reply because it is waiting for Router E to reply to the query.
4. Finally, the show ip eigrp topology active command in Router E shows that Router E does not think that any routes are active, while going back to Router D shows that the route 184.108.40.206/24 is still in active state.
From this sequence of events, you can see that there is clearly a discrepancy between Router D and Router E. More investigation is needed between these routers.
A look at Router D and Router E's router CPU utilization and memory usage doesn't show a problem. Both routers' CPU utilization and available memory are normal. You need to look at Router D's neighbor list to see if there is a problem with the neighbors. Example 7-12 shows Router D's EIGRP neighbor list.
Was this article helpful?