As we have setup a new cluster of four ESXi 6.5 hosts, we have extracted a host profile from one of the hosts that we have setup to my customer corporate standards. After applying that host profiles to the other three hosts, we were able to quickly resolove all non-compliant issues except one where it keep complaining: “Number of ipv4 routes did not match”.
There is a good KB article on this which can be found at: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2106112
We had two challenges with KB2106112 though, which I wanted to document to help others stumbling with the same issue as follow:
1- The KB state it is only covering up to vSphere 6.0, where our environment was vSphere 6.5 and the fix still apply
2- The KB only stated to look at the “defaultTcpipStack” Netstack Instance, where in our case it was more to do with the “VMotion” Netstack Instance. Exactly same resolution, but you need to apply it to the “VMotion” Netstack Instance.
As I have mentioned above, this can affect any of your Netstack Instances, so while I am demonstrating how to fix it for the “VMotion” Netstack Instance, you can follow exactly the same steps to fix it for other Netstack Instances include the “defaultcpipStack”.… Read More