Re: can i make block diagrams of technologies in lab ?

I think the original poster was talking about "process diagrams", ie.
block diagrams to describe technologies and processes how to
troibleshoot them, etc.

As far as other diagrams go... I won't argue against that. It would be
... stupid :-)

On Sun, Sep 13, 2009 at 00:06, Darby Weaver <darby.weaver_at_gmail.com> wrote:
> It all goes to say.B Maybe I'm not clear on what we are calling block
> diagrams.
>
> 1. The 4 boxes to represent the switches.B This diagram is easy and should
> take less that about 5 minutes to make and should serve one well during the
> entire exam.
>
> 2. A diagram with the routers and the various interfaces, the type of
> interface, the IP Address, and then circles for each routing protocol (some
> use colors) and then maybe arrows representing which way that redistribution
> may be needed or even specific tag values, etc. This is taught as lab
> strategy in some shape, form, or fashion in all bootcamps.B B Please don't
> tell all the vendors that after 10+ years of this methodology that it is
> purely rubbish.
>
> 3. You may also need a small diagram (maybe on the same sheet) for mcast,
> ipv6, or even bgp.B Your choice and it depends on the complexity.
>
> I question anyone who does not need a diagram at all.B It stands against the
> majority of network engineers and the need for visuals that seem to be a
> requirement in our industry.
>
> Remember, I also question those CCIE's (even multiples) who dismiss the CCIE
> Written as a merely theory.B Since most of those questions for the last
> decade have been quite practical in nature and output.
>
> Me, I'm sort of a hybrid... these days.
>
> I do something like this:
>
> 1. Look at the various diagrams.
> 2. What is given for Frame Relay for example.
> 3. Flip through the workbook looking for issues that I'm going to expect for
> Frame. Type it into notepad.
> 4. Look at my switching - find all the red herrings there that stick out
> like a core thumb.
> 5. Stick that into notepad.
> 6. If I need a diagram...
> B - Not likely for frame.
> B - Very likely for my 4 boxes - just to ensure I don't miss the boat
> somewhere down the road.
> B - For IGPs - I usually worry about physical/logical loops and how that
> stuff is going to work out.
> B - For BGP - I usually draw something to figure out my neighbor
> relationships and whether I need other config or not.
> B - For Multicast - I typically want to see the Unicast Flow so I know what
> to expect from my RPF checks.
> B - IPv6 - Most times can either re-use IPv4 or just don't need it.
>
> QoS tends to be a non-issue
> Security - I might mark the spot if I'm wondering why something broke.
> IP Services - It depends since mostly everythign would be working by the
> time I got here unless I had to NAT something, or maybe needed a DHCP
> interface somewhere.
>
> --
> Darby Weaver
> Network Engineer
>
> 407-802-7394
> darbyweaver_at_yahoo.com

Blogs and organic groups at http://www.ccie.net
Received on Sun Sep 13 2009 - 00:09:35 ART