I tried it, but it didn't work. Creating a second tunnel-ifc was ok, but the IP address must be in another range. Also the original tunnel crashed after applying the crypto rules.
I found some new commands on CCO, which our actual installed IOS doesn't support yet. i.e. "clear ip nhrp" and others.
This morning I performed the migration succesfully! The solution was to install a "out-of-band" backdoor on every spoke. Like an ssh or https access. This way, after changing the nhrp mapping, it was possible to login via ssh, then shut/no shut the tunnel-ifc. This way, the router activated the new mapping and a new tunnel was built to the hubs new IP-address.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...