Mainly, this is caused by misconfiguration, meaning, the Interface where Isakmp is binded, has already a NAT statement that will forward the packet to another destination for port 500, normally caused by a PAT statement.
The quick way to find this is out is using the following command along with the following string:
msgasa1(config)# sh xlate | inc 500
The solution is the clear the current Xlate that is using the port 500
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...