The user reported below trapcode and they did not see any service impact. The counter was increasing.
Router> show log messages.1.gz | match PECHIP
Jul 9 17:12:39.210 re0-root fpc3 INTR: throttle 3630sec PECHIP[0]:pe.irw.intr.status:do_not_transmit_in(0): (Count:1583081)
Jul 9 17:15:07.803 re0-root fpc2 INTR: throttle 3600sec PECHIP[0]:pe.irw.intr.status:do_not_transmit_in(0): (Count:371149)
This occurs quite commonly, not a concern. The main contributor to the "do_not_transmit_in" counter is "flt.Dispatcher.rule_deny" trap. It seems like packets are
getting filtered from Firewall filter configured on interface associated with PE-Chip. There are many other scenarios
when you see IRP set to "do_not_transmit" as it’s very generic message and is categorised as an info message. This can
be an expected log message for ttl expired or rule deny
fpc0 INTR: throttle 3600sec PECHIP[0]:pe.irw.intr.status:do_not_transmit_in(0): (Count:1593582)