VMware NSX Reviews

NSX is under the platform. NSX is used on a cloud-only platform for clients.

The solution works well overall and we are happy with it.

We enjoy the micro-segmentation and the ability to extend the network on Layer Two.

It is stable. 

The solution can scale well. 

We have found the UI to be very good. The interface is intuitive enough.

It offers good documentation. 

I'm not sure where the solution can be improved. 

We did recently need a patch to deal with an outage on NSX.

The price is rather high.

We've been using the solution for two years. 

The solution is stable. We have just had an issue that caused an outage of some of our NSX. However, now it's okay. VMware gave us a patch to correct it.

It is a scalable product. It's not a problem.

There are about 3,000 VMs on our data center. There are a lot of customers.

When we had an issue recently, VMware asked to upgrade to a high level of support to correct the problem.

The initial setup offers an average level of complexity. It's neither too difficult or too hard. 

I'm a system engineer, so I don't know exactly what the price is. However, I am aware that it's high. It's better suited to larger enterprises.

We are service providers and partners.

I'd rate the product eight out of ten.

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

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.

Its flexibility and integration with other VMware solutions are NSX's most valuable features.

The microsegmentation feature is very useful.

We would to have a reverse proxy. This would add great value to the solution. 

We would also like better integration with the standards on the market. For example, with OSPF, their integration in NSX is very low. It's not a full OSPF integration. It is too thin from a protocol perspective.

The product need to be improved. It is too complex.

The stability used to be perfect. Now, it is okay.

From a distributed firewall perspective, it's a solid solution.

It is scalable by design, so it's perfect.

The technical support is good. We have encountered several problems with NSX, and every time, support has found the solution to resolve the issue. 

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.

It was a complex setup.

We implemented it ourselves.

The solution is expensive.

We did not consider anyone else.

If someone is looking for security in a vSphere environment, I don't know of another solution in the market besides NSX.

We had to buy new hardware in order to introduce NSX into our data center.

We don't use load balancing with this solution.

We don't use vCloud Director.

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.

The most valuable feature of VMware NSX is the DFW (distributed firewall). The distributed firewall is much better and more powerful than the physical firewall because it's applied at the beginning level.

The software-defined version of VMware NSX contains all the security features like IPS and IDS. In the physical space, you have to get separate IDS, security, or load balancer products. VMware NSX provides several features like VPN, load balancers, DFW, and gateway firewall.

Since most people are very much used to physical networking, they find it difficult to use VMware NSX in the initial stage.

I have been using VMware NSX for the past six years.

The solution's stability is very good compared to its older versions. It is advisable not to go in a production environment with the latest version because it might sometimes have new features that can break.

I rate VMware NSX a nine out of ten for stability.

We can easily scale the solution with the current product version if we have more users.

I rate VMware NSX a nine out of ten for scalability

The solution's implementation is easy.

The initial phase of deployment involves deploying three NSX Managers. Then, you have to plan to do a lot of things like configurations and routing. If you have everything ready for configuration, you should be able to complete the VMware NSX installation in a month.

In the case of daily deployment, it depends on how much we are deploying and how many configurations we are doing. Two weeks should be more than sufficient to complete the configurations if we do it daily.

VMware NSX is a cheaper product compared to its competitor, Cisco.

Since most people are very much used to physical networking, they find it difficult to use VMware NSX in the initial stage. However, once you start using it, you'll be very much fond of the particular product. VMware NSX is very easy to manage.

You can deploy the solution on the cloud or on-prem, depending on the customer's requirement.

When changing from the physical to the virtual space, you have to plan the routing part. You'll have a hardening of networks in the physical space. However, when you bring it to NSX, everything is at the hypervisor level in the virtual space. That's one thing you will have to plan because a few critical applications might require a VLAN-backed network.

They have a restriction that they can't move it to the overlay networks and must remain in the physical VLAN. We have to plan properly for migrations because improper planning can break the current network or operations.

It would be good if users use all the features in the solution to have everything in one place. Users can access the web UI to manage security, load balancer, and VPN protection.

Overall, I rate VMware NSX an eight out of ten.

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

