Administrator Guide

Solution Check your network connections and verify functionality of the iSER interfaces
using vCenter (Configuration → Networking). Do not use vCenter to delete or
modify the iSER interfaces used by Fluid Cache, or to create new iSER interfaces.
Remove any iSER interfaces that were created prior to configuration of the Fluid
Cache VSA.
Possible Cause The correct version of the Mellanox driver is not installed, which results in an error
message when attempting to power on the VSA. The error message may specify
“Cannot set MAC address or default VLAN for PCI Virtual Function” or error
0x195887107.
Solution Make sure you have the correct Mellanox driver version installed.
Possible Cause One or more paths to the Compellent are not operational. During configuration of
the VSA, all paths to the Compellent must be operational or the configuration is not
successful.
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.
54