Administrator Guide

Table Of Contents
Workaround If a user frequently needs to perform a cross-protocol security related activity, split the data into
separate NAS volumes based on the main access protocol.
Attach Operation Fails
Description The operation to attach the NAS controller to the FluidFS cluster fails.
Workaround
Connect a keyboard and monitor to the NAS controller that failed the attach operation, and view
the error message to determine why the attach operation failed.
Verify that while the NAS controller was detached, the IP assigned to it on the client network was
not allocated to another host. While the NAS controller is detached, it loses its identity, including
IP addresses. When it is attached, its identity is applied back to the NAS controller, including the
IP addresses.
Verify that the default gateway is in the Primary subnet. If the default gateway is not in the
Primary subnet, change the default gateway. For attach to succeed, the default gateway must be
able to be pinged.
After an attach operation fails, the NAS controller must manually be reset to standby mode.
Controller Taking Long Time to Boot Up After Service Pack Upgrade
Description The NAS controller takes a long time to boot up after upgrading the service pack of the NAS
controller firmware.
Cause The upgrade process can take up to 60 minutes to complete.
Workaround
Connect a keyboard and monitor to the NAS controller that is taking a long time to boot up.
If the system is booting, and is at the boot phase, let the upgrades finish. This can take up to 60
minutes to complete.
Do not reboot the NAS controller manually if it is in the boot phase.
494 FluidFS Administration