We can deliver the network that customers need quickly and safely. That is most important.
Cloud Engineer at IBM
Video Review
We can deliver the network that customers need quickly and safely
What is most valuable?
What needs improvement?
There is one feature I'm finding with VMware which is special for us from IBM with JIRA routing protocols. This is in the future that they are planning, especially right now with our compatible AWS. AWS is good, understood, except for the software to improve, probably with Amazon right now doing this partnership. VMware and access are going to be improved for that.
What do I think about the stability of the solution?
It's totally stable, because right now it's running version 6.3. It's very mature. Even the versions with VMware 5.5, 6, and 6.5 are very stable right now. It's becoming more open to other environments, too. It's not only working with VMware, but also with Red Hat and Ubuntu. It's an amazing product.
What do I think about the scalability of the solution?
Totally scalable. I almost can tell this is the first real multi-tenant product from VMware that will scale out and do real multitenancy.
Buyer's Guide
VMware NSX
January 2025
Learn what your peers think about VMware NSX. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
How are customer service and support?
Tech support is nice. It could be a little bit better. Simple, since this is a new product, you don't have too much specialists over the world. Because it is a mix between the virtual world with VMs, and now networks, it's networking virtualization. So, VMware with NSX is being a pioneer. They are improving their support every day.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
System Engineer at a tech services company with 501-1,000 employees
It is robust and easy to implement
Pros and Cons
- "It is easy to implement it."
- "If there are other solutions already in place, it can be difficult to implement."
What is our primary use case?
We use it for microsegmentation, and it has performed well.
How has it helped my organization?
We use this in combination with VMware Horizon View. With Horizon, we have an isolated environment.
What is most valuable?
The most valuable feature is to control application behavior.
It provides us with features that other products have not.
What needs improvement?
If you start with a new or greenfield environment, it is okay to implement. However, if there are other solutions already in place, it can be difficult to implement.
What do I think about the stability of the solution?
The stability is very good.
What do I think about the scalability of the solution?
Because it is in the VMkernel, it is robust.
How is customer service and technical support?
I have no contact at the moment with VMware support about NSX.
How was the initial setup?
It is easy to implement it.
What about the implementation team?
I am the partner. I work with the customer to do the deployment.
What other advice do I have?
I would recommend it to another person.
We do not integrate it with vCloud Director.
I don't use load balancer at the moment.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Buyer's Guide
VMware NSX
January 2025
Learn what your peers think about VMware NSX. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
System Administrator
we can deploy many VMs faster but we have had recent issues with stability
Pros and Cons
- "We are happy with the scalability."
- "It was stable for one year, there was no impact. In the last two months, we had two big incidents."
- "We've have had good and bad experiences with them. We don't always find them to be so impactful. Sometimes the support guy isn't so on top of resolving the issue and it can take a while to sort out."
What is our primary use case?
My company's primary use case for this solution is the microsegmentation. It's futuristic.
How has it helped my organization?
VMware NSX has improved our organization in the way that we can now deploy many VMs faster than before and so we are scaling up much faster.
What is most valuable?
We like that NSX is faster. My colleagues manage their own firewalls so they can freely deploy their VMs. The ability to freely deploy is one of the most valuable features.
What do I think about the stability of the solution?
This solution is robust and agile. It was stable for one year, there was no impact. In the last two months, we had two big incidents.
What do I think about the scalability of the solution?
We are happy with the scalability.
How is customer service and technical support?
We have needed to use their technical support. We've have had good and bad experiences with them. We don't always find them to be so impactful. Sometimes the support guy isn't so on top of resolving the issue and it can take a while to sort out.
What about the implementation team?
It was deployed by a VMware consultant.
What other advice do I have?
I would tell people who say that NSX is complex that it's not as complex as they think and they should definitely consider this solution.
I would have rated this solution a nine, but in the last two months, we have had two incidents with them.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Practice Manager - Cloud, Automation & DevOps at a tech services company with 501-1,000 employees
NSX for vSphere vs. NSX Multi-Hypervisor
Originally posted at vcdx133.com.
This post provides a Tech101 breakdown of VMware NSX. If you have heard the buzz-word “NSX” or “Network Virtualisation” and want to learn more about it, this post is for you.
VMware NSX has two distinct variants – NSX for vSphere (NSX-v) and NSX Multi-Hypervisor (NSX-MH). The most feature rich version is NSX-v (as you would expect) and the most flexible and vendor agnostic is NSX-MH (albeit with less features). Currently these are separate binaries that you download and deploy, however there is talk that in the future it will be a single binary set with a V/MH software setting during deployment.
A little bit of history will also clarify things. VMware acquired Nicira in 2012 and integrated/developed the NSX product suite by combining VMware’s vCNS (aka vShield Edge and App) with Nicira’s NVP. So if you understand vShield, it will give you a good start to mastering NSX.
The diagram below illustrates the NSX architecture, complete with physical infrastructure. Note, storage virtualisation has been deliberately left out of the diagram since it is not in-scope. The “P2V” lines denote the possible NSX overlay to physical network integrations.
NSX for vSphere (NSX-v)
NSX-v has the following components:
- vSphere ESXi – server hypervisor.
- vSphere Distributed Switch – the advanced Layer 2 virtual Switch that VMware provides with the Enterprise Plus licence (you cannot use the vSphere Standard Switch with NSX).
- NSX Manager – management interface of NSX, presented via the vSphere Web Client and has a northbound NSX API.
- NSX Controller – the control plane of NSX which also has the northbound NSX API.
- Logical Switch – VXLAN tunnels that run across disparate networks.
- Edge Services Gateway (ESG) – provides L3-L7 network services to the outside world.
- Distributed Logical Router (DLR) – provides L3-L7 network services to the physical and virtual infrastructure via a hypervisor service for the data plane and a virtual appliance for the control plane.
- Distributed Firewall – this is a service that runs on ESXi and provides micro-segmentation of virtual infrastructure
- Third Party integrations – advanced L3-L7 services provided by Third Parties via the NSX API. eg. Palo Alto Networks, McAfee, Trend Micro, F5, Citrix, Silver Peak, etc.
- Physical Network – traditional core, aggregate, distribution, access or Clos-type Leaf & Spine architectures
- Virtual overlay to Physical network gateways – the NSX virtual overlay integrates with the physical world via a gateway. eg. Routing, L2 Extension, VXLAN, etc.
What are L2 to L7 services? VLAN, VXLAN tunnels, Network Firewall, IPS, Application Firewall, NAT, Routing (OSPF, BGP, IS-IS), Load Balancing, SSL VPN, IPSec VPN, Route redistribution, etc.
NSX for Multi-Hypervisor (NSX-MH)
The NSX-MH has the same functional components, except it uses Open vSwitch (instead of vDS) with KVM, Hyper-V or XenServer and does not have a Distributed Firewall (no micro-segmentation).
Why do it this way?
You may have heard about the “Goldilocks zone” (not too hot, not too cold, just right – used to describe Earth’s placement in the solar system for sustaining life). The hypervisor is the “Goldilocks zone” of the Data Center, it is the natural meeting place for the Software Defined Data Center (SDDC) – Compute, Network and Storage.
If you understand the benefits of server virtualisation with vSphere (abstraction of the Operating System from the hardware, etc.), you can apply the same logic to network virtualisation. There is also the driving force of creating blueprints within the Service Catalogue of the Cloud Management Platform and linking polices (compute, network, storage and security) to the blueprint.
Weaknesses
- The biggest weakness of NSX – no associated hardware, since VMware is a software company, is also its greatest strength. You can run NSX across any physical network (as long as it meets the fundamental requirements of scalability, performance and reliability) and use it to connect disparate networks together.
- Because NSX is software, it cannot match dedicated physical hardware in terms of performance, however this weakness is balanced with flexibility and scale. Ensure that your SDDC is designed to match your business requirements – this way the risk of lack of performance is mitigated.
- NSX on its own is not the greatest use-case, you really want to use it to complete your SDDC solution (ie. Cloud Management Platform, Compute Virtualisation, Network Virtualisation, Storage Virtualisation and Service Catalogue).
Disclosure: I am a real user, and this review is based on my own experience and opinions.
System Advisor IT at CRIF India
Support need improvement, but it is stable, and easy to install
Pros and Cons
- "It's a beneficial tool."
- "The support needs improvement."
What is our primary use case?
Load balancing is achieved using VMware NSX. The load balancing feature provided with VMware vSphere is called NSX.
While using the virtual server with your on-premises trusted internal network, you can set up rules to prevent them from doing specific activities.
What is most valuable?
VMware NSX is a very good product.
It's a beneficial tool.
What needs improvement?
VMware NSX needs improvement.
For how long have I used the solution?
We have been using VMware NSX for a couple of years.
We are using the most recent version.
What do I think about the stability of the solution?
I have no issues with the stability of VMware NSX.
What do I think about the scalability of the solution?
VMware NSX is a scalable solution.
NSX is not a user, product. NSX is for securing your virtualization platform.
How are customer service and support?
The support needs improvement.
How was the initial setup?
The initial setup is straightforward.
What other advice do I have?
I have not yet fully explored all that this solution provides. I am still analyzing it. From the knowledge and experience that I have today, I would recommend this solution.
I would rate VMware NSX a five out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Architect Enterprise Business at Mindfire Technologies LLC
Great for protecting virtual machines; stable and reliable
Pros and Cons
- "Provides protection for virtual machines."
- "Quite a complex solution."
What is our primary use case?
Many of our customers are moving to these kinds of options in order to reduce the number of physical devices and to increase security. I'm an architect of enterprise business and we are an enterprise partner with VMware.
What is most valuable?
The solution is valuable in that it makes it very easy to protect virtual machines
What needs improvement?
The product is quite complex and that could be an area where improvements could be made.
For how long have I used the solution?
I've been using this solution for over a year.
What do I think about the stability of the solution?
This solution is stable.
What do I think about the scalability of the solution?
The solution is scalable. I've implemented it in an organization with 2.000 servers and it's fine. That is my experience. I don't have experience with larger environments.
How are customer service and technical support?
We are directly linked to VMware so we haven't needed to contact the technical support.
How was the initial setup?
We did face some challenges with the initial setup.
What's my experience with pricing, setup cost, and licensing?
The cost of the solution is a little high, particularly given that most people will not use all the features of the product. If a customer does use all the options, it is a very cheap solution but that is unlikely. For a regular user looking for normal switching, the price feels high. If it's implemented properly you can reduce the cost.
What other advice do I have?
This is a good product and I highly recommend it.
I would rate this solution an eight out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
aucun at None
Micro-Segmentation helped us secure our organisation. The Distributed Firewall is simple to add and rules are easy to implement
Pros and Cons
- "We secured our organisation with Micro-segmentation."
- "The Distributed firewall is simple to add to the network and rules are easy to implement."
- "It lacks full knowledge of physical side of the network topology."
What is our primary use case?
I was an intern at a relatively large company here in Morocco, and NSX is a great solution.
How has it helped my organization?
NSX has improved our organisation in many ways, by securing it with micro-segmentation, and by allowing us to implement logical equipment in a matter of seconds instead of waiting for the physical material to implement and configure.
What is most valuable?
The Distributed Firewall is simple to add to the network and rules are easy to implement on it.
What needs improvement?
It should be more adapted to the physical side of network topology in order to prevent unavailability.
For how long have I used the solution?
Trial/evaluations only.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Specialist at a tech services company
Very easy to use out-of-the-box and doesn't have a steep learning curve
Pros and Cons
- "The ability to scale from different clouds. At the moment, the scalability of the product is the number one thing that I saw."
What is most valuable?
The ability to scale from different clouds. At the moment, the scalability of the product is the number one thing that I saw.
Right now, we're doing a private cloud, since we're government. In the future, we may want to look at public, but probably not.
How has it helped my organization?
It has the potential to improve the way we function by having our different clouds be able to easily communicate back and forth. Right now, it takes a lot of work to do collaboration from our test lab, to our production, and to do anything in-between. It has the potential of giving us streamline migrations from the test lab to production.
What needs improvement?
Pricing and licensing could be improved as we are a government entity. Lower pricing could always help.
For how long have I used the solution?
We just got it.
What was my experience with deployment of the solution?
About five to 10 people set new products up and we kick them down the road all the time. As soon as we see something real good we call in some users and it gets big. They call their managers and it grows; it's like a wildfire.
But it will start off as a spark, and I'm the spark.
What do I think about the stability of the solution?
It is pretty good. It cuts down on duplication. Right now, I have tools in the lab, have tools in pre-prod, and have tools in production.
Right now and well in the future, if we implement it, we'll be able to have the same tool set be applied through all regions and transfer and not have duplication. It will outline and teach our users how to operate them. Therefore, we will have one set of tools, one set of instructions, and they can operate in all three environments.
What do I think about the scalability of the solution?
Scalability definitely looks awesome. Again the three environments we'll be able to use one set of tools. Everybody would be familiar with it. It won't operate this region and a different way in another region because it's from another vendor, where one set of tools would be able to pass throughout all of our regions.
Our scale right now is about 60 users (the production and the customer).
Which solution did I use previously and why did I switch?
We had multiple solutions.
We were making do with what we had, but again, going to different conferences and seeing what other people were using. We got curious and our vendor said, let's demo it. So, we made time for it, and after we made time for the demo, we realized we should have been doing this two years ago.
How was the initial setup?
I was involved in the initial setup. It was straightforward. We did it with our government PFE.
What about the implementation team?
We do have partners, who are knowledgeable, did offer to come in and set it up for us. We had access to our online lab from our vendor, so they had to set it up, connect it, demo it, and see how it runs. Though, we set ours up.
Which other solutions did I evaluate?
Dell EMC and Symantec.
What other advice do I have?
It's a solid product. Very easy to use out-of-the-box. It didn't have a steep learning curve, and we're still finding things that we can add-on.
I would encourage anyone looking to buy the solution to demo it in a lab, or come to a conference and see it. They should see how it would fit in their environment, and don't be overwhelmed or overworked by adding another solution because the results pays off.
Most important criteria when selecting a vendor:
- Price
- Security
- Meeting the application requirements.
- Technical support.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free VMware NSX Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2025
Product Categories
Network Virtualization Cloud and Data Center Security Network Traffic Analysis (NTA) Network Detection and Response (NDR) Network Automation Microsegmentation SoftwareBuyer's Guide
Download our free VMware NSX Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What is the biggest difference between VMware NSX and Meraki SD-WAN?
- What is the biggest difference between Cisco ACI and VMware NSX?
- Is it possible to install VMware NSX outside of the VMware ecosystem?
- What are the biggest differences between Cisco ACI and VMware NSX?
- What are the biggest differences between Cisco ACI and VMware NSX?
- When evaluating Network Virtualization, what aspect do you think is the most important to look for?
- Why is Network Virtualization important for companies?