From: Tom Larus (tlarus@cox.net)
Date: Fri Apr 18 2003 - 12:39:10 GMT-3
I don't know about the exam, and would not say anything if I did, but in my
home lab, I found helpful software that pinged verious IP addresses to see
if they were still there, as well as SNMP trap watching/catching software.
Check out www.hojmark.net, for links to SNMP manager software with the
former cabability and also trap watching/catching software. Yes, I know
"catching traps" is not the right jargon, but I like it. (I would not want
to catch traps used in trap shooting, though.)
You learn a lot of about what the true state of your home lab network when
you see interfaces become reachable, and then unreachable. This was a VERY
important part of my CCIE learning process.
Tom Larus
----- Original Message -----
From: "Wayne Hines" <wayneh@DataNetDev.com.au>
To: "'Kristof Ulrix'" <kristof@uk-systems.com>; <ccielab@groupstudy.com>
Sent: Friday, April 18, 2003 10:13 AM
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