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

NFS Insecure Access To Secure Export
Description User tries to access a secure export from an insecure port.
Cause Secure export requirement means that the accessing clients must use a well-known
port (below 1024), which usually means that they must be a root (uid=0) on the client.
Workaround
• Identify the relevant export and verify that it is set as secure (requires secure client
port).
• If the export must remain secure, see the NFS client documentation in order to
issue the mount request from a well-known port (below 1024).
• If a secure export is not required (e.g., the network is not public), ensure that the
export is insecure and retry accessing it.
NFS Mount Fails Due To Export Options
Description This event is issued when NFS mount fails due to export options.
Cause The export list filters client access by IP, network or netgroup, and screens the
accessing client.
Workaround
1. Verify the relevant export details. Write down all existing options so that you are
able to revert to them.
2. Remove IP/client restrictions on the export and retry the mount.
3. If the mount succeeds, verify that the IP or domain is explicitly specified, or that it
is part of the defined network or netgroups. Pay attention to pitfall scenarios,
where the network netmask is not intuitive, for example, 192.175.255.254 is part
of 192.168.0.0/12, but not of 192.168.0.0/16.
4. After the mount succeeds, adjust the original options accordingly.
NFS Mount Fails Due To Netgroup Failure
Description This event is issued when client fails to mount an NFS export because the required
netgroup information cannot be attained.
Cause This error is usually the outcome of a communication error between the NAS system
and the NIS/LDAP server. It can be a result of network issue, directory server overload,
or a software malfunction.
Workaround Repeat the following process for each configured NIS server, each time leaving just a
single NIS used, starting with the problematic NIS server:
1. Inspect the NIS/LDAP server logs and see if the reason for the error is reported in
the logs.
2. Complete a network test by pinging the NAS from a client located in the same
subnet as the NIS/LDAP server.
3. Ping the NIS/LDAP server from a client located in the same subnet as the NAS.
4. If a packet loss is evident on one of the above, resolve the network issues in the
environment.
5. Using a Linux client located in the same subnet as the NAS and configured to use
the same directory server, query the netgroup details from the NIS/LDAP server
using the relevant commands. Ensure that the reply is received in a timely
manner (up to 3 seconds).
You can temporarily workaround the problem by removing the netgroup restriction
on the export and/or by defining an alternative directory server.
177