vCenter 5.5 u1 - Host Profile Issue - IPv4 routes did not match

[lennyburns]

No matter what I do, i cannot figure out why some hosts have this issue and others do not.

I have seen this issue in 5.1, and seen that it is resolved in this very version, however, I have it in 5.5 and cannot rid myself of it.

I have torn down the networks and rebuilt them, and this returns every time.

Does anyone have any idea how this happens in a 5.5 vCenter?

[rcporto]

Do you have more than one VMkernel on the same subnet ? Any changes made on reference host after the creating of Host Profile ? Maybe you can try update the host profile from the reference host and check compliance again.

[lennyburns · Accepted solution]

Okay, so HERE is why it would (and did) happen.

I have typoed IP addresses in the 3rd octet on a couple of my vKernel interfaces.

Check yours - they must have a typo in them.... right?  (seriously, go look...  C A R E F U L L Y)

================================================================================

I have two separate iSCSI vKernel interfaces, each bound to two seperate vSwitches, and each vSwitch with 1 physical NIC.

( I do this for multi-pathing (I use Round Robin with an i/o value of 1 request per channel before changing to enhance speed)

Anyway, I also have multiple vSAN vKernel adapters as well for the same reason.

ALL these adapters have separate subnets.

I got the 3rd octet wrong when I typed in the IP on one host in two seperate clusters.

One IP was an iSCSI interface

The other was a vSAN interface.

This is why the hosts compliance would flip from one host in compliance and the others out, or all the others IN compliance, and this ONE being out.

This same type of error being in two separate clusters, on two different types of vKernel interfaces mad it nearly IMPOSSIBLE to spot.

All the flipping made it hard to diagnose, because it all looked related.

Once I corrected the issues, and updated my profile from the reference host (yes you need to do this), then everything passed compliance.

[lennyburns]

Multiple vKernel interfaces on the same subnet causing this was a known problem, and fixed in 5.5 U1 - hence my confusion on why it was happening now.

Also, re-updating was always going to be required after discovering the root cause.

See my reply below and you will understand the silliness that caused this.