RE: 3 Questions

From: Kent Noyes (kentnoyes@xxxxxxxxxxx)
Date: Sun Mar 04 2001 - 15:55:46 GMT-3


   
So doing this we will have the ip addresses in a table and the same ip
addresses again in the diagram? We will have enough time to put all this
info in twice? You feel it is worth it?
Thanks,
Kent

----Original Message Follows----
From: "Chuck Larrieu" <chuck@cl.cncdsl.com>
Reply-To: "Chuck Larrieu" <chuck@cl.cncdsl.com>
To: "Gordon Olson" <gordonolson@telocity.com>, <ccielab@groupstudy.com>
Subject: RE: 3 Questions
Date: Sun, 4 Mar 2001 07:38:35 -0800

The two things I got from ASET in terms of organizational stuff were:

1) write out your addressing matrix clearly, neatly readably.

Device port protocol address

R1 E0 IP 172.16.10.1/24
                IPX A1A

        S0 -- ---
        S0.1 IP 172.254.254.1/30

Etc. this helps clarify how you are doing things. As you fill in the matrix
you can get an idea how to address the ports where you have discretion, so
that you can summarize easily. It also helps to have a clear reference when
you are doing virtual links and access lists.

2) use the butterfly ballot method for writing your diagram and basic router
configs and notes. Even if you are a democrat, the butterfly method should
not be too confusing for you, just follow the arrows... oops I mean ...
you will have an 11x17 sheet of paper. Face it lansdscape. Fold the left and
right edges together so they meet in the middle. you should then have an
8x11 space in the center, with "wings" 4.5 inches wide on either side. Draw
your diagram in the middle, write your pertinent information on the sides.
Need more? Or want to separate out protocols? Fold in one wing and use that
part.

Hard to describe this, but it helps.

I have found that for myself, organizational skills are really important.
Both bootcamp labs and ASET have taught me that my current "kill a forest"
method of working can be counterproductive.

Whatever you do, develop a method and then use it every time. When you walk
into the lab, you want certain things to be automatic, so you can whack out
your basic configs quickly so you have the time to check your work and do
any necessary research.

Now that I am in the later stages of my preparation, I also try not to refer
to books for answers. I try to look for what I need on the doc CD so that I
become familiar with where things are.

HTH

Chuck

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Gordon Olson
Sent: Sunday, March 04, 2001 6:45 AM
To: Troy Allen McCarty; ccielab@groupstudy.com
Subject: RE: 3 Questions

Thank you, I have been practicing this as I have been building labs, mostly
because I tend to get confused if I don't. Is something that they go over in
ECP1 or ASET to help you with your organizational stuff? What you should put
on your drawing and so forth?

-----Original Message-----
From: Troy Allen McCarty [mailto:troy@mccarty.org]
Sent: Sunday, March 04, 2001 6:08 AM
To: Gordon Olson; ccielab@groupstudy.com
Subject: Re: 3 Questions

Your questions don't cross the NDA line

12.0
There are at least two diagrams (the network and frame connections)
You should have everything documented if you make it to troubleshooting.
You don't get to keep your folders.

Troy McCarty
CCIE #6967

At 09:20 PM 3/3/2001 -0800, Gordon Olson wrote:
>What version of IOS is the lab currently using?
>
>On the Lab (can I ask this) when they give you the folder, it is my
>understanding that there is not a diagram inside, That you have to diagram
>your work as you build out the network, is that correct?
>
>If this is correct, can you use this to take extensive notes regarding the
>configuration or do you even have the time to? This would certainly make
the
>troubleshooting day a little easier, I presume.
>
>Gordon
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:19 GMT-3