tFilterRPVrtrId

The value of the object tFilterRPVrtrId specifies the target routing
instance as part of the redirect policy. When the target routing
instance is configured (not equal to 0), the following applies:
              
- Ping and unicast-reachability tests configured in a redirect policy
  are now executed in the routing instance specified by the redirect
  policy regardless of what routing instance is the filter using this
  redirect policy deployed in.
              
- When packets are routed to a destination configured in a redirect
  policy with router instance specified (as result of filter match),
  routing is executed in the router instance context configured in
  the redirect policy regardless of the routing context for the
  interface on which the packet arrived.
  Note that if all destinations are down, the forward action is still
  executed in the routing instance of the incoming interface and not
  the routing instance of the redirect policy.
  If PBR specifies action forward router, then deploying the policy
  on card not supporting such action will result in action forward
  using incoming interface routing context.
              
- If the H/W does not support the next-hop router PBR action, action
  forward is executed (even if the router instance in the action is the
  same as the router instance of the incoming interface).
              
If the target routing instance is not configured (equal to 0), the
following applies:
              
- Redirect policy can be deployed in any VPRN or GRT routing context
  but a test will only run in GRT context regardless of where the policy
  is deployed.
              
- The PBR will execute in the routing context of the ingress interface.
              
SNMP and URL tests can be configured only if the target routing
instance is not configured.

MIB

TIMETRA-FILTER-MIB

OID

.1.3.6.1.4.1.6527.3.1.2.21.10.1.6

Type

column

Access

readwrite

Status

current

Parent

tFilterRedirectPolicyEntry

Table

tFilterRedirectPolicyTable

Siblings

12