VMware NSX Reviews

We host citizen-centric portals. They are web portals where citizens can enter and fetch data. For example, we have tax-related portals, health-related portals, and education-related portals. These are social welfare portals, and for that, we use AWS services.

NSX helps us by making IT management and operations more efficient. When VMs spin off from the DC to the DR site, all required settings on the network level are handled automatically.

The most valuable feature of NSX is the ease of configuration. It handles automatic configuration of IP addresses and network settings during VM migrations between data centers.

The ticket support response time from VMware could be improved. Often, callbacks are delayed, which can be problematic if the servers are in production.

We have been using NSX for almost one year.

NSX is stable and reliable. I would rate its stability between eight or nine out of ten.

NSX is quite scalable. I would rate its scalability as eight out of ten.

The customer support from VMware could be more responsive, as sometimes callbacks are delayed, causing delays in addressing critical issues.

We did not switch from another solution to NSX. We have been using VMware products, including vSphere, for many years.

The initial setup of NSX was complex, but with the help of an experienced vendor and support from VMware, we managed to configure it successfully in a short time.

We had an experienced vendor help with the implementation and received good support from VMware during the setup.

VMware has moved to a bundled pricing model, which means we are sometimes forced to pay for features we don’t use. This has increased our overall costs.

We evaluated Azure and other solutions, but we preferred AWS.

I recommend NSX because it simplifies IT operations and management, especially for data center network configurations.

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. 

Firewall security is one of VMware NSX's vital features. Using the tags and the solution's security policy is incredibly simple. For instance, I can create a sketch on paper and redesign it with the tags present on the network segment using VMware NSX. 

A basic load balancer feature was present in a previous version, but the latest version only has an advanced load balancer. The vendor should integrate a basic load balancer in future versions. The advanced load balancer is mostly suitable for system integrators, but it is not usable for our company dimensions. 

I have been using VMware NSX for three years. 

I would rate the stability a ten out of ten. 

I would rate the scalability a nine out of ten. There are about a few hundred end-users of the solution in our organization. 

Our organization's virtual environments consist of virtual machines and systems within the network segments of VMware NSX, and every lab has professors, researchers, and students. 

Before Broadcom acquired VMware NSX, I would rate the tech support a nine out of ten. But presently, I wouldn't rate it so high because our company has difficulty reaching customer support. Whenever I write an email to the technical manager of the solution, I often don't receive a response. 

Overall, the setup process of VMware NSX was easy, but due to the unfamiliarity, the beginning of the process was a steep climb for our organization's team. In our company, we majorly utilize the on-prem deployment model but temporarily we also used the solution in the cloud because we needed the virtual labs and sometimes we needed to use VMware NSX on Azure. 

As a public administrator in Italy, our company signs a contract with an organization connected to numerous universities. This aforementioned organization creates the tender with VMware. I would rate the pricing of VMware NSX as seven out of ten. 

The micro-segmentation function of VMware NSX is wonderful because this feature allows for the best control of every single entrance point of data packets. I would overall rate VMware NSX a nine out of ten. I would recommend others to use the solution. 

It's what we use the CIS Benchmarks for. It's for employing hardening rules and keeping them up to date when things happen on our systems. So it's really configurations and stuff that harden and report back. 

Now, some of the hardening we have in our configuration, so there's some overlap there, but actually running the benchmarks and enforcing the benchmarks as security rules, they don't have much built for that. They got nothing for AIX, and Linux is not where the CIS benchmarks are. So they're way behind on partnering.

We had proof of concept at one point before the VMware purchase of SaltStack. And it had some merit, but the reality was it was under-implemented. And the merits were all in Linux. It was a good first stab at it, but it didn't have enough to implement in our environment, and then AIX kind of washed it right out, and they made a statement that they weren't going to support it. So it's been ruled out for us for a number of months.

SecOps does not work for us. Their SecOps is so infant, and it doesn't support AIX that we just can't use it.

Unusable is unusable. So if someone gives it to me for free. I can't use it. The only good thing is they've thought about it, but to me, they've underwritten it and haven't given it the attention to be a real product.

We use CIS (Center for Internet Security) Benchmark. It's actually a membership-type thing. And they have hardening rules and benchmarks, and it's a very common standard. 

They have products out there that Syscat is an older one, and they have a newer one, which I can't remember the name of. But it runs on your system, and they have benchmarks in there, and it scores your system based on hardening. 

We maintain a matrix of our hardened systems on a daily basis and know whether that score changed or not and alert if it does change. And then, in our environment, we have a whole lot of other tools out there.  

I would rate my experience with the initial setup a three out of ten, where one is a complex process, and ten is a difficult setup process.

This solution is really unusable from my perspective at this point. Overall, I would rate the solution a one of ten. 

