Hi all!
I need a help with one specific problem more related to TCP session behavior of the MX router, than to SYSLOG. It seems like a bug on this Junos Version:
Prior to upgrading to 22.4R3-S3.3, the router would automatically re-establish the SYSLOG TCP session if no events were logged for a prolonged period. However, after the upgrade, this behavior has changed. Now, if the router fails to send a SYSLOG event within an hour, the firewall's session timeout triggers, terminating the connection. Subsequent attempts by the router to send events result in no response from the server, leading to the closure of the TCP session. The issue lies in the router's inability to re-initiate the SYSLOG TCP session after it is terminated.
------------------------------
IGOR BARTOLIC
------------------------------