Sponsored Content
Full Discussion: Help
Top Forums UNIX for Advanced & Expert Users Help Post 26471 by bigkevmcd on Monday 19th of August 2002 12:08:10 PM
Old 08-19-2002
I'd guess that "expect" is your friend.

If you can telnet into the Cisco units, then expect can telnet in the boxes and execute your commands for you.

http://www.samag.com/documents/s=118...903c/9903c.htm is a pretty good start for you

Smilie
 
telnetrc(4)						     Kernel Interfaces Manual						       telnetrc(4)

NAME
telnetrc, .telnetrc - Specifies setup commands for a telnet session SYNOPSIS
$HOME/.telnetrc DESCRIPTION
The .telnetrc file contains the setup information for a telnet session. It is a hidden file in your home directory and must be readable by the user logging in. The file can consist of multiple entries for each remote host to which a user can connect. A remote host entry consists of multiple lines. The first line is the name of a remote host. The subsequent lines must begin with blank spaces, and contain telnet subcommands. These sub- commands are processed as though they were typed in manually. Lines beginning with a number sign (#) are comment lines. See telnet(1) for a complete list of telnet subcommands. To specify subcommands that apply to all systems, create an entry, using the word "DEFAULT" as the system name, and specify the telnet sub- commands in the subsequent lines. EXAMPLES
The following shows a sample .telnetrc file: # Beginning of telnetrc file # Default subcommands that apply to all systems DEFAULT environ undefine USER # First system entry system1 set echo toggle crlf # Second system entry system2 set echo mode line toggle crlf FILES
User-customized telnet startup values. RELATED INFORMATION
Commands: telnet(1). delim off telnetrc(4)
All times are GMT -4. The time now is 06:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy