Administrator Guide

Table Of Contents
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 flow control on the switch(es).
Troubleshoot Replication Issues
This section contains probable causes of and solutions to common replication problems.
Replication Configuration 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.
Replication Target File System is Busy
Description
Replication between the source NAS volume and the target NAS volume fails because the target
FluidFS cluster file system is temporarily unavailable to serve the required replication.
Cause Replication fails because the target FluidFS cluster is temporarily unavailable to serve the required
replication.
Workaround The replication continues automatically when the file system releases part of the resources. Verify
that the replication continues automatically after a period of time (an hour).
Replication Target is Down
Description
Replication between the source NAS volume and the target NAS volume fails because the target NAS
volume is down.
Cause Replication fails because the file system of the target NAS volume is down.
Workaround Check whether the file system is down in the target system. If the FluidFS cluster file system is not
responding, you must start the file system on the target FluidFS cluster. The replication continues
automatically after the file system starts.
490 FluidFS Administration