Administrator Guide

5. Run the following command to edit theinitiatorname.iscsi file.
#vi initiatorname.iscsi
6. Change the characters with asterisk (*) with the proper ESXi Hosts vmhba##
software IQN that the VSA is associated. For example:
root@localhost iscsi]# cat initiatorname.iscsi
InitiatorName=iqn.1998-01.com.vmware:FLDC-QAESXi55U1-
Srv1-48a43810
7. Run the following command to restart iscsid service.
#service iscsid restart
Solution 2 Perform the steps provided in the section “Configuring the VSA” of the deployment
guide in the following sequence:
1. Perform the steps 1 through 5 as described in the deployment guide.
2. Select Configure This Appliance and press <Enter>.
3. Configure your Backend Storage connection.
4. Perform the steps 6 and 7 and continue with step 10 as provided in the
deployment guide.
Unable to Recreate a Fluid Cache Cluster After a
Hardware Failure
Use Enterprise Manager to completely delete a Fluid Cache cluster that has failed before trying to remake
the cluster.
NOTE: Clean up Enterprise Manager and the Storage Centers after a hardware failure before
recreating a Fluid Cache cluster. The Delete option will not appear unless the Fluid Cache cluster
has been fully removed from Enterprise Manager.
Cache Node is Not Listed
The node was not selected in the Select Servers window when creating the Fluid Cache cluster or the
network switch may not be configured correctly.
1. Make sure the node is selected.
2. If the node is still not listed, review the settings for the network switch and consult your switch
documentation.
Unable to Select a Specific Caching Mode
The required number of nodes or PCIe SSDs may not be available.
Keep in mind that while a cache device or cache server may have been previously configured, it may have
since failed or is impacted by a network failure.
For write-back caching, ensure that there is a minimum of two nodes with PCIe SSDs on different
servers in the Fluid Cache cluster.
For write-through caching, ensure that there is at least one node with a PCIe SSD.
Ensure the cluster is not in maintenance mode.
59