EIGRP neighbors blocked using DMVPN dual tunnels?

My setup is like my work. I have 1 NHS router
I have tunnel5 /24 dmpvn peer addresses
I have tunnel6 /24 dmpvn peer addresses
If I shut either off the tunnels work fine seperate on their own, and establish eigrp neighbor ships
but If I have both tunnels up same time I get message:

 *Sep  4 01:23:30.312: %DUAL-6-NBRINFO: EIGRP-IPv4 2010: Neighbor (Tunnel6) is blocked: not on common subnet (
*Sep  4 01:23:57.875: %DUAL-6-NBRINFO: EIGRP-IPv4 2010: Neighbor (Tunnel6) is blocked: not on common subnet (

at my work I dont have this issue. why am i forming neighborship with wrong ip subnets?

I have 2 NHS servers routers
1 is for tunnel 5 -this is dmvpn subnet peer address
1 is for tunnel 6 -this is dmvpn subnet peer address

I get why conflict with eigrp neighbors not same subnet.but my work below has 2 different dmvpn subnets 10.166.43 and 10.166.143 different subnet and neighbors formed fine?
What am I doing wrong ? thank you.

I dont understand eigrp message. I get that neighbors have to be on same subnet.
but at my work ( . we have dmvpn tunnels on routers like this
tunnel5 is is dmvpn subnet peer address
tunnel6 is is dmvpn subnet peer address
and no error messages at my work?

this is message I am getting.

*Sep  4 00:16:45.459: %DUAL-6-NBRINFO: EIGRP-IPv4 2010: Neighbor (Tunnel6) is blocked: not on common subnet (


Hello Robert

I have a suspicion about what is happening, but without knowing more about your topology at home and your topology at work I can’t be sure. Let me share what I’m thinking and it may be able to help you…

It looks like you’re configuring DMVPN with a dual hub. The way in which you implement this will also depend upon your underlying physical and layer 2 infrastructure. If your infrastructure is a single layer 2 infrastructure, such as a single ISP connecting to both hubs, then you have a single cloud topology. If you have separate ISPs, or at least separate networks for each hub, then you would have a dual cloud topology.

The difference is that in a single cloud scenario, both hubs are on the same broadcast domain, while in the second case, each hub is in its own broadcast domain.

My suspicion is that at work, you have a dual cloud scenario while at home you are configuring a single cloud scenario. In this case, even if you have exactly the same configuration as the devices at work, you will encounter these EIGRP error messages, if the underlying network infrastructure is single cloud. This is because the interface of one hub will receive EIGRP multicast packets destined for a different subnet.

Take a look at the following two lessons which depect the two scenarios. These lessons use OSFP, but you can still understand the difference in their topologies, and the reasons behind the “not on common subnet” error.

Take a look at these and reexamine your topology. If you have further questions, let us know!

I hope this has been helpful!


thank you so much for your deep reply. wow I hope to know as much as you some day. hahah
thanks for the articles these are just what I need. I could not find them .but you found them for me
Thanks man!

1 Like