We just raised a $30M Series A: Read our story
2018-06-29T06:40:00Z

What needs improvement with VMware NSX?

16

Please share with the community what you think needs improvement with VMware NSX.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
Guest
2727 Answers

author avatar
MSP

I cannot recall coming across any missing features. At this time, there is nothing I would need in a future release. Occasionally the licensing is not very clear. They should make it easier to understand.

2021-09-29T19:02:11Z
author avatar
Top 5LeaderboardReal User

NSX-T supports more platforms, and VMware NSX only supports some platforms like KVM. I want to see support for Hyper-V and other hypervisors. Their technical support could be faster as well.

2021-05-21T17:51:38Z
author avatar
Top 20Real User

Any technical product has its own limitations in one place or another. Our technical team is always looking for the solutions that they work with to offer more convenient integrations.

2021-03-29T09:21:19Z
author avatar
Top 5LeaderboardReal User

One drawback is this solution requires a lot of other products in the VMware ecosystem to have a full end-to-end operation orchestration monitoring. You have to buy a lot of add-ons to fully utilize the functionality. Some additional features in the next release could be for the solution to be more directed toward the end-to-end functions, from physical to virtual monitoring. It should also include streamlined troubleshooting of our operation.

2021-03-09T13:16:59Z
author avatar
Top 20Reseller

There is always room for improvement, in any solution. In some cases, this product is very technical. Some configuration maximums are limiting to the user, especially when it comes to the deployment of very, very large environments. There are limits to the number of firewall rules, security groups, et cetera. With the number of security groups, you can nest all these limits, however, somehow limiting the use cases may be restrictive for the free design of different use cases.

2021-02-08T10:06:39Z
author avatar
Top 10MSP

The technical support could use some improvement.

2021-01-27T12:05:45Z
author avatar
Top 10MSP

The product is quite complex and that could be an area where improvements could be made.

2021-01-22T18:58:23Z
author avatar
Top 5LeaderboardReal User

There are always issues integrating with Cisco. Switching is always a big problem for us because our switch is not supported. If the integration was more open, then it would be good.

2021-01-14T17:10:41Z
author avatar
Top 5LeaderboardReal User

Traffic flow introspection topology visibility is definitely needed because at the moment, NSX-T lacks in this area. A hardware scan of the ESXi host for possible incompatibilities should be added to NSX-T/vSphere, as it would allow us to know in advance, for example, if a pNIC is not compatible with a version of vSphere before moving forward with an NSX-T deployment. It needs a better, integrated migration tool. Something like RestNSX with more elaborate capabilities from a troubleshooting perspective and pre-migration perspective would be an improvement.

2020-11-14T15:17:00Z
author avatar
Top 5LeaderboardReal User

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.

2020-08-19T07:57:00Z
author avatar
Top 5LeaderboardReal User

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.

2020-07-02T10:05:57Z
author avatar
Top 10Real User

Everybody needs a network to connect to, and VMware doesn't readily provide one. It is reliant on an existing network to connect to, which means that for me, it requires two different teams to manage the SDN.

2020-06-28T08:51:00Z
author avatar
Top 10Real User

It could be cheaper!

2020-01-02T15:21:00Z
author avatar
Real User

* vRNI * Improve integration with many third-party solutions, because only Palo Alto and Check Point, and VMware would be like improve this integration with other vendors.

2019-02-14T21:52:00Z
author avatar
Real User

We would like tenant segmentation available in future releases.

2018-11-21T08:01:00Z
author avatar
Real User

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.

2018-11-21T08:01:00Z
author avatar
Real User

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

2018-11-21T08:01:00Z
author avatar
Real User

The solution is quite complex. You need to keep your thinking cap on and know what you are doing: Go to the training and listen to the solution architects when they come in because they have a lot of knowledge. There is a concern and some confusion around who owns NSX in the end, whether it's the network team or the VMware team. There is not much confusion about this anymore, but there was at the start. Would it be owned by the network team, who might never even have seen VMware before, but would understand firewall rules? Or would it be owned by your average VMware person? As far as someone else putting it in, make sure you know who is going to own it, and they have the staff and the capabilities to cover it.

2018-11-18T09:40:00Z
author avatar
Top 20Real User

We would to have a reverse proxy. This would add great value to the solution. We would also like better integration with the standards on the market. For example, with OSPF, their integration in NSX is very low. It's not a full OSPF integration. It is too thin from a protocol perspective. The product need to be improved. It is too complex.

2018-11-18T09:40:00Z
author avatar
Real User

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.

2018-11-18T09:40:00Z
author avatar
Real User

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.

2018-11-18T09:40:00Z
author avatar
Real User

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.

2018-11-18T09:40:00Z
author avatar
Real User

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

2018-11-18T09:40:00Z
author avatar
Real User

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

2018-11-18T09:40:00Z
author avatar
Real User

I would like to see some more add-ons on the security features.

2018-11-18T09:40:00Z
author avatar
Consultant

We would like them to improve the deployment time. The management console also needs a bit of improvement.

2018-11-18T09:40:00Z
author avatar
Real User

It should be more adapted to the physical side of network topology in order to prevent unavailability.

2018-06-29T06:40:00Z
Learn what your peers think about VMware NSX. Get advice and tips from experienced pros sharing their opinions. Updated: September 2021.
542,029 professionals have used our research since 2012.