Required MetroCluster IP components and naming conventions
When planning your MetroCluster IP configuration, you must understand the required and supported hardware and software components. For convenience and clarity, you should also understand the naming conventions used for components in examples throughout the documentation.
Supported software and hardware
The hardware and software must be supported for the MetroCluster IP configuration.
When using AFA systems, all controller modules in the MetroCluster configuration must be configured as AFA systems.
Hardware redundancy requirements in a MetroCluster IP configuration
Because of the hardware redundancy in the MetroCluster IP configuration, there are two of each component at each site. The sites are arbitrarily assigned the letters A and B, and the individual components are arbitrarily assigned the numbers 1 and 2.
ONTAP cluster requirements in a MetroCluster IP configuration
MetroCluster IP configurations require two ONTAP clusters, one at each MetroCluster site.
Naming must be unique within the MetroCluster configuration.
Example names:
Site A: cluster_A
Site B: cluster_B
IP switch requirements in a MetroCluster IP configuration
MetroCluster IP configurations require four IP switches. The four switches form two switch storage fabrics that provide the ISL between each of the clusters in the MetroCluster IP configuration.
The IP switches also provide intracluster communication among the controller modules in each cluster.
Naming must be unique within the MetroCluster configuration.
Example names:
Site A: cluster_A
IP_switch_A_1
IP_switch_A_2
Site B: cluster_B
IP_switch_B_1
IP_switch_B_2
Controller module requirements in a MetroCluster IP configuration
MetroCluster IP configurations require four controller modules.
The controller modules at each site form an HA pair. Each controller module has a DR partner at the other site.
Each controller module must be running the same ONTAP version. Supported platform models depend on the ONTAP version:
Starting with ONTAP 9.5, new MetroCluster IP installations on Hybrid systems are supported.
Starting with ONTAP 9.4, controller modules configured for ADP are supported.
Example names:
Site A: cluster_A
controller_A_1
controller_A_2
Site B: cluster_B
controller_B_1
controller_B_2
Gigabit Ethernet adapter requirements in a MetroCluster IP configuration
MetroCluster IP configurations use a 40/100 Gbps or 10/25 Gbps Ethernet adapter for the IP interfaces to the IP switches used for the MetroCluster IP fabric.
| Platform model | Required Gigabit Ethernet adapter | Required slot for adapter | Ports |
|---|---|---|---|
| AFA DM7000F and DM7000H | X1116A | Slot 1 | e1a, e1b |
| AFA DM5000F, and DM5000H | Onboard ports | Slot 0 | e0a, e0b |
Pool and drive requirements (minimum supported)
Eight SAS disk shelves are recommended (four shelves at each site) to allow disk ownership on a per-shelf basis.
The MetroCluster configuration requires the minimum configuration at each site:
Each node has at least one local pool and one remote pool at the site.
For example, in a four-node MetroCluster configuration with two nodes at each site, four pools are required at each site.
MetroCluster configurations support RAID-DP.
Drive location considerations for half-shelf configurations
For correct auto-assignment of drives when using shelves that are half populated (12 drives in a 24-drive shelf), drives should be located in slots 0-5 and 18-23.