Matilda Bailey is a Networking specialist who focuses on the latest technologies and trends in cellular, wireless, and next-gen solutions. Today, we will discuss network automation, the debate over commercial versus DIY solutions, and the current challenges that NetOps teams face. Our conversation will also cover the cultural and organizational factors that impact automation choices, and what improvements are needed to make automation tools more effective.
Can you explain what network automation is and why it’s gaining popularity in IT?
Network automation involves using software and tools to automate the planning, deployment, and management of network devices and services. It’s gaining popularity because of the increasing complexity of networks due to factors like IoT, remote work, and the rise of cloud services. By automating network tasks, organizations can improve operational efficiency, reduce human error, and manage their networks more effectively with the same amount of resources.
What are some of the key drivers behind the increasing complexity of networks?
The key drivers include the proliferation of IoT devices, the shift to remote work, the adoption of software as a service (SaaS), and the move towards software-defined networking (SDN). These factors have exponentially increased the number of devices and services that networks need to support, making manual network management impractical.
What are the main benefits of buying commercial network automation tools?
Commercial network automation tools are generally stable, secure, and come with support. They also meet security and compliance requirements, which is crucial for organizations that need to adhere to stringent regulatory frameworks like HIPAA or SOC2. These tools can also save a lot of time and resources because they come with customer support for troubleshooting and management.
What are the advantages of building your own DIY network automation tools?
DIY automation tools offer a high degree of customizability and can be tailored to specific network requirements, which might not be possible with commercial tools. They can also be more cost-effective because you avoid the high costs associated with commercial tools. However, they do require a significant investment of time and effort to build and maintain.
Why do most IT organizations use a mix of homegrown, open source, and commercial tools for network automation?
Most IT organizations use a mix because no single solution can meet all their needs. Homegrown tools offer customizability, open-source tools provide a middle ground in terms of cost and features, and commercial tools offer stability and support. Using a mix allows organizations to leverage the strengths of each type of tool.
What are the challenges in integrating different network automation tools?
The biggest challenges are integration issues due to the lack of standardization in enterprise networks and the technical debt from legacy components. Poor API support and inconsistent features in network automation products also contribute to these challenges. Additionally, limited budgets and staff knowledge can make integration even harder.
According to the 2024 EMA analyst report, why do only 18% of organizations consider their automation strategies successful?
Only 18% of organizations consider their automation strategies successful because of the aforementioned challenges like integration issues, lack of standardization, and technical debt. Additionally, limited budgets and staffing, as well as low prioritization by IT leadership, play significant roles in these low success rates.
What are some specific barriers that hinder successful network automation?
Specific barriers include integration issues, lack of standardization in enterprise networks, technical debt, poor API support, inconsistent features in automation products, limited budgets, and insufficient staff knowledge. Resistance to change within NetOps teams and a preference for manual processes also pose significant barriers.
How do commercial automation tools ensure security and compliance requirements are met?
Commercial automation tools are designed to meet basic security and compliance requirements out of the box. They are rigorously tested and updated to comply with various regulatory standards, making them a safer choice for organizations that must adhere to these standards. They also offer customer support for troubleshooting, which can be crucial for maintaining compliance.
What are the drawbacks of relying solely on commercial automation tools for network automation?
The main drawbacks are that commercial tools may not cover all the unique requirements of a specific network, and they can be expensive. They might also lock organizations into a specific vendor’s ecosystem, making it harder to switch tools or vendors in the future. Additionally, commercial tools may not be as customizable as DIY solutions.
How do open-source tools like Ansible provide a middle ground in the buy vs. build debate?
Open-source tools like Ansible offer a middle ground by being cost-effective and somewhat customizable while still providing some level of support and community backing. They allow organizations to save on costs while meeting security, compliance, and platform requirements to a certain extent.
Can you discuss some of the time commitments involved in supporting homegrown automation tools?
Supporting homegrown automation tools can be very time-consuming. According to a survey by EMA, over 50% of organizations spend between 6 to 20 hours per week debugging and supporting these tools. This time commitment can become a significant burden, especially for smaller teams with limited resources.
How do cultural preferences within NetOps teams impact the choice between commercial and DIY automation tools?
Cultural preferences play a significant role in this choice. Many NetOps teams have a traditional mindset and prefer manual processes because they’re familiar and proven. This resistance to change makes adopting new automation tools, whether commercial or DIY, a challenging task.
Why do many network engineers prefer manual processes over automation?
Many network engineers prefer manual processes because they are familiar and often feel they have more control over the network. There’s also a learning curve associated with automation tools, and not all engineers have the coding skills required to build or manage automated solutions.
What improvements do you think are needed in automation tools to make them more effective?
Automation tools need better integration capabilities and should be vendor-neutral to tackle the problem of legacy networks. They also need to have deep network mapping capabilities to reduce the need for DIY solutions. Low or no-code tools can help by making automation more accessible, thus easing budget, staffing, and skill issues.
How can low or no-code tools help overcome budget, staffing, and skill issues?
Low or no-code tools can democratize automation by making it accessible to personnel who may not have advanced coding skills. This can significantly reduce the time and cost associated with developing and maintaining automation scripts, making it easier for organizations to implement and benefit from automation.
Why is it important for NetOps teams to shift their focus from automating important tasks to automating repetitive ones?
Automating repetitive tasks can save significant amounts of time and reduce human error. For example, automating diagnostic tests can save thousands of troubleshooting hours. When scaled, these savings can be immense and contribute to overall operational efficiency, allowing teams to focus on more strategic and complex tasks.
Can you provide an example of how automating a routine task can lead to significant time savings?
One organization saved 16,000 troubleshooting hours in one year by automating routine diagnostic tests that previously took 15-20 minutes per ticket. With a major enterprise handling up to 50,000 tickets per month, the time savings quickly add up, demonstrating the value of automating even seemingly minor tasks.
What steps can organizations take to build a successful network automation program?
Organizations can start by establishing clear objectives for their automation projects and securing IT leadership support. They should also invest in training their staff to develop the required skills and choose a mix of tools that best meet their needs. Continuous assessment and iteration of their automation strategies will also help them maintain a successful program.
How can continuous network assessments help organizations maintain a reliable network infrastructure?
Continuous network assessments allow organizations to spot issues early before they escalate into major problems. Automating these assessments ensures they are done regularly, providing ongoing visibility into the network’s health and reducing the risk of outages or performance issues.
You have any advice for our readers?
My advice would be to embrace the mixed approach to network automation—leveraging commercial, open-source, and DIY tools where they make the most sense. Also, focus on fostering a culture that values automation and continuous improvement. By doing so, you can make significant strides in operational efficiency and network reliability.
