We just raised a $30M Series A: Read our story

VMware NSX OverviewUNIXBusinessApplication

VMware NSX is #1 ranked solution in top Network Virtualization tools, #2 ranked solution in top Network Automation tools, #2 ranked solution in top Microsegmentation Software tools, and #3 ranked solution in best Cloud Security companies. IT Central Station users give VMware NSX an average rating of 8 out of 10. VMware NSX is most commonly compared to Cisco ACI:VMware NSX vs Cisco ACI. VMware NSX is popular among the large enterprise segment, accounting for 67% of users researching this solution on IT Central Station. The top industry researching this solution are professionals from a comms service provider, accounting for 30% of all views.
What is VMware NSX?
VMware NSX is the network virtualization platform for the Software-Defined Data Center (SDDC). By bringing the operational model of a virtual machine to your data center network, you can transform the economics of network and security operations. NSX lets you treat your physical network as a pool of transport capacity, with network and security services attached to VMs with a policy-driven approach.

VMware NSX was previously known as VMware Nicira.

VMware NSX Buyer's Guide

Download the VMware NSX Buyer's Guide including reviews and more. Updated: November 2021

VMware NSX Customers
City of Avondale, Lumeta, Kroll Ontrack, Heartland Payment Systems, Baystate Heallth, Exostar, Tribune Media, iGATE, NTT Communications, Synergent, California Natural Resources Agency, Bloomington Public Schools, Columbia Sportswear, Join Experience S.A, Schuberg Philis
VMware NSX Video

Pricing Advice

What users are saying about VMware NSX pricing:
  • "You can scale NSX if you have the resources, but it's usually expensive and complex to scale up."
  • "I was not involved in the purchase of the solution but I hear it is on the expensive side."
  • "The licensing fees are expensive and we pay on a yearly basis."

VMware NSX Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Kolawole  Olowoporoku
Systems Engineer at a tech services company with 1-10 employees
Reseller
Top 5
A flexible option for managing security, but setup is complex and documentation is lacking

Pros and Cons

  • "NSX's stand-out function is the distributed firewall. The firewall system is just top-notch, and I haven't seen another solution like it."
  • "NSX could better integrate with open-source products. Of course, it integrates with some, but I know many people are uncomfortable deploying NSX with certain open-source solutions, such as Radar."

What is our primary use case?

Our main use case is the distributed firewall. NSX can segment every application and server based on the ports they need to communicate externally. Ports that aren't required are inactive, so we activate them for some specific applications. We can get the ports from the application guys, activate the ones we need, and then disable the rest of the ports. We've done other things with NSX, but it's just mostly about the distributed firewall.

How has it helped my organization?

We typically run a lot of vulnerability assessments — sometimes spam testing — and get a lot of bad results because some ports are open. I think NSX has significantly cut down on that. Right now, we have been able to fix almost all of our problems with unnecessary ports being opened and related issues. We are secure in this specific aspect, so we can log other options. 

What is most valuable?

NSX's stand-out function is the distributed firewall. The firewall system is just top-notch, and I haven't seen another solution like it. Aside from that, there are numerous other cases where NSX comes in handy. For example, we've done intrusion prevention and implemented some next-generation firewalls for service training. We deployed some next-generation firewalls inside certain servers. Then we could bring all the traffic down that was meant to lead each server to a specific firewall. The security guys put policies on the firewall for checking signatures and hash values to contain particular security breaches within the server and prevent them from affecting the network. So we could use the particular firewall that we usually use and use it within the server close-up at the data center instead of the VH. 

What needs improvement?

NSX could better integrate with open-source products. Of course, it integrates with some, but I know many people are uncomfortable deploying NSX with certain open-source solutions, such as Radar. They don't integrate so well, and the integration is usually so complex that many people would rather not use them.

For how long have I used the solution?

I've been using VMware NSX personally for one year now, but I'm a consultant on this product, so I've deployed it for multiple customers.

What do I think about the stability of the solution?

We've experienced some bugs with NSX's user interface. For example, sometimes we click something, and it's not clicking. But they put out a lot of updates and patches. Also, they've added some particular boards on the applications. So with every update, they make the user interface more stable. 

What do I think about the scalability of the solution?

You can scale NSX if you have the resources, but it's usually expensive and complex to scale up.

How are customer service and support?

