Instruction Manual
Table Of Contents
- Dell FluidFS V3 NAS Solutions For PowerVault NX3500, NX3600, And NX3610 Administrator's Guide
- Introduction
- How PowerVault FluidFS NAS Works
- FluidFS Terminology
- Key Features Of PowerVault FluidFS Systems
- Overview Of PowerVault FluidFS Systems
- PowerVault FluidFS Architecture
- Data Caching And Redundancy
- File Metadata Protection
- High Availability And Load Balancing
- Ports Used by the FluidFS System
- Other Information You May Need
- Upgrading to FluidFS Version 3
- FluidFS Manager User Interface Overview
- FluidFS 3.0 System Management
- Connecting to the FluidFS Cluster
- Managing Secured Management
- Adding a Secured Management Subnet
- Changing the Netmask for the Secured Management Subnet
- Changing the VLAN ID for the Secured Management Subnet
- Changing the VIP for the Secured Management Subnet
- Changing the NAS Controller IP Addresses for the Secured Management Subnet
- Deleting the Secured Management Subnet
- Enabling Secured Management
- Disabling Secured Management
- Managing the FluidFS Cluster Name
- Managing Licensing
- Managing the System Time
- Managing the FTP Server
- Managing SNMP
- Managing the Health Scan Throttling Mode
- Managing the Operation Mode
- Managing Client Connections
- Displaying the Distribution of Clients between NAS Controllers
- Viewing Clients Assigned to a NAS Controller
- Assigning a Client to a NAS Controller
- Unassigning a Client from a NAS Controller
- Manually Migrating Clients to another NAS Controller
- Failing Back Clients to Their Assigned NAS Controller
- Rebalancing Client Connections across NAS Controllers
- Shutting Down and Restarting NAS Controllers
- Managing NAS Appliance and NAS Controller
- FluidFS 3.0 Networking
- Managing the Default Gateway
- Managing DNS Servers and Suffixes
- Managing Static Routes
- Managing the Internal Network
- Managing the Client Networks
- Viewing the Client Networks
- Creating a Client Network
- Changing the Netmask for a Client Network
- Changing the VLAN Tag for a Client Network
- Changing the Client VIPs for a Client Network
- Changing the NAS Controller IP Addresses for a Client Network
- Deleting a Client Network
- Viewing the Client Network MTU
- Changing the Client Network MTU
- Viewing the Client Network Bonding Mode
- Changing the Client Network Bonding Mode
- Managing SAN Fabrics
- FluidFS 3.0 Account Management And Authentication
- Account Management and Authentication
- Default Administrative Accounts
- Default Local User and Local Group Accounts
- Managing Administrator Accounts
- Managing Local Users
- Managing Password Age and Expiration
- Managing Local Groups
- Managing Active Directory
- Managing LDAP
- Managing NIS
- Managing User Mappings between Windows and UNIX/Linux Users
- FluidFS 3.0 NAS Volumes, Shares, and Exports
- Managing the NAS Pool
- Managing NAS Volumes
- File Security Styles
- Thin and Thick Provisioning for NAS Volumes
- Choosing a Strategy for NAS Volume Creation
- Example NAS Volume Creation Scenarios
- NAS Volumes Storage Space Terminology
- Configuring NAS Volumes
- Cloning a NAS Volume
- NAS Volume Clone Defaults
- NAS Volume Clone Restrictions
- Managing NAS Volume Clones
- Managing CIFS Shares
- Managing NFS Exports
- Managing Quota Rules
- Viewing Quota Rules for a NAS Volume
- Setting the Default Quota per User
- Setting the Default Quota per Group
- Adding a Quota Rule for a Specific User
- Adding a Quota Rule for Each User in a Specific Group
- Adding a Quota Rule for an Entire Group
- Changing the Soft Quota or Hard Quota for a User or Group
- Enabling or Disabling the Soft Quota or Hard Quota for a User or Group
- Deleting a User or Group Quota Rule
- Managing Data Reduction
- FluidFS 3.0 Data Protection
- FluidFS 3.0 Monitoring
- FluidFS 3.0 Maintenance
- Troubleshooting
- Getting Help
Replication Internal Error
Description Replication between the source and the destination NAS volumes fails due to an
internal error.
Workaround Contact Dell to resolve this issue.
Replication Jumbo Frames Blocked
Description Replication between the NAS source volume and NAS destination volume fails
because the jumbo frames are blocked over the network.
Cause Replication task fails because jumbo frames are blocked over the network.
Workaround The administrator must verify that the network configuration between the source
cluster and the destination cluster has enabled transferring jumbo frames across the
switches or routers.
Replication Destination Does Not Have Enough Space
Description Replication between NAS source volume and NAS destination volume fails because
there is not enough space in the destination NAS volume.
Cause Replication task fails because there is not enough space in the destination NAS
volume.
Workaround Increase the space of the destination NAS volume.
Replication Source Is Busy
Description Replication between the NAS source volume and the NAS destination volume fails
because the file system of the source NAS volume is busy replicating other NAS
volumes.
Cause Replication task fails because the file system of the source NAS volume is busy
replicating other NAS volumes.
Workaround The replication continues automatically when the file system releases part of the
resources. The administrators must verify that the replication automatically continues
after a period of time (an hour).
Replication Source Is Down
Description Replication between the NAS source volume and the NAS destination volume fails
because the file system of source NAS volume is down.
Cause The file system of the source NAS volume is down.
Workaround Administrators must check if the NAS cluster solution is down in the source system,
by checking the monitoring section of the NAS Manager. If the NAS cluster solution is
down, the administrators must start the file system on the source cluster. The
replication continues automatically when the file system starts.
Replication Source Is Not Optimal
Description Replication between the source and the destination NAS volumes fails because the file
system of the source NAS volume is not optimal.
Cause Replication fails since the file system of the source is not optimal.
184