Considerations when implementing a MetroCluster configuration with disks and array LUNs

Contributors netapp-thomi

When planning your MetroCluster configuration for use with disks and array LUNs, you must consider various factors, such as the order of setting up access to storage, root aggregate location, and the usage of FC initiator ports, switches, and FC-to-SAS bridges.

Consider the information in the following table when planning your configuration:



Order of setting up access to the storage

You can set up access to either disks or array LUNs first. You must complete all setup for that type of storage and verify that it is set up correctly before setting up the other type of storage.

Location of the root aggregate

  • If you are setting up a new MetroCluster deployment with both disks and array LUNs, you must create the root aggregate on native disks.

    When doing this, ensure that at least one disk shelf (with 24 disk drives) is set up at each of the sites.

  • If you are adding native disks to an existing MetroCluster configuration that uses array LUNs, the root aggregate can remain on an array LUN.

Using switches and FC-to-SAS bridges

FC-to-SAS bridges are required in four-node configurations and two-node fabric-attached configurations to connect the ONTAP systems to the disk shelves through the switches.

You must use the same switches to connect to the storage arrays and the FC-to-SAS bridges.

Using FC initiator ports

The initiator ports used to connect to an FC-to-SAS bridge must be different from the ports used to connect to the switches, which connect to the storage arrays.

A minimum of eight initiator ports is required to connect an ONTAP system to both disks and array LUNs.

Related information