If you were talking to someone whose organization is considering VMware NSX, what would you say?
How would you rate it and why? Any other tips or advice?
I would recommend this VMware product. We are not using vCloud Director.
I rated this solution a nine because it's easy to use. It has a lot of capabilities, like microsegmentation, which is very good. If you're worried that NSX is too complex, I would tell you to take another look. If you compare NSX to a similar solution you might find it to be a bit more complex. Usually, the guy that comes in to implement NSX isn't the network guy and will lack the knowledge for the program. He can lack the knowledge for this program and will therefore think it's complex. You need somebody with network experience.
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.
PoC the platform before you test it. It is not so bad. We are using the VVD implementation. It is implemented together with the vRA, vROps, and other solutions.
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 would rate this solution a nine because we maximize most of its features. We have many advantages with the cloud infrastructure. I would tell someone looking into this solution to go for it. At first, it may seem to be complex but using it will make it easier to manage jobs. Yes, its initial establishment can be complex but you will see its advantages later on.
I would rate this solution an eight because of its ease of deployment. I'm a partner so this is what I mostly care about. Also because of the ease of scalability. If you're looking into NSX or similar solutions I would recommend you to first learn about vSphere and other VMware products because it's essential in order to implement NSX. Without that knowledge, it would be hard for you to understand. And to those who think NSX is complex I would say it's not. You need to try it and see.
Get it in your environment as soon as possible. Network segmentation is hard. A lot of businesses still use the traditional three-tier system, because it has been proven, but it isn't particularly robust or secure. Realistically, it's a natural step in terms of network management to move to micro-segmentation. It just makes sense. If someone is worried that the solution is too complex, they should hire people with experience.
I would recommend it to another person. We do not integrate it with vCloud Director. I don't use load balancer at the moment.
NSX is a good product.
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.
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.
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.
To those who say this solution is complex, I would say it is but not for the key user. You just need to learn the standards and mechanics for your specific product. That means that it's simple even if it's really complex beyond that.
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.
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.