ASA Public IP changing, what affect does it have on AnyConnect

[tselby3]

Hi

The public IP on our Cisco ASA is changing, what effect will it have with Cisco AnyConnect Mobility Client?  Currently, clients connect to AnyConnect with our current public IP, once a connection is established they choose a group from a dropdown and then enter their credentials for authentication.  I know they will need to change the old IP to the new IP to connect, and by selecting the group from the dropdown and authenticating I am assuming that the connection will be successful without having to edit any of the groups from the dropdown.  I have looked at all the profiles and groups and cannot find any relation to the public IP so I want to make sue I am not missing something.

Thanks.

[Rob Ingram · Accepted solution]

@tselby3 if you had configured a tunnel-group/connection profile with a group-alias and used the IP address instead of a FQDN then that would need changing.

Best practice would be to use a DNS FQDN and get the clients to point at the FQDN rather than the IP address.

In regard to the ASA configuration, change the IP address on the interface and a new default route with the new next hop IP address.

[MHM Cisco World]

only make change in DNS entry that it 

nothing will need to change in WebVPN config

MHM