5.5 HP StorageWorks X9720 Network Storage System Administrator Guide (AW549-96026, March 2011)

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 that are mostly related to the failover status of the node. The
following table describes the states.
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 management console GUI, and an email notification may be sent.
Up-InFailover: Server is powered on and visible to the management console, and the management
console is failing over the server’s segments to a standby server.
Up-FailedOver: Server is powered on and visible to the management console, and failover is
complete.
Alert
Down-InFailover: Server is powered down or inaccessible to the management console, and the
management console is failing over the server's segments to a standby server.
Down-FailedOver: Server is powered down or inaccessible to the management console, and
failover is complete.
Down: Server is powered down or inaccessible to the management console, and no standby
server is providing access to the server’s segments.
Error
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 will be reported as HBAsDown or NicsDown.
Monitoring cluster events
X9000 Software events are assigned to one of the following categories, based on the level of severity:
• 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 59 for more information.
You can set up event notifications through email (see “Setting up email notification of cluster
events” on page 43) or SNMP traps (see “Setting up SNMP notifications” on page 44).
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:
Monitoring cluster operations58