6.2.3 HP StoreAll Storage Release Notes (update)

• When using the ibrix_vs -a command during file system extension, the command fails on a
combined cluster configuration (such as 9730 and 9320) with the following error message:
Lun already set for physical volume dxx can two vendorstorages see the
same luns?
Contact HP Support for assistance.
• You might not be able to mount a file system after an unmount if you:
Stop the metabox.1.
2. Evacuate the segment.
3. Failover of a server (ibrix_server -f -h <server_name>)
4. Unmount the file system.
To resolve the issue, restart the affected server before unmounting the file system.
• If the ibrix_auth command fails after a QR restore of a server in a cluster with a message
similar to:
ibrix_auth -n IBRQA1.HP.COM -A [e-mail] -P password
-h hostnameX
Iad error on host hostnameX failed command (<HIDDEN_COMMAND>) status
(1) output: (Joining to AD Domain:IBRQA1.HP.COM With Computer DNS Name:
hostsnameX.ibrqa1.hp.com )
Verify the contents of the /etc/resolve.conf file is not empty. If it is empty, copy the contents
of the /etc/resolve.conf file on another server to the empty resove.conf file.
• When configuring automated failover with the HA wizard for the X9720, you must create the
ibrixpwr iLO user on each node before the cluster HA can be fully functional. Enter the
following command on each cluster node to create an iLO user with the user name ibrixpwr
and the password hpinvent:
ibrix_ilo —c —u ibrixpwr —p hpinvent
• HP-OpenIPMI does not work with the HP-Health service. For example, Proliant health check tools
such as SMH and SIM and hpasmcli commands such as SHOW POWERSUPPLY do not report
errors. This situation occurs because StoreAll OS software requires standard RHEL IPMI. Remove
the HP-OpenIPMI RPM (execute rpm -e HP-OpenIPMI), and then start the standard RHEL IPMI
(execute /etc/init.d/ipmi start). The standard RHEL IMPI will now start automatically
when the server is booted.
• During server migration or failover, certain cluster events will be reported as alerts. These events
are expected and normal, and are reported temporarily as a server is failing over to another
server.
• Node failover does not occur when a node has a complete loss of power (for example, removing
power cords or pulling a blade from a chassis). Do not test high availability in this manner.
• NFS locks may return an error code (37) after an unlock operation even though the lock was
correctly released. If other results are normal, you can ignore this error code.
• On 9730 systems, the iLO can fail to power up a server when directed to do so from the iLO web
page or the iLO's Integrated Remote Console. To correct this condition, reset the iLO processor.
This can be done from the iLO web UI; select Reset on the Diagnostics page.
• After a server is rebooted following a QR install and before the server is configured, an error
message reports that the SRVSVCD service failed to load. The failure occurs because the service
requires that the network subsystem be configured. The error message can be safely ignored.
After the network is configured, restart the SMB service.
Workarounds 27