VMware NSX Reviews

We use this product for micro-segmentation and network function virtualization.

This is the most scalable product of its type.

It is very good for automation and software-defined networking.

I would like to see improvements made to the certification process. As it is now, you have to do the training with VMware itself, and you have to spend a lot of money doing it, which is very discouraging. 

If you compare other certifications especially from the cloud providers, you can get trained from your choice of training providers and not very expensive or learn on your own at your pace, prepare for exams and pass and your certificate will be issued. In contrast, you have to register under VMware to get training done at minimum of $3000 before your certificate is issued to you. The training costs a minimum of $3,000, which is expensive and should be reduced. 

I have been using this product for more than a year.

Outside of the cloud infrastructure, it is the most scalable network product that I have worked with. It is used in a server farm that contains about 2,000 servers.

We have not needed to contact technical support.

We did not use another network function virtualization product prior to this one.

The initial setup is very straightforward. Our deployment took three months, end to end.

We had a consultant to assist us with the deployment.

We have two or three in-house staff who manage and maintain the solution.

The licensing fees are expensive and we pay on a yearly basis. However, we were able to leverage some of the licenses that we had for an affiliated product, ESXi. There are no costs in addition to the standard licensing fees.

We chose VMware NSX-T because it was the most scalable.

This is a good product and one that I recommend for anybody who does not want to change their existing infrastructure. The problem is that they have to compete with the likes of AWS and cloud providers.

I would rate this solution an eight out of ten.

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. 

The primary use case is microsegmentation for other VMs, which should provide us great value. We are quite early in our use case of it. As for now, the performance is looking good.

The main reason for deploying the product was the possibility to isolate machines inside a VLAN from each other. It was also to have a local firewall with firewall profiles attached to the machines.

The organization of it is logical, useful, and intuitive.

The security part of micro-segmentation is getting more important.

We are early in our use of the product, but stability has been good so far.

It seems like it will scale.

We have not used technical support.

We had some complexities implementing into the other parts of a network. Otherwise, the NSX product was straightforward to setup.

We deployed it in-house

We were already using other VMware products, so this product seemed to be the best product for our purposes. The solution is less complex than other competitive products.

I would recommend this VMware product.

We are not using vCloud Director.

Usually customers, from the beginning, want state-of-the-art, latest technologies. They would like to rid themselves of their struggle with networking. This drives them to the next step, bringing in VMware services for implementing NSX.

After working for about 10 years as a consultant and always waiting for networking engineers to either attend meetings, then do the changes or be willing to do the changes that we need. NSX has improved the process. 

Any administrator with basic networking knowledge, in a couple of days, can be in full control of their networking without going through a networking engineer.

The microsegmentation feature is the reason why everybody wants to implement NSX. It's just awesome. I was impressed by it when I saw it for the first time. However, now that I see it everyday in production, it works perfectly.

We would like them to improve the deployment time.

The management console also needs a bit of improvement.

In the beginning, the stability needed real improvements. Nowadays, it works like a charm.

I have found the solution to be robust. I haven't had major issues except for a simple connectivity one, probably because it is not integrated with cloud.

The scalability comes along when you implement it. Within a couple of clicks, it makes the process so easy. This is why companies go for it.

The initial setup was a bit lengthy in the beginning. Now, it is a bit smoother. While I like it, it still takes time to setup. It is a bit slow, which is surprising.

The solution has helped to prolong hardware refresh.

The solution is not complex. Though, you need to have some experience in networking, but just the basics that come when you work in the industry. However, if you've never worked with networking, start at the beginning, then NSX will come along easily.

I recommend building your own lab and continue to keep breaking it. Break your own lab, because you'll find weird things.

We have not integrated with vCloud Director as our customers are not very eager to work with automation yet.

We aren't a service-based company, so in terms of improvement, VMware NSX hasn't improved our company, but we need it for business purposes because we do have clients who give us all these products, and they tell us to evaluate these products in our environment and then give them reports on those products. VMware NSX is a good product, but for us, the solution doesn't add that much value to our organization.

Though I haven't been working a lot on VMware NSX, it's good to have. What I like the most about it is that its console is good, and it doesn't take a lot of effort in terms of doing my daily tasks on it or what it's meant for. VMware NSX is still a preferred product in the market.

An area for improvement in VMware NSX is that it uses up more resources and is heavy on the network.

What I'd like to see in the next release of the solution is more automation.

I've been using VMware NSX for more than two years now.

VMware NSX is a stable solution. It's very reliable.

VMware NSX, In terms of scalability, particularly at the enterprise level, is hectic. It's a complex process if you want to scale it compared to its competitors. It still depends, for example, if you've been in VM all your life or if you have been a VM administrator for a long time, you'll take comfort in something new, so people tend to go for it. If it's a new customer, an upgrade, or if the entire organization is going through a revamp, the process is quite complex. On a scale of one to five, I'll rate the scalability of VMware NSX a four.

