HPE FlexNetwork HSR6800 series Configuration Manual page 216

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 Invalid state of the track entry shows that the apply clause is valid.
The following objects can be associated with a track entry:
•
Outgoing interface.
•
Next hop.
•
Default outgoing interface.
•
Default next hop.
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. For more information about PBR, see Layer 3—IP
Routing Configuration Guide.
To associate Track with PBR:
Step
1. Enter system view.
2. Create a policy or policy
node and enter PBR policy
node view.
3. Define a match criterion.
Command
system-view
policy-based-route policy-name [ deny |
permit ] node node-number
•
Define a packet length match
criterion:
if-match packet-length min-len
max-len
•
Define an ACL match criterion:
if-match acl acl-number
209
Remarks
N/A
N/A
Optional.
By default, no packets are
filtered.