I don’t usually post on weekends, but I want to try out an idea for troubleshooting labs (and I’m bored). This is the second in the series. We got a lot of answers for the last one, most all of which were correct. I’ve started requiring approval for all comments, this way the answer won’t be posted immediately after I make the post. I think this will be more fun and encourage more people to answer.

This time we’ll have the topology and a .net file, but I won’t be posting configs and you guys won’t be able to do “sh run”. I’ve saved the configs inside the .net file. Run the topology and login with username “tshoot” and password “tshoot”. This user only has privilege level 1, so show commands will be available, but show run will not be. Obviously you could get around this pretty easily, but that would defeat the purpose. ;)

Here’s our topology:

This is another easy one. Today we have two directly connected routers, R1 and R2. They are running OSPF and LDP (MPLS), the issue is that the LDP relationship is not forming.

I’m attaching the .net file with the configs saved inside.
The Troubleshooting Lab #2 .net file
(Don’t forget to change your paths)

UPDATE: I’ve created another Dynamips server in a VM. Telnet to dynamips.alwaysthenetwork.com:2001 for R1 and dynamips.alwaysthenetwork.com:2002 for R2, username: tshoot and password: tshoot.

At the moment only one person can connect at a time. I’ll need to figure if it’s possible to allow multiple console sessions in Dynamips.


Colby Glass has been in IT since 2002. He is currently a Systems Engineer (presales) with a Cisco Gold partner and holds the CCNP R/S, CCNP DC, CCDP, CCIP, JNCIA-ER.

More Posts