VMware NSX Reviews

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.

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. 

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 most valuable features are stability and low cost.

There are always issues integrating with Cisco.

Switching is always a big problem for us because our switch is not supported.

If the integration was more open, then it would be good.

I have been using VMware NSX for three years.

We are using the latest version, and we already want to upgrade it.

It's a stable solution. We plan to continue using it.

There are three users in our organization who are using this solution.

VMware technical support is good but we find that the Cisco support is better for us.

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

The initial setup is straightforward but still takes time.

It takes longer to deploy than Cisco products. It takes between three and seven days to deploy,

We had a team of five for deployment. Two are from our company and three were from the vendor.

We have a license.

It is an expensive product, but cheaper than some competing solutions.

It's a good product.

This is a solution that I recommend.

I would rate this solution a nine out of ten.

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.

Positive

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.

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.

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.

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.

The microsegmentation is great, and the security team thinks it is great.

The solution is quite complex. You need to keep your thinking cap on and know what you are doing: Go to the training and listen to the solution architects when they come in because they have a lot of knowledge. 

There is a concern and some confusion around who owns NSX in the end, whether it's the network team or the VMware team. There is not much confusion about this anymore, but there was at the start. Would it be owned by the network team, who might never even have seen VMware before, but would understand firewall rules? Or would it be owned by your average VMware person? As far as someone else putting it in, make sure you know who is going to own it, and they have the staff and the capabilities to cover it.

The solution is robust as it covers everything we want to do and is stable, so we're happy enough with it. We have had no problems so far. Everything is great.

We have not seen any problems, but we are only at 10 applications though. There is still a long way to go.

We haven't had any problems to contact tech support about yet.

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

The initial setup was simple. We started probably in December of last year and did a lot of prep: A lot of VMware upgrades, licensing upgrades, etc. All this was done in advance with VMware's help. The project came in for install in June and it took about two weeks. It was great, and we did not have problems.

VMware came on site and did the install with us, then handed it over, not transferred. They did the first two apps, then we have done the next eight. So, we haven't had to contact them for support yet. 

We deal directly with Dell EMC and VMware via Dell. This solution was the only thing on our radar. We didn't even look at anything else.

If a colleague was to ask me if it was a good idea to go ahead and put it this solution in, I would say, "Straightaway." I wouldn't have any doubts.

Usually, when we are deployed for a period of two months, we have to program VMware NSX from the beginning and set up all the security measures.

VMware NSX has helped by saving time. A task that would typically take a man several days can now be done in one or two days.

The most powerful feature of VMware NSX is the micro-segmentation that allows us to separate the different protocols our application works with. We also benefit from automation capabilities using Python scripts.

I cannot think of something specific that needs improvement since our needs are currently covered by VMware NSX. I have no complaints regarding the user interface or any technical issues.

I have been working with VMware NSX for two years. That said, it is not part of my everyday work.

No stability issues were mentioned.

No scalability issues were mentioned.

Our technicians have a good support experience from the company. I would rate customer service eight out of ten.

Positive

We have to follow specific rules and use accredited tools like VMware and have not used anything else.

We underwent training first, which made the deployment process not very difficult.

The primary benefit is time-saving for my organization.

VMware NSX is a little higher in price compared to the competition. I haven't gone through the internal analysis.

There are other solutions available, however, we are required to go with specific vendors due to accreditation and our organizational requirements.

I'd rate the solution nine out of ten.

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.