topic Do you have a copy of the in Network Security

Cisco ASA 5510 NO CLI or ASDM

pprinz001 — Fri, 21 Feb 2020 13:10:15 GMT

Hello,

Have an issue with a 5510 at one of the data centers........

Made a change in the ASDM adding a SMTP rule in the access rules.

Applied the change (all good)

Then saved the config..... during the save the asdm froze.

The device is all up and and running and is able to be pinged.

I no longer can CLI (Telnet or SSH) and ASDM is not able to work anymore.

All VPNS are up and all is running OK.

I just can't SSH, Telnet or ASDM in to the unit internal or external. The device is in a remote site for console cabling is not an option. Can anyone please advise what to do........ is there anyway to get this going again without rebooting?

Regards......

Can you ssh to the inside

bmurray — Thu, 24 Apr 2014 21:44:46 GMT

Can you ssh to the inside interface? If it is a VPN tunnel.

Do you have a copy of the

bmurray — Thu, 24 Apr 2014 21:47:56 GMT

Do you have a copy of the config after the change and before wr mem?

No both internal and external

pprinz001 — Thu, 24 Apr 2014 21:49:46 GMT

No both internal and external can no longer be accessed via shh or telnet. I do not have a copy of the config that I could paste either.

Possibly the locally

bmurray — Thu, 24 Apr 2014 21:56:59 GMT

Possibly the locally generated key got changed. But if telnet to the inside does not work I am guessing that is not the problem. Do you have the config before the change?

Try a nmap to the outside ip

bmurray — Thu, 24 Apr 2014 22:01:06 GMT

Try a nmap to the outside ip and see if ssh or https is open.

Unfortunately this was for a

pprinz001 — Thu, 24 Apr 2014 22:02:12 GMT

Unfortunately this was for a newer production firewall and I have not backed up

I am not positive that a

bmurray — Thu, 24 Apr 2014 22:06:35 GMT

I am not positive that a reload will fix the problem. If the wr mem did not complete and you reload it might go back to before the change. But short of console access there is not much can be done.

I have had this happen before

pprinz001 — Thu, 24 Apr 2014 22:14:00 GMT

I have had this happen before on 5505's several times but reloading fixed. The change I made was minor and easy enough to redo it is just the 7 hour drive to the site. I thank you for your help.