It’ll be the eleventh time when VMworld Europe opens its gates in Barcelona from 4th November to 7th November 2019. Traditionally VMworld Europe takes place after VMworld North-America, which will be held in San Francisco in August 2019. VMworld Europe will mainly attract visitors from the EMEA region. Although breakout sessions will be mostly the same in SF and BCN, both events will have different content and highlights. There are three months time in between, so you can be sure to expect announcements in Barcelona that weren’t ready in August.
Every year bloggers can apply for one of the few blogging passes handed out by VMware. In 2018 I successfully applied for a pass and so I tried it again in 2019. Last Monday I got an email which confirmed that I will get one of the blogging passes. I’m very happy honored about getting a pass for the second time. Many thanks to the blogging team at VMware.
Friends asked me if I would go there even if I hadn’t been selected. The answer is yes for numerous reasons. Besides condensed first-hand information it is networking with friends from all over the world. Where else can you meet VMware product managers and developers in one place. Last year I have written a VMworld Survival Guide about going to Barcelona and why.
Early Bird registration will be open until July 23rd 2019. You can save 200 € on ticket price when booking before end of early bird registration phase.
I’m going to post articles here on ElasticSky.de before and during VMworld Europe. Stay tuned.
Virtual Distributed Switches have many advantages over standard switches. Because you have a centralized configuration over all hosts they’re less error prone to configuration errors than standard switches. Call me old fashioned but I prefer to have at least the hosts management interface on a standard switch. In case something bad happens, you can still access the host and make changes on the interface.
Recently a customers host had failed. After restoring configuration, for some reason vmnics were swapped between vdSwitches and it wasn’t possible to configure that host neither with hostclient nor with vCenter. The customer was short on vmnics in the past and has configured Management Network on a distributed Portgroup on a distributed vSwitch. This is legal and usually not a problem. In that special case it was a problem. I was literally locked out of the host. Reassigning NICs in the DCUI didn’t work, because they were all claimed by Distributed-vSwitches thus not available for standard switches.
What now ?
There’s help, but you need to access the CLI of DCUI. Login to DCUI console, select “Troubleshooting Options” in the main menu.
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 (18.104.22.168000). 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 ;-).