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?
It could be cheaper!
* 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.
At the moment it hasn't helped us prolong our hardware refresh.
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.
We would like tenant segmentation available in future releases.
We would like them to improve the deployment time. The management console also needs a bit of improvement.
I would like to see some more add-ons on the security features.
I would like them to make integration with other vendors easier.
I would like to have automating reporting built into common service management platforms, such as JIRA, Serviceaide, and ServiceNow.
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 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.
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.
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.
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.
It should be more adapted to the physical side of network topology in order to prevent unavailability.