Networklore is my home online, the main focus of the site is network automation.
Networklore started it's life as a blog. Most of the content here is in the form of blog articles.
Some of the content here is in a longer form than you would usually see in blog posts. I'm currently working on setting up a specific section for tutorials.
I like sharing what I do and aim to continue releasing open source tools which can help other people in the networking industry. There's a small list below of example projects and a longer one on the contact page.
If you like Networklore make sure you subscribe and I'll let you know as soon as I publish anything new.
Each email you receive will have an unsubscribe link included, so as soon as you don't want any more mails you're just an easy click away.
Here you can find a few of the open source projects I have created.
A toolkit for aimed to help network engineers written with everyday tasks
A collection of network plugins for Nagios and compatible products.
Proof of concept for managing Cisco IOS devices with Ansible using SNMP.
Ansible modules to query network devices with SNMP from Ansible.
Here's the latest of my writings from the blog
A lot of people who aren’t familiar with Napalm tend to laugh nervously when you suggest they use it in their network. The name Napalm is partly based on getting that perfect acronym and partly a desire to incinerate the old way of doing things and move to network automation. This article is about explaining what Napalm is and what lies behind the acronym.
A lot of new networking modules were released as part of Ansible 2.1. The Cisco IOS, IOS XR, NXOS, Junos and Arista EOS platforms got three common modules, the platform_config, platform_command and platform_template. The command and template modules more or less explains themselves. The config modules have some more tricks to them and I’ve gotten a few questions about how they work. In this article I’m going to focus on the ios_config module and show how you can use it to configure Cisco IOS devices. Future version of Ansible will add more parameters, this article is for Ansible 2.1.
It can get quite exciting when you start to think about network automation and what it can do for you and your network. Once you’ve automated everything you can instead focus on deep work to evolve your business. However this daydream can soon fade away as you start to think about the things you can’t automate, or at least don’t know how to do. Ivan Pepelnjak wrote a piece about automating the exceptions. The post is based on a discussion he had with Rok Papež and his ideas about handling exceptions in an automated way. While the strategy presented is great I think it overlooks some parts when it comes to exceptions that can arise, also the post doesn’t highlight how limitation of the configuration management tools were solved.