6.1.4 HP IBRIX X9000 Storage Release Notes

• When a file system containing a CIFS share was replicated in continuous mode, file deletions
from the CIFS share were not propagated to the target.
• The NIC monitor failed with a segmentation fault.
• The HP IBRIX X9000 Network Storage System File System User Guide did not explain that when
a quotas file is imported, the quotas are stored in a different, internal format. When a quotas file
is exported, it contains lines using the internal format. However, when adding entries, you must
use the A, B, or C format, as described in the user guide.
• When FTP was used behind a NAT firewall, the pasv_address parameter could not be specified
to allow FTP connection through the NAT device. You can now allow NAT connections on the
Modify FTP Share dialog box on the GUI, or you can set the allow_nat=true parameter with
the ibrix_ftpshare -m -S SETTINGLIST option.
• NFS clients would hang when the network lost TCP connectivity temporarily.
• The HP IBRIX X9000 Network Storage System File System User Guide and HP IBRIX X9000
Network Storage System CLI Reference Guide needed more information about deleting directories
containing snapshots.
• Data tiering could result in zero length files.
Workarounds
This section contains workarounds for product situations that may occur:
Installation and network configuration
• On X9720 systems with G6 blades, the Quick Restore installation reports that the G6 Ethernet
firmware must be upgraded. The Ethernet device (eth0) must be up when you upgrade the
firmware. Use the following command to bring up eth0 and then upgrade the firmware:
# ifup eth0
The following document provides additional detail for HP Support personnel:
http://saw.cce.hp.com/km/saw/view.do?docId=emr_na-c03466768
• When creating a user NIC with a VLAN tag on a bond, running the ibrix_nic -c command
causes the parent bond to become degraded. The workaround is to determine the device that is
down and then bring up that device manually. For example, if bond0 is made up of eth4 and
eth5, use ifcfg to determine which device is down. Then use ifup to bring up the device,
such as ifup eth4.
Management console
• If you need to make cluster configuration changes such as adding, extending, or deleting a file
system, be sure that at least two file serving nodes in the cluster are UP and are not in
NoFMFailover mode. If a configuration change is necessary and only one node is UP, save a
copy of /usr/local/ibrix/tmp/fmbackup.zip after each configuration change is
completed. In the case where only one node is UP, this copy can be used later if that node goes
down before any of the other nodes come up. In general, before you bring up cluster nodes that
have been down for some time, ensure that the cluster already has an active Fusion Manager
running.
• When the active management console is moved to fmnofailover mode, a passive management
console will transition to active mode. Be sure that this transition is complete before you move the
previously active management console from fmnofailover mode to passive mode. (Use the
ibrix_fm -i command to check the mode of each management console.) If the passive
management console has not yet assumed active mode, the management console being moved
from fmnofailover to passive mode will become active again.
Workarounds 11