A housing authority spoke stops registering to the DMVPN hub after the branch firewall’s NAT pool changes. What registration detail should engineers verify first?
Select an answer to reveal the explanation.
Short Explanation
When the firewall’s public face changes, the spoke’s “home address on the Internet” changes too. NHRP registration and NAT-T have to advertise that new NBMA mapping—old pool leftovers leave the hub staring at a ghost.
Full Explanation
DMVPN spokes behind NAT register an NBMA address that must reflect the currently mapped public address the hub can reach. After a NAT pool change, stale mappings, blocked NAT-T (UDP 4500), or mismatched outer addressing prevent Registration Reply success even if GRE and IPsec transforms still look correct. Campus L2 features such as VTP are unrelated to spoke-to-hub NHRP registration over the underlay.