A county fabric uses DHCP relay from the management VRF to a central DHCP server. Why does relay commonly appear in this DC management design?
Select an answer to reveal the explanation.
Short Explanation
When the DHCP server sits in a central VRF and the new leaf is on another management subnet, relay is the courier that forwards the Discover. County fabrics use it so one server can serve many provisioning segments. It is not an EVPN crypto feature or a VXLAN load-balancer.
Full Explanation
DHCP relay appears in county fabrics so provisioning clients and a central DHCP server can live in different management subnets or VRFs while still completing Discover/Offer/Request/Ack. Relay does not encrypt EVPN routes end to end. Relay does not replace the need for an actual DHCP server. Relay is not a VXLAN BUM load-balancing feature on spines. Exam caveat: Mis-aimed relay helpers or wrong VRF context are common reasons Discover never becomes Offer across segments. Operational check: Traceroute/check from leaf management VRF to the relay target and confirm the central server sees Discover messages with correct giaddr/context. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.