Resources & Next Steps
Where to go deeper, and how to keep the skills sharp after the course.
Primary references
SONiC project (SONiC-net on GitHub)
Upstream source, wiki, architecture docs, and build instructions.
SAI (OCP) on GitHub
The Switch Abstraction Interface specification, headers, and metadata.
FRRouting
The routing stack SONiC uses (zebra, bgpd) — docs and configuration reference.
Open Compute Project — Networking
Disaggregated networking and merchant-silicon context.
For enterprise SONiC (for example Dell Enterprise SONiC), obtain release notes, hardware compatibility matrices, and upgrade guides from the current official vendor documentation portal and support channel. Keep version-specific details in your own notes — they change between releases.
Next steps
- Keep your virtual lab. Re-run the failure-injection labs from memory until the layered method is automatic.
- Build a SONiC image from source once — it demystifies the platform/HWSKU model.
- Validate one route and one MAC on real hardware and compare against the virtual lab; document every difference.
- Draft a distribution evaluation and an upgrade plan for a switch you actually operate.
- Contribute back: file an issue or a doc fix upstream — it is the fastest way to learn the project’s edges.
On every future incident, ask the two questions this course was built around: how far did intent travel? and does healthy control-plane state actually mean correct forwarding here?