03-18-2012 10:20 AM - edited 02-21-2020 05:57 PM
Hello,
I'm in the process of setting up Anyconnect on the ASA, and have successfully updated the licensing, as well as uploaded the anyconnect pkg for web deployment. I enabled anyconnect on the outside interface and can now have the ASA push the client to the machine. Works fine. However, I want to add backup servers that the client will attempt to reach in the event the primary is down. I understand that "client profiles" can be created to customize settings like this. Problem is, when I follow the configuration guide with instructions for making client profiles at this location:
It shows that I should have an option for Anyconnect Client Profile and Anyconnect Client Settings.
I don't have either of those options in ASDM. Here's what mine shows:
I have another "SSL Client profiles" option, but it doesn't seem the same as the options above.
Can someone assist with what I need to do to get the Client Profiles option to be available so I can add backup server information to the client? Thanks!
Solved! Go to Solution.
03-18-2012 04:22 PM
It could be your ASDM version. I do note, however, that the ASDM Release Notes for 6.3(1) note that that version (when combined with ASA 8.3(1)) introduced support for the AnyConnect Profile Editor.
You can run the curent ASDM Version 6.4(7) with your ASA remaining on 8.2(1). Trying that wouldn't hurt.
Another bit more clunky alternative is to use the standalone AnyConnect Profile Editor and deploy the resultant xml profiles manually.
03-18-2012 07:19 PM
Glad you're up and working. Thanks for the rating.
Strange that the new ASDM isn't "taking". How did you upgrade it? If you use the current ASDM's menu ("Tools, Upgrade Software from Local Computer" it will push the new ASDM image onto the appliance via the https connection (assuming you've downloaded it locally) and set the configuration line to use it.
If you already have the new ASDM image on disk0, you can just replace the existing script line with:
asdm image disk0:/asdm-647.bin
03-18-2012 12:35 PM
What version of ASA and ASDM are you running? ("sh ver | i Ver")
Can you post the Anyconnect license status on this ASA? ("sh act | i Ess" and "sh act | i Pre")
I just checked an ASA with 8.4(3) and ASDM 6.4(7) with AnyConnect Premium license - it shows as the link you cited expects.
03-18-2012 01:48 PM
Thanks for the response Marvin,
It shows the ASA and ASDM versions are 8.2 and 6.2 respectively.
Result of the command: "sh version"
Cisco Adaptive Security Appliance Software Version 8.2(1)
Device Manager Version 6.2(1)
Result of the command: "sh act | i Ess"
AnyConnect Essentials : Enabled
I don't have the premium license, just the Anyconnect Essentials and Mobile licenses. I would imagine essentials should have the same profile configuration options, though. If it is in fact because I'm running an older version of ASDM, do I need to update both the ASA IOS and ASDM together, or can I just upgrade ASDM on its own? Thanks again.
03-18-2012 04:22 PM
It could be your ASDM version. I do note, however, that the ASDM Release Notes for 6.3(1) note that that version (when combined with ASA 8.3(1)) introduced support for the AnyConnect Profile Editor.
You can run the curent ASDM Version 6.4(7) with your ASA remaining on 8.2(1). Trying that wouldn't hurt.
Another bit more clunky alternative is to use the standalone AnyConnect Profile Editor and deploy the resultant xml profiles manually.
03-18-2012 06:56 PM
Thanks for the help! Per your advice, I used the standalone Profile Editor and exported the subsequent XML file to the ASA. This worked just as you suggested. I tried the upgrade to 6.4 ASDM, but it still wants to use version 6.2 when I connect to the ASA. At any rate, this provides me with a temporary solution until l can get the ASA updated to at least version 8.3 per your investigations. Thanks again!
03-18-2012 07:19 PM
Glad you're up and working. Thanks for the rating.
Strange that the new ASDM isn't "taking". How did you upgrade it? If you use the current ASDM's menu ("Tools, Upgrade Software from Local Computer" it will push the new ASDM image onto the appliance via the https connection (assuming you've downloaded it locally) and set the configuration line to use it.
If you already have the new ASDM image on disk0, you can just replace the existing script line with:
asdm image disk0:/asdm-647.bin
03-18-2012 08:38 PM
Great stuff. I was missing the "asdm image disk0:/asdm-647.bin" CLI command. I closed ASDM and relaunched and VOILA! Now the Anyconnect Client Profile is there! Thanks again, that saved some serious headaches.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide