Preparing for the MetroCluster installation

As you prepare for the MetroCluster installation, you should understand the MetroCluster hardware architecture and required components.

Differences between the ONTAP MetroCluster configurations
The various MetroCluster configurations have key differences in the required components.
Considerations for using ONTAP Mediator or MetroCluster Tiebreaker
Starting with ONTAP 9.7, you can use either the ONTAP Mediator-assisted automatic unplanned switchover (MAUSO) in the MetroCluster IP configuration or you can use the MetroCluster Tiebreaker software. Only one of the two services can be used with the MetroCluster IP configuration.
Considerations for MetroCluster IP configuration
You should be aware of how the MetroCluster IP addresses and interfaces are implemented in a MetroCluster IP configuration, as well as the associated requirements.
Considerations for automatic drive assignment and ADP systems in ONTAP 9.4 and later
Starting with ONTAP 9.4, MetroCluster IP configurations support new installations with AFF systems using ADP (Advanced Drive Partitioning). In most configurations, partitioning and disk assignment is performed automatically during the initial configuration of the MetroCluster sites.
Considerations for using All SAN Array systems in MetroCluster configurations
Some All SAN Arrays (ASAs) are supported in MetroCluster configurations. In the MetroCluster documentation, the information for AFF models applies to the corresponding ASA system. For example, all cabling and other information for the AFF A400 system also applies to the ASA AFF A400 system.
Considerations for configuring cluster peering
Each MetroCluster site is configured as a peer to its partner site. You should be familiar with the prerequisites and guidelines for configuring the peering relationships and when deciding whether to use shared or dedicated ports for those relationships.
Considerations for ISLs
Considerations for sharing private layer 2 networks
Starting with ONTAP 9.6, MetroCluster IP configurations with supported Cisco switches can share existing networks for ISLs, rather than using dedicated MetroCluster ISLs. Earlier ONTAP versions require dedicated ISLs.
Considerations for using MetroCluster compliant switches
MetroCluster IP switches provided by NetApp are NetApp validated. Beginning with ONTAP 9.7, MetroCluster IP configurations can support switches that are not NetApp validated provided that they are compliant with NetApp specifications.
Considerations for using TDM/xWDM and encryption equipment with MetroCluster IP configurations
You should be aware of certain considerations for using multiplexing equipment in the MetroCluster IP configuration.
Considerations when using unmirrored aggregates
If your configuration includes unmirrored aggregates, you must be aware of potential access issues after switchover operations.
Considerations for firewall usage at MetroCluster sites
If you are using a firewall at a MetroCluster site, you must ensure access for certain required ports.
Preconfigured settings for new MetroCluster systems from the factory
New MetroCluster nodes are preconfigured with a root aggregate. Additional hardware and software settings are configured using the detailed procedures provided in this guide.