Sponsored Content
Top Forums Shell Programming and Scripting EXPECT script for Telnet automation. Need your support. Post 302543251 by starchen on Saturday 30th of July 2011 10:59:28 AM
Old 07-30-2011
Bug EXPECT script for Telnet automation. Need your support.

Dear experts, please help me .

I've found simple EXPECT scripts and all works fine. But I need more automation in error handling and sending list of commands/output logging from multiple remote hosts.

I have 10 hosts, for example:
host1 192.168.1.1 LOGIN1 PASSWORD1
...... ................ ........ ................
host10 192.168.5.16 LOGIN10 PASSWORD10


For me better to put these addresses and credentials to special "my_hosts" file in ~/scripts/teln/config/ directory.

Also I have a few files () with only sets of commands for remote hosts, for example:

enable
sh runn
con ter
br
en

I need expect script with 2 parameters: "Hosts list" file name and "Commands list for remote hosts" file name which can run this list of commands in all hosts (sequent, host by host) and put only telnet log to separate log files - one per host and/or one per command type.

Also I need every command from "Commands list for remote hosts" to be executed in cycle - to evaluate/expect for error printout and finish/halt script with line number of wrong command in
"Commands list for remote hosts".

If "Stop on error", "Delay between commands" options will be available as CL parameters and in some .config file - it will be great.

I understand that this script is not possible with my dummy level but hope to get some useful information, support from you.

Thanks you in advance!

BR,
Alexander




---------- Post updated at 05:59 PM ---------- Previous update was at 03:17 PM ----------

Dear experts,

solution is found.

Please search: Automated_Remote_VTY_Command_Script
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Automation of telnet and ftp

I have a basic query. I use telnet and ftp very frequently. I want to do it without spending time in typing username and password everytime. I know that if I have .netrc file which contains server address, username, pasword, then just typing ftp will conect to that server with that username and... (10 Replies)
Discussion started by: asutoshch
10 Replies

2. Shell Programming and Scripting

Run expect script in systems that don't support it out of box

Noob question .. My Java based application needs to change some user passwords based on some user actions. Since this application can run on Redhat AS2.1 / AS4.0 / Solaris 9 etc, the most safe and portable solution that I could think of was: Use expect. Now, expect is not available on all... (1 Reply)
Discussion started by: namityadav
1 Replies

3. Shell Programming and Scripting

Webpage to Telnet via Perl and Expect: Telnet problem?

Somewhat long story: I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage. This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies

4. AIX

Automation from Windows to Linux - Telnet and su using perl

