HP 3PAR InForm OS 3.1.1 GA/MU1/MU2/MU3 Release Notes
To allow users to authenticate while also requiring a certificate with SSL, recreate the certificate
used by the LDAP or Active Directory server and sign it with SHA. A less secure option is to configure
LDAP authentication with SSL but not require a valid certificate by using the setauthparam
command to set the ldap-reqcert parameter to 0.
A more definitive method of confirming that the issue is with the certificate is by using the gnutls-cli
command (available for most Linux distributions) to display certificate information. For example,
if the LDAP server is called ldap-server.example.com and its certificate is in the file ca.cert, this
command checks the certificate:
% gnutls-cli -p 636 --x509cafile ca.cert ldap-server.example.com
If the certificate is signed with MD5 the output includes:
- The hostname in the certificate matches ‘ldap-server.example.com’.
nl
- Peer’s certificate chain uses insecure algorithm
nl
- Peer’s certificate is NOT trusted
nl
*** Verifying server certificate failed...
Remote Copy Link Speeds
When setting link speeds for Remote Copy operations using the controlport command speed
setting, only the 1000Mbps link speed option should be used. Using the 10Mbps and 100Mbps
link speed options may result in negotiation issues. Support for setting the interface speed to 10Mbps
and 100MBps will be removed in a future release.
Known Issues with the InForm OS
Thin Provisioned Virtual Volumes with no_tp_bzero policy enabled could result in
uninitialized data (Bug 62394)
HP 3PAR Storage Systems running InForm OS version 3.1.1 and using a Thin Provisioned Virtual
Volume (TPVV) in either of the following scenarios are susceptible to having uninitialized data on
the volume.
Scenario 1:
• E-Class, S-Class, T-Class, F-Class, or HP 3PAR P10000 Storage System
• Thin Persistence license available on the array
• Policy no_tp_bzero enabled on a Thin Provisioned Virtual Volume (the default policy is tp_bzero)
• Host issuing 16KB page aligned writes using SCSI WRITE_SAME command with zeros
Scenario 2:
• T-Class, F-Class, or HP 3PAR P10000 Storage System
• Thin Persistence license available on the array
• Policy no_tp_bzero enabled on a Thin Provisioned Virtual Volume (the default policy is tp_bzero)
• Policy zero_detect enabled on a Thin Provisioned Virtual Volume
• A host uses any of the following methods to write 16KB page aligned zeros to the TPVV:
Host issuing SCSI WRITE command◦
◦ Host issuing SCSI WRITE_SAME command (for example, ESX hosts use SCSI WRITE_SAME
when using the VAAI plugin)
Workaround: To avoid this issue, the TPVV must be kept at the default setting of tp_bzero policy.
In cases where the policy is set to no_tp_bzero, the policy should be changed back to tp_bzero
Known Issues with the InForm OS 17