After you associate a track entry with an apply clause, the detection module associated with the track
entry sends Track the detection result of the availability of the tracked object.
•
The Positive state of the track entry indicates that the object is available, and the apply clause is
valid.
The Negative state of the track entry indicates that the object is not available, and the apply clause
•
is invalid.
The NotReady state of the track entry indicates that the apply clause is valid.
•
The following objects can be associated with a track entry:
•
Output interface.
Next hop.
•
Default output interface.
•
Default next hop.
•
Configuration prerequisites
Before you associate Track with PBR, create a policy or a policy node, and configure the match criteria.
Configuration procedure
You can associate a nonexistent track entry with PBR. The association takes effect only after you create the
track entry.
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 | name acl-name }
78
Remarks
N/A
N/A
By default, no match
criterion exists.