Cisco Catalyst SD-WAN Review
Rating: 5 out of 10
IncentivizedUse Cases and Deployment Scope
I guess for the intent of it was just to centralize the management as the network scales. Like we used to just send out templates for things and now it's just an easier way to standardize everything across the board, whether they're local or remote.
Pros
- I think it does pretty well of tying in multiple transports, allowing you to build a template and baseline for multiple, I guess lack of better term sites, so simplified deployments, stuff like that.
Cons
- We're still trying to figure out how to make it work. Some issues that we were running into is just like the user interface. A good example is your configuration templates and deployment groups. Making a group for a specific thing. I'm not trying to get too much into specifics, but you would have a group for remote sites say that one remote site has some sort of requirement that a site, another site may not have a requirement, but if I make a CLI configuration change in that template, it applies to all the templates. So maybe something that didn't apply to that certain site. I don't need it deployed across all sites. So I think a really cool thing would be, if you have multiple devices in one group, maybe it would be good to, if I were able to select which sites would receive the change versus hey, I'm going to make a site that applies, make a change that applies to one site. I don't want to deploy to all sites or have that become part of the template. It was just the one case scenario.
Likelihood to Recommend
We've used it for less than a year and I think we're still doing testing, so I don't know if I would go and say a 10 for recommendation yet. I just haven't seen it in action for a good period amount of time.
Vetted Review
1 year of experience