VMware NSX Reviews

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.

NSX is extremely invaluable from the standpoint of security.

It does have capabilities of micro-segmenting a network, being able to create smaller segments of various types of applications separated by various tiers.

However, what it's mostly important for is being able to actually set security policies right at the interfacing virtual machine, which we haven't had the ability to do in the past.

So the third-party marketplace is growing and growing for this product and being able to redirect traffic to them, to the third-party products in order to take advantage of those additional features, is wonderful.

I think that one of the more important things to see better integrated into the NSX product would be an IDS/IPS type solution, which right now we're handing off to a third-party, which sometimes doubles the cost of the product. However, there are new products that we're learning about over the course of this week like AppDefense, that may actually help provide some additional capabilities in terms of that IDS/IPS type structure.

There are elements that have been added to it over the years, but its history goes way back with vShield, and has been included in products like vCloud Director, etc. To be honest with you, I've deployed it over the past five to six years and I've had nothing but great success with it.

From a tech support standpoint, as with most VMware text support, the people that we get a hold of on the phone are generally very knowledgeable of the product and have the ability to actually help us through whatever issue we have. We try not to spin our wheels too much. We do try to dig in as much as we can, but as soon as we understand we've gone beyond our limitations we get them on the phone and we've never had an issue trying to get the support we need.

It's a complex product so setup is essentially as easy as the person whose knowledge is being used to install it. There are various elements to it. It can be installed in modules - in a modular fashion. You don't have to install everything right away. And, unfortunately, with this particular product, when you read through all the marketing materials it sounds like it has to be installed completely when, in fact, you can start out with only the pieces you need and add what you need - the other pieces - later as needed.

I always have a hard time giving a ten to anything. I think everything needs improvement. So that's why I would give it a solid eight out of 10.

Security. Our Trend platform runs off NSX.

We use the solution strictly for security.

Roughly six months.

We didn't have this issue, but I would recommend to others looking at this solution to make sure that their hardware is compatible.

It seems to be taking care of our whole environment. It seems to be pretty scalable.

I have not used it, but my coworker has. Every time he talks to them, they're easy to get a hold of; very knowledgeable and they solve his issues right away.

If you put in a trouble ticket, they contact you very quickly (in response). If there is a problem, it usually isn't around very long. They jump on it, fix it, and it's done.

We were on McAfee, and we switched to Trend. We switched to Trend because Trend supports virtual environment a lot better than McAfee does.

Trend migrated in a way that it will only work with NSX. The older version of Trend that we were on worked without NSX. The newer version does not. Now, we use NSX in conjunction with Trend.

We upgraded Trend to keep up-to-date and all the security loopholes closed.

Most important criteria when selecting a vendor:

• They have to be able to support the environment you're running.
• The service and support is a big must. We work at an Enterprise level, so sometimes you can't go with the little new guy. You need that 24 hour service and support, seven days a week. It is very important for us.

We use VMware NSX for box integration. If box integration is still a code, we use this technology to understand it.

When we have problems in the Kubernetes cluster inside the XDN or problems in the Container Network Interface (a container integrated with the NSX), we can join the Kubernetes cluster data source. If there is a problem in CNI, we can see the connection with the NSX manager and create alerts.

The alert features are the most valuable.

The integration with other brands is not the best and could be better.

We have been using this solution for almost two years. We are using version 3.1.

It is a stable solution.

It is scalable, and we have 20 users using this solution.

I rate the technical support a ten out of ten. Their support is excellent.

The initial setup was straightforward.

We have had a very good return on investment.

I rate this solution a ten out of ten. I recommend VMware NSX because it's a powerful tool. We can see the flows inside the SDN, which has a lot of power.

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.

Our clients consist of enterprise companies. 

From my experience, VMware on a private cloud is a good choice. They offer some great webinars and workshops to learn how to use the product better.

Over the last two years, they've enhanced a lot, especially in regard to integration with OpenStack.

It's great for building a virtualized environment. It features great motion mobility, its own logical distributor, router switches, load balance, firewall, etc. 

I have been using VMware NSX for four to five years. 

Personally, I find VMware NSX to be very stable. 

They need to enhance their technical support. There is no comparison between VMware technical support and Cisco's technical support. It's one of the main criteria that everyone is looking for.

The initial setup was straightforward. Deployment was very easy.

VMware NSX is expensive and everything is licensed. We have to pay for each individual feature. 

Be sure to read over the documentation on their website. They announce a lot of webinars and workshops for the product. It's good marketing and you should attend them. 

Overall, on a scale from one to ten, I would give this solution a rating of six. 

We use this solution to build our VMware platform.

The most valuable features are security and dynamic routing.

The routing functionality needs to be improved, as there are lots of bugs in the system.

I would like to see automation capabilities in the deployment process.

I have been using VMware NSX since 2016.

I think that there is room to improve from a stability standpoint. There are lots of bugs in this product.

VMware NSX is highly scalable.

The technical support team is good.

I would not say that the initial setup was straightforward. In terms of how easy it was to complete the deployment, I would rate the process a seven out of ten. 

My advice for anybody who is researching VMware NSX is to first have an understanding of network engineering.

I would rate this solution an eight out of ten.