From: Deepesh Chouhan (deepesh@cisco.com)
Date: Mon Aug 25 2003 - 18:25:55 GMT-3
Hey Roger
i belong to category of people who check the answers after a subsection.
For e.g. check all IGP after IGP, check all BGP after BGP and so on.
Further i classified verification into three -
1. Basic things - like IP address, rtr names (e.g. config ACL on rtrX) ..
make sure its on RTRx
... Make sure PVCs are correct ....
2. Connectivity/Feature verification
- routes in routing table
- traceroute; prefer this over ping ... helps in detecting asymmetric
routes
- ping
- For features not verified by connectivity; show commands; e.g. QOS
traffic parameters.
You should know 'show' commands for all features
3. English
- Have i read the question correctly; is this what was required
- Why do i have multiple solutions for this question. Why can't i rule out
some solutions
Hope that helps
thanks
Deepesh
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Roger McNeace
> Sent: Monday, August 25, 2003 1:38 PM
> To: 'ccielab@groupstudy.com'
> Subject: Lab verification techniques
>
>
> I have now failed the lab 3 times. I know all the material and
> felt fairly
> confident going in, but I believe I am getting killed on the details that
> can only be caught with plenty of time for review. In my opinion the lab
> should be completed within 5-6 hours with 2-3 hours for review. I would
> like to get some feedback on what techniques people are using to
> check thier
> configs during the lab. What show commands, debugs, ping scripts etc.
>
> Example
>
> all IGP routes reachable - ping every device in route table (gotta be a
> faster way)
> Routing loops - debug ip routing
>
> etc
>
>
> _______________________________________________________________________
> You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:54:06 GMT-3