Pbr and track, Configuring pbr, Defining a policy – H3C Technologies H3C SR8800 User Manual
Page 283
267
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 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
Defining a policy
To define a policy:
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 an ACL match
criterion.
if-match acl acl-number
Optional.
4.
Set a VPN instance.
apply access-vpn vpn-instance
vpn-instance-name
Optional.
5.
Set an IP precedence.
apply ip-precedence value
Optional.
6.
Set next hops.
apply ip-address next-hop
ip-address [ direct ] [ track
track-entry-number ] [ ip-address
[ direct ] [ track
track-entry-number ] ]
Optional.
Two next hops at most can be
specified. Only one next hop can
be active at a time. The other is for
backup.
7.
Set default next hops.
apply ip-address default next-hop
ip-address [ track
track-entry-number ] [ ip-address
[ track track-entry-number ] ]
Optional.
Two default next hops at most can
be specified. Only one default next
hop can be active at a time. The
other is for backup.