Software Storage Platform Mixing Rules

Transcription

1 ONTAP Software Storage Platform Mixing Rules June _A0 ur005

2

3 Table of Contents 3 Contents ONTAP storage platform mixing rules... 4 Cluster configuration qualifications... 5 Current platform support for homogeneous clusters... 6 Previous platform support for homogeneous clusters... 7 Platform mixing qualifications... 9 Platform mixing rules for the Data ONTAP 8.1 release family... 9 Platform mixing rules for the Data ONTAP 8.2 release family... 9 Platform mixing rules for the Data ONTAP 8.3 release family Platform mixing rules for the ONTAP 9.0 release family Frequently asked questions about platform mixing rules Copyright information Trademark information How to send comments about documentation and receive update notifications Index... 18

4 4 ONTAP storage platform mixing rules When designing and deploying an ONTAP configuration composed of different models of storage controller, there are specific rules concerning the combinations you can use. ONTAP enables you to build and deploy storage systems that can consist of up to 24 nodes and include a combination of different platforms (models) of storage controller. When combining different platforms of storage controller in an ONTAP configuration, you must be aware of the rules for deploying variations. There are numerous conditions that affect your deployment options, including which platform models you can combine, the number of nodes present in each of the platforms, the protocols employed, and which version of ONTAP you have. This document provides information to clarify the variations that you can use. In this document, when a storage system name appears without a prefix (for example, 3270 instead of FAS3270 or V3270), the related content applies to both FAS systems and V-Series systems. Note: The rules detailed in this document remain in compliance with NetApp support. ONTAP does not prevent combinations outside the supported options listed here. If you have any questions about the options provided in this document, contact NetApp customer support or your account team. For detailed information about the latest storage system configuration options, be sure to consult the Hardware Universe. hwu.netapp.com

5 5 Cluster configuration qualifications When deploying an ONTAP system, there are numerous qualifications that can affect the size and type of cluster you build. A cluster can be deployed with a single node and can grow to as many as 24 nodes (12 HA pairs) in NAS configurations. Note: Single-node clusters are supported starting from the clustered Data ONTAP 8.2 release. Every node in a cluster containing two or more nodes must be part of an HA pair, where both nodes in the HA pair are identical storage platform models. SAN-enabled clusters are smaller than NAS-only clusters. The maximum size of a SAN or SAN +NAS cluster is as follows: 8 nodes in ONTAP nodes in Data ONTAP nodes in Data ONTAP nodes in Data ONTAP nodes in Data ONTAP 8.1 FAS6070, FAS6030, FAS3070, FAS3040, FAS2220, and FAS2040 systems do not provide SAN support. The supported protocols for FAS2220 and FAS2040 systems are NFS, SMB, and iscsi. FAS2040 supports FC only in single-node configurations. In ONTAP 9.0 and clustered Data ONTAP 8.3.x: 10 GbE cluster interconnect connections are required for every node in the cluster. All Flash FAS (AFF) nodes can be mixed in a cluster with FAS and V-Series nodes. However, mixing different node types in an HA pair is not allowed. In clustered Data ONTAP 8.2.x: 10 GbE cluster interconnect connections are required for every node in the cluster. FAS2040 systems require a 10 GbE mezzanine card; all 10 GbE ports are used for the cluster network; the data network can use two to four 1 GbE ports; supported protocols are NFS, SMB, and iscsi. V-Series and FlexArray-compatible controllers running clustered Data ONTAP are required to use NetApp disks for the root volume. In clustered Data ONTAP 8.1.x: FAS2040 connects into a cluster using onboard 1 GbE ports. The first 8 ports of the Cisco Nexus 5010 and the first 16 ports of the Cisco Nexus 5020 can be either 1 GbE or 10 GbE, depending on the SFP module used. A 1 GbE SFP is available to enable the FAS2040 system to participate in clusters. All other storage controllers remain at 10 GbE. Best practice is to not mix 1 GbE and 10 GbE nodes.

