From: Elias Chari (elias.chari@gmail.com)
Date: Sun Feb 25 2007 - 07:44:24 ART
I think sometimes too much emphasis is put on check lists. The only think
you have to do is verify each task before you move on to the next. If you
know how to do that you don't need to have a long check list. You should
check each task objective against your configuration. Use show and debugging
(where necessary) commands to achieve this. This is your checklist...-)
The only mental notes that I made were voip ports (never managed to find
them on the univercd) and remember to send the community to BGP peers, if
required.
-- Regards, Elias CCIE#17354On 2/25/07, Darby Weaver <darbyweaver@yahoo.com> wrote: > > Do you have a script to for the Switch Macro? > > Do you have a list of show commands for your QoS? > > Do you have a list of show commands and have a > procedure to check you Multicast configuration? > > Did you double-check your BGP? > > Did you verify your frame relay has no inarp? > > Did you check your Switches for Root, Paths, values, > etc. > > Did you check your neighbor relationships for each > routing protcol? > > Did you check whatever you may have been asked to do > with regards to NAT, Telnet, SSH, DRP, WCCP, etc.? > > If you have virtual links are they working, if they > are supposed to authenticate, are they? If you were > asked to authnticate on a per link basis - does this > work, how about a per area basis? > > If you were asked to SPAN/RSPAN is it working, how > about any port security? > > Let's see, if your were asked to Bridge, does it work? > > If you were asked to use IP SLA, did you meet the > requirements asked? > > If you were asked to match a table for anything or a > certain show output, does yours match as requested? > > If you were asked to ensure a certain value for > anything in particular does it match? > > If you were asked to restrict or allow certain routes, > even or odd, or as specified, did you meet the > requirements? > > Are you prepared to ask the proctor about any > ambiguities? > > If you were asked to perform some type of shaping or > policing or even queueing are your results what is > expected? How about the default class? Did you > specify it? Why/Why not? Did you ask yourself the > question? > > If you were asked to change any values or DSCP values > do you know how? > > If you have tunnels, did you watch for recursive > routing? > > If you had to change any timers or metrics, does > everything match in the AS or domain in question? > > You did not forget about Split-Horizon anywhere, did > you? > > > If you are given a chance to call one person - a > lifeline? Who would it be? > > If you are asked not to hum... are you prepared to > work without humming? > > Hmmm... > > I'm sure I missed something... > > But these are at least some of the things I think of > on most of my labs... these days... > > In reality, I take the lab questions and try to > approach them from a layer by layer layer basis? > > Does this help you at all? > > Remember your checklist vs. anyone's lab - any time / > any place. > > Whether you are sleepy, cold, or hot... mad or > happy... > > Be ready for whatever may come at you through those > doors at the testing facility of your choice... > > > > > --- Daniel_Steyn@Dell.com wrote: > > > Say a prayer > > > > > > -----Original Message----- > > From: nobody@groupstudy.com > > [mailto: nobody@groupstudy.com] On Behalf Of > > David A Goddard > > Sent: Saturday, February 24, 2007 8:52 AM > > To: ccielab@groupstudy.com > > Subject: Final checks > > > > Hello group, > > > > I'm about to take a shot soon and am in cram mode. > > A quick search of > > the archives didn't reveal what I'm looking for. > > Here it is: > > > > What are your final checks you perform during the > > lab exam. In other > > words, you've accomplished all tasks, and *think* > > everything is good to > > go. You've got an hour to burn before your time is > > up - what do you do? > > I'm trying to compile a quick hit list of what I > > should look at. Here is > > what I've come up with thus far: > > > > 1) Ping scripts > > a) IGP > > b) EGP > > > > 2) Debug ip routing - check to see if any routes are > > flapping > > > > 3) Verify all access-lists have 'deny all' or > > 'permit all' if needed > > > > 4) Reread and verify lab objectives to insure > > thoroughness and accuracy > > > > What else? > > > > thanks, > > Dave > > > > > _______________________________________________________________________ > > 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 : Thu Mar 01 2007 - 07:38:48 ART