Administrator Guide

Solution Wait for the volumes to unmap. Unmapping speed should increase as more
volumes are unmapped.
Unable to Map Volumes to Fluid Cache using Enterprise
Manager
Possible Cause ESXi hosts were added to vCenter by using their IP Address and not their hostname
when DNS is being used on your network.
Solution Turn off the Fluid Cache VSA virtual machines on the ESXi hosts. Remove the ESXi
hosts from vCenter. Add the ESXi hosts back to vCenter by using their registered
DNS name.
Possible Cause DNS assigned address for ESXi host and the VSA virtual machine that is used for
Fluid Cache has changed from its initial setting during Fluid Cache cluster creation.
Solution Configure your DNS server to use static addresses for your ESXi hosts and Fluid
Cache VSA VMs.
Cannot Configure the Cache Network
Possible Cause Firewall settings are preventing access to one or more ports required by Fluid
Cache.
Solution Change your firewall settings to allow access by Fluid Cache. For a list of required
ports, see Checking Network Connections.
Possible Cause One of the ports required by Fluid Cache is in use by another process.
Solution Refer to the required ports listed in Checking Network Connections and reassign
ports as needed.
NOTE: Port 3033 is used to communicate with Enterprise Manager and
Storage Center. To configure those applications to use a different port, refer to
the corresponding Administrator’s Guide. After a new port is configured in
Enterprise Manager or Storage Center, Fluid Cache automatically uses the new
port.
NOTE: Port 7449 and 5480 are required by Fluid Cache. If other applications
are using these ports, configure those applications to use different ports.
Possible Cause If an incorrect IP address is entered during configuration of the VSA (see
Configuring the VSA), an error message indicates that Fluid Cache cannot log in
due to an incorrect vCenter address.
Solution Select Change vCenter and re-enter the IP address, or check network connections
and settings.
Possible Cause If one of the iSER interfaces required by the VSA cannot be created, the VSA
configuration fails and an error message indicates that the network is not
configured properly. Note that an existing iSER interface configured in vCenter can
prevent creation of the iSER interface required by the VSA.
53