vSphere 8 is GA!
VMware has a great landing page that goes into details on all the new features and functionality.
The new DPU functionality, with the ability to offload network services, is a great advancement. How will this change how you architect future datacenters? When combined with the vSAN 8 Express Storage Architecture, there are many opportunities for optimization with next-gen hardware.
Presentation resources:
VMware Product Interoperability Matrices
vCenter Server 6.7 Update 1 Release Notes
ESXi 6.7 Update 1 Release Notes
vSAN 6.7 Update 1 Release Notes
Upgrade Considerations for VMware vSphere 6.7 (VMware vSphere Blog)
What’s New in Performance – VMware vSphere 6.7 (PDF)
vCommunity – Get involved on Twitter:
@vMiklm, @BhamVMUG, @myVMUG, @vExpert, @VMware
Video:
Often it is necessary to determine the PSC a vCenter server is pointed to. Is it an external PSC or an internal PSC?
In vSphere client, look at the vCenter Advanced Settings. Find the setting:
config.vpxd.sso.admin.uri
This URL will contain the hostname of the PSC.
The following resources should be helpful in understanding the Intel L1 Terminal Fault vulnerability announced today.
VMware KB 55636: VMware Overview of ‘L1 Terminal Fault’ (L1TF) Speculative-Execution vulnerabilities in Intel processors: CVE-2018-3646, CVE-2018-3620, and CVE-2018-3615 (55636)
Patching for CVE-2018-3646 “L1TF – VMM” could have performance impacts in customer virtualization environments. Refer to VMware KB 55806 for further details.
Overview video from Intel:
More detailed video from RedHat:
VM disk consolidation or Storage vMotion fails due to -CTK files.
Remove or rename any files ending with the *-ctk.vmdk file extension in the virtual machine directory.
http://paulgrevink.wordpress.com/2013/12/02/vm-disk-consolidation-fails/
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2048201
We had a recent situation where a virtual appliance (Avamar proxy) was mistakenly deployed configured with the IP address of the gateway. This caused the hosts to be unreachable from vCenter. After finding the offending VM and shutting it down from the console, the ARP tables either had to be cleaned up (you could also allow them to time out but that could take up to 20 minutes)
ESXi 5.1
esxcli network ip neighbor list
vsish -e set /net/tcpip/v4/neighbor del IPADDRESS
New functionality added in 5.5 to remove ARP entries through esxcli
Find a VM by MAC in vCenter with PowerCLI
Get-vm | Select Name, @{N=“Network“;E={$_ | Get-networkAdapter | ? {$_.macaddress -eq“00:50:56:A4:22:F4“}}} |Where {$_.Network-ne “â€}
Also you may need to clean up your Windows vCenter server from the command prompt
arp -a
arp -d IPADDRESS
Or,
netsh interface ip delete arpcache
Also a good idea to:
ipconfig /flushdns