- A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
RE: OT: 4 weeks and counting posted 05/22/2001
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]

I kept this advice, as offered by Roger Dellaca, CCIE # 6671 on this forum
last January. Note the very simple logic to it - I for ip, x for ipx, etc -
very simple pneumonic. Note also the manner in which the aliases can be used
as the basis for more complex commands. In terms of helping alleviate the
fat finger stuff, which I found to be the real time killer, this kind of a
process is worth considering.

I myself am not a big alias kinda guy, but after my bad experience in the
Lab, losing a lot of time because of my typos, I think I will incorporate
this advice into my regimen.

Begin Roger's advice:

Did a standard set of commands in Notepad to paste in all routers.  My
alias exec ii sh ip int
alias exec ib sh ip int brief
alias exec ir sh ip route
alias exec xi sh ipx int
alias exec xb sh ipx int brief
alias exec xr sh ipx route
alias exec pr sh ip protocol
alias exec cr clear ip route
alias exec cb clear ip bgp
alias exec b sh ip bgp
alias exec e sh ip eigrp
alias exec o sh ip ospf
alias configure a access-list

for some of these you have multiple uses, for example cb * for all neighbors
or cb <neighbor address> for a specific neighbor (I like typing in b s for
sh ip bgp summary).  I practiced with the aliases enough so they were second

End Roger's advice


-----Original Message-----
From:	nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf Of Rick
Sent:	Monday, May 21, 2001 2:43 PM
To:	ccielab@xxxxxxxxxxxxxx
Subject:	RE: OT: 4 weeks and counting

Good point about speed, brings up a question about aliases. Some people have
referred to creating aliases for commonly used commands, and over and over
again we hear about time management being key to success.

I wonder what is the real benefit to an alias where "si" is short for the
command "sh ip int brief".  I think typing out the command might take 1.5
seconds, whereas the alias might take .5 seconds saving 1 second ... is the
time factor really that tight?

I agree that short 15 minute drills of core topics would be extremely
beneficial, we repeatedly hear advise to have the core topics down cold.
Being able to bang out a quick configuration without having to think about
how to do it or what the gotchas are would appear to be a necessity.

I am still a few months away from my first attempt so I am by no means an
authority on speed and time management. Some insight by those who have gone
through the experience may be helpful.

-----Original Message-----
From: Mask Of Zorro [mailto:ciscokid00@xxxxxxxxxxx]
Sent: Monday, May 21, 2001 4:08 PM
To: jhealis@xxxxxxxxx; ccielab@xxxxxxxxxxxxxx
Subject: Re: OT: 4 weeks and counting

Speed baby! Speed!

At this point, you know what you know (and you don't know what you don't
know)... There will be no useful new learning between now and then. BUT -
how fast can you get that thing built???

Do short speed drills - build a hub and spoke frame architecture with a mix
of physical interfaces and sub-interfaces and have full connectivity in
under 15 minutes.

Build an ISDN connection with PPP authentication in 15 minutes. Then blow it

away and try it with one-way authentication, again in 15 minutes. Then again

with callback...

Implment OSPF authentication on area 0 of a multi-area network in under 15

You get the idea. Shoot for the 15 minute mark for all these little snippets

of technology. Do these things over and over from scratch until your fingers

can build them while the rest of you just watches...  Make sure you start
over from a clean router config each time, or the repitition will do you no

If you can build the core stuff quickly in the real lab, then you will have
plenty of time for the head-scratchers that are destined to be there.

Good luck!


>From: Jim Healis <jhealis@xxxxxxxxx>
>Reply-To: Jim Healis <jhealis@xxxxxxxxx>
>To: ccielab@xxxxxxxxxxxxxx
>Subject: OT: 4 weeks and counting
>Date: Mon, 21 May 2001 13:02:55 -0700
>(The OT listing is for those who don't wish to hear the journal-esque
>ramblings of a Lab candidate)
>I'm four weeks away now from my first lab attempt.
>I must say that the psychological aspect of the exam has been taking its
>toll on me.  In the last couple weeks I have lost sleep because of
>nightmarish dreams about routing, switching and the upcoming lab exam.
>I have been trying to force myself to study more and more as my lab date
>comes closer. But each time I do my mind tells me that I have done this
>over and over before and trying any harder will only cause loss of some
>other engram.  So I try to soak in what I can when I can get it.  I work in
>a department that has me solving complex LAN issues nearly every hour, so I
>feel that I am strong there.  My WAN knowledge is a bit dated however. I
>know Frame Relay very well, and leased circuits are easy too... ISDN is a
>bit rusty.
>More complex routing features seem distant to me now. Policy routing is
>easy for me once I get started, but knowing when to use it eludes me at
>times.  Redistribution is easy on the surface, but with more complexity I
>forget about how easy it is to screw up.
>The bottom line is that I feel I know what I need to know to pass the Lab
>exam, but I am fearful that I will not be able to recall it under such
>pressure.  This has caused me to contemplate postponing my exam for a
>couple months (like I could get a new date now).  But the optimistic part
>of me says I have to take it now to know what challenge I face, or I will
>never be brave enough to face the challenge in the future. In other words,
>once you start running away it's easier to keep running than to face the
>So my request to those in the group is this: What should I be focusing on
>in these last few weeks considering this feeling of burn-out on studying?
>I'm looking for direct responses, philosophical answers and mystic
>**Please read:
Get your FREE download of MSN Explorer at
**Please read:
**Please read:
**Please read:
To unsubscribe from the CCIELAB list, send a message to
majordomo@xxxxxxxxxxxxxx with the body containing:
unsubscribe ccielab