Direct Attach support for Stretch MetroCluster Configuration with NetApp E-Series array
Applies to
- MetroCluster
- ONTAP 9
- ONTAP 8.3
- FlexArray
Answer
This document outlines the direct attach configuration with NetApp E-Series Array for a Stretch MetroCluster.
Direct Attach is supported only with NetApp E-Series Array in a Stretch MetroCluster configuration starting from Clustered Data ONTA
P 8.3.1
For all other supported arrays, you must use FC switches for connecting array LUNs to the Data ONTAP systems.
Related Links:
- V-Series and FlexArray Virtualization for Stretch MetroCluster solution in NetApp Interoperablity Matrix for support information
- Stretch Metrocluster Installation and Configuration Guide for installing and configuring a stretch MetroCluster
Supported Direct Attach configuration:
- Stretch MetroCluster with only NetApp E-Series Array LUNs
- Stretch MetroCluster with both NetApp E-Series Array LUNs and NetApp native disks where NetApp Native Disks are connected via Optical SAS cables.
- Stretch MetroCluster with both NetApp E-Series Array LUNs and NetApp native disks where NetApp Native Disks are connected via FC to SAS bridges.
Examples of Direct Attach configuration for Stretch MetroCluster (MCC) with NetApp E-Series array LUNs:
In a stretch MetroCluster configuration with NetApp E-Series Array LUNs, you must cable each controller's HBA ports to target ports on the corresponding NetApp E-Series Array Controllers.
- The following illustration shows a two-node stretch MetroCluster direct attach configuration with the NetApp E-Series array LUN connections:
- The following illustration shows a two-node stretch MetroCluster configuration in which native disks are connected to Data ONTAP systems through SAS optical cables.
For controller ports connecting to array LUNs, see Figure-1
- The following illustration shows a two-node stretch MetroCluster configuration in which native disks are connected to Data ONTAP systems through FC-to-SAS bridges:
For controller ports connecting to array LUNs, see Figure-1
Additional Information