EIGRP Convergence Lab not working

[steeilers]

attached is a .pkt changed to a .jpg.

The PCs on both 192.168.1.x  and 192.168.2.x networks can ping each other fine. When I remove the link missing in the attached .pkt (packet tracer) the network isn't converging.

Troubleshooting done so far

- traceroute from router 3 fails after entering router1, packet not making it to router5

- traceroute from router 5 fails and doesn't make it to router1

I know the problem is in router5 but when i --show ip eigrp topology i see router5 knows about the route through router 1, but show ip route shows it isn't putting the route in the routing table, i verified router5 is in the same asn, it has neighbor relationship with router1, but for some reason it isn't converging when i remove the link between router4 and router3

can someone please download the .jpg attached, convert to .pkt, analyze what is wrong with router5?

Thank you! if you don't want to download and convert, i can send show commands let me know, thanks,

[steeilers · Accepted solution]

file eigrp uploaded with topology for those that can't download the .pkt converted to .jgp to review

[Julio E. Moisa]

Hi

Unfortunately the picture cannot be displayed. Please upload it again. Also can you upload the packet tracer file (zipped)

[steeilers]

Hey Julio, thanks for the reply, I just downlaoded it from the website, changed extension from .jpg to .pkt after downloading it and it loaded for me.

[Georg Pauwen · Accepted solution]

Hello,

I can ping between both PCs with the link missing. It took a while to converge, which is typical for EIGRP. To speed up convergence, change the EIGRP hold and hello timers on the interfaces that form the neighbors:

ip hello-interval eigrp 1 1

ip hold-time eigrp 1 3

Hold time should be 3 times the hello interval...

[steeilers · Accepted solution]

that's strange, i was troubleshooting it for over 15min and it wouldn't ping across with the link removed.

[steeilers]

weird, reloading the .pkt save it is working now for me too

[steeilers]

I tried to use GNS3 but was having install issues and didn't want to trouble with it so I went back to packet tracer until I can work through why GNS3 was crashing on launch.

[Julio E. Moisa]

it could be a bug on the packet tracer. 

[steeilers]

ya, thank you for trying to help, :)

[Julio E. Moisa]

You are welcome,

Have a great day

:-)

[Georg Pauwen]

Hello,

Packet Tracer is not the most reliable tool for testing real life scenarios. 180 seconds would be normal, 15 minutes is way too long...

As with regard to GNS3, did you use the all-in-one installer ?

https://www.gns3.com/support/docs/quick-start-guide-for-windows-us