Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

What are the requirements for NetApp ONTAP FC-NVMe deployment with ESXi 7.0?

Views:
151
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
virt
Last Updated:

Applies to

  • ESXi 7.0 FC-NVMe
  • VMware vSphere 7.0
  • ONTAP

Answer

VMware vSphere 7.0 release includes support for FC-NVMe storage stack.

This KB describes the settings required for improved Interoperability of ONTAP with ESXi 7.0 FC-NVMe.

  1. For Broadcom Emulex LPe3200x FCP HBA, the following parameter must be set to detect NVMe Namespaces:

    esxcli system module parameters set -m lpfc -p lpfc_enable_fc4_type=3

    Reboot the system for settings to take effect.

     Note: The above command in not required for Broadcom LPe3500x HBA.

  1. Once ESXi 7.0 has detected the Namespace and on presenting a new Subsystem from ONTAP, ESXi 7.0 does not detect the new Namespace presented. To detect the new subsystem and Namespace, following can be done: 
     
    1. On ONTAP issue: vserver stop <vserver-name>, followed by vserver start <vserver-name>
    2. Perform link reset on the host HBA or on target lifs

      Note: This would cause temporary loss to Namespace and possible application outage and should be carried out during planned maintenance window.

  1. Following parameter must be set to '0' for improved Interoperability:

    esxcfg-advcfg -s 0 /Misc/HppManageDegradedPaths

    Note: Failing to set this value to '0' would cause application outage
     
    1. Reboot system.
    2. Check if config disabled and start the test:

      esxcfg-advcfg -g /Misc/HppManageDegradedPaths

      Above command should show the value as 0 -> “Value of HppManageDegradedPaths is 0”
       
  2. Deploying Solaris VM and its data disk on Namespace, ensure to use virtual SCSI controller (LSI Logic SAS, PVSCSI) only. The use of virtual NVMe controller to Solaris VM is not recommended.
  3. NetApp supports FC SCSI LUNs and Namespace co-existence config. Refer to VMware documentation for number of LUNs and Namespaces and the path count recommended by VMware.
  4. For VM deployed on SCSI and NVMe Namespaces with virtual SCSI controller (LSI Logic SAS, PVSCSI) attached to the VM, the disk timeout recommended is 60 seconds. Refer to the corresponding VM OS vendor on how to set the disk timeouts to 60 seconds.
  5. Refer to NetApp IMT for any open issues and BURTs.

Additional Information

vSphere Upgrade Center