Skip to content

SYSTEM Cited by 2 sources

OSPA (Open Switch Platform Architecture)

OSPA (Open Switch Platform Architecture) is a new OCP initiative — co-led by Meta, Microsoft, and Alibaba — that standardizes the switch platform layer: a unified reference design for the hardware and software interfaces beneath the network data plane. Introduced at OCP Summit 2026, with specification v1.0 submitted to OCP.

The gap OSPA fills

SAI made the switch data plane software portable across silicon — one NOS can program any SAI-compliant ASIC. But the layer beneath it — the switch platform layer — stayed proprietary and fragmented. Every new hardware platform required months of duplicated, custom engineering to bring up, and the lack of a standard platform design multiplied long-term maintenance and troubleshooting cost. In an era of compressed AI hardware cycles, that onboarding tax became untenable.

This is a classic data-plane / platform-layer split: SAI abstracts the data plane; OSPA abstracts the platform layer so the same bring-up logic works across vendors' boxes.

What OSPA standardizes

Hardware and software interfaces for:

  • Power management and power sequencing.
  • Sensor and environment control, including thermal and fan management.
  • Hardware inventory management and device enumeration.
  • Out-of-band hardware interfaces (management Ethernet, serial console, USB, LED indicators).
  • Firmware maintenance and updates.
  • Platform troubleshooting and diagnostics.

Why it matters

  • SAI's missing complement. OSPA is to the switch platform layer what SAI is to the data plane: the abstraction that turns per-box bring-up into a write-once interface. Together they make a switch platform genuinely portable.
  • Pairs with FBOSS self-onboarding. OSPA plus the extended, self-service FBOSS vendor-onboarding model is the full "vendors bring up their own switches without the hyperscaler in the loop" story.
  • Another Meta × Microsoft (× Alibaba) OCP collaboration in the lineage that began with SAI (2018) and runs through OAM and ESUN.

Caveats

v1.0 is submitted to OCP, not a ratified/finalized standard; adoption breadth and the concrete interface definitions are early.

Seen in (wiki)

Last updated · 854 distilled / 2,448 read