Well, It took me two goes around, but I did it. I sat my Lab yesterday and received the dreaded email at 4:21am this morning. About two hours ago actually, im too excited to go back to sleep.
After my first failed attempt in May, I felt that my overall strategy and time management was pretty good, It was some weak technology areas and TSHOOT that let me down.
First off TSHOOT is an absolute beast, and it makes or breaks the whole day. I failed by one ticket last time, but having only attempted 8 tickets, it was no surprise that I dropped one. This time around, I made sure I managed my PuTTY windows better. As soon as I was done with a device, unless I was comparing it side by side to something it was a case of 'u all, wr' and see you later. I felt that last time I wasted too much time skipping round the tickets trying to find one to do. This time I said to myself, I need to all 10, start at number 1. I worked in a linear fassion until I found a ticket that look like it was going to be a bit more involved. Skipped it, made a note and carried on. For me this worked well, I had nailed 7 2 point tickets in 1 hour, which gave me plenty of time for the 3 pointers and a 2 point ticket which was quite involved. I completed 9 tickets in the end.
Config is config. Read the lab, read the questions. Theres no mystery to it, WB2 labs are perfect, literally perfect. In my 2 attempts I have not seen a task which I thought I hadnt seen before or hadnt learnt. At the end of the the day the blueprint is what it is and theres only so many ways you can be asked to do something.
One tip I use as much as possible, is try and keep ACL numbers to task numbers, so task 2.3 acl 23 etc. It seems to work well, it can save the hassle of using the same name for a route-map or something, and wondering why connectivity has gone to ***.
Re-run your TCL after every task where connectivity can be broken. If it breaks, you'll know what task or device broke it.
I went a bit maverick after my Layer 2 section, I'd always dreamt of having full connectivity by dinner, however after Layer 2 I knew I wasnt going to make a dent in IGP, so I went and did some Network Optimisation and Service tasks. Long story short I managed to get a good chunk of points before lunch. I came back after dinner with a lot of work to do, but most of services had been done, so I knew I only had to do all my IGP and BGP etc, and then a few tasks which Id saved for later.
Verification is key, I told myself, regardless of what happens, in the last hour verify everything Id done. With one hour to go I knew I had around 70 points, so I was in the 'Golden Circle', so I reloaded, went and washed my face and got a coffee. I came back and verified for the last hour. Im lucky I did, I found a number of silly mistakes, some quite embarassing, but hey, that one mistake is 3 points down the drain.
Notepad: Last time, I felt I used Notepad too much, for nearly every task I completed it on notepad, and typed it in. I found even if I used the CLI conetext sensitive help, id still go back to notepad. Myself and my study partner devised 'Engineering mode'. Forget notepad, hit the CLI and get it done, and it certainly helped with time. Anything big and repetitive like BGP, or when using route-maps etc, then Notepad all the way.
Other than that, theres no mystery. Study hard, put the time an and it will come. I told myself tht regardless of how long it takes, I am going to get my CCIE. I've watched a lot of helpful members in this forum get there CCIE, and theyve been more than willing to help me out when I had questions, so massive thanks to Daniel Dib, David Rothera, MellowD and everyone else in the forums/twitter etc.
And Finally, INE. Not much to say that hasnt already been said. Your workbooks are amazing, the mock labs where great and the support is second to none. Whilst waiting outside of the lab yesterday I was talking to the other candidates, well all used INE apart from one person, it just goes to show.
Now I have the fun of updating all my profiles etc with my number.
Marc
CCIE #40255