Like I hinted at in an earlier post, there are a some failure scenarios you need to consider for vPC. The first scenario we can’t really do much with, but I’ll describe it anyway. The topology is the one below:
Becoming a CCIE – the path and cost associated to my number
While on IRC I had a request to describe my journey and the costs associated with becoming a CCIE. Becoming a CCIE is not cheap but I’ve worked for great companies that have covered all of my costs. I first
MPLS troubleshooting scenario
I’m in final preparation for my second attempt and I have been doing a lot of troubleshooting scenarios lately. I created a MPLS topology in GNS3 and sent it to my friend Darren for testing. He is taking his lab
INE TS Vol4 – two labs done
Did some of these TS labs this week. They are very challenging but they are designed by Petr Lapukhov so they should be… I found these to be more difficult than the ASET TS labs. From what I’ve heard from
First troubleshooting session done
I did my first troubleshooting session tonight. I was worried about only having 2 hours alotted but time was the least of my concerns. I finished at 70 minutes so almost an hour to spare. I did quite OK, 60%
Troubleshooting multicast – RPF failure
In unicast routing we are interested in how to forward packets to their destination. In multicast routing we are interested where the source came from, multicast packets need to pass a RPF (Reverse Path Forwarding) check. Packets that are received
BGP troubleshooting – route not installed
Sometimes prefixes in BGP do not get installed into the routing table, if the route is also in an IGP that might be a reason but then a RIB-failure would be indicated. This scenario shows another possible source of problems.
BGP troubleshooting – peer address not matching
Yesterday I did some Internetwork Expert vol1 labs on BGP. I was having trouble getting some of the peers to come up and had to troubleshoot. This post will describe how to troubleshoot when peers won’t form. First, lets look