How Event Triggers Work

VCS determines if the event is enabled and invokes hatrigger, a high-level Perl script located at $VCS_HOME/bin/hatrigger.

VCS also passes the name of the event trigger and the parameters specific to the event. For example, when a service group becomes online on a system, VCS invokes hatrigger -postonline system service_group. Note that VCS does not wait for hatrigger or the event trigger to complete execution. After calling the triggers, VCS continues normal operations.

Event triggers are invoked by event names, for example violation denotes a concurrency violation.

Event triggers are invoked on the system where the event occurred, with the following exceptions:

• The sysoffline and nofailover event triggers are invoked from the lowest-numbered system in RUNNING state.
• The violation event trigger is invoked from all systems on which the service group was brought partially or fully online.