preferred-nexthop
Syntax
preferred-nexthop (highest-ip | lowest-ip);Hierarchy Level
[edit routing-instances name protocols evpn]
Description
The EVPN Preferred Next Hop feature introduces a sophisticated mechanism for handling unicast data traffic in all-active multihomed environments, such as EVPN E-LAN, EVPN-VPWS, and EVPN E-Tree deployments. This feature facilitates the selection of a preferred overlay next-hop IP address, establishing an active/backup model that optimizes unicast traffic management without disrupting broadcast, unknown unicast, and multicast (BUM) traffic operations or designated forwarder (DF) election processes. By integrating with BGP Prefix Independent Convergence (BGP-PIC), users achieve rapid network convergence when the primary provider edge (PE) fails, minimizing downtime and enhancing network reliability.
You must configure dynamic-list-next-hop under the edit
routing-options forwarding-table hierarchy in order to use the
preferred-nexthop statement.
user@device# set routing-options forwarding-table dynamic-list-next-hop
You will see a commit error if DLNH is not configured.
user@device# set routing-instances evpn-vxlan protocols evpn preferred-nexthop highest-ip commit [edit routing-instances evpn-vxlan protocols] 'evpn' DLNH config is not enabled error: configuration check-out failed
You will see a commit error if your routing-instance uses vxlan or
srv6 encapsulation under the edit routing-instances
<instance-name> protocols evpn encapsulation hierachy.
user@device# set routing-instances evpn-vxlan protocols evpn preferred-nexthop highest-ip commit [edit routing-instances evpn-vxlan protocols evpn preferred-nexthop] 'preferred-nexthop highest-ip' preferred-nexthop not supported with encapsulation vxlan/srv6 error: commit failed: (statement constraint check failed)
Options
| highest-ip |
Use highest IP address as preferred nexthop |
| lowest-ip |
Use lowest IP address as preferred nexthop |
Release Information
Statement introduced in Junos OS Evolved Release 26.2R1.