6 6 Software Storage Platform Mixing Rules A cluster using Cisco Nexus 5010 or 5020 switches for the cluster network can have a maximum of two FAS2040 nodes in the cluster. V-Series controllers running ONTAP are required to use NetApp disks for the root volume. Current platform support for homogeneous clusters There are limits on the maximum number of nodes supported in a homogeneous cluster that consists of current platforms for various ONTAP versions. The following table shows the current platform mixing rules for homogeneous clusters: Current platforms Data ONTAP 8.1.x Data ONTAP 8.2.x Data ONTAP 8.3.x and ONTAP 9.0 Maximum cluster nodes supported AFF AFF AFF and AFF FAS FAS FAS and FAS , and 6290 Not supported Not supported SAN and NAS 5 24 (8 for SAN) 1 Not supported SAN and NAS 5 SAN and NAS SAN and NAS SAN and NAS SAN and NAS and 3250 SAN and NAS SAN and NAS SAN and NAS 8 1 FAS and Not supported SAN and NAS SAN and NAS 8 FAS FAS2520 5,6,8 Not supported SAN and NAS SAN and NAS 4 5 FAS (NFS, CIFS, iscsi, and FCP ) FAS (NFS, CIFS, and iscsi ) SAN and NAS SAN and NAS SAN and NAS 4 4 NAS only SAN and NAS SAN and NAS 4 4 Note: 1 Clusters with nodes using any block protocol are limited to eight nodes with Data ONTAP 8.2 or 8.3, six nodes with Data ONTAP 8.1.1, and four nodes with Data ONTAP The maximum number of nodes within a cluster is determined by the platform that supports the fewest number of nodes. 3 The FAS2240 supports FC only in single-node configurations with clustered Data ONTAP 8.2 or 8.3. Single-node FAS2240 clusters running clustered Data ONTAP 8.2 or 8.3 support an 8 GB Fibre Channel mezzanine card. FAS2240 systems in a multinode configuration require a 10 GbE card in the mezzanine slot. 4 Clusters of FAS22xx controllers using internal drives should be limited to two nodes to allow nondisruptive controller hardware upgrades using DataMotion for Volumes.

7 Cluster configuration qualifications 7 5 The FAS2520 supports cluster sizes up to four nodes with the X1989-R6 Cisco Nexus 5596T switch.. Without the X1989-R6 switch, the cluster size for the FAS2520 is limited to two nodes The X1989-R6 Cisco Nexus 5596T switch includes 32 10GBaseT (RJ-45) ports and 16 SFP+ ports. The X1989-R6 supports up to four FAS2520 nodes, or a combination of two FAS2520 nodes and two entry or mid-range nodes. 6 The FAS2520 and FAS2220 only support iscsi for SAN and do not support FC or FCoE. 7 Data ONTAP RC2 or later is required for the FAS8020, FAS8040 and FAS8060 platforms. 8 Data ONTAP RC1 or later is required for the FAS2520, FAS2552, and FAS2554 platforms. 9 Data ONTAP or later is required for the FAS8080 platform. 10 Data ONTAP 8.3 or later is required for the AFF8020, AFF8040, AFF8060, and AFF8080 platforms. Previous platform support for homogeneous clusters There are certain limits on the maximum number of nodes supported in a homogeneous cluster consisting of previous platforms. The following table shows the previous platform mixing rules for homogeneous clusters: Previous platform Data ONTAP 8.1.x Data ONTAP 8.2.x Data ONTAP 8.3.x and ONTAP 9.0 Maximum cluster nodes and SAN and NAS SAN and NAS SAN and NAS SAN and NAS SAN and NAS Not supported and 3270 SAN and NAS SAN and NAS SAN and NAS SAN and NAS SAN and NAS Not supported SAN and NAS SAN and NAS SAN and NAS SAN and NAS SAN and NAS Not supported and SAN and NAS SAN and NAS Not supported SAN and NAS SAN and NAS Not supported NAS only Not supported Not supported NAS only Not supported Not supported NAS only Not supported Not supported 4 FAS2040 and 3040 NAS only Not supported Not supported 2 Note: 1 Clusters used for SAN are limited to eight nodes with Data ONTAP 8.2 or 8.3, six nodes with Data ONTAP 8.1.1, and four nodes with Data ONTAP 8.1.

