Anyconnect client problem, load balancing fqdn changes after update client?

MJonkers · ‎10-14-2009

Hi,

We use two asa's in loadbalancing. Users use the loadbalancing fqdn name to connect. This works fine until we push new client anyconnect software, that the connect to field changes from the fqdn to the appliance ip address where the client downloaded the software. So loadbalancing will not work anymore. Is there a solution for this?

Thx,

Marc

dgabrielson · ‎11-13-2009

Marc, did you ever find a resolution for this? I have the exact same problem.

hdashnau · ‎11-13-2009

This sounds like CSCsz39019:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz39019

Symptom:

Anyconnect client preserves the FQDN name of the ASA its connecting to instead

of load-balancing cluster FQDN.

Workaround:

When the cluster member appears in the host list, user can select the correct

host by clicking the drop down. The next time user starts the client, the

cluster member will no longer be visible. It will have been replaced with the cluster name last selected.

This should be fixed in 2.3(2028)

2.4(192) and 2.5(53) or any higher release. Keep an eye out for the next release with this fix.