This article describes the data to be collected for KRT issues in production and resolve the error
KRT queue is stuck from the "show krt queue"
show krt queue
Routing table add queue: 0 queued
Interface add/delete/change queue: 0 queued
Top-priority deletion queue: 0 queued
Top-priority change queue: 0 queued
Top-priority add queue: 0 queued
high priority V4oV6 tcnh delete queue: 0 queued
high prioriy anchor gencfg delete queue: 0 queued
High-priority multicast add/change: 0 queued
Indirect next hop top priority add/change: 0 queued
Indirect next hop add/change: 0 queued
high prioriy anchor gencfg add-change queue: 0 queued
MPLS add queue: 0 queued
Indirect next hop delete: 0 queued
High-priority deletion queue: 0 queued
MPLS change queue: 0 queued
High-priority change queue: 0 queued
High-priority add queue: 1 queued
ADD nhtype Router index 0 (25421)
error 'ENOENT – Item not found'
kqp '0x7a1ce80'
Normal-priority indirect next hop queue: 0 queued
Normal-priority deletion queue: 0 queued
Normal-priority composite next hop deletion queue: 0 queued
Low prioriy Statistics-id-group deletion queue: 0 queued
Normal-priority change queue: 0 queued
Normal-priority add queue: 0 queued
Least-priority delete queue: 0 queued
Least-priority change queue: 0 queued
Least-priority add queue: 0 queued
Normal-priority pfe table nexthop queue: 0 queued
EVPN gencfg queue: 0 queued
Normal-priority gmp queue: 0 queued
Routing table delete queue: 0 queued
Low priority route retry queue: 0 queued
From the syslog messages:
May 10 13:35:27 2024 re0.router rpd[24276]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
May 10 13:37:48 2024 re0.router rpd[24276]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
May 10 13:40:18 2024 re0.router rpd[24276]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
May 10 13:42:38 2024 re0.router rpd[24276]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
May 10 13:45:00 2024 re0.router rpd[24276]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
From the krt async output, we see that 2600:6001:d1c:b8a6 is the IP due to which the error is seen
show krt async queue detail
ADD gf 6 inst id 0 2600:6001:f167::/48 nexthop
2600:6001:d1c:b8a6::, ae17.1558
kqp '0x229c7480'
Generation: 420, Route table: 0
Input Filters: FIA-Filter-v6
Addresses, Flags: Is-Preferred Is-Primary
Destination: 2600:6001:d1c:b8a6::/64, Local: 2600:6001:d1c:b8a6::1
Generation: 664
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::86b5:9c06:1663:d7c3
The static route config next-hop is pointing to 2600:6001:d1c:b8a6::. On correcting the IP to 2600:6001:d1c:b8a6::2, the retries cleared.
route 2600:6001:f167::/48 next-hop 2600:6001:d1c:b8a6::;
route 2600:6001:1ad3::/48 next-hop 2600:6001:a5c:210e::2;
}
set routing-options rib inet6.0 static route 2600:6001:f167::/48 next-hop 2600:6001:d1c:b8a6::2
show | compare
[edit routing-options rib inet6.0 static]
route 2600:6001:de9::/48 { ... }
! route 2600:6001:1ad3::/48 { ... }
[edit routing-options rib inet6.0 static route 2600:6001:f167::/48]
- next-hop 2600:6001:d1c:b8a6::;
+ next-hop 2600:6001:d1c:b8a6::2;
2024-05-14 : Article Created
2026-06-08: Mark to be external