Re: testing lab connectivity

I'm familiar with that. I wonder if it works in Putty. Have the labs
completely converted to Putty? I thought I saw some threads on it.

--Hammer--

On 8/26/2010 10:33 AM, Grammer, Christopher wrote:
> A cool trick I learned with Secure CRT:
>
> On each router issue the command:
>
> show ip alias
>
>
> R1#sh ip alias
> Address Type IP Address Port
> Interface 1.1.1.1
> Interface 10.10.50.1
> Interface 150.50.24.4
> Interface 200.0.0.4
>
> Now, in secure CRT, hold down the ALT key and selectively highlight
> the IP addresses and paste them into notepad for your TCL script.
>
> Chris
>
>
>
>
> On Thu, Aug 26, 2010 at 10:28 AM, Carlos G Mendioroz <tron_at_huapi.ba.ar
> <mailto:tron_at_huapi.ba.ar>> wrote:
>
> Some options you may consider to complement whatever you use:
>
> -debug ip routing
> This will show quite fast if you have some instability because of
> redistribution
>
> -tcl based route availability checks
> instead of pinging, just find out at every router if your routes
> are there
>
> -remote exec
> instead of changing the terminal to see at every router, use
> remote command so you may use 1 tcl script to coomand the whole show
>
> -Carlos
> --Hammer-- @ 26/8/2010 10:45 -0300 dixit:
>
> Sorry CCIE UY, I was somewhat joking. There are a multitude of
> show commands to give you a good gauge of your reachibility in
> a lab. However, other than ping, I think TCL is the generally
> preferred (as in optimal) method by most of the instructors on
> the forums for good reason. I'm not aware of anything more
> effective for "scanning" your topology quickly to determine if
> you have lost any connectivity. The hardest part is keeping
> track of all the physical interfaces and loopbacks and whatnot
> to make sure your script has everything covered.
>
> --Hammer--
>
>
> On 8/25/2010 8:51 PM, CCIE UY wrote:
>
> Ping line by line... takes a lot of your time...
>
>
> 2010/8/25 --Hammer-- <bhmccie_at_gmail.com
> <mailto:bhmccie_at_gmail.com> <mailto:bhmccie_at_gmail.com
> <mailto:bhmccie_at_gmail.com>>>
>
> Ping?
>
> --Hammer--
>
>
>
> On 8/25/2010 2:22 PM, CCIE UY wrote:
>
> Hi Guys, is there any other or better solution
> than to
> create a TCL
> script in Routers to verify conectivity in the real
> lab?
>
> Regards.
>
> Horacio.
>
>
> Blogs and organic groups at http://www.ccie.net
> <http://www.ccie.net/>
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
> Blogs and organic groups at http://www.ccie.net
> <http://www.ccie.net/>
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
> --
> Carlos G Mendioroz <tron_at_huapi.ba.ar <mailto:tron_at_huapi.ba.ar>>
> LW7 EQI Argentina
>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 26 2010 - 10:35:25 ART