Enhancement summary
AVD currently supports an underlay and overlay design for data center and MPLS networks. Many WAN networks only need an IGP and iBGP peering (with and without route reflectors). It is possible to create a custom node type with AVD to make the devices that are needed in this type of network, but then structured configuration must be added to remove the overlay. Sample YAML will be included in the alternative option.
Which component of AVD is impacted
eos_designs
Use case example
A use case similar to what is needed for this can be found in the Tech Library at https://tech-library.arista.com/solution_guides/internet_edge/#example-configuration-epebgp-lu
Additionally, consider a WAN core/edge design where an IGP is needed between devices and iBGP peering is needed as well. Some WAN cores do not use route reflectors as well, so full mesh is needed and the ability to activate the peers.
Describe the solution you would like
The desired solution would be to have a node type of WAN Core/Edge that does not need an overlay address family and encapsulation of mpls. If it is not desirable to create a new node type, at least have the option of no overlay address family and encapsulation mpls. Also there would need to be a way to activate mesh iBGP peers with or without route reflectors without structured configuration. It is noted that today if one node type is a client and the other is a peer, no structured configuration is required.
Describe alternatives you have considered
The following can be used as a node type to describe the core and edge:
custom_node_type_keys:
- key: wan_core
type: wan_core
default_mpls_overlay_role: client
connected_endpoints: true
default_evpn_role: client
network_services:
l1: true
l2: true
l3: true
default_overlay_address_families:
- vpn-ipv4
default_evpn_encapsulation: mpls
custom_node_type_keys:
- key: wan_edge
type: wan_edge
default_mpls_overlay_role: client
default_evpn_role: client
network_services:
l3: true
default_overlay_address_families:
- vpn-ipv4
default_evpn_encapsulation: mpls
However, structured configuration must be added for the node defaults to disable the vpn_ipv4 parts of the bgp configuration, and if no route reflector is desired, manual activation of the iBGP peers must be done.
structured_config:
address_family_ipv4:
peer_groups:
- name: IBGP-PEERS
activate: true
address_family_vpn_ipv4:
peer_groups:
- name: IBGP-PEERS
activate: false
Additional context
No response
Contributing Guide
Enhancement summary
AVD currently supports an underlay and overlay design for data center and MPLS networks. Many WAN networks only need an IGP and iBGP peering (with and without route reflectors). It is possible to create a custom node type with AVD to make the devices that are needed in this type of network, but then structured configuration must be added to remove the overlay. Sample YAML will be included in the alternative option.
Which component of AVD is impacted
eos_designs
Use case example
A use case similar to what is needed for this can be found in the Tech Library at https://tech-library.arista.com/solution_guides/internet_edge/#example-configuration-epebgp-lu
Additionally, consider a WAN core/edge design where an IGP is needed between devices and iBGP peering is needed as well. Some WAN cores do not use route reflectors as well, so full mesh is needed and the ability to activate the peers.
Describe the solution you would like
The desired solution would be to have a node type of WAN Core/Edge that does not need an overlay address family and encapsulation of mpls. If it is not desirable to create a new node type, at least have the option of no overlay address family and encapsulation mpls. Also there would need to be a way to activate mesh iBGP peers with or without route reflectors without structured configuration. It is noted that today if one node type is a client and the other is a peer, no structured configuration is required.
Describe alternatives you have considered
The following can be used as a node type to describe the core and edge:
custom_node_type_keys:
type: wan_core
default_mpls_overlay_role: client
connected_endpoints: true
default_evpn_role: client
network_services:
l1: true
l2: true
l3: true
default_overlay_address_families:
default_evpn_encapsulation: mpls
custom_node_type_keys:
type: wan_edge
default_mpls_overlay_role: client
default_evpn_role: client
network_services:
l3: true
default_overlay_address_families:
default_evpn_encapsulation: mpls
However, structured configuration must be added for the node defaults to disable the vpn_ipv4 parts of the bgp configuration, and if no route reflector is desired, manual activation of the iBGP peers must be done.
Additional context
No response
Contributing Guide