Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[MX] Syslog message - "RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory"

0

0

Article ID: KB37417 KB Last Updated: 17 Sep 2021Version: 1.0
Summary:

This article explains why the "RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory" syslog message is seen frequently in the device syslog. It also explains that the message is logged when the segment-list is configured incorrectly.

Symptoms:

The following syslog messages can be seen every few minutes.

<snip>
Aug 19 08:54:49.289  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 08:58:09.964  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:01:30.355  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:04:51.029  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:08:11.391  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:11:32.100  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:14:52.569  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:18:13.148  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:21:33.728  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:24:54.194  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:28:14.733  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:31:35.232  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
Aug 19 09:34:55.831  mx960 rpd[24291]: RPD_KRT_Q_RETRIES: nexthop ADD: No such file or directory
<snip>
Cause:
When you run the show krt queue command, the following error can be seen.
lab@mx960> show krt queue 
Aug 19 09:45:55
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 priority 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 priority 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 (6467)
                    error 'ENOENT -- Item not found'
                    kqp '0x816f500'
Normal-priority indirect next hop queue: 0 queued
Normal-priority deletion queue: 0 queued
Normal-priority composite next hop deletion queue: 0 queued
Low priority 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

As you can see in the detailed output, the segment-list configuration to 4.4.4.4 in SR-TE is incorrect:

lab@mx960> show krt async queue detail 
Aug 19 09:46:13
          CHANGE TO indirect to 4.4.4.4 index 1048584 (0x760a208)
                    kqp '0x816cf80'
                ADD nhtype List index 0
                    kqp '0x8170d00'

lab@mx960> show route 4.4.4.4 
Aug 19 09:46:18

inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

4.4.4.4/32         *[IS-IS/18] 1w0d 16:20:06, metric 200
                    >  to 10.1.1.2 via ge-4/3/0.0
                       to 10.1.4.2 via lt-4/3/10.1

inet.3: 6 destinations, 16 routes (3 active, 0 holddown, 6 hidden)
+ = Active Route, - = Last Active, * = Both

4.4.4.4/32         *[SPRING-TE/6] 1w0d 16:20:06, metric 1, metric2 200
                    >  to 10.1.1.2 via ge-4/3/0.0
                       to 10.1.4.1 via lt-4/3/10.1         <<<  The next-hop IP address is not correct because the above configuration is not correct. It should be 10.1.4.2 (peer interface address).

Interface Setting

set interfaces lt-4/3/10 unit 1 family inet address 10.1.4.1/24

SR-TE Configuration

set protocols source-packet-routing segment-list path-pri-r4 segment1 ip-address 10.1.1.2
set protocols source-packet-routing segment-list path-sec-r4 segment1 ip-address 10.1.4.1       <<< It should be peer address.
set protocols source-packet-routing source-routing-path to-r4 to 4.4.4.4
set protocols source-packet-routing source-routing-path to-r4 primary path-pri-r4
set protocols source-packet-routing source-routing-path to-r4 secondary path-sec-r4
Solution:

To resolve this problem, use the correct segment-list:

set protocols source-packet-routing segment-list path-sec-r4 segment1 ip-address 10.1.4.2
commit

After correcting the segment-list configuration, the error will disappear as shown below, and no more syslog messages will not be logged in the message file again.

lab@mx960# run show krt queue
Aug 19 09:57:48
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 priority 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 priority 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: 0 queued
Normal-priority indirect next hop queue: 0 queued
Normal-priority deletion queue: 0 queued
Normal-priority composite next hop deletion queue: 0 queued
Low priority 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
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search