1.10 Implement Spanning Tree Protocol (STP)
X (a) 802.1d
(b) 802.1w
(c) 802.1s
(d) Loop guard
(e) Root guard
(f) Bridge protocol data unit (BPDU) guard
(g) Storm control
(h) Unicast flooding
(i) Port roles, failure propagation, and loop guard operation
This is what I am doing. I am looking at this blueprint, and since I have already gone through most of the v.4 once in good detail, I decided I will START OVER.
Why? It just feels like the right thing to do. I originally went through the v4 blueprint on my own without knowledge of the "expanded" blueprint on http://blog.internetworkexpert.com/2009/05/12/ccie-rs-4x-expanded-study-blueprint/
After looking at my "blueprint" compared to that one above, I realized I was lacking in many areas. So rather than trying to "fill in the gaps" by chasing down everything and figuring out "Did I cover that" I am just going to start from the beginning and nail everything down.
What's the point in all this? Right now, I am still working on my CCIE RS written. However, I am a practical hands on guy so I learn by doing really. I have Routing TCP/IP v1 2nd edition and Volume 2 as well. I have MPLS Fundamentals. Those books I mentioned are in hard copy. I have soft copies of troubleshooting routing protocols, qos certification guide and a soft copy of the CCIE RS guide 3rd edition. The 4th edition comes out in the first part of December '09.
As I take a look at what I just wrote, I should mention if you are going after the CCIE RS you should be WELL aware of tcp/ip v1 and v2 as they are the bibles. Read those cover to cover, I have done so ONCE. I don't know if I could do it again! I do however, open up to specific sections I need to know about like my favorite BGP. The most pain in the ass protocol in the entire world. Some people like it, I do like it actually but there is SO much to it!
Alright, getting sidetracked so back on point. The reason why I started over is to see what I remember and more importantly what I don't remember. If I am fuzzy on something but not quite "there" then at least I do remember it.
Last night I studied for 1 hour and I learned one single thing.
802.1d STP. That's it, how it works and what it does. Dropping trees on redundant links. So simple, yet there are entire books dedicated to the design of STP. I am not just talking about 802.1d I am also referring to all the other flavors of STP as well.
So that's where I am at, the very very bottom of the list. Nailing layer 2 as that is critical to getting layer 3 going. In the lab, if you don't have good layer 2 connectivity you are screwed as it can break everything else like ospf, bgp etc. Yea, not good.
That's all I got, figured I share.
Starting over is hard, but knowing it's the right thing to do is easy.
Ok, this comment is irrelevant towards your spanning tree, but wanted to start posting things on your blog. So BGP is coming out to be pretty interesting. So let me see if I understand. RIP, EIGRP, and OSPF uses the Network command to advertise. This advertisement will automatically form neighbor relationships when using RIP, EIGRP, & OSPF. With BGP, the neighbor relation has to me statically configured, and these relations do not advertise routes. We use different commands with BGP to form neighbors as we do to advertise routes. You will not have advertised info in BGP table even with formed neighbors. Am I accurate so far?
ReplyDeleteAnthony Sequora over at INE said this on the expanded blueprint page in regards to a comment I made.
ReplyDelete“when you break it up into small verifiable pieces – it is manageable. ”
The network command allows what interface or interfaces you want to advertise into those IGP's (RIP, OSPF, EIGRP)
Within BGP you are peering with the AS not the interfaces. You can peer with devices that are not even directly connected.
You have IBGP, which typically will have an IGP running over it such as OSPF.
Then you have EBGP which is going AS to AS. I'll leave it at that for now. BGP peering is a HUGE topic and is the most talked about topic within Cisco according to one of the IOS developers. It's an endless subject.
Focus on the basic BGP peering, but moreover really hit the basic BGP peering theory hard as without it BGP will leave you high and dry when trying to configure it. :)
Anthony Sequeira, #15626 I spelled his name wrong, oopsy :)
ReplyDelete