Host profile compliance check fails with the error: IPv4 routes did not match
book
Article ID: 302338
calendar_today
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
- If multiple VMkernel Ports are in the same subnet host profile, compliance check fails with the error:
IPv4 routes did not match
- After successfully applying a host profile, the host shows that the profile is Not Compliant.
- Host profile is reported as Non Compliant even though it is Compliant.
- You see the error:
IPv4 routes did not match
Cause
This issue occurs when two or more VMkernel port groups use the same subnet.
Resolution
This issue is resolved in ESXi 5.1 Update 1.
Feedback
thumb_up
Yes
thumb_down
No