To configure an SVM to use NVMe/FC, the following steps are necessary:

Add the FC protocol: This step involves enabling the Fibre Channel protocol on the SVM, which is required to support NVMe over Fibre Channel.

Create an NVMe/FC LIF: Logical Interfaces (LIFs) must be created to handle NVMe traffic over the Fibre Channel network. These LIFs enable the NVMe namespace access to the host systems.

These steps ensure that the SVM is correctly set up to use NVMe/FC, allowing for efficient and high-performance access to NVMe storage.

For more information, refer to:

NetApp NVMe/FC Configuration

When using Fibre Channel Protocol (FCP), the minimum number of FC switches needed to redundantly attach three ESXi hosts is 2. This setup ensures that each host has multiple paths to the storage, providing high availability and fault tolerance. Each ESXi host should be connected to both switches, allowing for continuous operation even if one switch fails.

For more information, refer to:

NetApp Documentation on FC Switch Configurations

NetApp Community Discussion on Redundant FC Setup

MetroCluster IP uses an IP-based backend infrastructure and supported Ethernet switches rather than the FC switching and FibreBridge architecture associated with MetroCluster FC configurations. The ASA A800 is supported in MetroCluster IP configurations, including deployments using supported Cisco IP switches. For automated unplanned switchover, ONTAP Mediator provides the independent quorum/state mechanism used by MetroCluster IP nodes to determine whether an automatic switchover should occur. NetApp describes Mediator-assisted automatic unplanned switchover (MAUSO) as the MetroCluster IP capability that can initiate switchover following qualifying failures, including complete site failure. ATTO FibreBridge devices and FC switches belong to FC-based MetroCluster topologies and are not the required IP components in this scenario. Consequently, the required choices are Ethernet switches and ONTAP Mediator.

To enable CHAP (Challenge-Handshake Authentication Protocol) authentication on iSCSI sessions, the command vserver iscsi security create should be used. This command sets up the necessary security policies and passwords required for CHAP authentication, ensuring secure access to iSCSI targets.

For more details, refer to:

NetApp Documentation on iSCSI Configuration​ ( NetApp )​.

To restore a LUN from a SnapMirror Synchronous destination, the following steps must be taken:

Release the relationship: This step is necessary to break the SnapMirror relationship, allowing the LUN to be restored independently.

Delete the relationship: After releasing the relationship, deleting it ensures that there are no residual dependencies or configurations that might interfere with the restore process.

For more information, refer to:

NetApp Documentation on SnapMirror Synchronous​ ( NetApp )​​ ( NetApp )​.

When the number of paths exceeds the recommended configuration for SAN deployment, it can cause performance issues. To address this problem, you can:

Use Selective LUN Mapping (SLM): SLM allows you to control which LIFs (Logical Interfaces) are used to access specific LUNs, thus reducing the number of paths and potentially improving performance by aligning with best practice configurations.

Reconfigure the fabric switch zoning: Adjusting the zoning on the fabric switches can help manage and optimize the number of paths, ensuring that there are not too many paths that could lead to inefficient I/O operations and performance degradation.

For more details, refer to:

NetApp SAN Host Configuration

NetApp Best Practices for SAN

ONTAP interface groups support several traffic-distribution algorithms, including port, which distributes traffic using transport-layer TCP or UDP port information. Therefore, network port ifgrp create -distr-func port establishes the corresponding ONTAP-side distribution behavior. The connected Cisco Nexus infrastructure should use a compatible port-channel hashing method; NetApp validated architectures show port-channel load-balance src-dst l4port for Nexus switches so source and destination Layer-4 ports contribute to traffic distribution. This improves utilization across member links compared with algorithms using fewer flow attributes. The original V9.02 text contained the typographical string 14port; the correct command parameter is l4port, meaning Layer 4 port. Options C and D do not establish the requested port-based load-balancing algorithm. Relevant SAN ONTAP topics include interface groups, port distribution functions, link aggregation, and Nexus port-channel hashing.

ONTAP provides dedicated FCP connectivity tests for validating communication between host initiators and FC LIFs. The vserver fcp ping-igroup show command performs a connectivity check between FCP initiators contained in an igroup and the FCP LIFs through which those initiators are configured to connect. The vserver fcp ping-initiator show command performs the equivalent validation for an individual FC initiator. These commands are therefore appropriate after zoning a new FCP SVM to SQL hosts. cluster ping-cluster validates ONTAP ' s internal cluster network and is unrelated to host-to-storage FC connectivity. network fcp zone show displays discovered FC zoning information but is not the specific FCP initiator connectivity test requested. Relevant SAN ONTAP topics include FC zoning validation, igroups, WWPN connectivity, FCP LIFs, and SAN troubleshooting commands.

The space-allocation option enables ONTAP support for SCSI thin-provisioning functions and allows compatible SAN hosts to manage and reclaim unused LUN space. When space allocation is enabled, ONTAP can communicate storage-space conditions to the host and support host-initiated space reclamation through mechanisms such as SCSI UNMAP. NetApp specifically states that enabling space allocation allows SAN hosts to reclaim storage that is no longer being used. space-reserve controls whether physical capacity is reserved for the LUN but does not provide host-side reclamation. resize relates to changing storage size, and alua controls asymmetric path behavior rather than capacity management. Current ONTAP releases enable space allocation by default for many newly created SAN objects. Relevant SAN ONTAP topics include LUN thin provisioning, SCSI UNMAP, space reclamation, and LUN space-allocation configuration.

Fibre Channel zoning is configured and maintained within the FC switching fabric. ONTAP hosts and storage LIFs provide WWPN identities, but the switch configuration determines which initiator and target ports are permitted to communicate. NetApp’s FC zoning guidance instructs administrators to log in to the FC switch administration interface, create zones containing host initiator WWPNs and ONTAP FC LIF WWPNs, save the zones, and activate the resulting zone configuration. Cisco environments use zones and zonesets, while comparable constructs exist on Broadcom/Brocade fabrics. Neither the host HBA nor the ONTAP storage system stores the authoritative fabric zoning configuration. Therefore, the FC switches are the correct location. Relevant SAN ONTAP topics include FC fabric design, WWPN zoning, zonesets, dual-fabric configurations, and SAN connectivity.