This KB explains the log messages HALP-trinity_nh_indirect_nhid_inc_ref which is not service impacting but informational logs.

This log messages will be logged during the issue,

Feb 10 06:57:12.676 SGP001IGR03_RE1 fpc2 HALP-trinity_nh_indirect_nhid_inc_ref:2251 Failed to find the indirect addr for incr ref paddr: 1262072

Feb 10 06:57:12.684 SGP001IGR03_RE1 fpc2 HALP-trinity_nh_indirect_nhid_inc_ref:2251 Failed to find the indirect addr for incr ref paddr: 1261541

Feb 10 06:58:33.332 SGP001IGR03_RE1 fpc2 HALP-trinity_nh_indirect_nhid_inc_ref:2251 Failed to find the indirect addr for incr ref paddr: 1257115

Feb 10 06:58:33.449 SGP001IGR03_RE1 fpc1 HALP-trinity_nh_indirect_nhid_inc_ref:2251 Failed to find the indirect addr for incr ref paddr: 1846745

Feb 10 06:58:33.449 SGP001IGR03_RE1 fpc0 HALP-trinity_nh_indirect_nhid_inc_ref:2251 Failed to find the indirect addr for incr ref paddr: 1895699

Multicast or flood nexthop which uses indirect nexthop (path) requires mapping between indirect nh-id and jnh address to be maintained in s/w. This map entry is created when a flood or multicast nexthop is installed and removed when flood or multicast is uninstalled. In some scenarios, where indirect nexthop changes, map entry may be in an invalid state or not found. Error is logged in such scenarios.

There is no functional impact due to this error.

Ideally it has no impact & its just the informative log message logged in syslog.

Error message has been converted to syslog info. Since there is no functional impact.

As per the confidential PR 1687478 request you to upgrade the device to any of the below mentioned fixed junos version in order to resolve the issue.Resolved-In

junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3 junos:22.3R3-S2 junos:22.4R2-S2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1 junos:23.4R2

Trigger could be due to config removal/restoration was done multiple times in all the devcies. after around 5-6 attempts, observed below errors in yaris router(mx480).