Example of switch zoning in a two-node 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 specific ONTAP systems.

You can use the following example as a reference when determining zoning for a two-node fabric-attached MetroCluster configuration with array LUNs:

The example shows single-initiator to single-target zoning for the MetroCluster configurations. The lines in the example represent zones rather than connections; each line is labeled with its zone number.

In the example, array LUNs are allocated on each storage array. LUNs of equal size are provisioned on the storage arrays at both sites, which is a SyncMirror requirement. Each ONTAP system has two paths to array LUNs. The ports on the storage array are redundant.

The redundant array port pairs for both the sites are as follows:

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 the illustrations:

Zone ONTAP controller and initiator port Storage array port
z1 Controller A: Port 0a Port 1A
z3 Controller A: Port 0c Port 1A'
z2 Controller A: Port 0b Port 2A'
z4 Controller A: Port 0d Port 2A
z5 Controller B: Port 0a Port 1B'
z7 Controller B: Port 0c Port 1B
z6 Controller B: Port 0b Port 2B
z8 Controller B: Port 0d Port 2B'

The following table shows the zones for the FC-VI connections:

Zone ONTAP controller and initiator port Switch
Site A  
zX Controller A: Port FC-VI a FC_switch_A_1
zY Controller A: Port FC-VI b FC_switch_A_2
Site B  
zX Controller B: Port FC-VI a FC_switch_B_1
zY Controller B: Port FC-VI b FC_switch_B_2