CCDE Topic: docs I found useful

CCDE Topic: docs I found useful

Step One: the written (read this even if you already passed!)

I found the written outline to be the most useful preparation not only for the written exam, but also the practical.  I went through all of the topics outlined and made sure I understood exactly what they were trying to get at.  Honestly, there were a number of items I had never heard of, so doing the research felt like I was accomplishing something.  I’ve posted a few of the written items on this blog, like What is the issue with re-marking and OoO packets? and What is fate sharing, and what is its impact?.

If you want to see more about the security portion of the written outline, be sure to check out this post too.

In case you can’t tell, I’m saying that even if you passed the written easily, you probably want to go back & make sure you understand everything that’s covered on the outline.

Step Two: the practical

This is the difficult part, but I’ll try to give a summary of what I found most useful for me.  Of course, you may already be an expert in one of these topics and won’t need to review it (but you probably should anyway).


High Availability Campus Network Design–Routed Access Layer using EIGRP or OSPF

Enterprise QoS Solution Reference Network Design

RFCs (in no particular order):

Multicast RFC1112


If you have access to the Partner Education Connection you’re in luck.  If not, your best bet is to check out elementK.  Your company may already have a subscription.  I’m sure there are others with equivalent training, but I’m speaking specifically about the path I took.

I took the online MPLS SE training, reviewed the Multicast training, and reviewed the EIGRP training.

I’ll go into the specific courses in a later post, as well as a book listing & the Cisco Live / Networkers materials I found useful.

CCDE certified, now what?

So it’s been a few weeks since learning that I passed the practical, and other than NOT having to attend the next practical in December, not much has changed. I think the marketplace is still trying to determine the value of this certification, and my feeling is that some employers may think it’s nothing more than a written exam. They’re right, of course, but it is a hard written exam. It remains to be seen just how / when employers will start to recognize the value. I think if the CCDE team published some statistics on the pass/fail rate it might help (along with the level of experience most taking it have), but I’m not holding my breath.

The path I took in studying for this exam made me a much stronger network engineer, and IMO that’s the whole point. Now the question will be whether or not others become stronger engineers in their pursuit of the CCDE.

Some people have emailed me asking how they should prepare for the practical, and I would say the following has been invaluable preparation for me:

1. Get a job where you’re tasked with maintaining & troubleshooting a production network.
2. Never be satisfied when something magically starts working – troubleshoot & solve real-world issues and find the root cause (wireshark is your friend).
3. Visualize how you would change the network to solve systemic problems with the network (and maybe even implement some changes).
4. Work with the applications people to help them understand how the network affects their applications (and vice-versa).
5. Become the ‘buck stops here’ person, meaning that if you cannot solve the issue, nobody can. You need to take ownership of the entire system – don’t pass off issues to the applications people / server people.

In short: you cannot just have book knowledge to pass this exam, you will need real-world experience troubleshooting and designing solutions to solve systemic problems. If you gain this experience, you won’t need the CCDE to prove your level of knowledge, your CV will speak for itself.

My background is in UNIX systems administration, networking, and security. I’ve also worked in several industries including Financial Services, SP, and DoD. I worked in small companies where I was in charge of everything, and large organizations where I was in charge of just one small part of the network. In all cases, I knew not just what I was responsible for, but all (or most) of the applications and systems running within the system. Personally, I believe this experience was key preparation for the CCDE. You need to understand real-world design issues, not just the best practice picked up from reading in a book. You need to never be satisfied with the design either – always look for ways to improve it. This quote from fellow blogger Jeremy Filliben sums it up nicely:

“When I take two eggs out of the carton, I take one from each row. It isn’t more correct, but it makes me feel better.”

Isn’t that the whole point anyway? If you have a passion for this stuff it will show, and you will be rewarded with an infinite number of interesting problems to solve.