From: Robert LaGrasse (rlagras1@xxxxxxxxxxxxxxx)
Date: Thu May 11 2000 - 14:46:40 GMT-3
It all depends on what your background is. If you're a design and
implementation guy, troubleshooting may be difficult for you. If you're a
maintenance guy, troubleshooting is the easy part -- Maintenance is where I
cut my teeth and I didn't miss anything in troubleshooting.
During the construction phases, document everything. The diagram is only
worth a point in the lab, but it is your best friend in the troubleshooting
section.
-B
-----Original Message-----
From: Asbjorn Hojmark <Asbjorn@Hojmark.ORG>
To: 'Pieter Bloem' <pbloem@fastwire.com.au>
Cc: ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Wednesday, May 10, 2000 2:17 PM
Subject: RE: Hi All
>
>> Anyone with tips on how to get through the last three hours I
>> would be grateful !
>
>In my experience, the setup for troubleshooting is so extremely
>fucked up, there's no chance you can correct all the errors in
>the two hours you have.
>
>I think the only way to pass is to make sure you don't lose too
>many points before going to troubleshooting and then settle for
>15+ points.
>
>I made it to troubleshooting and actually made the highest num-
>ber of points of the three who did. But that wasn't enough to
>make up for the points I lost on the first day and a half.
>
>-A
>--
>Heroes: Vint Cerf & Bob Kahn, Leonard Kleinrock, Robert Metcalfe
>Links : http://www.hojmark.org/networking/
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:28 GMT-3