HP 6125XLG - PBR and Track; PBR Configuration Task List; Configuring a Policy; Creating a Node

269
A node that has no if-match clauses matches any packet.
PBR and Track
PBR can work with the Track feature to dynamically adapt the availability status of a node configured
with an apply clause to the link status of a tracked next hop.
When the track entry associated with the node changes to negative because the next hop is detected as
being unavailable, the node cannot be used for forwarding. When the track entry changes to positive or
NotReady because the next hop is detected as being available, the node can be used for forwarding.
For more information about track-PBR collaboration, see High Availability Configuration Guide.
PBR configuration task list
Tasks at a
g
lance
(Required.) Configuring a policy:
• Creating a node
• Configuring match criteria for a node
• Configuring actions for a node
(Required.) Configuring PBR
Configuring a policy
Creating a node
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Create a node for a policy, and
enter policy node view.
policy-based-route policy-name
[ deny | permit ] node node-number
By default, no policy node is
created.
Configuring match criteria for a node
Ste
p
Command Remarks
1. Enter system
view.
system-view N/A
2. Enter policy
node view.
policy-based-route policy-name [ deny | permit ] node
node-number
N/A
3. Configure an
ACL match
criterion.
if-match acl acl-number
By default, no ACL
match criterion is
configured.