01-03-2013 05:39 AM - edited 03-04-2019 06:33 PM
Dear Fellows,
I believe that I should have started with this issue because I cannot run tclsh on a multilayer switch.
When I try to execute "tclsh" command I receive this message:
SWITCH#tclsh
Translating "tclsh"...domain server (X.X.X.X)
% Unknown command or computer name, or unable to find computer address
The equipment is a MLS C3550 - Version 12.2(35)SE3
Is there any wrong with the IOS version?
Thanks in advanced!
Solved! Go to Solution.
01-03-2013 06:03 AM
Hi,
It appears that Tcl is not supported on C3550/60 platforms:-
TCL scripting:
3550:
sw3#sh ver | i IOS
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE2,
RELEASE SOFTWARE (fc1)
sw3#t?
telnet terminal test traceroute tunnel <-no tcl
3560:
sw1#sh ver | i IOS
Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version 12.2(25)SEE2,
RELEASE SOFTWARE (fc1)
sw1#t?
telnet terminal test traceroute tunnel <-no tcl
It is possible to set up an automated ping test similar to a TCL script on these device we can use a macro to get the same functionality as a simple TCL ping script:
3550:
sw3(config-if)#do sh ip int br | e ass
Interface IP-Address OK? Method Status Protocol
Loopback0 100.0.0.100 YES manual up up
Loopback1 100.0.1.100 YES manual up up
Loopback2 100.0.2.100 YES manual up up
sw3(config-if)#macro name PING
Enter macro commands one per line. End with the character ‘@’.
do ping 100.0.0.100
do ping 100.0.1.100
do ping 100.0.2.100
@
sw3(config)#macro global apply PINGType escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.0.0.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.0.1.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.0.2.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms3560:
sw1(config-if)#do sh ip int br | e ass
Interface IP-Address OK? Method Status Protocol
Loopback0 10.0.0.100 YES manual up up
Loopback1 10.0.1.100 YES manual up up
Loopback2 10.0.2.100 YES manual up up
sw1(config-if)#macro name PING
Enter macro commands one per line. End with the character ‘@’.
do ping 10.0.0.100
do ping 10.0.1.100
do ping 10.0.2.100
@
sw1(config)#macro global apply PINGType escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.1.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.2.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
Please note this is copied and pasted from my study notes all credit goes to the auther cciepursuit
http://cciepursuit.wordpress.com/2007/08/27/
HTH
Kind Regards,
Liam
01-03-2013 06:09 AM
Hello Olivier and Liam,
The TCL seems to be supported on the 3560 after all:
SW-Dist1#sh ver | i IOS
Cisco IOS Software, C3560 Software (C3560-IPBASEK9-M), Version 12.2(52)SE, RELEASE SOFTWARE (fc3)
SW-Dist1#tcl?
tclquit tclsh
SW-Dist1#tcl
However, this is a 12.2(52)SE IPBASE. I am trying to find out what is the first IOS version for 3560 Catalyst switches that included the TCL interpreter.
Best regards,
Peter
01-03-2013 06:18 AM
Hello Olivier and Liam,
It seems that the first TCL support appeared in 12.2(46)SE as the Software Configuration Guide for this IOS version is the first one that mentions the Embedded Event Manager in combination with TCL applets.
The Cisco Feature Navigator was not helpful here, sadly - it thinks the 3560 series does not support the TCL at all.
Best regards,
Peter
01-03-2013 06:21 AM
I think its time my lab got an IOS update . I did double check the feature navigator before I posted. Weird that it is not listed on there.
Thanks for the update.
Kind Regards,
Liam
01-03-2013 06:30 AM
Hello Liam,
You are welcome. Yeah, the Feature Navigator has had some incomplete information for quite a time. It's been made significantly faster but it seems not to be as precise/up-to-date as before.
Best regards,
Peter
01-03-2013 06:42 AM
Hello Olivier,
the TCL is supported since IOS Version 12.3(2)T and 12.2(25), that is why I beleive my IOS (Version 12.2(35)SE3) could support this command.
Sadly, it is not that easy. This information is related to IOS versions for routers. However, the IOS versioning for switches was independent. The IOS version 12.2(25) for routers is not generally related to IOS version 12.2(25) for switches. This is probably a historical thing - Cisco first produced routers, and only started manufacturing switches later. The IOS for switches was obviously branched off the IOS for routers but was then developed, at least to a certain extent, independently. In fact, there are many commands for switches that are not described in IOS documentation, only in the documentation for a particular switch platform. There is no precise documentation about this - it's just years of experience I am now commenting upon.
Cisco has since aligned the IOS versioning with the transition to the version 15.x and beyond. Hopefully, things will get more simple.
Best regards,
Peter
01-03-2013 06:03 AM
Hi,
It appears that Tcl is not supported on C3550/60 platforms:-
TCL scripting:
3550:
sw3#sh ver | i IOS
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(25)SEE2,
RELEASE SOFTWARE (fc1)
sw3#t?
telnet terminal test traceroute tunnel <-no tcl
3560:
sw1#sh ver | i IOS
Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version 12.2(25)SEE2,
RELEASE SOFTWARE (fc1)
sw1#t?
telnet terminal test traceroute tunnel <-no tcl
It is possible to set up an automated ping test similar to a TCL script on these device we can use a macro to get the same functionality as a simple TCL ping script:
3550:
sw3(config-if)#do sh ip int br | e ass
Interface IP-Address OK? Method Status Protocol
Loopback0 100.0.0.100 YES manual up up
Loopback1 100.0.1.100 YES manual up up
Loopback2 100.0.2.100 YES manual up up
sw3(config-if)#macro name PING
Enter macro commands one per line. End with the character ‘@’.
do ping 100.0.0.100
do ping 100.0.1.100
do ping 100.0.2.100
@
sw3(config)#macro global apply PINGType escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.0.0.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.0.1.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.0.2.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms3560:
sw1(config-if)#do sh ip int br | e ass
Interface IP-Address OK? Method Status Protocol
Loopback0 10.0.0.100 YES manual up up
Loopback1 10.0.1.100 YES manual up up
Loopback2 10.0.2.100 YES manual up up
sw1(config-if)#macro name PING
Enter macro commands one per line. End with the character ‘@’.
do ping 10.0.0.100
do ping 10.0.1.100
do ping 10.0.2.100
@
sw1(config)#macro global apply PINGType escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.1.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.2.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
Please note this is copied and pasted from my study notes all credit goes to the auther cciepursuit
http://cciepursuit.wordpress.com/2007/08/27/
HTH
Kind Regards,
Liam
01-03-2013 06:09 AM
Hello Olivier and Liam,
The TCL seems to be supported on the 3560 after all:
SW-Dist1#sh ver | i IOS
Cisco IOS Software, C3560 Software (C3560-IPBASEK9-M), Version 12.2(52)SE, RELEASE SOFTWARE (fc3)
SW-Dist1#tcl?
tclquit tclsh
SW-Dist1#tcl
However, this is a 12.2(52)SE IPBASE. I am trying to find out what is the first IOS version for 3560 Catalyst switches that included the TCL interpreter.
Best regards,
Peter
01-03-2013 06:18 AM
Hello Olivier and Liam,
It seems that the first TCL support appeared in 12.2(46)SE as the Software Configuration Guide for this IOS version is the first one that mentions the Embedded Event Manager in combination with TCL applets.
The Cisco Feature Navigator was not helpful here, sadly - it thinks the 3560 series does not support the TCL at all.
Best regards,
Peter
01-03-2013 06:21 AM
I think its time my lab got an IOS update . I did double check the feature navigator before I posted. Weird that it is not listed on there.
Thanks for the update.
Kind Regards,
Liam
01-03-2013 06:30 AM
Hello Liam,
You are welcome. Yeah, the Feature Navigator has had some incomplete information for quite a time. It's been made significantly faster but it seems not to be as precise/up-to-date as before.
Best regards,
Peter
01-03-2013 06:28 AM
Dear Fellows,
Thank you very much for your help.
According to Cisco (http://www.cisco.com/web/about/security/intelligence/securetcl.html) the TCL is supported since IOS Version 12.3(2)T and 12.2(25), that is why I beleive my IOS (Version 12.2(35)SE3) could support this command.
Am I right?
Thanks again for your help!
01-03-2013 06:42 AM
Hello Olivier,
the TCL is supported since IOS Version 12.3(2)T and 12.2(25), that is why I beleive my IOS (Version 12.2(35)SE3) could support this command.
Sadly, it is not that easy. This information is related to IOS versions for routers. However, the IOS versioning for switches was independent. The IOS version 12.2(25) for routers is not generally related to IOS version 12.2(25) for switches. This is probably a historical thing - Cisco first produced routers, and only started manufacturing switches later. The IOS for switches was obviously branched off the IOS for routers but was then developed, at least to a certain extent, independently. In fact, there are many commands for switches that are not described in IOS documentation, only in the documentation for a particular switch platform. There is no precise documentation about this - it's just years of experience I am now commenting upon.
Cisco has since aligned the IOS versioning with the transition to the version 15.x and beyond. Hopefully, things will get more simple.
Best regards,
Peter
01-03-2013 07:55 AM
Dear Fellows,
Finally I solved my issue with the kron scheduler.
I do not need TCLSH command at this moment.
Thanks very much for your help!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide