From: Cheung, Gary YY (gary.yy.cheung@pccw.com)
Date: Tue May 31 2005 - 07:56:48 GMT-3
Hi Thomas
Don't worry and just remember both. The difference in two commands is so
minor.
Regards
Gary Cheung
CCIE#14642, BEng, CEng, MIEE, PMP, PRINCE2,
CISSP, MCSE, SCSA, SCNA
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
thomas.rader@freesurf.ch
Sent: Tuesday, May 31, 2005 6:13 PM
To: ccielab@groupstudy.com
Subject: RE: Testing with TCLSH
Hello Gary,
I don't understand why this works on my routers, and not on yours !
What IOS are you using ?
I'm using 12.2.15(T16)
R1R1#show flash:
System flash directory:
File Length Name/status
1 15192212 c2600-is4-mz.122-15.T16.bin
[15192276 bytes used, 1584940 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
R1R1#
Now I'm worried that my script won't run properly in the lab!
Thanks, Thomas
-----Original Message-----
From: Cheung, Gary YY [mailto:gary.yy.cheung@pccw.com]
Sent: Tuesday, May 31, 2005 12:03 PM
To: thomas.rader@freesurf.ch; ccielab@groupstudy.com
Subject: RE: Testing with TCLSH
My understanding on "puts" is just like the "print" command in most of
programming language.
I had tried your script on my routers before but it won't work. After I used
the script with "puts", it works fine in both my lab and real exam.
Regards
Gary Cheung
CCIE#14642, BEng, CEng, MIEE, PMP, PRINCE2,
CISSP, MCSE, SCSA, SCNA
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
thomas.rader@freesurf.ch
Sent: Tuesday, May 31, 2005 5:53 PM
To: ccielab@groupstudy.com
Subject: Testing with TCLSH
Hello,
I don't understand what the "puts" command does and why it should not having
it should stop my script from working.
I've been using the following script for a while now, and it seems to work
just fine.
tclsh
foreach CCIE {
10.1.1.1
10.2.2.2
10.3.3.3
10.4.4.4
10.5.5.5
10.6.6.6
} {ping $CCIE}
Here is the output of my script:
R1R1#tclsh
R1R1#foreach CCIE {
+>10.1.1.1
+>10.2.2.2
+>10.3.3.3
+>10.4.4.4
+>10.5.5.5
+>10.6.6.6
+>} {ping $CCIE}
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/3/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.4.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/60/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.5.5.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/60/61 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.6.6.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/60/60 ms
R1R1#
Are you saying that without using the "puts" command I might have problems
on the lab ? Please help!
Thanks, Thomas
-----Original Message-----
From: Gary Cheung [mailto:garymsue@netvigator.com]
Sent: Friday, May 13, 2005 7:03 PM
To: Dillon Yang; ccielab@groupstudy.com
Subject: RE: Failed again!
Since most people sent mail asked me about the TCLSH, I would like to share
it for you all.
In Cisco CCIE blueprint, all the routers in the lab are either Cisco 26xx or
37xx and these types of routers can support TCL language. It is very helpful
when you want to test the reachability. Prior to start the script, you need
to dig out all the IP addresses that you want to test or listed in the
diagram. I suggest you using a notepad and the script will like this.
tclsh
foreach addr {
10.1.1.1
10.1.1.3
10.2.2.2
10.3.3.3
.....
} {puts [exec "ping $addr"]}
- You SHOULD add "puts" before executing the ping commands, otherwise, it
wouldn't print out the result to you. Dillion - you may encounter this
problem.
After completing the script, you just copy and paste it into the prompt -
router#. Then you will get the ping result of each address. You need to
check which address is PING fails, and see whether this is a normal case.
PLEASE don't forget those SUCCESSFUL PINGs, you need to check whether it
performs right, may be FAIL should be the right answer.
Remember to run the script in each router (Catalyst 3550 won't support it)
and ensure the meaning of FULL REACHABILITY.
Besides, you need to test it TWICE, one for FR up/ISDN down and one for ISDN
up/FR down.
Before run the "ISDN TEST CALL", you should check the "SHOW ISDN STATUS"
first and ensure the SPID is valid. Otherwise, you need to REBOOT the
router.
Hope this help you.
Regards
Gary Cheung
CCIE#14642, BEng, CEng, MIEE, PMP, PRINCE2,
CISSP, MCSE, SCSA, SCNA
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Dillon Yang
Sent: Friday, May 13, 2005 4:45 PM
To: Gary Cheung
Subject: Re: Failed again!
Hi, Gary:
Congratulations first!
The TCLSH is a very trouble. The routers CAN NOT SUPPORT the
command "foreach" since I can execute the single "rsh $rt show run" as
the document made by B.Caslow in the NMC www page. The version of the
routers are all 12.1(14) with something "i5qxxx" on c2600.
So I have to do the connectivity test by sampling mentioned by
B.Sinclair, its maybe not so complete. IT IS A VERY PITY!
The second strange thing puzzling me is that the command "ISDN TEST
CALL interface" that mentioned by B.Caslow in the checklist to Jongsoo
DID NOT work on ONE router while the other is OK. Unluckily the few
points ISDN cost me about 40 minutes or more.
After BGP, it passed about 5 hours or more. I did not get all
scores of BGP since the BGP table and connectivity is ok.
TIA
dillon
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:12:03 GMT-3