The ESXi host fails the compliance check after starting from Autodeploy with the error: Host requires reboot before previously applied configuration changes will take effect seen after booting from Autodeploy

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• The ESXi host fails the compliance check after starting from Autodeploy.
• You see the message:

Noncompliant

Compliance Failures

Host requires reboot before previously applied configuration changes will take effect.

Environment

VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.0

Cause

This issue occurs if you have changed some of the settings in the ESXi host.

Modifying these parameters require a reboot:

ScratchConfig.ConfiguredScratchLocation
ScratchConfig.ConfiguredSwapState
Net.EtherswitchHeapMax
Net.TcpipHeapSize
Net.TcpipHeapMax
Net.TcpipRxDispatchQueues
NFS.MaxVolumes
NFS.DiskFileLockUpdateFreq
NFS.LockUpdateTimeout
NFS.LockRenewMaxFailureNumber
NFS.HeartbeatFrequency
NFS.HeartbeatTimeout
NFS.HeartbeatDelta
NFS.HeartbeatMaxFailures
NFS.MaxVolumes
NFS.VolumeRemountFrequency
NFS.SyncRetries
NFS.LogNfsStat3
NFS.MaxQueueDepth
Net.TcpipSocketMax
Net.TcpipUseIoat
Net.DVSLargeHeapMaxSize

Resolution

Currently there is no workaround to prevent the reboot after changing these settings.

Alternatively, you can remove the parameters from the host profile.

For example, to remove the scratch profile:

1. Right-click the host and click Edit Profile.
2. Expand the Advanced configuration option.
3. Right-click ScratchConfig.ConfiguredScratchLocation and click Remove Profile.
4. Click OK.

Additional Information

In the absence of scratch, VMware recommends setting up remote syslogs for stateless ESXi hosts.

For more information, see Configuring syslog on ESXi 5.x (2003322)

Auto Deploy で ESXi ホストを起動後、コンプライアンスチェックが次のエラーで失敗する：Host requires reboot before previously applied configuration changes will take effect seen after booting from Autodeploy