ingress (Chained Composite Next Hop)
Syntax ingress {
(evpn | no-evpn);
(fec129-vpws | no-fec129-vpws);
(l2ckt | no-l2ckt);
(l2vpn | no-l2vpn);
l3vpn;
labeled-bgp;
}
Hierarchy Level [edit logical-systems logical-system-name routing-options forwarding-table
chained-composite-next-hop],
[edit routing-options forwarding-table chained-composite-next-hop]
Release Information This statement was introduced in Junos OS Release 12.1.
labeled-bgp option was introduced in Junos OS Release 12.3.
l2ckt, l2vpn, no-l2ckt, and no-l2vpn options were introduced in Junos OS Release 13.3.
evpn, fec129-vpws, no-evpn, and no-fec129-vpws options were introduced in Junos OS
Release 14.1.
Description Allows you to configure chained composite next hops for devices handling transit traffic
in the network.
The other statements are explained separately.
NOTE: The extended-space statement is not supported in ACX Series routers.
NOTE: The [edit logical-systems] hierarchy level is not applicable in ACX
Series routers.
Default This statement is disabled by default.
Options evpn | no-evpn—Enable or disable composite chained next hop for ingress EVPN
label-switched paths (LSPs).
fec129-vpws | no-fec129-vpws—Enable or disable composite chained next hop for ingress
FEC 129 virtual private wire service (VPWS) LSPs.
l2ckt | no-l2ckt—Enable or disable composite chained next hop for ingress Layer 2 circuit
LSPs.
l2vpn | no-l2vpn—Enable or disable composite chained next hop for ingress Layer 2 virtual
private network (VPN) LSPs.
1565Copyright © 2017, Juniper Networks, Inc.
Chapter 41: Configuration Statements
To Next Page
Loading...
Need help?
General
