DELL Technologies VMAX All

Flash
250F/250FX/450F/450FX/850F/850F
X/950F/950FX
Simple Support Matrix
March 25, 2024

Copyright © 2022 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, and other
trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.
Host Servers/ Adapters: All host systems are supported where the host vendor allows the host/OS/adapter combination. All Fibre Channel HBAs branded as Emulex , or QLogic with line speeds 8 Gb/s, 16 Gb/s or 32
Gb/s, including vendor rebranded versions of the same are supported. AIX and HP-UX vendor branded HBAs, also support the 4Gb/s FC link speed. 10 or 25 GbE Cisco, Emulex, or QLogic CNAs (10GbE, 25GbE,
iSCSI, FCoE via FC-gateway), including vendor rebranded versions of the same are supported. 10 or 25 GbE NICs for iSCSI connectivity as supported by the server and OS vendor are supported.
Following allowances for Firmware/BIOS, Drivers, and for specific Platforms: Any Dell or vendor-supplied firmware/BIOS that meets the ESM minimum version for specified OS platform are allowed (Newer versions of
the Firmware/BIOS higher than the minimum version are allowed). For Solaris, HP-UX and AIX platforms, Dell only supports the Driver/Firmware/BIOS versions supplied by the OS Vendor. For CNA (HBA) drivers refer
to ELN, https://elabnavigator.dell.com, for supported versions. For Linux Drivers not listed in the ESM refer to the ‘Linux Out of Kernel Drivers Support (LoS)’. If systems meet these criteria, no further ELN connectivity
validation or RPQ is required.
Switches:
• Visit https://elabnavigator.dell.com/ Simple Support Matrices (Storage) Switch Support for supported switch models and associated switch firmware revisions
• For Dell Switch interoperability, all associated Switch Firmware Revisions, Switch Management Software and other interop settings; See Advanced Query Wizard: Category/Switch/Sub-Category/All Switched Fabric
Topology Parameters Table.
• All Dell approved FCoE and iSCSI switches are supported as IP stand-alone ethernet switches.

Operating Environment: PowerMax OS 5978.144.144, 5978.221.221, 5978.444.444, 5978.479.479, 5978.669.669 & 5978.711.711 (VMAX All Flash only) HYPERMAX OS 5977.1131.1131, 5977.1125.1125,

5977.952.892, 5977.945.890, 5977.814.786, 5977.813.785, 5977.811.784 & 5977.691.684. Service Pack 5560 is required for HYPERMAX OS 5977.691.684 to support the VMAX All Flash arrays.