VMware support is great. I would rate their support eight out of 10.

How was the initial setup?

The NSX setup is complex. That's one area where they could improve. Generally, it's too complicated to deploy. You can spend two or three days on it. And if you've never done it before, it might take a week. So it takes a relatively long time and lacks comprehensive end-to-end documentation. We had inadequate documentation when we implemented it, but I think it's better now. Total deployment for us took more than two weeks, but there were some breaks in that time where we stopped working on it. We weren't under any deadline. If we were pressed, we could have finished in four or five.

After the initial setup, NSX doesn't require a whole lot of maintenance. It's mostly troubleshooting, checking error codes, etc. There is no dedicated maintenance personnel specifically for NSX. Some guys in the IT department support this solution along with several other solutions. We have about four to five people handling that side of things, but there are six of us in the whole department responsible for infrastructure.

What was our ROI?

It's hard to judge with new deployments because you need some time to start seeing a return. But after someone has had one or two years to achieve a mature deployment on the product, they'll generally be happy that they spent the money. After a year, I'm beginning to see the return on investment, but everyone would argue that it's still expensive for the first two or three months.

What's my experience with pricing, setup cost, and licensing?

VMware NSX is expensive.

What other advice do I have?

I rate VMware NSX seven out of 10. If you are considering NSX, I suggest that you practice the deployment and know your use case. Know what you want to do with it and understand why you want to use the product. Identify the security features you want to use and consider what it's doing for your infrastructure. We're still exploring the features. I'm not sure we're using all the features that come with the application. There are so many that we have not used. For now, we're looking at more use cases and expanding on that knowledge.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer:
Flag as inappropriate
Roger Nurse
VMware NSX T/V Consulting Engineer /Solutions Architect at Plan IT Virtual, LLC
Real User
Top 5Leaderboard
Allows for seamless micro-segmentation and the support is exceptional

Pros and Cons

  • "From a security standpoint, the customer was able to better secure critical workloads while routing L2/L3 worked normally, giving them more confidence that they would be ready for any potential security incident mitigation or outage (DR)."
  • "Traffic flow introspection topology visibility is definitely needed because at the moment, NSX-T lacks in this area."

What is our primary use case?

The Environment was an active-active Tier-0 multi-site deployment (primary/secondary).

It contained compute and management clusters, and a small number of transport ESXi nodes (between five and six) v6.7u2, vCenter 6.7u2, AD.

The primary use case was to implement micro-segmentation and route production workloads through NSX-T via BGP. Our customer needed assurances that BGP routing within NSX-T would be efficient.

We implemented a very simple architecture and setup site with one NSX Manager as the primary source. This was a financial customer, thus security was the main item.

We had to explain to the customer that NSX-T deployment and micro-segmentation were two different projects explicitly.

How has it helped my organization?

NSX-T has allowed us to implement micro-segmentation in the customer's environment seamlessly (zero-trust). We have also looked at deploying Tufin or Gardicore, ReSTNSX as alternative tools. The Environment was an active-active Tier-0 multi-site deployment

The organization was able to begin scaling out its production workloads and clusters.

From a security standpoint, the customer was able to better secure critical workloads while routing L2/L3 worked normally, giving them more confidence that they would be ready for any potential security incident mitigation or outage (DR).

What is most valuable?

The most valuable features are:

  • N-VDS Geneve encapsulation L2/L3
  • Less need for the VM to hit the TOR switch to communicate with VMs on the same ESXi host/segment (logical switch)
  • Micro-segmentation capabilities/tagging
  • NSX-T dashboard/compute usage across the configuration allows a quick view
  • The NSX-T configuration screens are fairly easy to navigate but they might need to simplify them a bit in future versions.
  • Very extensive detailed configuration items can be set in Uplink profiles to better map pNICs
  • Edge TEP and Host TEP tunnel config and troubleshooting is much more understandable and verifiable

What needs improvement?

Traffic flow introspection topology visibility is definitely needed because at the moment, NSX-T lacks in this area.

A hardware scan of the ESXi host for possible incompatibilities should be added to NSX-T/vSphere, as it would allow us to know in advance, for example, if a pNIC is not compatible with a version of vSphere before moving forward with an NSX-T deployment. 

It needs a better, integrated migration tool. Something like RestNSX with more elaborate capabilities from a troubleshooting perspective and pre-migration perspective would be an improvement.

