Route-Target membership - RTC support

[onurgashi]

Issue Type

• Role enhancement

Is your feature request related to a problem? Please describe.
VTEPs will advertise their route-types for different services to Route-Servers/Route-Reflectors. There is a chance that not every VRF/VLAN will be on every VTEP, and with networks that have high numbers of routes every VTEP in the network will have to learn about all these even though they do not have the services defined on them. Thus leading to different scale issues data plane or control plane.

Describe the solution you'd like
Route target membership (RTC) will be very important addition to the AVD as it helps with scale and convergence as a result of lowering the scale.

The solution is to support new address-family (RT membership) that allows us to only reflect back to Leaves the route-types based on RT that are available on the VTEP. Thus reducing the number of routes massively.

router bgp {{ ASN }}
   !
   address-family rt-membership
      neighbor EVPN-OVERLAY-PEERS activate

Describe alternatives you've considered
In case of large data centres with hundreds of VTEPs there is a burden of implementing per neighbour (VTEP pair) policies using route-maps with extcommunity and AS path filters. This with scale will prove difficult.

Additional context
This is merely another address-family that will use the same peer-group config as EVPN peers and it will be enabled on EVPN speaking devices.