6 Configuring cluster event notification
Cluster events
There are three categories for cluster events:
Alerts.
Disruptive events that can result in loss of access to file system data.
Warnings.
Potentially disruptive conditions where file system access is not lost, but if the situation is not
addressed, it can escalate to an alert condition.
Information.
Normal events that change the cluster.
The following table lists examples of events included in each category.
Name
Trigger Point
Event Type
login.failure
User fails to log into GUI
ALERT
filesystem.unmounted
File system is unmounted
server.status.down
File serving node is down/restarted
server.unreachable
File serving node terminated unexpectedly
segment.migrated
User migrates segment using GUI
WARN
login.success
User successfully logs in to GUI
INFO
filesystem.cmd
File system is created
server.deregistered
File serving node is deleted
nic.added
NIC is added using GUI
nic.removed
NIC is removed using GUI
physicalvolume.added
Physical storage is discovered and added using
management console
physicalvolume.deleted
Physical storage is deleted using management console
You can be notified of cluster events by email or SNMP traps. To view the list of supported events,
use the command
ibrix_event -q
.
Setting up email notification of cluster events
You can set up event notifications by event type or for one or more specific events. To set up
automatic email notification of cluster events, associate the events with email recipients and then
configure email settings to initiate the notification process.
Associating events and email addresses
You can associate any combination of cluster events with email addresses: all Alert, Warning, or
Info events, all events of one type plus a subset of another type, or a subset of all types.
The notification threshold for Alert events is 90% of capacity. Threshold-triggered notifications are
sent when a monitored system resource exceeds the threshold and are reset when the resource
70
Configuring cluster event notification
