Switch zoning for a MetroCluster configuration with array LUNs

Switch zoning defines paths between connected nodes. Configuring the zoning enables you to define which array LUNs can be viewed by a specific Data ONTAP system.

When using switch zoning for a MetroCluster configuration with array LUNs, you must ensure that it meets these requirements:

A single-initiator to single-target zoning scheme must be followed for MetroCluster configurations.
Single-initiator to single-target zoning limits each zone to a single FC initiator port and a single target port.
FC-VI ports must be zoned end-to-end across the fabric.
Sharing of multiple initiator ports with a single target port is not supported. Similarly, sharing of multiple target ports with a single initiator port is also not supported.

You can use the following example as a reference when determining zoning for a MetroCluster configuration with array LUNs. The example shows single-initiator zoning for a MetroCluster configuration. The lines in the following example represent zones rather than connections; each line is labeled with its zone number:

This graphic depicts the switch zones in an example MetroCluster configuration with array LUNs. The graphic is described by the surrounding text.

In the example illustration, array LUNs are allocated on each storage array for the MetroCluster configuration. LUNs of equal size are provisioned on the storage arrays at both sites, which is a SyncMirror requirement. Each Data ONTAP system has two paths to array LUNs. The ports on the storage array are redundant, and are configured as follows:

Storage array at Site A:
- Ports 1A and 2A are a redundant port pair.
- Ports 1B and 2B are a redundant port pair.
Storage array at Site B:
- Ports 1C' and 2C' are a redundant port pair.
- Ports 1D' and 2D' are a redundant port pair.

The redundant port pairs on each storage array form alternate paths. Therefore, both the ports of the port pairs can access the LUNs on the respective storage arrays.

The following table shows the zones for this example:

Zone	Data ONTAP controller and FC initiator port	Storage array port
Switch A1
z1	Controller A1: Port 0a	Port 1A
z2	Controller A1: Port 0b	Port 2A'
z3	Controller A1: Port 0c	Port 1A'
z4	Controller A1: Port 0d	Port 2A
Switch A2
z5	Controller A2: Port 0a	Port 1B
z6	Controller A2: Port 0b	Port 2B'
z7	Controller A2: Port 0c	Port 1B'
z8	Controller A2: Port 0d	Port 2B
Switch B1
z9	Controller A3: Port 0a	Port 1C'
z10	Controller A3: Port 0b	Port 2C
z11	Controller A3: Port 0c	Port 1C
z12	Controller A3: Port 0d	Port 2C'
Switch B2
z13	Controller A4: Port 0a	Port 1D'
z14	Controller A4: Port 0b	Port 2D
z15	Controller A4: Port 0c	Port 1D
z16	Controller A4: Port 0d	Port 2D'

The following table shows the zones for the FC-VI connections at Site A and Site B:

Zone	Data ONTAP controller and FC initiator port	Switch
Site A
zX	Controller A1: Port FC-VI a	Switch A1
zY	Controller A1: Port FC-VI b	Switch A2
zX	Controller A2: Port FC-VI a	Switch A1
zY	Controller A2: Port FC-VI b	Switch A2
Site B
zX	Controller B1: Port FC-VI a	Switch B1
zY	Controller B1: Port FC-VI b	Switch B2
zX	Controller B2: Port FC-VI a	Switch B1
zY	Controller B2: Port FC-VI b	Switch B2