Administrator Guide
1 Ping the server from a client on the FluidFS cluster subnet and verify that it responds.
2 Issue a request to the server from a client on the FluidFS cluster subnet and verify that it responds.
3 Check the server logs to see what is causing the server not to respond to requests.
Troubleshooting DNS Congurations
Description Clients are unable to connect to the FluidFS cluster using the system name and/or unable to resolve host
names.
Cause Probable causes might be:
• Client IP address information is not set correctly.
• The FluidFS cluster is not congured to use the correct DNS server.
• DNS records are incorrect.
Workaround
1 Verify that the client IP address information is set correctly.
2 Verify that the FluidFS cluster is congured to use the correct DNS server.
3 Contact the DNS server administrator to verify the DNS record creation.
RX and TX Pause Warning Messages
Description The following warning messages might be displayed when Storage Manager reports connectivity in a Not
Optimal state:
Rx_pause for eth(x) on node1 is off.
Tx_pause for eth(x) on node 1 is off.
Cause Flow control is not enabled on the switch(es) connected to a FluidFS cluster controller.
Workaround See the switch vendor's documentation to enable ow control on the switch(es).
Troubleshoot Replication Issues
This section contains probable causes of and solutions to common replication problems.
Replication Conguration Error
Description
Replication between the source and target NAS volumes fails because the source and target FluidFS cluster
topologies are incompatible.
Cause The source and target systems are incompatible for replication purposes.
Workaround Verify that both the source and target have the same number of NAS controllers.
Replication Target FluidFS Cluster is Busy
Description
Replication between the source NAS volume and the target NAS volume fails because the target FluidFS
cluster is not available to serve the required replication.
Cause Replication fails because the target FluidFS cluster is not available to serve the required replication.
Workaround Verify the replication status on the target FluidFS cluster.
506 FluidFS Administration