- multihop {
-
ttl-value;
- no-nexthop-change;
- }
- [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]
Statement introduced before JUNOS Release 7.4.
Configure an EBGP multihop session.
External confederation peering is a special case that allows unconnected third-party next hops. You do not need to configure multihop sessions explicitly in this particular case; multihop behavior is implied.
If you have confederation external BGP peer-to-loopback addresses, you still need the multihop configuration.
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.
ttl-value—Configure the maximum TTL value for the TTL in the IP header of BGP packets.
no-nexthop-change—Specify not to change the BGP next-hop value; for route advertisements, specify the no-nexthop-self option.
See Configuring an EBGP Multihop Session.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.