This is usually indicative of an ACL mismatch between crypto peers, e.g. ACLs not being mirror images, etc. However the ASR side is correct, but there is only the option to configure the remote network/subnet.
Are there any other scenarios where this error could be generated, which aren't related to crypto ACL mismatches?
If you get a 'debug crypto isakmp' and more importantly, a 'debug crypto ipsec', it *should* tell you what proxy identities are being sent from the other side so you can modify your side to match, or see if there is something (ie, it's tcp port based rather than IP) that might be causing the issue.
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...