R211x-HP Flexfabric 11900 Layer 3 - IP Routing Configuration Guide

288
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{ acl-number | name acl-name }
By default, no ACL
match criterion is
configured.
NOTE:
If an ACL match criterion is defined, packets are matched against the ACL rules, and the permit or den
y
action and the time ran
g
e of the specified ACL are i
g
nored. If the specified ACL does not exist, no packe
t
is matched.
Configuring actions 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. Set next hops.
apply next-hop [ vpn-instance
vpn-instance-name ] { ip-address [ direct ]
[ track track-entry-number ] }&<1-n>
By default, no next hop is specified.
You can specify multiple next hops for
backup or load sharing by executing
this command once or multiple times.
You can specify a maximum of two
next hops for a node.
Configuring PBR
Configuring local PBR
Configure PBR by applying a policy locally. PBR uses the policy to guide the forwarding of locally
generated packets. The specified policy must already exist. Otherwise, the local PBR configuration fails.
You can apply only one policy locally. Before you apply a new policy, you must first remove the current
policy.
Do not configure local PBR unless required.
To configure local PBR: