H3C Technologies H3C S10500 Series Switches - Manual (Page 385)

370
NOTE:
For more information about QoS policies, see ACL and QoS Configuration Guide.
Configuring PBR (using a PBR policy)
Defining a policy
Follow these steps to define a policy:
To do… Use the command… Remarks
Enter system view system-view ––
Create a policy or policy node and
enter PBR policy node view
policy-based-route policy-name
[ deny | permit ] node
node-number
Required
Define an ACL match criterion if-match acl acl-number Optional
Set an IP precedence type/value
apply ip-precedence { type |
value }
Optional
Set next hops
apply ip-address next-hop
ip-address [ direct ] [ track
track-entry-number ] [ ip-address
[ direct ] [ track
track-entry-number ] ]
Optional
You can specify two next hops at a
time.
• For local PBR, both the two next
hops take effect to implement
load sharing.
• For interface PBR, the first next
hop serves as the main next
hop and the second one serves
as the backup next hop.
Set default next hops
apply ip-address default next-hop
ip-address [ track
track-entry-number ] [ ip-address
[ track track-entry-number ] ]
Optional
You can specify two next hops at a
time.
• For local PBR, both the two next
hops take effect to implement
load sharing.
• For interface PBR, the first next
hop serves as the main next
hop and the second one serves
as the backup next hop.
NOTE:
•
If an ACL match criterion is defined, packets are matched against the ACL rules, whereas the permit or
deny action and the time range of the specified ACL are ignored. If the specified ACL does not exist, no
packet is matched.
• You can configure two next hops by using the apply ip-address next-hop command twice (first case) or
once (second case). After that, executing the apply ip-address next-hop command with a new next hop
will replace the earlier configured next hop in the first case, or will replace the second next hop specified
in the second case. To remove both next hops, execute the apply ip-address next-hop command again
by specifying two next hops.