VMware NSX Reviews

We use this solution for extended on-premise capabilities. We've been using it for five years.

I use the cloud now but in the past, we were able to create very specific segments for each part of the company. 

We like that we can split networks. Layers 4 and 7 are nice. We like that load balancing is easy for the person running it and certain features like the web bouncers F5. 

We like that the microsegmentation feature is easy to use. It is easy to segment the network.

At the moment it hasn't helped us prolong our hardware refresh.

You can easily integrate this with other VMware products. It is a robust solution.

The scalability is good. 

I never had to use their technical support. 

We were trying to save money and trying to use a more flexible solution so we decided to go with NSX as opposed to another hardware or solution.

I found that it was easy to install. In fact, I installed it myself.

We saw ROI within the first year and a half. 

It has helped us save CapEx but I'm not sure exactly how much. 

I rated this solution a nine because it's easy to use. It has a lot of capabilities, like microsegmentation, which is very good.

If you're worried that NSX is too complex, I would tell you to take another look. If you compare NSX to a similar solution you might find it to be a bit more complex. Usually, the guy that comes in to implement NSX isn't the network guy and will lack the knowledge for the program. He can lack the knowledge for this program and will therefore think it's complex. You need somebody with network experience. 

We support clients who use on-premise VMware NSX. We provide daily maintenance and support for this solution.

We are mostly using it for microsegmentation, which is very good. We now use it on a daily basis. Our clients are very satisfied that we can limit ourselves to NSX without the need to purchasing additional network systems and physical devices.

We can do a lot of things without waiting for the purchase of additional devices, such as setting up VRF on physical devices. We are able to implement a lot of things with the infrastructure code.

The firewall is its most valuable feature.

It is a mature solution that is available for enterprise companies.

We would like tenant segmentation available in future releases.

So far, so good.

We haven't face any problems yet with scalability. Hopefully, it will stay that way.

We were previously using the physical devices from Cisco.

The setup is not easy, but it is doable.

We did it ourselves.

We have been able to save CAPEX with this solution.

We chose NSX because we were looking for a product with network polarization, so VMware was the first choice for us.

PoC the platform before you test it. It is not so bad.

We are using the VVD implementation. It is implemented together with the vRA, vROps, and other solutions.

We use it for microsegmentation, and it has performed well.

We use this in combination with VMware Horizon View. With Horizon, we have an isolated environment.

The most valuable feature is to control application behavior.

It provides us with features that other products have not.

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.

The stability is very good.

Because it is in the VMkernel, it is robust.

I have no contact at the moment with VMware support about NSX.

It is easy to implement it.

I am the partner. I work with the customer to do the deployment.

I would recommend it to another person.

We do not integrate it with vCloud Director.

I don't use load balancer at the moment.

The primary use case is the microsegmentation of all our infrastructure, which is a huge bonus. It's performed well.

The microsegmentation allows me to sleep at night. My job is reducing risk, plugging security holes, and working with the automated layer security. Even if somebody spins up a new server, it has to have a tag in NSX. Therefore, all the security rules are already applied across the infrastructure or automatically applied to new machines. It doesn't generate any new security holes if people have new products. It gives peace of mind that project managers are not screwing up my entire security posture.

Automation, because we're constantly onboarding massive customers. We have our own management system, which integrates nicely with NSX. Therefore, we've built an automation layer so we can deploy and completely secure new customers in a hosted environment within a couple of minutes.

Microsegmentation is incredible. It's the only way to go for managing networks long-term.

The security benefit has been huge.

I would like to have automating reporting built into common service management platforms, such as JIRA, Serviceaide, and ServiceNow. 

The stability has been great. I have had no problems with it. It is a robust solution.

We manage a huge infrastructure, and it has not been a problem for us. It has caused no issues.

We generally load balance with separate hardware. With the normal traffic that we see between virtual machines, they never leave the host. So, there are no real issues there. We will use separate, dedicated hardware, because we are at such a scale that our customers prefer to have separate load balances in the hardware.

We jumped onboard with NSX right when it started. VMware worked with us when we had issues or made suggestions to the point that we were invited as a partner to 2016 VM World, because we contributed so heavily into NSX. It has been nice to see the things our potential pain points that we were having with NSX at the time be implemented into the product. Now, it's just seamless, which is great.

We just bought it off the shelf and implement it ourselves.

We have saved man-hours and decreased our security exposure.

We haven't had to hire a dedicated network engineer because NSX handles 90 percent of it. The reduced overhead in terms of managing networks has been the biggest plus. 

We haven't had to buy additional switching capacity.

Get it in your environment as soon as possible.

Network segmentation is hard. A lot of businesses still use the traditional three-tier system, because it has been proven, but it isn't particularly robust or secure. Realistically, it's a natural step in terms of network management to move to micro-segmentation. It just makes sense.

