Filter
Top Products
omconfig: Managing Components Using the Instrumentation Service 91
Example Set Alert Action Commands
The examples below are valid example commands. For each successful command issued, the following
message appears:
Alert action(s) configured successfully.
Example Current Probe Actions
To disable system console alert if a current probe detects a warning event, type:
omconfig system alertaction event=currentwarn alert=false
To enable broadcast messages if a current probe detects a failure event, type:
omconfig system alertaction event=currentfail broadcast=true
Example Fan Probe Actions
To generate alerts when a fan probe detects a failure value, type:
omconfig system alertaction event=fanfail alert=true
Example Chassis Intrusion Actions
To clear all alert actions for chassis intrusion, type:
omconfig system alertaction event=intrusion clearall=true
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.
event=tempwarn Sets actions when a temperature probe detects a warning value.
event=tempfail Sets actions when a temperature probe detects a failure value.
event=voltwarn Sets actions when a voltage probe detects a warning value.
event=voltfail Sets actions when a voltage probe detects a failure value.
event=watchdogasr Sets actions that Server Administrator performs on the next system startup
after a watchdog Automatic System Recovery (ASR) is performed for a hung
operating system.
Table 4-21. Events for Which You Can Set Alert Actions (continued)
Event Name Description