User's Manual

132 omconfig: Managing Components Using the Instrumentation Service
Components and Events for Which You Can Set Alert Actions
Table 4-23 lists the components and the events for which you can set alert
actions. Components are listed in alphabetical order, except that warning events
always precede failure events for a component.
Table 4-23. Events for Which You Can Set Alert Actions
Event Name Description
event=batterywarn Sets actions when a battery probe detects a warning value.
event=batteryfail Sets actions when a battery probe detects a failure value.
event=fanwarn Sets actions when a fan probe detects a warning value.
event=fanfail Sets actions when a fan probe detects a failure value.
event=hardwarelogwarn Sets actions when a hardware log detects a warning value.
event=hardwarelogfull Sets actions when a hardware log is full.
event=intrusion Sets actions when a chassis intrusion event is detected.
event=memprefail Sets actions when a memory probe detects a prefailure
value.
event=memfail Sets actions when a memory probe detects a failure value.
event=systempeakpower Sets actions when a power consumption probe detects
peak power value.
event=systempowerwarn Sets actions when a power consumption probe detects a
warning value.
event=systempowerfail Sets actions when a power consumption probe detects a
failure value.
event=powersupply Sets actions when a power supply probe detects a failure
value.
event=powersupplywarn Sets actions when a power supply probe detects a warning
value.
event=processorwarn Sets actions when a processor probe detects a warning
value.
event=processorfail Sets actions when a processor probe detects a failure
value.
event=redundegrad Sets actions when a redundant component becomes
inoperative, resulting in less than full redundancy for that
component.
event=redunlost Sets actions when one or more redundant components
become inoperative, resulting in a lost or a "no redundant
components working" condition for that component.