Sponsored Content
Operating Systems OS X (Apple) Terminal scripting to automate login to cisco devices. Help Please ! Post 302277932 by drdread on Sunday 18th of January 2009 10:42:41 PM
Old 01-18-2009
Terminal scripting to automate login to cisco devices. Help Please !

Hello,

I am new to the mac world, and would like to automate my login to cisco devices (routers, switches etc...), i am in a need of writing a script that i may just click on an icon on the desktop and it will open terminal and run a few command.

as follow:

telnet to an ip address
type the username and password
log all screen output to a file.

Currently i am using the expect and send command but cannot get the script to work as one piece.

any help in the matter would be appreciated.


here is what i got:

telnet x.x.x.x.x

expect -re "Username:"
send "Admin\r"
expect -re "ass:"
send "XXX\r"

Thanks,

Rasta.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Connecting to cisco devices via console

I use configure cisco devices daily using hyper terminal in windows via the serial port. Is there an alternative solution in unix that I can connect to a cisco console port via serial port? What application do I need?? (1 Reply)
Discussion started by: dgroove3
1 Replies

2. Shell Programming and Scripting

Need help on ssh login script to cisco ios

I'm trying to write a login script to ssh into a cisco switch that will run some command remotely. Similar to this expect script located here: SSH login expect shell script to supply username and password However, that script does not work with cisco ios. Anyway know what the best way to... (1 Reply)
Discussion started by: streetfighter2
1 Replies

3. Shell Programming and Scripting

Automate CVS login using shell script

Hi, Can anyone pls help me to automate login to cvs. I basically want to login to cvs and update a file. the script always gets to the login and returns the prompt for a password. Is there any way to send the password in the script itself. Here is the script: #!/bin/ksh... (0 Replies)
Discussion started by: raghu_shekar
0 Replies

4. Shell Programming and Scripting

How to automate pbrun login through script?

Hi All, I need information regarding how to automate the pbrun process in script in Linux. Example sample script below, #!bin/sh /usr/xyz/pbrun testusr -password testpwd testusr is username for pbrun and testpwd is password for pbrun. Im not sure if it is correct way to invoke pbrun in... (2 Replies)
Discussion started by: Pravs4info
2 Replies

5. Shell Programming and Scripting

SFTP script to automate login in to remote server

Greetings, guys. I'm not much of a programmer forgive me for being a noob, because of someone leaving, I was put in an IT spot where I have to figure out a few things. Being new to Linux and programming has been a challenge. My boss has asked me to create an automated script to connect to a 3rd... (7 Replies)
Discussion started by: giovannym
7 Replies

6. Linux

Syslog Server for Cisco Devices

Hi, My name is SAMKZ and I'm a dummy with Linux and I'm so sad about that. I need to have a Syslog Server to archive Logs from my Cisco Routers and Switches. I'd like to know to most robust way of doing this. I've installed Centos 5.9 and Trixbox both on VMWares. I've read... (1 Reply)
Discussion started by: SAMKZ
1 Replies

7. Shell Programming and Scripting

Unable to automate telnet login

i have to connect windows server from one of the unix box so i am using telnet and below is my following code #!/bin/sh host=hostname log=loginid port=23 pass=password cmd1=mkdir test1234 ( echo open ${host} ${port} sleep 1 echo ${log} sleep 3 echo "\r\n" sleep 3 echo ${pass}... (11 Replies)
Discussion started by: chandan.p
11 Replies

8. Shell Programming and Scripting

Automate OTPW login to ssh via bash script

Hello everyone. I'm a Linux novice trying out a lot of bash scripting lately, as it is so very addictive. Lately I have been setting up one of my boxes remotely and have been hardening it as much as possible. Please allow me to explain the scenario, as it does tend to become a little... (1 Reply)
Discussion started by: instro
1 Replies
clogin(1)						      General Commands Manual							 clogin(1)

