VMware NSX Reviews

The ease in which to install this product and make it work straight away without minimum changes in your physical network and is simply astonishing. The only thing you need to do when installing this product is change your MTU to 1600 (jumbo frames). It provides microsegmentation and good security features for north-south and east-west traffic across your SDDC. The performance you obtain at the virtual layer and traffic crossing for your VMs gets improved dramatically because the traffic doesn't leave the hypervisor. I'm not a network guy myself but NSX makes it really easy to understand how the virtual network pins together and how you can manage the traffic and security within your VMware deployment without the hassle of changing VLANs, adding unnecessary protocols for discovery, etc.

Encapsulating the traffic using VXLAN is a great addition. It extrapolates the number of VLANs that you can stretch to an almost infinite number of VXLAN (millions of VXLANs). In abstract, you are dealing with numerous VLANs every time you want to send traffic from one VM to another, basically VMs on different hosts within the same datacenter will be connected to the same logical switch and traffic is advertised via unicast traffic from the NSX controllers to let every body know in the environment "who is who" to minimize the amount of multicast traffic.

We haven't installed this in our environment yet. We have a major lab to provide our Ci-Dev team a sandpit to test apps and its security when deploying a three-tier application on our customers and test every single connection and performance before handing over the application to the customer.

The upgrade process is okay overall, but we have encountered issues every time when upgrading with the ESXi hosts VIB installation packages not being properly deployed, and after upgrading NSX manager, the ESXi hosts still uses the old version. This causes additional steps to manually remove those old VIBs from the ESXi, reinstall them, and try again. In some cases, we had to uninstall and install them from scratch NSX and restore from backup, which in a real world scenario won't be desirable to do. You would like to have an in-place a seamless upgrade from one version to another, especially if you are changing minor versions (e.g., 6.3.1 to 6.3.2).

Six months now.

The upgrade process is okay overall, but we have encountered issues every time when upgrading with the ESXi hosts VIB installation packages not being properly deployed, and after upgrading NSX manager, the ESXi hosts still uses the old version. This causes additional steps to manually remove those old VIBs from the ESXi, reinstall them, and try again. In some cases, we had to uninstall and install them from scratch NSX and restore from backup, which in a real world scenario won't be desirable to do. You would like to have an in-place a seamless upgrade from one version to another, especially if you are changing minor versions (e.g., 6.3.1 to 6.3.2).

A very stable product, it is more mature than it was four years ago when it first came out. The performance you get with this product is near-line rate.

If you have a large environment, the sprawl of Distributed Logical Routers or logical switches can be hard to manage, but you will have the same issues in a physical network.

We have a direct line with VMware support and with the specialized engineer who provides support on NSX. We haven't had to open a support call yet, but the engineer we've dealt with is very capable and knowledgeable on the product.

Excellent. VMware engineers are top of the line. I haven't met one engineer who doesn't know the product well that they support.

Nope, never used a network virtualisation product before.

It was straightforward. Just a couple of install media and .ovf files and you're done. The interesting part comes after installation when you need to define your virtual network architecture and how you're going to deploy rules and connectivity for your VMs.

In-house deployment. We're a large VMware shop and know VMware products well.

Not applicable for this product yet.

We got the licenses from VMware as part of the NFR agreement, but you will require a medium infrastructure to deploy this initially. Lot of memory and CPU are required to have the product run smoothly

No, there are no other products in the market that provide network virtualisation as far as I know.

Download the installer, try it, and you will love it. Some hardcore network administrators will say it is not the same, and of course is not the same, but it is a new way to do things in the network space. It is the way of the future when deploying large networks in Software Defined Data Centres.

We are using VMware NSX for network security.

It is used for Tanzu, it is successful for our Kubernetes environment.

The most valuable features are ease of use and user interface.

The security feature for the Kubernetes environment can be improved.

I have been using this solution for approximately one year.

The solution is stable.

The solution is scalable. 

We have approximately 10 users using this solution in my organization.

We have been satisfied with the technical support. They were able to solve our problems. However, they could be faster.

Positive

The installation is straightforward and it took approximately two days.

We did the implementation ourselves. We have a manager and an administrator that does the maintenance of the solution.

There is a license required for this solution and there is also a support license available. 

The price of the solution could be better.

I would recommend it to others.

I rate VMware NSX ten out of ten.

I primarily use NSX for micro-segmentation, security, and load-balancing.

NSX's stability could be improved.

I've been working with NSX for six years.

I would rate NSX's stability eight out of ten - there's room for improvement.

I would rate NSX's scalability eight out of ten.

The initial setup is easy and takes between one and five days.

I would give NSX a rating of seven out of ten.

Some of NSX's most valuable features are:

• Its distributed firewall
• The we can actually extend Layer 2 networking across datacenters, and also Layer 3 networking, which comes along with it.
• The routing and switching.

They could branch out to the physical layer. Today, it's just the virtual layer, and they're starting to talk about the physical layer. We'd like to see the physical layer incorporated.