Note: 5977.811.784 has been replaced with the Q2`16 SR release 5977.813.785. Version 5977.811.784 can still be used for new installs only, and can be downloaded from https://support.emc.com/. For complete
details please refer to Salesforce KB: 482212.

Director Bits: Director Bit Setting for VMAX3 & VMAX All Flash: https://elabnavigator.dell.com/vault/pdf/VMAX_All_Flash_VMAX3_Dir_Bit_ESSM.pdf

Note: Table 2 contains VMAX ALL Flash and VMAX3 for eNAS Operating Environment 8.1.4 Configuration Guidelines.

Note: The information in this ESSM is a configuration summary. The versions listed in the columns represent versions that work with the listed Platform/Operating Systems
and Storage Array. Versions listed in the columns for each specific Platform/Operation System may not be interoperable. For more detailed information, refer to the Advanced
Query section on the ELN home page at https://elabnavigator.dell.com.

Dell® E-LabTM qualified versions for Dell VMAXTM All Flash/VMAX3

No. Platform Support Dell PowerPath® Native MPIO & DMP Solutions Enabler (5977)
1 Canonical Ubuntu 16.04LTS Ubuntu DM-MPIO
2 Citrix Systems Inc. Citrix Hypervisor [x86_64] 8.2 DM-MPIO
3 HPE HP-UX 11i v3 (HP-UX 11.31) DMP , HP PV Links , 10.0, 10.1, 8.2.0 (EOSL),
HP-UX Native MPIO 8.3.0 (EOSL), 8.4.0, 9.0.0
(EOSL), 9.1.0 (EOSL), 9.2
4 HPE OpenVMS V8.3-1H1 VMS Native 8.4.0, 9.0.0 (EOSL), 9.1.0
Multipathing (EOSL), 9.2
5 HPE OpenVMS V8.4 VMS Native 8.2.0 (EOSL), 8.3.0 (EOSL),
Multipathing 8.4.0, 9.0.0 (EOSL), 9.1.0
(EOSL), 9.2
6 IBM AIX 7.2 7.0 P03 AIX-MPIO , DMP 10.0, 10.1, 8.2.0 (EOSL),
8.3.0 (EOSL), 8.4.0, 9.0.0
(EOSL), 9.1.0 (EOSL), 9.2
7 IBM AIX 7.3 7.0 P03 AIX-MPIO
8 IBM IBM i 7.1,IBM IBM i 7.2,IBM IBM i 7.3 Native IBMIOS 10.0, 10.1, 9.1.0 (EOSL), 9.2
9 IBM IBM i 7.4,IBM IBM i 7.5 Native IBMIOS
10 IBM IBM i i6.1.1 10.0, 10.1, 9.1.0 (EOSL), 9.2
11 IBM VIOS 3.1.0.0,IBM VIOS 3.1.0.10,IBM VIOS 3.1.0.11,IBM VIOS 3.1.0.20,IBM VIOS 3.1.0.21,IBM VIOS 7.0 P03 AIX-MPIO
3.1.0.30,IBM VIOS 3.1.0.40,IBM VIOS 3.1.0.50,IBM VIOS 3.1.0.60,IBM VIOS 3.1.1.0,IBM VIOS 3.1.1.10,IBM VIOS
3.1.1.20,IBM VIOS 3.1.1.21,IBM VIOS 3.1.1.25,IBM VIOS 3.1.1.30,IBM VIOS 3.1.1.40,IBM VIOS 3.1.1.50,IBM VIOS
3.1.1.60,IBM VIOS 3.1.2.0,IBM VIOS 3.1.2.10,IBM VIOS 3.1.2.20,IBM VIOS 3.1.2.21,IBM VIOS 3.1.2.30,IBM VIOS
3.1.2.40,IBM VIOS 3.1.3.0,IBM VIOS 3.1.3.10,IBM VIOS 3.1.3.14,IBM VIOS 3.1.3.21,IBM VIOS 3.1.4.0,IBM VIOS
3.1.4.10
12 IBM z/OS 2.3 z/OS Native 10.0, 8.1, 8.2, 8.3, 8.4, 8.5
Multipathing
13 IBM z/OS 2.4 z/OS Native 10.0, 8.2, 8.3, 8.4, 8.5
Multipathing
14 IBM z/OS 2.5 z/OS Native 10.0, 8.5
Multipathing
15 IBM z/OS 3.1 z/OS Native
Multipathing
16 IBM z/VM 7.2 z/VM Native
Multipathing
17 Microsoft Windows Server 2016 7.1 - 8.0 DMP , MPIO 10.0, 10.1, 8.4.0, 9.0.0
Framework [default (EOSL), 9.1.0 (EOSL), 9.2
DSM]
18 Microsoft Windows Server 2019 7.1 - 8.0 DMP , MPIO 10.0, 10.1, 9.1.0 (EOSL), 9.2
Framework [default
DSM]
19 Microsoft Windows Server 2022 7.1 - 8.0 DMP , MPIO 10.1
Framework [default
DSM]
20 Oracle Linux OL 7.x [x86_64] OL7U5 and above support R5U2[4.14.35-1902] 7.0 - 7.4 DM-MPIO
21 Oracle Linux OL 7.x [x86_64] OL7U5 and above support R5U3[4.14.35-1902.30*],Oracle Linux OL 7.x [x86_64] 7.1 - 7.4 DM-MPIO
OL7U5 and above support R5U4[4.14.35-2025.40*],Oracle Linux OL 7.x [x86_64] OL7U5 and above support
R5U5[4.14.35-2047.500]
22 Oracle Linux OL 7.x [x86_64] OL7U7 and above support R6U1[5.4.17-2036] 7.2 - 8.0 P01 DM-MPIO
23 Oracle Linux OL 7.x [x86_64] OL7U7 and above support R6U2[5.4.17-2102] 7.2 - 8.1 DM-MPIO
24 Oracle Linux OL 7.x [x86_64] OL7U7 and above support R6U3[5.4.17-2136] 7.4 - 8.2 DM-MPIO
25 Oracle Linux OL 7.x [x86_64] OL7U7 and above support R6[5.4.17-2011] 7.2 - 7.4 DM-MPIO
26 Oracle Linux OL 7.x [x86_64] UEK R3 U6 [3.8.13-98] (EOSL),Red Hat RHEL [IBM Power] 6.0,Red Hat RHEL [s390x- DM-MPIO 10.0, 10.1, 8.2.0 (EOSL),
64-Bit] 6.3,Red Hat RHEL [s390x-64-Bit] 6.5,Red Hat RHEL [s390x-64-Bit] 6.6,Red Hat RHEL [s390x-64-Bit] 6.7,Red 8.3.0 (EOSL), 8.4.0, 9.0.0
Hat RHEL [s390x-64-Bit] 7.0,Red Hat RHEL [s390x-64-Bit] 7.1,Red Hat RHEL [x86_64] 6.0 (EOL),SUSE SLES (EOSL), 9.1.0 (EOSL), 9.2
[s390x-64-Bit] 12,SUSE SLES [s390x-64-Bit] 12 SP1
27 Oracle Linux OL 8.x [x86_64] OL8U1 and above support R6 [5.4.17-2011] 7.2 - 7.4 DM-MPIO
28 Oracle Linux OL 8.x [x86_64] OL8U1 and above support R6U1[5.4.17-2036] 7.2 - 8.0 P01 DM-MPIO
29 Oracle Linux OL 8.x [x86_64] OL8U1 and above support R6U2[5.4.17-2102] 7.2 - 8.1 DM-MPIO
30 Oracle Linux OL 8.x [x86_64] OL8U1 and above support R6U3[5.4.17-2136] 7.4 - 8.2 DM-MPIO
31 Oracle Linux OL 8.x [x86_64] OL8U5 and above support R7U1[5.15.0-10*] 8.1 - 8.2 DM-MPIO
32 Oracle Linux OL 8.x [x86_64] OL8U5 and above support R7U2[5.15.0-20*] 8.2 DM-MPIO
33 Oracle Linux OL 8.x [x86_64] OL8U5 and above support R7[5.15.0-0] 7.5 - 8.2 DM-MPIO
34 Oracle Linux OL 9.x [x86_64] R7U1 [5.15.0-10*] 8.1 - 8.2 DM-MPIO
35 Oracle Linux OL 9.x [x86_64] R7U2 [5.15.0-20*] 8.2 DM-MPIO
36 Oracle Linux OL 9.x [x86_64] R7[5.15.0-0] 7.5 - 8.2 DM-MPIO
37 Oracle OVM 3.3.4,Oracle OVM 3.3.5,Oracle OVM 3.4.1,Oracle OVM 3.4.2,Oracle OVM 3.4.3,Oracle OVM DM-MPIO
3.4.4,Oracle OVM 3.4.5,Oracle OVM 3.4.6
38 Oracle Solaris 10 SPARC,Oracle Solaris 10 x86 DMP , MPxIO 8.2.0 (EOSL), 8.3.0 (EOSL),
8.4.0, 9.0.0 (EOSL), 9.1.0
(EOSL)
 No. Platform Support Dell PowerPath® Native MPIO & DMP Solutions Enabler (5977)
39 Oracle Solaris 11 SPARC,Oracle Solaris 11 x86,Oracle Solaris 11.1 SPARC,Oracle Solaris 11.1 x86,Oracle Solaris 5.5 P06 - 6.0 P03 DMP , MPxIO 8.2.0 (EOSL), 8.3.0 (EOSL),
11.2 SPARC,Oracle Solaris 11.2 x86 8.4.0, 9.0.0 (EOSL), 9.1.0
(EOSL), 9.2
40 Oracle Solaris 11.3 SPARC,Oracle Solaris 11.3 x86 5.5 P06 - 6.0 P04 DMP , MPxIO 8.3.0 (EOSL), 8.4.0, 9.0.0
(EOSL), 9.1.0 (EOSL), 9.2
41 Oracle Solaris 11.4 SPARC 6.0 P04 DMP , MPxIO
42 Oracle Solaris 11.4 x86 6.0 P04 MPxIO
43 Red Hat RHEL [32-Bit] 6.0,Red Hat RHEL [32-Bit] 6.1,Red Hat RHEL [32-Bit] 6.2,Red Hat RHEL [32-Bit] 6.3,Red Hat DM-MPIO
RHEL [32-Bit] 6.4,Red Hat RHEL [32-Bit] 6.5
44 Red Hat RHEL [s390x-64-Bit] 6.10 DM-MPIO
45 Red Hat RHEL [s390x-64-Bit] 6.9,Red Hat RHEL [s390x-64-Bit] 7.4,SUSE SLES [s390x-64-Bit] 12 SP3 DM-MPIO 10.0, 10.1, 9.0.0 (EOSL),
9.1.0 (EOSL), 9.2
46 Red Hat RHEL [s390x-64-Bit] 7.3,SUSE SLES [s390x-64-Bit] 12 SP2 DM-MPIO 10.0, 10.1, 8.4.0, 9.0.0
(EOSL), 9.1.0 (EOSL), 9.2
47 Red Hat RHEL [s390x-64-Bit] 7.5,Red Hat RHEL [s390x-64-Bit] 7.6,Red Hat RHEL [s390x-64-Bit] 7.8,Red Hat RHEL DM-MPIO
[s390x-64-Bit] 8.0,Red Hat RHEL [s390x-64-Bit] 8.1,Red Hat RHEL [s390x-64-Bit] 8.2
48 Red Hat RHEL [x86_64] 6.1 (EOL),Red Hat RHEL [x86_64] 6.2 (EOL),Red Hat RHEL [x86_64] 6.3 (EOL),Red Hat DM-MPIO , DMP 10.0, 10.1, 8.2.0 (EOSL),
RHEL [x86_64] 6.4 (EOL),Red Hat RHEL [x86_64] 6.5 (EOL),Red Hat RHEL [x86_64] 6.6 (EOL),Red Hat RHEL 8.3.0 (EOSL), 8.4.0, 9.0.0
[x86_64] 6.7 (EOL),Red Hat RHEL [x86_64] 6.8 (EOL) (EOSL), 9.1.0 (EOSL), 9.2
49 Red Hat RHEL [x86_64] 6.10 (EOL) 7.0 - 7.2 DM-MPIO , DMP 10.0, 10.1, 9.1.0 (EOSL), 9.2
50 Red Hat RHEL [x86_64] 6.9 (EOL) 7.0 - 7.2 DM-MPIO , DMP 10.0, 10.1, 8.4.0, 9.0.0
(EOSL), 9.1.0 (EOSL), 9.2
51 Red Hat RHEL [x86_64] 7.0,Red Hat RHEL [x86_64] 7.1 DM-MPIO , DMP 8.2.0 (EOSL), 8.3.0 (EOSL),
8.4.0, 9.0.0 (EOSL), 9.1.0
(EOSL), 9.2
52 Red Hat RHEL [x86_64] 7.2 7.0 - 7.3 DM-MPIO , DMP 8.2.0 (EOSL), 8.3.0 (EOSL),
8.4.0, 9.0.0 (EOSL), 9.1.0
(EOSL), 9.2
53 Red Hat RHEL [x86_64] 7.3,Red Hat RHEL [x86_64] 7.4 7.0 - 7.3 DM-MPIO , DMP 8.4.0, 9.0.0 (EOSL), 9.1.0
(EOSL), 9.2
54 Red Hat RHEL [x86_64] 7.5 7.0 - 7.3 DM-MPIO , DMP 9.0.0 (EOSL), 9.1.0 (EOSL),
9.2
55 Red Hat RHEL [x86_64] 7.6 7.0 - 7.3 DM-MPIO , DMP 9.1.0 (EOSL), 9.2
56 Red Hat RHEL [x86_64] 7.7 7.0 - 7.3 DM-MPIO , DMP 9.2
57 Red Hat RHEL [x86_64] 7.8 7.1 P02 - 7.4 DM-MPIO , DMP 9.2
58 Red Hat RHEL [x86_64] 7.9 7.2 - 8.2 DM-MPIO , DMP 10.0, 10.1, 9.2
59 Red Hat RHEL [x86_64] 8.0 7.0 - 7.4 DM-MPIO , DMP 10.0, 10.1, 9.2
60 Red Hat RHEL [x86_64] 8.1 7.1 - 7.4 DM-MPIO , DMP 10.0, 10.1, 9.2
61 Red Hat RHEL [x86_64] 8.2 7.2 - 7.4 DM-MPIO , DMP 10.0, 10.1, 9.2
62 Red Hat RHEL [x86_64] 8.3 7.2 - 7.5 DM-MPIO 10.0, 10.1, 9.2
63 Red Hat RHEL [x86_64] 8.4 7.3 SP1 - 8.0 P01 DM-MPIO , DMP 10.0, 10.1, 9.2
64 Red Hat RHEL [x86_64] 8.5 7.4 - 8.0 P01 DM-MPIO , DMP 10.0, 10.1, 9.2
65 Red Hat RHEL [x86_64] 8.6,Red Hat RHEL [x86_64] 9.0 7.5 - 8.2 DM-MPIO , DMP 10.0, 10.1
66 Red Hat RHEL [x86_64] 8.7 8.0 - 8.2 DM-MPIO , DMP 10.0, 10.1
67 Red Hat RHEL [x86_64] 8.8 8.0 - 8.2 DM-MPIO , DMP 10.1
68 Red Hat RHEL [x86_64] 8.9 8.2 DM-MPIO , DMP
69 Red Hat RHEL [x86_64] 9.1 8.0 - 8.2 DM-MPIO 10.1
70 Red Hat RHEL [x86_64] 9.2 8.1 - 8.2 DM-MPIO , DMP 10.1
71 Red Hat RHEL [x86_64] 9.3 8.2 DM-MPIO
72 SUSE SLES [s390x-64-Bit] 12 SP4,SUSE SLES [s390x-64-bit] 15,SUSE SLES [s390x-64-bit] 15 SP1 DM-MPIO
73 SUSE SLES [x86_64] 12 SP5 7.1 - 8.2 DM-MPIO , DMP 10.0, 10.1, 9.2
74 SUSE SLES [x86_64] 15 SP2 7.2 - 7.3 DM-MPIO 10.0, 10.1, 9.2
75 SUSE SLES [x86_64] 15 SP3 7.3 SP1 - 7.4 DM-MPIO , DMP
76 SUSE SLES [x86_64] 15 SP4 7.5 - 8.2 DM-MPIO 10.1
77 SUSE SLES [x86_64] 15 SP5 8.1 - 8.2 DM-MPIO 10.1
78 VMware ESXi 7.0 (vSphere 7.0) 7.2 - 8.2 NMP
79 VMware ESXi 8.0 (vSphere 8.0) 8.0 - 8.2 NMP
80 VSI OpenVMS 8.4-2L1 VMS Native
Multipathing

Note: The information in this ESSM is a configuration summary. The versions listed in the columns represent versions that work with the listed Platform/Operating Systems
and Storage Array. Versions listed in the columns for each specific Platform/Operation System may not be interoperable. For more detailed information, refer to the Advanced
Query section on the ELN home page at https://elabnavigator.dell.com.
Table 2 VMAX3 and VMAX All Flash for Embedded NAS Operating Environment 8.1.4 Connectivity Guidelines (page 1 of 3)
Guidelines /Specifications MaximumTested Value Comments

CIFS Guidelines
CIFS TCP Connection 64K (default and theoretical• Param tcp.maxStreams sets the maximum number of TCP connections a
max.), 40K (max. tested) DataMover can have. Maximum value is 64K, or 65535. TCP connections
(streams) are shared by other components and should be changed in monitored
small increments.
• With SMB1/SMB2 a TCP connection means single client (machine) connection.
• With SMB3 and multi channel, a single client could use several network
connections for the same session. It will depend on the number of available
interfaces on the client machine, or for high speed interface like 10Gb link, it can
go up to 4 TCP connections per link.
Share name length 80 characters (Unicode) Unicode : The maximum length for a share name with Unicode enabled is 80
characters.
Number of CIFS shares 40,000 per Data Mover Larger number of shares can be created. Maximum tested value is 40K per Data
(Max. tested limit) Mover.
Number of NetBIOS names/ 509 (max) Limited by the number of network interfaces available on the Virtual Data Mover.
compnames per Virtual Data From a local group perspective, the number is limited to 509. NetBIOS and
Mover (VDM) compnames must be associated with at least one unique network interface.
NetBIOS name length 15 NetBIOS names are limited to 15 characters (Microsoft limit) and cannot begin with
an @ (at sign) or a – (dash) character. The name also cannot include white space,
tab characters, or the following g symbols: / \ : ; , = * + | [ ] ? < > . If using compnames,
the NetBIOS form of the name is assigned automatically and is derived from the first
15 characters of the ,comp_name>.
Comment (ASCII chars) for 256 Limited to 256 ASCII characters.
NetBIOS name for server • Restricted Characters: You cannot use double quotation ("), semicolon (;),
accent (`), and comma (,) characters within the body of a comment. Attempting to
use these special characters results in an error message. You can only use an
exclamation point (!) if it is preceded by a single quotation mark (’).
• Default Comments: If you do not explicitly add a comment, the system adds a
default comment of the form EMC-SNAS:T<x.x.x.x> where <x.x.x.x> is the
version of the e NAS software.
Compname length 63bytes For integration with Windows environment releases later than Windows 2000, the
CIFS server computer name length can be up to 21 characters when UTF-8 (3
bytes/ char) is used.
Number of domains 10 tested 509 (theoretical max.) The maximum number of Windows domains a Data Mover can
be a member of. To increase the max default value from 32, change parameter
cifs.lsarpc.maxDomain. The Parameters Guide for VNX for File contains more
detailed information about this parameter.
Block size negotiated 64 KB Maximum buffer size that can be negotiated with Microsoft Windows clients. To
128 KB with SMB2 increase the default value, change param cifs.W95BufSz, cifs.NTBufSz or
cifs.W2KBufSz. The Parameters Guide for VNX for File contains more detailed
information about these parameters.
Note: With SMB2.1, read and write operation supports 1MB buffer (this feature is
named “large MTU”).
Number of simultaneous 127 (SMB1) • For SMB1, value is fixed and defines the number of requests a client is able to
requests per CIFS session 512 (SMB2) send to the Data Mover at the same time (for example, a change notification
(maxMpxCount) request). To increase this value, change the maxMpxCount parameter.
• For SMB2 and newer protocol dialect, this notion has been replaced by ‘credit
number’, which has a max of 512 credit per client but could be adjusted
dynamically by the server depending on the load.
The Parameters Guide for VNX for File contains more detailed information about this
parameter.
Total number files/directories 500,000 A large number of open files could require high memory usage on the Data Mover
opened per Data Mover and potentially lead to out-of-memory issues.
Number of Home Directories 20,000 (Maximum possible A configuration file containing Home Directories info is read completely at each user
supported limit; not recommended) connection, recommendation is to not exceed a few thousands for easy
management.
Number of Windows/UNIX 40,000 (Limited by the Earlier versions of the NAS Software relied on a basic database, nameDB, to
users connected at the same number of TCP connections) maintain Usermapper and secmap mapping information. DBMS now replaces the
time basic database. This solves the inode consumption issue and provides better
consistency and recoverability with the support of database transactions. It also
provides better atomicity, isolation, and durability in database management.
Number of users per TCP 64k To decrease the default value, change param cifs.listBlocks (default 255; max 255).
connection The value of this parameter times 256 = max number of users.
Note: TID/FID/UID shares this parameter and cannot be changed individually for
each ID. Use caution when increasing this value as it could lead to an out-of-memory
condition. Refer to the Parameters Guide for VNX for File for parameter information.
Number of files/directories 64k To decrease the default value, change param cifs.listBlocks (default 255; max 255).
opened per CIFS connection The value of this parameter times 256 = max number of files/directories opened per
in SMB1 CIFS connection.
Note: TID/FID/UID shares this parameter and cannot be changed individually for
each ID. Use caution when increasing this value as it could lead to an out-of-
memory condition. Be sure to follow the recommendation for total number of
files/directories opened per Data Mover. Refer to the System Parameters Guide for
VNX for File for parameter information.
Table 2 VMAX3 and VMAX All Flash for Embedded NAS Operating Environment 8.1.4 Connectivity Guidelines (page 2 of 3)
Guidelines /Specifications MaximumTested Value Comments

