Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

What settings made by VSC for VMware require an ESX host reboot to take effect?

Views:
146
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
nfs
Last Updated:

Applies to

FlexPod

Answer

Virtual Storage Console (VSC) for VMware has a feature that assigns NetApp recommended values for NFS, MPIO, and HBA settings on any or all the ESX hosts attached to the vCenter with which it is registered. However, for certain NFS and HBA settings to take effect, the ESX host has to be rebooted.

Given below are the settings. The settings that require a reboot are identified with an asterisk (*).

NFS Settings

  • Net.TcpipHeapSize *    
  • Net.TcpipHeapMax *
  • NFS.MaxVolumes
  • NFS.HeartbeatMaxFailures
  • NFS.HeartbeatFrequency
  • NFS.HeartbeatTimeout

MPIO Settings

  • PSP changes: Set to RR (round robin) for ESX 4.0+ FC paths with ALUA enabled. Set to FIXED for all other configurations.
  • ALUA: Set in the igroup on the controller. ESX will be unable to see it, until the host is rebooted.

Adapter Settings

  • Disk.QFullSampleSize
  • Disk.QFullThreshold
  • Emulex FC HBA timeouts *
  • QLogic FC HBA timeouts *
  • QLogic iSCSI HBA timeouts *

Additional Information

N/A