382NOTE:For more information about QoS policies, seeACL and QoS Configuration Guide.Configuring PBR (using a PBR policy)Defining a policyFollow these steps to define a policy:To do… Use the command… RemarksEnter system view system-view ––Create a policy or policy node andenter PBR policy node viewpolicy-based-route policy-name[ deny | permit ] nodenode-numberRequiredDefine an ACL match criterion if-match acl acl-number OptionalSet an IP precedence type/value apply ip-precedence { type |value } OptionalSet next hopsapply ip-address next-hopip-address [ direct ] [ tracktrack-entry-number ] [ ip-address[ direct ] [ tracktrack-entry-number ] ]OptionalYou can specify two next hops at atime.• For local PBR, both the two nexthops take effect to implementload sharing.• For interface PBR, the first nexthop serves as the main nexthop and the second one servesas the backup next hop.Set default next hopsapply ip-address default next-hopip-address [ tracktrack-entry-number ] [ ip-address[ track track-entry-number ] ]OptionalYou can specify two next hops at atime.• For local PBR, both the two nexthops take effect to implementload sharing.• For interface PBR, the first nexthop serves as the main nexthop and the second one servesas the backup next hop.NOTE:• If an ACL match criterion is defined, packets are matched against the ACL rules, whereas the permit ordeny action and the time range of the specified ACL are ignored. If the specified ACL does not exist, nopacket is matched.• You can configure two next hops by using the apply ip-address next-hop command twice (first case) oronce (second case). After that, executing the apply ip-address next-hop command with a new next hopwill replace the earlier configured next hop in the first case, or will replace the second next hop specifiedin the second case. To remove both next hops, execute the apply ip-address next-hop command againby specifying two next hops.
