A design review asks who the “controller” is in a controllerless EVPN-VXLAN municipal fabric. Which answer best reflects the architecture?
Select an answer to reveal the explanation.
Short Explanation
Controllerless EVPN-VXLAN means the leaves and BGP do the talking—no mandatory brain-in-a-box pushing every MAC first. Route reflectors help scale BGP, but they are still part of that distributed control plane story. STP roots and console servers are not the EVPN controller.
Full Explanation
EVPN-VXLAN fabrics commonly use distributed control via Multiprotocol BGP among VTEPs, frequently optimized with route reflectors, rather than requiring a centralized SDN controller to program MAC tables. “Controllerless” in this context means BGP EVPN signaling provides the control plane. Spanning Tree roles and out-of-band consoles are unrelated to EVPN route origination. Centralized controllers can exist in some ecosystems, but they are not a prerequisite for standard Juniper EVPN-VXLAN professional designs.