SONiC Network Operating System · Independent skills preparation

Open networking and the SONiC architecture

Configure, verify and troubleshoot open networking and the SONiC architecture on a SONiC switch, from the click CLI down to CONFIG_DB and the containers.

20 min read4 chapters2 labs8 quiz3 scenarios5 interview Q&A

This first module is free: read the lesson and take the quiz. Labs need an account: sign up free to run up to 3 hands-on labs.

Log inStart free trial
This reading material cannot be printed. Read it on config.nwkings.com.
01

What you will learn and why SONiC matters

For thirty years a switch was one closed box: the hardware, the operating system and the support contract all came from one vendor. You bought a Cisco switch and ran IOS on it, or an Arista switch and ran EOS. Open networking breaks that box into parts. The hardware is a "white-box" or "brite-box" switch with a merchant silicon ASIC (Broadcom, NVIDIA, Marvell and others), and the network operating system (NOS) is software you choose separately.

SONiC (Software for Open Networking in the Cloud) is the most widely deployed open-source NOS. Microsoft built it for the Azure data centers and released it as open source in 2016; since 2022 it is governed by the SONiC Foundation under the Linux Foundation. Large cloud operators, AI/GPU clusters and an increasing number of enterprises run it, and switch vendors such as Dell, Edgecore, Celestica, NVIDIA and Arista ship SONiC images or support it on their hardware.

Why it is a career skill

  • AI back-end networks and hyperscale fabrics are built from leaf-spine switches running BGP. SONiC is a common choice there.
  • SONiC engineers need networking and Linux skills: the same person reads show ip bgp summary, checks a Docker container and queries a Redis database. Few candidates have both.
  • Community releases are named by year and month (for example 202405, 202411) and come out about twice a year.

What this track covers

You will configure SONiC the way operators do: the click CLI (show ... and sudo config ...), the CONFIG_DB and /etc/sonic/config_db.json, VLANs, PortChannels, routed /31 fabric links, BGP in FRR, and the internals: containers, the Redis databases and the path of a change down to the ASIC. Every module ends with troubleshooting tickets.

About the simulator. The labs run on an educational model of community SONiC behaviour. Commands and outputs follow real SONiC closely, but this is not a SONiC image: there is no real ASIC, SAI or P4, and VXLAN EVPN, MC-LAG and ACL tables are taught in later modules of the track. Become a CLI King with Network Kings.

Upgrade to keep reading

The free plan lets you read chapter 1 of this module. Upgrade to open the remaining chapters.

  1. Disaggregation: ASIC, SAI, ONIE and the NOS
  2. Inside SONiC: containers and Redis databases
  3. The life of a change: CONFIG_DB to the ASIC

Join the community