Post route change to the prefix, the routing table (RIB) gets updated correctly, but the same is not updated in the forwarding table (FIB) as the rpd-agent process might get into a wedged state where updates to older routes do not work.
RIB and FIB are not in sync. There are stale entries causing impact.

After we start seeing the "DEPENDENCY_UNRESOLVED" logs for object "net::juniper::rtnh::Route" for the apps, we can check if we are hitting the issue following the steps below:

1) show platform dependency-state summary | except ok - This command will show us the apps having issues.

2) show platform binding-queue incomplete node <> (node obtained from step 1) - This command will give us the apps having the issue, what object type is having issues, what is the potential reason/remedy for the issue.

Potential Reason: Delete is gated because its dependent(guid: xxxxxxxxxxxx) has not been deleted ====> confirming why there is dependency unresolved

Potential Remedy: request system application restart app rpdagent node re0 =====> confirming that the rpdagent is the app having issue

3) Check the system uptime. - but the issue is seen when there is a large churn of routes/objects in the system over a long time (after 200+ days of uptime).

4) Once it's confirmed it's the RPDagent and the system has over 200+ days of uptime, we will need to check if it's hitting the OLC (OLC: object logical clock) issue. This will let us know where we are in regards to the OLC threshold and whether we need to restart the rpdagent application or not. (please reach out to a JTAC technical representative to help with this step)

5) If the customer is able to provide certain prefixes that are having issues, then another symptom is there can be issues with those prefixes not being in sync between the RIB and FIB. Please use the below command to check the next-hop for such a (issue) prefix in the routing table and forwarding table.

show route x.x.x.x table inet.0 detail
show route forwarding-table destination x.x.x.x

Workaround:

Restart the rpdagent: request system application restart app rpdagent node <>

Resolution:

Code upgrade. Resolved in:

20.4R3-S5-EVO
20.4X6-EVO
21.1R3-S3-EVO
21.2R3-S3-EVO
21.3R3-S2-EVO
21.3R3-S3-EVO
21.4R3-S1-EVO
21.4X1-EVO
22.1R3-EVO
22.2R2-EVO
22.2R2-S1-EVO
22.2R3-EVO
22.3R2-EVO
22.3X80-D39-EVO
22.4R1-EVO
23.1R1-EVO