TR-4036: FlexPod Datacenter Technical Specifications
Technical ReportFlexPod Datacenter Technical SpecificationsDavid Klem, Lindsey Street, Melissa Palmer NetAppNovember 2016 TR-4036
TABLE OF CONTENTS1FlexPod Datacenter Architecture . 62FlexPod Platforms . 63FlexPod Rules . 64Supported Versus Validated FlexPod Configurations . 65NetApp Data ONTAP Modes of Operation. 76Cisco Nexus Switching Modes of Operation . 77Minimum Hardware Requirements . 78Minimum Software Requirements . 89Connectivity Requirements . 810 Other Requirements . 911 Optional Features . 911.1 MetroCluster .911.2 FCP SAN Boot Through Cisco MDS .1011.3 FCP SAN Boot with Cisco Nexus .1111.4 FCoE SAN Boot Option .1211.5 iSCSI Boot Option .1312 Cisco Components . 1412.1 Cisco UCS B-Series Chassis Option .1512.2 Cisco UCS B-Series Blade Server Options .1512.3 Cisco UCS C-Series Rack-Mount Server Options .1512.4 Cisco UCS Fabric Interconnect Options .1612.5 Cisco Nexus 5000 Series Switch Options .1612.6 Cisco Nexus 6000 Series Switch Options .1712.7 Cisco Nexus 7000 Series Switch Options .1712.8 Cisco Nexus 9000 Series Switch Options .1712.9 Cisco APIC Options .1812.10Cisco Nexus Fabric Extender Options .1812.11Cisco MDS Options .1812.12Cisco Software Licensing Options .1912.13Cisco Support Licensing Options .1913 NetApp Components . 202FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
13.1 NetApp Storage Controller Options .2013.2 Cluster Interconnect Switch Options .2013.3 NetApp Ethernet Expansion Module Options .2113.4 NetApp Disk Shelf and Disk Drive Options .2113.5 NetApp Software Licensing Options .2213.6 NetApp Support Licensing Options .2214 Power and Cabling Requirements . 2214.1 Power Requirements .2214.2 Minimum Cable Requirements .2415 Technical Specifications and References . 2615.1 Cisco UCS B-Series Blade Server Chassis .2615.2 Cisco UCS B-Series Blade Servers .2615.3 Cisco UCS C-Series Rack-Mount Servers .2815.4 Cisco UCS VIC Adapters for Cisco UCS B-Series Blade Server .2915.5 Cisco UCS Fabric Interconnects .3015.6 Cisco Nexus 5000 Series Switches .3115.7 Cisco Nexus 6000 Series Switches .3215.8 Cisco Nexus 7000 Series Switches .3215.9 Cisco Nexus 9000 Series Switches .3315.10Cisco Application Policy Infrastructure Controller .3415.11Cisco Nexus Fabric Extender Details .3415.12Small Form Factor Pluggable Modules .3515.13NetApp Storage Controllers .3615.14NetApp Ethernet Adapters .3715.15NetApp Disk Shelves .3815.16NetApp Disk Drives .3816 Legacy Equipment . 38Version History . 39LIST OF TABLESTable 1) Cisco UCS B-Series chassis option. .15Table 2) Cisco UCS B-Series blade server options. .15Table 3) Cisco UCS C-Series rack-mount server options.15Table 4) Cisco UCS fabric interconnect options. .16Table 5) Cisco Nexus 5000 Series Switch options. .163FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
Table 6) Cisco Nexus 6000 Series Switch options. .17Table 7) Cisco Nexus 7000 Series Switch options. .17Table 8) Cisco Nexus 9000 Series Switch options. .17Table 9) Cisco APIC sizes. .18Table 10) Cisco Nexus FEX option. .18Table 11) Cisco MDS switches. .18Table 12) Cisco software licensing options. .19Table 13) Cisco support licensing options. .20Table 14) NetApp storage controller options. .20Table 15) Cluster interconnect switch options. .21Table 16) Ethernet expansion module options. .21Table 17) NetApp disk shelf options. .21Table 18) NetApp software licensing options. .22Table 19) NetApp support licensing options. .22Table 20) Required power ports. .23Table 21) Minimum cable requirements. .24Table 22) Cisco UCS B-Series blade server chassis options. .26Table 23) Cisco UCS B-Series blade server options (1). .26Table 24) Cisco UCS B-Series blade server options (2). .27Table 25) Cisco UCS B-Series blade server datasheets. .27Table 26) Cisco UCS C-Series rack-mount server options (1). .28Table 27) Cisco UCS C-Series rack-mount server options (2). .28Table 28) Cisco UCS C-Series rack-mount server datasheets.28Table 29) Cisco UCS VIC adapters (1).29Table 30) Cisco UCS VIC adapters (2).29Table 31) Cisco UCS VIC adapter datasheets. .30Table 32) Cisco UCS 6300 series fabric interconnect options.30Table 33) Cisco UCS 6200 series fabric interconnect options.30Table 34) Cisco UCS fabric interconnect datasheets. .31Table 35) Cisco Nexus 5000 Series Switch options. .31Table 36) Cisco Nexus 5000 Series Switch datasheets. .31Table 37) Cisco Nexus 6000 Series Switch options. .32Table 38) Cisco Nexus 6000 Series Switch datasheets. .32Table 39) Cisco Nexus 7000 Series Switch options (1). .32Table 40) Cisco Nexus 7000 Series Switch options (2). .33Table 41) Cisco Nexus 7000 Series Switch datasheets. .33Table 42) Cisco Nexus 9000 Series Switch options. .33Table 43) Cisco Nexus 9000 Series Switch datasheets. .34Table 44) Cisco APIC technical specifications. .34Table 45) Cisco Nexus 9000 Series Switch datasheets. .354FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
Table 46) Ethernet SFP modules. .35Table 47) FC SFP modules. .35Table 48) FAS8000 series controller options.36Table 49) AFF8000 series controller options. .36Table 50) NetApp FAS2500 series storage controller options. .37Table 51) NetApp 10GbE adapters. .38Table 52) NetApp disk shelves. .38Table 53) Legacy equipment. .38LIST OF FIGURESFigure 1) FlexPod Datacenter with NetApp MetroCluster architecture. .10Figure 2) FlexPod Datacenter with FC with Cisco MDS. .11Figure 3) FC boot scenario. .12Figure 4) FCoE boot scenario. .13Figure 5) iSCSI boot scenario. .145FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
1 FlexPod Datacenter ArchitectureFlexPod is a predesigned, best practice data center architecture that is built on the Cisco UnifiedComputing System (Cisco UCS), the Cisco Nexus family of switches, and NetApp fabric-attachedstorage (FAS) or V-Series systems.FlexPod is a suitable platform for running a variety of virtualization hypervisors as well as bare-metaloperating systems and enterprise workloads. FlexPod delivers not only a baseline configuration but alsothe flexibility to be sized and optimized to accommodate many different use cases and requirements.Note:Before ordering a complete FlexPod configuration, refer to the NetApp FlexPod Solutions pagefor the latest version of these technical specifications.Note:For an overview of FlexPod reference architectures, refer to the FlexPod Solutions Guide.Note:For an overview of FlexPod reference architectures with Cisco Application Centric Infrastructure,refer to the FlexPod Datacenter with ACI Solutions Guide.2 FlexPod PlatformsThere are three FlexPod platforms: FlexPod Datacenter. This platform is a massively scalable virtual data center infrastructure suited forworkload enterprise applications, virtualization, VDI, and public and private cloud. FlexPod Express. This platform is a compact converged infrastructure that is targeted for remoteoffice and edge use cases. FlexPod Express has its own specifications, which are documented in theFlexPod Express Technical Specifications. FlexPod Select. This platform is a purpose-built architecture for high-performance applications, suchas FlexPod Select for high-performance Oracle RAC.This document provides the technical specifications for the FlexPod Datacenter platform.3 FlexPod RulesThe FlexPod design allows a flexible infrastructure that encompasses many different components andsoftware versions.Use the rule sets as a guide for building or assembling a valid FlexPod configuration. The numbers andrules listed in this section are the minimum requirements for FlexPod; they can be expanded in theincluded product families as required for different environments and use cases.4 Supported Versus Validated FlexPod ConfigurationsThe FlexPod architecture is defined by the set of rules described in this document. The hardwarecomponents and software configurations must be supported by the Cisco Hardware Compatibility List(HCL) and the NetApp Interoperability Matrix Tool (IMT).Each Cisco Validated Design (CVD) or NetApp Verified Architecture (NVA) is a possible FlexPodconfiguration. Cisco and NetApp document these configuration combinations and validate them withextensive end-to-end testing. The FlexPod deployments that deviate from these configurations are fullysupported if they follow the guidelines in this document and all of the components are listed as compatiblein the Cisco HCL and NetApp IMT.For example, adding additional storage controllers or UCS servers and upgrading software to newerversions are fully supported if the software, hardware, and configurations meet the guidelines defined inthis document.6FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
5 NetApp Data ONTAP Modes of OperationThe NetApp Data ONTAP operating system is the common operating system that is installed on everyNetApp storage system and is configured to operate as clustered Data ONTAP or in 7-Mode.FlexPod is validated with both modes of operation, with clustered Data ONTAP providing a highlyscalable storage architecture that enables nondisruptive operations, nondisruptive upgrades, and an agiledata infrastructure. For more information about clustered Data ONTAP, refer to NetApp Data ONTAP:Scale-Out Storage to Achieve Nondisruptive Operations.6 Cisco Nexus Switching Modes of OperationA variety of Cisco Nexus products can be used as the switching component of a given FlexPoddeployment. Most of these options leverage the traditional Cisco Nexus OX or NX-OS software. TheCisco Nexus family of switches offers varying capabilities within its product lines. These capabilities aredetailed later in this document.Cisco’s offering in the software-defined networking space is called Application Centric Infrastructure(ACI). The Cisco Nexus product line that supports the ACI mode, also called fabric mode, is the 9300series. These switches can also be deployed in NX-OS or standalone mode.Cisco ACI is targeted at data center deployments that focus on the requirements of a specific application.Applications are instantiated through a series of profiles and contracts that allow for connectivity from thehost or virtual machine all the way through the network to the storage.FlexPod is validated with both modes of operation of the Cisco Nexus switches. For more informationabout the ACI and the NX-OS modes, see the following Cisco pages: Cisco Application Centric Infrastructure Cisco NX-OS Software7 Minimum Hardware RequirementsA FlexPod configuration has minimum hardware requirements including, but not limited to, switches,fabric interconnects, servers, and FAS controllers.You must use Cisco Unified Computing System (Cisco UCS) servers. Both C-Series and B-Series servershave been used in the validated designs. You can choose B-Series servers, which require chassis andblades, or the C-Series servers, which require rack-mount servers. Cisco Nexus Fabric Extenders (FEXs)are optional with C-Series servers.A FlexPod configuration has the following minimum hardware requirements: Two Cisco Nexus switches in a redundant configuration. This configuration can consist of tworedundant switches from the Cisco Nexus 5000, 6000, 7000, or 9000 series. The two switches shouldbe of the same model and be configured in the same mode of operation.Note:If you are deploying an ACI architecture, you must observe the following additionalrequirements: Deploy the Cisco Nexus 9000 series switches in a spine-leaf topology. Use three Cisco Application Policy Infrastructure Controllers (APICs). Two Cisco UCS 6100, 6200, or 6300 series fabric interconnects in a redundant configuration. Cisco UCS servers: 7If the solution uses B-Series servers, one Cisco UCS 5000 B-Series blade chassis plus two CiscoUCS B-Series blade servers plus two 2104, 2204, or 2208 FEX modules.FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
If the solution uses C-Series servers, two Cisco UCS C-Series rack-mount servers.Note: For larger deployments of Cisco UCS C-Series rack-mount servers, a pair of 2232PP FEXmodules may be desirable. However, the 2232PP is not a hardware requirement.Two NetApp FAS controllers in a high-availability (HA) pair configuration.Note: This configuration can consist of products from the NetApp FAS2000, 3000, 6000, or 8000family of controllers. The HA configuration requires two redundant interfaces per controller for data access; theinterfaces can be Fibre Channel over Ethernet (FCoE), Fibre Channel (FC), or 10 GigabitEthernet (10GbE). If the solution uses clustered Data ONTAP, a cluster interconnect topology approved by NetAppis required. For more information, refer to Cluster Management and Interconnect Switches. If the solution uses clustered Data ONTAP, at least two additional 10GbE ports per controller arerequired for data access. For clusters with two nodes, a two-node switchless cluster can be configured. For clusters with more than two nodes, a cluster interconnect is required.One NetApp disk shelf with any supported disk type.8 Minimum Software RequirementsA FlexPod configuration has the following minimum software requirements: NetApp Data ONTAP: 7-Mode requires Data ONTAP 7.3.5 or later, including Data ONTAP 8.x Clustered Data ONTAP requires Data ONTAP 8.1.1 or later Cisco UCS Manager 1.3 or later, including Cisco UCS 2.x For Cisco Nexus 5000 Series Switches, Cisco NX-OS software release 5.0(3)N1(1c) or later,including NX-OS 5.1.x For Cisco Nexus 6000 Series Switches, Cisco NX-OS software release 6.0(2)N2(3) or later For Cisco Nexus 7000 Series Switches: The 4-slot chassis requires Cisco NX-OS software release 6.1(2) or later The 9-slot chassis requires Cisco NX-OS software release 5.2 or later The 10-slot chassis requires Cisco NX-OS software release 4.0 or later The 18-slot chassis requires Cisco NX-OS software release 4.1 or laterFor Cisco Nexus 9000 Series Switches, Cisco NX-OS software release 6.1(2) or laterNote:The software used in a FlexPod configuration must be listed and supported in the NetApp IMT.Some features might require more recent releases of the software than the ones listed.9 Connectivity RequirementsA FlexPod configuration has the following connectivity requirements: The port-channel ports on the NetApp storage controllers must be directly connected to the CiscoNexus 5000, 6000, 7000, or 9000 Series Switches because the Cisco UCS fabric interconnects donot support virtual port channels (vPCs). vPCs are required from the Cisco Nexus 5000, 6000, 7000, or 9000 Series Switches to the NetAppstorage controllers.8FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
The Cisco UCS fabric interconnect appliance ports are recommended only for SAN protocols (FC,FCoE, and iSCSI). FCoE port channels between the fabric interconnects and the Cisco Nexusswitches are recommended for end-to-end FCoE designs. No additional equipment can be placed inline between the core FlexPod components. vPCs are required from the Cisco Nexus 5000, 6000, 7000, or 9000 Series Switches to the fabricinterconnects. FCoE port channels are recommended for end-to-end FCoE designs. Jumbo frame support is recommended to be enabled throughout the environment, but not required. A separate 100MbE/GbE out-of-band management network is required.10 Other RequirementsA FlexPod architecture has the following additional interoperability and support-related requirements: All hardware and software components must be listed and supported on the IMT, the Cisco UCSHCL, and the Cisco UCS Hardware and Software Interoperability Matrix. If V-Series components are used with Data ONTAP 7-Mode, they must be listed and supported in theV-Series/gFiler Gateway Support Matrix. In clustered Data ONTAP 8.2 and later, this feature is calledNetApp FlexArray , and the compatibility information is detailed in the NetApp IMT. Valid support contracts are required for all equipment, including: SMARTnet support for Cisco equipment SupportEdge Premium support for NetApp equipmentFor more information, see the NetApp IMT and the V-Series/gFiler Gateway Support Matrix.11 Optional FeaturesFor FlexPod architectures, NetApp supports several optional components to further enhance FlexPodDatacenter architectures. Optional components are outlined in the following sections.11.1 MetroClusterFlexPod supports the NetApp MetroCluster solution for continuous availability, in either two- or fournode cluster configurations. MetroCluster provides synchronous replication for critical workloads. Itrequires a dual-site configuration connected with Cisco switching. The maximum supported distancebetween the sites is 300km (approximately 186 miles). Figure 1 illustrates the FlexPod Datacenter withNetApp MetroCluster architecture.For additional details and guidance, see the FlexPod Datacenter with NetApp MetroCluster deploymentdocument.9FlexPod Datacenter Technical Specifications 2016 NetApp, Inc. All rights reserved.
Figure 1) FlexPod Datacenter with NetApp MetroCluster architecture.11.2 FCP SAN Boot Through Cisco MDSTo provide increased scalability by using a dedicated SAN network, FlexPod supports Fibre ChannelProtocol (FCP) through the Cisco MDS switches. The FCP SAN Boot option through Cisco MDS has thefollowing licensing and hardware requirements: A minimum of two FC ports per NetApp storage controller; one port
Each Cisco Validated Design (CVD) or NetApp Verified Architecture (NVA) is a possible FlexPod configuration. Cisco and NetApp document these configuration combinations and validate them with extensive end-to-end testing. The FlexPod dep
Deviations based on customer requirements from a given CVD or NVA are permitted if these variations do not create an unsupported configuration. The FlexPod program includes two solutions: FlexPod Express and FlexPod Datacenter. FlexPod Express. Offers customers an entry-level solution with technologies from
Flexpod: Cisco NetApp was ist ein Flexpod? Flexpod ist eine gemeinsame Architektur (CVD / NVA) Flexpod ist lösungsortientiert Die Flexpod Architektur ist vollständig dokumentiert: Design Guide Sizing Guide Wiring diagrams Bill of Materials Deployment Guide und, und, und
FlexPod Datacenter with VMware vSphere 6.5, NetApp AFF A-Series and Fibre Channel Deployment Guide for FlexPod Datacenter with Fibre Chan-nel SAN and VMware vSphere 6.5 and ONTAP 9.1 Last Updated: August 30, 2018
FlexPod configuration is racked, powered, and cabled per the instructions in the FlexPod Datacenter with Fibre Channel Storage using VMware vSphere 6.5 Update 1, NetApp AFF A-series and Cisco UCS Manager 3.2 CVD. Cisco Nexus switch configuration A fault- tolerant pair of Cisco Nexus 9300
FLEXPOD ERFOLGREICH 10 JAHRE FLEXPOD 100 CVDS ABER 700 MANUELLE TASKS 4 ELEMENT MANAGER HIGH SKILLED ENGINEERS WERDEN BENÖTIGT CVD: FlexPod Datacenter with
(WANs) [24, 26, 27]. WAN traffic shares the datacenter network with intra-datacenter traffic, with the ratio of datacenter to WAN traffic typically around 5:1 [42]. Despite the small fraction of WAN traffic, we find that its impact on datacenter traffic is significant when both ty
Figure 2) Cisco OTV. For more information on OTV, refer to the Cisco OTV Overview. 2.2 Use Case Summary FlexPod Datacenter with NetApp MetroCluster is a flexible architecture that can be sized and optimized to accommodate a wide variety of use cases. This deployment focuses on a fabric MetroCluster
Units of Study by Grade Level Kindergarten 5 Grade 1 15 Grade 2 25 Grade 3 35 Grade 4 45 Grade 5 54 Grade 6 64 Differentiation Guide 72 Curriculum Connections 75 Pacing Guide 78 . 3 Rationale and Philosophy Note on Curriculum Format The Chesterfield School District has adopted the Understanding by Design (UbD) format to organize the Curriculum Standards. Overall Unit topics are thus seen as .
