From: Bates, Eric M (eric.m.bates@xxxxxxx)
Date: Wed Feb 21 2001 - 14:47:26 GMT-3
I would have to echo Earl's comments. The layered approach to
troubleshooting
helped immensely in my case. I didn't really have the opportunity to color
code the cables, but plugging R2 into port 2 on the switch and so on was an
alternative that worked fairly well.
My approach was to make sure I could access all the devices, then work on
layer 1, then layer 2, etc. Your mileage may vary.
But, I can say from experience that people do pass the first time out.
Eric Bates, CCIE 6560
-----Original Message-----
From: Earl Aboytes [mailto:Earl@dnssystems.com]
Sent: Wednesday, February 21, 2001 12:24 PM
To: 'David Ankers'; ccielab@groupstudy.com
Subject: RE: A story of woe.
David,
I think that your first mistake was goin into the test with the assumption
that you were not going to pass.
Prepare your network with troubleshooting in mind. Color code your cables.
This will let you know whether or not the proctor has switched cables or
addresses fairly easily. Code your ip addresses. The connection between R1
and R2 should be along the lines of 172.16.12.X or 172.16.21.X.
The layered approach is always best to troubleshooting. When I went through
troubleshooting I went router by router to get layer 1 (don't forget to
check your cables!) and 2 up and running. If you are working on router 1
you will have to touch routers that are connected to it but only those
interfaces that are directly attached to router 1. Layer 3 was a little
tricky. I made sure my addressing was correct and then routing protocols.
Internal routing protocols, one protocol at a time, and then BGP.
Do the ISDN and VoIP last. I realize these are layer 2 protocols but I see
them as external technologies.
You've got to assume that you will pass this test. Assumption of failure is
doomed to failure.
Earl Aboytes, CCIE 6097
-----Original Message-----
From: David Ankers [mailto:d.ankers@chello.nl]
Sent: Wednesday, February 21, 2001 9:19 AM
To: ccielab@groupstudy.com
Subject: A story of woe.
Group,
I'd like to give a little something back that might help someone else's lab
attempt where mine failed. It all started Monday morning with my first
attempt at the lab in Brussels, arrived early feeling relaxed as I only was
interested in having a look what the lab was about as apparently nobody
really passes first time anyway. Day 1 started a little slowly, read the
whole exam and although it was demanding I've spent a lot of time studying
and I felt I could at least configure everything, this was the first time I
though "hey, might make it to see what day two is about". From their on in
it
just got better, as I configured each section in turn and tested it, I knew
it was the best could do and I didn't spot any issues. I finished the whole
of day with one and a half hours to spare, checked everything and left at
the
end of the day. I missed only 2 points from day one due to a not really
understanding the question.
So, I got to see day two, I had a feeling what was on it as I knew what main
topics where missing from day 1, they are not my strongest but at least I
get
to see the day 2 lab. I opened the folder and read the exam and it wasn't
too
bad, there were a couple of things I didn't know 100% but I just got my head
down. I finished the first run of day two and looked at the clock, only 45
mins, I checked a few things with the CD, got a coffee and went back and did
the lab again. I did everything I knew and even if I had a week longer I
would not have spotted the issues I lost points on. On day two I lost a
total
of 4 points.
Having lost only 6 points I was going to make it to troubleshooting. I
thought, great I get to see what troubleshooting is like not bad for a first
go and it'll really make the second attempt easier. Then I thought, hey I
only need less than half the points and I've passed, there might not even be
a second attempt Once I realized this, I got nervous, badly. In the time
between lunch and troubleshooting I went completely to bits and
troubleshooting was a disaster, a total of 8 points. Its indicated on the
Cisco web page and in Cisco press books that a passing score is 80 points so
I its within the NDA to say I only needed 11 points on TS. It wasn't only
going to bits on the TS, even if I would have stayed calm I don't think I
would have passed, my troubleshooting was awful. I didn't know where to
start
what router to start on etc. In fact the first 2 mins went very well as I
checked if I had access via the console port to enable mode to all routers
and fixed the problems in 2 mins. It's when I had full access that things
went wrong.
Now I need your help like I've never needed it before :-) How is the best
way
to handle troubleshooting? I know the idea is to get layer 1 up then layer
2,
no problem I did that but all the layer 3 addressing etc was just plain
messed up, the amount of errors was massive. Just didn't know where to
start
and with the nerves I wasn't thinking straight either. Lesson here stay
calm.
Two things, help with the methology, first do I keep the messed up addresses
and try and fix them or do I re-type my ones on my map? What do I work on
first, getting connections between just two routers for all protocols and
move on from there or do I get all of ip running on all routers then do the
routing + other protocols?
What I'm thinking is if I had a network like this:
R1-R2-R3-R4-R5
Lets say layer 2 is sorted. I should get R1 to talk IP with R2 and then R2
to
talk ip with R3 and then R3 to talk with R4 etc... Then check the routing
protocols are running on the correct interfaces and see if this routing
protocol works between all routers i.e. I can see R5's routes from R1 and
vice versa?
My biggest mistake was not thinking about TS before at all, the first time
I've really had a clear head to think about what I should have done is now.
I
never expected to get anywhere near it and when I did I froze because I had
no plan at all. Hopefully another bit of advise, if your reading this and
think you do troubleshooting everyday so it should be OK, the lab is not
everyday TS, it a lot of problems in a very short space of time, without a
real plan of attack it's very difficult.
Any ideas on how you either did this or think is a good idea? Also if I make
a lab on my home rack would any of you guys be willing to either A let me
send you the configs you mess them up and I'll tftp them to start up and
realod or B log into my rack and mess them up badly. Won't be straight away
because I want some time off now.
Well, I'm not yet a CCIE but seeing the lab helped a lot and also confirmed
that I have actually learnt something over the years. 12 people started the
lab and 4 gained thier CCIEs, one of these had 57 points going in to TS. The
ones that failed on day 1 never expected it to be that hard and there was
some really wacky stuff that really tested your knowledge in some serious
depth. From the experience I'm happy at the standard of the questions and
the
way the exam is run, I failed fairly as it was a really weak point that
brought me down and nothing more.
Regards,
David.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:55 GMT-3