Owners Manual

/opt/dell/fluidcache/bin/fldcsan --user=<username>:<password> --list –hcn
The results should be similar to the following, and should list all the servers you intend to include in the
Fluid Cache cluster:
-------------------------------------------------------
hcnId: 75fd0b3d-8626-4c1c-85da-3c2a2e518932
hccId: b8ddf6de-ba87-4ce9-9ab7-6c5b39dbf7af
hostname: server1.company.com
-------------------------------------------------------
hcnId: 70c152c5-8639-49e1-a870-a0fbb23b762d
hccId: b8ddf6de-ba87-4ce9-9ab7-6c5b39dbf7af
hostname: server2.company.com
-------------------------------------------------------
hcnId: d22b054a-b3ff-4180-8b6e-1cc4169141a5
hccId: b8ddf6de-ba87-4ce9-9ab7-6c5b39dbf7af
hostname: server3.company.com
SUCCESS:
Checking Linux Dependencies
During installation, RPM checks for the necessary Linux dependencies and prompts you to install any that
are not found.
To check which dependencies are currently installed on your system, run this command: rpm -qa
For a complete list of dependencies required for installation, refer to the Release Notes.
Avahi Functionality
Fluid Cache uses Avahi for autodiscovery between cluster nodes. To check that the Avahi daemon is
running on a node, run this command: ps –ef | grep avahi-daemon. To start the Avahi daemon, run
this command: /etc/init.d/avahi-daemon start. To ensure that the Avahi daemon starts when the
system is rebooted, run this command:
chkconfig avahi-daemon on.
NOTE: 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.
47