News: VMwareGuruz has been  Voted Top 50 vBlog 2018. 

Cloud E2E

VMWorld 2017 – Don’t get confused with NSX-T 2.0

After busy VMworld 2017 schedule, today I’m at my desk to publish some good content and my manager is curious about the updates. When I mentioned VMware NSX-T 2.0 seems to be a promising solution for Docker/Containers networking, then he immediately reacted like “why there are two NSX versions released by VMware?”. I assume most of them has this question in their mind and here is the simplest answer: VMware NSX or NSX-V is designed for vSphere where it has one to one mapping with vCenter server to provide SDN (Software Defined Network) features. However VMware NSX-T (similar previous version NSX-mh multi-hypervisor) is designed to support vSphere and other hypervisors like KVM without one to one mapping with vCenter server.

 

NSX can now provide seamless network virtualization for workloads running on either VMs or Containers. VMs can be located either on-prem or on AWS. NSX will provide the entire feature set for either Vmware vSphere Hypervisors or KVM hypervisors. For native workloads on AWS, NSX will provide VMware NSX Secure Cloud to provide the same security and network virtualization that you would receive on your private cloud. NSX-T 2.0 has below features.

  • VM’s & Containers running at on-premises vSphere environment or AWS
  • CNI Integtration for Kubernetes
  • Automation with OpenStack
  • VMs & Containers running on ESXi or KVM
  • Multi Domain Networking
  • Improvements of On-Prem deployments
  • Support for Multi Off Site Clouds

 

 

NSX-T as a platform has been purpose-built to be ready for Infrastructure-As -A – Service (IAAS) providers to provide self-service functionality to their users. Additionally, deploying it for on premise infrastructure can enable you to provide a self-service model. NSX-T is also built for Developer Ready infrastructure. It can automatically integrate with Kubernetes and Redhat Openshift (Platform-As-A-Service) PAAS model providing the much-needed network policy. NSX-T contains both configurations and operational information built in. The operational state of the data center that is NSX enabled – whether in private cloud or public cloud – is available at the console. Based on our deployment experiences from the past – various parts of NSX-T has been optimized for east-west traffic between your applications. What’s new with NSX-T 2.0 slide from the presentation is here

 

 

 

“Be social and share it with social media, if you feel worth sharing it”

 

Related posts
Cloud E2E

vSphere Diagnostic Tool - Quick health checks via python script

Cloud E2ENutanix

Nutanix Support Engineer Diary

Cloud E2ENutanix

Nutanix AHV Networking (CLI commands)

Cloud E2E

How to become a Certified Kubernetes Administrator (CKA)?

Leave a Reply

Your email address will not be published. Required fields are marked *