Welcome to Knowledge Base!

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Categories
All

Products-NetApp

How to support Shared Initiator and Shared Target configuration with Array LUNs in a MetroCluster environment

Applies to

  • MetroCluster
  • ONTAP 9
  • FlexArray

Answer

This document outlines the shared initiator and shared target configuration support with Array LUNs in a MetroCluster environment.
Sharing of Initiator and sharing of target in a MetroCluster Configuration with Array LUNs is supported starting with Data ONTAP 8.3

Note: A minimum of four target ports are required for a MetroCluster with array LUNs.

Being able to share a given FC initiator port or target ports is useful for organizations that want to minimize the number of initiator or target ports used.
For example, an organization that expects low I/O usage over an FC initiator port or target ports might prefer to share FC initiator port or target ports instead of dedicating each FC initiator port to a single target port.
However, sharing of initiator or target ports can adversely affect performance.

Supported configuration:

Supported MetroCluster for Shared Target with array LUNs:

  1. 4/8-node MetroCluster configuration, where initiators are sharing target ports from the same site
  2. 4/8-node MetroCluster configuration, where initiators are sharing target ports from both the local and remote site

Supported MetroCluster for Shared Initiator with array LUNs:

  1. 2-node MetroCluster configuration, where initiators are shared across array target ports from the same site
  2. 4/8-node MetroCluster configuration, where initiators are shared across array target ports from the same site
  3. 2-node MetroCluster configuration, where initiators are shared across array target ports from both the local and remote site
  4. 4/8-node MetroCluster configuration, where initiators are shared across array target ports from both the local and remote site

Additional Information

Planning a MetroCluster with array LUNs for Shared Target Ports:
Connecting a maximum of two Data ONTAP FC initiator ports to a single target port on the storage array is supported. Each target port is zoned into two FC initiator ports.

The rules for this configuration are as follows:

  • Each node can share, at the most, one FC initiator port with the same target port.
  • All storage arrays must be from the same vendor and model family.
  • The best practice for zoning is to have each FC initiator-target port pair in a separate zone (1:1).


Example configuration: Shared target ports:

4/8-node MetroCluster where initiators are sharing target ports from the same site.
The below diagram shows a 4-node MetroCluster configuration, where initiators are sharing target ports from the same site with the respective zoning information

Shared target ports-1.png
For 8-Node MetroCluster, to configure the switch zoning, you can use the zoning examples of the above 4-node MetroCluster for the first DR group. To configure zoning for the second DR group, follow the same example and requirements for the FC initiator ports and array LUNs belonging to the controllers in the second DR group.

4/8-node MetroCluster where initiators are sharing target ports from both local and remote site.
The below diagram shows a 4-node MetroCluster configuration where initiators are sharing target ports from both local and remote site with the respective zoning information

Shared target ports-2.png


For 8-Node MetroCluster, to configure the switch zoning, you can use the zoning examples of the above 4-node MetroCluster for the first DR group. To configure zoning for the second DR group, follow the same example and requirements for the FC initiator ports and array LUNs belonging to the controllers in the second DR group.

Planning a MetroCluster with array LUNs for Shared Initiator:
Connecting an FC initiator port on a Data ONTAP system to up to four target ports on storage arrays is supported.
The rules for this configuration are as follows:

  • All storage arrays must be in the same vendor model family.
    Storage arrays in the same family share the same performance and failover characteristics.
    For example, storage arrays with different architectures would be in different families even though other characteristics might be the same. See the FlexArray Virtualization Implementation Guide for Third-Party Storage for details about the models in the storage array families for your vendor.
  • A single FC initiator port can connect to up to four target ports on multiple storage arrays.
  • The best practice zoning recommendation is to put each FC initiator-target port pair in a separate zone (1:1), even if the same FC initiator is talking to multiple target ports


Example configuration: Shared FC initiator ports

2-node MetroCluster where initiators are shared across array target ports from the same site
The below diagram shows a 2-node MetroCluster configuration where initiators are shared across target ports of the arrays in the same site with the respective zoning information.

Shared FC initiator ports-1.png


4/8-node MetroCluster where initiators are shared across array target ports from the same site
The below diagram shows a 4-node MetroCluster configuration where initiators are shared across array target ports from the same site with the respective zoning information.