We use so little of Red Hat Satellite. We use it for patching only. And I liked it better when it was the spacewalk equivalent, the informant thing. They're putting too much effort into the Virtu utilization and not enough into the day-to-day operations, for patching and stuff. Patching is a plugin as opposed to, like, the main product. Which is what we use it for.

So we're actually writing our own at this point because it's so heavy right now. The old satellite was good. Not great, but good. This one is just way too much overhead and focused on stuff we don't use.

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

Segmentation, specifically micro-segmentation, and also for its extended service between sites to keep the same IP address on all sites are valuable features of the solution for our company.

The solution could benefit from improvements in its pricing and scalability.

I have been using VMware NSX for two years. Also, I am using VMware NSX-T 1.0

It is a stable solution. Our company is migrating from VMware NSX-T 1.0 to VMware NSX-T 3.0.

In terms of scalability, I would rate the solution a seven out of ten. Currently, VMware NSX is being used extensively in my company by approximately 1,000 end-users.

When our company contacts VMware's technical support, we open a ticket for our support request. In the past, we escalated issues to VMware support and raised tickets to receive resolutions.

The solution's initial setup process was easy.

The implementation process for the solution was executed with the assistance of our organization's in-house team.

Regarding the deployment process, we begin with the manager and the product. Next, we deploy the controller and proceed with the requirements of UA6. Subsequently, we configure the DLR, ULS, or UDL.

I don't look over the pricing and licensing of the solution.

Before our company decided to go with VMware NSX, we evaluated VMware vRA and VMware vRO.

The solution is highly recommended for those with similar use cases as our company, given its features and the exceptional support it offers. The solution's prompt and responsive support team makes it a reliable option. Overall, I rate the solution an eight out of ten.

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.

NSX has excellent security features like virtual firewalls. I also like the micro-segmentation features, which are useful for the virtual machines inside the servers.

I started working with Nutanix NSX last year. 

I rate NSX eight out of 10 for stability. 

NSX is easy to scale. 

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'm not implementing. I am selling the solution. You can use it on-prem or in the cloud. If you are using SRM, including NSX in your workloads makes things easier. You can easily move everything, including the network security and several layers inside the appliance, to the cloud or any other site.

VMware has a subscription and perpetual license. In the New Year, they're changing many things about the licensing model. Previously, NSX was licensed according to the number of sockets inside the appliance, so we bought VMware licenses based on that. However, that may have changed this year. We are still contacting the vendors to understand the new licensing strategy.

I rate VMware NSX nine out of 10. I recommend it.

We were using VMware NSX for high availability. 

We recently used it to migrate a way to the public cloud.

The migration methods are the most valuable aspect of this solution. The rest is just overly complicated.

We had some issues with the cloud version.

It needs to be cheaper.

We are stopping its use. We won't need it because we'll be using cloud-native.

The company has been working with VMware NSX for six years.

I have hands-on experience with VMware NSX.

It was on-premise, but we just used it to do cloud migration to VMC, and it will be removed after that.

The on-premises version of VMware NSX was not stable, but it was for VMC migrations. 

The on-premises version of VMware NSX is not scalable.

The cloud version is most likely fine. I couldn't really say, but after the on-premise system was implemented, everyone was afraid of change. It was really flaky.

We don't have a large number of users. It is not used as such by people; it is a piece of infrastructure software.

There would have been less than half a dozen, not very many.

I personally have not had any contact with technical support.

The initial setup is complex.

TCS assisted us with the installation.

If five is a good price and one is a high price, I would rate the price a one out of five.

I would not recommend this solution to others.

As a technical solution, I would rate VMware NSX a five out of ten.

I primarily use the product as network virtualization software.

VMware NSX is a great product for network virtualization. No other vendor can offer this kind of solution up until now, and it's great for enhancing security at the virtual machine level. There is micro-segmentation, and a distributed firewall, and all network and network security components can be virtualized with the help of this NSX-T stack. It is a pioneer software solution for network security in a virtualized environment.

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

NSX features include micro-segmentation, distributed IPS, IDS functionality, URL analysis, gateway firewall, logical routing, and all the staple networking solutions like DNS, DSCP, and routing. All these features are very interesting.

The solution is stable.

We can scale it if we need to.

It should support Hyper-V also. Nowadays, NSX supports the KVM and ESXi hypervisors only. It should also support Hyper-V and Citrix hypervisors.

There have already been lots of improvements. For example, they edited the intelligent plans and added an advanced load balancer. The latest version, 4.0, really has all the features you need.

It's a bit complex to set up the product.

I have a total of around three years of experience using the NSX-T solution. 

The stability is good architecture-wise. We haven't had any issues. 

The solution can scale well. 

It is not a user-based solution. We deploy it to about 20 servers. 

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

It is a little bit complex to set up. It depends upon deployment. Either it is greenfield or brownfield deployment. If it is greenfield, it is very easy. If it is a brownfield deployment, so you need to take care of multiple scenarios of your network, and you need to understand the network architecture, then the deployment of services. 

