6.3 HP StoreAll Storage Release Notes (TA768-96086, April 2013)

3. To verify your installation of the credentials, list the credentials by entering the following
command:
hpsp_credmgmt --get-cred -s couplet:couplet/* --output-sl
The command displays the credentials for your system. Your output would differ from the
following example to reflect your system configuration:
10.125.2.221|monitor|!monitor|couplet:couplet/array/500c0ff1390c0000/mgmtport_b/ro
10.125.2.221|manage|!manage|couplet:couplet/array/500c0ff1390c0000/mgmtport_b/rw
10.125.2.220|monitor|!monitor|couplet:couplet/array/500c0ff1390c0000/mgmtport_a/ro
10.125.2.220|manage|!manage|couplet:couplet/array/500c0ff1390c0000/mgmtport_a/rw
SMB
• The HP SMB authentication process could crash while processing authentication requests that try
to enumerate local users. This problem occurs only when local authentication mode is used and
the local user database has a group that has more than 1,500 users.
• SMB and StoreAll Windows clients cannot be used together because of incompatible AD user to
UID mapping. You can use either SMB or StoreAll Windows clients, but not both at the same time
on the cluster.
• The StoreAll SMB server does not support connections from Linux SMB clients. The workaround
is to use NFS for Linux.
• SMB 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.
• When the Microsoft Windows Share Management interface is used to add a SMB share, the
share path must include the StoreAll 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 StoreAll management console GUI and CLI allow only 9000 file systems and directories to
be exported as SMB shares. However, the Microsoft Windows Share Management interface
allows you to create an SMB share that is not on a StoreAll 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 an
SMB 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 StoreAll 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 an SMB 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 SMB 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 an SMB 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'
Workarounds 13