"... SHA-256 ... can also be used for ESP integrity protection on the newer ASA platforms (and not 5505, 5510, 5520, 5540, or 5550)."
Since Cisco has announced the end-of-life date for these older platforms, it may be a good time to evaluate migrating to the newer hardware. The standard sha-1 is plenty of hash for the ipsec sa's for now until systems are replaced with the new gear.
The following legacy models do not support ASA 9.2 (refer to the link at the bottom). That is why in 9.2 guide the note "... SHA-256 ... can also be used for ESP integrity protection on the newer ASA platforms (and not 5505, 5510, 5520, 5540, or 5550)." was removed. In other words, the following models do not support SHA-2 in IKEv1 or IPsec (but they do support SHA-2 in IKEv2).
Your link (as of right now) says 9.2 is supported on the 5505 but SHA-2 for ESP integrity is not supported in the 5505 despite what half the documentation says. 9.2 VPN CLI configuration guide page 1-31 says it should support it while page 6-10 says it doesn't support it. SHA-1 it is then it seems
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...