HOME/SOLUTIONS/Open Networking

OPEN NETWORKING FABRIC

The incumbent's renewal quote arrived with a support cliff attached. You run a data centre; you know what a leaf-spine should cost, and lock-in is the only reason it doesn't. You need an open fabric with an operator-grade NOS and someone local who stands behind it.

WHAT YOU WILL HAVE AT THE END

  • SONiC leaf-spine fabric on open hardware you own outright
  • VXLAN/EVPN multi-tenancy designed and documented
  • Zero-touch provisioning — replacement switches configure themselves
  • Automation-ready: NetBox/Ansible workflows as deliverables
  • Per-SKU economics visible — no bundled lock-in
  • A migration path that runs alongside the incumbent estate
SPINE 1AS7726-32X · SONiCSPINE 2AS7726-32X · SONiCLEAF 1AS7326-56X100GTENANT T1VXLAN/EVPNLEAF 2AS7326-56XTENANT T2VXLAN/EVPNLEAF 3AS7326-56XTENANT T3VXLAN/EVPNLEAF 4AS7326-56XTENANT T4VXLAN/EVPNNetBox → Ansible → ZTPSWITCH REPLACES ITSELFRUNS ALONGSIDE INCUMBENT ESTATE DURING MIGRATIONREFERENCE DESIGN
SpineAS7726-32X (100G)as deployed in Edgecore's public SONiC references
LeafAS7326-56X (25G/100G)
NOSEnterprise SONiC / Community SONiC
OpticsET7402 (100G) · ET7302 (25G) · DAC/AOC

WHAT WE DELIVER

  1. 01Current-fabric audit and tenancy model
  2. 02Engineered design + BOM
  3. 03Hardware supply
  4. 04Fabric build, ZTP and automation handover
  5. 05Acceptance incl. failover and tenant isolation proofs
  6. 06Documentation + IaC repository handover
  7. 07Support tiers

SIZING & TIMELINE

BANDSCALETIMELINE
S2–6 racks3–5 weeks
M6–20 racks6–10 weeks
L20+ racks / multi-site DCI10–16 weeks, phased
  • Outright purchase
  • เช่าใช้ 36-month service agreement
  • Design + migration-only engagement over existing procurement channels

PROVEN IN THE FIELD

Operators run production SONiC fabrics on this exact hardware. Photon State designs and delivers this solution in Thailand on the same platform.

Representative venue image

IPNexia

BELGIUM · 2026

Belgian operator IPNexia replaced aging, vendor-locked datacenter gear with a spine-leaf fabric of Edgecore switches running Broadcom Enterprise SONiC, with Deca Consulting handling design, rollout, and knowledge transfer. The rebuild added zero-touch provisioning and NetBox-driven Ansible workflows so the network can be run as infrastructure-as-code.

EDGECORE DEPLOYMENT · delivered with Deca ConsultingSOURCE ↗
Representative venue image

London Internet Exchange (LINX) - Manchester

UNITED KINGDOM · 2021
DATED

IP Infusion and Edgecore announced completion of a full production migration of the LINX Manchester interconnection point onto their disaggregated switch-plus-OcNOS solution, mirroring the earlier LON2 architecture. The rebuild added redundancy where a single point of failure previously existed and was credited by LINX with cutting cost of ownership while speeding technical improvements.

EDGECORE DEPLOYMENT · delivered with IP InfusionSOURCE ↗
Representative venue image

Multinational e-commerce company (unnamed)

2024

An unnamed multinational e-commerce operator built an IP Clos spine-leaf network with VXLAN/EVPN on Edgecore 400G switches running Community SONiC. Edgecore's hardened community SONiC distribution provided a production-ready open NOS across the deployment.

ALSO ON RECORD
  • SAKURA InternetJAPAN · 2019SOURCE ↗
  • CleanSafeCloud AGSWITZERLAND · 2015LEGACY STACKDATEDSOURCE ↗
  • Dubai MunicipalityUNITED ARAB EMIRATESLEGACY STACKSOURCE ↗

QUESTIONS BUYERS ASK

Is SONiC production-ready?
Edgecore's public references run it in production; the design states which distribution (Enterprise or Community) fits your operation and why.
Who supports the NOS?
Support tiers cover the full stack; NOS support channel (Edgecore/Broadcom or community + Photon State) is stated in the contract.
Can it interoperate with our Cisco/Arista gear during migration?
Yes — standard EVPN/BGP boundaries are part of the design, and migration runs estate-alongside-estate.
What about our existing automation?
The fabric is API-first; we hand over NetBox/Ansible workflows and adapt to your tooling where it exists.
Hardware failure at 3 a.m.?
ZTP means a spare configures itself from the repo; replacement paths per tier are contractual.
Why not white-box from a broker?
Same hardware, but with engineered design, acceptance testing, documentation and a Thai support contract behind it.