8 8 Software Storage Platform Mixing Rules 2 The maximum number of nodes within a cluster is determined by the platform that supports the fewest number of nodes. 3 Third-party array LUNs are not supported for 3140, 3160, 3170, 6240, and 6280 V-Series platforms. These models are supported only with NetApp storage.

9 9 Platform mixing qualifications When deploying an ONTAP system that consists of different models of storage controller, there are specific qualifications that can affect the size and type of system you build. Both controllers in an HA pair must be the same platform model. As a result, two-node clusters always use the same platform. Beyond the requirement that the same platform be used in an HA pair, clusters containing four or more nodes can be built using HA pairs of different platform models. In general, platforms that have a maximum cluster size of four nodes can coexist with other platforms that have a maximum cluster size of four or eight nodes, but not with those having a maximum cluster size of 24 nodes. Similarly, platforms that have a maximum cluster size of 24 nodes can coexist with other platforms that have a maximum cluster size of eight or 24 nodes, but not with those having a maximum cluster size of four nodes. Exceptions are the FAS8020 and AFF8020 platforms, which have a maximum cluster size of 24 and can also coexist with those platforms that have a maximum size of four or eight nodes. For example, a cluster can consist of an HA pair of FAS2240 systems and an HA pair of FAS3250 systems, or an HA pair of FAS3250 systems and an HA pair of FAS6290 systems. However, a cluster cannot consist of an HA pair of FAS2240 systems and an HA pair of FAS6290 systems. Platform mixing rules for the Data ONTAP 8.1 release family There are certain limits on the maximum number of nodes supported on the platform models that can coexist in clusters running Data ONTAP in the 8.1 release family. The following table shows the platform models with the maximum number of supported nodes that can coexist in the same cluster: FAS2220, FAS2240, 3070, 3160, 3170, 3210, and , 3250, 3270, 6030, 6040, and , 6080, 6220, 6240, 6250, 6280, 6290 FAS2220, FAS2240, 3070, 3160, 3170, 3210, and , 3250, 3270, 6030, 6040, and No No , 6080, 6220, 6240, 6250, 6280, and 6290 Platform mixing rules for the Data ONTAP 8.2 release family There are certain limits on the maximum number of nodes supported on the platform models that can coexist in clusters running Data ONTAP in the 8.2 release family. The following table shows the platform models with the maximum number of supported nodes that can coexist in the same cluster: Note: For the table to appear as desired, the FAS prefix for the platforms FAS2520, FAS2220, FAS2240, FAS2552, FAS2554, 8020, 8040, 8060 and 8080 are removed.

10 10 Software Storage Platform Mixing Rules and , 3170, 3210, and and , 3250, and and , 6220, 6240, 6250, 6280, and , , and No 4 No No 2220 and , 3170, 3210, and and , 3250, and , and No No No No No No No , 6220, 6240, 6250, 6280, and , , and No No No No No No No No Note: 1 Data ONTAP RC2 or later is required for the 8020, 8040, and 8060 platforms. 2 Data ONTAP RC1 or later is required for the FAS2520, FAS2552, and FAS2554 platforms. 3 Data ONTAP or later is required for the 8080 platform. 4 When combining 6080 with 80xx, the object limits of 80xx series, such as volumes, LIFs, or SVMs might be constrained to what only 6080 supports until 6080 is removed from the cluster.

