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

To move SAN LIFs to new nodes that are members of a portset during maintenance of a NetApp AFF ONTAP cluster, you should take the following steps:

Remove the LIF from the portset : This ensures that the LIF is no longer associated with the current node, preparing it for the move to the new node.

Take the SAN LIF offline : This step is necessary to make configuration changes without causing disruption to the SAN hosts. Once offline, the LIF can be moved to the new node and reconfigured as needed.

These actions help maintain the integrity and performance of the SAN environment during the migration of LIFs.

For more details, see:

NetApp Documentation on Moving SAN LIFs

NetApp Community on Moving LIFs

To validate that the ESXi host and NetApp ONTAP software releases are supported, the NetApp Interoperability Matrix Tool (IMT) should be used. The IMT provides comprehensive compatibility information, ensuring that all components of the SAN environment will work together seamlessly.

For further details, refer to:

NetApp Interoperability Matrix Tool

To migrate data from a LUN on an existing third-party SAN storage system to a new NetApp AFF A400 all-flash MetroCluster system, the supported methods include:

Foreign LUN Import in online mode : This method allows for data migration without significant downtime, enabling the system to continue serving data while the migration process is ongoing.

Foreign LUN Import in offline mode : This method involves taking the LUN offline during the migration process, which may be necessary in certain scenarios to ensure data integrity.

For more details, refer to:

NetApp Documentation on Foreign LUN Import

NetApp Community on LUN Import Methods

To clone a LUN from a SnapMirror destination volume for testing purposes, the volume clone create command should be used. This command creates a FlexClone volume from the SnapMirror destination, making the LUN within it accessible for testing without disrupting the original volume.

For more details, refer to:

NetApp Documentation on Volume Clone Create

NetApp Community Discussion on LUN Cloning