If someone is worried that the solution is too complex, they should hire people with experience.

Our primary use case is the integration with the platform, so we can use it to orchestrate everything from a single console. That's the magic of having everything in one single dashboard. 

Our customers can see how much easier having multiple integrations on a single dashboard can be for them. The speed and agility of the implementations is another way it has helped improve our clients' organizations. It's easy to monitor exactly what is missing and the speed of implementation. 

We can manage and interact with different network devices, not just the local environment but also in the remote environments. It's very effective in how easy it is to manage and orchestrate all the different devices with the different types of requirements we have. NSX is a great platform to have everything in one single pane of glass.

The easy integration and management are the two most valuable features.

In regards to Layer 4 and 7 load balancing with a solution, for us, it's about the continuity. We look for different ways to create something similar while making improvements. We like to include different services and make sure that we have high availability, not just in our closer environment but also around multiple environments.

Microsegmentation is important. We cap it depending on the compliance and regulations that are in the systems for every single company's requirements. It depends on the size of the customer, but I don't see a reason not to use it. We cap it based on industry, size of a company, and the compliance regulations that the company requires. Also, we consider the nature of the industry, although the reality is that security applies to everybody. Some industries take it more seriously than others because of their policies, rules, and regulations that they have to comply with. Ultimately, security is an issue that affects everybody and is important for all to have.

The engineering team has room for improvement. They should have more of a Knowledge Base about different case studies and should develop more advanced features. These kinds of improvements will change the way things get done.

The stability is great. That's one of the things that we can quantify and leverage through NSX, because it's less complex. We have the availability to manage multiple things at the same time. We can identify problems before they manifest. 

Their technical support is great but I believe that it also has to do with the relationship that we've built with the technical support staff. We're not afraid to have conversations. Most people try to figure things out by themselves but we don't hesitate to reach out to technical support. They have an intelligent team.

We based our decision to switch solutions on an analysis we did. We based this analysis on what we are missing and what the impact is of not having it.

In the beginning, implementation was quite challenging. Once you know your way around it, it becomes a lot easier to navigate. Every master was once a disaster. The beginning stages are the most challenging but as you pass through the initial starting point, you begin to realize how easily it can be integrated with multiple devices. 

I have been in technology for 23 years and I see the constant evolution of not just the portable technology but also the management. I believe that adapting to the multiple levels of security inside of the business management is a challenge for different vendors.

We look at different vendors for our customers. It depends on the compliance and regulations that are in the systems for every single company's requirements. Every company will have specific needs for certain features that other options do or don't have. 

This solution has helped our clients save CapEx. The agility and speed of the implementation offer CapEx savings. 

It does and doesn't prolong software refresh. It does because there is better integration with the product. It doesn't because there are new features developing and people like to replace their hardware. They will have better chances of getting more value out of their software solutions because now they can reach more control of multiple functionalities. I would approximate that it saves the hardware for around two to three years.

I have rated this product a seven because this product still needs to evolve. It's a good product but it's not great. 

If you are considering NSX or a similar solution I would advise that you have to adapt or die. Technology is emerging with different features. It is important to be in that conversation. You've got to move into the new trends. There are multiple solutions, and there will be different brands with different features but ultimately you have to find a solution that will meet your exact needs. 

To those who say NSX is complex, I would say that every master was once a disaster. In the beginning, it's going to be challenging. When you start something new, it very might well be a disaster and you will probably find it hard to navigate. Once you overcome the complexity issue, it's just a matter of perception. It's not really complex, despite what you may think. The solution is evolving, getting better. This is a smarter way to do things. This solution is at another level. 

My company's primary use case for this solution is the microsegmentation. It's futuristic.

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.

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. 

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.

We are happy with the scalability.

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. 

It was deployed by a VMware consultant. 

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. 

Our customers need load balance and firewalls with advanced NSX. They are really happy to use NSX.

It's free for our customers. It benefits them in that way and it benefits us because it makes our customers happy.

The most valuable features would be VPN and PCM. 

I use L7 balancing. I can use it for two tethers and I can see the source IP. I can split for monitoring for me and my analyst.

I would like to see extended performance charts in other versions of NSX. For example, CPU usage, memory usage, and bandwidth usage on NSX.

I would rate this product an eight because it's a good product but it needs more work. They should fix some of the bugs.

NSX is very stable. I don't remember when I have ever had any trouble with NSX. It's been a great process.

The scalability is not perfect. 

We use technical support but not for NSX. We don't have any trouble from NSX and we, therefore, don't need technical support.

I found the initial setup to be complex. 

NSX can reduce costs and has good service. It is easy for you and your users to use. 

We have integrated this solution with vCloud Director. Without NSX you can't deploy the cloud.

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.