6.3 HP IBRIX X9720/StoreAll 9730 Storage Administrator Guide (AW549-96073, June 2013)

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.

NameTrigger PointEvent Type

filesystem.unmountedFile system is unmounted

server.status.downFile serving node is down/restarted

server.unreachableFile serving node terminated unexpectedly

segment.migratedUser migrates segment using GUIWARN

filesystem.cmdFile system is created

server.deregisteredFile serving node is deleted

nic.addedNIC is added using GUI

nic.removedNIC is removed using GUI

physicalvolume.addedPhysical storage is discovered and added using

management console

physicalvolume.deletedPhysical 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