Multi-tenant EVPN-VXLAN fabrics for hosting and GPU clouds

IP Infusion delivers the multi-tenant data center fabric: OcNOS-DC on qualified switches that give each tenant its own VRF and VNIs on a shared EVPN-VXLAN fabric, and share a service between tenants only by an explicit route leak, under one support contract.

12OcNOS-DC switch models with EVPN-VXLAN
32 × 400Gports on a Trident 4 tenant leaf
900+operators run OcNOS
Best for
Hosting and GPU cloud operators giving each tenant its own VRF and VNIs on a shared fabric.
Running at
Scott DataProsoluceIzarLink

Each tenant sees only its own routes

On a shared fabric, every tenant gets its own VRF on the leaves it uses. The VRF holds only that tenant's routes, until you leak a shared service into it on purpose.

Pick a tenant to see its routing table on Leaf 1

Three leaves on a shared EVPN-VXLAN fabric, each carrying a VRF per tenant, with a shared services VRF on Leaf 3 Spine Spine Shared EVPN-VXLAN fabric Leaf 1 Leaf 2 Leaf 3 VRF Tenant A VRF Tenant A VRF Tenant B VRF Tenant B VRF Shared services Imported into Tenant A by route target

Tenant A. Leaf 1 holds Tenant A's local subnet and the subnet EVPN learns from Leaf 2. Tenant B's routes never appear.

Tenant A routes on Leaf 1
PrefixLearnedFrom
10.1.1.0/24LocalLeaf 1
10.1.2.0/24EVPNLeaf 2

Illustrative. Support varies by switch model.

What OcNOS-DC runs for tenants

Isolation, sharing and limits per tenant, from the OcNOS Feature Matrix.

CapabilityWhat it doesWhere
EVPN-VXLANLayer 2 EVPN over VXLAN, with VNIs per tenantTrident 3 and 4
Inter-VRF route leakingShares chosen routes between VRFsAll OcNOS-DC
Route leaking over EVPN-VXLANShares a service between tenant VRFs across the fabricSelected switches
Route-target filteringFilters EVPN routes by route targetSelected switches
EVPN multihomingSingle-active or port-active multihoming for a serverTrident 3 and 4
MLAGActive/active dual-homing for a server across a switch pairAll OcNOS-DC
Tenant limitsPer-tenant MAC limits and storm controlSelected switches
VXLAN QoSClassifies and queues tenant traffic on the overlayTrident 3 and 4
PFC and ECN over VXLANLossless storage traffic on the overlaySelected switches
BGP underlayEVPN-VXLAN with BGP unnumbered, and EVPN route reflection on the spineTrident 3 and 4 leaves

Support varies by switch model and license. Check the OcNOS Feature Matrix.

Switches by role

Tenant leaves run EVPN-VXLAN on Trident switches. The spine routes the underlay traffic.

Edgecore AS7326-56X switch

25G tenant leaf

Edgecore AS7326-56X

Trident 3 · 2.0 Tbps

48 × 25G, 8 × 100G

UfiSpace S9110-32X switch

100G tenant leaf

UfiSpace S9110-32X

Trident 3 · 3.2 Tbps

32 × 100G

Edgecore AS9726-32DB switch

400G leaf and border

Edgecore AS9726-32DB

Trident 4 · 12.8 Tbps

32 × 400G

Edgecore AS9736-64D switch

Spine

Edgecore AS9736-64D

Tomahawk 4 · 25.6 Tbps

64 × 400G

See the AI fabric for GPU traffic that needs lossless transport. See the data center fabric for a full data center build. See the full list of qualified switches on the OcNOS Hardware Compatibility List.

Questions about tenant isolation.

Each tenant gets its own VRF and VXLAN VNIs, which keep its routes and MAC addresses separate from other tenants. EVPN-VXLAN runs on Trident 3 and Trident 4 switches, so tenant VNIs live on the front-end and storage leaves.
A VLAN alone separates traffic only at Layer 2, inside one shared routing table. A per-tenant VRF gives each tenant its own routing table, and its VNIs carry it across the fabric, so tenants are separated in both bridging and routing.
Put the shared service in its own VRF and import its routes into each tenant VRF by route target. Each tenant reaches the shared service, and no tenant learns another tenant's routes. Route leaking over EVPN-VXLAN runs on selected switches, so check the OcNOS Feature Matrix.
Classify traffic by interface, ACL, DSCP or 802.1p into separate queues. VXLAN QoS runs on Trident 3 and Trident 4 switches, and PFC and ECN over VXLAN keep storage traffic lossless on supported switches.
MAC limits per tenant cap how many addresses a tenant can learn, storm control limits broadcast floods, and separate queues keep traffic classes apart. Support varies by switch model.
Trident 3 switches at 25G and 100G, and Trident 4 switches at 400G, carry the EVPN-VXLAN tenant leaves. Tomahawk 4 and Tomahawk 5 switches fit the spine. All run OcNOS-DC.

Solution brief and datasheet.

The EVPN-VXLAN fabric brief and the OcNOS-DC datasheet to share with your team. Quick form, and the PDF downloads immediately.

EVPN-VXLAN Data Center Fabric

How the fabric isolates tenants: a VRF and VNIs per tenant, and controlled route leaks for shared services.

Get the brief

OcNOS-DC Datasheet

The OcNOS-DC overview: the fabric feature set, the qualified data center hardware, and operations, in one PDF.

Get the datasheet

Plan your multi-tenant fabric.

Tell us your tenants, shared services and switch speeds. An IP Infusion engineer will map them to qualified switches and the isolation design that fits.