We have never used any other solution. NSX is the premier product in this space.

No previous solution in place.

I have experience with Cisco, but I find VMware to be a superior solution. The primary reason is the seamless integration that VMware offers, especially within a data center environment. When working within a data center, VMware's virtualization capabilities are all that we need. We no longer require separate hardware, edge products, load-balancing solutions, or firewall products. Everything can be fully integrated into a unified system and it allows us to accomplish everything from one console and one central point of control, making it a highly efficient and streamlined solution.

We didn't use any solution for the virtualized environment.

That said, for other solutions in the market that have the same feature, we have experience. This includes Juniper, Cisco, and Palo Alto. These all have next-generation firewall features, which have been standard for 20 years now.

We are still in the process of completing the migration from the physical servers to NSX.

We sell Nutanix, Dell EMC, HPE, and IBM. Right now, I'm working with IBM Storage and Power Servers. We have Pure Systems, too, but I'm still new. It's my first week at the company, so I'm still studying other vendors that I'm unfamiliar with.

I cannot say if there was a different solution used in our organization. It had been implemented before I arrived.

This product is better for network security than Cisco ASA and Firepower.

We didn't have anything before. The solution was highlighted by audits, which is why we decided to put it in.

We did not previously use a different solution before this product.

I have used previously Cisco 1000V. It was much more expensive than VMware NSX. We cannot compare them because the Cisco 1000V is obsolete and I don't know if they have a newer version or something similar. They are not the same technology, Cisco 1000V is from 2015, and NSX-T is from 2021. There is a big difference between time and technology.

I have not used a similar solution to VMware NSX.

One of our prominent clients is a major university in Pakistan, and they expressed dissatisfaction with their current solution, Sentra for SCI. They expressed a desire to transition to VMware, specifically NSX, as they are seeking hyper-converged integrations with both cloud and on-premises solutions.

I didn't use a previous solution before I used VMware NSX.

My company went with VMware NSX because the infrastructure within the company is VMware.

We have using Cisco ACI  and it is a strong competitor. When you are not using NSX NCP then everything that you need from SDN prospective can be done in Cisco ACI except for the distributed firewall at the vnic level.

We also use NSX-T alongside this solution. NSX started with micro-segmentation and the other option is based on a different architecture with some differences.

I have used Qumulo but we needed to buy a switch for it which was not favorable.

I have used other network virtualization tools and the main difference is VMware NSX is tightly integrated with the Hypervisor layer. We've been able to have end-to-end visibility of the virtual machine traffic, and we have been able to see the flow. The other solution will be agent-based.

We jumped onboard with NSX right when it started. VMware worked with us when we had issues or made suggestions to the point that we were invited as a partner to 2016 VM World, because we contributed so heavily into NSX. It has been nice to see the things our potential pain points that we were having with NSX at the time be implemented into the product. Now, it's just seamless, which is great.

We previously used a different solution for server virtualization, but we switched to NSX.

We based our decision to switch solutions on an analysis we did. We based this analysis on what we are missing and what the impact is of not having it.

We previously used OpenShift together with OpenStack. It's a different platform. One is open-source and the other is a commercial platform with vendor support and established customers.

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

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.

I didn't work with another solution per se, however, the previous triggered cloud tool that we had was by VMware. It was not really, at least at the very beginning, a tool for a software-defined network, however, there were some elements that allowed you to create customer networks practically on the fly. There were also some other network visualization techniques, which allowed you actually to encapsulate the traffic and to create networks on the fly. You had some security constructs, including tenents constructs, that you can find somehow in the VRA today. The tenant concept is also present in NSX.

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.

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. 

Business is demanding more agility and capability than ever before. NSX offers solutions to those business-level problems.

I also have experience using Red Hat. However, sometimes I have had some problems with it. It can be a bit more difficult in terms of integration with other vendors. 

Nope, never used a network virtualisation product before.

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 have not worked with another software-defined networking product.

We were previously using the physical devices from Cisco.

We had multiple solutions.

We were making do with what we had, but again, going to different conferences and seeing what other people were using. We got curious and our vendor said, let's demo it. So, we made time for it, and after we made time for the demo, we realized we should have been doing this two years ago.

We are mainly a Cisco house, but we are trying to use VMware NSX as the next stage of our software-defined networking (SDN) expansion.

No.