NOTE:
If an ACL match criterion is defined, packets are matched against the ACL rules, and 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.
Configuring actions for a node
Step
1.
Enter system
view.
2.
Enter policy
node view.
3.
Set next hops.
Configuring PBR
Configure PBR by applying a policy to an interface. PBR uses the policy to guide the forwarding of
packets received on the interface. The specified policy must exist. Otherwise, the interface PBR
configuration fails.
You can apply only one policy to an interface. Before you apply a new policy, you must first remove the
current policy from the interface.
You can apply the same policy to multiple interfaces.
To configure interface PBR:
Step
1.
Enter system
view.
2.
Enter interface
view.
3.
Apply a policy
to the interface.
Displaying and maintaining PBR
Execute display commands in any view and reset commands in user view.
Task
Display PBR policy information.
Command
system-view
policy-based-route policy-name [ deny |
permit ] node node-number
apply next-hop [ vpn-instance
vpn-instance-name ] { ip-address [ direct ]
[ track track-entry-number ] }&<1-n>
Command
system-view
interface interface-type interface-number
ip policy-based-route policy-name
Remarks
N/A
N/A
By default, no next hop is specified.
You can specify multiple next hops for
backup, which are executed in the
order they are configured.
The value of n is 2.
Remarks
N/A
N/A
By default, no policy is applied to the
interface.
Command
display ip policy-based-route [ policy policy-name ]
270