Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

FAS8020 storage initiator connection rules in a MetroCluster solution

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

Applies to

  • MetroCluster
  • ONTAP 9
  • FAS8020 only

Issue

In a MetroCluster in clustered Data ONTAP, each controller must have two HBA initiator connections to each of the two fabrics to connect storage. Along with that, each controller requires four HBA initiator ports.

When using FAS8020 controllers, there might be a need to only use two, instead of four, HBA initiator ports to connect storage to use the single free slot for host connectivity or tape backup. This applies to the FAS8020 only and no other platform. This type configuration can also be called as a 'single initiator per fabric' configuration.

Note: If a MetroCluster is configured using FAS8020 controllers and the hardware configuration is changed, these rules must be evaluated in order to add / remote paths so the configuration remains supported.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support