topic Re: Unable to Set ASDM Image on 5515-x in Network Security

Unable to Set ASDM Image on 5515-x

kbowles — Tue, 24 Dec 2024 00:17:19 GMT

I have a 5515-x firewall that use to allow ASDM connections without issue. Now out of nowhere the ASDM image has decided to remove itself and not allow itself to be added back.

I have done the following

hq-fw# show asdm image
Device Manager image file not set

hq-fw(config)# asdm image disk0:asdm-7201.bin
% ERROR: ASDM signature verification failed
hq-fw(config)#

Helppppppp lol

I tried setting no http certificate-authentication inside and redo the asdm set image command but still same error.

Re: Unable to Set ASDM Image on 5515-x

Flavio Miranda — Tue, 24 Dec 2024 00:44:36 GMT

@kbowles

Which is te ASA version?

Re: Unable to Set ASDM Image on 5515-x

kbowles — Tue, 24 Dec 2024 00:47:09 GMT

Hi,

9.12(4) 62 is the code it is running. using asdm-7201

Re: Unable to Set ASDM Image on 5515-x

Flavio Miranda — Tue, 24 Dec 2024 01:02:50 GMT

Error seems quite similar to the one on this Bug. Although version 9.12 was not reported.

https://bst.cisco.com/bugsearch/bug/CSCwc12322?rfs=qvlogin

Re: Unable to Set ASDM Image on 5515-x

kbowles — Tue, 24 Dec 2024 17:50:52 GMT

Yes I had seen that bug and noted that 9.12 wasn't reported as affected. The weird part was it was working no issues last week. Nothing changed in the environment but now it does not work randomly.

Re: Unable to Set ASDM Image on 5515-x

Flavio Miranda — Tue, 24 Dec 2024 18:03:10 GMT

Windows update? Maybe Java.

Re: Unable to Set ASDM Image on 5515-x

kbowles — Tue, 24 Dec 2024 19:07:01 GMT

I thought that too at first but I am able to ASDM into the other firewalls I manage. Thats also what led me to find that the asdm image had unset itself on the firewall in question.

Re: Unable to Set ASDM Image on 5515-x

Marvin Rhoads — Thu, 26 Dec 2024 15:18:21 GMT

You could be seeing behavior related to this: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwb05291

It is supposed to not affect 9.12(4)50 or higher in that release but the bugs sometimes regress. It could be that a firewall reload "forced" a revalidation of that newer ASDM release that is requiring it be signature-verified. You might try an older ASDM image since 7.18 (or even 7.12) will give you access to all supported features on that older ASA code.