6.3.2 HP StoreAll OS Release Notes

3. Fail over a server (ibrix_server -f -h <server_name>)
4. Unmount the file system.
Workaround: Restart the server with the issue 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.
• 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 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.
• Incorrect status reporting the storage is degraded when it is not occurs because the monitoring
software did not know that the credentials to the storage array had been changed and could not
communicate with the array and became confused. A future release will correct the events and
make them more useful.
• The Data Tiering Wizard in the GUI was designed to function with the file system segments
selection set to either the default value or specific segments and the allocation policy set to the
default value. If you use the CLI to change the segment selection to either ALL or LOCAL, the GUI
(the Data Tiering Wizard) will no longer function correctly. With the segment selection changed
to a non-default value, attempts to change the file system tuning settings while modifying the
primary tier in the wizard will not be accepted. Further, no messages or warnings are displayed
in the GUI.
To restore normal GUI behavior, you must reset the file system segment selection and allocation
policy to the default values in the CLI using the following command:
ibrix_fs_tune -f file_system_name -h host_name,host_name -p -U
28 Workarounds