Sadly enough, sometimes network equipment goes out of order. This, of course, happens when you're least expecting it. In most cases that I've come across throughout my work, this is what happens: Cisco ASA is unexpectedly powered down or reloaded (due to planned or unplanned power outage, thunderstorm or work with electric equipment), and after reload, the interfaces, VPN tunnels and other services don't come back up. We're not going to examine the situation in which the device cannot turn on entirely and all the LED indicators are dead - in that case, a replacement for the device is the only viable option. Let's focus on the situation when the Cisco ASA device is still operable, but does not perform a full load - i.e. the Cisco IOS operating system image can't load properly. In this case, there is still a chance to reanimate the device, at least until you get a new one for replacement.
The first thing we need to do is connect to the firewall through a console cable. If the firewall does not respond to any commands and produces no output on the console screen, then you've reached the worst-case scenario - you can thank the device for its long and fruitful service and put it on a shelf. However, if you are seeing some activity on the console screen, it's not that bad and you can try to understand what's going on. The firewall may have entered into the special ROMMON mode (under normal circumstances, this mode is activated by pressing the ESC key during boot-up) or is in a cyclic reload that happens as it tries to load the operating system image.
The special ROMMON mode looks something like this:
Use ? for help.
ROMMON #0>
Once you're in this mode, you should try to force the device to start by entering the system command "boot":
ROMMON #0> boot