Configuring Cluster Event Notification; Cluster Events - HP IBRIX X9720 Administrator's Manual

5 Configuring cluster event notification

Cluster events

There are three types of cluster events:
Table 5 Event types
Icon
The notification threshold for generating 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 utilization dips 10% below the threshold. For example, a notification is sent the first
time usage reaches 90% or more. The next notice is sent only if the usage declines to 80% or less
(event is reset), and subsequently rises again to 90% or above.
Table 6 (page 57)
supported events, use the command ibrix_event -q.
Table 6 Event name examples by event type
Event Type
ALERT
WARN
INFO
TIP: If you are configuring events for snapshots, ensure that you select the events for the type of
snapshot you are creating (native or block). Native snapshot events begin with the word "native";
block snapshot events begin with the word "snapshot". One exception is the
filesystem.snapshot.invalid event, which is for block snapshots.
Type
Alerts
Warnings
Information
lists examples of events included in each category. To view a complete list of
Trigger Point
User fails to log into GUI
File system is unmounted
Node is down/restarted
Node terminated unexpectedly
User migrates segment using GUI
User successfully logs in to GUI
File system is created
Node is deleted
NIC is added using GUI
NIC is removed using GUI
Physical storage is discovered and added using
management console
Physical storage is deleted using management console
Description
Disruptive events that can result in loss of access to file system
data (for example, a segment is unavailable or a server is
unreachable).
Potentially disruptive conditions where file system access is not
lost, but if the situation is not addressed, it can escalate to an
alert condition (for example, reaching very high CPU utilization
or nearing a quota limit).
Normal events that change the cluster (for example, a segment
is created or a file system is mounted).
Name
login.failure
filesystem.unmounted
server.status.down
server.unreachable
segment.migrated
login.success
filesystem.cmd
server.deregistered
nic.added
nic.removed
physicalvolume.added
physicalvolume.deleted
Cluster events 57