Description

These logs are being generated every minute and we would like to know how to solve it.

Symptoms

<181>1 2024-05-02T09:00:04.435-07:00 device0 /kernel - - - tcp_timer_keep: Dropping socket connection due to keepalive timer expiration, idle/intvl/cnt: 7200000/75000/8 <181>1 2024-05-02T09:00:04.435-07:00 device0 /kernel - - - tcp_timer_keep:Local(0x81100001:59095) Foreign(0x8f100001:33010)

 

<180>1 2024-05-02T09:00:09.325-07:00 device0 dot1xd 2119 JTASK_IO_CONNECT_FAILED [[email protected] task-name="ESP CLIENT:33010.143.16.0.1+33010" remote-address="143.16.0.1" error-message="No route to host"] ESP CLIENT:33010.143.16.0.1+33010: Connecting to 143.16.0.1+33010 failed: No route to host.

 

 

Solution

The message can be safely ignored, but if you want to remove it, you have 2 options:

 

1) You can keep this "tcp_timer_keep", "JTASK_IO_CONNECT_FAILED" logs separated from the other logs, you can create a log file under the [edit system syslog] hierarchy and then configure it to store these logs with the "match" statement.

Examples:

set system syslog file <filename> match "!(tcp_timer_keep)"

set system syslog file <filename> match "!(JTASK_IO_CONNECT_FAILED)"

 

2) Upgrade a version listed on PR1580667 or 21.4R3-S4.9 where it has not seen.

 

Modification History

2024-05-18 : Article Created