Associating Track With Pbr - HP MSR Series Configuration Manual

The static route is valid.
When you associate Track with static routing, follow these restrictions and guidelines:
You can associate a nonexistent track entry with a static route. The association takes effect only after
•
you create the track entry.
In static routing-Track-NQA collaboration, you must configure the same VPN instance name for the
•
NQA operation and the next hop of the static route. Otherwise, the accessibility detection cannot
operate correctly.
• If a static route needs route recursion, the associated track entry must monitor the next hop of the
recursive route. The next hop of the static route cannot be monitored. Otherwise, a valid route might
be considered invalid.
To associate Track with static routing:
Step
1. Enter system view.
2. Associate a static
route with a track
entry to check the
accessibility of the
next hop.

Associating Track with PBR

PBR uses user-defined policies (based on such criteria as the source address and packet length) to route
packets. You can specify parameters to guide the forwarding of the packets that match specific ACLs or
have specific lengths. The parameters include the VPN instance, packet priority, output interface, next
hop, default output interface, and default next hop. For more information about PBR, see Layer 3—IP
Routing Configuration Guide.
PBR cannot detect the availability of any action taken on packets. When an action is not available,
packets processed by the action might be discarded. For example, if the output interface specified for
PBR fails, PBR cannot detect the failure, and continues to forward matching packets out of the interface.
To enable PBR to detect topology changes and improve the flexibility of the PBR application, configure
Track-PBR-detection module collaboration.
Command
system-view
•
Method 1:
ip route-static dest-address { mask-length |
mask } { interface-type interface-number
[ next-hop-address ] | next-hop-address [ track
track-entry-number ] | vpn-instance
d-vpn-instance-name next-hop-address
[ permanent | track track-entry-number ] }
[ preference preference-value ] [ tag tag-value ]
[ description description-text ]
•
Method 2:
ip route-static vpn-instance
s-vpn-instance-name dest-address { mask-length
| mask } { interface-type interface-number
[ next-hop-address ] | next-hop-address
[ public ] [ track track-entry-number ] |
vpn-instance d-vpn-instance-name
next-hop-address [ permanent | track
track-entry-number ] } [ preference
preference-value ] [ tag tag-value ] [ description
description-text ]
77
Remarks
N/A
By default, Track is not
associated with static routing.