You're mostly there, but things get confusing depending on whether the interface that hosts the tunnel is in a VRF and/or the tunnel terminates on a VRF.
The "vrf customervrf" isn't needed on your keyring if you're just terminating the tunnel on the VRF. The "vrf customervrf" statement for that piece is only used if the interface hosting the tunnel is in a VRF, so this is going to keep your phase 1 from coming up.
You also don't need the "crypto map customer-crypto-map" statement on your GigabitEthernet0/0.12 interface. That should be applied to the interface facing the VPN peer.
I'm running under the assumption that you're only wanting to terminate the VPN on the VRF and that the route to the other end of the tunnel is in your global routing table. Please correct me if I'm wrong on that.
The VRF keyword on the letting can be removed unless the peer address is reached through that VRF.
From the looks of your configuration GigabitEthernet0/0.12 is the incoming interface for your VRF, not the outgoing interface for the peer. Assuming that the peer is across the Internet, the crypto map should be on the interface that holds the route to the peer. This will usually be your Internet-facing interface.
If the peer is being reached via GigabitEthernet0/0.12, then the vrf keyword is going to need to go back on the key ring and the crypto map will need to be applied to the GigabitEthernet0/0.12 interface again.
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...