Last week I faced an issue with network throughput performance within VXLAN on NSX-v with a specific NIC and NIC driver. I came across this problem, because I am currently working on a ‘greenfield’ SDDC implementation project at one of our customers, and I was doing initial performance tests on the platform. (more…)
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.
Requirements:
– Powershell (5.1)
– PowerCLI
– PowerNSX
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 [1] cpu core(s) which is less than recommended [2] 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…)
Currently, I am moving my in-house lab to my garage. I installed a cabinet in the garage, bought a new Ubiquiti 24 ports switch which functions as a layer 2 switch inside of the cabinet.
My Synology is now connected to a LAG interface on my 16 Ports Layer 3 switch. Since I’m planning to move all of my hardware to my cabinet in the garage I also need to move the Synology, connect it to the UniFi switch and create a LAG again.
