NOC sees DHCP Discover from a new spine but no Offer. Which troubleshooting focus is most appropriate in a DC management context?
Select an answer to reveal the explanation.
Short Explanation
Discover with no Offer is a missing reply on the management path—scope empty, wrong VLAN, broken relay, or dead server. NOC should chase those basics before tearing down VXLAN. Overlay surgery rarely fixes a silent DHCP server.
Full Explanation
Discover without Offer points to DHCP scope, L2 domain membership, relay, or server reachability problems on the management path—not overlay rebuilds as first steps. Rebuilding the entire VXLAN overlay before checking L2/DHCP services wastes time on the wrong plane. Increasing EVPN MAC aging does not create DHCP Offers. Disabling spine uplinks worsens isolation instead of fixing silent DHCP. Exam caveat: Treat management-path DHCP as its own troubleshooting tree separate from EVPN/VXLAN. Operational check: Capture Discover on the management VLAN, verify scope availability, relay targets, and server logs for the new spine. 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.