What is our primary use case?
We have a controller-based deployment template for switches. All that you need to do is simply create templates for switches that would have a similar configuration and roll it out.
It's like configuring one switch. The amount of energy and time that you spend to configure one switch can allow you to configure tens of hundreds of switches. The single template can be pushed out across the entire campus.
What is most valuable?
The template functionality saves a lot of time and man-hours, which results in cost and time savings.
The good part is the CLI is similar to an industry-standard CLI or Cisco, which usually is considered as the industry standard due to the size of the deployment and the tools they have.
The feature sets are pretty cool. They've got almost everything that the competition offers. The good part is they help you get rid of the switch-tracking deployment models.
They use an approach that ensures that the number of switches that you require is on the lower side. You could have your core communicating directly with the access and that results in cost-saving overall when you look at it from a project cost perspective.
The solution is stable.
The scalability is very good.
Technical support is great.
What needs improvement?
It would be ideal if the solution was less expensive.
For how long have I used the solution?
I've been using the solution for three to four years at this point. It's been a while.
What do I think about the stability of the solution?
The product is stable. There aren't any bugs or glitches. It doesn't crash or freeze. It's reliable.
What do I think about the scalability of the solution?
The solution scales very well. There aren't any issues with expanding it. It's massively scalable.
We have about six clients that use the solution at this time.
How are customer service and support?
Technical support is lightning-fast. They are helpful and responsive. We are satisfied with the level of support on offer.
How was the initial setup?
The product is very easy to deploy. If you look at the competition, if you take, say, 20 minutes to configure one switch, and you have to deploy 200 switches, just multiply 20 into 200. When it comes to Arista it's just 20 minutes for all 100 switches. It's very simple and offers a lot of time savings.
In terms of deployment and maintenance, for probably 200 switches, a couple of employees are good enough to manage the show. You don't need a big team.
What's my experience with pricing, setup cost, and licensing?
The solution does have some cost-cutting capabilities, however, we would prefer it if it was less expensive.
The licensing cost is pretty heavy. That is something that they need to definitely work upon. Customers tend to move away from Arista due to the initial procurement costs or the recurring price, both of which are on the higher side. People are willing to pay at initial procurement, however, when it comes to the recurring price, clients expect to pay a lower price point.
What other advice do I have?
There are options for cloud management as well, however, in most places where I have seen it, the deployment model has been on-premises.
I'd rate the solution at a nine out of ten.
I would absolutely recommend the solution. However, someone with deep pockets should look at Arista. Otherwise, there are many alternatives that are less expensive if a company is short on budget.
Which deployment model are you using for this solution?
On-premises