Getting Started with Ansible- Programming and Playbooks - (by NetworkChuck and Jesse Keating)

* I am using an Ubuntu server, which means I could skip epel-release and simply install Ansible from these instructions.

Opening the configuration file in vi (as su, or you won't be able to overwrite), I'm pleasantly surprised it didn't take me more than 3 minutes to find #host_key_checking = False. The # means 'this is a comment', so let's take that away so it can work with the demo.

Let's configure;

This is openly available information over here.

Let's ping it; Yes, apparently my Ansible was using older Python for backwards compatibility.
But we did successfully ping the router!

First bit of automation = ✅

With a bit of manipulation, we can run some good old Cisco IOS commands like 'show ip int brief';

The command is sudo ansible router -m ios_command -a "commands='show ip int brief'"

I revisited this the next day and added the second router;

I got a really funky error pointing out a mistype on "Line 47, point 1" - I put a space between [routers] and the machines, and that cleared things up.

I'm not here to spoil the entire video for you, and there is much more. Go try it yourself!

Someone shared an Ansible course on LinkedIn that I looked at - let's make a playbook. An Ansible Playbook is the configuration deployment written in YAML.

Let's pretend that the Wi-Fi in Hogwarts was installed smoothly, and has been chugging away for awhile. The larger routers connected to the ISP need updating. Let's keep pretending that the ISP just doesn't want to do it, and so, it falls upon us.

You can see a (very simple) Playbook I created here.

Comments

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.

Building, Breaking, and Building A CRM with Retool

I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself. I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is: To have a GUI to add people to a NRM (Network Relationship Management). Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others). Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see. When you get set up, there's a plethora of resources you can use -- Incl

RUN TCP/IP | Morgan Lucas' Tech Portfolio

Search This Blog