314
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:
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 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 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.
Local PBR might affect local services, such as ping and Telnet. Do not configure local PBR unless
doing so is required.
To configure local PBR:
Step Command Remarks
1. Enter system view.
system-view
N/A
To Next Page
Loading...
Need help?
General