How to get the most out of your VMworld visit

It is only a few days to VMworld 2018 US and just over 3 months to VMworld 2018 EU. Time to think about a few points.

VMworld is a major event lasting several days at which hundreds of activities and sessions are offered every day. So there are many reasons to go there. In fact, I think some people just go for the party. But the question for most of us is: How can I get the most out of my visit?

There are some great blogposts from other people with general tips, like comfortable shoes, big bags or that you should definitely network with other people. Besides these general and useful tips I try to point out some other aspects.

Continue reading “How to get the most out of your VMworld visit”



vCloud Architecture Toolkit for Service Providers – What is it?

VMware recently released the latest version 2.5 of the vCloud Architecture Toolkit for Service Providers (vCAT-SP). But I know that many service and cloud providers around the globe don’t know what that is and that something like that even exists.

I will therefore try to give a brief overview and introduction to this topic and hopefully show how powerful this toolkit can be for your business.

Continue reading “vCloud Architecture Toolkit for Service Providers – What is it?”



Upgrading NIOC to v3 – Disruptive or not?

Upgrading NIOC from version 2 to 3 is no big deal. But I’m writing this blog post because the official VMware documentation says that the upgrade to NIOC v3 is disruptive and that worried me.

We have only one dvSwitch in our virtual infrastructure and use vSAN and NSX. If this upgrade is really disruptive, we need to shut down all virtual machines before the upgrade process starts. And that would be a big deal for us and our customers.

Continue reading “Upgrading NIOC to v3 – Disruptive or not?”



ESXi 6.x, Intel X710 and malicious driver event

Two of our vSAN clusters consist of VxRail S570 nodes with Intel X710 NICs. A few weeks ago the ESXi 6.5 hosts failed again and again. Not all at once but a different host every time. Failed means the host was displayed as “not responding” in the vSphere client and VMs stopped running and were restarted by vSphere Availability on other hosts.

Of course we thought of a network error at first, but on the physical upstream switches there were no related events in the logs and also all other hosts were not affected.

Continue reading “ESXi 6.x, Intel X710 and malicious driver event”