Configuring the next_hop attribute, Configuring a policy, Creating a node – H3C Technologies H3C S12500-X Series Switches User Manual
Page 302: Configuring match criteria for a node, Configuring actions for a node
288
87B
Configuring a policy
357B
Creating a node
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a node for a policy, and
enter policy node view.
policy-based-route policy-name
[ deny | permit ] node node-number
By default, no policy node is
created.
358B
Configuring match criteria for a node
Step 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 deny
action and the time range of the specified ACL are ignored. If the specified ACL does not exist, no packet
is matched.
359B
Configuring actions for a node
Step 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.