Please check message we got on our ACX7348 router every few seconds.
2025-06-29T00:00:00 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:03 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:06 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:15 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:18 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:21 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:24 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:27 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
2025-06-29T00:00:36 ACX7348-JTAC: packetio[18088]: [t:18088] [Info] CORE:SETUP: AFT Server not ready waiting...
The brcm kernel modules are loaded/unloaded based FEB board state - as part of online sequence modules modules are loaded, and during offline they get unloaded.
This is unlike pizza boxes, as the BCM PFE PCI device itself is only accessible after Feb is brought online.
When FEB is not loaded, knet interface is not created, hence file /tmp/aft is not created, this file syncs pfe and pktio.
Since this file is not present pktio keeps printing ERR severity log msg and floods log file, but once FEB is loaded, knet interface is created and file /tmp/aft is created,and these log msgs stop logging.
Since this state of the system is temporary/transient, severity of the log message changed to INFO.
This was initially an Error message & was later modified as notice.
We can filter this out from messages using below kb.
https://supportportal.juniper.net/s/article/Junos-Platform-Example-How-to-prevent-certain-syslog-messages-from-being-written-to-the-log-file