NSX-T has allowed us to implement micro-segmentation in the customer's environment seamlessly (zero-trust). We have also looked at deploying Tufin or Gardicore, ReSTNSX as alternative tools. The Environment was an active-active Tier-0 multi-site deployment

The organization was able to begin scaling out its production workloads and clusters.

From a security standpoint, the customer was able to better secure critical workloads while routing L2/L3 worked normally, giving them more confidence that they would be ready for any potential security incident mitigation or outage (DR).

It has allowed our customers to scale/extend their existing IP subnets and spin up new subnets on-demand for new app/web/DB tiers. Increasing overall VM-to-VM security and policy deployments. It has helped increase operational efficiency from a network management perspective. Many firms have multiple racks of equipment at different data centers that leveraging NSX definitely helps (extending the 'same' IP subnets to different racks in the same data center). For customers who use SRM, there are also great benefits (i.e., not having to manually re-IP DR-side VMs during a failover test).

It's important to have whenever I need to segment or control the traffic from virtual machine to virtual machine. This was not the case without the NSX.

It makes our life easier as far as PCI and auditing are concerned. We have been audited over the last few years, which has brought up concerns and issues. The easiest resolution for this was to put NSX into place and use microsegmentation. So, that's what we did.

This solution comes with an API that can easily integrate with other solutions. 

Regarding network management, it enables the ease of creating a network configuration for any application.

VMware NSX improved my organization because it's more flexible than network hardware and provides many solutions, such as firewalls and load balancers.

Have worked on multiple organizations with VMware NSX. It heavily depends on the use case of the solution and how well you are able to use all the features of the product. When using for K8s container platforms or a networking backed for on premises cloud using a CMP(VRA, VIO) then VMware NSX is the best SDN solution but If an organization is not able to use NSX to its full potential (Switching, Routing, Load-balancing, Firewall, IDS, IPS etc.) then its not worth it.

The microsegmentation allows me to sleep at night. My job is reducing risk, plugging security holes, and working with the automated layer security. Even if somebody spins up a new server, it has to have a tag in NSX. Therefore, all the security rules are already applied across the infrastructure or automatically applied to new machines. It doesn't generate any new security holes if people have new products. It gives peace of mind that project managers are not screwing up my entire security posture.

It is used for Tanzu, it is successful for our Kubernetes environment.

Our customers can see how much easier having multiple integrations on a single dashboard can be for them. The speed and agility of the implementations is another way it has helped improve our clients' organizations. It's easy to monitor exactly what is missing and the speed of implementation. 

We can manage and interact with different network devices, not just the local environment but also in the remote environments. It's very effective in how easy it is to manage and orchestrate all the different devices with the different types of requirements we have. NSX is a great platform to have everything in one single pane of glass.

This solution has given us the ability to move from a physical to a virtual server estate with all of the expected VM benefits of decoupling servers from dedicated hardware.

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.

When we have problems in the Kubernetes cluster inside the XDN or problems in the Container Network Interface (a container integrated with the NSX), we can join the Kubernetes cluster data source. If there is a problem in CNI, we can see the connection with the NSX manager and create alerts.

We use the solution strictly for security.

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.

We aren't a service-based company, so in terms of improvement, VMware NSX hasn't improved our company, but we need it for business purposes because we do have clients who give us all these products, and they tell us to evaluate these products in our environment and then give them reports on those products. VMware NSX is a good product, but for us, the solution doesn't add that much value to our organization.

VMware NSX has improved our customers' organizations through its automation of security policies, delivery of policy by intent, rapid provisioning, and removing security as being a blocker.

The full integration has been great. Its infrastructure and its ability to be part of the whole application are very useful for organizations. 

We typically run a lot of vulnerability assessments — sometimes spam testing — and get a lot of bad results because some ports are open. I think NSX has significantly cut down on that. Right now, we have been able to fix almost all of our problems with unnecessary ports being opened and related issues. We are secure in this specific aspect, so we can log other options. 

We haven't installed this in our environment yet. We have a major lab to provide our Ci-Dev team a sandpit to test apps and its security when deploying a three-tier application on our customers and test every single connection and performance before handing over the application to the customer.

I use the cloud now but in the past, we were able to create very specific segments for each part of the company. 

After working for about 10 years as a consultant and always waiting for networking engineers to either attend meetings, then do the changes or be willing to do the changes that we need. NSX has improved the process. 

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.

NSX has improved our organisation in many ways, by securing it with micro-segmentation, and by allowing us to implement logical equipment in a matter of seconds instead of waiting for the physical material to implement and configure.

We use this in combination with VMware Horizon View. With Horizon, we have an isolated environment.

VMware NSX has improved our organization in the way that we can now deploy many VMs faster than before and so we are scaling up much faster.

It has the potential to improve the way we function by having our different clouds be able to easily communicate back and forth. Right now, it takes a lot of work to do collaboration from our test lab, to our production, and to do anything in-between. It has the potential of giving us streamline migrations from the test lab to production.  

We have deployed it in a virtual environment and it saved a lot of time and effort for us to configure.

It's free for our customers. It benefits them in that way and it benefits us because it makes our customers happy.

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

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