HP StoreAll 8800, Руководство администратора

Страница: 56 / 167

5 Configuring cluster event notification
Cluster events
There are three types of cluster events:
Table 5 Event types
Description Type Icon
Disruptive events that can result in loss of access to file system
data (for example, a segment is unavailable or a server is
unreachable). Alerts
Potentially disruptive conditions where file system access is not
lost, but if the situation is not addressed, it can escalate to an Warnings
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). Information
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 56) lists examples of events included in each category. To view a complete list of
supported events, use the command
ibrix_event -q
.
Table 6 Event name examples by event type
Name Trigger Point Event Type
login.failure
User fails to log into GUI ALERT
filesystem.unmounted
File system is unmounted
server.status.down
Node is down/restarted
server.unreachable
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
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
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.
56 Configuring cluster event notification