NAME
clogin - Cisco login script SYNOPSIS
clogin [-autoenable] [-noenable] [-dSV] [-c command] [-E var=x] [-e enable-password] [-f cloginrc-file] [-p user-password] [-s script-file] [-t timeout] [-u username] [-v vty-password] [-w enable-username] [-x command-file] [-y ssh_cypher_type] router [router...] DESCRIPTION
clogin is an expect(1) script to automate the process of logging into a Cisco router, catalyst switch, Extreme switch, Juniper ERX/E- series, Procket Networks, or Redback router. There are complementary scripts for Alteon, Avocent (Cyclades), Bay Networks (nortel), ADC- kentrox EZ-T3 mux, Foundry, HP Procurve switches and Cisco AGMs, Hitachi routers, Juniper Networks, MRV optical switch, Mikrotik routers, Netscreen firewalls, Netscaler, Riverstone, Netopia, and Lucent TNT, named alogin, avologin, blogin, elogin, flogin, fnlogin, hlogin, htlogin, jlogin, mrvlogin, mtlogin, nlogin, nslogin, rivlogin, tlogin, and tntlogin, respectively. clogin reads the .cloginrc file for its configuration, then connects and logs into each of the routers specified on the command line in the order listed. Command-line options exist to override some of the directives found in the .cloginrc configuration file. The command-line options are as follows: -S Save the configuration on exit, if the device prompts at logout time. This only has affect when used with -s. -V Prints package name and version strings. -c Command to be run on each router list on the command-line. Multiple commands maybe listed by separating them with semi-colons (;). The argument should be quoted to avoid shell expansion. -d Enable expect debugging. -E Specifies a variable to pass through to scripts (-s). For example, the command-line option -Efoo=bar will produce a global variable by the name Efoo with the initial value "bar". -e Specify a password to be supplied when gaining enable privileges on the router(s). Also see the password directive of the .cloginrc file. -f Specifies an alternate configuration file. The default is $HOME/.cloginrc. -p Specifies a password associated with the user specified by the -u option, user directive of the .cloginrc file, or the Unix username of the user. -s The filename of an expect(1) script which will be sourced after the login is successful and is expected to return control to clogin, with the connection to the router intact, when it is done. Note that clogin disables log_user of expect(1)when -s is used. Example script(s) can be found in share/rancid/*.exp. -t Alters the timeout interval; the period that clogin waits for an individual command to return a prompt or the login process to produce a prompt or failure. The argument is in seconds. -u Specifies the username used when prompted. The command-line option overrides any user directive found in .cloginrc. The default is the current Unix username. -v Specifies a vty password, that which is prompted for upon connection to the router. This overrides the vty password of the .cloginrc file's password directive. -w Specifies the username used if prompted when gaining enable privileges. The command-line option overrides any user or enauser directives found in .cloginrc. The default is the current Unix username. -x Similar to the -c option; -x specifies a file with commands to run on each of the routers. The commands must not expect additional input, such as 'copy rcp startup-config' does. For example: show version show logging -y Specifies the encryption algorithm for use with the ssh(1) -c option. The default encryption type is often not supported. See the ssh(1) man page for details. The default is 3des. RETURNS
If the login script fails for any of the devices on the command-line, the exit value of the script will be non-zero and the value will be the number of failures. ENVIRONMENT
clogin recognizes the following environment variables. CISCO_USER Overrides the user directive found in the .cloginrc file, but may be overridden by the -u option. CLOGIN clogin will not change the banner on your xterm window if this includes the character 'x'. CLOGINRC Specifies an alternative location for the .cloginrc file, like the -f option. HOME Normally set by login(1) to the user's home directory, HOME is used by clogin to locate the .cloginrc configuration file. FILES
$HOME/.cloginrc Configuration file. SEE ALSO
cloginrc(5), expect(1) CAVEATS
clogin expects CatOS devices to have a prompt which includes a '>', such as "router> (enable)". It uses this to determine, for example, whether the command to disable the pager is "set length 0" or "term length 0". The HP Procurve switches that are Foundry OEMs use flogin, not hlogin. The Extreme is supported by clogin, but it has no concept of an "enabled" privilege level. You must set autoenable for these devices in your .cloginrc. The -S option is a recent addition, it may not be supported in all of the login scripts or for every target device. BUGS
Do not use greater than (>) or pound sign (#) in device banners. These are the normal terminating characters of device prompts and the login scripts need to locate the initial prompt. Afterward, the full prompt is collected and makes a more precise match so that the scripts know when the device is ready for the next command. All these login scripts for separate devices should be rolled into one. This goal is exceedingly difficult. The HP Procurve switch, Motorola BSR, and Cisco AGM CLIs rely heavily upon terminal escape codes for cursor/screen manipulation and assumes a vt100 terminal type. They do not provide a way to set a different terminal type or adjust this behavior. The resulting escape codes make automating interaction with these devices very difficult or impossible. Thus bin/hpuifilter, which must be found in the user's PATH, is used by hlogin to filter these escape sequences. While this works for rancid's collection, there are side effects for interactive logins via hlogin; most of which are formatting annoyances that may be remedied by typing CTRL-R to reprint the current line. WARNING: repeated ssh login failures to HP Procurves cause the switch's management interface to lock-up (this includes snmp, ping) and sometimes it will crash. This is with the latest firmware; 5.33 at the time of this writing. 26 April 2011 clogin(1)
All times are GMT -4. The time now is 03:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy