Automating network troubleshooting with NetQ + Ansible
Network Automation is so hot right now! Joking aside, DevOps tools like Ansible, Puppet, Chef and Salt as well as proprietary tools like Apstra are becoming all the rage in computer networks everywhere. There are python courses, network automation classes and even automation focused events for the first time in the history of computer networks (or at least it feels like it).
For this blog post I want to focus on automating network troubleshooting, the forgotten stepchild of network automation tasks. I think most automation tools focus on provisioning (or first time configuring) because so many network engineers are new to network automation in general. While I think that is great (and I want to encourage everyone to automate!) I think there is so much more potential for network automation. I am introducing Sean’s third category of automation use-cases — OPS!

I want to combine Cumulus NetQ, a fabric validation system, with Ansible to:
- Figure out IF there is a problem (solved by NetQ)
- Figure out WHAT the problem is (solved by NetQ)
- FIX the problem (solved by Ansible)
- AUTOMATE the above 3 tasks (solved by Ansible)
Because I think looking at terminal windows is super boring (no Continue reading
VMware NSX network virtualization is the bridge between the Vodafone and IBM clouds.
Customers can group and manage transport links from a single entity.


IBM views commodity solutions as put together with "tape and bailing wire."
Versa only monitors its own network components.