HP 3PAR StoreServ Cluster Extension Software Administrator Guide (5697-2894, December 2013)

Also, the physical disk must be connected to the primary datacenter storage array as soon as
the storage array is brought back online.
Another way to avoid this situation is to configure the CLX preexec script which does the
rescan of the disks. The preexec script can be configured in CLX as
DiskRescanDiskpart.bat in the same Windows folder and having the following line in
this script.
echo rescan | diskpart
NOTE: The syntax of the command in the preexec script must be proper, otherwise preexec
script operation fails and then the CLX failover operation also does not succeed.
• If the storage array in the secondary datacenter is brought back online or started after the
array shutdown due to the datacenter disaster or HP 3PAR OS upgrade, the disks presented
to the hosts in the secondary datacenter are not recognized by the Windows operating system.
Due to this issue, if Failover of the cluster resources is triggered to the secondary datacenter,
the disk cluster resource does not come online even though the corresponding CLX resource
comes online.
To avoid this situation (physical disk resources not coming online), ensure that the disk rescan
is done in the Microsoft Failover Cluster hosts manually, connected to the secondary datacenter
storage array as soon as the storage array is brought back online and before you Failover
the corresponding cluster application role to the secondary datacenter hosts.
Another way to avoid this situation is to configure the CLX preexec script which does the
rescan of the disks. The preexec script can be configured in CLX as
DiskRescanDiskpart.bat in the same Windows folder and having the following line in
this script.
echo rescan | diskpart
NOTE: The syntax of the command in the preexec script must be proper, otherwise preexec
script operation fails and then the CLX failover operation also does not succeed.
Cannot connect to HP 3PAR StoreServ Storage
During HP 3PAR StoreServ Cluster Extension configuration, if you are unable to connect to the
3PAR StoreServ Storage, ensure that the storage system is up and running, and the network ports
are functioning properly. To check for response from the storage system over the network, use the
ping command from cluster nodes to the storage system's network name or IP address.
ping <storage system network name or IP address>
If you are using storage system network name, verify it is resolving to proper IP address using
nslookup command from the cluster nodes.
nslookup <storage system network name>
Resource disk failure when HP 3PAR StoreServ Cluster Extension is online
In a cluster resource group, if the Cluster Extension resource is online but dependent disk resource
is failing:
• Ensure that the fibre channel connectivity between the servers and the storage systems is up
and running.
• Verify that the disk resource is dependent to the Cluster Extension resource.
• Ensure that the Remote Copy volume group managed by the Cluster Extension resource contains
the virtual volume which is correctly mapped to the configured disk resource.
• On a cluster node where the Cluster Extension resource is online, ensure that the presented
virtual volume is having read/write access on the HP 3PAR StoreServ Storage.
Cannot connect to HP 3PAR StoreServ Storage 81