6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)

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 [e-mail] -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.
LDAP
• When configuring LDAP on the GUI, double quotes are not supported in any fields of the LDAP
configuration window, including the password field. Also, escaped slashes are not supported. If
you enter \\; it will be parsed literally as \\ instead of \. Also, the ibrix_ldapconfig
command supports double quotes only at the beginning and end of a value. For example:
ibrix_ldapconfig -a -h 10.30.239.174 -b "cn=Manager,dc=ldapx,dc=net"
-p "mypassword "
The command does not support escaped slashes.
LDAP ID mapping
• When LDAP ID mapping is configured with the GUI or CLI, the following fields are not validated
to ensure successful communication with the LDAP server: LdapBase, LdapServer, LdapUserDn,
LdapLapMaxWaitTime, LdapMaxEntries fields. It may be helpful to perform a manual ldapsearch
test with the intended configuration values to assure success when configuring LDAP ID mapping.
Workarounds 17