11 Platform mixing qualifications 11 Platform mixing rules for the Data ONTAP 8.3 release family There are certain limits on the maximum number of nodes supported on the platform models that can coexist in clusters running Data ONTAP in the 8.3 release family. The following table shows the platform models (with the FAS and AFF prefixes removed) with the maximum number of supported nodes that can coexist in the same cluster: Note: For the table to appear as desired, the FAS, V-Series and AFF prefixes are removed. FAS AFF FAS and V-Series No 4 No No 4 No No No 4 No No No 4 No No No 8 No No No No No No No AFF No No No No

12 12 Software Storage Platform Mixing Rules Platform mixing rules for the ONTAP 9.0 release family There are certain limits on the maximum number of nodes supported on the platform models that can coexist in clusters running ONTAP in the 9.0 release family. The following table shows the platform models (without the FAS and AFF prefixes) with the maximum number of supported nodes that can coexist in the same cluster: Note: For the table to appear as desired, the FAS, V-Series and AFF prefixes are removed. FAS AFF FAS and V-Series No 4 No No 4 4 No No No 4 No No No No 8 8 No No No No No AFF No No No No

13 13 Frequently asked questions about platform mixing rules This topic provides answers to common questions about ONTAP platform mixing rules. Are the platform mixing rules guidelines or requirements, and if they are requirements, how are they enforced? Although these rules are not currently enforced in ONTAP, the platform mixing rules are a requirement for all ONTAP systems. Clusters that do not comply with the cluster platform mixing rules are unsupported configurations and are treated as such by NetApp Customer Success Services (CSS). What is the technical basis for these rules? The platform mixing rules enable you to have the best possible experience with ONTAP and are based on technical reasons. In short, as ONTAP has scaled the maximum number of resources supported in a cluster (volumes, Snapshot copies, and more), older platforms cannot be expected to support the same number of resources as newer platforms. If a cluster consists of numerous platform models, how do I determine the maximum number of nodes supported in a cluster? The maximum number of nodes supported in a cluster is determined by the platform that supports the fewest number of nodes. For example, a cluster consisting of a FAS2240 HA pair and a FAS3250 is limited by the FAS2240 node limit, which is four nodes. Similarly, any cluster containing a FAS3220 HA pair cannot exceed eight nodes, even if the other six nodes in the cluster are FAS6290. Are there special considerations when mixing FAS/V 6080 systems in the same cluster with 80xx systems? When combining the 6080 with the 80xx series, the object limits of the 80xx series (such as volumes, LIFs or SVMs) might be constrained to what the 6080 supports until the 6080s are removed from the cluster. Do the platform mixing rules apply equally to FAS and V-Series clusters? Yes. Consult the Interoperability Matrix (IMT) to confirm that the V-Series model is supported. FAS and V-Series models can coexist in the same cluster. Note that certain V-Series models (3140, 3160, 3170, 3140, and 6080) are supported only when they are connected solely to NetApp storage and are not supported when connected to third-party LUNs. mysupport.netapp.com/matrix For which versions of clustered Data ONTAP do these rules apply? These rules apply to clustered Data ONTAP 8.1.x, 8.2.x, and 8.3.x. Does aggregate relocation (ARL) allow you to refresh controllers without increasing the cluster node count? Yes. Aggregate relocation does an in-place upgrade, meaning that the controller being upgraded is removed from the cluster prior to the new controller being brought up in the cluster. During the upgrade, storage failover is disabled on the nodes being upgraded due to the varying controller models and physical disconnection of the HA interconnect.

14 14 Software Storage Platform Mixing Rules Are there performance considerations when using ARL? Aggregate relocation (ARL) occurs quickly (similar to programmatically changing disk ownership) and with little to no impact on storage system performance. If standard sizing practices are followed, headroom should be built into the HA pair configuration to account for failover performance (the general sizing guideline is 50 percent utilization). As with any failover, performance can be affected if insufficient controller resources are available for the workloads. How do I perform simultaneous controller and disk technology refreshes? DataMotion for Volumes is required for upgrades of both the controllers and the storage shelves. You can use aggregate relocation (ARL) to perform the nondisruptive controller upgrade; however, nondisruptive shelf removal is not supported for removing the shelves that are upgraded from the existing storage controllers. The new controllers and shelves need to be joined to the cluster, and then DataMotion for Volumes must be used to migrate the volumes from the existing HA pair to the new HA pair.

