Owners Manual

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.

Possible Cause HCN Setup could not set up Fluid Cache on the server because the MPIO service

was configured for multipathing, but devices required by Fluid Cache were not

blacklisted in the etc/multipath.conf file.

Solution Add blacklist entries for the devices required by Fluid Cache. On each node in the

cluster, modify the Devices section of the /etc/multipath.conf file as follows:

blacklist {

devnode "^fldc[0-9]*"

devnode "^nvme[a-z]*"

devnode "^rssd[a-z]*"

}

After creating the entries and saving the file, start Fluid Cache by running this

command: service fldc_agentd start

Incorrect Network Address or Netmask

Possible Cause While setting up a server, incorrect values were entered for the network address or

netmask of either the management interface or the cache network.

Solution Restart HCN Setup and enter the correct values. See Setting up the Fluid Cache

Servers.

Server Does Not Appear in List of Servers

Possible Cause A configuration issue is preventing the server from appearing in the list.

Solution From the server, run the command ip addr. The cache network interface’s state

should display as UP. If not, recheck the server configuration. See Preparing the

Fluid Cache Servers and Setting up the Fluid Cache Servers.

Possible Cause Firewall or iptables settings are preventing network communication.

Solution Check your firewall and iptables settings. See Checking Security Settings.

Possible Cause The network switch is not correctly cabled or configured.

Solution Review the settings for the network switch and consult your switch

documentation. See Cluster or Application Has Performance Issues.

Possible Cause The Fluid Cache agent is not running on the server.

Solution From the server, run the command: service fldc_agentd start

Possible Cause The Avahi daemon is not running on the server.