From: HP-France,ex2 ("SANCHEZ-MONGE,ANTONIO)
Date: Thu Feb 19 2004 - 10:21:00 GMT-3
Here you go:
List of source IPs:
1.1.1.1
2.2.2.2
List of destination Ips:
3.3.3.3
4.4.4.4
5.5.5.5
6.6.6.6
7.7.7.7
tclsh
foreach i {
3.3.3.3
4.4.4.4
5.5.5.5
6.6.6.6
7.7.7.7
} { foreach j {
1.1.1.1
2.2.2.2
} { ping $i source $j repeat 3 }}
tclquit
Cheers,
Ato.
-----Original Message-----
From: Yasser Aly [mailto:blackyeyes00@hotmail.com]
Sent: jueves, 19 de febrero de 2004 14:15
To: Colin.Fowlie@aliant.ca; ahmed.mustafa@sbcglobal.net;
ccielab@groupstudy.com
Subject: RE: Checking the Lab Work
Hi Colin,
When you use the tclsh script to verify reachability, the outgoing interface
IP will be used as the source of the packet. My question is: Is it possible
to write the script in such a way to simualte an extended ping, where you
can define the source IP ?? If yes, then kindly ellaborate.
Regards,
Yasser
>From: "Fowlie, Colin" <Colin.Fowlie@aliant.ca>
>
>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
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:51 GMT-3