family (Protocols BGP)
Syntax
family {
(inet | inet6 | inet-vpn | inet6-vpn | iso-vpn) {
(any | flow | labeled-unicast | multicast | unicast | segment-routing-te) {
accepted-prefix-limit {
maximum number;
teardown <percentage-threshold> idle-timeout (forever | minutes);
drop-excess <percentage>;
hide-excess <percentage>;
}
add-path {
receive;
send {
include-backup-path backup_path_number;
multipath;
path-count number;
path-selection-mode { (all-paths | equal-cost-paths); }
prefix-policy [ policy-names ];
}
}
aigp [disable];
loops number;
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
protection;
rib-group group-name;
topology name {
community { target identifier; }
}
flow {
no-install;
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; }
export (Protocols BGP)
import (BGP)
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
resolve-vpn;
rib (inet.3 | inet6.3);
rib-group group-name;
traffic-statistics {
file filename <world-readable | no-world-readable>;
interval seconds;
}
}
}
route-target {
accepted-prefix-limit {
maximum number;
proxy-generate <route-target-policy route-target-policy-name>;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
advertise-default;
external-paths number;
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
}
(evpn | inet-mdt | inet-mvpn | inet6-mvpn | l2vpn) {
signaling {
accepted-prefix-limit {
maximum number;
teardown <percentage-threshold> idle-timeout (forever | minutes);
drop-excess <percentage>;
hide-excess <percentage>;
}
add-path {
receive;
send {
include-backup-path backup_path_number;
multipath;
path-count number;
path-selection-mode { (all-paths | equal-cost-paths); }
prefix-policy [ policy-names ];
}
}
aigp [disable];
damping;
loops number;
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
rib-group group-name;
}
}
traffic-engineering;
}
}
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 family prefix-limit (inet | inet6)(any | flow | labeled-unicast | multicast | unicast)], [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]
Description
Enable multiprotocol BGP (MP-BGP) by configuring BGP to carry network layer reachability information (NLRI) for address families other than unicast IPv4, to specify MP-BGP to carry NLRI for the IPv6 address family, or to carry NLRI for VPNs.
-
When you configure the family statement at multiple BGP hierarchy levels, Junos OS does not merge or inherit family settings between levels for a given neighbor.
-
For any neighbor that has an explicit family configuration, only the families configured at that neighbor level are used for that BGP session. The neighbor does not inherit any families from its group or from the global BGP level.
-
For neighbors without an explicit family configuration, the families configured at the group level (if any) are used. If there is no group-level family configuration, the global BGP family configuration (if present) is used for those neighbors.
| Configuration level | What applies to a neighbor | Notes | |
|---|---|---|---|
Global: [edit protocols bgp] |
Used only if there is no family configured at the group or neighbor level for that neighbor. | No inheritance into a neighbor that has its own family configured. | |
Group: [edit protocols bgp group
name] |
Used only for neighbors in the group that do not have their own family configured. | Overrides global family for those neighbors, but is ignored for neighbors with an explicit family. | |
Neighbor: [edit protocols bgp group
name neighbor
address] |
Used exclusively for that neighbor when configured. | No inheritance from group or global; only neighbor-level families take effect. |
For example, if a group is configured with multiple families, but a neighbor in that group has its own family statement, only the neighbor-level families are applied to that neighbor; the group-level families are not inherited.
Options
any—Configure the family type to be both unicast and multicast.
evpn—Configure NLRI parameters for Ethernet VPNs (EVPNs).
inet—Configure NLRI parameters for IPv4.
inet6—Configure NLRI parameters for IPv6.
inet-mdt—Configure NLRI parameters for the multicast distribution
tree (MDT) subaddress family identifier (SAFI) for IPv4 traffic in Layer 3 VPNs.
inet-mvpn—Configure NLRI parameters for IPv4 for multicast VPNs.
inet6-mvpn—Configure NLRI parameters for IPv6 for multicast
VPNs.
inet-vpn—Configure NLRI parameters for IPv4 for Layer 3 VPNs.
inet6-vpn—Configure NLRI parameters for IPv6 for Layer 3 VPNs.
inet6-vpn—Configure NLRI parameters for IPv6 for Layer 3 VPNs.
iso-vpn—Configure NLRI parameters for IS-IS for Layer 3 VPNs.
l2vpn—Configure NLRI parameters for IPv4 for MPLS-based Layer 2 VPNs
and VPLS.
labeled-unicast—Configure the family type to be labeled-unicast.
This means that the BGP peers are being used only to carry the unicast routes that
are being used by labeled-unicast for resolving the labeled-unicast routes. This
statement is supported only with inet and inet6.
multicast—Configure the family type to be multicast. This means that
the BGP peers are being used only to carry the unicast routes that are being used by
multicast for resolving the multicast routes.
unicast—Configure the family type to be unicast. This means that the
BGP peers only carry the unicast routes that are being used for unicast forwarding
purposes. The default family type is unicast.
segment-routing-te—Configure the family type to be segment routing
traffic engineering. This means that BGP peers only carry segment routing policies
for traffic steering.
inet-bgpmcast—Configure the family type to be multicast for
IPv4.
inet6-bgpmcast—Configure the family type to be multicast for IPv6.
route-target—Route Target is a 64-bit field used as part of the BGP
extended communities attribute to identify which route should be exported or
imported to specific VPN.
traffic-engineering—BGP traffic engineering involves optimizing and
managing traffic flow within a network using the BGP protocol.
If you enable family inet-vpn unicast for external BGP peer,
Junos considers the node is positioned as an AS boundary router in an
inter-provider scenario. Hence, it keeps the VPN-IPv4 routes in the routing
information base (bgp.l3vpn.0), and the labels associated with the prefixes in
the forwarding information base (FIB).
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.
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.
inet-mvpn and inet6-mpvn statements introduced in
Junos OS Release 8.4.
inet-mdt statement introduced in Junos OS Release 9.4.
Support for the loops statement introduced in Junos OS Release
9.6.
evpn statement introduced in Junos OS Release 13.2.
traffic-engineering statement introduced in Junos OS Release
14.2.
segment-routing-te option introduced in Junos OS Release 17.4R1 for
QFX Series, MX Series, and PTX Series with FPC-PTX-P1-A.