I am among the few, the proud who passed in spite of having pretty much chewed up the entire time alotted. Having said that, I spent probably around an hour at the start of my day drawing L2 and L3 and fully reading the workbook from cover-to-cover. Also some time was dedicated to understanding the stuff already done before I ever walked in. It’s probably also worth mentioning that I lean more towards a “build-and-verify” approach vs. a “build-move-on-verify-at-the-end-of-the-day” methodology, so I’m naturally going to be (or at least appear) slower than some.

But my reason for posting is not to try to be the exception to the rule. My reason for posting is to say that I would not have passed without learning to draw L2 and L3 during practice/mock labs. The L2 stuff can be critical early in the day when you need to make good time with little to no mistakes and the L3 stuff can be critical towards the end of the day when you’re exhausted but still facing down significant tasks such as, oh, say BGP!

Learn to draw and budget the time for it. Certainly I have talked to those who did not and yet passed. But also I talk to those who did not (draw or pass) and simply cannot figure out how they didn’t get 80 for the nth straight time. In these cases, I often wonder there was some subtle peering or next-hop thing they didn’t even recognize. Along this same line, learning TCL scripts (much as I dreaded doing so) and running them over and over again is another “time-consuming” technique that can make or break your day…

Cheers,

Scott

I was wondering if you could maybe post examples of the different types of diagrams (L1, L2, L3) that you suggest to make here.

Also, how do you draw out your IPv6 design, or you IP Multicast design, etc?

Thanks
Marc

Is it possilbe you could pin up somewhere an example of a layer 3 diagram that you have drawn based on on your VOL 3 workbook? One that has the requistite inforormation wihout re-inventing the wheel.

I do beleive self made diagrams are important, we do them everyday at work in troubleshooting problems. But the problem often lies in trying to do a diagram without actually re-drawing out the infromation that a supplied diagram has already given you!! This as you know takes time and of courses, is not very economical on the brain and lab time for that matter.