ONTAP 9.14

to Japanese version

All SAN Array configuration limits and support

All SAN Array (ASA) configuration limits and support varies by ONTAP version.

SAN protocols and nodes per cluster

ASA support for SAN protocols and nodes per cluster are as follows:

Beginning with ONTAP…​

Protocol support

Max nodes per cluster

9.12.1

  • NVMe (supported on 4-node MetroCluster IP configurations and non-MetroCluster IP configurations)

  • FC

  • iSCSI

12

9.9.1

  • NVMe (supported on non-MetroCluster IP configurations)

  • FC

  • iSCSI

  • 12 nodes (for non-MetroCluser IP configurations)

  • 8 nodes (for MetroCluster IP configurations)

9.7

  • FC

  • iSCSI

4

Support for persistent ports

Beginning with ONTAP 9.8, persistent ports are enabled by default on All SAN Arrays (ASAs) that are configured to use the FC protocol. Persistent ports are only available for FC and require zone membership identified by World Wide Port Name (WWPN).

Persistent ports reduce the impact of takeovers by creating a shadow LIF on the corresponding physical port of the HA partner. When a node is taken over, the shadow LIF on the partner node assumes the identity of the original LIF, including the WWPNe. Before the status of path to the taken over node is changed to faulty, the shadow LIF appears as an Active/Optimized path to the host MPIO stack, and I/O is shifted. This reduces I/O disruption because the host always sees the same number of paths to the target, even during storage failover operations.

For persistent ports, the following FCP port characteristics should be identical within the HA pair:

  • FCP port counts

  • FCP port names

  • FCP port speeds

  • FCP LIF WWPN-based zoning

If any of these characteristics are not identical within the HA pair, the following EMS message is generated:

EMS : scsiblade.lif.persistent.ports.fcp.init.error

Top of Page