CIFS Guidelines (Continued)

Number of files/directories 127 k To decrease the default value, change parameter cifs.smb2.listBlocks (default 511;
opened per CIFS connection max 511). The value of this parameter times 256 = max number of files/directories
in SMB2 opened per CIFS connection.
Number of VDMs per Data 128 Total number of VDMs, file systems, and checkpoints across the entire system
Mover cannot exceed 2048.
FileMover

Max connections to 1024

secondary storage per
primary (VNX for File) file
system
Number of HTTP threads for 64 Number of threads available for recalling data from secondary storage is half the
servicing FileMover API number of whichever is the lower of CIFS or NFS threads. 16 (default), can be
requests per Data Mover increased using server_http command, max (tested) is 64.
File System Guidelines

Mount point name length 255 bytes ( ASCII) The "/" is used when creating the mount point and is equal to one character. If
exceeded, Error 4105: Server_x:path_name: invalid path specified is returned.
File system name length 240 bytes (ASCII) For nas_fs list, the name of a file systemwill be truncated if it is more than 19
19 chars display for list characters. To display the full file system name, use the –info option with a file system
option ID (nas_fs -i id=<fsid>).
Filename length 255 bytes (NFS) • With Unicode enabled in an NFS environment, the number of characters that can
255 characters (CIFS) be stored depends on the client encoding type such as latin-1. For example: With
Unicode enabled, a Japanese UTF-8 character may require three bytes.
• With Unicode enabled in a CIFS environment, the maximum number of
characters is 255. For filenames shared between NFS and CIFS, CIFS allows
255 characters. NFS truncates these names when they are more than 255 bytes
in UTF-8, and manages the file successfully.
Pathname length 1,024bytes Note: Make sure the final path length of restored files is less than 1024 bytes. For
example, if a file is backed up which originally had path name of 900 bytes, and it is
restoring to a path with 400 bytes, the final path length would be 1300 bytes and
would not be restored.
Directory name length 255bytes This is a hard limit and is rejected on creation if over the 255 limit.The limit is bytes
for UNIX names, Unicode characters for CIFS.
Subdirectories (per parent 64,000 This is a hard limit, code will prevent you from creating more than 64,000
directory) directories.
Number of file systems per 4096 This max number includes VDM and checkpoint file systems.
eNAS system
Number of file systems per 2048 The mount operation will fail when the number of file systems reaches 2048 with an
Data Mover error indicating maximum number of file systems reached. This maximum number
includes VDM and checkpoint file systems.
Maximum disk volume size Dependent on RAID group eNAS systems — For eNAS systems, users might configure LUNs greater than 2
(see comments) TB up to 16 TB or max size of the RAID group, whichever is less. This is supported
for eNAS systems when attached to VMAX3 arrays.
Total storage for a Data 256 TB (raw) • On a per-Data-Mover basis, the total size of all file systems, and the size of all
Mover SavVols used by SnapSure, must be less than the total supported capacity.
Exceeding these limit can cause out of memory panic.
• Refer to the eNAS file capacity limits table for more information.
File Size 16 TB This hard limit is enforced and cannot be exceeded.
Number of directories Same as the number of inodes in a file system. Each 8 KB of space = 1 inode.
supported per file system
Number of files per directory 500,000 Exceeding this number will cause performance problems.
Maximum number of files and 256 million (default) This is the total number of files and directories that can be in a single eNAS file
directories per VNX file system.
system This number can be increased to 4 billion at file system creation time, but should only
be done after considering recovery and restore time and the total storage utilized per
file. The actual maximum number in a given file system is dependent on a number of
factors including the size of the file system.
Maximum amount of 256 TB When quotas are enabled with file size policy, the maximum amount of deduplicated
deduplicated data supported data supported is 256 TB. This amount includes other files owned by UID 0 or GID.
All other industry-standard caveats, restrictions, policies, and best practices prevail. This includes, but is not limited to, fsck times (now made faster
through multi-threading), backup and restore times, number of objects per file system, snapshots, file system replication, VDM replication,
performance, availability, extend times, and layout policies. Proper planning and preparation should occur prior to implementing these guidelines.
Naming Service Guidelines
Number of DNS domains 3 - WebUI Three DNS servers per Data Mover is the limit if using WebUI. There is no limit
unlimited – CLI when using the command line interface (CLI).
Number of NIS Servers per 10 You can configure up to 10 NIS servers in a single NIS domain on a Data Mover.
Data Mover
NIS record capacity 1004 bytes A Data Mover can read 1004 bytes of data from a NIS record.

