Administrator Guide
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

Workaround Interactive users can retry with correct password. Applications and servers may need
special attention as the user/password, which is usually set in a script or configuration
file, has probably expired.
CIFS Connection Failure
Description CIFS client share access denied.
Cause The user is unknown in the Active Directory server, and the NAS system mapped this
user to a guest user. If the share does not allow guest access, the user receives an
access denied alert.
Workaround Ensure that the user is listed in the Active Directory server the NAS is using.
Alternatively, you can remove the guest limitation for the share. If the user can now
access the share as guest, the newly created files are owned by the nobody/guest
user.
CIFS Delete On Close Denial
Description Files are deleted while they are in use.
Cause If a file is deleted when it is open, it is marked for deletion, and is deleted after it is
closed. Until then, the file appears in its original location but the system denies any
attempt to open it.
Workaround Notify the user who tried to open the file that the file is deleted.
CIFS File Access Denied
Description CIFS file access denied.
Cause Client has insufficient privileges to perform the requested operation on the file.
Workaround This is an informative event. The user may request to modify the file ACL to allow
access.
CIFS File Sharing Conflict
Description CIFS file sharing conflict.
Cause When a file is opened using the CIFS protocol, the opening application communicates
the sharing mode that must be used while this file is open.
This sharing mode describes what other users activities are allowed on this file, while
it is open.
This definition is sent by the application and the user cannot control/configure it.
After there is a violation of the sharing definition, the user receives an access denied
error and this event is issued.
Workaround This is an informative event; The administrator may contact the locking user and
request to close the application referencing this file.
The application which opened the file may not have shut down gracefully. It is
recommended to reboot the client if possible.
CIFS Guest Account Invalid
Description CIFS service cannot start.
Cause A valid CIFS guest account is required for CIFS functionality.
Workaround Configure the system guest account with a valid account.
173