Owners Manual

Solution Remove the volume mapping and create a new mapping. When you create the

new mapping, you can then select a different cache mode (“cache policy”). See

Removing Volume Mappings and Mapping Volumes.

Possible Cause The cluster is in maintenance mode.

Solution Take the Fluid Cache cluster out of maintenance mode by selecting the cluster in

Enterprise Manager, clicking Edit Settings in the Summary tab, and clearing the

Maintenance Mode option. Note that certain system failures or an invalid license

may prevent the cluster from being taken out of maintenance mode. Refer to the

Enterprise Manager Status and Events tabs, and see Fluid Cache License Is Expired.

Fluid Cache Node Is Unavailable in Enterprise Manager

Possible Cause The node failed during restart. The node was unable to perform a graceful

shutdown because the chkconfig command was used to shut down the Fluid

Cache agent service.

Solution Do not use the chkconfig command to disable the Fluid Cache agent service.

Perform normal node recovery procedures to return the node to normal operation.

Cached LUNs Are Unavailable

Possible Cause After restarting Fluid Cache or restarting a server, cached LUNs may not be

immediately available.

Solution Wait for the cached LUNs to reappear. It may take a significant amount of time to

write a large amount of data. The cached volumes reappear after the cache

completes recovery.

Possible Cause A fault in the cluster is preventing the volume from being recognized by Enterprise

Manager.

Solution Check the Enterprise Manager status page and event log for error messages.

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.