Owners Manual

Solution Make sure that all paths to the Compellent are operational.
Possible Cause The TUI configuration tool could not obtain the iSCSI IQN from the ESXi host.
When attempting to configure the iSCSI network, the following error message is
displayed: “Cannot configure iSCSI. ESXi host <host_name> is missing configured
iSCSI software adapter.”
Solution Manually configure the ESXi host by logging in to the ESXi host that the VSA is
deployed on and configure the iSCSI software initiator.
Cannot Create a Fluid Cache Cluster
Possible Cause A minimum of three PowerEdge servers have not been configured for use with
Fluid Cache. Until at least three servers have Fluid Cache installed and configured,
the option to create a Fluid Cache cluster is unavailable.
Solution Add three or more nodes and configure the nodes before attempting to create a
Fluid Cache cluster in Enterprise Manager.
Possible Cause Network connectivity issues are preventing the creation of a Fluid Cache cluster.
Solution Check that the security settings are correct and the required ports and network
connections are open. See Checking Network Connections and Checking Security
Settings.
Cannot Map Volumes to a Fluid Cache Cluster
Possible Cause The iSCSI software adapter on the ESXi host is not logged in to the Storage Center
that contains the LUN you are mapping.
Solution Make sure the iSCSI adapter on the ESXi host is logged in to the appropriate
Storage Center.
Possible Cause The iSCSI VMkernel port on the ESXi host is not bound properly to the iSCSI
initiator.
Solution Check the binding in vSphere by opening the iSCSI Initiator Properties window. If
no VMkernels are shown, click Add, select the VMkernel that corresponds to your
iSCSI (uncached) network, and click OK. Click Close on the Properties window and
when prompted to rescan the adapter, click Yes.
Cannot Connect to Cluster Nodes
Possible Cause Time synch issues are preventing Enterprise Manager from connecting to the
cluster nodes. The cluster appears to be configured correctly, but in the Overview
page, no Fluid Cache connections are active.
Solution Make sure that you have enabled Network Time Protocol and that in the vTools
control panel, Synchronize guest time with host is not selected. (For more
information, refer to the VMware document Timekeeping in VMware Virtual
Machines).
41