While deployment requires a complete team, maintenance only requires on VMware administrator. 

We handled the initial setup with the help of a third-party SI team.

This product provides end-to-end visibility and security to your virtual environment. So it's a very huge return on investment in terms of security enhancement and maintaining cybersecurity posture.

The cost of the solution is moderate. I'd rate it three out of five in terms of affordability.

There is no other option available for this kind of product.

The product should be implemented in any IT infrastructure virtual environment. It is a must-have.

I'd rate it a ten out of ten.

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.

Apart from the normal functionality, a few things are quite useful, including multi-cloud networking. They have container networking and load balancing. Those are quite useful in terms of when we are designing a solution.

It's a pretty mature platform right now. 

The initial setup is straightforward. 

We found the solution to be stable. 

It's scalable. 

I haven't found any shortcomings. 

It might be nice to have more AI in the future. It would help keep us from redesigning every time. 

I've worked with the solution for four years now. 

The solution is stable and perfectly fine. There are no bugs or glitches. It doesn't crash or freeze. 

The solution can scale well. 

We had a user base of around 1200 people.

I dealt with tech support during pre-deployment, and they were fine. They were helpful when we were dealing with staging cases. I wasn't an active part of the actual deployment and can't speak of how helpful they were in that part of the process. 

I was the previous architect for the NSX, not the implementer.

My understanding is the setup process is quite straightforward. 

Our deployment was quite big. Including the staging and all the stuff, we were able to deploy in a four-month timeframe. That is not only NSX, that is the complete deployment of the cloud. We had a few issues here and there, however, overall, it was fine. 

It's easy to maintain for the most part. The orchestration layer for it was a bit hectic work for us. That needed a dedicated VMware team. Apart from that, everything was quite smooth for NSX or vSphere, et cetera, and it is quite simple to manage it.

The finance team handles the licensing agreements. I can't speak to the exact cost.

When going for multiple OEM solutions, like Juniper, Cisco, HPE, et cetera, NSX will be quite useful. Don't go for the ACSIs and all Juniper proprietary options since future upgrades will be a bit tough if something needs to be added. Therefore, if it is a multiple OEM architecture, go for NSX, it'll be more helpful.

I'd rate the solution eight out of ten.

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.

NSX extends Layer-2 scalability on Layer 3, covering the vRO and extending the capability on Layer 3 by decapsulating using a new mechanism. NSX-V was designed to use with VMware products and Success 360, providing more flexibility toward different levels of cloud, containers, and components. NSX-T gives you the ability to stretch your network across different view locations. If you have multiple sites, you can connect them using NSX-T.

In the next release, they should enhance the visual interface. With NSX-T, it's difficult to communicate between the public cloud and the container. 

I have been using NSX for three or four years. 

NSX is stable.

NSX is scalable. You can deploy it on one node or a three-node cluster.

I rate VMware support six out of 10 for NSX-V and seven out of 10 for NSX-T.

Deploying NSX is difficult. VMware NSX has three components: management, controller, and database. You have to understand each of them and where to deploy them. There are lots of logs as well. The deployment varies whether you are deploying on a VM, public cloud, or standalone hardware. Each has its own prerequisites.

First, you have to enable features on your physical equipment, enabling you to install NSX. You have to deploy the dependencies and fix the board. The deployment time depends on the equipment, whether it's from Cisco, Jupiter, or another vendor. They have different approaches to enabling NSX.

The licensing is based on the CPU or the physical unit.

I rate NSX nine out of10. 

The most valuable feature of VMware NSX is the load balancing and routing of firewall rules. Many of the features are beneficial.

I have been using VMware NSX for approximately four years.

VMware NSX can be stable. However, before you start, you need a very thorough sturdy design. Once this is complete you can go on building your VMware NSX in your environment. 

I went to VMware to look at their best practice designs, but they didn't apply to our environment. I had to take some parts of different designs and build my own that was exactly what was right for us.

Get the designs first, study them very thoroughly and after that, you can implement what will work for you.

The scalability of VMware NSX is very good. However, you have to take into consideration that you have to study their documentation.

The amount of users or devices VMware NSX  can handle depends on the resource that you allocate to the Edges and to the management cluster. They are small, medium, and large. A large allocation can handle thousands of virtual machines. We mostly deploy medium to large-scale systems.

The support from VMware NSX could improve. We are a large company and when we have an issue we do not need to waste everyone's time with level one and two support. I try and explain to them I need level three support but they say they have to follow protocol and pass me through the different levels.   

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.

If you have experience with the setup of VMware NSX it is simple, but if you do not it could be difficult. I would advise new users to contact professional support from VMware.

The price of VMware NSX is reasonable.

I rate VMware NSX a nine out of ten.