Defining The Launch Script Action - Brocade Communications Systems Brocade BladeSystem 4/24 User Manual

Defining the launch script action

NOTE
Launch scripts with a user interface are not supported.
You can define the path to the script that is launched when a policy is triggered. When the script
launches, the Management application does not verify the existence of the script.
The script must have the following characteristics:
•
•
You can only edit actions from the Add Event Policy, Duplicate Event Policy, or Edit Event Policy
dialog boxes.
For step-by-step instructions on adding or editing an event policy, refer to
on page 258,
on page 260, or
For step-by-step instructions on duplicating an event policy, refer to
page 266,
policy"
For step-by-step instructions on editing an event policy, refer to
page 270,
page 272, or
To define the launch script path, complete the following steps.
1. Select Launch Script from the Actions list.
2. Click Configure.
3. Enter the full path (including executable) of the launch script in the File Name field.
4. Select the check box to send event parameters (Level, Source Name, Source Address, Type,
5. Click OK on the Launch Script dialog box.
6. Click OK on the Add, Duplicate, or Edit Event Policy dialog box.
DCFM Enterprise User Manual
53-1001775-01
It must reside on the Management application server.
It must be capable of being executed by the OS where the Management application server is
installed and it must be a valid binary for that OS (Windows, Solaris, or Linux).
"Adding an Port offline policy"
"Adding a security violation policy"
"Duplicating an Port offline policy"
on page 268, or "Duplicating a security violation policy"
"Editing an Port offline policy"
"Editing a security violation policy"
The Launch Script dialog box displays.
NOTE
Launch scripts with a user interface or a Network file launch are not supported.
You must enter a fully qualified path on the Management application Server for Windows (for
example, C:\Program Files\Management_Application_Name 10.X.X\bin\xyz.bat) as well as
Linux and Solaris (for example, /etc/proc/sbin/script.sh).
and Description) as arguments.
NOTE
The Management application does not verify that the file name exists in the specified folder.
Defining the launch script action
on page 259, "Adding a PM threshold crossed policy"
on page 261.
"Duplicating an event policy"
on page 267, "Duplicating a PM threshold crossed
on page 269.
"Editing an event policy"
on page 271, "Editing a PM threshold crossed policy"
on page 273.
10
"Adding an event policy"
on
on
on
263