Number of DNS servers per 3

DNS 3 domain

Table 2 VMAX3 and VMAX All Flash for Embedded NAS Operating Environment 8.1.4 Connectivity Guidelines (page 3 of 3)
Guidelines /Specifications MaximumTested Value Comments

NFS Guidelines

Number of NFS exports 2,048 per Data Mover tested You might notice a performance impact when managing a large number of exports
Unlimited theoretical max using Unisphere.
Number of concurrent NFS 64K with TCP (theoretical) Limited by TCP connections.
clients Unlimited with UDP
theoretical)
Netgroup line size 16383 The maximum line length that the Data Mover will accept in the local netgroup file
on the Data Mover or the netgroup map in the NIS domain that the Data Mover is
bound to.
Number of UNIX groups 64k 2 billion max value of any GID. The maximum number of GIDs is 64K, but an
supported individual GID can have an ID n the range of 0- 2147483648.
Networking Guidelines

Link aggregation/ether 8 ports (ether channel) Ether channel: the number of ports used must be a power of 2 (2, 4, or 8). Link
channel 12 ports (link aggregation aggregation: any number of ports can be used. All ports must be the same speed.
LACP) Mixing different NIC types (that is copper and fibre) is not recommended.
Number of VLANs supported 4094 IEEE Standard
Number of interfaces per 45 tested Theoretically 509.
Data Mover
Number of FTP connections Theoretical value 64K By default the value is (in theory) 0xFFFF, but it is also limited by the number of
TCP streams that can be opened. To increase the default value, change param
tcp.maxStreams (set to 0x00000800 by default). If you increase it to 64K before
you start TCP, you will not be able to increase the number of FTP connections.
Refer to the Parameters Guide for VNX for File for parameter information.
Quotas Guidelines

