Just another Cisco blog
Posts tagged Troubleshooting
Troubleshooting Lab #6
Apr 7th
First lab with our new topology. I’m excited! This should be an easy one. When functioning correctly, Customer “a” connects to AS 6500 using MPLS VPNs and running OSPF with the provider between sites. Site 2 (CE2a) has internet access through a physical connection to AS 6500s global RIB, it also has a GRE tunnel to PE1 which connects to the MPLS VPN. Customer “b” has a similar configuration. Customer “b” is using EIGRP. Both customers have a single “internet” circuit which is reachable from only one site, all internet traffic from the other site will go over the WAN first.
The issue today is users in VLAN 40 are having issues accessing the internet (87.3.85.1), determine why.
New Troubleshooting Lab Topology
Apr 3rd
The old topology I’ve been using for the weekly labs is pretty limited. I created a new one today which should keep us going for awhile. It’s relatively complex, it consists of two customer MPLS VPNs and lots of routing. The two customer VPNs also have internet access through one of their sites. We are simulating the internet with Peer1 and Peer2. Here’s the diagram:
(click image for fullsize)
I should have the first lab up early next week after I work out some issues I’m having. So tell me what you guys think.
Here’s the .net file:
New Troubleshooting .net file
Troubleshooting Lab #5
Mar 25th
This one might be easy, but I’m having trouble gauging it after last week. Same topology, users are having trouble communicating from one VLAN to the other. Soon I’ll make a new (bigger) topology with more diverse technologies, I haven’t had the time lately.
You can run the .net on your own Dynamips server or you can use mine. 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. You can also login with username: “shrun” and password: “shrun”, this will print the running config and boot you out. I would like to grant full privilege 15 access, but I’m worried about people messing with the configs, this is after all a public post. Obviously you could get around this pretty easily, but that would defeat the purpose. 
Troubleshooting Lab #4
Mar 18th
Today is probably going to be another easy one, but I threw it together pretty quick. We’re using the same topology as last time. Same issue, users cannot communicate, but different problem.
You can run the .net on your own Dynamips server or you can use mine. 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. You can also login with username: “shrun” and password: “shrun”, this will print the running config and boot you out. I would like to grant full privilege 15 access, but I’m worried about people messing with the configs, this is after all a public post. Obviously you could get around this pretty easily, but that would defeat the purpose.
Here’s our topology:
(Click for fullsize)
Troubleshooting Lab #3
Mar 11th
This one is a little different (again). I’ll be posting the .net file with the configs, like last time. I will also have accessibility to the topology through a sandboxed Dynamips VM. This time you will be able to see the running config.
You can run the .net on your own Dynamips server or you can use mine. 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. You can also login with username: “shrun” and password: “shrun”, this will print the running config and boot you out. I would like to grant full privilege 15 access, but I’m worried about people messing with the configs, this is after all a public post. Obviously you could get around this pretty easily, but that would defeat the purpose.
Recent Comments