Table of Contents
Advertisement
button in VBAdmin or (2) you can use an external event trigger (see "Event
Run Script
Triggering" in the VBrick Appliance Getting Started Guide) to run a script. There are four
event trigger scripts, with fixed names, that can be created and stored in flash memory in the
folder. You write your own scripts and associate them with the file names shown
/scripts
below.
Note Do not confuse Event Trigger scripts with User Function scripts. User Function
scripts are associated and run with the (F1–F4) buttons on the appliance front panel.
See Front Panel on page 11 for more about User Function scripts.
The VBrick appliance can be set up to use serial (COM) Pins 7 and 8 as input events to
trigger the appliance to run scripts. The script files execute a subset of the CLI commands
(
and
) in order to activate specific functions on the VBrick appliance. There are a
SVAR
WAIT
total of four possible input events (COM Pin8 Low, COM Pin8 High, COM Pin7 Low, COM
Pin7 High) associated with four different scripts. The script file names cannot be changed.
•
/scripts/com1Pin8LowEventScript.txt
•
/scripts/com1Pin8HighEventScript.txt
•
/scripts/com1Pin7LowEventScript.txt
•
/scripts/com1Pin7HighEventScript.txt
Run Scripts Using VBAdmin
You can run scripts using the
mode and is basically used for test purposes. See Sample Script below. Note that you
Edit
cannot execute a script using an event trigger if VBAdmin is currently running in
If you run a script directly from VBAdmin, it automatically exits
the active editing session.
24
button in VBAdmin. This button is only available in
Run Script
mode.
Edit
mode and terminates
Edit
© 2009 VBrick Systems, Inc.
Advertisement
Table of Contents