The solution is easy to use and is good for management control.

It isn't easy to deploy.

I have been using VMware NSX for almost 10 years.

We currently have 2,000 users.

The solution is scalable.

I haven't used technical support. If I have a problem, I find out what the best practice is.

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

The solution was easy to install but not easy to deploy. 

We have a technical team. The time it takes and the amount of people needed for maintenance depends on the solution that is deployed. Sometimes it is easy, and sometimes it takes more than one day.

The subscription is on a yearly basis.

I would rate this solution 8 out of 10.

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

One significant advantage of VMware NSX is the ability to provide advanced security at the micro-level, focusing on securing applications and workloads rather than just the network structure or virtualization-based network security.   

I believe we need to attain a certain level of maturity and work closely with multiple customers to make substantial improvements and achieve notable results. The feature it can improve is essentially application-based load balancing with intelligent load distribution for applications that require redundancy and high availability. This feature operates at a micro-level, specifically focusing on the payloads of applications.

To clarify further, I believe that if NSX offers this functionality along with robust security measures for application payloads, it would greatly benefit customers. Instead of investing in additional devices or appliances for load balancing and security, organizations would likely prefer to leverage NSX's integrated capabilities in this regard.

We have been using this solution for the past six months. 

As for stability, the customer I mentioned earlier is extremely satisfied with the product's stability.

VMware doesn't have a physical presence in Pakistan. They recently initiated their operations here. However, we do have interactions with their team based in Singapore, and I must say they are quite supportive. The customer hasn't raised any complaints regarding their support. The time required for deployment can vary based on the size of the infrastructure, but typically, it can be accomplished within a two-week timeframe.

Positive

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.

Regarding the initial setup, VMware products, including NSX, are generally straightforward to set up and deploy, so complexity hasn't been an issue.

The implementation of VMware NSX can be cost-intensive, especially if an organization is looking for a comprehensive solution. The costs can vary based on factors like the level of conversation and discounts obtained during negotiations. Some government organizations, for instance, may find the prices relatively high, leading to concerns about budget hikes, especially when deploying the solution across the entire organization.

Regarding maintenance and support, they are typically included in the standard licensing costs for enterprise-level businesses. While these costs can be significant, many companies opt for standard licensing to ensure they have access to necessary support and maintenance services.

The deployment of NSX security can be somewhat challenging, and it requires a thorough understanding of the organization's specific needs and objectives. To effectively implement NSX security measures, it's crucial to have a clear understanding of the applications, payloads, and various components within the network environment.

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

VMware NSX offers some of the best features for security, such as micro-segmentation. This feature allows us to define policies on a per-virtual machine basis. For example, if we have four virtual machines, we can have four different firewalls attached to each of the VMs. This allows us to monitor the traffic between each VM, as they will have to go through two firewalls or two IPs. This added layer of security provides a great benefit to those utilizing the solution.

Despite being somewhat behind in the cybersecurity field, VMware should develop a cloud and a red team to continuously monitor for new malware and ransomware. They must maintain their own cloud to do their own research, and send the resulting hashes or values to all customers using VMware NSX. This will ensure that each customer is regularly updated with the latest malware and ransomware hashes to keep their systems secure.

Web filtering is a good feature that I would like to have added to the solution.

I would like the ability to limit the bandwidth per virtual machine to ensure that I understand the throughput requirements of any application that is running. This way, I can be protected from the risks of a DoS or DDoS attack, which may require a high level of throughput. This limitation would apply to Layer 4 or Layer 5 of the network.

I have been using the solution for three years.

VMware NSX is stable.

The great advantage of VMware is its scalability and hardware independence; The solution is compatible with a wide range of server brands, including Dell, Lenovo, HP, and Cisco.

My job was to offer consultancy, demonstrations, and conceptual approval to the VMware official team and their partners.

Positive

Of all the cybersecurity vendors we have, the installation of VMware products is the most straightforward. The time needed to deploy depends on the purpose of the use case. Complex tasks between two data centers could take up to four days, whereas micro-segmentation would usually take only two days.

