Recently I changed my vCenter Certificate. But the AutoDeploy Service didn’t learned the new vCenter Certificate. So I got errors in /var/log/vmware/rbd/rbd-syslog.log
Recently we installed a brand new UCS System with 6454 Fabric Interconnects attached to Cisco MDS Fibre Channel Switches. But we get into some trouble with FirbeChannel Ports and their PortChannels.
Recently I upgraded my vCenter 6.7 U3 to vCenter 7.0 U1. During this upgrade, my Auto Deploy configuration was not adopted correctly.
Recently I upgraded my vCenter from Version 6.7 U3 17138064 to Version 7.0 U1. During deployment I hit the first issue.
A short wrapup to the latest Intel security leaks for VMware Administrators: CVE-2018-3639 aka Speculative Store Bypass (SSB), Variant 4 CVE-2018-3640 aka Rogue System Register Read (RSRE), Variant 3a. Once again we have to patch the whole stack: Update vCenter CPU Microcode (BIOS Update) VMware ESXi Hypervisor Patch Check if the new CPU flags are mapped to a new VM All VMs – Shutdown and start (reboot is not enough!) Update Guest OS Get some hints about EVC-Mode and how…
The last days we got two new All-Flash Storage Systems. These systems can present LUNs in a Metro-Cluster fashion. So I got the challenge to configure the Storage Plugin UltraPath from Huawei. In the manual from Huawei is explained how to configure the settings with esxcli on the ESXi-Host. That’s fine, but not enough 😉 We want to configure this with PowerCli to easily manage more than one Host. #get esxcli $esxcli2 = Get-ESXCLI -VMHost (Get-VMhost MyHost-001) -V2 #show…
The last days I had an issue with the vapi endpoint service. This was caused when I recreated the VMCA Solution Certificates with the Certificate Manager. BTW: VMware Support advised me to do so :/ The complete Message was: “Failed to connect to d30d9c10-e830-4a2e-b2dd-12de77fc11a3\com.vmware.cis.cls.vapi vAPI provider.” Look what other services are affected by this issue and how to fix it.
We design highly redundant Datacenters, Clusters, Storage Systems and even Networks, but in the end we still have some unplaned outages :/ This week we had a defect Memory DIMM that caused a PSOD on one ESXi Host. HA restarted the VMs fine, but we want to know quickly which VMs restarted. Check out a PowerCLI one liner to find the restarted VMs!
Check out the new Fling DRS Lens! It shows you a litte more how DRS is taking action.
I would like to show you my stumbling blocks when migrating to VCSA.