neighbor (Protocols BGP)
Syntax
neighbor address {
accept-remote-nexthop;
advertise-bgp-static
advertise-external <conditional>;
advertise-inactive;
(advertise-peer-as | no-advertise-peer-as);
as-override;
authentication-algorithm algorithm;
authentication-key key;
authentication-key-chain key-chain;
cluster cluster-identifier;
damping;
description text-description;
enforce-first-as;
export [ policy-names ];
family {
(inet | inet6 | inet-mvpn | inet6-mpvn | inet-vpn | inet6-vpn | iso-vpn | l2-vpn) {
(any | flow | multicast | unicast | signaling) {
accepted-prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
damping;
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
rib-group group-name;
topology name {
community {
target identifier;
}
}
}
flow {
no-validate policy-name;
}
labeled-unicast {
accepted-prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
aggregate-label {
community community-name:
}
explicit-null {
connected-only;
}
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
resolve-vpn;
rib inet.3;
rib-group group-name;
topology name {
community {
target identifier;
}
}
}
}
forwarding-context
route-target {
advertise-default;
external-paths number;
accepted-prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
}
signaling {
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
}
}
forwarding-context rti-name;
graceful-restart {
disable;
restart-time seconds;
stale-routes-time seconds;
}
hold-time seconds;
import [ policy-names ];
ipsec-sa ipsec-sa;
keep (all | none);
local-address address;
local-as autonomous-system <private>;
local-interface interface-name;
local-preference preference;
log-updown;
metric-out (metric | minimum-igp <offset> | igp <offset>);
mtu-discovery;
multihop <ttl-value>;
multipath {
multiple-as;
}
no-aggregator-id;
no-client-reflect;
out-delay seconds;
passive;
peer-as autonomous-system;
preference preference;
rfc6514-compliant-safi129;
tcp-aggressive-transmission;
tcp-mss segment-size;
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
}
vpn-apply-export;
}
Hierarchy Level
[edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name], [edit protocols bgp group group-name], [edit protocols bgp family prefix-limit (inet | inet6)(any | flow | labeled-unicast | multicast | unicast)], [edit routing-instances routing-instance-name protocols bgp group group-name]
Description
Explicitly configure a neighbor (peer). To configure
multiple BGP peers, include multiple neighbor statements.
By default, the peer’s options are identical to those
of the group. You can override these options by including peer-specific
option statements within the neighbor statement.
The neighbor statement is one of the statements you
can include in the configuration to define a minimal BGP configuration
on the routing device. (You can include an allow all statement
in place of a neighbor statement.)
On MX Series routers configured with enhanced subscriber
management, you can use this statement to statically provision a subscriber’s
client IP address as the BGP neighbor IP address. This is supported
for only LNS subscribers. With enhanced subscriber management, you
must also configure the routing-services statement at the [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] hierarchy level.
Options
address—IPv6
or IPv4 address of a single peer.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.