From: Pinnacle -- Erik Freeland (erik.freeland@xxxxxxxxxxxxxxx)
Date: Sun Mar 04 2001 - 16:20:17 GMT-3
To clarify a little, before the NDA brigade attack. This was the code
revisions in my home lab
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Pinnacle -- Erik Freeland
Sent: Sunday, March 04, 2001 9:40 AM
To: 'Gordon Olson'; 'Chuck Larrieu'; ccielab@groupstudy.com
Subject: RE: 3 Questions
On my lab I ran 12.0.9 Enterprise Plus Code w/IPsec.
The biggest key to the lab is speed. You have to be fast. this will give you
time to spin the cd. I can do my basic configs quick. this allowed me to
look up almost every item on the lab to triple check things.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Gordon Olson
Sent: Sunday, March 04, 2001 9:04 AM
To: erik@pinnacleinc.com; 'Chuck Larrieu'; ccielab@groupstudy.com
Subject: RE: 3 Questions
Erik & Chuck,
Great stuff! I am trying to establish good habits and it seems that
everytime I setup a lab I use a different approach. I need to build a
routine and practice that each time.
In your Labs, have you upgraded everything to 12.0, where possible?
Thank you,
Gordon
-----Original Message-----
From: Pinnacle -- Erik Freeland [mailto:erik.freeland@pinnacleinc.com]
Sent: Sunday, March 04, 2001 8:47 AM
To: 'Chuck Larrieu'; 'Gordon Olson'; ccielab@groupstudy.com
Subject: RE: 3 Questions
Chuck makes many great points about organization. One additional hint I
learned in ECP1 was to do the following for IP addressing.
Draw a line on your paper. This represents a whole Class B address range.
Then add the numbers below the line to represent individual class Cs.
Finally as you use a network, make a note on the line. Also, if you a told
to use a network note it on the line. This helps you keep from overlapping
network ranges and summarizing correctly.
-------------------------------------------------------------------
0 65 128 192 255
A final note on IP addressing, if at all possible, I made the IP address on
a router the same as the router number. This helps you see where routes are
originating from and if all the routes are present.
The CCIE blueprint says that commands up to 12.0 code can be tested, but it
does NOT say what code is one the routers. In ECP1, we had to perform some
tasks in several ways b/c pre 12.0 code behaved differently. Also, in ECP1,
a router with 12.0.5XK1 code would not perform distribute-lists correctly :)
Regards,
Erik Freeland
CCIE #6854
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Chuck Larrieu
Sent: Sunday, March 04, 2001 7:39 AM
To: Gordon Olson; ccielab@groupstudy.com
Subject: RE: 3 Questions
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