topic Re: Problem With ASA-5505 in Network Security

Problem With ASA-5505

robert.mccarter — Mon, 11 Mar 2019 17:51:03 GMT

Hello,

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,

Robert

Re: Problem With ASA-5505

Panos Kampanakis — Wed, 26 May 2010 18:46:41 GMT

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).

Re: Problem With ASA-5505

Federico Coto Fajardo — Wed, 26 May 2010 18:51:21 GMT

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).

Federico.

Re: Problem With ASA-5505

robert.mccarter — Wed, 26 May 2010 21:04:19 GMT

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,

Robert

Re: Problem With ASA-5505

Panos Kampanakis — Wed, 26 May 2010 21:22:23 GMT

It is likely a bogus xlate.

You need to check the conns and xlates as suggested.