Table of ContentsView in Frames

ESXi host values set by VSC for VMware vSphere

Virtual Storage Console for VMware vSphere sets ESXi host timeouts and other values to ensure best performance and successful failover. The values that Virtual Storage Console (VSC) sets are based on internal NetApp testing.

VSC sets the following values on an ESXi host.

ESXi advanced configuration

VMFS3.HardwareAcceleratedLocking
You should set this value to 1.
VMFS3.EnableBlockDelete
You should set this value to to 0.

2007427.

NFS settings

Net.TcpipHeapSize
If you are using vSphere 5.0 or later, you should set this value to 32.

For all other NFS configurations, you should set this value to 30.

Net.TcpipHeapMax
If you are using vSphere 6.0 or later, you should set this value to 1536.

If you are using vSphere 5.5, you should set this value to 512.

If you are using vSphere 5.0 or 5.1, you should set this value to 128

If you are using vSphere 5.0 or earlier, you should set this value to 120.

NFS.MaxVolumes
If you are using vSphere 5.0 or later, you should set this value to 256.

For all other NFS configurations, you should set this value to 64.

NFS41.MaxVolumes
If you are using vSphere 6.0 or later, you should set this value to 256.
NFS.MaxQueueDepth
If you are using the vSphere 6.0 or later version of ESXi host, then you should set this value to 128 or higher to avoid queuing bottlenecks.

For vSphere versions prior to 6.0, you should set this value to 64.

NFS.HeartbeatMaxFailures
You should set this value to 10 for all NFS configurations.
NFS.HeartbeatFrequency
You should set this value to 12 for all NFS configurations.
NFS.HeartbeatTimeout
You should set this value to 5 for all NFS configurations.

FC/FCoE settings

Path selection policy
You should set this value to RR (round robin) when FC paths with ALUA are used.

You should set this value to FIXED for all other configurations.

Setting this value to RR helps to provide load balancing across all of the active/optimized paths. The value FIXED is used for older, non-ALUA configurations and helps to prevent proxy I/O. In other words, it helps to keep I/O from going to the other node of a high-availability (HA) pair in an environment that has Data ONTAP operating in 7-Mode.

Disk.QFullSampleSize
You should set this value to 32 for all configurations. Setting this value helps to prevent I/O errors.
Note: vSphere 5.1 handles Task Set Full (QFull) conditions differently from vSphere 4.x and 5.0.

NetApp Knowledgebase Answer 1030581: How to manually configure Task Set Full (QFull) Tunables for LUNs in vSphere 5.1

Disk.QFullThreshold
Set to 8 for all configurations. Setting this value helps prevent I/O errors.
Note: vSphere 5.1 handles Task Set Full (QFull) conditions differently from vSphere 4.x and 5.0.

NetApp Knowledgebase Answer 1030581: How to manually configure Task Set Full (QFull) Tunables for LUNs in vSphere 5.1

Emulex FC HBA timeouts
Use the default value.
QLogic FC HBA timeouts
Use the default value.

iSCSI settings

Path selection policy
You should set this value to RR (round robin) for all iSCSI paths.

Setting this value to RR helps to provide load balancing across all of the active/optimized paths.

Disk.QFullSampleSize
You should set this value to 32 for all configurations. Setting this value helps to prevent I/O errors.
Note: vSphere 5.1 handles Task Set Full (QFull) conditions differently from vSphere 4.x and 5.0.

NetApp Knowledgebase Answer 1030581: How to manually configure Task Set Full (QFull) Tunables for LUNs in vSphere 5.1

Disk.QFullThreshold
You should set this value to 8 for all configurations. Setting this value helps prevent I/O errors.
Note: vSphere 5.1 handles Task Set Full (QFull) conditions differently from vSphere 4.x and 5.0.

NetApp Knowledgebase Answer 1030581: How to manually configure Task Set Full (QFull) Tunables for LUNs in vSphere 5.1