In Part 1 of this blog series, we examined time management in the scope of the CCIE R&S exam. That part dealt with the Core Knowledge section. Time management is unlike any other section there. You have plenty of time, and you gain absolutely nothing by rushing. In fact, all you can do is harm yourself by rushing. It is incredibly odd advice for the exam in this section – take your time! :-P

In this part of the series, we are going to examine the Troubleshooting section. Time management is absolutely critical here. In fact, it makes time management more important than in any other CCIE-level exam section ever created. Many of the initial exam failures have come from this section, and it has come from students that failed to manage their time correctly. For those of us that have been in this field for a long time, we here a familiar exclamation…”if only I had more time in that section – no problem!”

Cisco has made the rules for this section very clear. We will see 8 to 12 Trouble Tickets, and we have 2 hours in which to solve them. The Trouble Tickets will span a 20 to 30 router topology. Fortunately, each Trouble Ticket will be independent from each other. In other words, you do not have to solve one Trouble Ticket in order to solve another Trouble Ticket.

Wow! Think about how much time is the enemy in this section. Plan (and practice) for the worst case scenario – 12 Trouble Tickets. That is 10 minutes per Trouble Ticket on average. Drill that into your head. 10 minutes per Trouble Ticket. 10 minutes per Trouble Ticket!

I recommend a tracker to aid you in managing your time here. Start building the tracker as you work through the Trouble Tickets. Here is the key. The tracker is going to allow you to record some observations about the ticket, and will allow you to move on to the next ticket the minute you start to struggle with it. Here, struggling can be defined as exceeding 10 minutes! The other important thing about the tracker is that you can note WHERE in the topology of 20 to 30 routers this issue exists.

In my bootcamps, I like to administer an Advanced Troubleshooting exam on the last day. Students are given 8 Trouble Tickets and they are given 80 minutes to solve them. I intentionally make the first Trouble Ticket unsolvable for most of the students. Sure enough, because it involves an easier technology, students will spend 30 minutes on this first ticket and ensure that they fail this final exam! If only they could bring themselves to leave it after 10 minutes, they would find they can pretty easily solve the other 7 tickets and pass the exam.

For many of us, this is a very difficult thing to bring ourselves to do. Our personalities dictate that we just HAVE TO SOLVE a task that involves a technology that we know very well. It is nearly impossible to abandon our efforts and “admit defeat.” But we are not admitting defeat! We are merely moving on to solve other Trouble Tickets, and hopefully, we will return to this one feeling much less pressure and we can solve it rather easily.

Another aspect of time management for the Troubleshooting section involves the DOC-CD. I spoke with one candidate that passed this section recently (and failed on the Configuration portion of the exam) and they stressed to me how they needed the DOC-CD for one of the Trouble Tickets.  They indicated they would have been absolutely doomed if they had to spend any significant time looking for the feature. Be honest with yourself regarding your mastery of the DOC-CD. If it takes you 10 minutes just to find some strange little IP Service, you are in big trouble in this exam for obvious reasons.

What is the dream scenario for this section? You finish and verify all of your Trouble Tickets in less than 2 hours. This extra time you gain will apply to the Configuration section of the exam. Adding to the 5.5 hours they allow for this section will indeed be a huge help, since time pressures also exist there. We will detail time management for this section in the third part of this blog series. Be sure to watch for other important blog posts soon that cover other aspects of successful strategy for this exam, as well as the other tracks.

As a final note, remember that you will pass this section. Initially students reported the section was “unpassable”. Now we have students passing the section with relative ease. In the words of Henry Ford, “whether you think you can or your can’t, you’re right!”  Start getting excited now for this section, and envision yourself passing it with ease. It will happen.

Thank you so much for everything. Thank you for reading and participating in this blog. Thank you for not giving up in your pursuit of this valuable certification. Thank you for choosing INE, and thank you for watching the clock closely in two of the three parts of this new lab examination.

You can leave a response, or trackback from your own site.

17 Responses to “Time Management in the CCIE R&S Exam – Part 2 of 3”

  1. Shashank says:

    Thanks for these pep talks….

  2. Andrei says:

    Very nice post.
    I love this blog, i think it would become soon my home page :)

  3. KT says:

    Hi, I hate to say this but I have to.
    The journey is long and hard, but with assistance like this, it makes it a lot easier along the way. For all your blog post, thank you. It shows you guys are not just after the money, and to take your weekend time off to do a blog post like this one is certainly appreciated.

  4. Ralph says:


    With this time constraint in mind, is it still possible to apply the “Build and Analyse the Baseline” technique.


  5. Bob says:

    All the CCIE tracks just got the Core Knowledge section. How about the troubleshooting? Is that still only R/S?

  6. Good advice!!!
    It seems to be something you really have to know it. Being prepare and being ready it`s something you allways says on CoD, on V-Seminar, on Audio Classes, etc!!! Be ready for the exam and then … pass it!!! That’s the point even though this is a new version.

  7. Ian Finlayson says:


    Always like to read your Time Management Blogs as they always help me to “try” and focus the way I should with regards to time.

    Kind of like the way you spoke of tracking Core Tasks and Non Core Tasks in the BC! Of course this is going to be a bit more difficult now in V4 isn’t it, with them adding more “non-core” and kind of including MPLS into what we should consider to be “Core”

    When you say these tickets can span 30-40 routers, do they “chop and change” from one ticket to the next, i.e. One ticket might use Routers 1,4,6 and 8 say, and another ticket might use routers 10,20,30, and 35, or do you have to pay attention to the entire topology???


    • Hello Ian!

      Thanks for the fun Facebook stuff by the way!

      I will be doing a Time management post on the Config section and will elaborate on Core versus Non-core in that post – or another if needed.

      As far as the Trouble Tickets go – yes – expect a Ticket to involve a subset of routers, then another ticket to involve another subset. While some routers will be used in more than one ticket – it will be completely independent issues. One big time saving tip – if you are on a router for one ticket – and you notice something else broken – FIX IT – as you probably just fixed another Trouble Ticket!!!!!

      I had a student ace the TS section recently that used this very approach.

  8. Ian Finlayson says:

    Great thanks for that information!!
    Wasn’t too sure how that whole 30-40 router thing worked out…

    Yes I agree with you about keeping an eye out for other issues, that’s a very good idea, thanks for that!!


  9. Seifeddine says:

    Every time guys i read this blog before doing my labs and it just provide confidence and courage and after i just hit my routers for intensive labs Thanks again for all the IE team … what an amazing job :)

  10. Bob says:

    Is there a timeline for when other tracks will get troubleshooting? Will they do like they did with core knowledge and just give us a month to prepare from the announcement?

    I have my lab booked already so it would be nice not to get any last-minute surprises.

    • Hi Bob!

      We have not heard on this one. They added Troubleshooting with a blueprint change for R&S. So we did get the benefit of a 6 month warning. Not sure if the Troubleshooting introduction for the other tracks will coincide with a blueprint change.

      I tend to think they will not guarantee that.

  11. Net_OG says:

    Great advice, it helped me on my mock exam today!

  12. Deepak says:

    Thanks for giving this valuable suggestion through this blog.

  13. Barmak says:

    Many thanks to you for valuable guides and suggestions


Leave a Reply


CCIE Bloggers