Just another Cisco blog
Posts tagged CCNP
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. 
CCNP TSHOOT Exam Topology
Feb 21st
According to a post on Cisco Learning Network, Cisco will be releasing the topology used in the TSHOOT exam:
First, I am part of the exam development team. Second, what am about to reveal is not part of some secret NDA.
The new TSHOOT exam requires you to isolate issues on a defined network topology. The purpose of the exam is to evaluate troubleshooting skills, not how quickly you can grasp a network topology you have never seen. To this end, it is Cisco’s intent that the exam network topology be available for review before the candidate attempt the exam.
However, the wheels seem to move slowly and the network topologies have not been posted on CLN. Because of this I have authorized to make the topologies available through this discussion until they are officially posted.
BGP Multi-Exit Discriminator (MED)
Feb 8th
Today we’ll go over another important BGP topic: MED. From Cisco:
“MED is an optional nontransitive attribute. MED is a hint to external neighbors about the preferred path into an autonomous system (AS) that has multiple entry points. The MED is also known as the external metric of a route. A lower MED value is preferred over a higher value.”
So, to summarize, MED is used to influence incoming traffic from a multi-homed neighbor AS.
Here’s our diagram:
In this case we’ll say that the link between PE1 and CE1 is only a T1, while the link between PE2 and CE1 is a DS3. Obviously we will want traffic to use the faster link, the PE2-CE1 DS3.
First we’ll configure our interfaces and basic BGP:
PE1: hostname PE1 ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! interface Serial0/0 description To PE2 ip address 10.1.1.2 255.255.255.254 ! interface Serial0/1 description To CE1 bandwidth 1500 ip address 172.16.1.2 255.255.255.254 ! router bgp 5300 no synchronization bgp log-neighbor-changes neighbor 2.2.2.2 remote-as 5300 neighbor 2.2.2.2 update-source Loopback0 neighbor 2.2.2.2 next-hop-self neighbor 172.16.1.3 remote-as 1200 no auto-summary ! ip route 2.2.2.2 255.255.255.255 10.1.1.3 PE2: hostname PE2 ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 ! interface Serial0/0 description To PE1 ip address 10.1.1.3 255.255.255.254 ! interface Serial0/2 description To CE1 bandwidth 45000 ip address 172.16.1.4 255.255.255.254 ! router bgp 5300 no synchronization bgp log-neighbor-changes neighbor 1.1.1.1 remote-as 5300 neighbor 1.1.1.1 update-source Loopback0 neighbor 1.1.1.1 next-hop-self neighbor 172.16.1.5 remote-as 1200 no auto-summary ! ip route 1.1.1.1 255.255.255.255 10.1.1.2 CE1: hostname CE1 ! interface Loopback0 ip address 3.3.3.3 255.255.255.255 ! interface Loopback1 ip address 192.168.1.1 255.255.255.0 ! interface Loopback2 ip address 192.168.2.1 255.255.255.0 ! interface Loopback3 ip address 192.168.3.1 255.255.255.0 ! interface Loopback4 ip address 192.168.4.1 255.255.255.0 ! interface Serial0/1 description To PE1 bandwidth 1500 ip address 172.16.1.3 255.255.255.254 ! interface Serial0/2 description To PE2 bandwidth 45000 ip address 172.16.1.5 255.255.255.254 ! router bgp 1200 no synchronization bgp log-neighbor-changes network 192.168.1.0 network 192.168.2.0 network 192.168.3.0 network 192.168.4.0 neighbor 172.16.1.2 remote-as 5300 neighbor 172.16.1.4 remote-as 5300 no auto-summary |
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”.
BGP Best Path Selection
Feb 1st
As I gear up for the CCIP BGP exam (hoping to take it in the next few weeks), I’m relearning all the little things I’ve forgotten since BSCI. I had the Best Path criteria memorized for the exam and I’ve since forgotten some of the criteria and the exact order. Google pointed me to these docs:
This one courtesy of Ciscozine:
This one courtesy of Richard Bannister’s CCIE Blog:
These two charts are great, they’ve helped immensely. I love the internet. I’m posting them here for my future use and in case and of you haven’t already seen them.
