SAN configurations in a MetroCluster environment
-
PDF of this doc site
- Cluster administration
-
Volume administration
- Logical storage management with the CLI
-
NAS storage management
- Configure NFS with the CLI
- Manage NFS with the CLI
-
Manage SMB with the CLI
- Manage file access using SMB
- Security and data encryption
- Data protection and disaster recovery
Collection of separate PDF docs
Creating your file...
You must be aware of certain considerations when using SAN configurations in a MetroCluster environment.
-
MetroCluster configurations do not support front-end FC fabric “routed” vSAN configurations.
-
Beginning with ONTAP 9.12.1, four-node MetroCluster IP configurations are supported on NVMe/FC. MetroCluster configurations are not supported on NVMe/TCP. MetroCluster configurations are not supported for NVMe prior to ONTAP 9.12.1.
-
Other SAN protocols such as iSCSI, FC, and FCoE are supported on MetroCluster configurations.
-
When using SAN client configurations, you must check whether any special considerations for MetroCluster configurations are included in the notes that are provided in the NetApp Interoperability Matrix Tool (IMT).
-
Operating systems and applications must provide an I/O resiliency of 120 seconds to support MetroCluster automatic unplanned switchover and Tiebreaker or Mediator-initiated switchover.
-
The MetroCluster is using the same WWPNs on both sides of the front-end SAN.