For how long have I used the solution?

I have used this solution version most recently, as it has not been out that long.

Many companies are moving to v3 and v3.01

N-VDS will be depreciated in newer versions and integrated within the standard VDS

What do I think about the stability of the solution?

From a recoverability standpoint, if designed correctly and perhaps if VMware SRM is integrated with NSX-T, it would help the stability of workload availability.

From a routing perspective, NSX-T must be designed for redundancy with cross/overlapping uplinks from the edge nodes to your L3 upstream devices. Routing will be more reliable with default routes in place. Hardware compute and compatibility with the solution is critical for good communication via the  nsx overlay network.  Overall this solution is very scalable

What do I think about the scalability of the solution?

NSX-T is extremely scalable as a solution. Make sure that you plan your IP pools accordingly in advance if you plan to add many transport ESXi nodes in the future.

How are customer service and technical support?

VMware Global support for NSX-T/V is exceptional.

Which solution did I use previously and why did I switch?

We have never used any other solution. NSX is the premier product in this space.

How was the initial setup?

The initial setup will go smoothly if the design of the solution was done correctly. 

NSX-T can be complex if the discovery phase was not granular enough.

What about the implementation team?

We implemented it with an in-house team.

What was our ROI?

Customers will better be able to determine ROI once they have been running the solution for a year or so. How much they will have from the Capex perspective will have to be calculated.

What's my experience with pricing, setup cost, and licensing?

My advice is to make sure that you properly scope the project from both hardware and network requirements. NSX-T can be complicated if it is not designed correctly.

Which other solutions did I evaluate?

Some customers are evaluating Gardicore vs NSX.

Gardicore is a great tool for micro-segmentation only. It can fill in many gaps that NSX-T misses with its native micro-seg capabilities.

What other advice do I have?

An NSX-T solution requires a solid understanding of routing/switching, IP pools, local egress, and solution design to be successful. It takes a team of both VMware and Cisco folks to collaborate to get it done right the first time.

As a customer, make sure you are hiring the best resources.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about VMware NSX. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
554,382 professionals have used our research since 2012.
SB
Senior Infrastructure Engineer at a retailer with 10,001+ employees
Real User
Top 20
Feature rich, distributing routing useful, but expensive

Pros and Cons

  • "This is a good firewall and overall it is rich in features."
  • "There are sometimes mismatch in the control, the details and what you actually see on the transport note."

What is our primary use case?

Have used this solution to implement PAS (PCF) and have also used it for Native Datacenter networking as part of DC refresh.

How has it helped my organization?

Have worked on multiple organizations with VMware NSX. It heavily depends on the use case of the solution and how well you are able to use all the features of the product. When using for K8s container platforms or a networking backed for on premises cloud using a CMP(VRA, VIO) then VMware NSX is the best SDN solution but If an organization is not able to use NSX to its full potential (Switching, Routing, Load-balancing, Firewall, IDS, IPS etc.) then its not worth it.

What is most valuable?

Logical routing, switching are  overall good feature of this SDN solution especially when using CMP's and distributed firewall is very attractive features for micro-segmentation.

What needs improvement?

In rare situation there are  mismatch in the control plane data and dataplane data i.e. the details and what you actually see on the transport note. This is rare but time consuming to troubleshoot . Additionally, there could be better integration between VMware Cloud Federation (VCF) and NSX-T. Currently, there are some limitations, for example, VCF allows just one overlay transport zone. Also there is not upgrade path from VCF 3(NSX-T 2.5.x) to VCF 4 (NSX-T 3.x)

For how long have I used the solution?

I have been using the solution for approximately five years.

What do I think about the stability of the solution?

The stability is good and is getter better after each new release.

What do I think about the scalability of the solution?

The solution is scalable. In the 2.4 version, the controller got merged to create the cluster manager, it now is even better.

How are customer service and technical support?

The technical support was pretty good, but recently I have had quite a few bad experiences with the support. But that really depends on the account and geographic location and multiple other factors

Which solution did I use previously and why did I switch?

We have using Cisco ACI  and it is a strong competitor. When you are not using NSX NCP then everything that you need from SDN prospective can be done in Cisco ACI except for the distributed firewall at the vnic level.

How was the initial setup?

The initial installation feels at first a little complex because there are a lot of components, but when you get the understanding after a short time, it is fine.

