I'm new to ASA and have a question about what alternatives there is to manage the ASA "out of the box".
My problem is that after uppgrading ASDM to 6.0(3) I get the following error message:
"Your ASA Image has a version number 7.2(2) which is not supported by ASDM 6.0(2). Please use Device Mgr 5.2(x)"
I've tried downloading and installing ASDM 5.2(3) but when I try to connect it upgrades leaving me stucked with no connection.
The thing I think is making this is: asdm image flash:/asdm-603.bin...
When trying to connect with SSH i recieve a login prompt but can't login with the same password as through ASDM. (are the login options different from ASDM?).
I've never needed to connect through terminal and Console: Does the login options (user and pwd) differ in some way from ASDM?
I have not changed any settings as far as I know for administrative access more then enabling ASDM for VPN https access.
Hope someone can help me regaining access to my ASA.
First try fixing asdm, go to firewall command line and see where your asdm upgrade image landed "dir", most likely it landed in disk0, if that is the case do " show run | inc asdm" to see current firewall asdm statement and correct as follows.
Directory of disk0:/
75 -rwx 6851212 05:22:16 Dec 11 2007 asdm-603.bin
76 -rwx 1868412 09:02:20 Apr 19 2007 securedesktop-asa-184.108.40.206-k9.pkg
77 -rwx 398305 09:02:36 Apr 19 2007 sslclient-win-220.127.116.11.pkg
2 drwx 4096 05:27:40 Dec 11 2007 log
79 -rwx 14635008 05:17:54 Dec 11 2007 asa803-k8.bin
80 drwx 4096 11:00:56 Oct 18 2007 sdesktop
6 drwx 4096 05:28:02 Dec 11 2007 crypto_archive
81 -rwx 545757 08:02:48 Jan 04 2008 rdp-plugin.jar
82 -rwx 2206269 08:03:34 Jan 04 2008 sslclient-win-18.104.22.168-anyconnect.pkg
verify that indeed your asdm 5.2.3 the one you downloaded is in disk0 directory, if it is there do the following to verify asdm config statement in firewall.
show run | inc asdm
it will show the firewall current asdm config statement, if it is still loading 603 you must correct it.
remove old statement, add new statement
asa(config)#no asdm image disk0:/asdm-603.bin
asa(config)#asdm image disk0:/new_asdm_image.bin
I do not believe you need reboot after changing statement, after corrections try loading asdm, if it does no load then reboot asa, but again asdm should load without reload.
as for ssh follow this link.( use aaa authentication local )
Let us know how it works out.
Rate any helpful posts if it helps