According to cRPD documentation, cRPD is able to delegate to the Linux kernel the creation of the devices required for vxlan transport in evpn, supporting both mac-vrf (type 2 routes) and ip-vrf (type 5 routes).
(However, no static vxlan from what I see)
See as example https://www.juniper.net/documentation/us/en/software/crpd/crpd-deployment/topics/topic-map/debugging-evpn-vxlan-on-rpd-and-kernel.html
Configuration should be extremely similar to the one used for vjunos-router or vPTX, using bridge domains inside mac-vrfs.
(Side note: MPLS transport for evpn seems supported as well, but only for L3VPN - Type 5 -- https://www.juniper.net/documentation/us/en/software/crpd/crpd-deployment/topics/concept/crpd-supported-features.html )
According to cRPD documentation, cRPD is able to delegate to the Linux kernel the creation of the devices required for vxlan transport in evpn, supporting both mac-vrf (type 2 routes) and ip-vrf (type 5 routes).
(However, no static vxlan from what I see)
See as example https://www.juniper.net/documentation/us/en/software/crpd/crpd-deployment/topics/topic-map/debugging-evpn-vxlan-on-rpd-and-kernel.html
Configuration should be extremely similar to the one used for vjunos-router or vPTX, using bridge domains inside mac-vrfs.
(Side note: MPLS transport for evpn seems supported as well, but only for L3VPN - Type 5 -- https://www.juniper.net/documentation/us/en/software/crpd/crpd-deployment/topics/concept/crpd-supported-features.html )