61
• 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.
To associate Track with PBR:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Create a policy or policy
node and enter PBR policy
node view.
policy-based-route policy-name [ deny |
permit ] node node-number
N/A
3. Define a match criterion.
• 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 }
By default, no packets
are filtered.
4. Associate Track with PBR.
• Set the outgoing interface, and associate it
with a track entry:
apply output-interface { interface-type
interface-number [ track
track-entry-number ] }&<1-n>
• Set the next hop, and associate it with a
track entry:
apply next-hop [ vpn-instance
vpn-instance-name | inbound-vpn ]
{ ip-address [ direct ] [ track
track-entry-number ] }&<1-n>
• Set the default outgoing interface, and
associate it with a track entry:
apply default-output-interface
{ interface-type interface-number [ track
track-entry-number ] }&<1-n>
• Set the default next hop, and associate it
with a track entry:
apply default-next-hop [ vpn-instance
vpn-instance-name | inbound-vpn ]
{ ip-address [ direct ] [ track
track-entry-number ] }&<1-n>
Use at least one of the
commands.
To associate Track with IPv6 PBR:
Step Command Remarks
1. Enter system view.
system-view N/A