Overview

Layer 3 Leaf Spine VXLAN EVPN designs¶

Overview¶

The eos_designs role provides an abstracted data model to deploy various Layer 3 leaf & spine topologies leveraging a VXLAN data-plane with an EVPN control-plane.

The following topologies are supported:

Across all designs the following functionality is provided:

• Flexible placement of EVPN RS or RR, including dedicated overlay controller
• EVPN service definition: Layer 2 and Layer 3
• L3 Edge port definition
• Server edge ports definition

Inventory Structure¶

The inventory must have a dedicated group for super-spines and every leaf-spine POD. Example:

all:
  children:
    < DC-group-name >:
      children:
        < Super Spines group name >:
          hosts:
            < super-spine name >:
              ansible_host: < management IP >
            < super-spine name >:
              ansible_host: < management IP >
            ...
        < DC POD 1 group name >:
          children:
            < spines group >:
              <-- omitted -->
            < leaf group >:
              <-- omitted -->