Municipal IPv6 tenants need host advertisements in the EVPN-VXLAN control plane alongside IPv4. What design awareness is required?
Select an answer to reveal the explanation.
Short Explanation
Dual-stack civic apps need the overlay phone book to speak both IPv4 and IPv6 host bindings—not just one. Turning on IPv6 underlay loopbacks is about reaching VTEPs, not auto-publishing tenant GUAs. EVPN is not an IPv4-only club that forces you back to GRE.
Full Explanation
Municipal IPv6 tenants that need host advertisements in the EVPN-VXLAN control plane alongside IPv4 require EVPN and VTEP configurations that support the needed host address families so MAC/IP routes can carry IPv6 bindings as well as IPv4 where dual-stack workloads exist. Underlay IPv6 reachability to VTEP loopbacks is necessary but separate from advertising tenant IPv6 addresses into EVPN.
IPv6 tenant hosts are not forbidden in EVPN, and claiming only IPv4 Type-2 routes are legal is incorrect for modern EVPN-VXLAN. Enabling IPv6 on underlay loopbacks does not automatically advertise every tenant GUA without EVPN and IRB configuration. IPv6 tenants need not disable VXLAN and fall back to GRE because of an “EVPN is IPv4-only” myth.
Exam caveat: dual-stack civic tenants need dual-stack EVPN/IRB feature enablement—not GRE substitution or underlay-only IPv6 assumptions.
Operational check: enable IPv6 host advertisement for a test MAC-VRF, learn an IPv6 neighbor on a leaf, confirm EVPN carries the IPv6 binding to peers, and ping between dual-stack hosts across VTEPs in the township fabric.
In civic fabric operations, retain the correct idea—The EVPN control plane and VTEP configurations must support the required host address families so MAC/IP routes can carry IPv6 as well as IPv4 bindings where dual-stack tenants exist—and reject distractors that confuse layers or tools. Specifically, do not treat “IPv6 tenant hosts can never be advertised in EVPN; only IPv4 Type-2 routes are legal.” as valid, do not accept “Enabling IPv6 on the underlay loopbacks automatically advertises every tenant GUA without EVPN.” as a substitute design, and do not operationalize “IPv6 tenants must disable VXLAN and fall back to GRE because EVPN is IPv4-only.” in production runbooks. Re-validate after changes with show commands for sessions, routes, VTEP reachability, and a simple tenant traffic test appropriate to the VNI under review.