The following command line will use the Text to Speech converter in *nix to say the word "pingtastic" every time a successful icmp response message is received using the ping command.
The post Tech Notes: Audio Ping Response From The Terminal / CLI appeared first on EtherealMind.
This is a continuation from Part 1 Remote LFA At this point we already know that simple LFA doesn’t always provide full coverage and its very topology dependent. Reason is simple i.e.in many cases backup next hop best path goes through the router calculating the backup next hop. This problem can be solved if we […]
The post IP FRR and Micro-loops Part 2 appeared first on Packet Pushers Podcast and was written by Diptanshu Singh.
Introduction In this post we will take a look at IP FRR and Micro-loops. If the reader already doesn’t have some kind of basic familiarity with IP FRR and Micro-loops, then I would highly recommend the reader go through below post series by Russ as he introduces various concepts in a very clear way. This post […]
The post IP FRR and Micro-loops Part 1 appeared first on Packet Pushers Podcast and was written by Diptanshu Singh.
If you watched the Network Field Day videos, you might have noticed an interesting (somewhat one-sided) argument I had with Sunay Tripathi, CTO and co-founder of Pluribus Networks (start watching at around 32:00 to get the context). Let’s try to get the record straight.
Read more ...Original content from Roger's CCIE Blog Tracking the journey towards getting the ultimate Cisco Certification. The Routing & Switching Lab Exam
The spanning tree portfast command is a very simple feature but often mis-understood. In this short post I will explore how this feature behaves, how it works and how to configure it on a cisco switch. Portfast is a Cisco Propietary feature that was originally developed to overcome an issue when a PC was trying... [Read More]
Post taken from CCIE Blog
Original post Spanning Tree Portfast – The Definitive Guide
If you have ever worked with Ansible, it’s almost a guarantee that you have used their online docs to figure out what parameters a given module supports, how they should be used, or what their defaults are. Over the past few weeks, I’ve been working on a few custom modules and was trying to find a way to generate web docs for them, and have them locally accessible or easily posted to GitHub.
Ansible offers a way to “make webdocs,” but it generates the complete module inventory and truth be told, I didn’t get this work for my custom modules, so I figured I would explore a “simplified” way — a way that should be able to generate docs as needed for one or more modules on an as needed basis.
The outcome was the creation of an Ansible module and Jinja2 template that automatically generates a markdown file (that can then be viewed or posted anywhere).
The modules you’ve built or are local to your machine (even Ansible core modules) that you want to generate a web doc for must be documented according to Ansible standards. That’s the only major requirement.
From there, Continue reading