DMVPN and HSRP are not designed to work together. When using pure IPsec with two hubs where you need redundancy, you have to combine this with a mechanism like HSRP. This is because we cannot run a dynamic routing protocol through the pure IPsec tunnels to help out with forwarding traffic. So the Stateful IPsec feature was added to specifically have IPsec work with HSRP and keep the IPsec and ISAKMP SA databases synchronized between the two HSRP routers. Therefore HSRP can switch the encrypted traffic between the two HSRP routers as necessary without too much loss of traffic.
DMVPN uses an active/active redundancy model where we build at least two spoke-hub tunnels one to each DMVPN hub from the DMVPN spoke. These tunnels come up immediately and stay up all of the time. With the DMVPN active/active redundancy model we didn't need Stateful IPsec nor a protocol to transfer NHRP mapping information between hub routers, since the hub routers would have their own independent IPsec and NHRP database information. Because of this DMVPN is not designed to work with HSRP.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...