This article describes the issue of the “downward spike recived from pfe for ibytes_reply” log message being continuously generated.
The Junos device continuously logs the following messages:
May 11 06:12:50 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:10625039 ibytes_record:10694154 for ifl:82 loc_id:100030004000 May 11 07:17:49 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:14729085 ibytes_record:14799865 for ifl:82 loc_id:100030004000 May 11 11:42:50 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:31697100 ibytes_record:31767260 for ifl:82 loc_id:100030004000 May 11 11:47:50 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:32027662 ibytes_record:32110398 for ifl:82 loc_id:100030004000
You can use a regular expression to filter out these log messages. However, to avoid flooding of /var/log/messages, the router logs only the first 2000 of these messages and then stops until the next reboot (or pfed restart):
>show log messages | match ifl:82 | last 10 May 12 19:32:35 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:3552107661 ibytes_record:3552179185 for ifl:82 loc_id:100030004000 May 12 19:42:48 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:3552784281 ibytes_record:3552876117 for ifl:82 loc_id:100030004000 May 12 20:27:49 mx-router pfed: %USER-3: downward spike recived from pfe for ibytes_reply:3555651689 ibytes_record:3555744389 for ifl:82 loc_id:100030004000 > show log messages | match ifl:82 | count Count: 2000 lines