topic Re: Session end reason: tcp-fin and aged-out? in General Topics

Session end reason: tcp-fin and aged-out?

Chivas — Mon, 14 Jan 2019 06:05:49 GMT

Hi all,

I am using PA-850. I am having the problem. sometimes the internet is blocked. and I see in the monitor, the sesson end is: tcp-fin and aged-out. but after refresh some times, then I can access to internet.

Please help to advise how to fix it. please let me know if you need more information for this issue

Re: Session end reason: tcp-fin and aged-out?

santonic — Mon, 14 Jan 2019 07:28:42 GMT

TCP-FIN is a normal way to end a TCP session and doesn't indicate an error.

Aged-out is as normal way for UDP session to end. But make sure packets are flowing in both way in this case, check sent/received packets count.

Re: Session end reason: tcp-fin and aged-out?

Chivas — Mon, 14 Jan 2019 08:37:32 GMT

Hi Santonic,

I checked and see that, session end reason aged-out: packets sent and packets recived is same numbers

but session end reason tcp-fin: sent and recviced is different.

please help to advise.

Re: Session end reason: tcp-fin and aged-out?

santonic — Mon, 14 Jan 2019 13:47:44 GMT

That's all normal. That doesn't indicate any errors.

Re: Session end reason: tcp-fin and aged-out?

chouna19 — Thu, 15 Oct 2020 01:07:27 GMT

Hi,

Aged-out doesn't mean failed to get a further response as well..? For some reason, the other end is not responding to my query, after a certain amount of time, the session will age out and terminated. The reason could be my IP is been block listed, or some network path issue in-between.

Thanks,

Narendra

Re: Session end reason: tcp-fin and aged-out?

TMSSupport — Fri, 03 Dec 2021 18:34:32 GMT

Hello,

I am the Jr. Network Admin of a Private School in Dobbs Ferry, NY and we are experiencing this exact issue. Our traffic is fine for our users until suddenly they are unable to get to any external webpages and the Traffic Monitor shows the session application as "incomplete" and end reason of "Aged-out" despite being TCP. After anywhere from 5-15 minutes, it seems to clear up and be fine, only to happen to another subnet/user(s) again and again. Our packet captures show "flow_fwd_l3_noarp 12 0 drop flow forward Packets dropped: no ARP" and nothing we have done seems to fix it. We have confirmed there are no Security or NAT policies that are blocking the traffic and that the counters on the network facing interfaces increase for "no arp found" and "packets dropped by flow state" increase when the problem occurs. The external interfaces affected show only increasing counters for "packets dropped by flow state."

It has been on and off for about 3 months and Palo Support has not gotten us anywhere in terms of solutions. Hoping you or someone else who has experienced this can offer some guidance!

Thanks!

Re: Session end reason: tcp-fin and aged-out?

geometrydashhero — Sat, 04 Dec 2021 19:00:00 GMT

Great thread ! Got lot of value from it.

Re: Session end reason: tcp-fin and aged-out?

fwmike2 — Fri, 28 Jan 2022 15:29:26 GMT

@TMSSupport

If you have the issue again, get on the CLI and use:

show arp all

to see if you have an entry for your device's default route next hop. If it's not in the ARP table, you may be having a physical or layer 2 issue where the firewall is not able to forward to your Internet provider's upstream device because it doesn't have a MAC for it.