From: sheherezada@gmail.com
Date: Wed Nov 28 2007 - 14:03:13 ART
The approach that worked for me best was:
1) Log on to all devices and to see if you were given a
pre-configuration in sync with the scenario. The reason to do this
was to discover possible issues with the lab early. Takes 5 minutes.
One time I was given the wrong setup.
2) Read the scenario and do your homework
3) Fix the issues as you complete the Layer 2 tasks, then check basic
connectivity again. "sh run" is great at discovering "typos" and the
like. However, not all issues appear in sh run (I am thinking of VTP,
system MTU, SDM and other goodies). Do not forget to check if console
logging is on.
HTH,
Mihai
On Nov 27, 2007 8:38 PM, Rakesh Menon (rakmenon) <rakmenon@cisco.com> wrote:
> Hi All,
>
> From what I have heard abt the lab, there are a few initial mistakes
> that u have to correct to get a couple of marks (IP Addresses, Mask
> etc). Tried to see if there is a pattern or flow that I could induct in
> my lab practise to find these, but no avail. Just a beginner in the CCIE
> World so don't have much idea abt lab strategy right now.
>
> Please suggest if there are any Tips or Tricks that i can use to find
> these initial glitches. And most importantly when should I start looking
> for them..
>
> Thanks in advance.
>
> With Regards,
> Rakesh Menon
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:31 ART