Your Path to Full Stack Networker Starts Here

Back to Posts
Linux Commands for Networking Configuration and Troubleshooting for Network Engineers

Share this post

Your Path to Full Stack Networker Starts Here

full stack networker engineer manifesto


Before, we get into why, what and how FullStack networker, let me a do a quick introduction as to who we are and what we stand for.

We’re a bunch of industry veterans out of silicon valley (California) with corporate backgrounds from Cisco, Huawei, Apple (and a few more). Most of us started our career when networking was about knowing Cisco IOS CLI and protocol soup from IETF (ever heard about them?). Now, since we are an ambitious bunch, we all did our CCIEs and wrote for Cisco Press too! This was a lot of fun, until it wasn’t, and that brings me to why we created Full Stack Networker. Disruptive technologies such as virtualization, cloud computing (or AWS!), SDN, OpenStack, NFV, white boxes (from ODMs or OEMs), and DevOps tooling ecosystem over the past seven years or so, have really transformed what it takes to be a Network Engineer (don’t believe me? check out google careers here). We started Full Stack Networker to help out our fellow citizens by bringing them all they need to know and learn to transform their careers and avoid facing skill set irrelevance. “Full Stack” refers to knowing everything it takes to stay relevant and thrive in the new era as a network engineer.

Now, I have already mentioned the key technologies that are disrupting networking, so let’s get into how we can get this re-skilling effort started. If you look at the disruption stack, you can easily identify that, the very foundation of everything is open source software ecosystem and LINUX. Linux is the perfect place to get stared, if you don’t know enough of it already.

Here are my four reasons, why Network Engineers need to learn Linux on their path to becoming Full Stack Network Engineer. Keeping this in mind, we’ve made our Linux Fundamentals and Shell Scripting course available.

  1. Linux or some form of Unix is the foundation OS behind all of the network operating systems such as Cisco IOS, Juniper Junos OS. Linux understanding can be helpful in learning Network OS system internals where access to native Linux shell is possible
  2. Open source network OS entirely based on Linux, such as one from Cumulus Networks, are also shaking up the otherwise black box networking from Cisco and Juniper
  3. Top open source projects, such as Docker, are based off Linux networking internals. Docker container network isolation leverages Linux namespaces along with basic Linux interfaces and L2 internals
  4. Ultimately network engineering is headed to full stack, which primarily includes fusion of skill set across network and server admin boundaries leveraging DevOps ecosystem and cloud/web technologies

Once you believe you got Linux down, your next stop is network automation. Without a doubt, I can tell you that network automation is the lowest hanging fruit so to speak, is here to stay and you need to be part of this transition. Fusion of network and server tooling ecosystem is the inevitable that awaits us. This would require us to deeply understand Python and Ansible programming fundamentals and corresponding libraries from both vendors such as Cisco, Juniper, Arista as well as multi-vendor libraries such as netmiko and napalm etc.

Please share your take in the comments below. We’d like to know your stories.

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Back to Posts
sample guides, quizzes and discount
We hate spam as much as you do.