EIGRP One-way Peering in DMVPN

[Jason Szucs]

After upgrading from 12.4(15)T13 to 15.2(4)M3 we have an EIGRP one-way peering condition.  The Hub sees the remote, but not vice-versa.  The condition can be temporarily resolved by deleting the tunnel from the configuration and then re-adding it.  After about a day, the one-way condition returns.  A reboot does not resolve the issue.  Booting back to T13 code also resolves.

Hardware is 7206VXR (NPE-G2) on both Hub and Spoke.

Has anyone seen this condition or possibly have a bugID to reference?

[Lei Tian]

Hi,

Do you see one way neighbor on ipsec, or routing protocol? Does it impact traffic? This seems to be new. I just did a bug scrub for my customer against the code. There are couple critical IPSec bugs, but I don't recall seen this DMVPN issue. Please open a case with TAC to track the bug.

HTH,
Lei Tian

Sent from Cisco Technical Support iPhone App

[Jason Szucs]

It's a one-way peering relationship with EIGRP.  The peers on the encrypted DMVPN cloud are lost, but LAN peers are unaffected.  I've opened a TAC Case to investigate.