Administrator Guide

Solution

To check device function, select the device in Enterprise Manager and in the Event

tab, look for a device failure message.

If necessary, replace the cache device by following the instructions provided in the

Dell Compellent Enterprise Manager User’s Guide.

Cannot Select a Specific Cache Mode

Possible Cause There is an existing cache mode configured for the volume mapping. The cache

mode chosen for a volume mapping cannot be changed. The existing mapping

must be deleted, and a new mapping created. A new cache mode can be selected

while creating the new mapping.

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.

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.

Enterprise Manager Freezes While Adding or Removing a

Volume Mapping

Possible Cause You are using the VMFS filesystem and did not unmount the filesystem before

removing volume mappings.

Solution Unmount the filesystem before removing the volume mappings (refer to the

document VMware Knowledge Base article 2004605.

Possible Cause Under some conditions, when removing multiple volume mappings, the first

volume may take an unusually long time (more than 20 minutes) to unmap.