I've been tossing this around for a bit now. Even posted a preliminary on
the cciecert list. I call it The Seven Habits of Highly Successful CCIE's"
my apologies to a good writer of a good book )
But from my early days on this list I have been saving the words and wisdom
of folks who have attained the prize, and have offered their advice. My self
help guru, after all, maintains that one secret to success is modeling. Find
someone who has what you want, find out those things that person does
consistently, do those things yourself, and you can't help but attain the
same success.
So far, here are things I have gleaned:
1) Love what you do. Seems silly, but I have noticed that folks whom I
admire who have attained the prize really love what they do. So much so
that they are able to leverage that love into the hours necessary to master
the material.
2) Learn something new every day. One command. One subtlety. One concept.
3) Help others. In teaching another one can find clarity in one's own
thinking
4) Document everything. Practice documentation when you read a lab, when you
set up a lab, when you try different show and debugs. Document the results.
Compare those results with what you predicted when you first read the lab
and drew out your sketches.
There will be more.
But I have to say, recent posts by our newer CCIE's, have only reinforced
the value and the importance of good study habits, and good work habits. No
one that I have known who has attained the CCIE did so by accident. Or got
lucky. All have done so with focus, determination, and a lot of structured
work.
My congratulations to all who have made it. And all who will soon.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Greg
Myran
Sent: Monday, May 29, 2000 6:40 PM
To: [EMAIL PROTECTED]
Subject: Re: New CCIE
This is excellent advice, and virtually identical to the method I found
successful when I passed last week in Halifax..
It is unfortunate Bruce Caslow is not on this list to see how well his
methodology is helping people get through the CCIE lab..
Greg Myran
CCIE# 5906
At 08:00 PM 5/29/2000 , Joe Martin wrote:
>I have a method that I used for the lab. Mostly developed by Bruce Caslow
>and specified in his book. Here's how I start things out. This is all
>generic information that I used for all my prep work. None of this
material
>is specific to the CCIE lab.
>
>1-Read the entire lab. Think of all the issues involved with the protocols
>and the topology.
>2-Write down specific info in a list regarding IP addressing and interfaces
>and summarization.
>3-Draw a REALLY nice drawing of the network. Leave plenty of room to write
>in addressing info.
>4-Label the drawing with all the interface number.
>5-Use different colored pencils for different routing and routed protocols
>6-Fill in all the IPs from the list you created.
>7-Then fill in the rest of the IPs from the allowed block.
>8-As you read the exam, look to see if they specify summarizing so that you
>create an IP scheme that can be summarized.
>look at each router and write down the type/IOS version/IOS name
>9-Create a script in notepad with all the common commands that you want on
>each router and paste this onto each one. Put the command "hostname " last
>so you can just type in the name of your router and your finished.
>10-Next, put the IP addressing on all of the routers. As you do this do
>whats necesary to turn up the interfaces. Frame Relay/mapping, clock
rates,
>ISDN/ppp/username/dialer-list.
>11-After doing this on each router, go thru and ping each interface, local
>and neighbor. Make sure they are all reachable. Doing this now keeps you
>from wondering if you have a layer 1,2,3 problem and not a routing problem
>that may show up in the steps to come. Remember to that many multipoint
>interface types don't allow you to ping your local interface without some
>extra programming. Also remember spoke to spoke reachability in partially
>meshed NBMA networks.
>12-After doing this, start the main portion of the lab.
>13-Try to save access lists to the end. Remember what access lists will do
>to your network. It can block DLSW, or routing protocols or AURP appletalk
>tunnels, etc...
>14-Try to get done early enough that you can reload your routers and make
>sure everything comes up OK. Remember that a reload could change your
>router ID for OSPF and mess up your virtual tunnels. But, by IPing all of
>your routers before appying routing protocols will help avert these types
of
>problems.
>
>THINK, THINK, THINK.
>
>Other tips:
> IPX ROUTING X.X.X where X=your router number. Ex. Router 1 will
become
>IPX ROUTING 0001.0001.0001
> This tip makes it easy for frame relay mapping, ISDN mapping and
IPX
>ping testing.
> APPLETALK CABLERANGE X-X X.Y where Y=router number.
> This also makes if easy for frame relay mapping, ISDN mapping and
>apple ping testing
>
>JOE
>CCIE #5917
>
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
