320
Policy-based routing commands
apply next-hop
Use
apply next-hop
to set a next hop.
Use
undo apply next-hop
to remove the configuration.
Syntax
apply next-hop
[
vpn-instance
vpn-instance-name
] {
ip-address
[
direct
] [
track
track-entry-number
] }&<1-
n
>
undo apply next-hop
[ [
vpn-instance
vpn-instance-name
] {
ip-address
}&<1-
n
>
]
Default
No next hop is set.
Views
Policy node view
Predefined user roles
network-admin
Parameters
vpn-instance
vpn-instance-name
: Specifies an MPLS L3VPN instance by its name, a case-sensitive string
of 1 to 31 characters. The specified VPN must already exist. If no VPN is specified, the next hop belongs
to the public network.
ip-address
: Specifies the next-hop IP address.
direct
: Specifies that the next hop must be directly connected to take effect.
track
track-entry-number
: Specifies a track entry by its number in the range of 1 to 1024.
&<1-
n
>: Indicates that the argument before it can be entered up to
n
times. The value of
n
is 2.
Usage guidelines
You can specify up to
n
next hops for a policy node by configuring
n
next hops in the
apply next-hop
command or by executing the command
n
times.
With a next hop specified, the
undo apply next-hop
command removes the next hop.
Without any next hop specified, the
undo apply next-hop
command removes all next hops.
Examples
# Set a directly-connected next hop of 1.1.1.1.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply next-hop 1.1.1.1 direct