Grass Valley iControl V.4.43 - Manual (Page 381)

iControl
User Guide
371
Figure 7-31
Some alarm consumer plug-ins are included in every iControl system. Others are available as
options. The table below provides an overview of some common plug-ins.
Global Actions vs. Specific Actions
Alarm consumer actions can be either specific to an individual alarm, or global.
Global actions are associated with, and can be triggered by, every alarm in the system. For
example, the SQL event log plug-in is normally used to create a global action that causes every
alarm event to be logged to a database on the Application Server. When new alarms are
added, any global actions in effect will apply to them as well.
Specific actions can apply to one or several alarms. For example, you can apply a Send e‐mail
action to the Disk used space (%) alarm, so when that alarm is triggered, an e-mail is sent
automatically to a system administrator. The same action could similarly be applied to a range
of health monitoring alarms, with an e-mail being sent if any of them is triggered.
Plug-in Name Type Instance Plug-in Description Availability
Event and
incident log GSM -- Option
GPI VNODE relay GSM -- Option
Scripted action GSM -- Option
Send email GSM -- Enables iControl to send e-mail messages (SMTP) in
response to an alarm Option
SNMP agent GSM Single Enables the GSM to act as an SNMP agent Option
SNMP trap
sender GSM Multiple Enables the GSM to send SNMP traps (based on any GSM
alarm) to a third party manager Option