This article describes the steps on how we bypass PRPD routes.

In customer network same prefixes are learned via programmed route and BGP. Programmed routes are always preferred due to low preference value.

Programmed routes gets added/deleted using controller. In customer environment we have seen problem due to controller these PRPD routes gets stuck in router (stale entry) which causes black hole in customer network.

As we have same prefixes also learned via BGP we have given workaround policy to bypass these programmed routes so that BGP learned routes are used.

We can use below policy to bypass PRPD routes:
 

set policy-options policy-statement <policy-name> term <term name-1> from instance <affected routing-instance name>
set policy-options policy-statement <policy-name> term <term name-1> from protocol static
set policy-options policy-statement <policy-name> term <term name-1> from programmed
set policy-options policy-statement <policy-name> term <term name-1> then reject
set policy-options policy-statement <policy-name> term <term name-2> then accept
set routing-options forwarding-table export <policy-name>