6.1.2 HP IBRIX X9000 Release Notes (AW549-96048, October 2012)

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.
The LDAP ID mapping features depends on successful communication with the configured LDAP
server.
The openldap-clients-<version> RPM is required to perform ldapsearch commands
from the command line. This RPM is available on the OpenLDAP site.
• Increasing the values of the LdapMaxWaitTime and LdapMaxEntries can affect the performance
of name resolutions for CIFS and non-CIFS users in large LDAP directory environments. The AD
name cache protects against excessive LDAP searches. The default value for these parameters is
10. The range of values is 0 (unlimited) or 1–32767.
Block snapshots
• Snapshot creation may fail while mounting the snapshot. The snapshot will be created successfully,
but it will not be mounted. Use the following command to mount the snapshot manually:
ibrix_mount -f <snapshotname> -m /<snapshotname>
• Quotas are disabled on block level snapshots (for example, MSA2000 snapshots) and the quota
information from the origin file system is not carried to the block level snap file system. Block level
snapshots are temporary file systems that are not writable. Users should not query quota information
against block level snap file systems.
• After the initial creation of a snapshot, it can take 4 to 6 minutes to mount the snapshot.
• Block snapshots are not created when a volume group is mapped to more than one logical volume.
Remote Replication
• When remote replication is running, if the target file system is unexported, the replication of data
will stop. To ensure that replication takes place, do not unexport a file system that is the target
for a replication (for example, with ibrix_crr_export -U).
• Remote replication will fail if the target file system is unmounted. To ensure that replication takes
place, do not unmount the target file system.
• When continuous remote replication is used and File Serving Nodes are configured for High
Availability, you will need to take the following steps following failure of a node:
1. Stop continuous remote replication.
2. After the migration to the surviving node is complete, restart continuous remote replication
to heal the replica.
If these steps are not taken, any changes that had not yet been replicated from the failed node
will be lost.
Workarounds 11