Re: Verification techniques / strategy in the lab

The route profile is a little less intrusive and is a good method to
check yourself. Like you noted, I prefer the "in your face" method of
debug ip routing!

*Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,

JNCIE-M #153, JNCIS-ER, CISSP, et al.

JNCI-M, JNCI-ER

evil_at_ine.com

Internetwork Expert, Inc.

http://www.InternetworkExpert.com

Toll Free: 877-224-8987

Outside US: 775-826-4344

Knowledge is power.

Power corrupts.

Study hard and be Eeeeviiiil......

Ryan West wrote:
> Mark,
>
> I'm not finding much value in that command either :) I remember Brian Dennis
> on a CoD saying to enable it. I think the preferred method that a lot of
> people use is 'deb ip routing' and checking the logs / console for unexpected
> changes.
>
> -ryan
>
> From: Mark Matters [mailto:markccie_at_gmail.com]
> Sent: Thursday, September 10, 2009 9:47 AM
> To: Ryan West
> Cc: Irfan Azher; ccielab_at_groupstudy.com
> Subject: Re: Verification techniques / strategy in the lab
>
> Ryan,
>
> I tried 'ip route profile' before but I am not sure what I am looking for. The
> documentation does not provide any exampled that I can use to learn from.
>
> Can you explain how to use 'ip route profile"? What should I be looking for?
>
> Thanks
>
> On Thu, Sep 10, 2009 at 9:08 AM, Ryan West
> <rwest_at_zyedge.com<mailto:rwest_at_zyedge.com>> wrote:
> Irfan,
>
> Time permitting, I would mentally redo the entire lab and run the
> verifications for each task. But at a minimum, I would make sure that nothing
> changed in your routing table and that the ping results were the same, may
> want to use 'ip route profile'. Also remember that anything that you added to
> the lab (aliases etc) will be removed at the end, so it's good to keep that in
> mind, just use the same technique for getting them to remove them.
>
> -ryan
>
> -----Original Message-----
> From: nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>
> [mailto:nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>] On Behalf Of
> Irfan Azher
> Sent: Thursday, September 10, 2009 7:31 AM
> To: ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>
> Subject: Verification techniques / strategy in the lab
>
> Dear all,
>
> What can be describe as best way to verify the lab after completion of your
> lab.
>
> As I understand the best verification is done right after u completed your
> task, but if you have completed your all tasks and luckily have spare time
> what ll the best practice for verification. For example for end to end
> connectivity ping script cane be used then verify each task one by one by
> again reading the task and verifying it with show commands.
>
> Kindly share if some one used a good strategy for verification in limited
> time.
>
>
> Best Regards
>
> Irfan Azher
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
>
> --
>
>
> -
> "The more I learn the less I know". This is incredibly frustrating to me.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Sep 10 2009 - 10:24:22 ART