ClickCease

Build and buy? Close, but no cigar. Instead, buy then build.

matthias-jordan-TnDaYFLMoSY-unsplash

Deanna Darah of TechTarget wrote an interesting article: “Reasons to Build and Buy Network Automation Tools”. I agree with her that most organizations will end up with both – once they reach a mature state of network automation. But at BackBox, we recommend flipping the approach so that you buy and then build.

A good way to frame this is by thinking about where your company is on its journey to network automation. If you’re at the more mature end of the spectrum and have the capabilities to do deep integrations with your IT service management stack, joining off-the-shelf products with custom workflows and leveraging open source tools, that’s one thing. But most organizations aren’t there yet. In fact, almost half (48%) of companies say they haven’t implemented or invested deeply in network automation, despite nearly all (98%) agreeing that it would allow their teams to do more impactful work.

First, Buy the Foundation

To get started, we recommend looking at a product like BackBox, a flexible, multi-vendor network automation platform that allows you to accomplish 80% or more of your network automation needs out-of-the-box, including:

  • Reliable and trustworthy backups and instant restore
  • Compliance audits and remediation
  • Onboarding and device discovery
  • OS updates and vulnerability management

When you can quickly cover these four basics that usually have to be done during maintenance windows and off-hours, teams get back their nights and weekends and eliminate work that is mundane. Additionally, instant restore unlocks other automation use cases because if you can reliably roll back, then when you do more enhanced automation and if you encounter a problem, you can recover quickly.

Buying first also frees up time so you can focus on the things you are interested in and want to learn more about. For example, solving the automation gaps you still want to address.

Then, Build

To extend automation – whether that’s another 20% or 5% of tasks – you have multiple options.

  • Contact BackBox’s Network Automation-as-a-Service team. We can create automations for you, often as part of your service contract. For more extensive needs we may refer you to one of our certified partners.
  • Consider specialty services shops. These providers have the expertise to stitch together multiple automation tools for complex multi-step automations.
  • Leverage open source tools. If you have the expertise, solutions like Python, PowerShell, and Ansible provide a solid way to weave in custom built network automation with off-the-shelf network automation solutions.

Here are a couple of typical use cases we help customers with that require connecting custom code with off-the-shelf products:

Automate post-change validation. For example, you send a change request to ServiceNow, which flows to BackBox and BackBox pushes the change out to the network. Now you want to kick-off a process to validate the network is working the way you think it should be working after the change. If so, close the ticket and update ServiceNow. If not, roll back the configuration and send an error report to ServiceNow for investigation. This may require stitching together three products: BackBox, ServiceNow, and an IP Fabric.

Update network device status in a configuration management database (CMDB). Say you want to put a new customer on a specific port of a switch or issue an IP address or assign a VLAN. Before you make a change, you want to validate availability through an API. BackBox can act as a network source of truth (NSOT), validating network devices and their status which satisfies the first part of the workflow. The second half is porting that information into a CMDB. As you build out a more mature network automation strategy you can extend that automation even further and port asset data stored in different systems into the CMDB.

Don’t Think DIY

A final word of caution. Sometimes the term “build” is used interchangeably with “DIY”, but this is a misnomer. DIY implies a kit that comes with instructions, tools, and parts, and it’s intended that you do it yourself. Like a desk from IKEA, there are no special skills required.

Building network automation capabilities is not like this. There are no instructions. It requires whittling and shaping to your exact specifications so that it fits your environment precisely. And it requires people with knowledge in network engineering, network security, and custom development. Finding someone that knows one of those things can be a challenge, two is really difficult, and all three is extremely rare. Most work for consulting companies or large network automation vendors and are focused on generating service revenue. This is not our customers’ core business.

Focus on Your Core Business and Rapid ROI

The point Deanna made is there is a reason to build and buy. I agree that it’s not separate or one or the other. Most organizations should do both. But the order should be to buy, implement, and extend through building. That way you gain rapid ROI with limited investment, without sacrificing customization that can add extensions at later stages of automation projects.

See for yourself how consistent and reliable your device backups and upgrades can be