From: Scott Morris (swm@emanon.com)
Date: Tue Mar 15 2005 - 23:57:33 GMT-3
I'll agree with that, and add that it's all based on what you are used to.
If you have months and months before your lab, it's likely worthwhile to
learn. If your lab is next week and you don't know tcl scripting, don't
bother.... This is another area that a good diagram will come in handy and
look for key things in the lab!
But, it is indeed a powerful tool!
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Bob
Sinclair
Sent: Tuesday, March 15, 2005 7:27 PM
To: robbie; ccielab@groupstudy.com
Subject: Re: tclsh Tips for the lab?
Robbie,
I am a total believer in the utility of a simple ping script to test
reachability - I use it every day in class and in lab development. But you
do not want to spend time and energy troubleshooting a script. I have seen
clueful guys use the RCMD tack in practice lab after practice lab, only to
end up in script-trouble when a minor difference cropped up in the real
thing.
KISS!
HTH,
Bob Sinclair
CCIE #10427, CCSI 30427, CISSP
www.netmasterclass.net
----- Original Message -----
From: robbie
To: ccielab@groupstudy.com
Sent: Tuesday, March 15, 2005 6:20 PM
Subject: tclsh Tips for the lab?
I see that Gladston's posted some quick tclsh scripting to automate the
process of checking for connectivity, but does anyone else perhaps have
a short primer on tclsh as it relates to the lab? I'd love to see
exactly what people have come up with to improve their speed in checking
things like that. Any suggestions? Thanks a ton.
robbie
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:46 GMT-3