Need help with Expect script for Cisco IPS Sensors, Expect sleep and quoting
This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are some problems I haven't been able to solve.
Delays in prompts, Sleep timers:
1. Sometimes the script appears to send the next command before the next prompt appears in which case the correct command is skipped and the one afterwards sent and accepted. The commands usually need to be entered in order so this usually produces an error. For example Expect sends "service signature-definition sig0" and the sensor receives it but the sensor takes 5-10 seconds to provide the next prompt. The possibility of this long delay which will cause an error has forced me to insert a sleep timer after each command is sent in my loop. One problem with that is if the delay is even longer than my sleep timer I still get an error. Another problem is the script takes forever because there's a 10 second pause after every command. Is using a sleep timer the only or best solution to this problem?
Quoting, Escaping \. in Regex
2. From what I can tell in Expect if I don't quote the command "configure terminal" it's received at the IPS sensor as 2 separate commands so I have to quote it. I don't know if this is causing this problem but for some reason when I use this script the regex string 10\.1\.1\.100 ends up being sent to the IPS sensor without the backslashes 10.1.1.100 but I don't want the regular expression dot . evaluated I just want an IP address with periods i.e. with the periods escaped with the backslash. Something about my Expect script is causing this problem because when I log into an IPS sensor using ssh and copy and paste the commands into the IPS sensors manually the regex string is saved with the backslashes. I've tried removing the quotes and I've also tried double quoting and neither work. Does anyone know what I'm doing wrong here or what I could try to use Expect to send a regex string with backslashes intact?
Hello to all...this is my first post (so please go easy). :)
I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
I wrote some expect script to telnet to some device to execute some commands.Firstly,I can't get full result some time,then I try to add some "sleep" command in it.Fortunately it works.
My idea about it is that it uses sleep command to wait the result to be displayed.Am I right or correct the... (4 Replies)
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)
Fairly new to the System Admin world, and this is my first post here, hoping to get some clarification.
I am using a BASH script to automate some Logfile Archiving (into .tars). The actual logfiles are accessed through an SSH, so I have used the following EXPECT sub-script within my main BASH... (8 Replies)
Hi all,
I use a bash script which use expect to connect throught ssh and run command on a cisco router. The ssh connection with expect work fine, but the first command on the cisco router failed,
I try to run the command in error by hand and it work fine... :(
the first part of the script... (2 Replies)
Hi,
Am very new to expect scripting..
Can You please suggest me how to call an expect script inside another expect script..
I tried with
spawn /usr/bin/ksh
send "expect main.exp\r"
expect $root_prompt
and
spawn /usr/bin/ksh
send "main.exp\r"
expect $root_prompt
Both... (1 Reply)
I know there are better ways to do this.
I prefer snmp. I do not have the proper perl modules loaded on the platorm. Snmp isnt loaded on the platform. Telnet is not an option. I need to write an expect script to pull cisco equipment configs.
The following code is executed once I gain... (0 Replies)
I have an expect script called remote that I want to call from inside my expect script called sudoers.push, here is the code that is causing me issues:
set REMOTE "/root/scripts/remote"
...
log_user 1
send_user "Executing remote script as $user...\n"
send_user "Command to execute is: $REMOTE... (1 Reply)
I'm fairly new to scripting so this might not be possible.
I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version:
#show version
... (0 Replies)
HI all
i need to connect to about 900 cisco routers and switch to do some configs changes. the issue i am having is that half the devices have one set of username and password and the other half have another username and password. From expect or bash script i can ssh into a device and make... (0 Replies)
Discussion started by: quintin
0 Replies
LEARN ABOUT DEBIAN
sensors-detect
SENSORS-DETECT(8) System Manager's Manual SENSORS-DETECT(8)NAME
sensors-detect - detect hardware monitoring chips
SYNOPSIS
sensors-detect
DESCRIPTION
sensors-detect is an interactive program that will walk you through the process of scanning your system for various hardware monitoring
chips, or sensors, supported by libsensors(3), or more generally by the lm_sensors tool suite.
sensors-detect will look for the following devices, in order:
o Sensors embedded in CPUs, south bridges and memory controllers.
o Sensors embedded in Super I/O chips.
o Hardware monitoring chips accessed through ISA I/O ports.
o Hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system.
As the last two detection steps can cause trouble on some systems, they are normally not attempted if the second detection step led to the
discovery of a Super I/O chip with complete hardware monitoring features. However, the user is always free to ask for all detection steps
if so is his/her wish. This can be useful if a given system has more than one hardware monitoring chip. Some vendors are known to do this,
most notably Asus and Tyan.
WARNING
sensors-detect needs to access the hardware for most of the chip detections. By definition, it doesn't know which chips are there before
it manages to identify them. This means that it can access chips in a way these chips do not like, causing problems ranging from SMBus
lockup to permanent hardware damage (a rare case, thankfully.)
The authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is
impossible to guarantee that sensors-detect will not lock or kill a specific system. So, as a rule of thumb, you should not run sensors-
detect on production servers, and you should not run sensors-detect if can't afford replacing a random part of your system. Also, it is
recommended to not force a detection step which would have been skipped by default, unless you know what you are doing.
SEE ALSO sensors(1), libsensors(3)AUTHOR
Frodo Looijaard and Jean Delvare
lm-sensors 3 December 2008 SENSORS-DETECT(8)