5.5.5 HP IBRIX X9000 Release Notes

ibrix_fm_tune -S -o vendorStorageHardwareStaleInterval=1800
The default value of this command is 900; the value is in seconds. A higher value reduces the
probably of all components toggling from Up to Stale and back to Up because of the conditions
listed above, but will increase the time before an actual component failure is reported.
General
• On Windows X9000 clients, when Active Directory is switched from the static mapping mode to
dynamic mapping, users with Full Control cannot rename files. This situation occurs because the
UIDs and GIDs have changed. Take these actions:
◦ If the static mapping mode had UID 0 and GID 0 mapped to the domain administrators and
you want to retain this configuration, execute the following command:
ibrix_activedirectory -A -d DOMAIN_NAMES -W DEFAULTWINUSERNAME –M
–U 0 –G 0
◦ Change the UID and GID on all existing files and directories to match the new UID and GID.
For example, if user John previously had UID=10 and now has UID=20003456, you will
need to change the owner on all files with UID=10 to UID=20003456.
• The ibrix_pv -a -o mpath command does not recognize a multipath device. The command
works properly when an argument is added to ignore the standard scsi devices. Execute the
command as follows, specifying the path to your device.
ibrix_pv -a -o accept:/dev/mapper/mpath10,~standard
• 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 X9000 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.
• The log files for user-initiated jobs (such as running ibrix_fsck and migrating or rebalancing
segments) are not rotated automatically. To control the space used by these log files, you will
need to maintain them manually. The log files are located in /usr/local/ibrix/log.
• When you perform a Quick Restore of a file serving node, the NFS, CIFS, FTP, and HTTP export
information is not automatically restored to the node. After operations are failed back to the node,
the I/O from client systems to the node fails for the NFS, CIFS, FTP, and HTTP shares. To avoid
this situation, manually restore the NFS, CIFS, FTP, and HTTP exports on the node before failing
it back.
• 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.
• The Modify NDMP Configuration dialog box reports an error when you attempt to change any
of the values on the dialog. To work around this condition, first click in the field for Enable NDMP
Sessions and then make your changes.
Documentation additions and corrections
Following are additions and corrections to the user documentation.
Fixes 15