What's my experience with pricing, setup cost, and licensing?

I was not involved in the purchase of the solution but I hear it is on the expensive side. That is why quite a few companies are moving towards open source because there are multiple solutions such as NginX, that can do the load balancing, and Calico and Flannel can do your logical switching routing.

Which other solutions did I evaluate?

If there is already VMware environment then it makes sense to use NSX-V, NSX-T as it can be integrated with other VMware automation products. But if approach it towards opensource then other SDN solutions like flannel, Nginx etc. can be evaluated depending on the use case.

What other advice do I have?

If you are wanting to implement this solution I would advise if your project supports it then definitely. You should have a solid use case, the solution is rich in feature sets and you should use all of them. Then only is it worth the money, if you are just buying it for your logical switching and routing, then it is not worth it.

I rate VMware NSX a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Roger Nurse
VMware NSX T/V Consulting Engineer /Solutions Architect at Plan IT Virtual, LLC
Real User
Top 5Leaderboard
It has allowed our customers to scale/extend their existing IP subnets and spin up new subnets on-demand for new app/web/DB tiers.

What is our primary use case?

Primary use case is to implement network virtualization for L2/L3 traffic in customers environment and at a minimum implement baseline micro segmentation. each customer has a different business requirement depending on how their existing network is setup --what physical L3 devices are in place and how NSX will need to be configured to function properly.  Most customer using NSX V that we have worked with are running UCS servers or HP

with vsphere 6.7 /7  mid level transport node counts respectively etc.

 

How has it helped my organization?

It has allowed our customers to scale/extend their existing IP subnets and spin up new subnets on-demand for new app/web/DB tiers. Increasing overall VM-to-VM security and policy deployments. It has helped increase operational efficiency from a network management perspective. Many firms have multiple racks of equipment at different data centers that leveraging NSX definitely helps (extending the 'same' IP subnets to different racks in the same data center). For customers who use SRM, there are also great benefits (i.e., not having to manually re-IP DR-side VMs during a failover test).

What is most valuable?

  • micro segmentation features
  • VDS
  • NSX Transport zone
  • vxlan encapsulation
  • edge services gateway 
  • distributed logical router
  • esxi Vtep

By utilizing NSX V solutions from VMware, customers have the tools needed to move their data regardless of the underlying physical network. They can do this in a way that enforces proper security policies and compliance regulations. Even with SDN solutions, customers must protect their business-critical data residing in their virtual infrastructure

NSX V has less security features than NSX T just so you are aware

What needs improvement?

  • NSX Manager console: limit on number of NSX Controllers an architecture can have
  • Support for ESXi, KVM, bare-metal servers, Kubernetes, OpenShift, AWS and Azure.
  • Integrate NSX Controllers into NSX Manager as a single virtual appliance so controllers no longer need to be deployed independently.
  • Directs to vCenter by registering Transport Nodes instead of registering NSX Manager inside of vCenter.
  • Use a more modern overlay technology for encapsulation that performs better and is more flexible for the future over older, more traditional VXLAN overlay technology.

For how long have I used the solution?

I have used it for 3+ years.

What do I think about the stability of the solution?

Stability factors stemmed from existing ESXi host setup/configuration/performance and compute capacity; did not identify any stability issues with VMware NSX solution itself.

What do I think about the scalability of the solution?

No scalability issues encountered.

How are customer service and technical support?

Customer Service:

Customer service is 10/10.

Technical Support:

Technical support is 10/10.

Which solution did I use previously and why did I switch?

No previous solution in place.

How was the initial setup?

Straightforward setup; best practices need to be adhered to.

What about the implementation team?

Implemented in-house in PoC/prod; showed customer PoC demo, then implemented at customer site with positive results.

What was our ROI?

As a VMware Partner, our ROI is the same as our customers perhaps. NSX helps us leverage our existing infrastructure that is used for training/consulting purposes.

Which other solutions did I evaluate?

No other options evaluated. VMware is the leader in network virtualization.

What other advice do I have?

Typically CCIE's are the ones tasked with implementing NSX due to their solid network background. Organizations for the most part do not have resources that know VMware as well as they know Cisco. The skills required to be well versed in deploying this technology is rare.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: VMware Professional Partner (consulting and training services)
WJ
Senior Cloud Consultant with 201-500 employees
Reseller
Top 20
Good security with improved scalability and allows for the creation of virtual access networks

