Host Profile compliance check fails on a profile created from an ESXi host using DHCP

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• The host profile becomes non-compliant when the initial configuration was taken from an ESXi host configured with DHCP and assigned to an ESXi host with static IP settings.
  
  
• The compliance check shows the error:

Number of IPv4 routes did not match

Environment

VMware vCenter Server 5.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server 6.0.x

Cause

This issue occurs if the Host Profile is created using a reference ESXi host configured to use DHCP. The Host Profile created from this will have a fixed Default Gateway set and one static route. This issue occurs when configuring an ESXi host with static settings. This creates two routes as Non-Compliant when compared to the host profile is expecting one static route.

After extracting the profile, the host profile is modified to change the management VMkernel address from DHCP to static.

Resolution

This is a known issue affecting VMware vSphere 6.0.x.

Currently, there is no resolution.

To work around this issue, manually add the default gateway.

1. Right-click the Host Profile and click Edit Host Profile.
2. Select the defaultTcpipStack under Netstack Instance Profile.
3. Add a sub-profile under IP Route Configuration. This should add a new sub-profile named GenericStaticRouteProfile.
4. Edit the newly added GenericStaticRouteProfile with the below information.
   
   Destination Network address: 0.0.0.0
   Destination prefix length: 0
   IP Next Hop: <default gateway IP address>
   Device name: <vmknic>
   IP Family type: "IPv4"
   

Additional Information

There is a similar issue that occurs when there are multiple vmkernel ports. For more information, see Host profile compliance check fails with the error: IPv4 routes did not match (2040943).

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box

Host profile compliance check fails with the error: IPv4 routes did not match
DHCP 設定の ESXi ホストからホストプロファイルを作成するとコンプライアンスチェックに失敗する