There are two modes of deploying redirect policies on VPRN interfaces. The functionality supported depends on the configuration of the redirect-policy router option with config>filter>redirect-policy>router:
Redirect policy with router option enabled (recommended):
When a PBR destination is up, the PBR lookup is performed in the redirect policy's configured routing instance. When that instance differs from the incoming interface where the filter policy using the specific redirect policy is deployed, the PBR action is equivalent to forward next-hop router filter policy action.
When all PBR destinations are down (or a hardware does not support action router), action forward is programmed and the PBR lookup is performed in the routing instance of the incoming interface where the filter policy using the specific redirect policy is deployed.
Any destination tests configured are executed in the routing context specified by the redirect policy.
Changing router configuration for a redirect policy brings all destinations with a test configured down. The destinations are brought up after the test confirms reachability based on the new redirect policy router configuration.
Redirect policy without router option disabled (no router) or with router options not supported (legacy):
When a PBR destination is up, the PBR lookup is performed in the routing instance of the incoming interface where the filter policy using the specific redirect policy is deployed.
When all PBR destinations are down, action forward is programmed and the PBR lookup is performed in the routing instance of the incoming interface where the filter policy using the specific redirect policy is deployed.
Any destination tests configured are always executed in the Base router instance regardless of the router instance of the incoming interface where the filter policy using the specific redirect policy is deployed.
Restrictions:
Only unicast-rt-test and ping-test are supported when the router option is enabled.