When you have NSX running on a vSAN stretched cluster over two datacenters, or a Cross vCenter NSX setup over multiple datacenters you probably need static routes for the networks behind the DLR to keep the routing tables alive on the physical network routers when a datacenter failover occurs. I am working at a customer where I needed to add 10 static routes to 20 different ESG’s. It’s obvious that I didn’t want to add them manually. Therefore I created a script to put in the static routes in the edges for me. This may come in handy for somebody else.
– Powershell (5.1)
Usually installing ESXi (since 5.0) on a host with just one CPU core will simply fail. If you only have a single CPU core then the installation terminates with the following error: CPU_CORES_ERROR: Your machine has  cpu core(s) which is less than recommended  cpu cores. Since I have a server in my lab with just one core ( why? good question 🙂 ) I needed to get myself a workaround in order to get ESXi installed in my lab environment. (more…)
The NSX-v manager is not being backed up via snapshot-based backups. This isn’t officially supported. Therefore a file/configuration based backup method used to backup the configuration of your NSX manager periodically.
Unfortunately, there is no retention setting available in the NSX manager so if you are not careful the backup directory will grow in a rapid fashion and fill up your disk very fast. Via this easy script I’ve written, you can enable backup retention for your NSX-v backup files. (more…)
Lately, I have been playing around with NSX-T in my homelab, to be specific with version 2.2. A week or two ago NSX-T 2.3 has been released and initially, I was planning to upgrade all the stuff. After having a chat with a colleague where he suggested to do a clean install instead of upgrading it, I went for a fresh installation for the latest NSX-T version. (more…)
Day 1 – Sunday 26th of August
Today is the unofficial start of VMworld US 2018 in Las Vegas. Johan van Amersfoort, Marco van Baggum, Laurens van Duijn and myself are representing #TEAMITQ during the conference week. (more…)