383
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 an IP
precedence.
apply precedence
{
type
|
value
}
By default, no IP precedence is
specified.
4.
Set next hops.
apply next-hop
[
vpn-instance
vpn-instance-name
] {
ip-address
[
direct
]
[
track track-entry-number
] }&<1-2>
By default, no next hop is specified.
You can specify two next hops for
backup in one command line or by
executing this command twice.
You can specify a maximum of two
next hops for a node.
The
vpn-instance
vpn-instance-name
option is not
supported in the current software
version.
5.
Set output
interfaces.
apply output-interface
{
interface-type
interface-number
[
track
track-entry-number
] }
By default, no output interface is
specified.
6.
Set default
next hops.
apply default-next-hop
[
vpn-instance
vpn-instance-name
] {
ip-address
[
direct
]
[
track track-entry-number
] }&<1-2>
By default, no default next hop is
specified.
You can specify two default next hops
for backup in one command line or by
executing this command twice.
You can specify a maximum of two
default next hops for a node.
The
vpn-instance
vpn-instance-name
option does not
take effect.
7.
Set the
service chain
information.
apply service-chain path-id service-path-id
[
path-index service-patch-index
]
By default, no service chain
information is set.
A policy that contains this clause is
not supported on Layer 3 Ethernet
subinterfaces.
This clause does not apply to
software forwarded packets.
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.
Summary of Contents for HPE FlexNetwork 7500 series
Page 505: ...493 Connector N A ...
