Recently I’ve upgraded my homelab from 6.7U3 to vSphere7. The workflow is straightforward and very easy. The VMware Design team did a very good job with the UI.
I cannot point that out enough: check the VMware HCL. Just because your system is supported under your current vSphere version, doesn’t mean it’ll be supported under vSphere7 too. On the day I’ve upgraded, vSphere7 was brand new and there were just a few entries in the HCL. But it’s a homelab and if something breaks I don’t care to rebuild it from scratch. Don’t do this in production!
Although my Supermicro E300-9D is not yet certified for version 7.0, it works like a charm. I guess it’s just a matter of time, because the VMware Nano-Edge cluster is based on that hardware.
Before we can start, you need to download the vCenter Server Appliance 7.0 (VCSA) from VMware downloads (Login required). You also need to have new license keys for vCenter, ESXi and vSAN (if yor cluster is hyperconverged).
During a cluster routine check with RVtools I’ve seen a warning.
Warnings like this on a vCenter appliance let my alarm bells ring. Partitions filling up close to 100% are not a desirable condition. But let’s have a look into VAMI (vCenter Appliance Management Interface).
Now that’s strange. Everything seems to be in a green state. It’s a VCSA 6.7 Update 2a (220.127.116.11000). Older versions did show a storage warning. “File system /storage/archive is low on storage space“. But this appliance seems to be happy. Let’s have a look at the shell, to see what’s really happening.
It looks like mount point /storage/archive is almost filled up.
To manage a vCenter Server Appliance (VCSA) there’s a special user interface called Virtual Appliance Management Infrastructure (VAMI). You can access it by entering the FQDN of your vCenter into a browser, followed by port 5480.
This UI helps you to monitor your vCenter Virtual Appliance. You can change basic settings, apply updates and watch system status.
After updating a VCSA to the latest version of vCenter, I had to reboot the appliance. After the reboot process had finished, I wasn’t able to login to VAMI. Sometimes services need quite some time to become available, but even waiting for a longer period of time (a cup of coffee) nothing happened. VAMI presented a login screen, so obviously the webserver was up and running. But each time I entered the (correct) credentials I got the message “unable to login”. Screenshot is in German but you’ll most likely get the point ;-).