Draw the fabric.
Get every config.

This one is real: two spines and four leaves, VXLAN EVPN on Nexus 9000. Each filled cell is a section of configuration Fabricwright wrote for that device. Choose one to read it.

Free during launch. Sign in with Google or GitHub. No card, no password.

The configuration Fabricwright wrote for each device, by section. Choose a cell to read the first lines of it.
VXLAN EVPNNexus 9000spine1Spinespine2Spineleaf1Leafleaf2Leafleaf3Leafleaf4Leaf
Base and management
OSPF underlay
Fabric links
BGP EVPN
VTEP
VLAN 100 USERS
VLAN 200 SERVERS
VRF TENANT_A
Anycast gateways
  • Written by the generator
  • The chosen device and section
  • Not in that device's config
leaf1.cfgVRF TENANT_A6 of 15 lines
153vrf context TENANT_A154  description TENANT_A tenant VRF155  rd 10.255.255.1:10156  vni 33010 l3157  address-family ipv4 unicast158    route-target both 65000:109 more lines in this part, not shown here

Real output from the generator, unedited: the first lines of each part.

Columns are devices. Rows are configuration.

What you draw is the design, so there's no spreadsheet or separate diagram to keep in step with it. The fabric above took these four steps.

  1. Draw the fabric

    Pick one of five fabric types, place the devices and give each a platform and a role: spine, leaf, P, PE, core or access. Only valid choices are offered, so a role a platform can't hold never appears.

  2. Cable it

    Draw the core links and the host links. Speed, module and port become the interface name each platform uses, and every link is described with the device and port at the other end.

  3. Add the services

    VLANs, VRFs, E-Line and E-LAN, through a wizard that says what's still missing. A service stays a draft until it's complete. A long list can come in from CSV.

  4. Generate

    Every device gets its whole configuration, from the base settings to the last route target, from the same templates every time, with warnings for anything that doesn't add up.

Every address handed out once

Four of the links in the draft above, as the generator named, addressed and described them. Router IDs, point-to-point /31s, VTEP loopbacks, management and out-of-band addresses all come from pools you set, and none is given out twice.

Spine portAddressLeaf portAddressLeaf's description
spine1 Eth1/110.255.0.0/31leaf1 Eth1/4910.255.0.1/31To_spine1_Eth1/1
spine1 Eth1/210.255.0.2/31leaf2 Eth1/4910.255.0.3/31To_spine1_Eth1/2
spine2 Eth1/110.255.0.8/31leaf1 Eth1/5010.255.0.9/31To_spine2_Eth1/1
spine2 Eth1/210.255.0.10/31leaf2 Eth1/5010.255.0.11/31To_spine2_Eth1/2
  • Spine port and leaf port, above

    Interface names that match the box

    Speed, module and port become Eth1/4, Te1/1/4 or Hu0/0/0/1, as each platform names them, and each description names the far end.

  • Row: Anycast gateways

    Gateways you choose

    Anycast gateways on VXLAN. HSRP everywhere else, with the pair you pick and the active side set per device, not guessed from the cabling.

  • Row: OSPF underlay

    BFD, multicast and IPv6

    BFD on the links you pick, as on every fabric link here. TRM on VXLAN and MVPN profiles on MPLS. Dual-stack VLANs next to IPv4-only ones.

  • Not drawn in this fabric

    Dual-homing done per platform

    vPC on Nexus, EVPN ethernet segments where the platform supports them, and port-channels on everything else, with matching IDs on both sides.

  • The whole project

    Yours to take away

    Export the topology as a printable PDF with an inventory, or the whole project as a file you can import again later. Projects are saved to your account, and a second tab can't silently overwrite the first.

It won't write what the box won't take

A generator that offers everything will happily write config a box rejects. Fabricwright leaves those options out, and says why.

  • No ESI dual-homing on Nexus. NX-OS EVPN multihoming is too new, so dual-homing there is vPC.

  • No E-Line or E-LAN on a Catalyst PE. It carries VLANs instead, stretched by VFI over LDP.

  • No access role on a router, so nothing switched is ever written for one.

  • No VXLAN roles on IOU images, which accept the config but don't forward it reliably.

Why these choices were made
Services offered on each fabric
FabricVLANVRFE‑LineE‑LANRoles
VXLANYesYesNoNoSpine, Leaf, Access
MPLS-LDPNoYesYesYesP, PE, Access
SR-MPLSNoYesYesYesP, PE, Access
VRF-LITEYesYesNoNoCore, Access
PURE-L2YesNoNoNoCore, Access
Every fabric has an Access role for switches that hang off it. A Catalyst PE on MPLS is offered VLANs in place of E-Line and E-LAN.

Coming soon

Planned for Design, with no dates yet.

  • QoS support

    Quality-of-service policy, written with the rest of each device's configuration.

  • SRv6 support

    Segment routing over an IPv6 data plane.

  • Nexus 9000 EVPN ESI dual-homing

    EVPN ethernet segments on Nexus, where today dual-homing is vPC.

  • Multi-fabric support

    Several fabrics in one project, and the links between them.

Notes from the lab

How-tos and design notes on VXLAN EVPN, MPLS, segment routing and the platforms they run on, newest first.

All posts

Every post, in one place

How-tos and design notes, including a step-by-step guide to Design.

Built for network engineers, by one

Fabricwright is built and run by Rafi Samuel, CCIE Enterprise Infrastructure #66087, with more than ten years of hands-on network work.

Rafi writes the templates, tests them against real platforms in a lab, and reads every message that reaches support. It's independent, with no investors. It doesn't replace your judgement: every configuration is written to be read, and you should still review it before it goes near a live network.

More about Fabricwright

Design first. The rest follows.

Design is live now. The next two tools take a finished design onto real hardware.

  • Design

    Live now. Draw the fabric, pick roles and services, and generate the configuration for every device.

    Explore Design
  • Provision

    Planned. Hands those configurations to the boxes over PnP and POAP, so a switch configures itself when it's plugged in. A server you download and run beside them.

    What's planned
  • Build

    Planned. Puts together IOS-XR golden images from a base ISO, optional packages and bug fixes. It ships inside Provision.

    What's planned

Free while it launches

Every fabric type, every service, up to three projects. Paid plans come later, and accounts will be told before anything starts costing money.