384
PBR and track
Associated with a Track object, PBR can sense topology changes faster. You can associate PBR with a
track entry when configuring the outgoing interface, default outgoing interface, next hop, and default
next hop to dynamically determine link reachability. The PBR configuration takes effect when the status of
the associated Track object is
Positive
or
Invalid
.
NOTE:
For more information about track-PBR collaboration, see
High Availability Configuration Guide.
Configuring PBR (using a QoS policy)
Before configuring PBR, complete the following tasks:
•
Configure a QoS policy by configuring the match criteria and a redirection action for PBR.
•
Apply the QoS policy by defining the occasion to which the PBR applies.
Configuring a QoS policy
Follow these steps to configure traffic redirection:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a class and enter class
view
traffic classifier
tcl-name
[
operator
{
and
|
or
} ]
—
Configure the match criteria
if-match
match-criteria
—
Exit class view
quit
—
Create a behavior and enter
behavior view
traffic behavior
behavior-name
Required
Configure a traffic redirection
action
redirect next-hop
{
ipv4-add1
[
ipv4-add2
] |
ipv6-add1
[
interface-type
interface-number
] [
ipv6-add2
[
interface-type interface-number
] ] }
[
fail-action
{
discard
|
forward
} ]
Optional
Exit behavior view
quit
—
Create a policy and enter
policy view
qos policy
policy-name
—
Associate the class with the
traffic behavior in the QoS
policy
classifier
tcl-name
behavior
behavior-name
—
NOTE:
The default option for the
fail-action
is
forward
.
Applying the QoS policy
When configuring PBR, you can apply a QoS policy to the following occasions:
