On June 1st VMware released the latest version for VMware Cloud Foundation (VCF), version 5.0. The release of VCF 5.0 means that VCF customers now can benefit from all the cool new features included in vSphere 8.x and NSX 4.1.x.
The first release off VCF dates back to 2015. During the VMworld (what we now know as VMware Explore) of that year VMware launched a product called SDDC EVO. In the following years that product evolved to what we know today as VCF.
vSphere 8 has been released on October 11 in 2022. It was first announced during the VMware Explore US (the event previously known as VMworld). vSphere 8 includes many new features . To be clear, when we talk about vSphere we talk about both vCenter Server and ESXi.
Compared to VMware vSphere 7 U3, this new release has increased a number of hard limits:
On VMware Explore US (the event previously known as VMworld) vSphere 8 and vSAN 8 was announced. In this blog I want to explain what has been changed. vSAN was first introduced back in 2014, the product has been evolved allot in these past 8 years. A few of these changes are support for All-Flash, Encryption, Deduplication and allot improvement in how vSAN handles failures and maintenance mode.
In a SDDC project the customer is requesting to rename the vLANS and vSphere vCenter Portgroups. Since the costomer is using NSX-T Datacenter the place to perform this rename is actions is the NSX-T Datacenter Manager console. The location where you can find this information is under Network>Segments. Or via the API.
At a customer site where the vSphere environment is setup over two locations. At both location the customer has setup MSA storage.
In order to keep the customer data safe we want to setup replication between the two locations. To set this up we install VMware vSphere Replication.
Lees verder
VMware has identified a security thread within vCenter. An upload vulnerability in vCenter’s Analytics service allows attackers to run arbitrary code on vulnerable servers. On a scale of 1 to 10 in terms of impact, the vulnerability, CVE-2021-22005, is rated 9.8. “The implications of this vulnerability are serious and it will only be a matter of time, probably minutes after the announcement, before working exploits appear,” VMware said on September 21. The thread has been registered by VMware under VMSA-2021-0002.
Lees verder
In a project we where starting an action to export a VM to an OVF file. We launched the export from the vSphere WebClient. During the export action the file stream failed and we cancelled the export action. Because we where running into a time restriction with the allowed time frame we wanted to boot the machine so it would be available to the end users.
Lees verder
The root account is the only login account to vSphere ESXi. There is no extra account to create a backdoor to logon to vSphere ESXi when the root password is lost. When a vSphere ESXi host is added to a vCenter instance, management of the host is primary done via vCenter. Troubleshooting ESXi is done primarily on the command line via an SSH connection. By default the SSH service is stopped. To start the SSH service you have to access the server via vCenter Host>Configure>System>Services. When you don’t have the root password for the vSphere ESXi host you have to follow the following procedure.
Lees verder
It is that time of the year again to start looking forward to VMworld 2021. Due to the ongoing Covid-19 pandemic VMworld 2021 will again be “fully virtual” again.
The upside to a virtual event is that you don’t need to walk across a big conference complex to get from one session to another. You can follow the conference from the luxury of you own chair and desk. Poor your own drink of choice, sit back and relax and take in all the information on VMware latest and greatest from your own home. Because VMworld 2021 will be fully virtual, like last year that will make it easier for people to attend since you don’t need to arrange travel (flight/hotel) to attend VMworld.
Recently I was upgrading vSphere ESXi host from version 6.5.0 (7388607) to version 7.0.1. vCenter for this environment is upgraded to version 7.0.2.0000. at first I was trying to start the upgrade via VMware LifeCycle Manager but that resulted in an error indicating that the vCenter/LifeCycle Manager and the ESXi version where not working well together. In order to make progress I’ve accessed the server via it’s Integrated Lights Out (ILO) interface (HPE). Mounted the HPE ESXi image through ILO and booted the server.
Lees verder