Monitoring cluster events
StoreAll software events are assigned to one of the following categories, based on the level of
severity:
•
Alerts.
A disruptive event that can result in loss of access to file system data. For example, a
segment is unavailable or a server is unreachable.
•
Warnings.
A potentially disruptive condition where file system access is not lost, but if the
situation is not addressed, it can escalate to an alert condition. Some examples are reaching
a very high server CPU utilization or nearing a quota limit.
•
Information.
An event that changes the cluster (such as creating a segment or mounting a file
system) but occurs under normal or nonthreatening conditions.
Events are written to an events table in the configuration database as they are generated. To
maintain the size of the file, HP recommends that you periodically remove the oldest events. See
“Removing events from the events database table” (page 104)
.
You can set up event notifications through email (see
“Setting up email notification of cluster events”
(page 70)
) or SNMP traps (see
“Setting up SNMP notifications” (page 72)
).
Viewing events
The GUI dashboard specifies the number of events that have occurred in the last 24 hours. Click
Events
in the GUI Navigator to view a report of the events. You can also view events that have
been reported for specific file systems or servers.
On the CLI, use the
ibrix_event
command to view information about cluster events.
To view events by alert type, use the following command:
ibrix_event -q [-e ALERT|WARN|INFO]
The
ibrix_event -l
command displays events in a short format; event descriptions are truncated
to fit on one line. The
-n
option specifies the number of events to display. The default is 100.
$ ibrix_event -l -n 3
EVENT ID TIMESTAMP LEVEL TEXT
-------- --------------- ----- ----
1983 Feb 14 15:08:15 INFO File system ifs1 created
1982 Feb 14 15:08:15 INFO Nic eth0[99.224.24.03] on host ix24-03.ad.hp.com up
1981 Feb 14 15:08:15 INFO Ibrix kernel file system is up on ix24-03.ad.hp.com
The
ibrix_event -i
command displays events in long format, including the complete event
description.
$ ibrix_event -i -n 2
Event:
=======
EVENT ID : 1981
TIMESTAMP : Feb 14 15:08:15
LEVEL : INFO
TEXT : Ibrix kernel file system is up on ix24-03.ad.hp.com
FILESYSTEM :
HOST : ix24-03.ad.hp.com
USER NAME :
OPERATION :
SEGMENT NUMBER :
PV NUMBER :
NIC :
HBA :
RELATED EVENT : 0
Event:
=======
EVENT ID : 1980
TIMESTAMP : Feb 14 15:08:14
LEVEL : ALERT
TEXT : category:CHASSIS, name: 9730_ch1, overallStatus:DEGRADED,
component:OAmodule, uuid:09USE038187WOAModule2, status:MISSING, Message: The Onboard
Administrator module is missing or has failed., Diagnostic message: Reseat the Onboard
Administrator module. If reseating the module does not resolve the issue, replace the Onboard
Monitoring cluster events 103