Pros and Cons

  • "One of the big improvements between the NSX-V and NSX-T is that in NSX-T you are no longer dependent on V-Center anymore."
  • "Some configuration maximums are limiting to the user, especially when it comes to the deployment of very, very large environments."

What is our primary use case?

I work with two different companies with different large cloud environments. 

This product is a software-defined network, and that allows you to create virtual access networks and managing security to allow for different workloads.

What is most valuable?

The solution offers a very good software-defined network that allows you to create virtual access networks. It's very helpful at allowing you to manage security to allow for different workloads. 

One of the big improvements between the NSX-V and NSX-T is that in NSX-T you are no longer dependent on V-Center anymore. That was a huge improvement due to the fact that it allows you to take into account new cases, and have better scalability, among other improvements.

What needs improvement?

There is always room for improvement, in any solution. 

In some cases, this product is very technical. 

Some configuration maximums are limiting to the user, especially when it comes to the deployment of very, very large environments. There are limits to the number of firewall rules, security groups, et cetera. With the number of security groups, you can nest all these limits, however, somehow limiting the use cases may be restrictive for the free design of different use cases.

For how long have I used the solution?

I've been working with the solution for a while at this point. It's been at least a couple of years.

What do I think about the scalability of the solution?

The scalability capabilities have improved in NSX-T. It is much better than when the NSX-V version was out.

I work with two different clients, both of which are quite sizeable. They have thousands of machines and thousands of security groups.

Which solution did I use previously and why did I switch?

I didn't work with another solution per se, however, the previous triggered cloud tool that we had was by VMware. It was not really, at least at the very beginning, a tool for a software-defined network, however, there were some elements that allowed you to create customer networks practically on the fly. There were also some other network visualization techniques, which allowed you actually to encapsulate the traffic and to create networks on the fly. You had some security constructs, including tenents constructs, that you can find somehow in the VRA today. The tenant concept is also present in NSX.

What's my experience with pricing, setup cost, and licensing?

Our customers can use the solution for free, however, this comes with restrictions.

What other advice do I have?

We are consultants and integrators. We have a business relationship with VMware.

I am working with both NSX-V and NSX-T. The latest one is actually NSX-T.

On a scale from one to ten, I would rate it at an eight.

Disclosure: My company has a business relationship with this vendor other than being a customer: reseller
GG
Senior Solution Architect at a financial services firm with 10,001+ employees
Real User
Top 20
Scalable, problem-free and very stable

Pros and Cons

  • "Overall, I would say the solution has been quite stable."
  • "Our technical team is always looking for the solutions that they work with to offer more convenient integrations."

What is our primary use case?

We primarily use the solution in order to build a private cloud.

What is most valuable?

I'm not using it directly. Basically, for me, this is just another tool in the portfolio. I'm not the engineering staff that are next to the console and doing configurations.

Overall, I would say the solution has been quite stable.

The solution is likely scalable.

I haven't heard of any problems with the solution.

What needs improvement?

Any technical product has its own limitations in one place or another.

Our technical team is always looking for the solutions that they work with to offer more convenient integrations.

For how long have I used the solution?

I've been using the solution for around a year or so. 

What do I think about the stability of the solution?

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

There are some limitations in terms of scaling. It depends on how you would like to scale. Our engineers are using it and they don't see any problems with the scaling, however, it doesn't mean the same will work for any other organization.

Currently, we have more than 10,000 end-users. Our technical team isn't really that big. However, I can't say the exact number.

We do plan to continue to use the solution, however, we don't have plans for any big expansion.

How are customer service and technical support?

I do not have any personal experience with technical support. I can't speak to how helpful, knowledgeable, or responsive they are.

Which solution did I use previously and why did I switch?

I cannot say if there was a different solution used in our organization. It had been implemented before I arrived.

How was the initial setup?

I didn't handle the initial installation. I can't speak to how easy or difficult it was to implement, or how long it took to deploy. I wasn't a part of the process.

What's my experience with pricing, setup cost, and licensing?

I'm not involved in the licensing process at all. I have no knowledge of how long our licenses last or how much it costs the company.

What other advice do I have?

We are just a customer and end-user. We don't have a business relationship with VMware.

We use a few different VMware products, not just NSX.