Number of tree quotas 8191 Per file system

Max size of tree quotas 256 TB Includes file size and quota tree size
Max number of unique 64k Per File system
groups
Quota path length 1024

eNAS Replication for File

Number of replication 682 (eNAS)

sessions per eNAS
Max number of replication 1024 This enforced limit includes all configured file system, VDM, and copy sessions.
sessions per Data Mover
Max number of local and 682
remote file system and VDM
replication sessions per Data
Mover
Max number of loopback file 341
system and VDM replication
sessions per Data Mover
Snapsure Guidelines

Number of checkpoints per 96read-only Up to 96 read-only checkpoints per file system are supported as well as 16 write-
file system 16write-able able checkpoints.
On systems with Unicode enabled, a character might require between 1 and 3 bytes, depending on encoding type or character used. For
example, a Japanese character typically uses3 bytes in UTF-8. ASCII characters require 1 byte.
NAS for VMAX All Flash and VMAX3

eNAS eNAS eNAS eNAS eNAS

VMAX 100K VMAX 200K VMAX 400K VMAX 450F/ VMAX 850F/
450 FX 850 FX
Usable IP Storage capacity per Data Mover (all disk 256 TB 512 TB 512 TB 256 TB 256 TB
types/uses)
Number of Data Movers 2 2 or 4 2, 4, 6, or 8 2 or 4 2 or 4
Max FS Size 16 TB 16 TB 16 TB 16 TB 16 TB
Max # of FS per Data Mover a 2048 2048 2048 2048 2048
Max # of FS per system 4096 4096 4096 4096 4096
Max configured replications sessions per Data Mover for 1024 1024 1024 1024 1024
Replication for File b
Max # of checkpoints per Primary File System 96 96 96 96 96
Max # of NDMP sessions per Data Mover 4 8 8 8 8
Memory per Data Mover 6 GB 24 GB 24 GB 24 GB 24 GB

a. This count includes production file systems, user-defined file system checkpoints, and two checkpoints for each replication session
b. A maximum of 256 concurrently transferring sessions are supported per Data Mover.