From: Eric Dobyns (eric_dobyns@yahoo.com)
Date: Thu May 10 2007 - 13:09:45 ART
I had thought about the alias idea, but the problem with the alias command
is that if you're NOT in config mode, the do makes it blow up.
-----Original Message-----
From: Scott Morris [mailto:smorris@ipexpert.com]
Sent: Thursday, May 10, 2007 11:06 AM
To: 'Eric Dobyns'; ccielab@groupstudy.com
Subject: RE: Exec commands: Do what?
You can run a PIX. :)
Otherwise, good luck with that! Cisco won't change it.
On the other hand, you can use the "alias configure" command to help you
out!
R1(config)#alias configure ping do ping
R1(config)#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1(config)#
While it may be a pain to type those in, every little bit helps!
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
IPexpert VP - Curriculum Development
IPexpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Eric
Dobyns
Sent: Thursday, May 10, 2007 11:58 AM
To: ccielab@groupstudy.com
Subject: Exec commands: Do what?
Anyone know of a way to get around having to put "do" in config mode to run
exec commands?
I.e. how to ping without exiting out of config mode or having to type "do
ping 1.1.1.1" etc.
Foundry and a lot of others allow the exec commands to work in config mode,
but Cisco doesn't.
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:20 ART