15 15 Copyright information Copyright NetApp, Inc. All rights reserved. Printed in the U.S. No part of this document covered by copyright may be reproduced in any form or by any means graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system without prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS (October 1988) and FAR (June 1987).

16 16 Trademark information NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL and other names are trademarks or registered trademarks of NetApp, Inc., in the United States, and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. A current list of NetApp trademarks is available on the web.

17 17 How to send comments about documentation and receive update notifications You can help us to improve the quality of our documentation by sending us your feedback. You can receive automatic notification when production-level (GA/FCS) documentation is initially released or important changes are made to existing production-level documents. If you have suggestions for improving this document, send us your comments by . To help us direct your comments to the correct division, include in the subject line the product name, version, and operating system. If you want to be notified automatically when production-level documentation is released or important changes are made to existing production-level documents, follow Twitter You can also contact us in the following ways: NetApp, Inc., 495 East Java Drive, Sunnyvale, CA U.S. Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888)

18 18 Software Storage Platform Mixing Rules Index C c-dot cluster configurations qualifications for 5 clustered data ontap clustered ontap clusters, homogeneous previous platform mixing rules 7 comments how to send feedback about documentation 17 configurations, cluster qualifications for 5 configurations, ONTAP storage platform mixing rules 4 controllers storage platform mixing rules 4 controllers, storage platform mixing qualifications 9 D documentation how to receive automatic notification of changes to 17 how to send feedback about 17 F FAQ mixing rules 13 platform mixing rules 13 feedback how to send comments about documentation 17 H homogeneous clusters previous platform mixing rules 7 I information how to send feedback about improving documentation 17 L limits platform mixing rules for the Data ONTAP 8.1 platform mixing rules for the Data ONTAP 8.2 M maximum nodes platform mixing rules for the Data ONTAP 8.1 platform mixing rules for the Data ONTAP 8.2 mixing rules FAQ 13 frequently asked questions 13 platform 13 storage platform 4 mixing rules, platform previous platform support for homogenous clusters 7 mixing, platform qualifications 9 models platform mixing rules for the Data ONTAP 8.1 platform mixing rules for the Data ONTAP 8.2 models, storage controller platform mixing qualifications 9 N NAS cluster configurations qualifications for 5 nodes cluster configuration qualifications 5 maximum number supported in homogeneous clusters of previous platforms 7 mixing rules 4 platform mixing qualifications 9 platform mixing rules for the Data ONTAP 8.1 platform mixing rules for the Data ONTAP 8.2 storage platform mixing rules 4 O ONTAP systems platform mixing qualifications 9 P platform mixing previous platform support for homogenous clusters 7 qualifications 9 platform mixing rules clusters running ONTAP in the 9.0 release family 12 for platforms in clusters running the Data ONTAP 8.3 release family 11 for the Data ONTAP 8.1 for the Data ONTAP 8.2 Platform mixing rules on the platform models that can coexist in clusters running Data ONTAP in the 8.3 release family 11 platform models that can coexist clusters running ONTAP in the 9.0 release family 12

19 Index 19 platform support homogeneous clusters 6 platforms cluster configuration qualifications 5 platforms, storage mixing rules 4 R rules platform mixing 11, 12 rules, mixing storage platform 4 rules, platform mixing for the Data ONTAP 8.1 for the Data ONTAP 8.2 previous platform support for homogenous clusters 7 S SAN cluster configurations qualifications for 5 storage controllers platform mixing qualifications 9 storage platforms 4 suggestions how to send feedback about documentation 17 support, previous platform for homogenous clusters 7 supported nodes platform mixing rules for the Data ONTAP 8.1 platform mixing rules for the Data ONTAP 8.2 systems cluster configuration qualifications 5 platform mixing qualifications 9 T Twitter how to receive automatic notification of documentation changes 17