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.
A couple of days ago I was visiting a customer to setup their Lenovo host to run vSAN – after the initial setup of vSAN kernel IPs, disk groups and so on, I took a look at the “VSAN Health check” to make sure that everything was healthy and supported.
Under the “hardware compatibility” part all checkmarks where green, but the Controller firmware version was not detected – so I did found it a bit strange that it reports the disk controller as supported without knowing what version it actually was running.
This issue is not new to me, as I have seen it a couple of times before, but this time it was different after all.
This morning I faced a strange issue in my vSphere Lab when a wanted to login to VAMI interface – of course to install the newly released “vSphere 6.7 U1” update.
I opened the VAMI URL for my Platform service controller (PSC): https://<FQDN>:5480 and typed in my root credentials as a normally would. However, the only thing that showed on the screen was a message saying: “Unable to login”.
After this I tried to type in my password multiple times to make sure that I was actually typing in the correct one, but still, I just got the same error message.
This blog post is not about the L1 Terminal Fault (L1TF -> VMware KB56931) but about the HTAware Mitigation tool version 22.214.171.124 (HTAwareMitigation-126.96.36.199.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
Get-HTAwareMitigationConfig -VMhostName <hostname>
As you might see the “Set-HTAwareMitigationConfig -VMhostname <hostname>” command doesn’t seem to do anything!
So, you find yourself in a situation where you have lost the root password for your ESXi host(s). Luckily there are multiple ways of resetting it – but the best method depends on the exact situation. Ill try to outline three different scenarios (of course, more exists) – maybe your are placed in a completely different scenario but maybe this post can help you anyway.
Ill like to highlight that after updating “Veeam Backup and Replication” to “version 9.5 update 3a” you might start to see warnings like this in your Veeam status reports:Continue reading
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 188.8.131.5200) and according to the vSphere version list KB2143838 there has been released some newer versions Continue reading
Welcome to my blog
A little something about me:
My name is Christian Møller and i have been working in the IT industry since 2004. I’ve been working with a lot of different stuff in my carrier but one thing that has been keeping me busy since 2006 is VMware. In year 2006 GSX and ESX was the new hot thing (at least for me) so it also made sense to get a VCP3 certification which i got in 2007.
On this blog ill try to post ideas, guidelines and provide tips and tricks and solutions to real life problems in the datacenter. Discussing new features and also providing “shortcuts” to daily operation tasks.
If you want to know more about me and my blog please visit the About page.