Closed perimore closed 1 year ago
@perimore the flood group is technically a separate feature right? So we can implement the two areas (IRB and flood group) seperately? I mean for all networks the flood group can be useful, even when not using IRB/OISM. Thanks.
@perimore the flood group is technically a separate feature right? So we can implement the two areas (IRB and flood group) seperately? I mean for all networks the flood group can be useful, even when not using IRB/OISM. Thanks.
Sure, separate feature below:
Enhancement summary
Support for EVPN Optimized Inter-Subnet Multicast Forwarding and Multicast EVPN Transit
Which component of AVD is impacted
eos_designs
Use case example
This enhancement will extend EVPN Multicast to support inter-subnet routing of multicast traffic within a tenant VRF, otherwise known as OISM.
OISM functionality and configuration is described in the document below:
https://www.arista.com/en/support/toi/eos-4-25-1f/14670-multicast-evpn-irb
Plus simple knob to enable transit as described below:
https://www.arista.com/en/support/toi/eos-4-26-2f/14832-multicast-evpn-transit
Describe the solution you would like
Providing the following are true at the fabric level:
The following can be enabled at the tenant level. But can imagine we will want control per VRF and/or per SVI as multicast is not always enabled on every VRF and VLAN.
Assuming the below tenant config:
The following config will be built:
Describe alternatives you have considered
Control at the VRF or VNI level could be achieved with:
Additional context
No response
Contributing Guide