Embed Size (px)
Citation preview
Isilon OneFS and IsilonSD EdgeVersion 8.1.0
Technical Specifications Guide
May 2017
This section contains the following topics:
l About this guide......................................................................................................2l IsilonSD Edge requirements.................................................................................... 2l Isilon scale-out NAS overview.................................................................................2l Where to go for support......................................................................................... 2l Documentation resources....................................................................................... 3l Protocol guidelines................................................................................................. 3l File system guidelines............................................................................................ 11l Authentication, identity management, and access (AIMA) control guidelines........17l OneFS software module guidelines........................................................................19l Networking guidelines...........................................................................................26l Hardware guidelines..............................................................................................27
About this guideThis document presents guidelines and recommendations for configuring OneFS andIsilonSD Edge. Configuration guidelines are provided for protocols, file systemfeatures, software and hardware components, and network settings.
Your suggestions help us to improve the accuracy, organization, and overall quality ofthe documentation. Send your feedback to https://www.research.net/s/isi-docfeedback. If you cannot provide feedback through the URL, send an email messageto [email protected].
IsilonSD Edge requirementsIsilonSD Edge 8.1.0 is compatible with Management Server versions 1.0.0, 1.0.1, and1.0.2. To use IsilonSD Edge with (ESRS) and ESXi 6.0, Management Server 1.0.2 isrequired.
For information about IsilonSD Edge—including installation, administration, andtroubleshooting guides—see the IsilonSD Edge - Isilon Info Hub.
Isilon scale-out NAS overviewThe Isilon scale-out NAS storage platform combines modular hardware with unifiedsoftware to harness unstructured data. Powered by the OneFS operating system, acluster delivers a scalable pool of storage with a global namespace.
The unified software platform provides centralized web-based and command-lineadministration to manage the following features:
l A cluster that runs a distributed file system
l Scale-out nodes that add capacity and performance
l Storage options that manage files and tiering
l Flexible data protection and high availability
l Software modules that control costs and optimize resources
Where to go for supportThis topic contains resources for getting answers to questions about Isilon products.
Online support l Live Chat
l Create a Service Request
For questions about accessing online support, send an email to [email protected].
Telephonesupport
l United States: 1-800-SVC-4EMC (1-800-782-4362)
l Canada: 1-800-543-4782
l Worldwide: 1-508-497-7901
l Local phone numbers for a specific country are available at EMC Customer Support Centers.
2 Isilon OneFS and IsilonSD Edge 8.1.0
IsilonCommunityNetwork
The Isilon Community Network connects you to a central hub ofinformation and experts to help you maximize your current storagesolution. From this site, you can demo Isilon products, askquestions, view technical videos, and get our latest Isilon productdocumentation.
Isilon Info Hubs For the list of Isilon info hubs, see the Isilon Info Hubs page on theIsilon Community Network. Use these info hubs to find productdocumentation, troubleshooting guides, videos, blogs, and otherinformation resources about the Isilon products and features you'reinterested in.
Support for IsilonSD EdgeIf you are running a free version of IsilonSD Edge, support is available through theIsilon Community Network. If you purchased one or more IsilonSD Edge licenses,support is available through Isilon Technical Support, provided you have a validsupport contract for the product.
Documentation resourcesSee the following Dell EMC Isilon info hubs for links to important OneFSdocumentation and resources:
l Isilon Info Hubs (complete list of Isilon info hubs)
l OneFS 8.1.0 Documentation - Isilon Info Hub
l IsilonSD Edge - Isilon Info Hub
You can also search for documentation and knowledge base articles on the OnlineSupport website.
Protocol guidelinesThis section presents guidelines for configuring protocols for OneFS.
Table 1 OneFS protocol specifications
Item OneFS 8.1.0 IsilonSD Edge Description
FTP connections per node 200 200 The recommended limit forFTP connections per node.This number is the testedlimit. If the number of FTPconnections to a nodeexceeds the recommendedlimit, FTP performance mightbe negatively affected. Thelimit for FTP connections pernode assumes anonymousaccess that requires noauthentication.
HDFS block size 64 MB - 512 MB 64 MB - 512 MB The recommended range forHDFS block sizes. For bestresults, the block size should
Technical Specifications Guide
Documentation resources 3
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
not be smaller than 4 KB orlarger than 1 GB. The specificvalue varies by workflow.Smaller block sizes requiremore tasks; however, youwant a large enough numberof tasks to take advantage ofall the slots on the cluster.
HDFS root directory 1 per access zone 1 per access zone The number of HDFS rootdirectories per access zonethat OneFS supports. Thislimitation for access zonesand authentication providersis the same for HDFS andother protocols.
HDFS threads per node 256 256 The maximum number ofactive HDFS threads pernode. The threads are sharedbetween NameNode andDataNode.
HTTP connections per node 500 500 The limit for HTTPconnections per node. OneFSruns version 2 of the ApacheHTTP Server (httpd), whichincludes the Apache Multi-Processing Module (MPM)that implements a hybridmulti-process, multi-threadedserver. The Apache MPMconfiguration limits thenumber of simultaneousconnections that OneFSservices.
OneFS queues connectionsafter the connection limit isreached and processes themas resources becomeavailable.
Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
4 Isilon OneFS and IsilonSD Edge 8.1.0
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
NDMP block size 512 KB 512 KB The size limit for tape blocks.If you back up tape blocksthat are larger than the sizelimit, OneFS will back up 256KB blocks.
NDMP connections per node 64 64 The limit for the number ofNDMP connections that areallowed per node.
NFS exports per cluster 40,000 40,000 The recommended limit forNFS exports per cluster.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
NFS max read size 1 MB 1 MB The limit for NFS read size, orrsize, for NFS3 and NFS4.When you mount NFS exportsfrom a cluster, a larger readsize for remote procedurecalls can improve throughput.The default read size inOneFS is 128 KB.
An NFS client uses the largestsupported size by default. Asa result, avoid setting the sizeon your clients. Setting thevalue too low on a clientoverrides the default valueand can undermineperformance.
NFS max write size 1 MB 1 MB The limit for NFS write size,or wsize, or NFS3 and NFS4.When you mount NFS exportsfrom a cluster, a larger writesize for remote procedurecalls can improve throughput.The default write size inOneFS is 512 KB.
An NFS client uses the largestsupported size by default. As
Technical Specifications Guide
Protocol guidelines 5
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
a result, avoid setting the sizeon your clients. Setting thevalue too low on a clientoverrides the default valueand can undermineperformance.
NFS threads Dynamic Dynamic The limit for NFS threads isdetermined by the number ofcores in the node.
NFS3 connections per node 1,000 active connections 250 active connections The recommended limit foractive NFS3 connections. Themaximum has not beenestablished; however, thenumber of available TCPsockets can limit the numberof NFS connections.
The number of connectionsthat a node can processdepends on the ratio ofactive-to-idle connectionsand on the resources that areavailable to process thesessions.
Monitoring the number ofNFS connections to eachnode helps preventoverloading a node withconnections.
NFS4 connections per node 1,000 active connections 250 active connections The recommended limit foractive and passive NFS4connections. The maximumhas not been established;however, the number ofavailable TCP sockets canlimit the number of NFSconnections.
The number of connectionsthat a node can processdepends on the ratio ofactive-to-idle connectionsand on the resources that areavailable to process thesessions.
Monitoring the number ofNFS connections to eachnode helps prevent
6 Isilon OneFS and IsilonSD Edge 8.1.0
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
overloading a node withconnections.
NFS4 state IDs Unlimited Unlimited State IDs for NFS4 are limitedby the amount of memorythat is available in the nodes.If sufficient memory isavailable, state IDs should notrun out. In the currentimplementation, the state IDis per target IP.
PAPI connections 20 connections (total) forclusters with 3–10 nodes
22–78 connections (2connections per node) forclusters with 11–39 nodes
80 connections (total) forclusters with 40 or morenodes
20 connections (total) forclusters with 3–10 nodes
22–78 connections (2connections per node) forclusters with 11–39 nodes
80 connections (total) forclusters with 40 or morenodes
The limit for the process poolfor the PAPI daemon. Thislimit scales automaticallybased on the size of thecluster.
RAN attribute key length 200 B 200 B The limit of the key length forthe OneFS extended userattribute (x-isi-ifs-attr-<name>).
RAN attribute value length 1 KB 1 KB The limit of the value lengthfor the OneFS extended userattribute (x-isi-ifs-attr-<name>).
Maximum RAN concurrentconnections per node
50 (default)
300 (custom)
50 (default)
300 (custom)
The limit of RAN concurrentconnections per node usingdefault parameters.
You can obtain higherscalability for RAN by usingnon-default configurationparameters. The maximumlimit depends on manyparameters and can bespecific to a clustersworkflow. Contact your DellEMC Isilon account team or for help configuring the non-default parameters. For moreinformation, see the Isilonknowledge base article304701, How to update RANscalability parameters(restricted).
Technical Specifications Guide
Protocol guidelines 7
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
RAN URI length 8 KB 8 KB The limit for the URI lengththat is used for the RANHTTP operation.
RAN user attributes 126 126 The limit for extended userattributes that OneFSsupports.
SMB share names 80 characters 80 characters The limit for the length ofSMB share names. Sharenames must include onlyalphanumeric characters,hyphens, and spaces.
SMB shares per cluster 80,000 20,000 The recommended limit forSMB shares per cluster.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
SMB 1 connections per node 1,000 1,000 The number of SMB 1connections that a node canprocess depends on the typeof node and whether theconnections are active or idle.The more CPUs and RAMthat a node has, the moreactive connections the nodecan process.
The kernel imposes memoryconstraints on the OneFSprotocol daemons, such asthe input-output daemon(lwio), and these constraintslimit the number of SMB 1connections.
SMB 1 request size 64 KB 64 KB The request size limit isdetermined by the SMB 1protocol.
SMB 2 connections per node 3,000 active connections
27,000 idle connections
350 active connections The number of active SMB 2connections that a node canprocess depends on the typeof node. The more CPUs and
8 Isilon OneFS and IsilonSD Edge 8.1.0
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
RAM that a node has, themore active connections thenode can process.
The kernel imposes memoryconstraints on the OneFSprotocol daemons, such asthe input-output daemon(lwio), and these constraintslimit the number of SMB 2connections.
To ensure that a node doesnot become overloaded withconnections, you shouldmonitor the number of SMB 2connections to each node.
SMB2 credits per client 1,024 1,024 Per client means per node,per client. The serverprovides this number of SMB2 credits for any client thatconnects to a node.
SMB 2 credits per cluster 100,000 100,000 The recommended limit forSMB 2 credits per cluster.The maximum number of SMB2 credits per cluster has notbeen established. Exceedingthis recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
SMB 2 request size 1 MB 1 MB OneFS supports the large 1MB maximum transmissionunit (MTU) that wasintroduced by SMB2.1. TheMTU is the size of the largestdata unit that the SMBprotocol can transmit andreceive. The large MTU canimprove the overallthroughput of SMBtransmissions.
Technical Specifications Guide
Protocol guidelines 9
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
Microsoft Windows 7 andWindows 2008 clients requirea registry change to turn onlarge MTU support. MicrosoftWindows 8 and Windows 2012clients support the large MTUby default.
SMB 3 connections per node 3,000 active connections
27,000 idle connections
350 active connections The number of active SMB 3connections that a node canprocess depends on the typeof node. The more CPUs andRAM that a node has, themore active connections thenode can process.
The kernel imposes memoryconstraints on the OneFSprotocol daemons, such asthe input-output daemon(lwio), and these constraintslimit the number of SMB 3connections.
To ensure that a node doesnot become overloaded withconnections, you shouldmonitor the number of SMB 3connections to each node.
SSH connections per node 200 200 The recommended limit forSSH connections per node.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support. Themaximum number of SSHconnections per node has notbeen established.
SWIFT connections per node 150 150 The SWIFT limit depends onthe memory pattern ofconcurrent GET/PUTconnections and is capped at512 MB of memory. Becausememory use varies by
10 Isilon OneFS and IsilonSD Edge 8.1.0
Table 1 OneFS protocol specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
process, lower connectionnumbers are possible.
SWIFT objects per container 10,000 10,000 The number of objects thatcan be listed in a containerGET or HEAD request.
File system guidelinesThis section presents guidelines for configuring the OneFS file system.
Table 2 OneFS file system specifications
Item OneFS 8.1.0 IsilonSD Edge Description
Block size 8 KB 8 KB The maximum block size limit.This limit cannot be changed.
Cluster name length 40 characters 40 characters The maximum length for thecluster name.
Cluster size 144 nodes 6 nodes The maximum number ofnodes that a cluster can have.
Custom access patterntemplates
5 5 The limit for custom file-system-tunable templates.This limit is in addition to thedefault templates of"random," "streaming," and"default."
Directories per directory 100,000 100,000 The recommended limit forthe number of directories in adirectory. Exceeding thisrecommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
Directory depth 509 509 The recommended limit fordirectory depths. Directorydepth is determined by themaximum path length.Exceeding this recommendedlimit might negatively affectthe cluster performance and
Technical Specifications Guide
File system guidelines 11
Table 2 OneFS file system specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
client connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
Disk pools 40 40 The recommended limit forthe number of disk pools. Thenumber of disk pools in thecluster is limited by themaximum number of nodepools in the cluster and thetype of nodes in those nodepools. For information aboutdisk pools, node pools, andtiers, see the white paper Next-Generation StorageTiering with EMC IsilonSmartPools. Exceeding thisrecommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
FEC protection 4 4 The following FEC options aresupported: +1n, +2n, +2d:1n,+3d:1n, +3d:1n1d, +3n, +4d:1n,+4d:2n, +4n.
OneFS protection is definedat the node pool level. Acluster with multiple nodepools can have multipleprotection schemessimultaneously. Forinformation about disk pools,node pools, and tiers, see thewhite paper Next-GenerationStorage Tiering with EMCIsilon SmartPools.
Mirrored protection 8x (maximum) 8x (maximum) Mirroring options from 2x to8x are supported. The
12 Isilon OneFS and IsilonSD Edge 8.1.0
Table 2 OneFS file system specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
recommended value dependson the cluster size.
File clones per file 32,766 32,766 The maximum number ofreferences for a single blockin a shadow store. When thelimit for file clones per file isexceeded, a new shadowstore is created .
File name length 255 bytes 255 bytes Most Unicode characterencodings, such as UTF-8,specify that a character canhave multiple bytes. UTF-8can have up to 4 bytes percharacter. As a result, the255 bytes in a file name canrange from 63 characters to255 characters. Thecharacters in some languages,such as Japanese, are likely tohave multiple bytes percharacter. OneFS supportsUTF-8 by default,
File size 4 TB 4 TB The maximum size for a file.Files larger than 1 TB cannegatively affect job engineperformance .
File system size 66 PB 36 TB The maximum capacity forthe file system.
The capacity size does notinclude overhead for theOneFS operating system, thefile system, or dataprotection.
Files per directory 1,000,000 1,000,000 The recommended limit forfiles per directory. Exceedingthis recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
Technical Specifications Guide
File system guidelines 13
Table 2 OneFS file system specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
To improve performancewhen managing largenumbers of files in a singledirectory, use nodes thathave solid-state drives(SSDs).
Hard links per file 1,000 1,000 The default and maximumnumber of hard links per file.You can set the maximumnumber of hard links per filewith theefs.ifm.max_linkssystem control. Setting thenumber higher than thedefault value can slowsnapshot operations and filedeletions. For moreinformation, see the EMCIsilon knowledge base article447064, OneFS: Sysctl:efs.ifm.max_links.
Inodes per cluster Billions Billions OneFS dynamically allocatesnew inodes from free filesystem blocks. The maximumnumber of possible inodesdepends on the number anddensity of nodes in thecluster, as expressed by thefollowing formulas:
l 4Kn drives: ((number ofnodes in the cluster) *(node raw TB) * 1000^4* .99) / (8192 * (numberof inode mirrors))
l 512n drives: ((number ofnodes in the cluster) *(node raw TB) * 1000^4* .73) / (512 * (numberof inode mirrors))
See the guideline for files perdirectory. The limit for filesper directory can limit thenumber of files that thesystem can store.
Logical Node Numbers(LNNs)
144 144 The limit for logical nodenumbers.
14 Isilon OneFS and IsilonSD Edge 8.1.0
Table 2 OneFS file system specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
Node pools per cluster 10 1 The recommended andmaximum limits for node poolsper cluster. The number ofnode pools that can becreated is limited by thenumber of nodes in thecluster.
Open files per node 315,000 315,000 The maximum number of openfiles per node depends on themaximum number of vnodesthat are available on the node.The amount of availablevnodes depends on how muchRAM the node has. Themaximum number of openfiles per node is 90% of themaximum number of vnodeson that node, as expressed inthe following formula:
kern.maxfiles =kern.maxvnodes * .9
The OneFS protocoldaemons, such as the input-output daemon (lwio), mightimpose additional constraintson the number of files that anode can have open. Theprotocol daemons typicallyimpose such constraintsbecause the kernel placeslimits on per-process memoryconsumption.
Path length 1,023 bytes 1,023 bytes The maximum length for apathname. The length is themaximum length of adirectory path that can bepassed into a system call; itdoes not represent theabsolute depth of nesteddirectories.
Shorter path and file namesrequire fewer lookupoperations. As a bestpractice, keep your path andfile names as short aspossible, especially inworkflows that include manylookups. NDMP cannot back
Technical Specifications Guide
File system guidelines 15
Table 2 OneFS file system specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
up files that have a pathlength greater than themaximum limit.
Device IDs 65,535 65,535 Device IDs are uniqueidentifiers for nodes. DeviceIDs are not reused whennodes are replaced. To reachthe limit of Device IDs in athree-node cluster, you mustreplace nodes 65,532 times.
User attribute keys 16 16 The limit of attribute keysthat can be created withinany file system object.
The user attribute term refersto custom file systemmetadata that the FreeBSDextattr API creates. Theseextended attribute data typescan be acted on bySmartPools, for example, bychoosing the FileAttribute file pool policy
filter. Extended attributesexist as "name=value" pairswithin a file system object.
User attribute key size 24 bytes 24 bytes The limit size for the userattribute key.
User attribute value size 128 bytes 128 bytes The limit size for the userattribute value.
User attribute total size 1 KB 1 KB The limit for the size of thecustom metadata that isassociated with the filesystem object.
16 Isilon OneFS and IsilonSD Edge 8.1.0
Authentication, identity management, and access (AIMA)control guidelines
This section presents guidelines for configuring directory services and OneFS accesszones.
Table 3 OneFS AIMA specifications
Item OneFS 8.1.0 IsilonSD Edge Description
Access zones 50 50 The recommended limit foraccess zones. Exceeding thisrecommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support. Themaximum limit has not beenestablished.
ACEs per ACL 1,000 1,000 The limit for Access ControlEntries (ACEs) per AccessControl List (ACL). ACEs arestored and evaluated linearly.Large numbers of ACEs perACLs increase the number ofauthorization checks thatmust be performed, whichmight negatively affectsystem performance.
Kerberos token size 64 KB 64 KB The size limit for the Kerberostoken.
LDAP domains 50 50 The recommended limit forLightweight Directory AccessProtocol (LDAP) domains.This guideline representsunique LDAP domains. Seethe entry for access zones.
Local groups (per cluster) 25,000 25,000 The recommended limit forlocal groups per cluster.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determine
Technical Specifications Guide
Authentication, identity management, and access (AIMA) control guidelines 17
Table 3 OneFS AIMA specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
the value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
Local users (per cluster) 25,000 25,000 The recommended limit forlocal users per cluster.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
Microsoft Active Directorydomains
50 50 The recommended limit forActive Directory domains. Seethe entry for access zones.
NIS domains 50 50 The recommended limit forNetwork Information Service(NIS) domains. The guidelinerepresents unique NISdomains. See the entry foraccess zones. Although youcan specify multiple NISdomains in an access zone,NFS users benefit only fromthe NIS configuration that isdefined in the system accesszone.
RBAC roles 200 200 The recommended limit forrole-based access control(RBAC) roles. Exceeding thisrecommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support. Themaximum limit has not beenestablished.
18 Isilon OneFS and IsilonSD Edge 8.1.0
Table 3 OneFS AIMA specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
User mapper rules 1,000 1,000 The recommended limit foruser mapper rules. Exceedingthis recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support. Themaximum limit has not beenestablished.
OneFS software module guidelinesThis section presents guidelines for configuring OneFS software modules.
Table 4 OneFS software module specifications
Item OneFS 8.1.0 IsilonSD Edge Description
Antivirus: file size 2 GB 2 GB The recommended file sizelimit for antivirus scans.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determinethe value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
Audit: CEE servers 1 (max) audit server per node144 (max) audit servers percluster
1 (max) audit server per node144 (max) audit servers percluster
OneFS must ping all theCommon Event Enabler(CEE) servers within a singleheartbeat window. Thenumber of servers that can becontacted and that canrespond during the window isestimated to be 144. Thenetwork topology and clusterbandwidth might require alower limit.
Technical Specifications Guide
OneFS software module guidelines 19
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
Audit: Events forwarded toCEE
4500 events per second 4500 events per second The sustained number of auditevents, per second, that canbe forwarded to a CEE server.This limit might be higher insome circumstances,depending on the workload,the type of node, and the CEEserver configuration.
Audit: log expiration Never Never Log files are kept indefinitely.Monitor the size and quantityof the log files on the cluster.If space on the cluster islimited, delete or move the logfiles.
Audit: log file size 1 GB 1 GB The size limit for a log file.When a log file reaches themaximum size, the log file isclosed and a new log file iscreated. Monitor the size andquantity of the log files on thecluster. If space on thecluster is limited, delete ormove the log files.
CloudPools: account name 768 characters 768 characters The maximum length for aCloudPool account name.
CloudPools: account username
Limit is set by serviceprovider
Limit is set by serviceprovider
The maximum length for aCloudPool account username. This limit is set by theservice provider. Check withyour cloud provider for moreinformation.
CloudPools: accountpassword
255 characters 255 characters The maximum length for aCloudPool account password.
CloudPools: pool name 768 characters 768 characters The maximum length for aCloudPool name
CloudPools: vendor name 2048 characters 2048 characters The maximum length for aCloudPool vendor name.
CloudPools: description 4096 characters 4096 characters The maximum length for aCloudPool description.
CloudPools: accounts to tierto
256 accounts 256 accounts
30 active accounts
The maximum number ofaccounts that a CloudPoolaccount can tier to. Thenumber of accounts that canbe active is limited by themaximum number of file poolpolicies.
20 Isilon OneFS and IsilonSD Edge 8.1.0
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
CloudPools: containers incloud
Limit is set by serviceprovider
Limit is set by serviceprovider
The maximum number ofcontainers in the cloud. Thislimit is set by the serviceprovider. Check with yourcloud provider for moreinformation.
CloudPools: cloud containersize
Limit is set by serviceprovider
Limit is set by serviceprovider
The size of the cloudcontainer. This limit is set bythe service provider. Checkwith your cloud provider formore information.
CloudPools: storage size perCloudPool account
Limit is set by serviceprovider
Limit is set by serviceprovider
The storage size for aCloudPool account. This limitis set by the service provider.Check with your cloudprovider for more information.
CloudPools: file size tiered tocloud
4 TB 1 TB The size of files that can bearchived to the cloud andretrieved from the cloud. Thislimit is set by the serviceprovider. Check with yourcloud provider for moreinformation.
CloudPools: proxy limits Proxy name: 1024 characters
Proxy hostname: 1024characters
Proxy username: 1024characters
Proxy password: 256characters
Proxy name: 1024 characters
Proxy hostname: 1024characters
Proxy username: 1024characters
Proxy password: 256characters
The maximum lengths for aCloudPool proxy name,hostname, username, andpassword.
File pool policies: AND and ORconditions
3 ORs and 5 ANDs 3 ORs and 5 ANDs A file pool policy can have 3OR disjunctions, and eachterm joined by the ORs cancontain at most 5 ANDs. Forexample: (A and B and C andD and E) or (F and G and Hand I and J) or (K and L and Mand N and O).
File pool policies: number offile pool policies per cluster
30 30 The recommended limit forfile policies per cluster.Exceeding this recommendedlimit might negatively affectthe cluster performance andclient connections. Evaluatethe workflow and workloadsfor your cluster to determine
Technical Specifications Guide
OneFS software module guidelines 21
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
the value that works best foryour environment. Forassistance, contact your Isilonaccount representative orIsilon Technical Support.
InsightIQ 3.0 and later:monitored clusters
8 clusters 8 clusters The number of clusters thatInsightIQ 3.0 and later canmonitor. If you are running adifferent version of InsightIQ,see the release notes for theversion of InsightIQ that youare running. For moreinformation about InsightIQ,see the InsightIQ - Isilon InfoHub.
InsightIQ 3.0 and later:monitored nodes
80 nodes for one cluster; 150nodes for multiple clusters
80 nodes for one cluster; 150nodes for multiple clusters
The number of nodes for onecluster or multiple clustersthat InsightIQ 3.0 and latercan monitor. If you arerunning a different version ofInsightIQ, see the releasenotes for the version ofInsightIQ that you arerunning. For more informationabout InsightIQ, see the InsightIQ - Isilon Info Hub.
Job Engine: concurrent jobs 3 3 The number of concurrentjobs that the Job Engine canrun. The limit does not includejobs for striping or marking;one job from each of thosecategories can also runconcurrently. For moreinformation, see the Isilon JobEngine white paper.
SmartDedupe: block size 8 KB 8 KB SmartDedupe works on filesystem blocks that are 8 KB.
SmartDedupe: maximumpaths per policy
10 10 The recommended limit forpaths per policy forSmartDedupe. Exceeding thisrecommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,
22 Isilon OneFS and IsilonSD Edge 8.1.0
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
contact your Isilon accountrepresentative or IsilonTechnical Support.
SmartDedupe: minimum filesize
32 KB 32 KB The minimum file size thatSmartDedupe can process.SmartDedupe will not de-duplicate files that are smallerthan 32 KB.
SmartDedupe: shadow stores 32,000 32,000 Each shadow store can have32,000 pointers. This limit isimposed by the kernel. TheOneFS shadow store is ametadata structure thatreferences physical blocks todecrease the physical storagethat is required to store data,which maximizes storageefficiency.
SmartPools: Tiers 5 5 The recommended limit forSmartPools tiers. Exceedingthis recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
SmartQuotas: directory depth 509 509 The recommended limit fordirectory depths forSmartQuotas. Directorydepth is determined by themaximum path length, whichis 1,023 characters. Directorydepths deeper than 275directories might negativelyaffect system performance.
SmartQuotas: number ofquotas per cluster
20,000 10,000 The recommended limit forquotas per cluster. If you havemore than 20,000 quotas, youshould use the command-lineinterface to administer them.The maximum number ofquotas per cluster has notbeen established. Exceeding
Technical Specifications Guide
OneFS software module guidelines 23
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
this recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
SnapshotIQ: directory depth 509 509 The recommended limit fordirectory depths forSnapshotIQ. Directory depthis determined by themaximum path length, whichis 1,023 characters. Depthsdeeper than 275 directoriesmight negatively affect thecluster performance.
SnapshotIQ: number ofsnapshots
20,000 20,000 The limit for snapshots percluster.
SyncIQ: defined policies 1,000 1,000 The recommended limit fordefined SyncIQ policies. Themaximum limit of definedpolicies has not beenestablished. If the number ofpolicies exceeds therecommended limit, youshould keep in mind thefollowing effects:
l SyncIQ is bound by thelimit on the number ofconcurrently runningpolicies. If many policiesare running on schedules,the queue to run the jobsmight become so largethat OneFS can nevercomplete all the jobs inthe queue.
l Each policy represents aset of snapshots on thesource and thedestination clusters. Moresnapshots mean thatmore jobs must run todelete the snapshots, andthe increase in the
24 Isilon OneFS and IsilonSD Edge 8.1.0
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
number of jobs cannegatively affect thecluster performance.
SyncIQ: running policies 50 - for clusters with 4 ormore nodes OR 4 * number ofCPU cores per cluster - forclusters with 3 or fewer nodes
50 - for clusters with 4 ormore nodes OR 4 * number ofCPU cores per cluster - forclusters with 3 or fewer nodes
The recommended limit ofrunning SyncIQ policies. Forclusters with 3 or fewernodes, the limit depends onthe number of CPU cores pernode. There can be oneworker per CPU core, witheach worker running 4policies. The recommendedlimit for smaller clusters is: 4* number of CPU cores percluster. Exceeding thisrecommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
SyncIQ: workers per node(policy setting)
3 3 The recommended limit forworkers per node. Exceedingthis recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,contact your Isilon accountrepresentative or IsilonTechnical Support.
SyncIQ: workers per policy 40 40 The recommended limit forworkers per policy. Exceedingthis recommended limit mightnegatively affect the clusterperformance and clientconnections. Evaluate theworkflow and workloads foryour cluster to determine thevalue that works best for yourenvironment. For assistance,
Technical Specifications Guide
OneFS software module guidelines 25
Table 4 OneFS software module specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
contact your Isilon accountrepresentative or IsilonTechnical Support.
Networking guidelinesThis section presents guidelines for OneFS networking configurations.
Table 5 OneFS networking specifications
Item OneFS 8.1.0 IsilonSD Edge Description
Default routes per node 1 1 The limit for default routesper node. OneFS does notsupport default routes perinterface.
DNS configurations percluster
1 per groupnet 1 per groupnet The recommended limit forDNS configurations percluster. In OneFS, you canspecify multiple DNS resolverconfigurations with a limit ofone DNS resolverconfiguration per groupnet.You can have as manygroupnets as there are accesszones.
DNS name servers perconfiguration
3 3 The limit for DNS nameservers per configuration.
Groupnets 1 per access zone 1 per access zone The limit for groupnets peraccess zone. Groupnets areoptional and should be usedonly if the access zonerequires an alternate DNSserver. The number of accesszones should not exceed 50.
DNS search suffixes perconfiguration
6 6 The limit for DNS searchsuffixes per configuration.
Network pools per cluster 100 100 The recommended limit fornetwork pools per cluster.The maximum limit has notbeen established. The numberof network pools should bekept under 100 pools acrossall subnets and groupnets inthe cluster
SmartConnect DNS zonenames
100 100 The limit for SmartConnectDNS zone names per cluster.
26 Isilon OneFS and IsilonSD Edge 8.1.0
Table 5 OneFS networking specifications (continued)
Item OneFS 8.1.0 IsilonSD Edge Description
See the "Network pools percluster" entry for moreinformation.
SmartConnect DNS zonename aliases
100 100 The recommended limit forSmartConnect DNS zonename aliases. The maximumlimit has not been established.The number of DNS zonename aliases should be keptunder 100 in the cluster.
Subnets per cluster 100 100 The limit for subnets percluster.
VLANs per cluster 100 100 The limit for VLANs percluster.
Hardware guidelinesThis section presents guidelines for Isilon hardware configurations.
Table 6 OneFS hardware specifications
Item OneFS 8.1.0 IsilonSD Edge Description
Backup accelerator: tapedevice paths
4 4 The limit for device paths perbackup accelerator node.
InfiniBand cable length Varies by node type Not supported Older nodes (S200, X200,X400, and NL400) use DDRIB cables and support lengthsup to 10 meters. Newer nodes(S210, X210, NL410, andHD400) use QDR IB cablesand support lengths up to 100meters.
Technical Specifications Guide
Hardware guidelines 27
Copyright © 2017 Dell Inc. or its subsidiaries All rights reserved.
Published May 2017
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH
RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION
REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
28 Isilon OneFS and IsilonSD Edge 8.1.0
