l3_edge configuration

[rich9474]

Hi am attempting to configure a multi DC Fabric, and am struggling to work out how the DCI & L3 Edge configuration is supposed to work. I would like to be able to stretch L2 vlans across DCs for VM migration. the l3_edge config is fairly simple, but I am not sure how it is supposed to work both from the perpective of connecting the overlay VRF to external devices such as firewalls, and also for the inter site DCI connections.

The docs say "Make sure to configure the variables in a group_vars file covering all devices mentioned in the data model." but I can't see how I shoild reference the DCI configured under the L3_edge.

I have the following config

l3_edge:
  p2p_links_ip_pools:
    ip_pool_wan: "10.10.250.0/24"
  p2p_links_profiles:
    p2p_defaults:
      ip_pool: ip_pool_wan
      include_in_underlay_protocol: true
      bfd: true
      ptp_enable: true

  p2p_links:
    # Inter DC connections
    - id: 1
      profile: p2p_defaults
      nodes: [ dc1-wan1a, dc2-wan1a ]
      interfaces: [ Ethernet55/1, Ethernet55/1 ]
      as: [ "65001.1", "65002.1" ]
    - id: 2
      profile: p2p_defaults
      nodes: [ loynwan1b, losnwan1b ]
      interfaces: [ Ethernet55/1, Ethernet55/1 ]
      as: [ "65001.1", "65002.1" ]
    # Old world connections
    - id: 3
      profile: p2p_defaults
      nodes: [ l"dc1-wan1a", "dc1-core1" ]
      interfaces: [ Ethernet5, Ethernet1/45 ]
      as: [ "65001.1", "64999" ]
      speed: 10g
      include_in_underlay_protocol: false   # not sure about this
    - id: 4
      profile: p2p_defaults
      nodes: [ "dc1-wan1b", "dc1-core2" ]
      interfaces: [ Ethernet5, Ethernet1/45 ]
      as: [ "65001.1", "64999" ]
      speed: 10g
      include_in_underlay_protocol: false   # not sure about this

setting include_in_underlay_protocol: true seems to add config for the underlay bgp routing peering, but having false does not include the link in the Overlay peering config., it just sets an IP on the interface in the default vlan

Can someone please either point me in the direction of a multi DC example using l3_edge or explain what other components are required.

[ClausHolbechArista]

Hi
The l3_edge model will not cover overlay VRFs. We try to gather all data around VRFs inside the "Network Services" data model (tenants key by default).
This means that when you add or remove a VRF, there is only one place to modify.
If you look under the VRFs here, you will find l3_interfaces, bgp_peers, static_routes etc.
I hope this helps getting you started.
BR
Claus

[rich9474]

Thanks for the swift response Claus. That makes sense. It may be worth adding some words to clarify the use case for the l3_edge as I inferred from the include_in_underlay_protocol option that it would work with both the underlay and overlay.