Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)

144 Fabric Manager Administrator’s Guide
53-10000610-02
About call home
10
The supportShow and supportSave commands run in the background. When the operation
completes, another e-mail message is sent with the zipped supportShow or supportSave output
and XML file attachments.
When the call home e-mail is configured with supportSave, this is the only e-mail received. For
switches using the IPv6 address format, only supportSave information can be captured.
When the call home e-mail is configured with supportShow, this e-mail has the original call home
e-mail subject line plus “with supportShow” added at the end. The body of this e-mail is the same
as the first e-mail.
Fabric Manager also sends an XML file as an attachment in the call home e-mail message. You can
select the format for the XML file from one of two options. See “Notification parameter
configuration” on page 106 for instructions.
If you want to be notified that the server is still running, you can configure call home to send a
“server is alive” e-mail message periodically. The default (and minimum) value is one-hour
intervals; the maximum value is 32767. The “server is alive” messages include the list of switches
in the configuration and the server name and IP address. These messages serve as a notice that
call home is functioning properly.
Optionally, you can attach an HTML page containing the call home message which has the call
home message in a readable format. If you choose to attach the HTML content while creating the
call home configuration, all call home triggers except the isAlive action will have the HTML form of
the message attached to the mail sent out.
Call home external script
You can configure call home to run an external script whenever a call home event is triggered for an
unhealthy switch. You can configure call home to run this script instead of or in addition to sending
an e-mail message.
If you configure an external script, Fabric Manager passes an XML file to the script whenever a call
home event occurs. This XML file is also sent as an attachment in the call home e-mail message.
The external script runs as a background process, and the task manager monitors the process. All
other functionality is at your discretion. See “Notification parameter configuration” on page 106 for
instructions on selecting the format for the XML file.
ATTENTION
Large scripts can impair the performance of your server.
The external script must have the following characteristics:
• It must reside on the Fabric Manager server.
• It must be capable of being executed by the OS where the Fabric Manager server is installed
and it must be a valid binary for that OS (Windows, Solaris, or Linux).
• It must be able to receive a command-line argument from Fabric Manager. The argument is the
name of the XML file that call home generates when an event occurs.
For example, if you enter the script C:\script.exe in the External executable on Server field when
prompted by the Call Home Configuration wizard, call home launches C:\script.exe filename.xml,
where filename is the name of the file that is passed as an argument to the script when a call
home event is triggered.