VMware NSX Reviews

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. 

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.

The easy integration and management are the two most valuable features.

In regards to Layer 4 and 7 load balancing with a solution, for us, it's about the continuity. We look for different ways to create something similar while making improvements. We like to include different services and make sure that we have high availability, not just in our closer environment but also around multiple environments.

Microsegmentation is important. We cap it depending on the compliance and regulations that are in the systems for every single company's requirements. It depends on the size of the customer, but I don't see a reason not to use it. We cap it based on industry, size of a company, and the compliance regulations that the company requires. Also, we consider the nature of the industry, although the reality is that security applies to everybody. Some industries take it more seriously than others because of their policies, rules, and regulations that they have to comply with. Ultimately, security is an issue that affects everybody and is important for all to have.

The engineering team has room for improvement. They should have more of a Knowledge Base about different case studies and should develop more advanced features. These kinds of improvements will change the way things get done.

The stability is great. That's one of the things that we can quantify and leverage through NSX, because it's less complex. We have the availability to manage multiple things at the same time. We can identify problems before they manifest. 

Their technical support is great but I believe that it also has to do with the relationship that we've built with the technical support staff. We're not afraid to have conversations. Most people try to figure things out by themselves but we don't hesitate to reach out to technical support. They have an intelligent team.

We based our decision to switch solutions on an analysis we did. We based this analysis on what we are missing and what the impact is of not having it.

In the beginning, implementation was quite challenging. Once you know your way around it, it becomes a lot easier to navigate. Every master was once a disaster. The beginning stages are the most challenging but as you pass through the initial starting point, you begin to realize how easily it can be integrated with multiple devices. 

I have been in technology for 23 years and I see the constant evolution of not just the portable technology but also the management. I believe that adapting to the multiple levels of security inside of the business management is a challenge for different vendors.

We look at different vendors for our customers. It depends on the compliance and regulations that are in the systems for every single company's requirements. Every company will have specific needs for certain features that other options do or don't have. 

This solution has helped our clients save CapEx. The agility and speed of the implementation offer CapEx savings. 

It does and doesn't prolong software refresh. It does because there is better integration with the product. It doesn't because there are new features developing and people like to replace their hardware. They will have better chances of getting more value out of their software solutions because now they can reach more control of multiple functionalities. I would approximate that it saves the hardware for around two to three years.

I have rated this product a seven because this product still needs to evolve. It's a good product but it's not great. 

If you are considering NSX or a similar solution I would advise that you have to adapt or die. Technology is emerging with different features. It is important to be in that conversation. You've got to move into the new trends. There are multiple solutions, and there will be different brands with different features but ultimately you have to find a solution that will meet your exact needs. 

To those who say NSX is complex, I would say that every master was once a disaster. In the beginning, it's going to be challenging. When you start something new, it very might well be a disaster and you will probably find it hard to navigate. Once you overcome the complexity issue, it's just a matter of perception. It's not really complex, despite what you may think. The solution is evolving, getting better. This is a smarter way to do things. This solution is at another level. 

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

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.

We like that NSX is faster. My colleagues manage their own firewalls so they can freely deploy their VMs. The ability to freely deploy is one of the most valuable features. 

This solution is robust and agile. It was stable for one year, there was no impact. In the last two months, we had two big incidents.

We are happy with the scalability.

We have needed to use their technical support. We've have had good and bad experiences with them. We don't always find them to be so impactful. Sometimes the support guy isn't so on top of resolving the issue and it can take a while to sort out. 

It was deployed by a VMware consultant. 

I would tell people who say that NSX is complex that it's not as complex as they think and they should definitely consider this solution.

I would have rated this solution a nine, but in the last two months, we have had two incidents with them. 

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

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

The most valuable features would be VPN and PCM. 

I use L7 balancing. I can use it for two tethers and I can see the source IP. I can split for monitoring for me and my analyst.

I would like to see extended performance charts in other versions of NSX. For example, CPU usage, memory usage, and bandwidth usage on NSX.

I would rate this product an eight because it's a good product but it needs more work. They should fix some of the bugs.

NSX is very stable. I don't remember when I have ever had any trouble with NSX. It's been a great process.

The scalability is not perfect. 

We use technical support but not for NSX. We don't have any trouble from NSX and we, therefore, don't need technical support.

I found the initial setup to be complex. 

NSX can reduce costs and has good service. It is easy for you and your users to use. 

We have integrated this solution with vCloud Director. Without NSX you can't deploy the cloud.

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

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.

Microsegmentation and automation are two features we have found to be the most valuable. 
The microsegmentation feature is a mature feature used in NSX-V and NSX-T.

We are trialing Layer 4 and 7 load balancing with this solution, as it's very new.

The next release of NSX should try to make Kubernetes and container integration a little easier than it is now. It's quite a complicated process.

I would rate this solution an eight because it doesn't have Kubernetes integrations yet, and it isn't multi-federated. Those are some of the things that need to be added to the product. 

This solution is stable and robust. We've done failover testing and it kept working. 

I have found this solution to be scalable, more so now with NSX-T than NSX-V.

Their technical support team is firm. It's mature, and they've got a good support team.

Business is demanding more agility and capability than ever before. NSX offers solutions to those business-level problems.

The initial setup was straightforward. You just have to click it and follow the manuals. Deploying the infrastructure code can be more complex.

We looked at Nuage and Cisco. We decided to go with NSX because they have a good understanding and a strong VMware stack.

I would advise a colleague at another company who is researching NSX to know how the technology can answer their customer's business use cases. For those who say NSX is complex, I would agree that it can be complex but you can abstract that complexity through automation and Service Catalogs to make it easier for end-users to consume.

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.

The organization of it is logical, useful, and intuitive.

The security part of micro-segmentation is getting more important.

We are early in our use of the product, but stability has been good so far.

It seems like it will scale.

We have not used technical support.

We had some complexities implementing into the other parts of a network. Otherwise, the NSX product was straightforward to setup.

We deployed it in-house

We were already using other VMware products, so this product seemed to be the best product for our purposes. The solution is less complex than other competitive products.

I would recommend this VMware product.

We are not using vCloud Director.

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.

Our primary use case is to change from Cisco.

• It is scalable.
• The microsegmentation is a good feature. You can segment details, products, or hardware information.

It is stable.

It is scalable.

We haven't used technical support.

The first time setting it up was difficult. After a couple of installations, it should get easier.

We set it up with a partner.

NSX is a good product.

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.

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. 

Any administrator with basic networking knowledge, in a couple of days, can be in full control of their networking without going through a networking engineer.

The microsegmentation feature is the reason why everybody wants to implement NSX. It's just awesome. I was impressed by it when I saw it for the first time. However, now that I see it everyday in production, it works perfectly.

We would like them to improve the deployment time.

The management console also needs a bit of improvement.

In the beginning, the stability needed real improvements. Nowadays, it works like a charm.

I have found the solution to be robust. I haven't had major issues except for a simple connectivity one, probably because it is not integrated with cloud.

The scalability comes along when you implement it. Within a couple of clicks, it makes the process so easy. This is why companies go for it.

The initial setup was a bit lengthy in the beginning. Now, it is a bit smoother. While I like it, it still takes time to setup. It is a bit slow, which is surprising.

The solution has helped to prolong hardware refresh.

The solution is not complex. Though, you need to have some experience in networking, but just the basics that come when you work in the industry. However, if you've never worked with networking, start at the beginning, then NSX will come along easily.

I recommend building your own lab and continue to keep breaking it. Break your own lab, because you'll find weird things.

We have not integrated with vCloud Director as our customers are not very eager to work with automation yet.