Administrator Guide

• Unable to Add a Volume to a Fluid Cache Cluster
• Event Messages Are Not Being Delivered
• Storage Center is Not Available
• Fluid Cache Server is Not Available
• Information Displays Differently Between Storage Centers and Fluid Cache Clusters
• Verify That All Parts of the Fluid Cache Cluster are Communicating with Each Other
• Verify the Data Path is Working
• The Cluster in the Fluid Cache Clusters Display is Marked Red
• Problems Configuring Server Clusters Defined on a Storage Center with Dell Fluid Cache for SAN
Basic Troubleshooting Steps
Make sure the following conditions are fulfilled:
• You have downloaded and installed the most recent firmware, drivers, and software required to support
Fluid Cache for SAN (see Requirements for Fluid Cache).
• The hardware is racked and cabled according to your hardware documentation.
• The network security settings match those specified in Checking Network Connections.
• The ports available to Fluid Cache match those specified in Fluid Cache for SAN Environment.
• All servers are in the same management interface subnet and in the same cache network subnet.
• Each server in the Fluid Cache cluster appears in Enterprise Manager’s list of servers.
• The avahi-daemon is running.
• (Optional—for systems with multipath enabled and running) The Fluid Cache devices have been
excluded in the /etc/multipath.conf file on each server in the cluster. See
Checking Network Connections.
Cannot Set up Fluid Cache on a Server
Possible Cause HCN Setup could not set up Fluid Cache on a server because one of the Linux
dependencies is not installed.
Solution Follow the instructions given by RPM, which should state the dependencies that are
missing. Check for the dependencies listed in the Release Notes and compare them
with the list of currently installed dependencies, which you can check by running this
command: rpm -qa
Fluid Cache uses Avahi for autodiscovery between cluster nodes. To check that the
Avahi daemon is running on a node, run the command: ps –ef | grep avahi-
daemon. To start the Avahi daemon, run the command: /etc/init.d/avahi-daemon
start
. To ensure that the Avahi daemon starts when the server is restarted, run the
command: chkconfig avahi-daemon on. If your avahi-daemon.conf file does
not use the default settings, make sure that Disable Publishing is set to no, that Deny
Interfaces
does not list Fluid Cache interfaces, and that Allow Interfaces is either
commented out or lists all Fluid Cache interfaces.
Troubleshooting Fluid Cache Installations 40