What is your primary use case for VMware NSX?

VMware NSX helps create and operate on-demand networks. The solution is dynamic and flexible. Our company's principal use case for the product is to provide a network for private projects. VMware NSX is also used to link virtual networks with legal networks and develop a single environment that permits comprehending virtual and physical tasks.

We use the product for disaster recovery purposes. It helps us expand the network and security for workloads running inside the environment. In the cloud, specifically with Azure VMware Solution or AWS, VMware NSX provides protection-related capabilities.

I was part of the NSX troubleshooting team from VMware, where we worked with different customers to troubleshoot their NSX operational issues. Also, I was part of the design and deployment team. We do PSO projects and migration for customers.

Our primary focus is to create a layer that effectively connects to the remote site. This involves optimizing and accelerating the VXLend component, which is highly popular in our setup. We usually configure VXLend to enhance disaster recovery capabilities, specifically for applications that operate within the same subnet. This approach ensures that in the event of a disaster, such as a WAN failure or when external layers are inaccessible, there's no need to change IP addresses. It allows users to connect seamlessly from any location since the servers maintain the same subnet, and data replication occurs between the data centers. The result is minimal disruption and no requirement to modify configurations during these critical scenarios.

We're moving towards hyper-converged solutions with VMware, including NSX and vSAN. This direction has promising prospects in the market.

We use the solution for the software-defined network.

We use the solution to establish a connection between our two sites using the same IPs. This is our primary use case.

We are using VMware NSX primarily to enable address mechanisms in terms of having to provide the workloads publicly. In India and similar regions, the CSP faces a significant challenge. The primary issue is related to network address cancellation, which requires private to public IT mapping and the use of the CSP's own IP address space. VMware NSX has been effective in addressing this problem, along with the virtual firewall's ability to function as a network firewall. This has helped to minimize the need for customers to take responsibility for their network security. In these regions, customers expect full-service solutions and do not typically embrace DIY approaches. An analogy for this situation is that if a customer buys a toothbrush from you, they might expect you to brush their teeth for them.

VMware NSX is used for server virtual machines.

I primarily use NSX for micro-segmentation, security, and load-balancing.

The solution is primarily used for micro-segmentation for the security of virtual machines.

Our clients are moving from traditional to virtual infrastructure, so we sold them vSphere, vSAM, and NSX to manage all the workloads inside VMware. All the VMs work just like traditional infrastructure inside an appliance.

I use VMware NSX for virtualizing networks for VMware virtual machines.

I used to sell the solution as a bundled package. My role was to find the best solutions for customers from various vendors and work with our pre-sales and solution architecture departments to present these options. I provided high-level advice and my colleagues provided technical details. Our customers used the solution for segmentation and automation to secure workloads in their lower computing layer. One customer was CaixaBank, an important financial institution in Spain.

NSX is used with vCloud Director to provide networking as a service or extend the capabilities of the load balancer, VPN, firewall, etc. There are two types of NSX. VMware's latest version is a product called NSX-T. It's a universal solution used across the VMware lineup and products like Hyper-V or the public cloud. You can use it on-prem or public cloud as well. NSX is used by the operations team, architects, and engineers. There are maybe 20 to 30 people using it.

The solution is used for network virtualization. Normally, in my cases, I was billing it for the government clouds, for NIC, the National Informatics Computer of India. For them, I was making a cloud where a different government, a smaller government entity, wanted to buy a cloud from the government clouds.

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

It is for internal networking. Basically, we will be migrating the workloads to the cloud vCenter, and to manage those workloads, networking is required, which is called NSX in the VMware environment.

The solution is mainly used for rolling virtual environments and private clouds. I use the product for my company and for other customers.

It is helping me get an entire blueprint done of the source and the target. I was able to make it into a catalog and can set up anything on the cloud quickly.

We use VMware NSX for micro-segmentation.

VMware NSX can be used for micro-segmentation in the network space.

VMware NSX is used as a software-defined network. We used the solution in a data center.

We use NSX as a security solution. The solution is deployed on-premise. We are using version 6.4 of NSX.

This product is a software-defined data center with a cloud-native approach. We mainly use it for application migration of some of the architecture to containerized solutions.

We are using VMware NSX for all our network needs.

Load balancing is achieved using VMware NSX. The load balancing feature provided with VMware vSphere is called NSX. While using the virtual server with your on-premises trusted internal network, you can set up rules to prevent them from doing specific activities.

Our main use case is the distributed firewall. NSX can segment every application and server based on the ports they need to communicate externally. Ports that aren't required are inactive, so we activate them for some specific applications. We can get the ports from the application guys, activate the ones we need, and then disable the rest of the ports. We've done other things with NSX, but it's just mostly about the distributed firewall.

We are using VMware NSX for network security.

It's very useful for making network configurations and setting the network configurations in an easy way. The infrastructure team has all of the components under these controls, that is, the infrastructure and the network itself.

We primarily use the solution in order to build a private cloud.

I work with two different companies with different large cloud environments. This product is a software-defined network, and that allows you to create virtual access networks and managing security to allow for different workloads.

We use this product for software-defined networking. We are a solution provider and we build a platform for our clients that includes it.

Many of our customers are moving to these kinds of options in order to reduce the number of physical devices and to increase security. I'm an architect of enterprise business and we are an enterprise partner with VMware.

This is a product for network security, and network management. We don't use it at the production level. I am conducting a PoC. We are using this in our testing data center and not in our live data center. This infrastructure contains many security devices from other vendors such as Palo Alto. We are also using vSAN and vCenter.

The Environment was an active-active Tier-0 multi-site deployment (primary/secondary). It contained compute and management clusters, and a small number of transport ESXi nodes (between five and six) v6.7u2, vCenter 6.7u2, AD. The primary use case was to implement micro-segmentation and route production workloads through NSX-T via BGP. Our customer needed assurances that BGP routing within NSX-T would be efficient. We implemented a very simple architecture and setup site with one NSX Manager as the primary source. This was a financial customer, thus security was the main item. We had to explain to the customer that NSX-T deployment and micro-segmentation were two different projects explicitly.

We use this product for micro-segmentation and network function virtualization.

We use this solution to build our VMware platform.

We are a professional services company and we have been evaluating VMware NSX for our clients.

Our primary use case is moving from physical to VM infrastructure.

* Deployment * Planning and designing * Troubleshooting sustain.

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.

We support clients who use on-premise VMware NSX. We provide daily maintenance and support for this solution.

Our primary use case is the integration with the platform, so we can use it to orchestrate everything from a single console. That's the magic of having everything in one single dashboard.

We use this solution for extended on-premise capabilities. We've been using it for five years.

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.

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.

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 primary use case is the microsegmentation of all our infrastructure, which is a huge bonus. It's performed well.

We use it for microsegmentation, and it has performed well.

Our primary use case is to change from Cisco.

Our primary use cases of this solution are hybrid, cloud, private cloud, and automation.

Our customers need load balance and firewalls with advanced NSX. They are really happy to use NSX.

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

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 use it for microsegmentation. We're still in the middle of the project. We have 70 or 80 apps to microsegment and have only done about ten so far. We have a long way to go.

My company's primary use case for this solution is the microsegmentation. It's futuristic.

I was an intern at a relatively large company here in Morocco, and NSX is a great solution.