VMware NSX Reviews

We use the solution for the software-defined network. 

I am impressed with the tool's protection. 

The tool's setup is complex and we need support to implement it. 

I am working with the product for two months. 

The solution is stable. 

My company has three users for the tool. We plan to increase the usage of the solution in future. 

The solution is difficult to deploy due to network complexity. The deployment took three months to complete. We had around five to seven resources involved in the product's deployment. They were mainly from the roles of network security and infrastructure. We created a plan and deployed the solution following it. 

Our partner helped us with the solution's implementation. 

The tool's pricing is reasonable. 

We compared the solutions from Cisco and Nutanix. We chose VMware NSX due to its price. 

I would rate the solution an eight out of ten. 

We use this solution for network virtualization alongside Nutanix and for the firewall blueprint. I'm an IT manager. 

This product is like the layer between traditional networking and virtualization. It gives you the flexibility to deploy and have network virtualization on different types of firewalls. We implemented this solution when we moved to the private cloud. 

The setup of the solution could be simplified.

I've been using this solution for two years. 

We haven't had any issues with stability. 

The solution is scalable, but we haven't tested that yet. We have three network engineers using the product. We don't plan to increase usage in the near future. 

The response time of the technical support team could improve. We also sometimes had the feeling that they didn't properly understand the issue.

Positive

The initial setup is not that straightforward. We used a consultant and even then deployment took a full week. It wasn't easy. 

This is a good solution if it fits your requirements. You can achieve a lot if it suits your needs. I rate this solution eight out of 10. 

VMware NSX can be used for micro-segmentation in the network space.

The solution is very good at micro-segmentation.

VMware NSX provides a lot of automation capabilities, but there is still room for improvement.

I have been using VMware NSX for approximately 14 years.

The stability of VMware NSX is good.

VMware has been the market leader for stability. If you look at the competitors,  I would rate that it's one of the top five solutions which I have worked on in this space.

VMware NSX provides excellent support.

If you are a new user and are looking for overall automation skills, then VMware vRealize Automation fits the purpose.

If the new user is looking for micro-segmentation in the network space, then  VMware NSX is the best solution. It has a very good capability in terms of micro-segmentation. Although, there are certain capabilities of the Layer 7 functionality, which other solutions have available, specifically from the Cisco stack. However, VMware NSX is an overall good solution when it comes to virtualization and Automation.

I rate VMware NSX a nine out of ten.

Our customers had multiple data centers in different locations. Now, with NSX we built one fabric over an IP transport, like WAN internet. When we created the switches, it spread out over the data centers which are the configuration and the management of the underlying network for the VM workloads.

The reusability of the objects for the switches has improved our client's organization. For example, if I do some sort of vMotion, there is no need to recreate the portal groups on the other sides. We have one centralized NSX Manager which is managing those controllers on those sites.

The most valuable features would be the easy management and the possibility of using our existing vSphere environment so that we don't need to purchase a new hardware.

Layers 4 and 7 load balancing are good. We like that it's integrated with the vSphere. This means that we can see its full capabilities because of the full visibility of the kernel on the NSX management.

Microsementation is really powerful. With the existing networks of the legacy networks, we need to build a firewall between the segments in order to do microsegmentation but now having, for example, one VLAN connected to multiple VLANs, I can do micro-segmentation between the workloads even with the ushering the same segments.

I would like them to make integration with other vendors easier.

It's pretty stable. Just deploy it and just forget about it. It's also robust, flexible, and scalable. 

Scalability is really easy. We can scale within an hour. We can scale either new controllers or add new hosts to the fabric.

We haven't had to use their technical support yet, which is a good thing.

I'm involved in the decision making. My boss would say that it's time to advance the customer so we'll look into a solution.

We were already a VMware-based customer so our first option for an SDN solution was to go with NSX. 

The initial setup was straightforward. It follows a certain structure and you won't miss a step. It's all on the same level, step by step.

It has saved us CapEx. They should adjust the license for NSX so that we can invest in the infrastructure or purchasing of new hardware. This solution is reasonably priced compared to other vendors.

Our customers usually compare NSX to Cisco ACI. The main issue is the underlying network that VMware does not provide visibility to. They chose NSX because they were already VMware customers and they already had vSphere. The second reason they chose NSX is because of the powerful features like microsegmentation, as opposed to relying on other vendors to manage the microsegmentation feature.

I would rate this solution an eight because of its ease of deployment. I'm a partner so this is what I mostly care about. Also because of the ease of scalability.

If you're looking into NSX or similar solutions I would recommend you to first learn about vSphere and other VMware products because it's essential in order to implement NSX. Without that knowledge, it would be hard for you to understand.

And to those who think NSX is complex I would say it's not. You need to try it and see.

I sell to a lot of customers in the DoD. NSX has really become part of their ecosystem, especially for the tactical customers in the DoD. It's very important for them to have small footprints and have as much services in their servers, as possible. NSX has fit this role really well for them.

• Going through and getting more features sets from the routing protocols is definitely necessary for the future.
• Being able to properly manipulate BGP
• Getting multiprotocol BGP into the stack
• A little bit better redistribution

As a CCIE, I like to have all my tool sets, and there are some things which NSX is missing right now.

