NAN114: Demystifying Automation Tools, Processes, and Culture Gates

In the rapidly evolving world of network engineering, the shift from manual Command Line Interface (CLI) operations to scalable NetDevOps and automation is becoming increasingly important. To understand this transition, Eric recently sat down with David Henderson, Principal Architect for NetDevOps at Presidio, to explore the practical journey for network engineers looking to embrace automation.

David Henderson began by emphasizing the importance of traditional networking knowledge and certifications as a strong foundation. "Network engineers have always relied on a deep understanding of protocols, network design, and troubleshooting," he explained. "These foundational skills are still critical, but now they must be augmented with automation and DevOps practices to keep pace with the demands of modern networks."

Henderson highlighted that the transition to automation doesn't require discarding years of expertise but rather building on it. "Automation tools are designed to complement, not replace, the skills that network engineers have honed over time," he noted. "The goal is to enable engineers to work more efficiently, reduce errors, and scale their operations to meet the growing complexity of today's networks."

When discussing the essential tools for starting an automation journey, Henderson pointed to Ansible and Puppet as popular choices. These tools allow network engineers to automate repetitive tasks, such as configuration management and software deployment, across multiple devices. He also mentioned Terraform for infrastructure provisioning and Ansible Tower for orchestrating complex workflows.

"The key to successful automation is not just about choosing the right tools but also adopting the right mindset," Henderson stressed. He suggested that network engineers should focus on developing habits such as version control, modular scripting, and continuous testing. "By using version control systems like Git, engineers can track changes and collaborate more effectively," he explained. "Modular scripting ensures that automation tasks are reusable and maintainable, while continuous testing helps catch issues early on."

Henderson also touched on the importance of cultural shifts within organizations. "Automation isn't just a technical change; it requires a cultural transformation," he said. "Teams must embrace collaboration, experimentation, and a growth mindset to fully leverage automation." He encouraged network engineers to participate in communities like NetDevOps and engage in continuous learning to stay updated with the latest trends and best practices.

In conclusion, the journey from manual CLI operations to scalable NetDevOps and automation is both challenging and rewarding. By building on traditional networking knowledge, adopting the right tools and habits, and fostering a supportive culture, network engineers can unlock new levels of efficiency and innovation in their work. As Henderson aptly summarized, "Automation is an opportunity to elevate the practice of network engineering, and it's up to us to seize it."

The full interview with David Henderson, Principal Architect for NetDevOps at Presidio, can be found [here](https://www.example.com/read-more).