Administrator Guide

Checking Network Connections
For Fluid Cache to function correctly, each Fluid Cache server must be able to communicate with other
network components. Make sure that the following ports are available:
Table 2. Ports Specifications
Interface Port number Port type
Fluid Cache cluster Configuration Manager 7449 TCP
Node Auto-Discovery functionality 5353 UDP
Web-based server status tool 6773 and 6774 TCP (https)
(optional) Web-based server status tool 8080 and 8082 TCP (http)
Fluid Cache to Enterprise Manager 3033 TCP
Fluid Cache to Storage Center 3033 TCP
NOTE: Fluid Cache cannot be configured and does not function properly if any of these ports are
unavailable. To diagnose network connection problemsand reassign port numbers, see the
troubleshooting topic Cannot Configure Fluid Cache.
RDMA Functionality
To make sure that RDMA is working correctly between the cluster nodes, use the utility ib_send_bw:
1 On one node, run the command: ib_send_bw
2 On a second node, run the command: ib_send_bw <IP_address_of_first_node>
If the test is successful, the bandwidth for the node displays on each node.
Multipathing Support
Fluid Cache supports multipathing and uses existing multipath configurations. You must make two
modifications to the Devices section of the /etc/multipath.conf file on each node in the cluster:
1 For the vendor “COMPELNT”, specify no_path_retry 6
2 Add blacklist entries to exclude devices used by Fluid Cache, as shown:
blacklist {
devnode "^fldc[0-9]*"
devnode "^nvme[a-z]*"
devnode "^rssd[a-z]*"
}
Preparing the Fluid Cache Components 15