Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

multihop

Syntax

multihop {no-nexthop-change;ttl ttl-value;}

Hierarchy Level

[edit logical-systems logical-system-name protocols bgp],[edit logical-systems logical-system-name protocols bgp group group-name],[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address],[edit protocols bgp],[edit protocols bgp group group-name],[edit protocols bgp group group-name neighbor address],[edit routing-instances routing-instance-name protocols bgp],[edit routing-instances routing-instance-name protocols bgp group group-name],[edit routing-instances routing-instance-name protocols bgp group group-name neighbor address]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Statement introduced in Junos OS Release 11.3 for the QFX Series.

Description

Configure an EBGP multihop session.

For Layer 3 VPNs, you configure the EBGP multihop session between the PE and CE routing devices. This allows you to configure one or more routing devices between the PE and CE routing devices.

An external confederation peer is a special case that allows unconnected third-party next hops. You do not need to configure multihop sessions explicitly in this particular case because multihop behavior is implied.

If you have external BGP confederation peer-to-loopback addresses, you still need the multihop configuration.

Note: You cannot configure the accept-remote-nexthop statement at the same time.

Default

If you omit this statement, all EBGP peers are assumed to be directly connected (that is, you are establishing a nonmultihop, or “regular,” BGP session), and the default time-to-live (TTL) value is 1.

The remaining statements are explained separately.

Options

Required Privilege Level

routing—To view this statement in the configuration.

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

 

Related Documentation

 

Published: 2013-04-03

Previous Page Next Page