6.1.2 HP IBRIX X9000 Release Notes (AW549-96048, October 2012)

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/fmarchive.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.
CIFS
• CIFS and X9000 Windows clients cannot be used together because of incompatible AD user to
UID mapping. You can use either CIFS or X9000 Windows clients, but not both at the same time
on the cluster.
• The X9000 CIFS server does not support connections from Linux SMB clients. The workaround is
to use NFS for Linux.
• Alternate Data Streams (ADS) are not supported. When a file with an ADS is moved or copied
to the CIFS Server, X9000 Software moves/copies the file, but the attached ADS is not copied.
Attempts to create an ADS or a filename containing a colon (:) will be failed by the CIFS Server.
• CIFS DCN is supported on Windows File Explorer with the following exception:
◦ The recursive notification flag in the notify request is ignored. Notifications are delivered only
for one directory level.
• If CIFS is joined to a domain, before introducing LDAP ID mapping or changing the domain or
the provision mode, you should clear the name cache on each node. This step prevents unexpected
results such as the corruption of a name cache entry when the new configuration is in place. To
clear the cache, run the following command:
/opt/likewise/bin/lw-lsa ad-cache --delete-all
• When the Microsoft Windows Share Management interface is used to add a CIFS share, the
share path must include the X9000 file system name. The Browse button on the MMC cannot be
used to locate the file system. Instead, enter the entire path, such as C:\data\.
• The X9000 management console GUI and CLI allow only X9000 file systems and directories to
be exported as CIFS shares. However, the Microsoft Windows Share Management interface
allows you to create a CIFS share that is not on an X9000 file system. Although the share will be
available from the file serving node to which Windows Share Management was connected, it
will not be propagated to the other file serving nodes in the cluster.
Workarounds 9