ASA 5505 Software Version 7.2(3) Unexpected Reload

Unanswered Question
Sep 12th, 2008


I have a installed a new ASA ( see spec below ). Its been working fine for a few days but locked up twice yesturday ( 12 hrs apart ). I cant find anything in the logs or show tech. Has anyone come across something similar ?? if so please help

Cisco Adaptive Security Appliance Software Version 7.2(3)

Device Manager Version 5.2(3)

Compiled on Wed 15-Aug-07 16:08 by builders

System image file is "disk0:/asa723-k8.bin"

Config file at boot was "startup-config"

ciscoasa up 3 hours 5 mins

Hardware: ASA5505, 256 MB RAM, CPU Geode 500 MHz

Internal ATA Compact Flash, 128MB

BIOS Flash M50FW080 @ 0xffe00000, 1024KB

Encryption hardware device : Cisco ASA-5505 on-board accelerator (revision 0x0)

Boot microcode : CNlite-MC-Boot-Cisco-1.2

SSL/IKE microcode: CNlite-MC-IPSEC-Admin-3.03

IPSec microcode : CNlite-MC-IPSECm-MAIN-2.04

Licensed features for this platform:

Maximum Physical Interfaces : 8

VLANs : 3, DMZ Restricted

Inside Hosts : 50

Failover : Disabled

VPN-DES : Enabled

VPN-3DES-AES : Enabled

VPN Peers : 10

WebVPN Peers : 2

Dual ISPs : Disabled

VLAN Trunk Ports : 0

This platform has a Base license.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
robertson.michael Fri, 09/12/2008 - 07:15

Hi Suhale,

Does the device record a crash file when this happens ('show crash')?

When you say the device locks up, what exactly happens? Does a single interface stop passing traffic? Are you unable to reach the ASA at all? Are you able to get to the CLI via the console port?

If you watch the CPU and memory utilization ('show cpu' and 'show mem') do you see them slowly increasing or spiking up around the time of the problem?


schughtai Fri, 09/12/2008 - 07:28

Hi there

Thanks for the quick reply

I dont have a crash info module installed so I cannt see the crashinfo details

I am not able to get CLI via console when it crashes either.

I will observe the show mem show cpu settings nearer the time window to see what it is obvious....

suschoud Fri, 09/12/2008 - 07:33

Make sure asa interfaces are hard coded for speed and duplex settings.I am sure ur asa did not crash ( reload ) on it's own.When it locked up,I assume u reloaded it manually and that brought it back.Correct ?

If so,check interface speed and duplex......

Please rate if helpful.



robertson.michael Fri, 09/12/2008 - 07:36

Hi Suhale,

Since you did say that the ASA unexpectedly reloaded, a crashinfo file is definitely something you want to check for.

On the ASA, crashinfo files are recorded to flash automatically. So, unless you have 'crashinfo save disable' configured, you can look at the output of 'show crash' to see if a crash file was recorded.


schughtai Fri, 09/12/2008 - 07:47

No crash info file was generated - but I used 'crashinfo save enable' anyway to be sure one is generated

schughtai Fri, 09/12/2008 - 07:38

Hi Sushil

I will try the duplex settings and yes you are right I have to manually reload


This Discussion