Introduction The other day we updated our UsageMeter environment to 4.8. We have a couple and all of them including this appliance worked fine after the upgrade. After a couple of days I received a message that the Usage Meter Read more…
Introduction The other day we upgraded our VMware Cloud Director (VCD) environment. The upgrade itself did not go so well for us, but I will discuss this in another blogpost. However this blogpost is for a specific bug which came Read more…
Introduction In our NSX(T) environment I’ve had to replace certificates loads of times. This is actually quite easy if you know how (which I will explain in this post). However, this time after replacing all the NSX Manager certificates (Cluster Read more…
Introduction In my previous blogpost where we deleted stuck vSAN objects due to a vSAN bug in the remediation workflow I mentioned the use of the ‘objtool’ to delete objects from the vSAN filesystem. In that specific blogpost I had Read more…
Recently I upgraded a vSphere 7 environment to version 8. This left me with a vCLM baseline which was no longer applicable to any of the ESXi hosts. However I could not delete it. The option to detach the baseline from the cluster was grayed out. The baseline itself shows it was intended to install a host extension for NSX-V. And the option to remove the baseline entirely is also grayed out. This post describes the underlying issue and how to resolve it.
Introduction The other day we were finding us in the position to completely re-install a couple of vSphere ESXi hosts which were once part of a larger VMware vSAN cluster environment. Usually this does not take that long to do Read more…
In my previous post I explained how to quickly interpret a network capture on ESXi by using pktcap-uw and tcpdump-uw. This works great to get some information at a glance. But what if you require some further analysis? Well, then Wireshark is probably your tool of choice. Check out the rest of this blog post to learn how to set up remote capturing so you don’t need temporary storage on ESXi for your capture files.
As a vSphere admin you are sometimes tasked with investigating network issues. You don’t always have VM access so you need to diagnose at the ESXi level. Now as some of you may know quickly gaining insight in VM network traffic by capturing it on the ESXi level is a rather complex task. The tool at your disposal for capturing VM traffic is called pktcap-uw and one of it’s biggest shortcomings is that it doesn’t interpret the packets.
Introduction Recently I have been upgrading one of my test environments from NSX 3.1.2 to 3.2.1 and have come across a couple of issues. This time it seems like there is one Tier 1 GW in my environment that is Read more…
Introduction Recently I have been upgrading one of my test NSX-T labs. In this particular lab environment the scenario was upgrading NSX-T 3.1.2.1.0 to 3.2.3.1.0. NSX-T environments are upgraded in phases and the first (actually second) phase is upgrading the Read more…