Skip to main content
NetApp Knowledge Base

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

Views:
807
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
nas
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

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.