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?
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.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...