Just another Cisco blog
Posts tagged MPLS
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 #2
Mar 6th
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. 
CCIP Practice Lab #2
Feb 2nd
This is the second practice lab for my CCIP BGP and MPLS preparation. I’ve added my configs to the first post, let me know if I’ve missed anything. This lab has a lot of overlap with the last one, but I’ve added some more BGP-specific stuff in preparation for my upcoming exam. I have italicized all the changes. Here’s the topology:
(click image for fullsize)
Requirements
Core
- P1, P2, P3 and P4 run only MPLS and OSPF, no BGP.
- PE1, PE2, PE3 and PE4 will support EIGRP, OSPF and L2 VPNs to customers C1, C2 and C3.
BGP
- PE1 and PE4 will have an iBGP relationship and will be route reflectors for PE2 and PE3. Use the fewest commands possible.
- Configure MD5 authentication between CE4 and PE1 using the password “cisco1”.
- Configure MD5 authentication between CE4 and Peer1 using the password “cisco1”.
CCIP Practice Lab #1
Jan 28th
This is the first practice lab for my CCIP BGP and MPLS preparation. I have modified the existing topology to add another customer. This lab is somewhat basic, but it incorporates many different technologies.
(click image for fullsize)
Requirements
Core
- P1, P2, P3 and P4 run only MPLS and OSPF, no BGP.
- PE1, PE2, PE3 and PE4 will support EIGRP, OSPF and L2 VPNs to customers C1, C2 and C3.
BGP
- All PE routers will have iBGP relationships with each other. Use the fewest commands possible to accomplish this. Ensure multiple paths can be taken to peer with each router.
- PE1 and PE2 will have eBGP relationships with Peer1 and Peer2.
- Peer1 and Peer2 will inject networks from several loopbacks into BGP to simulate the internet.
- Peer1 and Peer2 will have an eBGP relationship.
Recent Comments