Shared FC initiator ports-2.png


For 8-Node MetroCluster, to configure the switch zoning, you can use the zoning examples of the above 4-node MetroCluster for the first DR group. To configure zoning for the second DR group, follow the same example and requirements for the FC initiator ports and array LUNs belonging to the controllers in the second DR group.

2-node MetroCluster where initiators are shared across array target ports from both local and remote site
The below diagram shows a 2-node MetroCluster configuration where initiators are shared across array target ports from both local and remote sites with the respective zoning information.

Shared FC initiator ports-3.png


4/8-node MetroCluster where initiators are shared across array target ports from both local and remote site
The below diagram shows a 4-node MetroCluster configuration where initiators are shared across array target ports from both local and remote sites with the respective zoning information.

Shared FC initiator ports-4.png


For 8-Node MetroCluster, to configure the switch zoning, you can use the zoning examples of the above 4-node MetroCluster for the first DR group. To configure zoning for the second DR group, follow the same example and requirements for the FC initiator ports and array LUNs belonging to the controllers in the second DR group.


Stay Ahead in Today’s Competitive Market!
Unlock your company’s full potential with a Virtual Delivery Center (VDC). Gain specialized expertise, drive seamless operations, and scale effortlessly for long-term success.

Book A Meeting To Setup A VDCovertime

NetApp Cloud Volumes ONTAP: Enterprise-Grade Storage for the Public Cloud

Storage for Any Business Workload

NetApp Cloud Volumes ONTAP provides the flexibility to create cloud storage tailored to the specific requirements of any business workload. With additional cyber-resilience tools, you can enforce data security requirements while defining storage availability levels with single node, single-zone high availability (HA), or multi-zone HA deployments. Moreover, you can set storage performance and costs by selecting the underlying cloud infrastructure resources to meet your needs.

Read article

Efficient Data Estate Management on Google Cloud with NetApp BlueXP

Build Your Enterprise Storage on Google Cloud

NetApp's BlueXP offers two distinct options for ONTAP-based storage on Google Cloud. Cloud Volumes ONTAP allows for the creation of ONTAP-based storage within your Virtual Private Cloud, providing detailed control over the infrastructure. On the other hand, Cloud Volumes Service offers a fully managed ONTAP-based storage solution provided by Google Cloud. Whether you opt for a customer-managed service with Cloud Volumes ONTAP or prefer the fully managed Google service with Cloud Volumes Service, BlueXP ensures seamless deployment and operation using the management tools of your choice.

Read article

Maximizing Efficiency and Visibility with NetApp's Data Infrastructure Insights

Hybrid Multicloud Monitoring and Visibility

NetApp's Data Infrastructure Insights (DII) offers end-to-end visibility into your infrastructure and applications, enabling you to monitor, troubleshoot, and optimize all of your resources across on-premises, hybrid, and multi-cloud environments. With DII, you gain full visibility of your infrastructure and workloads, allowing you to collect and analyze data from heterogeneous environments, including Kubernetes clusters. This comprehensive view includes relationship mapping and usage attribution for advanced capacity planning and troubleshooting.

Read article

Empowering Cloud Solution Providers with NetApp Public Cloud Services

NetApp Public Cloud Services for Cloud Solution Providers

NetApp is dedicated to supporting its partners in expanding their cloud revenue and gaining expertise in cloud data management. Through offerings like Spot PC for MSP Partners, partners can deliver enterprise-class cloud desktops more easily and profitably. By leveraging NetApp's professional services, partners can ensure superior backup solutions. The company also provides modern workplace solutions and optimized cloud services for SAP. With partner education seminars and featured content, NetApp empowers its partners to succeed in the cloud market.

Read article

Efficient Data Management Solutions with NetApp Azure Integration

Seamless Enterprise Storage Migration to Azure

The need for organizations to migrate workloads to Azure while retaining enterprise-grade data management capabilities has never been more critical. With BlueXP, enterprises can easily provision and manage a highly available, performant, and cost-efficient cloud-based storage infrastructure on Azure. This solution ensures a seamless migration process while maintaining data protection across hybrid cloud environments. Whether it's reliability, security, performance, or cost efficiency, BlueXP delivers consistent functionality across on-premises and cloud environments.

Read article