Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

multi-bgp-path

Syntax

Hierarchy Level

Description

(Junos OS only) Enable multiple BGP path support for reporting an accurate BGP next-hop address for traffic load-balanced over multiple BGP peers in the ingress direction only. Without this statement, we report only the first in a list of next hops. To contain this accurate BGP next-hop address, we use the IPv4 BGP Nexthop Address (IE 18) field in the IPv4 and MPLS-IPv4 templates and the IPv6 BGP Nexthop Address (IE 63) field in the IPv6 and MPLS-IPv6 templates, for both the IPFIX and the version 9 formats. For IPv6 and MPLS-IPv6 flows, you also need to configure the ipv6-extended-attrib statement at the [edit chassis fpc slot-number inline-services flow-table-size] hierarchy level. When this feature is enabled, the fragmentIdentification (IE 54) field reports a value of 0.

For this feature to work, you must also configure the the nexthop-learning enable statement at the [edit services flow-monitoring version version template template-name] hierarchy level.

Existing flows must be manually cleared using the clear services accounting flow inline-jflow fpc-slot slot-number command when this feature is enabled or disabled, because common memory is used both for the fragmentIdentification (IE 54) field and for this feature. Otherwise, the export thread may wrongly misunderstand the fragment identifier of an existing flow as a next-hop address when enabled, or wrongly misunderstand the next-hop address of an existing flow as a fragment identifier when disabled. To avoid this situation, existing flows must be cleared from all FPC slots on which inline active flow monitoring is enabled.

When the number of BGP peers is 4000 or above, we cannot allocate an accurate BGP next-hop address for a new BGP peer. In such cases, a BGP next-hop address of zero is used for these BGP peers, and all flows destined to these BGP peers report the default BGP next-hop address, which is the first BGP next-hop address in a list of next hops. That is, this feature is not supported for these BGP peers with a BGP next-hop address of zero.

Default

Disabled. Without this statement, we report only the first in a list of BGP next hops.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 24.2R1.