From: Chris Riling (criling@gmail.com)
Date: Tue Nov 27 2007 - 18:29:57 ART
I might be slightly paranoid about changing things that aren't specifically
spelled out in a task, not sure if I should be *this* paranoid or not. I
think I would quickly look over the info, and keep any possible problems in
the back of my head, then later if they created a problem with something I
was supposed to configure then I might start changing things... Is this a
horrible approach?
Chris
On 11/27/07, Scott Morris <smorris@ipexpert.com> wrote:
>
> That always depends on the evils of the lab... :)
>
> "sh ip int br | exc una" is a good place to get your IP addresses.
> "sh run | in interface|ip address" is a good place to get your interface,
> IP
> and MASK information.
> "sh int | in is up|Internet" is a good place for interfaces that are
> really
> up, plus IP and VLSM information.
>
> Tweak things around for whatever you are searching for! But each lab may
> be
> different in terms of how much is or is not preconfigured for you!
>
> HTH,
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
> JNCIE-M
> #153, JNCIS-ER, CISSP, et al.
> CCSI/JNCI-M/JNCI-ER
> VP - Technical Training - IPexpert, Inc.
> IPexpert Sr. Technical Instructor
>
> A Cisco Learning Partner - We Accept Learning Credits!
>
> smorris@ipexpert.com
>
>
>
> Telephone: +1.810.326.1444
> Fax: +1.810.454.0130
> http://www.ipexpert.com
>
>
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Scott Vermillion
> Sent: Tuesday, November 27, 2007 2:29 PM
> To: 'Rakesh Menon (rakmenon)'; 'Cisco certification'
> Subject: RE: Initial mistakes and correction - How to and when
>
> Hi Rakesh Menon,
>
> What I have started doing in my practice labs is a simple 'sh run'
> everywhere and also 'sh cdp neigh' to see if things are synched with the
> topology drawing/lab text. You will typically find a few bad IP
> assignments, IP address swaps b/t interfaces, etc. I don't know if you
> want
> to be bothering with trying to come up with some type of automated ping
> script at the outset of the lab. I think you should be able to pick up
> the
> little surprises the proctors have left for you with a simple manual
> review
> of things against the information given.
>
> But my first date with the actual lab isn't for a few months yet, so take
> that all with a grain of salt...
>
> Regards,
>
> Scott
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Rakesh Menon (rakmenon)
> Sent: Tuesday, November 27, 2007 11:38 AM
> To: 'Cisco certification'
> Subject: Initial mistakes and correction - How to and when
>
> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> 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