Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
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.
•
The ibrix_localusers -i
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
DOMAIN\username or a MACHINE\username. On X9000 systems, local users are displayed
as LOCAL\username, and it may seem like you should specify LOCAL\username in the Add
dialog box in Windows. However, in this case, the Windows client cannot interpret LOCAL.
Instead, specify the machine name of the server. For example, to add LOCAL\user1 to an ACL
on a CIFS file shared out by serverX, specify serverX\user1 in the Add dialog box on the
security tab. If you later use the Windows security tab to look at this ACL, the server name will
have been replaced by LOCAL (the CIFS server performs this remapping to ensure that local users
are symmetric between all servers in the cluster, and are not specific to any one machine name
in the cluster.)
•
When joining a CIFS domain, the $ character cannot be used in passwords unless it is escaped
with a slash (\) and enclosed in single quotes (' '). For example:
ibrix_auth -n IB.LAB -A john -P 'password1\$like'
•
If you are using a Windows Vista client and running more than a single copy of Robocopy from
that client, a hang is possible. The work around is to disable the SMB2 protocol on all file serving
nodes. Complete these steps:
12
Workarounds
...Other models in this manual:
Media Storage - HP IBRIX X9320 10GbE Performance Block (393.95 kb)
Media Storage - HP IBRIX X9320 IB Performance Block (393.95 kb)
Media Storage - HP StoreAll 8800 Storage Node (393.95 kb)
Media Storage - HP StoreAll 9320 1GbE Storage Node Pair (393.95 kb)