We've been using NSX now with Layer 2 stretching for approximately 10 months. We're getting ready to really ramp up the DFW, which is the distributed firewall piece, which we and our security team are very excited about.

NSX is a very stable product.

We've already scaled it across two data centers. We'll be incorporating two additional data centers, to give us that footprint, or IP address migration across four data centers. So, it's quite scalable.

The tech support for NSX is awesome. We are a premier production customer for VMware, therefore the tech support and the tech support representatives don't start a lower level. We start at the mid-level of the tech support engineers. Thus, we get answers very quickly. We also work with our technical account manager who knows what we're doing and what we've got coming up, so he's able to push things for us on the tech support side.

Our tech support's awesome.

The most important criteria when selecting a vendor (like VMware), it's important to us that they have the following:

• Their name recognition.
• The support that they provide.
• Their placement in the industry as a leader.
• The things that they're doing with NSX, which are phenomenal.

We're a supporter of VMware, and likewise they're a supporter and a partner with us and what we're doing.

It's really a great product. It fits all of our needs. Everything that we've asked it to do or asked VMware to help us get done with it, we've been able to do. Therefore, we're very excited about the product.

We are using VMware NSX primarily to enable address mechanisms in terms of having to provide the workloads publicly.

In India and similar regions, the CSP faces a significant challenge. The primary issue is related to network address cancellation, which requires private to public IT mapping and the use of the CSP's own IP address space. VMware NSX has been effective in addressing this problem, along with the virtual firewall's ability to function as a network firewall. This has helped to minimize the need for customers to take responsibility for their network security. In these regions, customers expect full-service solutions and do not typically embrace DIY approaches. An analogy for this situation is that if a customer buys a toothbrush from you, they might expect you to brush their teeth for them.

VMware NSX's overlay network is its most valuable feature, as it aligns with any network philosophy and allows for efficient addressing mechanisms. Additionally, the ability to extend the on-premise network into the provider space is beneficial. There are many features provided.

There is room for improvement in VMware NSX's workload management, particularly in the orchestration layer and in managing workloads across multiple clouds.

Additionally, where workload management could be improved is in the ability to federate workloads seamlessly between different control panels. For example, if I am using VMware vCenter as my control panel and have partnered with a non-VMware provider, I should be able to manage my workloads as a customer without having to worry about orchestration. This is an area where there is potential for improvement.

I have been using VMware NSX for approximately eight years.

The scalability of VMware NSX is similar to other solutions. It is scalable.

I rate the scalability of VMware NSX a seven out of ten.

We did not have local support to go to in India. There is no support center here.

I have used Qumulo but we needed to buy a switch for it which was not favorable.

The initial setup of VMware NSX is not complex. If someone has an understanding of how networks work it will be easy. It can take some time to be completed. For example, to configure the solution with the correct commands.

The implementation time can vary depending on the clarity and complexity of the requirements.

When comparing VMware NSX to OpenStack, VMware NSX is simpler to implement.

I rate the initial setup of VMware NSX a six out of ten.

The price of VMware NSX is optimal. Additionally, the price of the solution can be negotiated with the vendor. Many areas of the solution can impact the cost, such as features, time for onboarding, and support needed.

We evaluated other options before choosing VMware NSX.

VMware is a pioneer in virtualization, they are good at what they do. They score high overall in capability.

I rate VMware NSX an eight out of ten.

It is helping me get an entire blueprint done of the source and the target. I was able to make it into a catalog and can set up anything on the cloud quickly. 

The best part is the blueprint creation where I can create their things and then move on to the target environment.

The price is pretty high and their product stack forces me to use the feature set compared to all the others out there in the market from India. They could do more with cloud management, I need some third-party tools.

I have been using VMware NSX for the past four years.

VMware NSX is a stable solution.

The scalability is not a problem.

It was complex, but we worked on all the templates and now it is easy.

I would recommend getting your case worked out well before you get into any customer environment. When it comes to an out-of-the-box feature set on the website, it is not how it really works. Do the POC before you go into a real-time production implementation. I would rate VMware NSX an eight out of ten.

We use NSX as a security solution. The solution is deployed on-premise. We are using version 6.4 of NSX. 

The solution is easy to use and is good for management control.

It isn't easy to deploy.

I have been using VMware NSX for almost 10 years.

We currently have 2,000 users.

The solution is scalable.

I haven't used technical support. If I have a problem, I find out what the best practice is.

We previously used a different solution for server virtualization, but we switched to NSX.

The solution was easy to install but not easy to deploy. 

We have a technical team. The time it takes and the amount of people needed for maintenance depends on the solution that is deployed. Sometimes it is easy, and sometimes it takes more than one day.

The subscription is on a yearly basis.

I would rate this solution 8 out of 10.

Our primary use case is moving from physical to VM infrastructure.

This solution has given us the ability to move from a physical to a virtual server estate with all of the expected VM benefits of decoupling servers from dedicated hardware.

The most valuable feature is the ability to create, develop, and deploy servers in minutes to hours, rather than days.

It could be cheaper!

I have been using VMware NSX for seven years.