402
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.
ip-address: Specifies the next-hop IP address. Without the vpn-instance vpn-instance-name option, the
next hop belongs to the public network.
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 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.
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
# S e t a d i r e ct l y - c o n ne c t e d n ex t h o p 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