Skip to main content
NetApp Stage KB

Direct Attach support for Stretch MetroCluster Configuration with NetApp E-Series array

Views:
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

 

 

 

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:

 

Supported Direct Attach configuration:

  1. Stretch MetroCluster with only NetApp E-Series Array LUNs
  2. Stretch MetroCluster with both NetApp E-Series Array LUNs and NetApp native disks where NetApp Native Disks are connected via Optical SAS cables.
  3. 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.

  1. The following illustration shows a two-node stretch MetroCluster direct attach configuration with the NetApp E-Series array LUN connections:


     
  2. 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
     
  3. 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

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.