6.2.1 HP IBRIX 9000 Storage Release Notes (TA768-96074, December 2012)
• 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 IBRIX 9000 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'
• 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:
1. Disable the SMB2 protocol on all nodes:
ibrix_cifsconfig -t -S SupportSmb2=0
2. Restart the SMB service on all nodes:
ibrix_server -s -t cifs -c restart
You may also need to restart the Windows client, as the original negotiated protocol, SMB2, may
be cached by the client. Restarting the client renegotiates the protocol back to SMB1.
• Be sure to remove Active Directory users from the IBRIX 9000 share admin list before removing
them from Active Directory. If you remove an Active Directory user from Active Directory before
removing the user from the IBRIX 9000 share admins list, an error is reported when you attempt
to change the share admins list. If you are seeing errors from this situation, rejoin Active Directory
and remove all share admins. For example:
ibrix_auth -n ib.lab -A administrator@ib.lab -P fusion -S "share
admins="
Then run ibrix_auth again to specify the new list of share admins:
ibrix_auth -t -S "share admins=[ib\Administrator]"
• Do not use spaces in share names. The GUI cannot create a share if there is a space in the name.
• SMB clients have a 45 second timeout on every SMB request they make. If a request's timer
expires before a response comes, the client disconnects and terminates the SMB connection with
this error message: The specified network name is no longer available. After
this, the client must reconnect to the SMB server. If you are seeing this message from clients
connected to a busy server, they may be encountering timeouts from overload. For more information
about SMB client timeouts, see http://support.microsoft.com/kb/102067.
16 Workarounds