6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

Monitoring the status of file serving nodes
The dashboard on the GUI displays information about the operational status of file serving nodes,
including CPU, I/O, and network performance information.
To view this information from the CLI, use the ibrix_server -l command, as shown in the
following sample output:
ibrix_server -l
SERVER_NAME STATE CPU(%) NET_IO(MB/s) DISK_IO(MB/s) BACKUP HA
----------- ------------ ------ ------------ ------------- ------ --
node1 Up, HBAsDown 0 0.00 0.00 off
node2 Up, HBAsDown 0 0.00 0.00 off
File serving nodes can be in one of three operational states: Normal, Alert, or Error. These states
are further broken down into categories describing the failover status of the node and the status
of monitored NICs and HBAs.
DescriptionState
Up: Operational.Normal
Up-Alert: Server has encountered a condition that has been logged. An event will appear in the Status
tab of the GUI, and an email notification may be sent.
Alert
Up-InFailover: Server is powered on and visible to the Fusion Manager, and the Fusion Manager is
failing over the server’s segments to a standby server.
Up-FailedOver: Server is powered on and visible to the Fusion Manager, and failover is complete.
Down-InFailover: Server is powered down or inaccessible to the Fusion Manager, and the Fusion
Manager is failing over the server's segments to a standby server.
Error
Down-FailedOver: Server is powered down or inaccessible to the Fusion Manager, and failover is
complete.
Down: Server is powered down or inaccessible to the Fusion Manager, and no standby server is providing
access to the server’s segments.
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 HBAsDown or NicsDown.
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 94).
You can set up event notifications through email (see “Setting up email notification of cluster events”
(page 69)) or SNMP traps (see “Setting up SNMP notifications” (page 71)).
Monitoring the status of file serving nodes 93