From: Calton, Doug (Doug.Calton@getronics.com)
Date: Fri Mar 26 2004 - 06:10:26 GMT-3
That's great advice - a coworker also mentioned the write command. I
got conditioned against that with the ccnp written exams, probably and
had forgotten all about it. Funny how long it takes to retire old code
sometimes, eh?
-----Original Message-----
From: George Yiannibas [mailto:hintgy@hotmail.com]
Sent: Friday, March 26, 2004 2:56 AM
To: Calton, Doug; ccielab@groupstudy.com
Subject: RE: Failed 2nd Attempt
Doug,
Having also failed twice I feel your pain. Take an honest look at your
weaknesses, rest a bit, rewrite your study plan and go for it. For
example
(I hate to nitpick here but I must) copy run start is way too long
command
for a CCIE Lab participant. Try wr insted (short form for write memory,
older command but still works fine). Sometimes, no always in the Lab,
it's
the little things can make a difference between a pass and a fail
Best of luck
George
>One side story for my day that probably defined the day for me overall:
>Early on, I had some debugs streaming on my screen as I typed in copy
>run star And of course, it ended up coming out as "copy runs tar".
>Anyway, when I answered the prompt through the blur of debugs, I didn't
>recognise that it was asking me if it should erase flash prior to
>saving "tar", and not what to name the running config. Had to go to
>the proctor with hat in hand to ask him to restore my flash. Maybe I'm
>just fighting a losing battle here, eh?
>
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:48 GMT-3