10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
2. Shell Programming and Scripting
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
...... ... (2 Replies)
Discussion started by: starchen
2 Replies
3. Shell Programming and Scripting
At times I find the need to test that the tacacs port 49 is open.
The code below works but is painfully slow because I have to wait on the timeouts.
Examples of possible responds
router1#telnet 10.11.20.14 49
Trying 206.112.204.140, 49 ... Open
route1#telnet 10.11.19.14 49
Trying... (1 Reply)
Discussion started by: popeye
1 Replies
4. Shell Programming and Scripting
I've got some expect/tcl scripts.
Now i want to add a function that allows to open a telnet connection and redirect the output to a logfile.
On the shell/terminal i tried something like:
'telnet 192.168.123.123 12121 > /home/user/logging/log-telnet.log'
and the telnet is redirected into the... (2 Replies)
Discussion started by: JaPatton
2 Replies
5. Shell Programming and Scripting
I'm trying to write a script using expect. I'd like the script to execute several commands when the ssh succeeds and i want it to exit if the ssh fails. Does this require to define a time out for the ssh command so that if the prompt is back before this defined time the next commands are executed??... (2 Replies)
Discussion started by: Hossam_Nox
2 Replies
6. Shell Programming and Scripting
Hi All,
I am trying to write a expect script to telnet and run a command on a remote host.The command i want to send contains a text value is contained in file.txt in the linux box from where i am running the expect script.I want to pass the contains of file.txt into a variable and call the... (1 Reply)
Discussion started by: pistachio
1 Replies
7. Shell Programming and Scripting
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
8. Infrastructure Monitoring
I must automatically monitor and manage a large number of boxes on our network.
I have been using perl/Net::Telnet and expect/telnet and also perl/ssh and expect/ssh to reach the command line of the remote boxes. Scripts are working but slow.
(Yes, I do use SNMP also but many boxes do not... (2 Replies)
Discussion started by: kp2a
2 Replies
9. Shell Programming and Scripting
So here is what I am trying to do. I have a large # of switches and routers I am trying to log into. Unfortunately some have ssh only, some have telnet only. and some i have never logged into with ssh. I first want it to SSH, if i have never logged into the box it will ask for adding the ssh key. I... (0 Replies)
Discussion started by: ippy98
0 Replies
10. Shell Programming and Scripting
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
nstrtel(5) File Formats Manual nstrtel(5)
NAME
nstrtel - specifies the number of telnet device files the kernel can support for incoming telnet sessions
VALUES
Failsafe
Default
Allowed values
(Subject to available physical memory.)
It is best to use the default value, and there should not be any need to lower it. However, if the simultaneous telnet connection load is
very high, then the value of could be increased.
Recommended values
(Default value.)
DESCRIPTION
The telnet daemon uses two STREAMS-based pseudo-terminal drivers and The kernel parameter, can be used to tune the number of pseudo-termi-
nals. specifies the number of kernel data structures that are created at system boot time that are required to support the device files
used by incoming telnet sessions on a server. If the command or SAM is used to create more telnet device files, the value of must be
increased accordingly or the device files cannot be used because there are no kernel data structures available for communicating with the
system.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
When Should the Value of This Tunable Be Raised?
When there is an increase in the load of telnet connections and there are no device files available to open telnet connections, then this
kernel parameter should be increased.
When the error is encountered, then the device files have been exhausted and should be raised. Once the value of is raised, should be run
to create new device files. (If SAM is used to raise the value of is run automatically.)
What Are the Side Effects of Raising the Value of This Tunable?
More resources would be consumed. Extra kernel data structures, and extra device files may clog the system.
When Should the Value of This Tunable Be Lowered?
It is not advisable to lower the tunable value from the default value. Consult HP Support before lowering this tunable from the default
value.
What Are the Side Effects of Lowering the Value of This Tunable?
Though not recommended, there would not be any side effects.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
insf(1M), telnetd(1M), telm(7), tels(7).
Tunable Kernel Parameters nstrtel(5)
