RE: Verification techniques / strategy in the lab

From: Ryan West <rwest_at_zyedge.com>
Date: Thu, 10 Sep 2009 09:08:22 -0400

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] On Behalf Of Irfan Azher
Sent: Thursday, September 10, 2009 7:31 AM
To: 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
Received on Thu Sep 10 2009 - 09:08:22 ART

This archive was generated by hypermail 2.2.0 : Sun Oct 04 2009 - 07:42:03 ART