Here I will collect main steps to deploy UbuntuKVM on esxi for NSX-T deployment for testing purposes.

1. Install NSX-T version 2.4.1

2. Install Ubuntu 16.04.2 as most compatable

Why NSX-t v2.4.1: I am currently want to stick to VMware Validated Design VVD 5.1

1. Log in to the vCenter via vSphere client, right click the cluster and click “Deploy OVF

Sometimes you can see errors that one of the NSX controllers not healthy.

First, try to SSH to the applience and check logs.

Also, good practice to restart

ISSUE: When navigating to your vCenter Web Client (Flash) page, the browser no longer allows you to check the “Use Windows session authentication” box.

FIX: need to

NSX Manager version: 6.4.1
Appeared in earlier versions too.

Issue: The /var/log is full with 100% utilization for all 3 Controllers.
root@nsx-controller [ /var/log ]# df

This is basically a root bash shell on the underlying Linux based appliance. From here, system configuration files and scripts as well as most normal Linux functions can be

To take full advantage of the Intel® Converged Network Adapter's capabilities, enable Receive Side
Scaling (RSS) in the ESXi host to balance the CPU load across multiple cores. Refer to the

Some useful NSX CLI commands:

System related:

• ESXi build and version numbers
  esxcli system version

In the realease notes you will find a description of all the news ...

vRNI was installed and configured, but we forgot to put proper license and after demo license expired, we was locked down to put active license into environment.

Some work

After I decided to have VSAN on my small home lab, I looked up some

Connect to VMware vCenter Server Applience on port 5480

I used #6 ...

VMware PowerCLI 10.0.0 is the new release of PowerCLI and the first to become multi-platform: it adds support for Mac OS and Linux!

Thanks to Microsoft PowerShell Core 6.0, the

I just had an issue with vCenter 6.0 and ESXi 6.0 where I was unable to deploy OVF power on a VM.

The error which I was faced with was a relatively generic message based on the host

Issue:

I have recently had the requirement to put a NAT router performing NAT overload between an ESXi server and it's respective vCenter server. According to VMware ...

vSphere: vCenter behind NAT

Error: Live migration of 'Virtual Machine WIN2012-STD' failed. Virtual machine migration operation for 'WIN2012' failed at migration source 'WIN2012-R2-A'. The Virtual

Issue: Updates were stuck installing at 5% or Cannot instal updates:

1. Amended the 'Automatic Start action' on virtual machine settings to change the delay to 2 seconds,

Changing the Windows PowerShell Script Execution Policy

The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will