Refer to the exhibit: %LINK-3-UPDOWN: Interface Tunnel0, changed state to up %NHRP-5-REGISTRATION: Tunnel0: Spoke 10.1.1.25, NBMA 1.1.1.25 registered. %NHRP-5-REGISTRATION_COMPLETE: Tunnel0: Spoke…

The log lines 'NHRP-5-REGISTRATION: Tunnel0: Spoke 10.1.1.25, NBMA 1.1.1.25 registered' and 'NHRP-5-REGISTRATION_COMPLETE' confirm the spoke is performing its initial NHRP registration, supplying its tunnel address (10.1.1.25) and underlying NBMA physical address (1.1.1.25) to the NHRP server on the hub. This registration process is how a DMVPN spoke announces its reachability information so the hub can maintain the NHRP mapping database and other spokes can later dynamically resolve its address.

The debug output reflects the spoke's registration request and completion sequence, not the hub's acknowledgement workflow - the perspective shown is the registration being received and cached, not the hub sending a reply.

The first line 'Interface Tunnel0, changed state to up' indicates the tunnel interface is coming up, which is the opposite of being disabled or going down.

The messages display NHRP-specific event codes (NHRP-5-REGISTRATION) and cache entries, not IKE or ISAKMP phase 1 negotiation messages, which would show completely different debug prefixes and exchange information.