From: Carlos G Mendioroz (tron@huapi.ba.ar)
Date: Tue Mar 15 2005 - 21:48:36 GMT-3
I second that! (KISS, that is, Keep It Simple & Stupid)
I think this is a very good example of YMMV (Your Mileage May Vary)
TCL opens a world of things in the router, a world that you may already
be at ease with, or a new one. If the later is your case, then just take
it easy and (if you really insist) learn a recipe or two.
On the other hand, if you come from the programming arena, scripting can
save you a lot of time (and a lot more with centralized scripting via
rsh) and it surely deserves some time to master and add to your bag of
tricks. The time to setup the framework is not nil though, so I would
use it only if I encounter a problem, but that's my point of view.
In fact, I learned how to program tcl functions like reachable(Router,
Net, Mask) that would only print an error when a given network was not
reachable from a given router. A couple of foreach blocks would let you
assert that all of your networks are present in the routing table of all
of your routers or else pinpoint which one was not and where.
You can have variables with the list of your routers and the list of
your networks to make it even easier... the sky is the limit :)
I did learn how to do it, but in the end, I did not use it...
Bob Sinclair wrote:
> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Carlos G Mendioroz <tron@huapi.ba.ar> LW7 EQI Argentina
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:46 GMT-3