HP StorageWorks Fabric Manager 5.x Administrator Guide (AA-RUQSF-TE, September 2005)

Fabric Manager 5.x administrator guide 121
Using the Call Home external executable
The Fabric Manager Call Home feature can accept an external executable that runs when a Call Home
event occurs. If you configure an external executable, Fabric Manager passes an XML file to the executable
whenever a Call Home event occurs. The external executable runs as a background process, and the task
manager monitors the process. All other functionality is at your discretion.
CAUTION: Large executables can impair the performance of your server.
The external executable must have the following characteristics:
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 or Solaris).
It must be able to receive a command-line argument from Fabric Manager. The argument is the name of
an XML file that Call Home generates when an event occurs.
For example: If you enter the executable C:\executable.exe in the External Executable on Server field
in your Call Home window, Call Home launches C:\executable.exe filename.xml, where
filename is the name of the file that is passed as an argument to the executable, when a Call Home
event is triggered.
NOTE: There might be additional executable requirements, depending on your needs.
Sample XML data
Call Home provides an XML file to an external executable whenever a Call Home triggering event occurs.
This section describes the following events:
Switch status change, next
Switch rebooted, page 123
Switch unreachable, page 124
Server Up message, page 125
Switch status change
This section lists the XML and DTD definition for a switch status change.
XML for a switch status change
<?xml version="1.0" encoding="UTF-8"?>
<CallHomeAlert type="statusUnhealthy" serverName="EC4BCADE126037"
serverIP="10.114.62.152" time="Feb 9, 2005 7:44:38 PM IST" epochTime="1107958478860"
>
<Briefing>Call home is triggered on switch E12K_142116 (wwn=10:00:00:60:69:e0:01:68
ip=10.32.142.116 fcIp=0.0.0.0) of group sdfsadfas because switch status turns to
Marginal</Briefing>
<TriggerEvent>
<StatusEvent status="Marginal"> <Reason> Switch Status is MARGINAL. Contributors:
* Switch Offline (MARGINAL).</Reason>
</StatusEvent>
</TriggerEvent>
<Source>
<Switch name="E12K_142116" wwn="10:00:00:60:69:e0:01:68" ethernetIP="10.32.142.116"
ethernetIPMask="255.255.240.0" fcIP="0.0.0.0" fcIPMask="0.0.0.0"
firmware="v5.0.0_main_bld19" switchType="10" domainID="116"
factorySerialNumber="KQ00XE00168" supplierSerialNumber="none"/>
</Source>
<Detail>
<SwitchStatus status="Marginal">
<Reason>Switch Status is MARGINAL. Contributors: