From: Fowlie, Colin (Colin.Fowlie@aliant.ca)
Date: Thu Feb 19 2004 - 09:51:51 GMT-3
Whenever I was building practice scenarios I keep a copy of all IP addresses/networks in use in a text file. From there you can build a tcl script that will ping all active IP addresses and also check for all routes.
i.e.
tclsh
foreach IPS {
1.1.1.1
2.2.2.2
3.3.3.3
4.4.4.4
} {ping $IPS}
tclsh
foreach IPS {
1.1.1.1
2.2.2.2
3.3.3.3
4.4.4.4
} {show ip route $IPS}
Then you can quickly see if anything that should be there or should be reachable is failing.
I also like to run a "debug ip routing" when I'm not working on a device to ensure route stability. I usually check all routing tables incrementally to see that routes are being added/redistributed as I put them into the IGP... I'm sure there are lots of other shortcuts/tips you can use, but I find those are some of the ones that have worked for me.
Colin Fowlie
#12757
-----Original Message-----
From: Ahmed Mustafa [mailto:ahmed.mustafa@sbcglobal.net]
Sent: Wednesday, February 18, 2004 11:44 PM
To: ccielab@groupstudy.com
Subject: Checking the Lab Work
Guys,
What is the easiest way to check the lab work. This is the most important
task especially if one is taking a real lab.
I mean what is the best way to find out that you are seeing all the routes in
your routers that are you are supposed to be seeing, and pinging all the
interfaces making sure that there is no loss of connectivity. I know that one
can do this from each router to see what routes are seen and whether they are
pingable
Is there any work around?
Thanks,
Ahmed
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:51 GMT-3