HP 3PAR StoreServ Cluster Extension Software Administrator Guide

HP 3PAR StoreServ CLX Setting tab will not be visible, if the CSV disk dependency on the CLX
resource is not set.
HP 3PAR StoreServ Storage DNS resolution
If the HP 3PAR CLI command takes more than 4 seconds to respond, check if the DNS look up is
fast. If the DNS look up is slow, contact the system administrator to change the DNS settings. You
can also speed up the DNS look up by adding the HP 3PAR StoreServ Storage to the local failover
cluster node DNS mapping file. For example, on Windows host, navigate to C:\WINDOWS\
system32\drivers\etc\hosts and create an entry for Inserv as shown in the following
example.
<DCA_ArrayIP> <DCA_ArrayName>
15.32.75.13 3parArrayB
CLX resource fails to come online or CLX resource configuration fails
This section is applicable only if 3PAR CLI and 3PAR OS are running either 3.1.2 MU3 P16, 3.1.1
MU3 P27, 2.3.1 MU5 P35, 3.1.3, or later versions.
If there is a mismatch of the array certificate stored in the 3PAR StoreServ Storage, and the exception
file for that array stored locally on the failover cluster node, then you cannot configure the CLX
resource or the CLX resource fails to come online or fails.
In the following scenarios, run the CLX configuration tool to overcome the mismatch issue:
• Array certificate expired and was changed by the array administrator. However, CLX on the
failover cluster node continues to use the exception file for the old array certificate.
• Exception file on the failover cluster node got deleted.
• Array certificate on the 3PAR StoreServ Storage has expired but not renewed by the array
administrator.
• CLX fails to get the exception file location. This may be due to the CLX upgrade from previous
versions to 3.02.00 or later.
For more information, perform the steps in Configuring CLX after upgrading from 3.01.00 (For
Windows Server 2008/2008 R2/2012/2012 R2) section of the HP 3PAR StoreServ Cluster
Extension Software Installation Guide.
92 Troubleshooting