We aren't necessarily using the latest version of the solution. We usually use the latest minus one or two versions.

In general, I would rate the solution at an eight out of ten. We've been mostly quite please with it.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
ITCS user
Senior Consultant at a consultancy with 10,001+ employees
Real User
Top 5Leaderboard
Easy to set up, with good features for automation and software-defined networking

Pros and Cons

  • "This is the most scalable product of its type."
  • "The training costs a minimum of $3,000, which is expensive and should be reduced."

What is our primary use case?

We use this product for micro-segmentation and network function virtualization.

What is most valuable?

This is the most scalable product of its type.

It is very good for automation and software-defined networking.

What needs improvement?

I would like to see improvements made to the certification process. As it is now, you have to do the training with VMware itself, and you have to spend a lot of money doing it, which is very discouraging. 

If you compare other certifications especially from the cloud providers, you can get trained from your choice of training providers and not very expensive or learn on your own at your pace, prepare for exams and pass and your certificate will be issued. In contrast, you have to register under VMware to get training done at minimum of $3000 before your certificate is issued to you. The training costs a minimum of $3,000, which is expensive and should be reduced. 

For how long have I used the solution?

I have been using this product for more than a year.

What do I think about the scalability of the solution?

Outside of the cloud infrastructure, it is the most scalable network product that I have worked with. It is used in a server farm that contains about 2,000 servers.

How are customer service and technical support?

We have not needed to contact technical support.

Which solution did I use previously and why did I switch?

We did not use another network function virtualization product prior to this one.

How was the initial setup?

The initial setup is very straightforward. Our deployment took three months, end to end.

What about the implementation team?

We had a consultant to assist us with the deployment.

We have two or three in-house staff who manage and maintain the solution.

What's my experience with pricing, setup cost, and licensing?

The licensing fees are expensive and we pay on a yearly basis. However, we were able to leverage some of the licenses that we had for an affiliated product, ESXi. There are no costs in addition to the standard licensing fees.

Which other solutions did I evaluate?

We chose VMware NSX-T because it was the most scalable.

What other advice do I have?

This is a good product and one that I recommend for anybody who does not want to change their existing infrastructure. The problem is that they have to compete with the likes of AWS and cloud providers.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AA
Consultant at a computer software company with 10,001+ employees
MSP
Stable, great for controlling virtual switches and makes it easy to establish VLANs

Pros and Cons

  • "Overall, for me, it's a good solution and has been working well."
  • "Occasionally the licensing is not very clear. They should make it easier to understand."

How has it helped my organization?

The full integration has been great. Its infrastructure and its ability to be part of the whole application are very useful for organizations. 

What is most valuable?

The solution is great for controlling virtual switches and it is easy to establish VLANs and micro-segmentations. All those things are very useful.

The stability is pretty good. 

Overall, for me, it's a good solution and has been working well. 

What needs improvement?

I cannot recall coming across any missing features. At this time, there is nothing I would need in a future release. 

Occasionally the licensing is not very clear. They should make it easier to understand. 

For how long have I used the solution?

I have experience using the solution for around 25 years, on IT, however, for the last 10 years I've been working deeply on this and over the decade I have been more focused on software. In the last 4 or 5 years, I have had more and more focus. 

What do I think about the stability of the solution?

The stability is good. Our customers don't seem to have any issues with bugs or glitches. It doesn't crash or freeze.

What do I think about the scalability of the solution?

I haven't really dealt with scaling the solution. I can't speak to how it is. 

How are customer service and support?

I've never been in contact with technical support in the past. I can't speak to how helpful or responsive they are. 

Which solution did I use previously and why did I switch?

I also have experience using Red Hat. However, sometimes I have had some problems with it. It can be a bit more difficult in terms of integration with other vendors. 

How was the initial setup?

I didn't actually handle the implementation. I'm working more on the design side, not on setup or configuration. Therefore, I can't speak to how easy or difficult the implementation process is for users. 

What's my experience with pricing, setup cost, and licensing?

The licensing is complex. Sometimes I have trouble understanding it.

What other advice do I have?

We are VMware integrators and partners. 

I'd advise new or potential users to be aware that you will have to integrate it with other solutions. You'll need to look at how it fits in with all of your infrastructure, including IT infrastructure, for example. 

I'd rate the solution at a nine out of ten. It's been very good overall. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate