Dell FluidFS V3 NAS Solutions For PowerVault NX3500, NX3600, And NX3610Administrator's Guide

Management interface

The NAS ManagerUser Interface has been updated.

Management connections

The FluidFS cluster is managed using a dedicated Management VIP.

Version 3.0 does not use a Management VIP—the FluidFS cluster can be managed using any client VIP.

During the upgrade, the Management VIP from version 2.0 is converted to a client VIP.

Default management account

The default administrator account is named admin.

The default administrator account is named Administrator.

During the upgrade, the admin account from version 2.0 is deleted and the CIFS Administrator account becomes the version 3.0 Administrator account. During the upgrade, you will be prompted to reset the CIFS Administrator password if you have not reset it within the last 24 hours. Make sure to remember this password because it is required to manage the FluidFS cluster in version 3.0.

User‐defined management accounts

Only local administrator accounts can be created.

You can create local administrator accounts or create administrator accounts for remote users (members of Active Directory, LDAP or NIS repositories).

During the upgrade, any user‐defined administrator accounts from version 2.0 are deleted.

Workaround: Use one of the following options:

Convert the administrator accounts to local users before upgrading and convert them back to administrator accounts after upgrading.

Re‐create administrator accounts after the upgrade.

Command Line Interface (CLI) access and commands

Administrator accounts log into the CLI directly.

Version 3.0 introduces a cli account that must be used in conjunction with an administrator account to log into the CLI.

In addition, the command set is significantly different in version 3.0.

Dell Technical Support Services remote troubleshooting account

The remote troubleshooting account is named fse (field service engineer).

The remote troubleshooting account is named support. During the upgrade, the fse account from version 2.0 is deleted. After the upgrade, the support account is disabled by default.

FluidFS cluster name and NetBIOS name

The FluidFS cluster name and NetBIOS name do not have to match. The NetBIOS name can begin with a digit.

The FluidFS cluster name is used as the NetBIOS name.

Before upgrading, the FluidFS cluster name and NetBIOS name must be changed to match. Also, the FluidFS cluster name cannot be longer than 15 characters and cannot begin with a digit.

Data reduction overhead

Version 2.0 does not include a data

reduction feature.

Version 3.0 introduces a data reduction feature. If data reduction is enabled, the system deducts an additional 100GB per NAS appliance from the NAS pool for data reduction processing. This is in addition to the amount of space that the system deducts from the NAS pool for internal use.

Anti‐virus scanning

You can specify which file types to scan.

You cannot specify which files types to scan—all files smaller than the specified file size threshold are scanned.

You can specify whether to allow or deny access to files larger than the file size threshold.

As in version 2.0, you can specify file types and directories to exclude from anti‐virus scanning.

Supported NFS protocol versions

Version 2.0 supports NFS protocol version 3.

Version 3.0 supports NFS protocol version 3 and 4.

Supported SMB protocol versions

Version 2.0 supports SMB protocol version 1.0.

Version 3.0 supports SMB protocol version 1.0, 2.0, and 2.1.

CIFS home shares

Clients can access CIFS home shares in two ways:

\\<client_VIP_or_name>\<path_prefix>\<username>

\\ <client_VIP_or_name>\homes

Both access methods point to the same folder.

Version 3.0 does not include the “homes” access method. After the upgrade, the “homes” share will not be present, and clients will need to use the “username” access method instead. If you have a policy that mounts the \\ <client_VIP_or_name>\homes share when client systems start, you must change the policy to mount the \\ <client_VIP_or_name>\ <path_prefix>\ <username> share.

Local user names

A period can be used as the last

character of a local user name.

A period cannot be used as the last character of a local user name.

Before upgrading, delete local user names that have a period as the last character and re‐create the accounts with a different name.

Local users and local groups UID/GID range

A unique UID (user ID) or GID

(group ID) can be configured for

local users and local groups.

The UID/GID range for local users and local groups is 1001 to 100,000. There is no way to configure or determine the UID/GID of local users and local groups. This information is internal to the FluidFS cluster.

During the upgrade, any existing local users and local

groups from version 2.0 with a UID/GID that is outside the version 3.0 UID/GID range will remain unchanged. Local users and local groups created after the upgrade will use the version 3.0 UID/GID range.

Guest account mapping policy

By default, unmapped users are

mapped to the guest account, which allows a guest account to access a file if the CIFS share allows guest access.

Unmapped users cannot access any CIFS share, regardless of whether the CIFS share allows guest access.

Guest access is enabled automatically after the upgrade only if there are guest users already defined for any CIFS shares in version 2.0.

NDMP client port

The NDMP client port must be in

the range 1–65536.

The NDMP client port must be in the range 10000–10100.

Before upgrading, the NDMP client port must be changed to be in the range 10000–10100. You must also make the reciprocal change on the DMA servers.

Replication ports

TCP ports 10560–10568 and 26 are used for replication.

TCP ports 10550–10551 and 10560–10568 are used for replication.

Snapshot schedules

Snapshot schedules can be disabled.

Snapshot schedules cannot be disabled.

During the upgrade, disabled snapshot schedules from version 2.0 are deleted.

Internal subnet

The internal (interconnect) subnet

can be changed from a Class C

subnet during or after deployment.

The internal subnet must be a Class C subnet.

Before upgrading, the internal subnet must be changed to a Class C subnet, otherwise the service pack installation will fail with the following message:

“Please allocate a new C-class subnet for

FluidFS Internal Network, run the following

command, and then repeat the upgrade: system

networking subnets add NEWINTER Primary

255.255.255.0 -PrivateIPs x.y.z.1,x.y.z.2

(where x.y.z.* is the new subnet)”.

Note: If you receive this message while attempting to

upgrade, obtain a Class C subnet that is not used in your network, run the command to set the internal subnet (for example: system networking subnets add NEWINTER Primary 255.255.255.0 –PrivateIPs 172.41.64.1, 172.41.64.2 ), and retry the service pack installation.

Port for management and remote KVM

Only subnet‐level isolation of

management traffic is supported.

The following features are available:

Physical isolation of management traffic

Remote KVM that allows you to view and manage the NAS controller console remotely over a network

These features are implemented using the Ethernet port located on the lower right side of the back panel of a NAS controller.

1GbE to 10GbE client connectivity upgrade

Version 2.0 does not support

upgrading an appliance from 1GbE client connectivity to 10GbE client connectivity.

Version 3.0 introduces support for upgrading an appliance from 1GbE client connectivity to

10GbE client connectivity. Upgrades must be performed by a Dell installer or certified business partner.