I give the solution an eight out of ten. The solution is missing the red teams and R&D necessary to continuously receive updates from the cloud. Additionally, two other features are absent from VMware NSX which are bandwidth limitation and URL filtering.

We have two people using the solution. I'm the only architect, and the other person is mainly responsible for checking logs to determine if any resources are needed and then assigning those resources to the appropriate virtual machines. 

For someone who wants to secure their data center and three-tier application architecture (database, web application, etc.), they should use micro-segmentation with VMware NSX. This would enable them to set policies on a per-virtual machine basis. For example, if each VM has two virtual NICs assigned to it, each virtual NIC would have its own firewall, policy, and IP. This way, even when two virtual machines need to communicate with each other, their traffic will pass through two separate firewalls within the server. In addition to micro-segmentation, NSX also provides switching and routing services. The use of a data center firewall can be cost-effective for enterprise customers, SMBs, and medium-sized customers. By utilizing the routing, switching, and firewall capabilities provided by the data center firewall, the load on data center switches and routing can be reduced, making it a more cost-efficient option. The throughput required by the data center firewall, be it a Fortinet or Palo Alto Checkpoint, is directly proportional to the cost. With increased throughput, the cost of the firewall will also increase. VMware NSX offloads the workload from the data center firewall, taking on the task itself. This is possible without impacting performance because it is a software firewall, so it absorbs all the load from the data center firewall, providing the same security measures as the legacy firewall would.

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

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

The most valuable feature of VMware NSX is the high bandwidth.

A room for improvement in VMware NSX is that it has some security vulnerabilities, which means my company has to apply the patches every once in a while.

I have two years of experience with VMware NSX, and I've worked with the solution in the last twelve months.

VMware NSX is a stable solution.

VMware NSX is a scalable solution.

I have no experience contacting VMware NSX technical support.

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.

The initial setup for VMware NSX is not that complex. It's in the middle, so I'd rate it as five out of ten.

I'm trying to remember how long the deployment of the solution took, but it didn't take up a lot of time.

A third party helped my company with VMware NSX implementation.

I have experience with VMware NSX.

I'm using the latest version of the solution.

Sometimes, VMware NSX requires maintenance. The third-party was responsible for the first time, and then the vendor took over the subsequent maintenance activities.

VMware NSX has about three hundred users in the company.

I don't know if there's any plan to increase usage for the solution.

My rating for VMware NSX is nine out of ten.

The stability or the high availability in connecting two or more servers has been pretty good. This is to maintain the operations in the possible highest stability. That was a very important part of this project since you have to move all virtual machines to the new infrastructure. It took a very, very long time to understand how the old architecture was arranged and how to migrate to our new architecture.

There were some issues in finance and other accounting. The applications there are very old. To move these applications, we had to use some controls or web services for programming in a new program, for example, in Python or visual C#. You have to move these applications to new programming software. It was very, very complex to move them. However, we ended up doing it very well.

ESX servers are a part that they don't implement. The client that this part of the VMware is important. You can implement more virtual machines using ESX server infrastructure. However, they couldn't complete this part since, for some arrangements in the contract, they don't put it in the contract. They need to buy new licenses to complete the project.

I’ve been using the solution for six to eight months.

The solution is very stable and reliable. There are no bugs or glitches, and it doesn’t crash or freeze. The performance is good.

We have maybe 2,000 users using the solution. We use them to move to new infrastructure.

I have experience using help desk support to understand all the users' needs. We were in the area of quality control, so all the requirements that the users or the managers were indicating to me, we had to transfer to the area of programming and they would say, “okay, I'll let you know if I can do it or not.” I was the go-between. It worked very well. Support was offering quality service.

I am able to help clients set up the solution. I’m an integrator.

The original cost started at $1,500. The solution is paid monthly. All the institutions have to pay monthly for the services in the cloud. They have to pay $30,000 every month for this service every three years.

I am not a reseller. I am an integration company. More prominent companies contract us and we work for them.

I’d rate the solution nine out of ten.

VMware is a very, very good product. It's used a lot here in Ecuador in a lot of enterprises and institutions.