VMware NSX has great support, and I have no complaints about it. The support for this solution is reasonable.

The initial setup for VMware NSX was pretty straightforward. In terms of our implementation plan, mostly we have standard SOPs that we have laid down for our implementation teams and we stick to those. It would still depend on the environment where we're going to execute it, for example, it could be on-premises or on the cloud, and we'd also take into consideration which type of cloud they have and what other technologies they have in their environment, so based on all of those, the implementation plan and how we're going to approach the implementation changes.

How long the deployment of VMware NSX takes would depend on the client, the environment, and the requirements, but for the basic setup or initial setup where we would just get the box and the do configuration, the IP, etc., that doesn't take more than four to five days.

Our deployment model for VMware NSX used to be on-premises, but now the deployment is mostly on the public cloud.

We used consultants for the implementation of VMware NSX.

I'm unable to give information on the pricing or licensing cost of VMware NSX because I've never been someone who looks into the economic part of any security or virtualization solutions. That's handled by an entirely different team, and I don't even have the slightest idea about the costs associated with the solution, though I've heard pricing for VMware NSX is on the higher side.

We haven't evaluated other virtualization solutions apart from VMware NSX.

VMware NSX is a solution I use at the company very often. My company is a partner of VMware and I analyze products such as the VMware NSX, and I give a detailed report on how the features are, what are the differences between the solution and its competitors, etc.

Deploying VMware NSX requires a team of four, but it would still depend on the skillset. For example, two people can do the work where one is in charge of the networking and one would act as a backup. Currently, my team of five users works on VMware NSX.

My advice to others looking into implementing the solution is to first go through the POC and the documentation before purchasing VMware NSX. Get to know the features best and find out what works for your organization and what doesn't, then take a calculated decision on whether you need the solution because some VMware solutions would be quite heavy on your environment if you are a mid-level enterprise. Other than that, VMware is a trusted name, and it has been in the market for quite some time now, and it's reliable. Though you should also evaluate other solutions, especially in terms of pricing because what I've heard is that VMware NSX is on the higher end, so it depends on what type of fees you want to check off your list. After evaluating all these factors, only then should you make that decision whether you want to go for VMware NSX or not.

My rating for VMware NSX on a scale of one to ten is seven, particularly for virtualization. Technology-wise and implementation-wise, I'm giving the solution a seven.

I would rate the solution a ten out of ten if it was less complex and had more automation. Currently, it's on the heavier side, for example, even the basic agent or basic software takes up a lot of space at the end-user level. VMware NSX should utilize fewer resources when it sits in your environment, so all the other users or other solutions in the environment would have ample resources to use. The solution shouldn't be heavy on the network.

My company is a partner but not a reseller of VMware NSX.

We use the solution mainly for micro-segmentation and to permit security on flat networks without a V-LAN.

I have found the system to be very intuitive, functional, and they have great technology.

One of the areas that we are struggling with is how do we perform the same security level as we had for an NSX solution for the legacy system. For example, if I have a switch, and I am connecting a legacy application on the legacy system that does not support the hyper vision or another feature, is possible to push the security topic to the switches to be compliant, or compliant with an NSX component, and to perform the same security level as we perform for hyper vision side. It would be beneficial for us if there was better integration with legacy systems.

In the future, the solution should be compliant with internet NIC. They could deploy this NIC into some switches, servers, or other product. It would be interesting to have this sort of NIC stamped by VMware, and we could push some security feature into it. It would be a very useful feature. I do understand VMware is virtual and not on a physical device path but this would be a good endeavour.

I have been using the solution for approximately five years.

The solution is completely stable.

The solution is highly scalable. One of the biggest infrastructures we have deployed the solution in has approximately 70,000 people using the solution.

The installation has been complex.

This solution can be very complex to deploy. We have assembled complex deployments at a few huge network site. We work for several customers in the communication and industrial sectors that have complex environments.

The price is based on the virtual desktop infrastructure(VDI) side and also is dependant on the size of the environment. The price is expensive and it could attract more purchasers in smaller organisations if it was reduced.

I would definitely recommend this solution to others. I have deployed it in many different types of environments and it operates well.

I rate VMware NSX an eight out of ten.

We use this product for software-defined networking. We are a solution provider and we build a platform for our clients that includes it.

The most valuable features are the micro-segmentation and integrated security options.

The technical support could use some improvement.

I have been using VMware NSX for a year and a half.

This is a stable product.

NSX-T is scalable, and we have approximately ten people who use it.

The VMware technical support could be better. They're not always reachable and expertise is not widespread. Especially in Austria, there are not a lot of people who are skilled.

I have not worked with another software-defined networking product.

We had some challenges during the installation and setup.

We implemented this product in-house.

The price of this product is too high.

This is a good solution, but there is always room for improvement.

I would rate this solution a seven out of ten.

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.