Triggers let you invoke user-defined scripts for specified events in a cluster.
VCS determines if the event is enabled and invokes the hatrigger script. The script is located at:
VCS also passes the name of the event trigger and associated parameters. For example, when a service group comes online on a system, VCS invokes the following command:
hatrigger -postonline system service_group
VCS does not wait for the trigger to complete execution. VCS calls the trigger and continues normal operation.
VCS invokes event triggers on the system where the event occurred, with the following exceptions:
VCS invokes the sysoffline and nofailover event triggers on the lowest-numbered system in the RUNNING state.
VCS invokes the violation event trigger on all systems on which the service group was brought partially or fully online.
By default, the hatrigger script invokes the trigger script(s) from the default path
$VCS_HOME/bin/triggers. You can customize the trigger path by using the TriggerPath attribute.
See Resource attributes.
The same path is used on all nodes in the cluster. The trigger path must exist on all the cluster nodes. On each cluster node, the trigger scripts must be installed in the trigger path.