Capturing A Core Dump From A Failed Node - HP IBRIX X9720 Administrator's Manual

For example, to view a summary report for file serving nodes xs01.hp.com and xs02.hp.com:
ibrix_haconfig -l -h xs01.hp.com,xs02.hp.com
Host
Nics Monitored
xs01.hp.com
FAILED
xs02.hp.com
FAILED
Viewing a detailed report
Execute the ibrix_haconfig -i command to view the detailed report:
ibrix_haconfig -i [-h HOSTLIST] [-f] [-b] [-s] [-v]
The -h HOSTLIST option lists the nodes to check. To also check standbys, include the -b option.
To view results only for file serving nodes that failed a check, include the -f argument. The -s
option expands the report to include information about the file system and its segments. The -v
option produces detailed information about configuration checks that received a Passed result.
For example, to view a detailed report for file serving node xs01.hp.com:
ibrix_haconfig -i -h xs01.hp.com
--------------- Overall HA Configuration Checker Results ---------------
FAILED
--------------- Overall Host Results ---------------
Host HA Configuration Power Sources Backup Servers Auto Failover Nics Monitored
Standby Nics
xs01.hp.com FAILED
PASSED
--------------- Server xs01.hp.com FAILED Report ---------------
Check Description
================================================ ======
Power source(s) configured
Backup server or backups for segments configured PASSED
Automatic server failover configured
Cluster & User Nics monitored
Cluster nic xs01.hp.com/eth1 monitored
User nics configured with a standby nic
HBA ports monitored
Hba port 21.01.00.e0.8b.2a.0d.6d monitored
Hba port 21.00.00.e0.8b.0a.0d.6d monitored

Capturing a core dump from a failed node

The crash capture feature collects a core dump from a failed node when the Fusion Manager
initiates failover of the node. You can use the core dump to analyze the root cause of the node
failure. When enabled, crash capture is supported for both automated and manual failover. Failback
is not affected by this feature. By default, crash capture is disabled. This section provides the
prerequisites and steps for enabling crash capture.
NOTE: Enabling crash capture adds a delay (up to 240 seconds) to the failover to allow the
crash kernel to load. The failover process ensures that the crash kernel is loaded before continuing.
When crash capture is enabled, the system takes the following actions when a node fails:
1. The Fusion Manager triggers a core dump on the failed node when failover starts, changing
the state of the node to Up, InFailover.
2. The failed node boots into the crash kernel. The state of the node changes to Dumping,
InFailover.
3. The failed node continues with the failover, changing state to Dumping, FailedOver.
54 Configuring failover
HA Configuration Power Sources Backup Servers Auto Failover
Standby Nics HBAs Monitored
FAILED PASSED
PASSED FAILED
FAILED PASSED
WARNED WARNED
HBAs Monitored
PASSED PASSED
FAILED
PASSED
FAILED
PASSED
Result Result Information
==================
PASSED
PASSED
FAILED Not monitored
PASSED
FAILED Not monitored
FAILED Not monitored
PASSED
FAILED
FAILED