5.5 HP StorageWorks X9300 Network Storage Gateway Administrator Guide (AW539-96007, March 2011)

• Alerts. A disruptive evens 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” on page 52 for more information.
You can set up event notifications through email (see “Setting up email notification of cluster
events” on page 37) or SNMP traps (see “Setting up SNMP notifications” on page 38).
Viewing events
The dashboard on the management console GUI 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.
To view events from the CLI, use the following commands:
• View events by type:
<installdirectory>/bin/ibrix_event -q [-e ALERT|WARN|INFO]
• View generated events on a last-in, first-out basis:
<installdirectory>/bin/ibrix_event -l
• View adesignated number of events. The command displays the 100 most recent messages by
default. Use the -n EVENTS_COUNT option to increase or decrease the number of events displayed.
<installdirectory>/bin/ibrix_event -l [-n EVENTS_COUNT]
The following command displays the 25 most recent events:
<installdirectory>/bin/ibrix_event -l -n 25
Removing events from the events database table
The ibrix_event -p command removes events from the events table, starting with the oldest events.
The default is to remove the oldest seven days of events. To change the number of days, include the
-o DAYS_COUNT option.
<installdirectory>/bin/ibrix_event -p [-o DAYS_COUNT]
Monitoring cluster health
To monitor the functional health of file serving nodes and X9000 clients, execute the ibrix_health
command. This command checks host performance in several functional areas and provides either a
summary or a detailed report of the results.
Health checks
The ibrix_health command runs these health checks on file serving nodes:
Monitoring cluster operations52