12-23-2024 04:17 PM
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.
12-23-2024 04:44 PM
Which is te ASA version?
12-23-2024 04:47 PM
Hi,
9.12(4) 62 is the code it is running. using asdm-7201
12-23-2024 05:02 PM
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
12-24-2024 09:50 AM
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.
12-24-2024 10:03 AM
Windows update? Maybe Java.
12-24-2024 11:07 AM
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.
12-26-2024 07:18 AM
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.
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