Qodex.ai

createOrgEvpnTopology

POST https://{{host}}/api/v1/orgs/:org_id/evpn_topologies

While all the evpn_id / downlink_ips can be specifidd by hand, the easiest way is to call the build_vpn_topology API, allowing you to examine the diff, and update it yourself. You can also simply call it with overwrite=true which will apply the updates for you.

Notes:

  1. You can use core / distribution / access to create a CLOS topology (or super-spine / spine / leaf)
  2. You can also use core / distribution to form a 2-tier EVPN topology where ESI-Lag is configured distribution to connect to access switches
  3. In a small/medium campus, collapsed-core can be used where core switches are the inter-connected to do EVPN
  4. The API uses a few pre-defined parameters and best-practices to generate the configs. It can be customized by using evpn_options in Site Setting / Network Template. (e.g. a different subnet for the underlay)

Collapsed Core

In a small-medium campus, EVPN can also be enabled only at the core switches (up to 4) by assigning all participating switches with collapsed-core role. When there are more than 2 switches, a ring-like topology will be formed.

ESI-Lag

If the access switchess does not have EVPN support, you can take advantage of EVPN by setting up ESI-Lag on distribution switches

Leaf / Access / Collapsed-Core

For leaf nodes in a EVPN topology, you’d have to configure the IPs for networks that would participate in EVPN. Optionally, VRFs to isolate traffic from one tenant verus another

Request Body

{"overwrite"=>true, "name"=>"CC", "switches"=>[{"mac"=>"5c5b35000003", "role"=>"collapsed-core"}, {"mac"=>"5c5b35000004", "role"=>"collapsed-core"}, {"mac"=>"5c5b3500000f", "role"=>"esilag-access", "pod"=>1}]}