Our survey about the new CCIE R/S troubleshooting section revealed some interesting facts. First, more than 1/3 of us said that their chances of passing went down with the addition of the new troubleshooting section on the lab. Second, the overwhelming majority thinks that adding troubleshooting make the exam more realistic to what's required of a CCIE doing their normal job. So it got me thinking - how do you prep for the troubleshooting part of the exam?
As I often do when I plan to blog that day, I ended up at the gym for a swim, and let this stuff percolate. Swimming a great exercise for thinking - not a lot of visual input to distract, and certainly tough to use your iPod. So, while underwater today, I was thinking about the troubleshooting prep topic, while also pondering the Cisco 360 program's announcements that happened today May 19th. (Go here to find the scoop.)
Because it's timely with today's announcements, let me spend a few paragraphs giving some background for those of you weren't around during the whole 15+ year history of CCIE. Before 1993, Cisco both created courses and taught the courses, without using partners. In 1993, Cisco started the Cisco Learning Partner program, with Cisco continuing to create courseware, but moving the delivery function to partner companies. Interestingly, although Cisco has added authorized Cisco courses for almost everything they sell, and for most every Cisco certification, the big notable exception was the fact that Cisco had no authorized CCIE training - at least until 2008. Last year, Cisco first offered the Cisco 360 Learning Program for CCIE, which is essentially Cisco's first authorized CCIE curriculum - again delivered by some of Cisco's partners.
As you might guess, during those intervening years, a lot of companies created and offered their own CCIE prep tools and classes. Some of those companies specialized in CCIE, and some were the same old Cisco Learning Partners who wrote their own CCIE materials. The result today is that many companies compete in the CCIE training market, making for a much more competitive CCIE prep market as compared to the rest of the Cisco cert space.
(I'm obligated by Network World to disclaim, which is fine, but pardon my aside: I'm not suggesting which of these many competitors is best. I do have an association with Skyline ATS, which is one of the Cisco 360 program's Learning Partners. If you Google "CCIE training", you'll see hits for most companies I've heard of in the first few pages.)
Back to what's really on my mind: what should we be doing to prep for the troubleshooting part of the CCIE R/S lab? Just looking around at what's available for purchase, and what I know people do on their own, here are some of the more common CCIE lab prep activities:
But of these - any anything else one might do to prepare - what's really needed for preparing for troubleshooting? I'd rule out a few of the items in this list as being a little weaker than the others. For example, making up your own lab activities, or doing general experimentation, while useful, probably are not as effective as using someone's preset lab exercises. Most troubleshooting on the lab will likely be "fix what we misconfigured before you got here", and it's hard to forget what you misconfigured when you made it up yourself. I'd rule out online study groups as well - they are very useful for getting single points clarified, but probably not so good at getting a broad and comprehensive coverage of how to troubleshoot a particular technology area.
As an example of what might work well, the Cisco 360 stuff had a few nice features for troubleshooting. Their assessed labs - 9 hour labs that give feedback not just on points scored, but what you got wrong - have been enhanced to break down troubleshooting as a separate topic. And Cisco added a new 7 hour video section on troubleshooting, broken down by topic. (FYI, the folks at Cisco told me that they added over 100 hours of video/audio elearning for the new CCIE R/S exams. Those are examples; I'm sure the other companies in this space will be adding tools and options as well.
So, let's do a survey, and we'll see how it goes. Frankly, I struggled a bit at how to ask this question as a survey, rather than just open it up for comments, but we'll see how it goes. The question boils down to this: should you study it (books, elearning, classes), practice it (pre-set labs), be assessed on it (do labs, be critiqued), or ignore it (practice config, t'shooting will be natural). On each of those, is it more important to do those things by topic area, or is it better to do comprehensive tasks. For example, is it better to do labs that cover troubleshooting of one big topic, or scenarios that break everything, and you find all the problems? I think they all have merit. I'll post again to tell my opinion here in a few days, but let me know your preferences. Thanks...
Odom, CCIE No, 1624, splits time between writing books for Cisco Press and teaching classes for Skyline ATS. In his 25-ish years in the networking industry, he has worked as as a pre-sale and post-sale SE for a few networking vendors, as well as a network engineer implementing network technology. Wendell has spent the majority of the last 15 years teaching, consulting, and writing about networking technologies, most of which in some way relate to Cisco products. His books include titles on QoS, CCIE R/S, as well as several titles related to CCNA certification, including the September 2007 book CCNA Official Exam Certification Library (CCNA Exam 640-802) (Read a sneak peek of chapter 7). Click for the list of current titles by Wendell.
Troubleshooting
Nice article Wendell. I was talking to Bruce Caslow about this earlier today (well yesterday now).
The problem with Troubleshooting is that it is so... arbitrary when taken as a subject.
Take a guy like me. I've been to most of the classes ($$), worked through a few workbooks, read mostly every book (including some of yours that line my bookshelves) and I guess I'm fairly experienced by now.
I successfully fail the CCIE Lab with ease and agility.
So you listed a number of items on how to prepare for troubleshooting.
The best way to troubleshoot is to simply learn how to configure and along with configuration one has to learn how to verify each detail, through and through.
But!!!
That's not enough as you have recently seen for yourself. The truth is you need to be "natural" and you need to be fast and that is a hard combination.
I suppose if they'd have had this type of troubleshooting in the lab we'd have a lot less CCIE's today and then only the most persistent and fierce type who just won't quit or even give in.
I think this will ultimately bring the value of the CCIE back and do so quickly if it can maintain the momentum it has started.
I'm really waiting to hear the formal announcement that the Troubleshooting has been extended and is now the basis for every CCIE to recertify. It's definately more meaningful and real-world.
Now as for prep:
1. I bought every troubleshooting books I would find for Cisco and I went one better - Sniffer and Fluke (I'm a Sniffer Certified Master and I think highly of my qualification) - it is based on a lot of troubleshooting - applications, protocols, and media.
2. I'm reliving some of my choice lab materials (strangely enough I'm hovering over my NetMasterClass Full Labs and pretty much disregarding the other full labs). I may come back to them later but I always considered NMC's labs to be qualitatively superior and as lab-like as you can make a Workbook or Mock Lab without using a Proctor as a the cook.
3. I'm shooting for speed to. Now more walking and meandering my way through lab after lab and casually blogging online as I work through labs or examples. Now it is more of: do a lab - any lab - once, twice, thrice, etc. until I firmly understand each aspect of that lab, every nuance must be crystal clear, every nuance must simply be mastered. Yes it will take more time, a lot more time, but that's always been the name of the game hasn't it? Oh yes and ever since I met Johnny Bass, I've got a metric in my mind. So I'm aiming to be like Johnny in terms of speed. He only got as fast as he did by working out the details over and over again. That's my secret ingredient.
Post new comment