Viewing Software Version Numbers; Troubleshooting Specific Issues; Software Services; Failover - HP IBRIX X9720 System Administrator Manual

3. While the controller is still disengaged, ensure that the SAS cables are fully inserted.
4. Push the controller fully into the chassis so it engages.
The seven-segment display shows different codes as the controller boots. After a few minutes, the
seven-segment display should show a constant value (if you had previously run a firmware flash
utility, this can take up to 25 minutes). If the value is "on," the controller is operating normally.
Otherwise, see

Viewing software version numbers

To view version information for a list of hosts, use the following command:
ibrix_version -l [-h HOSTLIST]
For each host, the output includes:
Version number of the installed file system
Version numbers of the IAD and File System module
Operating system type and OS kernel version
Processor architecture
The -S option shows this information for all file serving nodes. The -C option shows the information
for all X9000 clients.
The file system and IAD/FS output fields should show matching version numbers unless you have
installed special releases or patches. If the output fields show mismatched version numbers and
you do not know of any reason for the mismatch, contact HP Support. A mismatch might affect the
operation of your cluster.

Troubleshooting specific issues

Software services

Cannot start services on a file serving node, or Linux X9000 client
SELinux might be enabled. To determine the current state of SELinux, use the getenforce
command. If it returns enforcing, disable SELinux using either of these commands:
setenforce Permissive
setenforce 0
To permanently disable SELinux, edit its configuration file (/etc/selinux/config) and set
SELINUX=parameter to either permissive or disabled. SELinux will be stopped at the next
boot.
For X9000 clients, the client might not be registered with the Fusion Manager. For information on
registering clients, see the HP IBRIX X9000 Network Storage System Installation Guide.

Failover

Cannot fail back from failover caused by storage subsystem failure
When a storage subsystem fails and automated failover is turned on, the Fusion Manager will
initiate its failover protocol. It updates the configuration database to record that segment ownership
has transferred from primary servers to their standbys and then attempts to migrate the segments
to the standbys. However, segments cannot migrate because neither the primary servers nor the
standbys can access the storage subsystem and the failover is stopped.
Perform the following manual recovery procedure:
1. Restore the failed storage subsystem (for example, replace failed Fibre Channel switches or
replace a LUN that was removed from the storage array).
2. Reboot the standby servers, which will allow the failover to complete.
"Identifying the failed component" (page 147) for more information.
Viewing software version numbers 151