Invalid next-hop messages are seen in the syslog. These next-hop messages have no operational impact.
Invalid next-hop messages are reported in the syslog: Mar 17 10:43:05.162 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:06.362 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:06.762 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:07.162 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:07.562 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:44:18.952 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:46:46.931 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:48:22.720 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:48:42.917 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:16:30.495 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:16:37.894 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:54:20.598 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:54:32.996 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4
Mar 17 10:43:05.162 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:06.362 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:06.762 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:07.162 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:43:07.562 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:44:18.952 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:46:46.931 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:48:22.720 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 10:48:42.917 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:16:30.495 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:16:37.894 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:54:20.598 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4 Mar 17 11:54:32.996 dover-re0 /kernel: rnh_index_alloc: Failing Invalid nexthop index allocation for type=2, op=4
This is expected behavior and it has no operational impact. These messages are logged in all Junos images, as they are kernel informational messages. If you want to prune these messages, configure one of the following:
set system syslog file messages kernel notice OR
Host xxx.xxx.xxx.xxx { any any; authorization info; match "!op=4"; <<<<< ignores messages with op=4 }"