Problem With ASA-5505

Unanswered Question
May 26th, 2010
User Badges:


I have about 30 ASA 5505 firewalls.  I am using them to remotely connect to my Allen Bradley PLCs.  I use ports 2222 and 44818 to connect to the PLC's from different devices.  The problem I am having is that sometimes one of the ports will stop responding.  More often than not it is the 44818.  To remedy the issue, I remotely connect to the firewall and perform and immediate system reload.  After the firewall comes back up, everything works normally.

There is no definite time period that this problem occurs and it does not occur equally across all of the firewalls.

Is this a known issue or is there some sort of resolution?

Thank you,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Panos Kampanakis Wed, 05/26/2010 - 11:46
User Badges:
  • Cisco Employee,

Issues like this usually relate to xlates.

I would start by checking the connnections ("sh conn det | i ") and xlates ("sh xlate deb | i ") for the host that is not working.

Also, check if clear local fixes the issue also or not just a reload (would mean it is not an xlate or conn issue).


Federico Coto F... Wed, 05/26/2010 - 11:51
User Badges:
  • Green, 3000 points or more

Just to add....

If you have the port open it should work everytime... so another thing that you can do is check the logs to see what kind of message you get when the connection fails and also run a packet tracer test when it fails (before reloading the device).


robert.mccarter Wed, 05/26/2010 - 14:04
User Badges:

I had a unit that had quit responding today.  I issued the "clear local" command and that cleared the issue.

Does that shed any light on the issue?

Thank you,


Panos Kampanakis Wed, 05/26/2010 - 14:22
User Badges:
  • Cisco Employee,

It is likely a bogus xlate.

You need to check the conns and xlates as suggested.



This Discussion