Today was a nice and peaceful day onsite, until I had the “pleasure” to configure vSphere Host Profiles and getting all the hosts compliant. After battling with some PSP path selection “Compliance Failures” an annoying “Number of network stack instances don’t match” failure appeared.
This is not the first time I got this failure and I knew how to solve it, but there is not much information online how you can solve it so I thought lets dedicate a small post about it.
The Host Profiles fix
First open a SSH connection to the reference host and run the following command :
|
1 |
esxcli network ip netstack list |
Then open a SSH connection to the hosts that won’t get it and refuses to get compliant with the Host Profile and run the last command show above again. Compare the two results, if it is correct there is another netstack shown on the not compliant host. Write down the netstack name and run the following command :
|
1 |
esxcli network ip netstack remove -N <netstackname> |
After this go back to the vSphere Host Profiles and click on “Check Profile Compliance”, the host should be “Compliant” when the check is completed!
Enjoy! 🙂
I had a similar issue on some hosts in our environment.
Using your esxcli command listed here, I found that there was actually a netstack missing from the list.
It would show up properly in the web client though.
To fix the issue, I edited the existing netstanc instance, and removed changed the advanced setting “Max. number of connections” form 11000 to 10999, saved, then changed it back to normal and saved again.
now with “esxcli network ip netstack list” all 3 netstack instances show up as normal, and the host profile checks as compliant.
I do wonder what caused the default ‘Provisioning’ netstack to drop off the host though…
Thanks for the tip!