Overview: NSX and vShield Edges support site to site IPSec VPN between Edge instances and remote sites. Behind each remote VPN router, you can configure multiple subnets to connect to the internal network behind an Edge through IPSec tunnels. These subnets and the internal network behind the Edges must have address ranges that do not overlap. You […] Read More
NSX Edge vs vShield Edge: Part 2 – High Availability
Overview: High Availability in both VSE and NSX Edges ensures Edge Network Services are always available by deploying a pair of Edge Appliances that work together in an active/passive HA cluster Pair. The primary appliance is in the active state and the secondary appliance is in the standby state. The configuration of the primary appliance is replicated […] Read More
NSX Edge vs vShield Edge: Part 1 – Feature and Performance Matrix
I was having a discussion internally about why we where looking to productize the NSX Edges for our vCloud Director Virtual Datacenter offering over the existing vCNS vShield Edges. A quick search online didn’t come up with anything concrete so I’ve decided to list out the differences as concisely as possible. This post will go through […] Read More
NSX vCloud Retrofit: Overlapping Networks in vCD with NSX Virtual Wires
Part 4: vCloud Director Overlapping Networks: vCloud Director has the ability to allow Overlapping Network segments configurable from the Administration Tab of the vCD UI. Traditionally for those using VLAN backed External Networks and Network Pools this would represent a potential risk to clients if admins where not careful provisioning network resources. If the same […] Read More
NSX vCloud Retrofit: vShield Edges Become Unmanageable – API Fix
If you are familiar with vCloud Director Edge Gateway Services you might have come across situations where Edges become unmanageable and you see the following options greyed out in the vCD UI. All Edge services remain functional, however no changes can be made. In environments where NSX has been retrofitted with an in place upgrade […] Read More
NSX Bytes: API Response Times and User Accounts
If there is one thing that working with NSX has done is drag me kicking and screaming into the world of APIs. Apart from being on the VCIX-NV Blueprint, in my current role it was becoming increasingly important to understand how our developers consume and manipulate the automation of our products and services…just being able to do […] Read More
NSX vCloud Retrofit: Upgrade Issue – Edge Gateway Unmanageable in vCloud Director or Deployment Fails
We have been working with VMware GSS on an issue for a number of weeks whereby we were seeing some vShield Edge devices go into an unmanageable state from within the vCloud Director Portal. In a nutshell some VSEs (version 5.5.3) where stuck in a Configuring Loop upon the committal of a Service Config change. […] Read More
NSX Bytes: 6.1.3 Upgrade and vSphere 6.0
Earlier today NSX-v 6.1.3 was released. This update brings vSphere 6.0 Support as well as bug fixes and a couple minor feature enhancements. https://www.vmware.com/support/nsx/doc/releasenotes_nsx_vsphere_613.html There is a warning in the release notes: NSX vSphere 6.1.3 is compatible with vSphere 6.0. However, the new vSphere features introduced in vSphere 6.0 have not been tested with NSX […] Read More
NSX Host Preparation: Cluster Not Ready – Legacy vCNS VXLAN VIBs Installed
I came across a situation today while going through an NSX Setup and Configuration where I came across a Cluster under the Host Preparation Tab that was reporting a status of Not Ready – Resolve and listed some hosts as Ready and Not Ready…What made this strange was that this was a fresh deployment of NSX over […] Read More
NSX vCloud Retrofit: Controller Deployment Internal Server Error Has Occurred
During my initial work with NSX-v I was running various 6.0.x Builds together with vCD 5.5.2 and vCenter/ESXi 5.5 without issue. When NSX 6.1 was released I decided to clone off my base Production Environment to test a fresh deployment of 6.1.2 into a mature vCloud Director 5.5.2 instance that had vCNS running a VSM […] Read More