From: Mike Williams (ccie2be@swbell.net)
Date: Fri Apr 18 2003 - 19:40:32 GMT-3
WOW.... So what's this TCL Shell and where can I find more info on how
to use it in Cisco gear? (Not being lazy, as I'm doing Google searches,
but just thought I'd ask)
TIA,
Mike W.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Brian Dennis
Sent: Friday, April 18, 2003 12:48 PM
To: rich@myhomemail.net; ccielab@groupstudy.com
Subject: RE: Quick method for testing reachability of all interfaces of
all routers?
You are in config mode. The tclsh command is an enable mode command.
Also I haven't personally tested it with 2500's or 4000's.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
Director of CCIE Training and Development -
IPexpert, Inc.
Mailto: brian@ipexpert.net
Toll Free: 866.225.8064
Outside U.S. & Canada: 312.321.6924
-----Original Message-----
From: Richard Davidson [mailto:rich@myhomemail.net]
Sent: Friday, April 18, 2003 10:41 AM
To: Brian Dennis; 'Wayne Hines'; ccielab@groupstudy.com
Subject: RE: Quick method for testing reachability of all interfaces of
all routers?
Is that in a specil feature set? It doesn't work on 12.1(5)t12.
r1(config)#tclsh
^
% Invalid input detected at '^' marker.
r1(config)#
r1#s ver
Cisco Internetwork Operating System Software
IOS (tm) 4500 Software (C4500-JS-M), Version
12.1(5)T12, RELEASE SOFTWARE (fc1)
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 04-Feb-02 09:42 by ccai
Image text-base: 0x60008968, data-base: 0x6102C000
ROM: System Bootstrap, Version 5.2(7b) [mkamson 7b],
RELEASE SOFTWARE (fc1)
BOOTFLASH: 4500 Software (C4500-BOOT-M), Version
11.1(7), RELEASE SOFTWARE (fc2)
--- Brian Dennis <brian@labforge.com> wrote:
> Yes this works with IOS 12.1T.
>
> Rack2R4#sho ver | inc (^IOS)|(bin)
> IOS (tm) C2600 Software (C2600-JK2O3S-M), Version
> 12.1(5)T9, RELEASE
> SOFTWARE (fc1)
> System image file is
> "flash:c2600-jk2o3s-mz.121-5.T9.bin"
> Rack2R4#tclsh
> Rack2R4(tcl)#
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> Director of CCIE Training and Development -
> IPexpert, Inc.
> Mailto: brian@ipexpert.net
> Toll Free: 866.225.8064
> Outside U.S. & Canada: 312.321.6924
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Wayne Hines
> Sent: Friday, April 18, 2003 7:13 AM
> To: 'Kristof Ulrix'; ccielab@groupstudy.com
> Subject: RE: Quick method for testing reachability
> of all interfaces of
> all routers?
>
> But
> 1) Is there a tcl script processor available as part
> of the CCIE 1 DAY
> LAB???!!! (No NDA breakage please!!)
> 2) I want to be able to do this from EACH router.
>
> Wayne
>
> -----Original Message-----
> From: Kristof Ulrix [mailto:kristof@uk-systems.com]
> Sent: Friday, 18 April 2003 23:57
> To: Wayne Hines; ccielab@groupstudy.com
> Subject: RE: Quick method for testing reachability
> of all interfaces of
> all routers?
>
>
> You can use the tcl shell commands:
>
> tclsh
> foreach pl {
> 128.200.1.1
> 133.10.0.1
> 133.10.0.2
> } {ping $pl}
>
> HTH
>
> Kristof Ulrix
>
> -----Oorspronkelijk bericht-----
> Van: nobody@groupstudy.com [mailto:nobody@groupstudy.com]Namens Wayne
> Hines
> Verzonden: vrijdag 18 april 2003 14:26
> Aan: ccielab@groupstudy.com
> Onderwerp: Quick method for testing reachability of
> all interfaces of
> all routers?
>
>
> Hello Group
>
> In the absense of tools such as Ciscoworks or 3rd
> party tools in THE
> LAB,
> has anyone come up with a quick way of testing
> interface reachability
> for
> all interfaces of all routers. (and no I do not
> trust myself to read
> each
> line of the sh ip route output under pressure.)
>
> My thoughts were to create a series of ping
> statements for each
> interface.
> (This can be done quickly by copying all the configs together, sorting
> them
> alphabetically grabing the ip address statements and
> changing them to
> ping
> statements) ie.
> ping 128.200.1.1
> ping 133.10.0.1
> ping 133.10.0.2
> ping 133.10.0.3
> ping 133.10.0.4
> ping 133.10.0.5
> ping 133.10.0.6
> ping 133.10.10.1
> ping 133.10.20.1
> ping 133.10.20.10
> ping 133.10.30.1
> ping 133.10.40.1
> ping 133.10.60.1
> ping 133.10.60.3
> ping 133.10.60.4
> ping 133.10.70.1
> ping 133.10.80.1
> ping 133.10.90.1
> ping 133.10.90.2
> ping 133.200.0.26
> ping 133.200.0.36
> ping 133.200.0.62
> ping 133.200.0.63
> ping 160.100.1.1
> ping 160.100.1.254
> ping 160.100.100.1
> ping 160.100.128.1
> ping 160.100.129.1
> ping 160.100.130.1
> ping 160.100.2.1
> ping 160.100.2.254
> ping 161.100.1.1
> ping 172.16.30.2
> ping 172.16.30.22
> ping 172.16.30.3
> ping 172.16.30.6
> ping 192.168.1.1
> ping 192.190.100.1
> ping 192.190.101.1
> ping 192.190.102.1
>
> but if I try to do a copy/paste to the router via
> either a console
> session
> or a telnet session buffer overflow results and
> characters are dropped.
> Hence this approach as is does not work. Has anyone
> come up with a
> solution
> that enables reliable and quick reachability testing
> of all interfaces
> of
> all routers.
>
> thanks in advance
> Wayne Hines
> B.Sc., M.Sc., CMACS Proj. Man., CSS1, CCDP+Net. Man.+Voice+ATM, CCNP,
> CNE,
> MCNE, MCSE
> Database & Network Developers - your Cisco Premier
> Partner / Novell
> Business
> Partner
> Mailing: P.O. Box 14283 Melbourne 8001
> Email: wayneh@DataNetDev.com.au
> Web: http://www.DataNetDev.com.au/
> Tel: +61 (0)3 9329 6444
> Mobile: +61 (0)41 152 4486
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:58 GMT-3