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
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
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
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
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
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
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
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
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
ttys(4) Kernel Interfaces Manual ttys(4)
NAME
ttys - terminal control database file for trusted systems
SYNOPSIS
DESCRIPTION
The system supports a single terminal control database containing entries for each local terminal that can log into the system. Authentica-
tion programs use information contained in the terminal control database to determine if login from the terminal is permitted. Additional
fields are maintained for informational purposes.
The format of the terminal control database file is identical to other system authentication database files. For more information on the
file format, see authcap(4). The file consists of keyword field identifiers and values for those fields. The keyword identifiers supported
and their use include:
This field defines the terminal device name for the entry. The terminal device
is expected to be contained in the directory, therefore this prefix should not be specified. If the terminal entry
describes the device, the field should contain
This field records the user id of the last user to successfully login using
the terminal device.
This field records the last successful login time to the terminal device.
This field records the last unsuccessful login time to the terminal device.
This field records the number of consecutive unsuccessful login attempts to
the terminal device.
This field specifies the maximum number of consecutive unsuccessful login
attempts permitted using the terminal before the terminal is locked. Once the terminal is locked, it must be unlocked by
an authorized administrator.
This field specifies the login timeout value (sec).
This field specifies the delay between login tries (sec).
This flag field indicates whether the terminal device has been administratively
locked or not. This field is manipulated by authorized administrators only.
EXAMPLES
The following is an example of a terminal control database entry:
This entry is for the system console device, The most recent successful login session was for the user The entry records the system time
for the current successful login and the time of the most recent unsuccessful login attempt.
WARNINGS
Remote terminals (ptys) should not be added to the or databases. Device name formats treated as ptys by login are:
where x is a letter, and y is a hex number
where x is a letter, and y is a hex number
HP-UX 11i Version 3 is the last release to support
trusted systems functionality.
AUTHOR
was developed by HP.
FILES
Terminal control database file
SEE ALSO
login(1), getprtcent(3), devassign(4), authcap(4), default(4).
TO BE OBSOLETED ttys(4)