VMware NSX Reviews

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.

I was an intern at a relatively large company here in Morocco, and NSX is a great solution.

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.

The Distributed Firewall is simple to add to the network and rules are easy to implement on it.

It should be more adapted to the physical side of network topology in order to prevent unavailability.

To be able to do the DR and SRM migrations from datacenter to datacenter, we're able to do them with SRM with VXLAN, with the NSX product.

Just being more knowledgeable about the different functions. I think the product is fine. It's just learning more about the product, and how you can benefit from it, and what it's got to offer.

Very stable. We've had great success with it. It's a different mindset for the actual network folks that are used to building an old traditional way, but it's much faster to get things deployed with firewall rules.

It's definitely scalable, however large, however small. We can bring people in with VDI desktops, with a control set already around that, to be able to control what they get without having to create a new VM and recreate all the policies. It's already done upfront.

It's great, if we have any problems at all, we give them a call. If there's something that's new that we're trying to figure out, they're real good about helping us out.

At first, it was a little complex, but it's more internal, just learning a new product and what it can do for you. But once you get all that set up, and done with the collaboration, and the other groups, it's really not that bad.

In terms of selecting a vendor, our end goal is to be able to accomplish a certain function that we need to for the business. But also, if we have any trouble, to be able to call and get some support, and work through those issues without, "You bought the product now, so you're on your own." They've been real good about support.

It's changed the way we do things. It's made things a lot more easy. Once everything's set up, and you have the collaboration from all the other different groups, it just works. It's going to help me be able to do a lot of the DR stuff that I'm working on with VXLAN, working through NSX and all those rule sets.

We can deliver the network that customers need quickly and safely. That is most important.

There is one feature I'm finding with VMware which is special for us from IBM with JIRA routing protocols. This is in the future that they are planning, especially right now with our compatible AWS. AWS is good, understood, except for the software to improve, probably with Amazon right now doing this partnership. VMware and access are going to be improved for that.

It's totally stable, because right now it's running version 6.3. It's very mature. Even the versions with VMware 5.5, 6, and 6.5 are very stable right now. It's becoming more open to other environments, too. It's not only working with VMware, but also with Red Hat and Ubuntu. It's an amazing product.

Totally scalable. I almost can tell this is the first real multi-tenant product from VMware that will scale out and do real multitenancy.

Tech support is nice. It could be a little bit better. Simple, since this is a new product, you don't have too much specialists over the world. Because it is a mix between the virtual world with VMs, and now networks, it's networking virtualization. So, VMware with NSX is being a pioneer. They are improving their support every day.

NSX gives us the ability to put our network, NSX, onto any network there is, which allows us not to have to go to the network team to create networks our VLANs for networks. We can just create all our networks right from the start. Whenever we want to spin something up, we just spin it up.

So far, what I've seen here at VMworld, it seems to be improving just the same line as everything else. It's going to expand, grow and grow and grow. It's going everywhere. It's not just going into "I'm using the V version of NSX," but it's going out to every environment. It's going out to all the clouds so that even if you have the V, you can also use the cloud part and put it into there, so it seems to be growing where it needs to go.

It still needs to grow. There are still some features that it doesn't do, like it doesn't do multicasting. It does do some multicasting, but it's within their own infrastructure, but multicasting in general, it doesn't do.

So far, it's been very stable. I've used it since the very beginning and it's been very stable in the beginning, and as they've added more and more features, it's become more and more stable in the environment; that is, better in the environment because we're able to use more and more features within it.

So far it's been very scalable, and with the new versions that are coming out, it's even more and more scalable. They've added more and more features of routing that they didn't have in the first versions, which allow it to be more scalable. It's become better than the actual infrastructure, the original network infrastructure that's there, because we can lay it on anything and it will scale to any part of the network that we want.

So far, I've had very good tech support. A lot of the guys we talk to are very knowledgeable, and if they don't know it, they're able to talk to others within their group that will know it. So I've gotten very good results from them.

The installation is very straightforward. The part that gets complex is how you do your routing, how you do your ESGs, how you set up the actual network itself within it. But once it's set up, you just create virtual switches and put any network you want on it. It becomes almost seamless.

In terms of criteria for selecting a vendor, it's a little of everything. It's the reputation that they have, but it's also more of the tech support, as well as the documentation that they have, because not everybody in their environment, as well as your own environment, knows everything. So you have to be able to look up stuff and have that knowledge to be able to do it, as well as allow them to do it.

They have a lot of good KB articles on what's going on, so if you need a problem solved, you look at that first and you'll be able to find it pretty easily.