Configuring a policy
Creating a node
Step
1.
Enter system view.
2.
Create a node for a policy, and
enter policy node view.
Configuring match criteria for a node
Step
1.
Enter system
view.
2.
Enter policy
node view.
3.
Configure an
ACL match
criterion.
NOTE:
An ACL match criterion uses the specified ACL to match packets regardless of the permit or deny action
and the time range of the ACL. If the specified ACL does not exist, no packet can match the criterion.
Configuring actions for a node
Step
1.
Enter system
view.
2.
Enter policy
node view.
3.
Set next hops.
Command
system-view
policy-based-route policy-name
[ deny | permit ] node node-number
Command
system-view
policy-based-route policy-name [ deny | permit ] node
node-number
if-match acl acl-number{ acl-number | name acl-name }
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>
Remarks
N/A
N/A
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.
316
Remarks
N/A
By default, no policy node is
created.
Remarks
N/A
N/A
By default, no ACL
match criterion is
configured.