It's missing some more advanced features. As an engineer, we need those tools. We need to be able to manipulate routes. We need to be able to set traffic the way that we need it to be. Especially as we interact with other vendors, sometimes it makes it difficult to have to do some workarounds. Once VMware flushes out the RFC for things like BGP and OSPF, it will be better.

We've tested it in our labs, and our customers are running it now. It is definitely stable, and it does what it's supposed to with no unnecessary crashes.

It's one of the major benefits of it. The distributed nature of NSX is really what the customers are interested in: spread into workloads across a lot of servers and not working out one host too hard.

All my customers seem to be very happy with the technical support. Anytime they call up, everything is very responsive and the engineers are intelligent. They know how to help them solve their problems.

NSX is one of the simplest network solutions that I've ever worked with.

I did a demo for our company's engineers about a year ago, and in 45 minutes, I stood up a cluster and had the VXLAN and some of the firewall policies, up and running in a 45-minute demo. It's really easy to use and everybody walked away from it knowing how to use NSX just from a 45-minute presentation.

It's very important for us to have good relationships with VMware from a reseller standpoint, and especially in the DoD, we have great reps. VMware is probably a 90% of the DoD networks. It's definitely not just reputation-wise, but they've been there for seven to eight years now and everybody knows that VMware is the enterprise solution for virtualization in the DoD.

NSX is a virtual network, and now is the right time for it. Technology-wise, it's actually an advancement in comparison with other solutions. We've been studying it, and so far, so good. NSX is the superior product when it comes to software for virtualized networks.

The non-enterprise version of the solution should be improved.

I want to see the solution expand to more than just the network, for example, perhaps it could provide some VLAN technologies.

I have been distributing this solution for over six years.

I believe the product is very stable.

The product is very scalable. I don't think NSX would have any problems with growth if a company wanted to expand their network and business. One person is enough to manage this solution.

Here in the Philippines, we need more technical support. I don't think they have good support here. There aren't any experts on NSX, only the distributor and reseller, so we have to really invest in training for us to able to understand the product.

Our team is already trained, so the setup is straightforward.

The licensing is renewed every three years. The cost for implementation and renovation are a huge portion of that price.

I think they need to market the solution more so that it can be accessible to more customers, because few are very familiar with it. It's hard to market it because we are provided with less marketing information about it, but in order to grow the product, it has to be properly marketed.

If you are looking for new technology of the future, NSX is one of them, and it will cost you less in power consumption since it's a virtual network as opposed to a pure physical network, which consumes more energy. That's a main advantage, that the operating expense will lessen while at the same time, the technology is great and is a secure network. When you're talking about virtual networks, I think NSX is one of the greatest products and will soon be the leader in the market.

I would rate this solution as a seven out of ten.

Our primary use cases of this solution are hybrid, cloud, private cloud, and automation.

VMware NSX has improved our customers' organizations through its automation of security policies, delivery of policy by intent, rapid provisioning, and removing security as being a blocker.

Microsegmentation and automation are two features we have found to be the most valuable. 
The microsegmentation feature is a mature feature used in NSX-V and NSX-T.

We are trialing Layer 4 and 7 load balancing with this solution, as it's very new.

The next release of NSX should try to make Kubernetes and container integration a little easier than it is now. It's quite a complicated process.

I would rate this solution an eight because it doesn't have Kubernetes integrations yet, and it isn't multi-federated. Those are some of the things that need to be added to the product. 

This solution is stable and robust. We've done failover testing and it kept working. 

I have found this solution to be scalable, more so now with NSX-T than NSX-V.

Their technical support team is firm. It's mature, and they've got a good support team.

Business is demanding more agility and capability than ever before. NSX offers solutions to those business-level problems.

The initial setup was straightforward. You just have to click it and follow the manuals. Deploying the infrastructure code can be more complex.

We looked at Nuage and Cisco. We decided to go with NSX because they have a good understanding and a strong VMware stack.

I would advise a colleague at another company who is researching NSX to know how the technology can answer their customer's business use cases. For those who say NSX is complex, I would agree that it can be complex but you can abstract that complexity through automation and Service Catalogs to make it easier for end-users to consume.

The most valuable part of NSX is it's very scalable and automated. Our change request time is really low.

For the most part, it's very stable.

The only hiccup is sometimes during an upgrade, there are hurdles that you can have during that time, but overall it's very stable.

Since we're almost 100% virtual, it's been very scalable for us.

Sometimes, it can be difficult to get to a higher level engineer if you need to, but it takes some work to make that case. Usually it happens, but it's a little difficult.

It seems to be very straightforward. Usually a lot of it's handled by the installer. Yeah, very straightforward. As long as you read the design guide, it's easy.

An important reason for selecting was VMware because they're the hypervisor we use and we see them to be a very valuable asset in purchasing something like NSX, and because they're the owner of the hypervisor and they have direct access into the hypervisor. That's very valuable for us. We foresee it being a very reliable product into the future.

An important reason for selecting was VMware because they're the hypervisor we use and we see them to be a very valuable asset in purchasing something like NSX, and because they're the owner of the hypervisor and they have direct access into the hypervisor. That's very valuable for us. We foresee it being a very reliable product into the future.

They developed the hypervisor, which is very valuable to us, because it has saved us a lot of money just on the micro-segmentation piece. That's basically all we use at this point, but the product has more than paid for itself just with that part of the product.