VMware released NSX 4.0 a few days ago, and took that opportunity to rename the product “VMware NSX“, replacing the well-known NSX-T Data Center.
As many of you know by now, NSX-V (NSX for vSphere) is no longer supported since earlier this year and many customers have already started the transition to migrate from NSX-V to NSX-T. There is then no reason to keep the name NSX-T Data Center and it makes more sense to simply keep “NSX”.
What’s new in NSX 4.0
NSX 4.0 is a major release with new networking and security features as well as some enhancements.
VMware released with vSAN 7 Update 2 a new feature called HCI Mesh to provide better scaling capabilities in a vSAN environment.
Before vSAN 7 Update 2, there’s always been a very tight integration between vSphere and vSAN that made both products dependent from each other, and it wasn’t possible either to consume storage from one vSAN cluster to another.
Now things have changed with HCI Mesh as a non-vSAN Cluster can now take advantage of a remote vSAN cluster to start provisioning VMs to a remote vSAN datastore.
Recently I was in charge of designing and implementing a new vSphere and vSAN infrastructure for a customer.
Everything went just fine, except that we all have experienced many network outages due to misconfiguration of some Firewall Virtual Appliances where the whole infrastructure relies on.
As a result, all ESXi got disconnected from the vCenter and this happened many times!
Anyway, the network team in the end fixed the issue and the network was finally stable but I have to say that I’m not a fan of firewall virtual appliance as it brings some limitations and complexity. Unfortunately, those outages had a bad impact on the virtualization network as some warnings appeared showing some ESXi hosts out of sync with the distributed switch.
This could not be a big deal at the beginning but this kind of issue definitely needs to be addressed to avoid any network problem in the future.