From: Aaron K. Dixon (adixon@xxxxxxxxxxxxxxxxxxxxx)
Date: Fri Dec 29 2000 - 18:41:19 GMT-3
I would stick to the way you've been doing things. When I took my lab I
made a very detailed L2/L3 map and then went straight to configuring
everything. They don't like to see any commands on the map. I've heard
that this is due to the fact that you may troubleshoot your own network and
you shouldn't need syntax. The L2/L3 information should be everything that
you need.
Regards,
Aaron K. Dixon
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Nick Tucker
Sent: Friday, December 29, 2000 4:51 PM
To: ccielab@groupstudy.com
Subject: 2 q's about the lab
BTW.. if either of these violate the NDA...please just don't respond.
Personally I dont think they will, I'm just trying to paint a bigger
picture of what I am up against next week ;)
1. For instance...will you be given an output from any command (say "sh ip
bgp") and be told to make one of your rrouters list look like that with no
other instructions?
2. Would it be considered good practice to fully draw a diagram and of all
your L2/L3 address/etc, and then write our your configs on paper from
looking at your diagram before jumping staight into the config?
I ask #2 because what I have always done is drawn out a diagram properly
labled, and then proceeded to jump straight into the configs and wing it
until it worked. From my understanding this would not be a good tactic to
use in the lab, just looking for opinions on this.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:13 GMT-3