You could:
make this into a file that accepts the IP as a parameter:
Then write a wrapper for the expect script.
Since it's run in the background the script won't wait for the next router. It does mean that if a router is hung, that individual script will hang.
Well, I am not even sure if its failing, cause at the other end I have a select call and it wakes up and reads the data I sent fine.
Ok here is the issue, I have a UDP socket(non blocking) through which I push some data to another port. At the other end I have select loop, waiting for this data.... (6 Replies)
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'm calling an expect script via a ksh script in cron and it is failing. The script runs fine if i run it manually. Does anyone know if it is an issue with compatibilty and if there is a way around it? (2 Replies)
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... (1 Reply)
Solaris 10 Server refuse to connect :wall:
fork: Resource temporarily unavailable , server unexpectedly unavailable network connection , refuse error, disconnect message, fatal error type2, (protocol error type2)
Issue has been resolved after taken few steps :b:
First of all need to check... (1 Reply)
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 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)
Dear All,
I have a requirement where I have to SFTP or SCP a file in a batch script. Unfortunately, the destination server setup is such that it doesn't allow for shell command line login. So, I am not able to set up SSH keys. My source server is having issues with Expect. So, unable to use... (5 Replies)
Hy guys,
My name is Alex, i am new here and I hope to find some answers. I am trying to run a expect script to telnet to a mikrotik router, run a command (export), and save the output of that commant to a file (outputfile.txt). The problem is that only part of the output is saved to... (2 Replies)
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)
Discussion started by: IBGaryA
0 Replies
LEARN ABOUT DEBIAN
router.db
router.db(5) File Formats Manual router.db(5)NAME
router.db - rancid group configuration file
DESCRIPTION
router.db contains information for devices which are members of a rancid group. control_rancid(1) reads this file to compile a list of
devices which it should collect.
SYNTAX
One device is listed per-line, where the syntax is:
<device_name>:<device_type>:<state>[:comments]
For example:
scooby.shrubbery.net:cisco:up
The fields are as follows:
<device_name>
The name of the device, which must resolve via gethostbyname, used as the argument to telnet(1), rsh(1), or ssh(1), to connect to
the device. Once converted to lower-case, this also becomes the name of the file used to store the configuration under
$BASEDIR/<group>/configs.
Experience has shown that using the device's FQDN (Fully Qualified Domain Name) works best, as in the example above.
<device_type>
The type of device from the set:
agm A Cisco Anomaly Guard Module (aka Riverhead). Suspect that at some point the UI will become more cisco-like and it can be
merged with the IOS rancid module.
alteon An Alteon WebOS switches.
arista An Arista Networks device.
avocent
An Avocent Cyclades console server.
baynet A Bay Networks router.
cat5 A Cisco catalyst series 5000 and 4000 switches (i.e.: running the catalyst OS, not IOS).
cisco A Cisco router, PIX, or switch such as the 3500XL or 6000 running IOS (or IOS-like) OS, but not IOS-XR.
cisco-nx
A Cisco Nexus switch/router.
cisco-xr
A Cisco device running IOS-XR.
css A Cisco content services switch.
enterasys
An enterasys NAS. This is currently an alias for the riverstone device type.
erx A Juniper E-series edge router.
extreme
An Extreme switch.
ezt3 An ADC-Kentrox EZ-T3 mux.
f5 A F5 BigIP switch.
force10
A Force10 router.
fortigate
A Fortinet firewall.
foundry
A Foundry router, switch, or router-switch. This includes HP Procurve switches that are OEMs of Foundry products, such as
the HP9304M.
hitachi
A Hitachi router.
hp A HP Procurve switch such as the 2524 or 4108 procurve switches. Also see the foundry type.
juniper
A Juniper router.
mikrotik
A Mikrotik router.
mrtd A host running the (Merit) MRTd daemon.
netscalar
A Netscalar load balancer.
netscreen
A Netscreen firewall.
procket
A Procket router.
redback
A Redback router, NAS, etc.
riverstone
A Riverstone NAS or Cabletron (starting with version ~9.0.3) router.
smc A SMC switch (some Dell OEMs).
tnt A Lucent TNT.
zebra Zebra routing software.
<state>
The state is either "up", or some other arbitrary value, e.g. "down". If the device is not marked "up" the device's configuration
will not be collected. It is highly recommended that comments are made for any router not listed as up, so as to indicate the
reason a router is not to be polled, e.g.:
dial1.paris:cisco:up:
core1.paris:cisco:down:in testing until 5/5/2001.
core2.paris:cisco:ticketed:Ticket 6054234, 5/3/2001
border1.paris:juniper:up:
The script "downreport" in util/ can be used to produce a report of routers in router.db that are not marked "up".
[comments]
Freeform string to describe the current state of the router.
A ``#'' at the beginning of a line is a comment; the entire line is ignored.
If a device is deleted from the router.db file, then rancid will clean up by removing the device's config file from
$BASEDIR/<group>/configs. The device will be removed from the revision control system. It is possible, in most cases, to resurrect or
check-out copies of deleted device configurations.
FILES
$BASEDIR/<group>/router.db
Configuration file described here, where <group> is a device group name defined in the variable LIST_OF_GROUPS within
$BASEDIR/etc/rancid.conf.
SEE ALSO control_rancid(1), rancid(1), rancid.conf(5)
24 April 2011 router.db(5)