HP 5900 series - Associating Track with PBR

132
Ste
p
Command Remarks
2. Associate the static
route with a track
entry to check the
accessibility of the
next hop.
• 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 [ track
track-entry-number ] } [ permanent ]
[ 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 [ track
track-entry-number ] } [ permanent ]
[ preference preference-value ] [ tag
tag-value ] [ description description-text ]
Not configured by default.
Associating Track with PBR
PBR is a routing mechanism based on user-defined policies. Different from the traditional
destination-based routing mechanism, PBR allows you to use a policy to route packets. You can specify
the next hop to guide the forwarding of packets that match specific ACLs. For more information about
PBR, see Layer 3—IP Routing Configuration Guide.
PBR cannot detect the availability of any action taken on packets. When the specified next hop fails, PBR
cannot sense the failure, and continues to forward matching packets to the next hop.
This problem can be solved by associating Track with PBR, which improves the flexibility of the PBR
application and enables PBR to sense topology changes.
After you associate a track entry with an apply clause, the detection module associated with the track
entry sends the detection result of the availability of the object (an interface or an IP address) specified
in the apply clause.
• The Positive state of the track entry shows that the object is available, and the apply clause is valid.
• The Negative state of the track entry shows that the object is not available, and the apply clause is
invalid.
• The NotReady state of the track entry shows that the apply clause is valid.
In PBR, only next hop can be associated with a track entry.
Configuration prerequisites
Before you associate Track with PBR, create a policy or a policy node and configure the match criteria as
well.
Configuration procedure
You can associate a nonexistent track entry with PBR. The association takes effect only after you use the
track command to create the track entry.