This article will describe about the below mentioned mosquitto syslog messages.

May 31 20:33:45.032 2024 EX4600_01 mosquitto[2283]: Client agentd-pfe-proxy_telemetry_publisher has exceeded timeout, disconnecting.
May 31 20:33:46.035 2024 EX4600_01 mosquitto[2283]: Socket send buffer size for broker is 65536
May 31 20:33:46.035 2024 EX4600_01 mosquitto[2283]: New connection from 128.0.0.1 on port 51883.
May 31 20:33:46.035 2024 EX4600_01 mosquitto[2283]: New client connected from 128.0.0.1 as agentd-pfe-proxy_telemetry_publisher (c1, k6000).

• Noticing below mosquitto syslog messages even though device is standalone and not enabled JTI [Junos telemetry interface].

May 31 20:33:45.032 2024 EX4600_01 mosquitto[2283]: Client agentd-pfe-proxy_telemetry_publisher has exceeded timeout, disconnecting.
May 31 20:33:46.035 2024 EX4600_01 mosquitto[2283]: Socket send buffer size for broker is 65536
May 31 20:33:46.035 2024 EX4600_01 mosquitto[2283]: New connection from 128.0.0.1 on port 51883.
May 31 20:33:46.035 2024 EX4600_01 mosquitto[2283]: New client connected from 128.0.0.1 as agentd-pfe-proxy_telemetry_publisher (c1, k6000).

• Not seeing any configuration related to telemetry except packages.

In QFX / EX Series devices with Junos telemetry interface (JTI), the data from Packet Forwarding Engines might not be published properly by the agentd process to the Message Queuing Telemetry Transport (MQTT) protocol and device will report mentioned syslog messages in this situation. However, these messages are harmless, and you can safely ignore.

Since these messages are harmless/if you are not using the telemetry services, you can disable them by using below commands or else you can filter these messages by adjusting syslog config.

# set system processes SDN-Telemetry disable
# commit

Please refer below KB article to filter certain syslog messages.

https://kb.juniper.net/InfoCenter/index?page=content&id=KB9382&actp=METADATA [juniper.net]