VMware NSX Reviews

We use it as a distributed firewall and for security purposes.

It has reduced the number of people on the network team along with the system engineer involved in the security process. So, it is valuable.

We can't go without NSX, so it's invaluable from this perspective.

Its flexibility and integration with other VMware solutions are NSX's most valuable features.

The microsegmentation feature is very useful.

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 stability used to be perfect. Now, it is okay.

From a distributed firewall perspective, it's a solid solution.

It is scalable by design, so it's perfect.

The technical support is good. We have encountered several problems with NSX, and every time, support has found the solution to resolve the issue. 

In our company, we were starting a hosting solution, so it was by design. We have worked with VMware products for a long time, so it was natural to buy NSX.

It was a complex setup.

We implemented it ourselves.

The solution is expensive.

We did not consider anyone else.

If someone is looking for security in a vSphere environment, I don't know of another solution in the market besides NSX.

We had to buy new hardware in order to introduce NSX into our data center.

We don't use load balancing with this solution.

We don't use vCloud Director.

• Deployment
• Planning and designing
• Troubleshooting sustain.

• Faster delivery of VMs
• Providing NAT
• Firewall rules
• Balance
• Connectivity between physical and virtual environments.

Visibility, because on our environment, it's impossible mapping end to end, and we don't have any tools that provide this integration.

• 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.

We use this solution in our private clouds networking environment. We have some subsidiaries that we service and are trying to isolate each of them in this network.

It has helped us prolong our hardware research. We haven't had to change hardware in five years.

Security and cloud readiness are the most valuable features for us. We're interested in looking into microsegmentation. 

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

It's very stable and robust. We haven't had any issues with it. 

Scalability is a great feature. 

Their technical support is very good. They help us figure out solutions when we have problems. 

The initial setup was straightforward. 

We integrated in-house. 

I would rate this solution a nine because we maximize most of its features. We have many advantages with the cloud infrastructure. I would tell someone looking into this solution to go for it. At first, it may seem to be complex but using it will make it easier to manage jobs. Yes, its initial establishment can be complex but you will see its advantages later on. 

Our customers had multiple data centers in different locations. Now, with NSX we built one fabric over an IP transport, like WAN internet. When we created the switches, it spread out over the data centers which are the configuration and the management of the underlying network for the VM workloads.

The reusability of the objects for the switches has improved our client's organization. For example, if I do some sort of vMotion, there is no need to recreate the portal groups on the other sides. We have one centralized NSX Manager which is managing those controllers on those sites.

The most valuable features would be the easy management and the possibility of using our existing vSphere environment so that we don't need to purchase a new hardware.

Layers 4 and 7 load balancing are good. We like that it's integrated with the vSphere. This means that we can see its full capabilities because of the full visibility of the kernel on the NSX management.

Microsementation is really powerful. With the existing networks of the legacy networks, we need to build a firewall between the segments in order to do microsegmentation but now having, for example, one VLAN connected to multiple VLANs, I can do micro-segmentation between the workloads even with the ushering the same segments.

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

It's pretty stable. Just deploy it and just forget about it. It's also robust, flexible, and scalable. 

Scalability is really easy. We can scale within an hour. We can scale either new controllers or add new hosts to the fabric.

We haven't had to use their technical support yet, which is a good thing.

I'm involved in the decision making. My boss would say that it's time to advance the customer so we'll look into a solution.

We were already a VMware-based customer so our first option for an SDN solution was to go with NSX. 

The initial setup was straightforward. It follows a certain structure and you won't miss a step. It's all on the same level, step by step.

It has saved us CapEx. They should adjust the license for NSX so that we can invest in the infrastructure or purchasing of new hardware. This solution is reasonably priced compared to other vendors.

Our customers usually compare NSX to Cisco ACI. The main issue is the underlying network that VMware does not provide visibility to. They chose NSX because they were already VMware customers and they already had vSphere. The second reason they chose NSX is because of the powerful features like microsegmentation, as opposed to relying on other vendors to manage the microsegmentation feature.

I would rate this solution an eight because of its ease of deployment. I'm a partner so this is what I mostly care about. Also because of the ease of scalability.

If you're looking into NSX or similar solutions I would recommend you to first learn about vSphere and other VMware products because it's essential in order to implement NSX. Without that knowledge, it would be hard for you to understand.

And to those who think NSX is complex I would say it's not. You need to try it and see.

We just introduced NSX in our headquarters. We have it running in some labs, but no real experiences. We've been using it for six months.

Our objective is to know each features component and how it works. Depending on the business requirements, we would adapt the solution as needed. This is the reason why we work a lot from the maps and then anticipate when we need a new feature for our company.

We like that NSX is integrated with everything. 

The load balancing is a real major opportunity for us. As a CIO, we have 99.9% network security. We would like to optimize this product.

The feedback we're getting from the labs is that the stability is rich and that we haven't had any trouble with it. The stability is really, really good.

We didn't use a service for implementation but we have a consultant to help us get a better understanding of NSX and to teach us the best practices. 

To those who say this solution is complex, I would say it is but not for the key user. You just need to learn the standards and mechanics for your specific product. That means that it's simple even if it's really complex beyond that.

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.