How to vote for Top vBlog 2016

Eric Siebert has just opened this years voting for the Top vBlogs 2016. I think it’s a good opportunity to appreciate all the great content that helps us all with our jobs. But how to vote? The list is quite long…and who to select as Nr. 1? Myself? Someone I know personally? The blog with the best design or content? How to measure content quality?

Like last year, I like to automate the decision. (No, not that kind of automation with different IP-Addresses for each vote….). My theory is that the blog where I spent the most time was most helpful for me and should therefore be my personal number 1 vote. So here is how I vote:

Export Browser History…
Filer URLs…
Calculate Sums..
Filter out non VMware related sites..


An also thank you to…


Which Features are missing in NSX Standard and Advanced?

VMware has changed their NSX licensing model from a one-fits-all license model to 3 license tiers. Starting May 3, 2016 VMware NSX is available as three offerings: Standard, Advanced, and Enterprise. All three tiers are licensed based on physical sockets. The existing NSX license scheme is no longer availale.

Special license models are available for Service Providers and Virtual Desktop environments. For EUC platforms, the advanced edition is also available one a per-user basis and Service Providers can license NSX on a per-VM basis. At least NSX 6.2.2 is required to work with NSX Standard, Advanced, and Enterprise license keys.nsx-offerings

According to VMware, these offerings are aligned to the following requirements:

  • Standard is targeted at organizations that needs agility and automation of the networks.
  • Advanced is for organizations requiring a more secure data center with micro-segmentation.
  • Enterprise is for organizations that needs networking and security across multiple domains.

Coming from the one-fits-all license model where everyone gets everything, the question is – which features are missing in Standard and Advanced? Read more »

Check VMware HCL with PowerCLI (half-done, need assistance)

It’s on my to-do list for quite a long time: Create a Script that checks hardware against VMwares HCL. There are some problems that needs to be solved to automate the process. My main problems are matching the installed ESXi version to the release Level (eg. 5.5 U2, 6.0, 6.0 U1,…), integrating the HCL into a script and matching HCL to the physical hardware.

This is what I can do today with PowerCLI, basically by running “Get-VMHost | Check-HCL“:
I’m not sure if anyone is interested in automating HCL checks because I couldn’t find any scripts online. If you are interested, nice! I need assistance…

I need a larger pool of hardware information to know how hardware identifies itself. So if you want to support me, please run the following PowerCLI command and send me the output (Just Copy/Paste CSV file contents to my Contact Form, or send me an eMail. I will respond with the output of my script as shown above). If you don’t want to disclose your hostnames, just remove the “Name” part in the command, or replace the content with dummy-names.

Get-VMHost |select Name,Build,Manufacturer,Model,ProcessorType |Export-Csv hosts.csv -NoTypeInformation

If you are interested in how the script works, or the script/function itself, feel free to contact me. (It’s unfinished spaghetti code….)

Some additional features:


Display VMware HCL link (For further verification)


Display all supported ESXi versions for the hardware


Integrate VMware NSX in Log Insight

VMware Log Insight provides an easy, at a glance, view of an entire VMware environment including NSX and other components. Additional available content packs provide predefined knowledge about events. Problems with a vSphere environment can be identified by simply looking at the Overview dashboard.
nsx-log-insight-integrationThis post describes how to integrate all NSX Components into VMware Log Insight.

Read more »

Manage NSX 6 with Active Directory Users

When you login as a user from an external authentication source like Active Directory or LDAP, configuration of NSX is not possible. The Network & Security button is present, but no NSX Managers or other configuration objects are visible, despite the user has administrative permissions at the vCenter Object. Network & Security configuration is empty. The default vCenter Administrator can see everything.nsx-missing-permissions
VMware NSX has its own permissions structure, separated from vCenter Server Permissions.

Read more »

Ping from specific VMkernel adapter in vSphere 6

When troubleshooting network problems on ESXi hosts you want to specify the outgoing VMkernel adapter. As explained here you can ping from a specific VMkernel adapter with the -I parameter. In vSphere 6.0, or with VXLAN activated, this might not work as expected and displays the following error.

[root@esx:~] ping -I vmk1
Unknown interface ‘vmk1’: Invalid argument

The problem is related to the multiple TCP/IP Stack features introduced in vSphere 6.0. To ping from specific VMkernel adapters that are not in the default Stack (defaultTcpipStack) you have to manually specify the NetStack with the -S parameter.

Read more »

VMware NSX 6.2 Hardware Requirement Calculator

NSXBefore you install or upgrade NSX 6.2, consider resource requirements. One NSX Manager per vCenter Server is mandatory. At least 3 NSX Controllers are recommended. You can install one instance of Guest Introspection and Data Security per ESXi host and multiple NSX Edge instances per datacenter.

I’ve created a NSX Hardware Requirement Calculator. Enter the number of NSX Controllers, ESXi Hosts and NSX Edges you are planning to deploy. The tool calculates the total required Memory, virtual CPUs and disk space.

Read more »

VMware NSX 6.2 Beginners Guide – From Zero to Full Deployment for Labs

NSXVMware NSX is the SDDC technology of the future. What ESX was once for Servers, NSX is now for Networks. I highly encourage everyone to make yourselves familiar with this technology. NSX with all its features is quite complex, but the entry point is quite simple and requires only basic vSphere and networking skills. This beginners guide explains how to deploy NSX in your homelab even with limited physical ressources by downsizing NSX Manager and NSX Controller VMs. The guide starts at zero and quickly explains how to deploy NSX and connect your first Virtual Machine to a VXLAN based logical switch that is able to communicate to the physical world through an NSX Edge Gateway.

What do you need to create the Lab?

  • vCenter 6 with some physical ESXi Hosts
  • vSphere Distributed Switch (dvSwitch)
  • NSX Manager Appliance (Download: NSX 6.2.2)
  • There is no special physical Switch requirement

Read more »

Evaluate PernixData FVP with replayed Production IO Traces

Using synthetic workloads to test drive PernixData FVP might result into odd findings. The most meaningful approach to test FVP is to deploy the software to production in monitor mode, let Architect do its magic and enable acceleration after checking the recommendations after a couple of days. Despite it is possible to deploy FVP, test drive, and remove it, without any downtime to virtual machines, this approach might not fit to all environments.


If you have separate DEV/QA environments with sophisticated load generators, the solution is obviously. If you don’t have that, there is another option by record production I/O traces and replay them in a FVP accelerated test platform.

Read more »

Product End Of Support Matrix now available as JSON (incl. Script)

The database used at my VMware Product End Of Support Countdown is now available in JSON. The database is based on VMware Lifecycle Product Matrix and allows you to use the information in scripts or for automation purposes.


I’ve also written a small script to demonstrate what this information can be used for.

Read more »