The ASA only terminates VPNs on the interface-IP-address. I'm pretty confident that your tweeks won't work on the ASA. But why do you want to use a different IP for VPNs? Perhaps there are better ways to solve your problem.
And the clients are configured with the VPN3000-IP instead of the FQDN?
Is there a possibility to instruct the clients to change the profile to FQDN instead of IP and later point the FQDN to the ASA? With the tunnel-count of the 5505 I wouldn't expect there to be that many clients.
Or different solution:
Use a second ASA 5505 for the VPNs to get some time in migration. Then change the clients to FQDN, move that to the primary IP and later combine the two ASAs to a Failover-system. Then you also have some redundancy when you're done.
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...