5.6.3 HP IBRIX X9000 Release Notes (AW549-96043, December 2012)

4. Start Likewise:
/etc/init.d/lwsmd start && /opt/likewise/bin/lwsm start srvsvc
5. Restart the management console:
/etc/init.d/ibrix_fusionmanager restart
The management console will now recognize the Active Directory users and groups, and you can
assign quotas to them.
• For configurations with two management consoles, if the node hosting the active management
console goes down, it is important to reboot it as soon as possible. The management console on
that node can then assume a passive role and receive updates from the new active management
console. If the node remains down and the node hosting the active management console also
goes down, the cluster configuration data may become inconsistent, depending on the order in
which the nodes are rebooted.
• When the active management console is moved to maintenance 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 maintenance 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 maintenance 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.
• Occasionally a share cannot be mounted using the DNS name. The workaround is to use the IP
address instead.
• 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.
Some older versions of the CIFS Server allowed these ADS files to be saved as separate files with
a colon (:) in their names, such as testfile.htm:Zone.Identifier or
Thumbs.db:encryptable:$DATA. These ADS files are no longer attached to their original
files and can be safely removed if they are not needed. Because the colon (:) is now illegal in a
filename, any ADS files from old CIFS Server versions must be removed from the Linux command
prompt instead of over a CIFS share. (Attempting to delete them using CIFS will fail because of
the illegal filename.)
• 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.
• The ibrix_localusers -i <user information> command fails if the user information
includes commas. To enter commas in the user information, use the management console GUI
instead of the CLI.
• When you use the Windows security tab to add local users or groups to a security ACL on a CIFS
file (for either file or share-level permissions), you typically specify the user to add as either a
14 Workarounds