<div>
4/21/2009 8:47:22 AM &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;172.16.101.254 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Emergency &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;%ASA-0-716507: Fiber scheduler has reached unreachable code. Cannot continue, terminating
</div>


4/21/2009 8:47:22 AM      172.16.101.254      Emergency      %ASA-0-716507: Fiber scheduler has reached unreachable code. Cannot continue, terminating

<div>
no. We have a machine with a console cable connected to it. And I consolled in successfully, then I saw something about a memory leak and now we can't even console in
</div>


no. We have a machine with a console cable connected to it. And I consolled in successfully, then I saw something about a memory leak and now we can't even console in

<div>
ok do one thing. Try to change the port speed if you are using putty or secure crt. If it doesn't work then could it be &nbsp;possible for you then reload it then at the boot prompt press escape and try to write boot flash:flashname. 
</div>


ok do one thing. Try to change the port speed if you are using putty or secure crt. If it doesn't work then could it be  possible for you then reload it then at the boot prompt press escape and try to write boot flash:flashname.

<div>
we rebooted it and it worked
</div>


<div>
<div class="content wysiwyg-content">
We have an ASA5505 at our backup site/co-location. Solarwinds reported that last night it went down and then came back up 3 minutes later. <br />
<br />
Right now, I can ping this device from headquarters, but can't SSH in. I ran ethereal during an attempted SSH session. The three way handshake completed, so I know port 22 is still open.<br />
<br />
All other devices at the co-location are accessible. Any ideas? I can ping it like I said, so the routing must be in place. 
</div>
</div>


We have an ASA5505 at our backup site/co-location. Solarwinds reported that last night it went down and then came back up 3 minutes later. 

Right now, I can ping this device from headquarters, but can't SSH in. I ran ethereal during an attempted SSH session. The three way handshake completed, so I know port 22 is still open.

All other devices at the co-location are accessible. Any ideas? I can ping it like I said, so the routing must be in place. 

ASA5505, can't SSH in all of a sudden

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.