Day 0/1/2 Operations: Open Source vs Enterprise
The distribution choice reshapes the entire operational lifecycle. This lesson walks Day 0 (design/bootstrap), Day 1 (deploy/provision/configure), and Day 2 (monitor, troubleshoot, back up, upgrade, replace, respond to security, manage capacity), comparing what upstream asks of your team versus what an enterprise distribution provides.
Prerequisites: Lessons 5.1–5.4 · Modules 1–4 operational content
Learning objectives
- →Map the Day 0/1/2 lifecycle onto both upstream and enterprise operating models.
- →Identify, at each phase, what the vendor supplies versus what your team must own on upstream.
- →Connect the operational differences back to the staffing and TCO rows from Lesson 5.4.
- →Recognize that the underlying SONiC operations (Modules 1–4) are the same; the *support and tooling around them* differ.
The distribution decision is really a decision about who does the operational work at each lifecycle phase. Seeing it phase-by-phase makes the staffing implications concrete.
Most cost and risk in a NOS lifecycle are in Day 2, not Day 0. Comparing only the initial deployment hides the real difference.
What your CCNP already gives you
- • You already run a Day 0/1/2 lifecycle for OS10 — commissioning, provisioning, monitoring, upgrades, RMA.
- • You have security-response and capacity-management processes you can adapt.
What is new in SONiC
- • On upstream, several Day 2 activities (image builds, CVE backports, upgrade validation) may become in-house engineering rather than vendor-supplied.
- • Monitoring and troubleshooting use the SONiC surface (containers, DBs, SAI) regardless of distribution.
- • Backup/restore centers on config_db.json and SONiC's config model rather than an OS10 running-config.
| In the analogy | In SONiC |
|---|---|
| Speccing and commissioning the truck | Day 0 design/bootstrap |
| Loading and dispatching it the first time | Day 1 deploy/provision |
| Years of fuel stops, repairs, and roadside breakdowns | Day 2 run/maintain |
| You drive, wrench, and answer your own breakdown calls | Upstream (owner-operator) |
| A fleet service handles maintenance and roadside support | Enterprise (managed fleet) |
Where the analogy stops working
A managed fleet does not drive the truck for you — enterprise support does not run your change control, monitor your fabric, or design your topology. You still operate the network daily. The analogy also flattens the fact that some organizations *are* the fleet service — a hyperscale engineering org running upstream at scale is deliberately internalizing that role because it has the crew for it (Lesson 5.6).
Same network, different ownership
Nothing in this lesson changes how SONiC forwards packets or where its state lives — Modules 1–4 still apply on every distribution. What changes across the lifecycle is who supplies the tooling and who is accountable when a phase goes wrong.
Day 0 — Design and bootstrap
| Aspect | Upstream (you own it) | Enterprise (vendor-assisted) |
|---|---|---|
| Image | Build or select and validate an image for your platform/HWSKU yourself. | Vendor-qualified, signed image for supported models. |
| Hardware fit | You confirm platform support in the branch you run. | Compatibility matrix tells you supported models up front. |
| Design guidance | Community docs and your own testing. | Vendor reference designs and documentation. |
Day 1 — Deploy, provision, configure
| Aspect | Upstream (you own it) | Enterprise (vendor-assisted) |
|---|---|---|
| Provisioning | You wire up ZTP/automation and validate it yourself. | Vendor-supported provisioning and validated automation integrations. |
| Configuration | Same SONiC config model; you own templates and review. | Same config model, plus vendor tooling and documented patterns. |
| Optics/cabling | You field-test optics compatibility. | Validated optics list keeps you inside the support envelope. |
Day 2 — Run, maintain, respond (the long tail)
| Aspect | Upstream (you own it) | Enterprise (vendor-assisted) |
|---|---|---|
| Monitoring | You assemble telemetry/monitoring from SONiC's surface. | Same surface, plus supported telemetry integrations. |
| Troubleshooting | Community + your team; no TAC backstop. | TAC escalation with an SLA behind it. |
| Backup | You own config_db.json backup/restore and versioning. | Same artifacts, with vendor-documented procedures. |
| Upgrade | You engineer and validate upgrade paths. | Supported, documented upgrade tooling and paths. |
| Rollback | You design and test rollback yourself. | Supported rollback procedure. |
| Replacement / RMA | Your spares and re-imaging process. | Vendor RMA plus qualified re-image workflow. |
| Security response | You track and backport CVEs across components. | Vendor security advisories and fixes for the distribution. |
| Capacity management | Your own scale testing and headroom analysis. | Vendor-tested scale limits and guidance. |
At every phase the SONiC operations are the same; the difference is who supplies the tooling and who is accountable. On upstream that is your team, funded from the staffing and TCO rows of Lesson 5.4. On an enterprise distribution, the vendor supplies and stands behind much of it — for a price.
Common misconceptions
Myth: The deployment is the hard part, so compare Day 0/1.
Reality: Day 2 dominates lifecycle cost and risk. Comparing only initial deployment hides the real difference between the models.
Myth: Enterprise support runs my operations.
Reality: It supplies tooling and accountability, but you still monitor, change-manage, and operate the fabric daily.
- In a Day 2 incident, the distribution determines your escalation path: community/self on upstream versus TAC with an SLA on enterprise. Know which you have before the incident.
- Backup/restore and upgrade/rollback maturity are what determine your recovery speed — verify these per distribution, not per NOS in the abstract.
Key takeaways
- ✓The distribution reshapes ownership at every lifecycle phase, not the SONiC operations themselves.
- ✓Day 2 is the long tail where cost, risk, and the model differences concentrate.
- ✓Upstream moves image builds, CVE backports, upgrade validation, and support in-house; enterprise supplies and backs them.
- ✓Tie each phase's ownership back to the staffing/TCO rows so the operational reality shows up in the numbers.
Tested against: Lifecycle model is version-independent; tooling specifics vary by distribution — verify · Compares upstream against enterprise distributions generally · N/A — operational lifecycle · last reviewed 2026-07. Exact commands and behavior can vary by SONiC release, image, hardware platform, and enterprise distribution.
Knowledge check
You inject the same fault (a shut interface) into an upstream and an enterprise SONiC switch. What is the most accurate description of the troubleshooting experience?
Related lessons