Monitoring Cluster Events; Viewing Events - HP IBRIX X9720 Administrator's Manual

The STATE field also reports the status of:
Monitored NICs and HBAs. If you have multiple HBAs and NICs and some of them are down,
the state is reported as Up, HBAsDown or Up, NicsDown.
Uptime of the node. If the number of consecutive days that the node has been up surpasses
the threshold (set by the serverUptimeEventThreshold parameter of the ibrix_fm_tune
command), the state is reported as Up, UptimeOverThreshold. The default (and recommended)
threshold is 400 days. If you see the state reported as UptimeOverThreshold, reboot the node
as soon as possible to prevent the file systems from eventually becoming unresponsive. To
reboot the node, see
NOTE: You can reboot the node at any time. The purpose of implementing these features is to
ensure the maximum uptime of a node does not exceed 400 days, thereby preventing file system
performance issues.

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
You can set up event notifications through email (see
(page 58)) or SNMP traps (see

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
-------- ---------------
1983 Feb 14 15:08:15
1982 Feb 14 15:08:15
1981 Feb 14 15:08:15
The ibrix_event -i command displays events in long format, including the complete event
description.
$ ibrix_event -i -n 2
Event:
=======
EVENT ID
TIMESTAMP
"Powering nodes on or off" (page
"Using SNMP notifications" (page
LEVEL
-----
INFO
INFO
INFO
: 1981
: Feb 14 15:08:15
102).
94).
"Viewing email notification of cluster events"
TEXT
----
File system ifs1 created
Nic eth0[99.224.24.03] on host ix24-03.ad.hp.com up
Ibrix kernel file system is up on ix24-03.ad.hp.com
59)).
Monitoring cluster events 93