Here is my requirement to automate the deployment procedure for my project. Telnet to AIX box (say SERVER1) from windows machine (with USER1) Select the server to login say "SERVER2" su as different user say "USER2"(Owner of the deployed files) Execute the script (Script has so many... (1 Reply)
Discussion started by: nurainos
1 Replies

5. Shell Programming and Scripting

Telnet Expect script question

Hi all, I have written a small expect script which should spawn a telnet session login and execute some commands. #!/usr/bin/expect -f spawn telnet $env(IP) match_max 100000 expect "login:" send -- "******\n" expect -exact "Password:" send -- "****\n" expect "%" Now I have got... (2 Replies)
Discussion started by: stinkefisch
2 Replies

6. Shell Programming and Scripting

Expect script to automate telnet session

Hi all, I am currently running a daemon which creates a virtual terminal for testing purposes. Essentially, if I were to interact with it manually, this is what I get. john@test1:~$telnet localhost 7777 Trying ::1... Connected to localhost. Escape character is '^]' mip6d> pl eth2... (6 Replies)
Discussion started by: abxccd
6 Replies

7. Shell Programming and Scripting

Calling Expect Script - Telnet

Hi All, I have an Expect script which logs into Cisco switch, performs a show interface command. I want to read a file of ip addresses which will be passed to the expect script. The script to read the file works, the expect script works on it's own but when i call the 'expect' script from the... (12 Replies)
Discussion started by: trinak96
12 Replies

8. Shell Programming and Scripting

Expect While Loops - Partial Automation?

I've been reading the O'Reilley expect book and I'm trying to create partial automation for common questions asked on screen in a telnet session and return to interact so the user can resume control. For example while {1} { expect { -re "What color is the sky?" {send... (0 Replies)
Discussion started by: mlarivie
0 Replies

9. Shell Programming and Scripting

expect telnet script execute by cronjob

hi, please help, keep getting this bolded error and look it up and people say its your environment variable though i tried to set it manually in expect..it run fine if i run it manually but once i run it by cronjob it error below..i tried to comment out ip/login info with *.. logfile:: START... (0 Replies)
Discussion started by: cssanangeles
0 Replies
rlogin(1)						      General Commands Manual							 rlogin(1)

NAME
rlogin - Connects the local host with a remote host SYNOPSIS
rlogin [-8L] [-e character] [-l user] remote_host The remote login command (rlogin) logs into remote_host and connects your local terminal to the remote host. OPTIONS
Allows an 8-bit data path at all times. Otherwise, unless the Stop and Continue key sequences on the remote host are not standard, rlogin uses a 7-bit data path and the eighth (high) bit of each byte is stripped. Changes the Escape character. Substitute the character you choose for character. Changes the remote username to the one you specify. Otherwise, your local username is used at the remote host. Allows the rlogin session to be run in litout mode. In this mode, the escape sequence ~. (where ~ is the escape character) disconnects you from the remote host and the escape sequence ~^Z (where ^Z, or Ctrl-Z, is the suspend character) suspends the rlogin session if you are using csh. DESCRIPTION
The remote terminal type is the same as that given in the local TERM environment variable. The terminal or window size is also the same, if the remote host supports them, and any changes in size are transferred. All echoing takes place at the remote host, so except for delays, the terminal connection is transparent. Pressing the Stop and Continue key sequences stops and starts the flow of information, and the input and output buffers are flushed on Interrupts. The rlogin command can only be used to connect to systems that are running the rlogind daemon. On systems that do not support rlogin, you can use telnet (if supported) as an alternative. If you do not specify the -l option, the local username is used at the remote host. If -l user is specified, the username entered is used at the remote host. In either case, the remote host allows access only if one or both of the following conditions is satisfied: The local host is included in the remote host's /etc/hosts.equiv file, the local user is not the superuser, and the -l user option is not specified. The local host is included in a $HOME/.rhosts file in the home directory of the remote user account. If -l user is specified, the local username must also be included in the file. If neither of these conditions is met and a password is defined for the remote user account, the remote host prompts for a password. The remote password file is checked to verify the password entered, and the login prompt is displayed if the password is not correct. Pressing the End-of-File key sequence at the login prompt ends the remote login attempt. For security reasons, any $HOME/.rhosts file must be owned by either the remote user or the root user and should have permissions set to 600 (read and write by owner only). In addition to the preceding conditions, rlogin also allows access to the remote host if the remote user account does not have a password defined. However, for security reasons, use of a password on all user accounts is recommended. Unless otherwise modified by the -e option, the standard Escape character for disconnecting from the remote host is a ~ (tilde). The Escape character is only recognized by the remote host if it occurs at the beginning of a line. Otherwise, the Escape character is sent to the remote host as a normal character. To send the Escape character to the remote host as a normal character at the beginning of a line, press the Escape character twice. Pressing the Escape character and a (dot) (for example, ~.) immediately disconnects the local terminal from the remote host. EXAMPLES
In the following examples, the local host is listed in the /etc/hosts.equiv file at the remote host: To log in to a remote host with your local username, enter: $ rlogin host2 Password: <Enter password> To log off the remote host and close the connection, enter the End-of-File key sequence. To log in to a remote host with a differ- ent username, enter: $ rlogin host2 -l dale You are prompted to enter your password and then are logged in to the remote host host2 with the username dale. To log in to host2 with the your local username and change the Escape character to (backslash), enter: $ rlogin host2 -e\ FILES
Specifies remote hosts from which users can execute commands on the local host (provided these users have an account on the local host). Specifies remote users who can use a local user account. SEE ALSO
Commands: rcp(1), rsh(1), rlogind(8), telnet(1) Files: rhosts(4) rlogin(1)
All times are GMT -4. The time now is 08:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy