Requirements for switch zoning in a MetroCluster configuration with array LUNs
Suggest changes
PDFs
When using switch zoning in a MetroCluster configuration with array LUNs, you must ensure that certain basic requirements are followed.
The requirements for switch zoning in a MetroCluster configuration with array LUNs are as follows:
-
The MetroCluster configuration must follow the single-initiator to single-target zoning scheme.
Single-initiator to single-target zoning limits each zone to a single FC initiator port and a single target port.
-
The FC-VI ports must be zoned end-to-end across the fabric.
-
Sharing of multiple initiator ports with a single target port can cause performance issues.
Similarly, sharing of multiple target ports with a single initiator port can cause performance issues.
-
You must have performed a basic configuration of the FC switches used in the MetroCluster configuration.
Shared initiator and shared target support for MetroCluster configuration with array LUNs
Being able to share a given FC initiator port or target ports is useful for organizations that want to minimize the number of initiator or target ports used. For example, an organization that expects low I/O usage over an FC initiator port or target ports might prefer to share FC initiator port or target ports instead of dedicating each FC initiator port to a single target port.
However sharing of initiator or target ports can adversely affect performance.
-
Switch zoning defines paths between connected nodes. Configuring the zoning enables you to define which array LUNs can be viewed by specific ONTAP systems.