I just uploaded a brand new EIGRP Troubleshooting lab which pretty much covers all the nasty things that can happen to EIGRP. It’s a preconfigured configuration with a bunch of routers and the goals are basically ‘trouble tickets’. If you think you are good at EIGRP then i challenge you to give it a go, see if you can solve it without using show run but only commands like ‘show eigrp’ , ‘show ip route’ and the appropiate ‘debug’ commands. This will teach you exactly the skills you need to troubleshoot networks in real life, beat the CCNP TSHOOT exam or troubleshooting skills needed for a CCIE.
This one took a lot more work to create then the other labs, since I had to think about creating scenarios without messing up the previous configurations.
Hopefully you like it, please let me know what you think of it…there’s no video solution / final config at this moment but questions can of course be asked in the forum 🙂
Take care and good luck!
Thanks so much..
Thanks, an interesting one 🙂
It looks like you’ve left out an IP on R5’s loopback. It’s not critical for the lab, just for consistency.
Also, hypervisors on Linux GNS3 do not start automatically for some reason with hypervisor set 127.0.0.1 in .net file. Not a big problem, but a slight annoyance.
Hmm I’ll add the loopback…or you have something else to troubleshoot 😉 About the hypervisors. I didn’t know this, I created the lab on Ubuntu so i’ll see what it does on another Linux machine.
Let me know if you find any other errors.
Before the issue, thanks for the lab Rene.
I too had issues loading the LAB. However changing the Hypervisor to 127.0.0.1 from localhost worked. Oh and I’m one of the un-cool using GNS3 in Windows 7.
Now I’ll attack the LAB and see how it goes.
I created this lab in windows which is why it uses “127.0.0.1” instead of localhost. The result is the same but Linux doesn’t work with 127.0.0.1.
So if you ever run into this issue this is what you have to do:
1) Open the .NET configuration file.
2) Change 127.0.0.1:xx to localhost:xx (X=port number)
3) Save it
4) Run it!
It’s a troubleshooting lab after all…seems the .NET error is just part of the lab 😉 j/k
Comments are closed.