Ingress (Chained Composite Next Hop) - Juniper ACX1000 Configuration Manual

ingress (Chained Composite Next Hop)

Syntax
Hierarchy Level
Release Information
Description
Default
Options
Copyright © 2017, Juniper Networks, Inc.
ingress {
(evpn | no-evpn);
(fec129-vpws | no-fec129-vpws);
(l2ckt | no-l2ckt);
(l2vpn | no-l2vpn);
l3vpn;
labeled-bgp;
}
[edit logical-systems logical-system-name routing-options forwarding-table
chained-composite-next-hop],
[edit routing-options forwarding-table chained-composite-next-hop]
This statement was introduced in Junos OS Release 12.1.
option was introduced in Junos OS Release 12.3.
labeled-bgp
, , , and
l2ckt l2vpn no-l2ckt
evpn , fec129-vpws , no-evpn
Release 14.1.
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
NOTE: The [edit logical-systems]
Series routers.
This statement is disabled by default.
—Enable or disable composite chained next hop for ingress EVPN
evpn | no-evpn
label-switched paths (LSPs).
fec129-vpws | no-fec129-vpws
FEC 129 virtual private wire service (VPWS) LSPs.
—Enable or disable composite chained next hop for ingress Layer 2 circuit
l2ckt | no-l2ckt
LSPs.
—Enable or disable composite chained next hop for ingress Layer 2 virtual
l2vpn | no-l2vpn
private network (VPN) LSPs.
options were introduced in Junos OS Release 13.3.
no-l2vpn
, and no-fec129-vpws options were introduced in Junos OS
statement is not supported in ACX Series routers.
hierarchy level is not applicable in ACX
—Enable or disable composite chained next hop for ingress
Chapter 41: Configuration Statements
1565