From: Thomas Perrier (thomas@perrier.name)
Date: Mon Dec 03 2007 - 07:50:05 ART
On 3/12/07 11:15, "sheherezada@gmail.com" <sheherezada@gmail.com> wrote:
> BTW, to me it seems very unfortunate the way that workbooks present
> BGP in diagrams. Why don't you guys use lines instead of clouds for
> BGP? BGP is about neighbor policy after all. Personally, I find more
I agree. In my labs (real and practice), I draw a single L3 diagram,
identical to the one provided, with routers, switches and links between
them. I add some IP addresses at the begining, not necessarily all of them;
I'll complete if needed. I draw circles for the various IGP domains. I add
arrows between the circles, indicating redistributions, as I progress
through the lab (i.e., if there's an arrow, then it's configured). For BGP,
like Mihai I'll add red lines between the peering routers (differentiating
EBGP and IBGP could be nice, but I never did it; maybe I should have!). For
multicast, I show multicast enabled interfaces with a code (I draw a little
circle, but anything would do). For interfaces having access-lists, I use
another code. At the end of the day, the drawing is a little of a mess, but
I almost know it by heart anyways. :) Just make sure to fill the whole sheet
of paper; all this can't fit on a miniature diagram.
This drawing, coupled with a single read of the exam (in order to try to
detect land mines and dependancies), takes me roughly 30 mn maximum.
For L2, I'll only bother to draw a quick small diagram with the switches,
links between them, and VLANs, if needed (STP tuning tasks). IMHO, it's not
very complicated and no need to get fancy there. For Frame Relay, the
provided diagrams are fine, don't waste time there.
But to each its own!
-- Thomas Perrier CCIE #18731 (R&S)
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:28 ARST