For quite some time I have observed a LOM warning in VMware health status tab on an HPE Proliant ML350 Gen10 server. It seems like it reports the warning on two NIC that are down, even though there are unused by ESXi.
This blog post is not about the L1 Terminal Fault (L1TF -> VMware KB56931) but about the HTAware Mitigation tool version 1.0.0.9 (HTAwareMitigation-1.0.0.9.zip) that seems to have issues when used on single hosts (instead of clusters) – here is the problem that I have observed.
You run the command:
Set-HTAwareMitigationConfig -VMhostName <hostname> -Enable
Followed by
Get-HTAwareMitigationConfig -VMhostName <hostname>
Get-HTAwareMitigationConfig not working on single host
As you might see the “Set-HTAwareMitigationConfig -VMhostname <hostname>” command doesn’t seem to do anything!
I recently wanted to make sure that my lab environment was on the latest VCSA version (Platform Service Controller and vCenter) so I went to the VAMI interface on my PSC and quickly discovered that there were no updates – that’s was strange because my PSC was at build 8217866 (build 6.7.0.10000) and according to the vSphere version list KB2143838 there has been released some newer versions Continue reading