unable to learn eigrp routes via DMVPN Tunnel phase 2

[Saurabh1]

Hi , I am unable to learn EIGRP routes from DMVPN neigbour . Also getting alert 

*May 23 01:50:32.219: %DUAL-5-NBRCHANGE: EIGRP-IPv4 222: Neighbor 10.248.2.2 (Tunnel400) is down: retry limit exceeded
*May 23 01:50:32.960: %DUAL-5-NBRCHANGE: EIGRP-IPv4 222: Neighbor 10.248.2.2 (Tunnel400) is up: new adjacency

Spoke config

interface Tunnel400
ip address 10.248.2.16 255.255.255.0
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 222
no ip split-horizon eigrp 222
ip nhrp authentication cisco
ip nhrp map 10.248.2.2 84.153.201.154
ip nhrp map multicast 10.248.2.2
ip nhrp network-id 111
ip nhrp holdtime 360
ip nhrp nhs 10.248.2.2
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel protection ipsec profile cisco

exit

router eigrp 222
network 10.0.0.0

Hub Configuration

interface Tunnel400
ip address 10.248.2.2 255.255.255.0
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 222
no ip split-horizon eigrp 222
ip nhrp authentication cisco
ip nhrp map multicast dynamic
ip nhrp network-id 111
ip nhrp holdtime 360
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel protection ipsec profile cisco

exit

router eigrp 222
network 10.0.0.0

[Kevin Rivest · Accepted solution]

The spoke configuration should be:

interface Tunnel400
ip address 10.248.2.16 255.255.255.0
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 222
no ip split-horizon eigrp 222
ip nhrp authentication cisco
ip nhrp map 10.248.2.2 84.153.201.154
ip nhrp map multicast 84.153.201.154
ip nhrp network-id 111
ip nhrp holdtime 360
ip nhrp nhs 10.248.2.2
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel protection ipsec profile cisco

Having the wrong NBMA IP address specified for multicast traffic on the spoke is causing EIGRP to fail after switching over to multicast hellos on the spoke side to hub.

[Saurabh1]

This is public ip at Hub side 

[Kevin Rivest]

Yes, the hub's public IP address is the address that should be specified in that command. The ip nhrp map multicast command tells the spoke router to replicate multicast traffic as unicast to the public IP address of the hub. With the tunnel or no address specified the spoke router will not know the correct location to replicate multicast to for EIGRP. This is causing one way multicast from the hub to spoke, the spoke cannot multicast hellos back. The adjaceny is building originally because the spoke responds to hub EIGRP messages through unicast. Once the communication switches back to multicast the hub cannot see the spoke.

[Saurabh1]

Still i a m facing same issue . Please assist me further . Now I am getting this message on hub router . Changes in config mentioned below . 

*May 23 02:37:11.057: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.248.2.16 (Tunnel400) is down: retry limit exceeded
--More--
*May 23 02:37:15.963: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.248.2.16 (Tunnel400) is up: new adjacency

Spoke

interface Tunnel400
ip address 10.248.2.16 255.255.255.0
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 100
no ip split-horizon eigrp 100
ip nhrp authentication cisco
ip nhrp map 10.248.2.2 84.153.201.154
ip nhrp map multicast 84.153.201.154
ip nhrp network-id 111
ip nhrp holdtime 360
ip nhrp nhs 10.248.2.2
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel protection ipsec profile cisco

router eigrp 100
network 10.0.0.0

Hub

interface Tunnel400
ip address 10.248.2.2 255.255.255.0
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 100
no ip split-horizon eigrp 100
ip nhrp authentication cisco
ip nhrp map multicast dynamic
ip nhrp network-id 111
ip nhrp holdtime 360
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/0
tunnel mode gre multipoint
tunnel protection ipsec profile cisco

exit

router eigrp 100
network 10.0.0.0

[Saurabh1]

Thanks issue got rectified !!!! I did EIGRP configuration again and now everything is working . Thanks !!!