Which option describes the purpose of the no ip next-hop-self eigrp configuration line in DMVPN deployment?
A. It preserves the original next hop value as learned by the spoke routers.
B. It allows the spoke routers to change the next hop value when sending EIGRP updates to the hub router.
C. It preserves the original next hop value as leaned by the hub routers.
D. It enables EIGRP to dynamically assign the next hop value based on the EIGRP database.
E. It allows the spoke routers to change the next hop value when sending EIGRP updates to the spoke router.
You are right, and it seems only logical.
See https://community.cisco.com/legacyfs/online/legacy/3/9/5/26593-DMVPNbk.pdf
It mentions “Spoke-to-spoke DMVPN networks present a unique challenge because the spokes cannot directly
exchange information with one another, even though they are on the same logical subnet. This limitation
requires that the headend router advertise subnets from other spokes on the same subnet. This would
normally be prevented by split horizon. In addition, the advertised route must contain the
hop as learned by the hub router. A new command (no ip next-hop-self) was added to allow this type of
operation”
Shouldn’t the correct answer be C?
when ‘ no ip next-hop-self’ command is to keep the next-hop learned by the HUB router (which will be pointing to the spoke router originating that advertisement). So It preserves the original next hop value as leaned by the hub routers