An Empty payload when it comes to the agentd will be dropped but before dropping an error message is logged.
Below logs are being spammed with AGENTD_PFE_SENSOR_EXPORT_DROPPED on FPC 4
Sep 8 05:15:39 re0-LAB agentd[30857]: AGENTD_PFE_SENSOR_EXPORT_DROPPED: AGENTD received empty payload for pfe sensor __default_fabric_sensor__ from fpc slot 4 Feb 20 03:05:44 re0-LAB agentd[30857]: AGENTD_PFE_SENSOR_EXPORT_DROPPED: AGENTD received empty payload for pfe sensor __default_fabric_sensor__ from fpc slot 4
This issue might be seen if the following conditions are met: * In Telemetry scenario * Subscribe to any PFE sensor * The PFE sensor exports packets with empty payload
In the Telemetry scenario, invalid data can be ignored when exported from PFE (empty payload). However, the system logs this event as an error. The fix in PR 1569167 changed the event as an info.
https://prsearch.juniper.net/problemreport/PR1569167Resolved in Versions: 19.2R3-S4, 19.3R3-S5, 19.4R3-S2, 20.1R3, 20.2R3, 20.3R2, 20.3R3, 20.3X75-D10, 20.3X75-D20, 20.4R2, 21.1R1, 21.2R1
If customer is still seeing this log on message log, it could be due to syslog configuration which is setup logging informational log.
For example:
file messages {
any notice;
authorization info;
daemon info;
interactive-commands none;
archive size 10m files 10 world-readable;
}
To avoid flooding of these message in syslog (older versions), we can filter out these log messages.
Please find reference KB:
https://supportportal.juniper.net/s/article/Junos-Platform-Example-How-to-prevent-certain-syslog-messages-from-being-written-to-the-log-file