Service

Choose switch hardware across vendors, and buy it on your terms

We move data center fabrics from a proprietary switch OS to SONiC, the open network OS that runs on switches from many vendors. The hardware is checked against the features you use, the fabric is rebuilt on EVPN/VXLAN where it needs to scale, and configuration comes from one model rendered per platform. On one programme, SONiC replaced end-of-life switching with all features kept.

Measured impact

What changes for your organization

  • Today

    One vendor sets the price

    The switch OS only runs on its vendor’s hardware, so every refresh and expansion is bought from one catalogue at one price list.

    With SONiC

    Hardware bought on your terms

    SONiC runs on switches from many vendors, so each purchase is a choice between suppliers.

  • Today

    Features on the vendor’s roadmap

    A function the fabric needs waits for the vendor to build it, in a release the vendor schedules.

    With SONiC

    A network OS you can extend

    SONiC is open source and modular, so a missing function is built and deployed as its own service.

  • Today

    A refresh that means rework

    Replacing a switch with another model or another vendor’s means rewriting its configuration by hand.

    With SONiC

    A swap that follows the model

    Configuration comes from one model with a renderer per platform, so new hardware means a new renderer.

  • Today

    A fabric out of room

    VLAN-based segmentation caps a network at around 4,094 segments, and multi-tenant growth hits that ceiling.

    With SONiC

    Room to grow

    An EVPN/VXLAN overlay on SONiC raises the ceiling to millions of segments.

  • Today

    New racks on manual work

    Every new rack waits for engineers to stage and configure its switches.

    With SONiC

    Racks that come up on their own

    Zero-touch provisioning brings each switch up with the configuration for its role and place in the fabric.

What we deliver

  • Feature and hardware check

    Every feature the fabric uses today mapped to SONiC, and candidate switches checked for the SAI support those features need on each ASIC.

  • Target fabric design

    The spine-leaf fabric on SONiC, with BGP and FRRouting, and an EVPN/VXLAN overlay where segments or tenants need to scale.

    Read the case study →
  • Configuration from one model

    One configuration model for the fabric, with a renderer per hardware platform, driven by GitOps and a source of truth.

    Read the case study →
  • A digital twin of the fabric

    The new fabric emulated before any switch is replaced, so designs, routing policies and the cut-over are tested first.

  • Zero-touch bring-up

    New and replaced switches boot through SONiC ZTP and receive the configuration for their role and position in the topology.

  • Gaps closed in code

    Where SONiC lacks a function you rely on, we build it in its own services, such as orchagent and syncd, on the hardware’s SAI.

How it runs

The fabric moves in planned waves; the scope scales with its size and the features it uses.

  1. Discovery

    The fabric and the features it uses today, the target design on SONiC, the hardware shortlist and a migration plan.

  2. Proof of concept

    The shortlisted switches tested with SONiC on your features, and any extensions they need confirmed.

  3. Design and twin

    The target fabric and its configuration model built and emulated as a digital twin, with the cut-over rehearsed there.

  4. Migration

    Switches replaced in waves, rack by rack or pod by pod, each validated before the next.

  5. Automation

    Zero-touch bring-up and configuration from the model, so the next rack and the next vendor follow the same path.

  6. Handover

    Your team runs and extends the fabric, documented and owned in-house, with our support for as long as you want it.

Proof

One programme moved switching to SONiC; the other runs SONiC fabrics in production for a client that has used SONiC for years.

Why CodiLime

  • SONiC in production

    We moved end-of-life switching to SONiC on EVPN/VXLAN for a global application delivery company, and build the orchestration for a marketplace’s web-scale SONiC fabrics.

  • Hardware choice built in

    On the marketplace’s fabrics, one model feeds a renderer per hardware type, and the small differences between SONiC flavors are absorbed there.

  • Inside SONiC, down to SAI

    In our own R&D we added a new forwarding function to SONiC by changing orchagent and syncd, and ran it on a Mellanox Spectrum switch.

FAQ

Good to know

  • Will SONiC support the features we use today?

    SONiC ships a strong set of network functions out of the box. The discovery maps each one you use, and where SONiC lacks one, we build it as part of the project.

  • Which switches can we buy?

    SONiC runs on hardware from many vendors, but feature support depends on each ASIC’s SAI implementation. We check that per platform before you buy.

  • Can the fabric stay in service during the move?

    That is how the work is planned. Switches are replaced in waves, the cut-over is rehearsed on a digital twin first, and each wave is validated before the next.

  • Do we have to rebuild the fabric on EVPN/VXLAN?

    Only where segments or tenants need to scale. A fabric can move to SONiC with its design as it is, and the overlay can follow in a later phase.

  • Who runs the fabric afterwards?

    Your team, with the configuration model and automation documented and owned in-house. We stay on for support and extensions for as long as you want us to.

Start with a SONiC assessment

Tell us about your fabric and the switch OS it runs on. We map the features you use to SONiC, check the hardware you could buy, and hand you a target design and a migration plan in waves.