From: Maljure, Sanjay (smaljure@xxxxxxxxxxxxxxxxx)
Date: Tue May 30 2000 - 11:10:35 GMT-3
Looks like a good list....
I have seen that spending time on the network diagram and addressing is
worth it in the long run.
My approach has also been to work out the entire scenario in my head before
I start going at the routers..This would mean I would have a pretty good
idea of what things will go wrong when I do 'x' and 'y' and what are the
steps to take to make it work.
I also try to write down my points as I complete the tasks. This kind of
gives u an idea of where u are in terms of getting into day2. Also gives u
an opportunity for check validity of results immediately after the task is
completed.
For relaxation (not choking), I told myself before I went into the test that
I would be willing to fail because of topics x, y, z...These were topics
that I were not very comfortable with. So when I got the test I could
immediately see which sections are the ones that I feel very comfortable
about. The last thing that we want to do is lose points in sections that we
are good at.
And very importantly, read the question paper like it is the only thing u
will ever get to read in ur life
Hope this helps. All the best
Sanjay
-----Original Message-----
From: Tony Jackson [mailto:tjackso@earthlink.net]
Sent: Monday, May 29, 2000 9:24 PM
To: ccielab@groupstudy.com
Subject: Ome Day and a Wake Up
Okay fellow techies.
Wednesday, 31st San Jose.
I've studied and studied. 2 1/2years of hands on and lab. I still don't
believe I'm ready for this exam.
I've put together a test strategy I hope to follow. You know like a game
plan before the Super Bowl.
1. Plenty of rest. (I'm spending the night before in a hotel 6 miles out.
2. Read the whole lab booklet first. (I would like to do this one. How much
time will this process consume?)
3. Remain calm. (I think I can do this one. This is not the jungles
of Panama.)
4. Ask the proctor questions. (I suppose I would if I think that they will
help.)
5. Work fast. (I'll try. This is really when the typos start to mount.)
6 Check your work. (Great idea if I have the time.)
This is all that I have listed for myself. Any other suggestions are
welcome.
Tony Jackson, CCNP, CCDA, CNE 4.11
Independant Consultant
Network Systems Engineer
925-202-3993 cell
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Chuah Eng Wee
Sent: Monday, May 29, 2000 5:00 PM
To: Earl Aboytes; ccielab@groupstudy.com
Subject: Re: troubleshooting
Hi Earl,
The way i practice troubleshooting is that I inject the fault, then do a
show......
and debug ......... to observe the symptoms when such faults occur. Of
course,
if u have someone to inject the fault, that will be great
Have fun !!
Eng Wee
CCIE #5335
At 02:51 PM 5/29/00 -0700, Earl Aboytes wrote:
>How do you guys practice troubleshooting? If you are the one to inject
>the trouble, you know what to fix.
>
>
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>Earl Aboytes
>
>Senior Technical Conultant
>
>GTE Managed Solutions
>
>805-381-8817
>
>earl.aboytes@telops.gte.com
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:32 GMT-3