09-20-2012 05:00 AM - edited 03-11-2019 04:56 PM
Hi,
I recently upgraded to ASA 8.2, but when I try to connect from the windows desktop ASDM I get the error ' Your ASA image has a version number 8.2(5) which is not supported by ASDM 5.2(4).
I installed the ASDM from version adsm-demo-649.msi which claims to be compatible with 8.2.
The installation was on a brand new machine, so no chance of it picking up an old version lurking somewhere in the background.
Any ideas of other things to try?
Thanks
DAmian.
09-20-2012 06:41 AM
You would need to also upload the asdm 6.4.9 image on the ASA itself.
Then refer the new image by configuring:
asdm image flash:/
09-20-2012 06:55 AM
Hi,
Thanks for the suggestion.
Unfortunately I can't figure out how to connect to the ASA to issue the command (I'm a novice, so sorry if this is basic stuff).
I connected to the ASA using the serial port, but the terminal window is flooded with logging messages. Everytime I try to issue a command, it seems the logging output is corrupting the input.
I can't connect via SSH since I didn't configure SSH access prior to the upgrade.
Are there any other ways to access the ASA to issue the command?
(I guess one option would be to unplug the ASA from the network to stop the traffic and consequently stop the logging messages, and then I can issue a command via terminal into the serial port. But, it's part of a live system, so I would only want to do that as a last resort).
Any other thoughts would be greatly appreciated.
Thanks again,
Damian.
09-20-2012 07:03 AM
What about telnet? did you try to telnet to the inside or any of the internal interfaces?
With the console connection, you can turn off logging. Depending on which mode you are currently on, you can try:
enable
config t
no logging on
Hopefully that would turn off the logging and you can at least manage it via console to enable telnet/ssh access so you can upload the asdm image.
09-20-2012 08:27 AM
Unfortunately Telenet access isn't configured either.
I'm not sure how to get the console to accept commands as it's being flooded with logging messages.
09-20-2012 02:04 PM
yes, i know it is being flooed with logging messages.
You can try to just type the command and it should be able to take it. You won't be able to view what you type, so make sure there is no typo
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