This powershell script is created for VMware PowerCLI. Its purpose is to find a VM by IP or MAC address. This is often useful when digging through NSX logs.Continue reading PS Script Find Machine or VM by Mac or IP
Had a ESXi PSOD today. That does not happened that often, so I was quite surprised to find out that it was not a hardware related issue that was the root cause.
VMware did an analysis of the memory dump, and it turned out to be a faulty driver. That made sense since the PSOD often comes from drivers og agents when it is not a hardware issue.
The PSOD i got was the following:
#PF Exception 14 in World xxxxxxx:vmnicX-pollw IP xxxxxxxxxx addr xxxxxxxxContinue reading ESXi 6.7 PSOD with qlfe3 driver version above 220.127.116.11
I was just updating a vCenter server and some ESXi hosts, but after running the vCenter update I found vCenter full of HA Agent install fails. To stop this fail loop, I turned off VMware HA while figuring out what was wrong.
Error: cannot install the vcenter agent service. cannot upload agent after vCSA upgradeContinue reading Error: cannot install the vcenter agent service. cannot upload agent after vCSA upgrade
Just provisioned the HPE ESXi 6.7 Update 3 custom OEM image onto some HP DL560 Gen10 servers.
After I updated the servers using update manager and the HPE vibsdepot I ran into problems. Turns out there is a conflict between the VMware provided driver and the HPE provided driver.
The result is that I cannot install all updates to satisfy compliance.
Checking the esxupdate.log file on the ESXi hosts I get the following error:
ValueError: VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 and ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 have unequal values of the 'payloads' attribute: '[elx-esx-libelxi: 1602.936 KB]' != '[elx-esx-libelxi: 1493.833 KB]'Continue reading Update Manager ELX_bootbank_elx-esx-libelxima.so driver conflict
So VMware released a security advisory (VMSA-2019-0009) about vulnerable VMware Tools.
In short it is recommended to upgrade all VMware Tools to at least version 10.3.10 (Build 10346) which is the newest at the time of writing.
After patching ESXi to the latest build, you might realize that the VMware tools you are left with, after upgrading the tools, in a VM, is 10.3.5 (build 10341) Continue reading How to upgrade to VMware Tools 10.3.10
I have found that, when working with VMware vSphere, there are many benefits of running Linux on your workstation.
Things like tight integration with SSH, ISO files, API’s, Python are all things that make your life easier not only on Linux, but also when working with VMware.
Recently ran into a HPE Proliant m510 server running vSAN, where vSAN complained that the controller driver for the NVMe disk where too new.
The health error said that the current driver nvme (18.104.22.168.-1vmw.622.214.171.12402608) was to new and the recommended driver was nvme (126.96.36.199-1vmw.670.0.08169922)
Downgrading is not always a breeze. When going to VMware compatibility guide, the NVMe disk is supported for vSAN 6.7 Update 1, and there are no download links to a specific driver, so how do you get the old driver? Continue reading vSAN – Downgrading NVMe driver in ESXi 6.7 Update 1
I recently installed Powershell Core om Ubuntu 18.04, and after installing the PowerCLI module. I ran into an error.
The error is not an uncommon one, but on Windows the error message makes a lot more sense, so I just wanted to let you know what this error actually means.
The error you might get when you try to connect to your vCenter server using the connect-viserver is the following:
Connect-VIServer : 9/27/18 10:41:37 AM Connect-VIServer The SSL connection could not be established, see inner exception. At line:1 char:1 + Connect-VIServer <servername> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-VIServer], ViError + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_SoapException,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer
The only hint here is “The SSL connection could not be established…”
This actually means that you do not have a valid certificate. And if you want to connect to vCenter without a valid certificate, you have to allow this.
You can either change you vCenter certificate to a trusted one, which is the correct solutions or you can ignore invalid certificates, which circumvents all security, but makes it work right now.
Please comment if this was helpful.
Issue with nic driver on HPE servers after updating HPE drivers on ESXi 6.5 and 6.7
I ran into an issue the other day with a vCenter Server Appliance filling up one of its partitions. The partition that was filling up was the /storage/seat partition. This partition holds the postgres SQL database, so the vCenter server was in trouble.
After some digging around I realized that the root cause was a new event error from all ESXi hosts, that was coming at a rapid pace. The errors had started during the last driver and base updates, and only the HPE servers was affected. Continue reading 10fb does not support flow control autoneg
Just had an odd issue today.
A customer had created a Virtual Distributed Switch, but was unable to add his ESXi hosts to the vDS. It said that: “Host is not compatible with the VDS version.”
He was only able to join his version 6.5 ESXi host to a 5.5 vDS. If it was upgraded to version 6.0 or 6.5 it did not work.
There are multiple reports of this online related to upgraded hosts and vCenters. I suspect that it is an issue that you only run into if you do major upgrades without reinstalling ESXi, and since I never do that I have not had that problem before.
The quick solution to this problem is: Continue reading Host xxx.xxx.xxx.xxx is not compatible with the VDS version