[MX] "task AGENTD I/O.128.0.0.4+9500 addr 128.0.0.4+9500: Connection refused" log message

Summary:

This article explains why the "task AGENTD I/O.128.0.0.4+9500 addr 128.0.0.4+9500: Connection refused" message is logged, and whether any action is required to prevent the message from being logged.

Symptoms:

The following messages are constantly seen when SDN-Telemetry is disabled:

task_connect: task AGENTD I/O.128.0.0.4+9500 addr 128.0.0.4+9500: Connection refused
task_connect: task AGENTD I/O.128.0.0.4+9500 addr 128.0.0.4+9500: Connection refused
task_connect: task AGENTD I/O.128.0.0.4+9500 addr 128.0.0.4+9500: Connection refused

These messages are the result of the following configuration:

system {
    processes {
        SDN-Telemetry disable;
    }
}

Cause:

Junos Telemetry Interface provides highly scalable streaming of telemetry information. Unlike previous monitoring systems, such as SNMP, which used the so-called pull model, Junos Telemetry Interface uses the push model to collect data. The push model overcomes earlier scaling limits and reduces the processing required by the management station.

You can enable monitoring and streaming of data for various system resources, such as physical and logical interfaces and firewall filters. To monitor a specific system resource, you configure a sensor.

On MX devices, these sensors are enabled by default.

groups junos-defaults routing-options enable-sensors

Because the sensors are enabled and SDN-Telemetry is disabled, the routing protocol daemon (RPD) logs the connection refused messages.

Solution:

These messages are harmless as long as the telemetry interfaces are not used for monitoring. To filter these messages, use the following set command:

deactivate groups junos-defaults routing-options enable-sensors >>>>> This command needs to be typed completely because it is hidden.

Knowledge Base