My blog has been selected again as a finalist in the Most Inspirational category of the 2019 IT Blog Awards, hosted by Cisco.
The goal of the IT Blog Awards is to recognize the broader community of IT bloggers
I am particularly happy to be in the Most Inspirational category.
Imagining that my blog may inspire somebody to look deeper on some topics, or try something new or even actively join the Networking community with a new blog repays me for all the efforts and time I spend creating content.
This is part two of the Open Office series. Read part one for a better context.
The Myth of Spontaneous Collaboration Let’s start with this assumption:
Open Office is the wrong least bad solution for a real problem.
Open Office is usually implemented by managers with the best intentions. The goal is to improve the quality of work and break silos. But sometimes the actual result is a damage for productivity and increased stress.
Open offices can be harsh environments. You never know what dangers are hidden behind you until the interruption arrives.
Productivity plummets, concentration is gone, the thread of reasoning destroyed in a moment. All of this caused by a casual question, a polite salute, an unsolicited tentative of small talk:
Source
Google today returns over 165M results for How to survive the Open Office, this post is my useless personal and semi-serious contribution to the topic.
Writing code today often means interacting with API of many products. For me it means the possibility to integrate existing tools or create new functions.
Sometimes it is just a matter to create a small utility.
The Problem Meraki Dashboard does not include a page that shows the CDP/LLDP neighbors. Can we do better than Make a Wish?
The Solution I wrote a Python script that uses Meraki API to list LLDP and CDP information for a device.
Two factor authentication (2FA) is the way to go for authenticated access for anything than is more than a lab.
I use an Yubikey to protect my personal accounts and the password manager1 I use to maintain unique password for each service.
When it comes to use PKI on multiple machines a common problem is where to store and how to protect the access to the private key.
I read about people saving the key in a private Git, some use sync tools like Dropbox or GDrive.
During Cisco Live this year I had a chance to stop by IP Fabric booth and exchange a quick chat about their product and the problem they’re trying to solve.
After the event I had the opportunity to run a trial to better understand the product and the features if offers.
What struck me was that the product solves problems that over the years I have tried to mitigate through scripts or the use of other software that have shown many limits.
String manipulation is a skill that is useful almost on daily basis for most IT professionals.
Search, replace, count, filter, order text files from the command line make the process repeatable and fast, without too much clickety-click.
Awk, sed, sort, cut, uniq are powerful tools to master.
Today my focus is on sed that helped me during the migration to the new theme of my website
sed (stream editor) is a non-interactive command-line text editor.
Sometimes small problems are opportunities to learn something new or apply skills seldom used.
I often try to do things differently or new paths, sometimes just to avoid boredom, but also to improve myself. This is one of the pillars of essentialism and Kaizen that I try to apply to my work and life.
The challenge For reasons I need to check very quick the public IP addresses of some Meraki MXs connected to LTE routers or dynamic IP addresses.
On May 10th I had a chance to attend again ITNOG in Bologna.
Even if ITNOG seems to be an event with focus on ISP I find it very educative for anyone working in the enterprise market.
The boundaries between enterprise and ISP network are a common ground for negotiation about connections, routing, security, SLA. Sun Tzu advice it is a good strategy to know your enemy, I see no enemies on the other side of the CPE but the idea remains valid.
Network documentation and monitoring are topics that never lose interest to me.
Over the years I worked with many products, Nedi, Observium, Librenms,, NetBox, Icinga, NetShot, Smokeping to name a few.
Each product has its strengths and weaknesses that in some cases are nothing more than the aspects on which the manufacturer has decided to concentrate development more.
NetShot has compliance tests easy to write and verify, Smokeping is easy to setup and focused on monitor network and services latency.