An Edge Services Gateway allows to connect services running on Logical Switches outside of NSX based networks. I've explained the base installation from zero to the first ESG here. This post explains how to connect Web servers running on logical networks VXLAN to the outside.
In this example I'm running 3 nginx web servers on small Linux appliances connected to a logical switch.
Read More »Configure Basic Edge Load Balancing in VMware NSX
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… Read More »How to vote for Top vBlog 2016 @vsphere-land.com
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.
According to VMware, these offerings are aligned to the following requirements:
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 »Which Features are missing in NSX Standard and Advanced?
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… Read More »Check VMware HCL with PowerCLI (half-done, need assistance)
VMware Log Insight provides an easy, at a glance, view of an entire VMware environment including NSX and other components. Additionally available content packs provide predefined knowledge about events. Problems with a vSphere environment can be identified by simply looking at the Overview dashboard.
This post describes how to integrate all NSX Components into VMware Log Insight.
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.
VMware NSX has its own permissions structure, separated from vCenter Server Permissions.
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 10.1.1.1
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.